Search Results

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 standard establishes the performance requirements for the control of the electromagnetic emission and susceptibility characteristics of electronic, electrical, and electromechanical equipment and subsystems designed or procured for use in severe electromagnetic environments such as ships, aircraft, spacecraft, armored vehicles, etc. Such equipment and subsystems may be used independently or as an integral part of other subsystems or systems.

The Manufacturing Message Specification is an application layer Standard designed to support messaging communications to and from programmable devices in a Computer Integrated Manufacturing (CIM) environment. This environment is referred to in this Standard as the manufacturing environment. This Standard does not specify a complete set of services for remote programming of devices, although provision of such a set of services may be the subject of future standardization efforts.

This standard applies to the interconnection of data terminal equipment and numerical control equipment at the tape reader interface. The data terminal would typically be connected to a remote data source/sink such as a computer. This standard defines: This standard is applicable for the interchange of signals when used in conjunction with electronic equipment, each interchange circuit of which has a single return (signal ground) that can be interconnected at the interface point. Figure 1.1, typical installation, shows how this standard should be applied to a typical tape reader interface of numerical control equipment.

This handbook provides guidance about the use of CM and about CM's interface with other management systems and procedures. The paragraph numbers in this handbook map directly to the paragraph numbers in ANSI/EIA-649. It is applicable to the support of projects throughout all phases of a product's life cycle. Generic CM examples are included which may be tailored, taking into account the complexity and nature of the work and the product. It is applicable to the support of projects throughout all phases of a products life cycle. Generic CM examples are included and may be tailored to suit the complexity and nature of the work and the product. This handbook establishes a common framework for generic product life cycle CM. It addresses tailored implementation based on differences that may exist in organization policies and procedures, in the phase of the product life cycle, in the acquisition method, in the project size and complexity, and in the system requirements and development.

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.

This standard covers both active and passive aspects of the electrical interface between the Numerical Control (NC) and the machine power and logic control, motor drive equipment, and other electrical apparatus on or associated with the machine tool. It covers:

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).

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.

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 is intended for use as a guide and defines the terms and definitions to be used during the development, documentation, verification, and delivery cycles of new and modified computer software. It lists and defines the most common terms currently used in the world of computer software configuration management. There has been no attempt to compete with some of the more formal documents in use within the software programming community.

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 Interface Control Plan establishes a program for interface control among the major segments/equipments of a DoD program. This could be an airborne weapon system, Medium Launch Vehicle System, Space Launch Complex System, etc. The program is based on formal agreements between participating organizations, and includes (1) documentation to establish, define and control interface requirements and to detail interface design definition between system segments, (2) interface management under the purview of the Interface Management Boards (IMB) and (3) interface control, through Interface Control Working Groups (ICWGs). The plan establishes the IMB and ICWG policy and procedures. Furthermore, it sets forth the Government Agencies Program Offices, associate contractors and participating Government Agency responsibilities in support of the Interface Control Program and the conduct of interface management/control through the IMBs, and ICWGs.

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.