PDM is used to manage information about items. ERP is used to schedule subordinate level items to support the master schedule. CMII is used to accommodate change and assure that requirements remain clear, concise and valid.
Requirements per ERP are the scheduled demands for physical items. Requirements per CM are the information sets that physical items must conform to. Both must be managed. Proper integration of the two is essential.
ERP is able to react to any type of configuration or schedule-related change and automatically replan (or renet) the demand for subordinate level items. The lack accuracy and stability in those netted requirements was the major downfall of MRP systems. The ditches along the MRP implementation trail were filled with wrecks. Today's ERP systems, although renamed, are on the same course.
Needed Solutions are Still the Same
Changes must be accommodated without compromising the accuracy and stability of requirements. Data integrity must also be assured. Those are the deficiencies that are addressed by CMII.
Material Requirements Planning, Manufacturing Resource Planning and now Enterprise Resource Planning. Besides name changes, what is the difference? There is little if any difference from a CMII point of view. The problems that caused MRP systems to flounder during the 70's and 80's continue to plague ERP systems in the 90's.
Making just-in-time work forced producers and suppliers to work as teams. It forced both parties to communicate better which, in turn, improved the suppliers ability to compensate for requirements that are less than clear, concise and valid.
Institute of Configuration Management Scottsdale, AZ 85261-5656 Tel: (480) 998-8600 Fax: (480) 998-8923 Email: info@icmhq.com