The functions are detailed in Section 5. The principles, highlighted in text boxes, are designed to individually identify the essence of the related CM function, and can be used to collectively create a checklist of criteria to evaluate a CM program. In describing each CM function and its principles, this standard utilizes neutral Configuration Management terminology, while also providing equivalent terms, that have historically been used in various product environments see Table 2. There is no intent to express preference for any particular set of terminology. Table 1 illustrates some of the aliases for each phase name and identifies characteristics that apply in each one. Regardless of the titles chosen for these phases, or whether the product is a facility, software, an airplane or a machine screw, at some time in its history a product will go through all or most of these phases.
|Published (Last):||1 October 2009|
|PDF File Size:||5.15 Mb|
|ePub File Size:||2.37 Mb|
|Price:||Free* [*Free Regsitration Required]|
The functions are detailed in Section 5. The CM principles defined in this standard apply equally to internally focused enterprise information, processes, and supporting systems i. In an Enterprise CM context there are several methodologies for principle use by the enterprise: The principles of this standard provide direction for developing enterprise or functional CM plans focused on identifying, defining, authorizing, and managing CM activities.
Acquirer uses this standard to develop a checklist with which to evaluate supplier CM plans. Acquirer reviews and approves the supplier CM plan and makes it a requirement of the contract.
This method requires both parties to the acquisition to understand both the concepts and the tailoring. Acquirer uses the principles of this standard as the basis for developing either or both an enterprise CM requirements document or a specific project CM requirements document to impose on suppliers.
Compliance with the contractual requirements constitutes conformance with this standard. In describing each CM function and its principles, this standard utilizes neutral Configuration Management terminology, while also providing equivalent terms, that have historically been used in various product environments see Table 2.
There is no intent to express a preference for any particular set of terminology. Table 1 illustrates some of the aliases for each phase name and identifies characteristics that apply to each one.
Regardless of the titles chosen for these phases, or what the product is i. The phases can have considerable overlap, or the sequence of the phases might change or be repeated, e. Approved configurations of a product can be in the build, distribution, operation, and disposal phases simultaneously, and changes to those configurations may occur during all life cycle phases.
Appropriate application of CM functions enables a user of this standard to plan and implement a CM program for a product, project, or enterprise. An organization that has the responsibility for performing Configuration Management for a product during any period of its life cycle could be a commercial enterprise, e.
References in this standard to the acquirer i. An acquirer may be external to the developing and producing organization or may be internal such as marketing, management, or the using department.
Configuration Management functions related to a product may be the responsibility of several organizations during its life cycle. For example, an organization with the responsibility to design and build a product will perform Configuration Management during the definition and build phases; other organizations or government activities with responsibility for upgrading the product and servicing units will perform Configuration Management during the operation phase. Revision History.
SAE EIA 649
EIA-649 National Consensus Standard for Configuration Management