Search Results

This standard applies to all products and services produced for Aeronautics and Space enterprises and regulatory environments, including those produced by component facilities and technical and service support centers. If applied, this standard must be cited in the CM requirements of Enterprise Planning, Facilities Programs, Projects, and Supplier agreements. This standard applies throughout all phases of the program and project life cycle. CM is about the truth, trust, and traceability of products, data used to produce products, and processes throughout their life cycle and should be applied across the Enterprise at the process and product level. The significant data to which CM is applied includes scientific and engineering data; data that drives mission success; data that ensures IT security; and data used to make technical, programmatic, and business decisions. Proper application of CM is essential for product integrity and overall effectiveness.

The purposeful integration of existing and emerging technologies into CM practice will enable collaboration with supporting systems and provide stakeholders access to authoritative and trusted data in a timely fashion at their desktop to help drive educated decision making. This lays to rest the misguided myth that CM and supporting systems operate at cross-purposes. What does it mean to have CM in a world of new initiatives and 2-week sprints (i.e., time-boxed work periods), multiple increments producing Minimum Viable Products (MVP) and synchronized with Model Based Systems Engineering (MBSE) while being digitally transformed? MBSE initiatives drive the jump from “2D” data to “3D” data, thereby becoming a Model-Centric practice. Products now enable technology to push the product lifecycle management process to new levels of efficiency and confidence. This mindset is evidenced by five major functions of CM, as discussed below, and described in EIA-649C.

This document applies to hardware and software and provides CM requirements to be placed on contracts after being tailored by the Acquirer. The requirements have been organized by the following five CM functions: a Configuration Planning and Management b Configuration Identification c Configuration Change Management d Configuration Status Accounting e Configuration Verification and Audit

This handbook is intended to assist the user to understand the ANSI/EIA-649B standard principles and functions for Configuration Management (CM) and how to plan and implement effective CM. It provides CM implementation guidance for all users (CM professionals and practitioners within the commercial and industry communities, DoD, military service commands, and government activities (e.g., National Aeronautics and Space Administration (NASA), North Atlantic Treaty Organization (NATO)) with a variety of techniques and examples. Information about interfacing with other management systems and processes are included to ensure the principles and functions are applied in each phase of the life cycle for all product categories.

This standard defines 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 “best practice” criteria to evaluate a CM program. The CM principles defined in this standard apply equally to internally focused enterprise information, processes, and supporting systems (i.e., Enterprise CM - policy driven, supporting the internal goals needed to achieve an efficient, effective and lean enterprise), as well as to the working relationships supported by the enterprise (i.e., Acquirer/Supplier CM - contracted relationship to support external trusted interaction with suppliers).

This Standard is intended to serve as a guide in the coordination of system design to promote uniformity of the nomenclature and description of the operator devices.

This handbook is intended to assist the user to understand the ANSI/EIA-649B standard principles and functions for Configuration Management (CM) and how to plan and implement effective CM. It provides CM implementation guidance for all users (CM professionals and practitioners within the commercial and industry communities, DoD, military service commands, and government activities (e.g., National Aeronautics and Space Administration (NASA), North Atlantic Treaty Organization (NATO)) with a variety of techniques and examples. Information about interfacing with other management systems and processes are included to ensure the principles and functions are applied in each phase of the life cycle for all product categories.

The primary focus of this standard is information of interest to Configuration Management (CM) practitioners related to the performance of CM functions as products are conceived, proposed, defined, developed, produced, operated, maintained, modified, and disposed. This information is stored when generated and, from time to time, must be moved or shared with others. This standard, through the use of the Data Dictionary, defines real world things of interest to the CM practitioner, which are the foundation of the following CM functional areas, and are needed for effective data exchange and interoperability: Configuration Management Planning and Management Configuration Identification Configuration Change Management Configuration Audit Configuration Verification Configuration Status Accounting The Data Dictionary [21] defines terms that are used to define these objects of interest, which are listed below.

This standard for Numerical Machine Control Perforated Tape is intended to serve as a guide in the coordination of equipment design, to minimize the number of sizes and codes of perforated tape used, and to minimize the variety of perforated tape preparation equipment required by users of numerically controlled machines.

This document applies to hardware and software and provides CM requirements to be placed on contracts after being tailored by the Acquirer. The requirements have been organized by the following five CM functions: a Configuration Planning and Management b Configuration Identification c Configuration Change Management d Configuration Status Accounting e Configuration Verification and Audit

This Bulletin provides a comprehensive list of Terms and Definitions used in or related to TechAmerica prepared standards/documents. The information in these listings was extracted from standards and documents prepared by the Systems Engineering (G47), Configuration Management (G33), Life Cycle Logistics Supportability and Enterprise Information Management Interoperability Committees along with other pertinent international, industry and government standards. It is intended that this bulletin be used as a resource to help with harmonization of terms and definitions across standards. One should be cognizant of the release date of this Bulletin and understand that updates to the included standards and handbooks after this Bulletin was released may affect its accuracy.

The role of CM, within any one company's organization, on the development and production of a product has been established by internal company needs or imposed by customer dictum. (As used hereinafter, in order to reduce any confusion, computer programs, components, software, hardware, firmware, etc., are included in the designation "PRODUCT".) The primary focus of this Bulletin is directed toward the Buyer and Supplier personnel who will be managing hardware products in the production phase and software products in the full-scale development phase. The trend in DoD is toward expanded use of standardized components and subassemblies, using competitive reprocurement. The DoD needs to know the full span of CM requirements which should be included in the production contract and the management tasks that will have to be accomplished.