Featured Case Study
Moopi Migration Case Study
A Picture Perfect Solution - Eastman Kodak Company relies on Numbers Only, Inc. to migrate from Moopi to Baan Scheduler.
About the client: With the slogan "you push the button, we do the rest," George Eastman in 1888 put the first simple camera into the hands of a world of consumers. In so doing, he made what had been a cumbersome and complicated process easy to use and accessible to nearly everyone – worldwide. Today, Eastman Kodak Company and its affiliates are considered a world leader in innovative products and solutions. Kodak technology directly impacts over 75% of today’s Internet revolution.
The business challenge: With manufacturing processes depending upon accurate scheduling, having a system that is reliable and trustworthy is mission critical. The business need was to convert the Moopi 4.11 scheduling system to Baan Scheduler 6.3.1 without interrupting the existing manufacturing or scheduling processes. Going ‘live’ with the new system left no room for error.
Technology in focus: Under pressure to insure the highest degree of accuracy and on-time deliverables, Numbers Only, Inc. sent their best and brightest on-site to convert Kodak’s Moopi 4.11 scheduling system to Baan Scheduler 6.3.1. With only four weeks to plan and complete the project, the Numbers Only team drew upon their in-depth Baan knowledge and technical skills to meet the demands of quality and on-time delivery.
Solution Details: Migration from Moopi 4.11 to BAAN Scheduler 6.3.1.
- Upgrade through each version of Moopi
Option Two (the approach chosen by Kodak)
- Implement Baan Scheduler 6.3.1
- Migrate setup data from Moopi 4.11 to Baan Scheduler 6.3.1
- Configure & Optimize the Baan Scheduler Application as per Kodak’s functional and business requirements.
- Train end-users on the functionality and configuration of the newly implemented Baan Scheduler 6.3.1.
- Develop Custom Reports using the Scheduler Reporting tool.
- Integrated Baan Scheduler 6.3.1 with Kodak’s ERP system.
Download the complete case study