SAE EIA-649B-2011 Configuration Management Standard (Formerly TechAmerica EIA-649-B).pdf

《SAE EIA-649B-2011 Configuration Management Standard (Formerly TechAmerica EIA-649-B).pdf》由会员分享，可在线阅读，更多相关《SAE EIA-649B-2011 Configuration Management Standard (Formerly TechAmerica EIA-649-B).pdf（85页珍藏版）》请在麦多课文档分享上搜索。

1、_ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there

2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2013 SAE International All rights reserved. No part of this p

3、ublication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-497

4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/EIA649B TECHNICAL REPORT EIA-649 REV. B Issued 1998-05 Revised 2011-04 Configurat

5、ion Management Standard NOTICE This document has been taken directly from the original TechAmerica document and contains only minor editorial and format changes required to bring it into conformance with the publishing requirements of SAE Technical Standards. The release of this document is intended

6、 to replace the original with the SAE International document. Any numbers established by the original document remain unchanged. The original document was adopted as an SAE publication under the provisions of the SAE Technical Standards Board (TSB) Rules and Regulations (TSB 001) pertaining to accel

7、erated adoption of specifications and standards. TSB rules provide for (a) the publication of portions of unrevised specifications and standards without consensus voting at the SAE committee level, and (b) the use of the existing specification or standard format. TechAmerica Standard Configuration M

8、anagement Standard EIA-649-B April 2011 EIA-649-BANSI/EIA 649-B-2011 Approved: June 17, 2011 NOTICE TechAmerica Engineering Standards and Publications are designed to serve the public interest by eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and

9、improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TechAmerica from manufacturing or selling products

10、not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TechAmerica members, whether the standard is to be used either domestically or internationally. Standards and Publications are adopted by Tec

11、hAmerica in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TechAmerica does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This TechAmerica Standard is consider

12、ed to have International Standardization implications, but the ISO/IEC activity has not progressed to the point where a valid comparison between the TechAmerica Standard and the ISO/IEC document can be made. This Standard does not purport to address all safety problems associated with its use or all

13、 applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Standards Proposal No. 4766, formulated under the cognizance of the G-33

14、Data and Configuration Management Committee). This document is maintained under the ANSI/TechAmerica continuous maintenance program. Changes may be submitted at any time on any part of the standard using the TechAmerica Document Improvement Proposal at the back of this document or a similar method c

15、ontaining the same information. These comments shall be acted on for revision of the standard at the first meeting following working group resolution of the comment. Published by 2011 TechAmerica Standards distribution is unlimited. EIA-649-B Contents Foreword .iii 1. Introduction 1 2. Scope. 1 3. R

16、eferences 3 4. Terminology . 3 4.1 Definitions3 4.2 Symbols and Abbreviations .11 5. CM Functions and Principles 12 5.1 Configuration Management Planning and Management .13 5.1.1 Identify Context and Environment .13 5.1.2 Document the CM Planning .14 5.1.3 Apply Adequate CM Resources and Assign Resp

17、onsibility 15 5.1.4 Establish, Implement, and Maintain Procedures 15 5.1.5 CM Training .15 5.1.6 Assess Compliance and Effectiveness16 5.1.7 Supplier Configuration Management .16 5.1.8 Product Configuration Information Processes17 5.2 Configuration Identification.19 5.2.1 Product Configuration Infor

18、mation 19 5.2.2 Identifying the Enterprise, Products and Product Configuration Information20 5.2.3 Product Structure 24 5.2.4 Configuration Items26 5.2.5 Configuration Baselines26 5.2.6 Interface Management 31 5.3 Configuration Change Management33 5.3.1 Manage Requests for Changes34 5.3.2 Coordinati

19、on, Evaluation and Disposition of Requested Changes.37 5.3.3 Implementation of Approved Changes.39 5.3.4 Manage Requests for Variance.41 5.4 Configuration Status Accounting.44 5.4.1 CSA Information Capture and Reporting.45 5.4.2 Configuration Status Accounting Performance Measurements48 i EIA-649-B

20、5.5 Configuration Verification and Audit 49 5.5.1 Verifying Product Configuration49 5.5.2 Verifying incorporation of approved changes 50 5.5.3 Configuration Audits 50 Application Notes . 53 Annex A. Configuration Management Principles 54 Annex B. Related Standards, Handbooks and Processes. 63 Annex

21、C. Alphabetical List of Commonly Used CM Terms. 65 Annex D. Acknowledgment of Participants in GEIA Standard ANSI/EIA-649 . 73 List of Figures 1 CM Functions.12 2 Product Configuration Information20 3 Product Structure (Graphical View) 25 4 Product Structure (Indentured List View)26 5 Configuration B

22、aselines.29 6 Multiple Levels of Interface.32 7 Configuration Change Management Process Model .35 8 Change Coordination, Evaluation and Disposition Process Model.38 9 Change Implementation and Verification Model 41 10 CSA Information evolves throughout the product life cycle.45 11 CSA Information Ca

23、pture and Reporting Model.46 List of Tables 1 Phases of a Products Life Cycle .2 2 Terms, Definitions, Aliases and Related Terms 4 3 Interface Documentation Related to Configuration Baselines.32 4 Typical Change Classification Criteria36 5 Coordination, Evaluation and Disposition Actions .39 6 Typic

24、al CSA Input Sources and Outputs over the Product Life Cycle47 A-1 CM Principles in 649B 54 A-2 649 Revisions Principle Map.57 C-1 Alphabetical Listing of Common CM Terms 65 ii EIA-649-B Foreword When effectively applied, Configuration Management (CM) provides a positive impact on product life cycle

25、 cost. This standard is intended to be used when establishing, performing, or evaluating CM processes. CM is a comprehensive process for maintaining consistency of any products performance, functional and physical attributes with its requirements, design, and operational information. The essence of

26、CM, as portrayed in this standard, is the common sense application of CM functions and their underlying fundamental truths (principles), which have universal applicability across the broad spectrum of commercial and governmental enterprises around the globe. An understanding of not just what to do,

27、but why, is necessary to tailor the application of CM functions. This standard fulfills an important function; it provides the rational basis upon which to apply good judgment in both planning for and executing CM. The standard treats CM principles like axioms in a geometry text; they are statements

28、 of fact to which implementing actions relate. The implementing actions for each CM function are defined in CM planning guided by the type of product involved and the environments in which it is to be developed, produced, marketed, distributed, used, and maintained. Because of the broad scope of its

29、 applicability, this standard is not written as a requirements document, per se, but as the foundation document upon which requirements may be structured. In the acquirer/supplier context there are several methodologies to conformance by a supplier: Acquirer requires a CM plan consistent with 649 fr

30、om the supplier. Acquirer uses 649 to develop a checklist with which to evaluate supplier CM plans. Acquirer reviews and approves the supplier CM plan and makes it a requirement on contract. This method requires both parties to the acquisition to understand both the concepts and the tailoring. Acqui

31、rer uses 649 as the basis for developing either or both an enterprise CM requirements document or a specific project CM requirements document to impose on suppliers. The requirements documents may state 649 principles as requirements and reference 649 paragraphs. Compliance with the contractual requ

32、irements constitutes conformance with 649. Since terminology varies considerably in different application environments, the standard provides equivalent terminology (aliases) for each defined term so that a user can substitute familiar language in a specific context. For example, while those of us p

33、roducing US military products use the term configuration item to describe components that we apply CM to, others use designated item or some other term. Regardless of the term used, the same principles apply. Section 5 of this standard is “normative;” the remainder of this standard is “informative.”

34、 1This revision replaces all previous revisions of this standard in whole. 1Normative elements contain provisions with which it is necessary to conform (as described in the text above) in order to be able to claim compliance with the standard, while informative elements provide useful supportive inf

35、ormation. iii EIA-649-B Revision Description of Change Release Date Interim Interim EIA standard EIA/IS-649 initiated to replace MIL-STD-973 by a task to develop an industry configuration management standard by ANSI project PN-3414. Aug 1995 _ ANSI/EIA-649 initiated by ANSI project PN-3721 to submit

36、 the industry configuration management standard for approval by ANSI ballot. May 1998 A ANSI/EIA-649 initiated by a task to separate the normative principles from the informative material and expand the use of neutral terminology in the industry configuration management standard by ANSI project PN-4

37、766 and approved by ANSI Ballot. Oct 2004 B Revision B was initiated to enhance the standard, and to harmonize with other TechAmerica standards. Revision B is considered an entire rewrite of the standard, so change bar indicators in the margins are not utilized. iv EIA-649-B 1. Introduction Configur

38、ation Management (CM) is a technical and management process applying appropriate resources, processes, and tools to establish and maintain consistency between the product requirements, the product, and associated product configuration information. CM facilitates orderly identification of product att

39、ributes, and: Provides control of product information Manages product changes that improve capabilities, correct deficiencies, improve performance, enhance reliability and maintainability, facilitate interface control, or extend product life Manages departures from product requirements. The term “pr

40、oduct” in this standard should be interpreted as applicable to all product categories; e.g., documents, facilities, firmware, hardware, software, tools, materials, processes, services, systems. A disciplined CM process ensures that the product definition information and changes to that information a

41、re identified, approved, verified, and recorded in sufficient detail to produce and support the product throughout its life cycle; and that the product conforms to the specified requirements. The CM processes result in accurate configuration information to facilitate product interchangeability and c

42、onsistent reproducibility, and thus contributes to continuous safe and effective product development, production, utilization, support and retirement. Although the term “product configuration information” does not specifically include project or administrative types of information; e.g., schedules,

43、plans, and cost information, these and other documents are products and are subject to CM. Appropriate CM functions are applied to manage all information products that can have an impact on product conformance. CM execution requires a balanced and consistent implementation of CM functions guided by

44、CM principles throughout the products lifecycle. The investment in resources necessary to perform effective CM is returned in long term cost avoidance. Significant expenses (e.g., to re-establish the accuracy of product configuration information) are avoided when CM is applied continuously throughou

45、t the products life cycle. Continuous CM application provides authentic approved source information for: Administering warranties Determining liabilities Managing proposed changes Performing maintenance and overhaul Identifying and resolving safety or environmental issues. 2. Scope This standard def

46、ines five CM functions and their underlying principles. 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 pr

47、ogram. 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 parti

48、cular set of terminology. Similarly, this standard uses a neutral set of names for the phases of a products life cycle, which are generic enough to be easily mapped to the myriad of different life cycle models in use. Table 1 illustrates some of the aliases for each phase name and identifies charact

49、eristics that apply in each one. 1 EIA-649-B 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. The phases can have considerable overlap, or the sequence of the phases might change or be repeated, e.g., for product improvements and enhancements. Approved