Configuration Management
Configuration management (CM) serves to ensure that configurations conform to their requirements. Configuration management was introduced in the 1960s to resolve the inability of defense contractors to build a 2nd unit identical to the 1st. Designs for the 2nd unit did not accurately represent the 1st unit. The ongoing flow of deviations and waivers prove that the integrity of design definition continues to be an issue. The needed solution is bigger than configuration management. CMII provides that solution.
|
Requirements Management
Requirements management serves to ensure that documented requirements are clear, concise and valid. Each document is a requirement to its user. Each document is identified by type, number and revision and is co-owned by its assigned creator (author) and a designated user. The creator is one who best understands the higher-level requirements. The designated user is one of all document users. Requirements management is most effective when each document is co-owned by its creator and one or more designated users. Resources spent on intervention are reduced with clear, concise and valid requirements.
|
Change Management/Change Control
Change management is a closed-loop process for releasing new information and upgrading existing information. A fast and efficient change process is a prerequisite for releasing new information quickly and for keeping existing information clear, concise and valid. To be fast and efficient, the information being changed must be properly identified, structured, linked and owned. The change management process is most effective when it is standardized across the organization and shared by all parties.
|
Product Structure/BOM Management
Product structure is a hierarchical decomposition of a product, typically known as the bill of materials (BOM). Within CMII this so called Physical Item Hierarchy is shared between Design and Manufacturing entities. Each item is directly linked to its own unique set of documents - including design and manufacturing information. This will lead to a common understanding of the product, its ingredients and all the requirements.
|
Product Variant Management
Handling of options or product variants is becoming more and more important. The goal is to minimize the lead time between the receipt of a customer's order and the actual delivery of the custom-built product. Another objective is to be as flexible as in a build-to-order environment. Build or assemble-to-order products tend to be very complex when products are sold in terms of "features and functions." Saleable features and functions must be translated into buildable units. Translations can be one to many, many to one or any combination.
|
Enabling PDM/PLM & ERP Software Tools
PDM/PLM, ERP and SCM are acronyms for software tools used to enhance the overall configuration management process. PLM is product lifecycle management. ERP is Enterprise Resource Planning. SCM is software configuration management. Although the names differ, their functionality is very similar. The capability of such tools has become increasingly robust since assessments against the CMII model were initiated in the year 2000.
|
