GEIA EIA-649-A-2004 National Consensus Standard for Configuration Management《配置管理的国家一致标准》.pdf

1、GEIA STANDARD ANSIIEIA-649-A 2004 Approved: 1012812004 National Consensus Standard for Configuration Management E IA-64 9-A October 2004 GOVERNMENT ELECTRONICS AND INFORMATION TECHNOLOGY ASSOCIATION z!EiEm _ ., . , .% . ., i. A Sector of the Electronic Industries Alliunc Copyright Government Electro

2、nics distribution is wilunted. Copyright Government Electronics correct deficiencies; improve performance, reliability, or maintainability; extend product life; or reduce cost, risk or liability. The term “product” in this standard should be interpreted as applicable to the generic product categorie

3、s; e.g., documents, facilities, firmware, hardware, software, tools, materials, processes, services, systems (also see definitions). Copyright Government Electronics a second organization with responsibility for upgrading the product and servicing units will perform Configuration Management during t

4、he operation phase. 1 Copyright Government Electronics e.g., re-commissioning. Approved configurations of a product can be in build, distribution, operation, and disposal phases simultaneously. Changes to approved configurations can be occurring simultaneously during any life cycle phase. Aliases fo

5、r the neutral terms used in this standard are provided Table 2, Table of Common Aliases. There is no intent to express preference for any particular terminology set. When planning and documenting a CM program, these terms and other aliases may be substituted for the neutral terminology. Table 1 Phas

6、es of a Products Life Cycle Terms Used Aliases Characteristics Conception Concept Exploration Marketing Predevelopment Research Study Analysis Functions Investigation Need Opportunity Mission Pre-Concept integrated product team, program review board amendment, engineering change order, engineering c

7、hange notice, engineering order, specification change notice, change notice, document change notice change proposal engineering change package, Engineering Change Request (ECR) Engineering Change Proposal (ECP), engineering change memo change control, change management, configuration control configu

8、ration change management configuration identification configuration item, group identifier, part identification, part number, product attribute, product configuration information, product definition, product definition information, product operational information, serial number, unique identifier, u

9、nit identifier Configuration Status Accounting configuration database, CSA, status accounting configuration verification and audit functional and physical configuration audit, product configuration verification, product consistency verification customer - external customer - internal acquirer, autho

10、rity, buyer, engineering user, external end user, procuring activity internal user, management, marketing department, specification activity engineering drawings and associated lists, product definition information, technical data design information/ documentation effectivity affected serial number(

11、s), block, change applicability, incorporation date(s), lot, point of embodiment, series enterprise company, contractor, organization approved, baselined, established, released, issued fixed group identifier interface document batch number, block number, date, date code, lot number interface control

12、 document, interface control drawing, interface specification life cycle phases I (See Table 1) process I methodology product assembly, component, configuration item, data, end item, entity, group, hardware, item, material or service, modeYsimulation, part, process, set, software, system, unit produ

13、ct attribute attribute, characteristic, requirement product information, product use documentation product configuration information product definition information attributes, configuration documentation, design basis, design information, design output, engineering drawing, interface control documen

14、t, interface document, requirements document, software requirements specification, software design document, software product specification, specification operation and maintenance instructions and other derived information, operational product operational 3 Copyright Government Electronics (2) one

15、of a series of sequentially-created variations of a product. configuration audit: The CM function that reviews processes and products to validate compliance with requirements, and verifies that products have achieved their required attributes and conform to released product definition information. C

16、onfiguration audits may be divided into separate functional and physical configuration audits. configuration baseline: Agreed-to information that identifies and establishes the attributes of a product at a point in time and that serves as basis for defining change. configuration change: An alteratio

17、n to a product and/or its product configuration information (as documented in a request for change). configuration change management: The CM function that ensures changes to a configuration baseline are properly identified, recorded, evaluated, approved or disapproved, and incorporated and verified

18、as appropriate. configuration identification: The CM function which (1) establishes a structure for products and product configuration information; (2) selects, defines, documents, and baselines product attributes; and (3) assigns unique identifiers to each product and product configuration informat

19、ion. 6 Copyright Government Electronics e.g., serial numbers, lot numbers, model, dates, or event at which the usage of a specific product configuration applies, a change to a specific product is to be or has been effected, or to which a variance applies. - fit: The ability of a product to interface

20、 or interconnect with, or become an integral part of, another product. - form: The shape, size, dimensions, and other physically measurable parameters that characterize a product. function: The action or actions that a product is designed to perform. functional attributes: Measurable performance par

21、ameters. These are expressed in terms of quantitative parameters; e.g., range, speed, lethality, reliability, maintainability, safety, and operating and logistical parameters, including their respective tolerances where applicable. group identifier: An alphanumeric identifier; e.g., lot, that (1) un

22、iquely identifies a group of like units of the same product which are manufactured or assembled under uniform conditions and are expected to function in a consistent manner. (2) uniquely designates a specific volumetric quantity (batch) of a material (usually a chemical mixture) created at the same

23、time and expected to have properties similar to, but not necessarily the same as, other batches created at other times. hardware: Products and their components; e.g., mechanical, electrical, electronic, hydraulic, pneumatic, made of material. interface: The product attributes that exist at a common

24、boundary of two or more products. 7 Copyright Government Electronics (2) Content model datatype, identification references, and other “atomic” properties associated with the character data or child elements of the associated element. nomenclature: (1) Names assigned to kinds and groups of products,

25、(2) formal designations assigned to products by customer or supplier; e.g., model number or model type, design differentiation, specific design series or configuration. part number or name: see product identifier. performance: A quantitative measure characterizing a physical or functional attribute

26、relating to the execution of an operation or function; e.g., quantity (how many or how much), quality (how well), coverage (how much area, how far), timeliness (how responsive, how frequent), and readiness (availability, missiodoperational readiness). phvsical attributes: Quantitative and qualitativ

27、e expressions of material features; e.g., composition, dimensions, fiiishes, form, fit, and their respective tolerances. product : Something that is used or produced to satisfy a need or is the result of a process; e.g., documents, facilities, firmware, hardware, materials, processes, services, soft

28、ware, systems. product attribute(s): Performance, functional, and physical characteristic(s) of a product. product configuration information: Information about a product consisting of product definition information and product operational information. product definition information: Information that

29、 defines the product requirements, documents the product attributes and is the authoritative source for configuration definition and control. product identifier: A name or alphanumeric identifier, unique to the issuing organization, used to designate products of the same configuration, and to differ

30、entiate them from other products. product operational information: Information developed from product definition information and used to test, operate, maintain and dispose the product. product structure: A hierarchical view of the relationship of products and component products. release (hardware):

31、 Authorization for dissemination of approved information and/or products subject to configuration change management. release (software): A particular version or revision of a software product that is made available for a specific purpose (for example, test release). 8 Copyright Government Electronic

32、s e.g., products. unit identifier: A sequentially-issued alphanumeric identifier used to designate a specific unit of a product. validation: Authentication that the requirements for a specific intended use or application have been fulfilled. variance: An approved departure from a specified requireme

33、nt(s) that does not require revision of approved product definition information. verification: Confirmation that a specified requirement has been fulfilled by the product. version: A specific configuration of a product which varies from other configurations of the product (see revision). 9 Copyright

34、 Government Electronics - training of CM personnel and any others who have CM responsibilities; - determination and application of adequate resources (including CM software - measurements as an indicator of performance and a basis for continuous - performance of Configuration Management by suppliers

35、 and subcontractors; - integration of the organizations product configuration information processes; - protection of the intellectual capital of the organization. cycle; tools) and facilities for product implementation; improvement; Comprehensive CM planning and management over the product life cycl

36、e is fundamental for a defined and repeatable CM system. CM functions focus on the product and shape the implementation of procedures, resulting in effective product configuration information management, cost avoidance, and product stability. 12 Copyright Government Electronics - type of support to

37、be provided, e.g., factory support, dealership support, independent maintenance center support, customer support, or no support required; - life cycle phases; - product and organizational constraints, e.g., product scope, product importance, product complexity, production quantity, quality requireme

38、nts, number and size of organizations involved, budgets, and schedules; information; - Configuration change management authority over the product configuration - intellectual property rights. CM planning should be re-evaluated following significant change affecting the context and environment, e.g.,

39、 changes in suppliers, or supplier responsibilities, changes in resource availabilities, changes in buyer contract, changes in the product. CM Planning should also be reviewed on a periodic basis for organizations in a sustaining mode to make sure that their application of CM functions to their orga

40、nization is kept current. 5.1.2 Document CM Planning Perform CM planning and document it. The form and format of the planning documentation; e.g., included with other project planning or included in a stand-alone CM plan, is not critical. However, execution of Configuration Management per the planni

41、ng documentation is critical for successful CM process implementation. 5.1.3 Assign Responsibility and Apply Adequate CM Resources It is necessary to plan and implement Configuration Management as a product flows through its life cycle, and it is essential that adequate resources be applied to maint

42、ain the needed controls and consistency. Resources are identified and assigned to perform the activities identified in CM planning. The required resources may include personnel, 13 Copyright Government Electronics - Released information has been reviewed and authorized for use or, if required, has b

43、een authorized for submittal to, or access by, a customer. Released information is under configuration change management. A new version cannot replace a released version until it has also been reviewed and authorized. The configuration of a document is fixed once it is in the released state and is o

44、nly changed by release of a superceding revision; - Archived information is released information (reviewed and approved) that is no longer authorized for continued use. It is kept as an historical record for reference purposes (e.g., redesign, failure analysis, regulatory requirements, etc.). Ensure

45、 delivered product configuration information is complete and appropriate for the users computing environment. The product configuration information should be acceptable to the user whether the exchange is by physical media, electronic data exchange, web access, or other means. When data are provided

46、 in floppy disks, tapes, CD-ROM, or other physical media, appropriate identification is affixed to the media to clearly identify the configuration of its contents. When it is impracticable to include all of the file identifications, a reference to an accompanying list, or to a “Read Me” file, should

47、 be created and tendered as part of the media. 5.1.9 Planning for Data Preservation The life cycles of the product, the information technology used to interpret the data, and the storage media are considered when planning for preservation of data. - Product: To determine what data must be retained a

48、nd for how long, consider the expected time the product will be in use (life span) as well as the applicable legal requirements for retaining the product data; 15 Copyright Government Electronics - Technology and Data: To ensure continued accessibilityheadability of the data, consider the expected l

49、ife spans of the associated technologies and plan for an appropriate frequency of update of both the technology and, where necessary, the data. 5.2 Configuration Identification The configuration identification function is the basis from which the configuration of products is defined and approved; products and documents are labeled; changes are managed; and accountability is maintained throughout the product life cycle. Configuration identification establishes: - A method for organizing the composition of the product elements and associated - Unique identification of products and