This standard establishes the performance requirements for the control of the electromagnetic emissio and susceptibility characteristics of electronic, electrical, and eletromechanical equipment and subsystems designed or procured for use in severe electromagnetic environments such as ships, aircraft, spacecraft, armored vehicles, tc. Such equipment and subsystems may be used independently or as an integral part of other subsystems or systems.
This standard establishes general techniques for use in the measurement and determination of the electromagnetic emission and susceptibility characteristics of electronic, electrical, and electromechanical equipment and subsystems.
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 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.
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 guide clearly defines the purpose, goals, and objectives of an IBR. It also describes the attributes of an effective IBR and discusses a baseline review process that will lead to a better understanding of program risks. It provides a common definition and framework for the IBR Process. This process harmonizes, and to the extent possible, unifies the management objectives for all PMs. The IBR Process enables managers to effectively utilize the project Performance Measurement Baseline (PMB) to assess performance, and to better understand inherent risks. The IBR Process should continue throughout the life of a project.
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 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 Standard applies to all products produced by NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers. This Standard may also apply to the Jet Propulsion Laboratory and suppliers/service providers to the extent specified in their agreements with NASA. This Standard may be cited in the CM requirements of NASA Headquarters, NASA Centers, Programs, Projects, and Supplier agreements.
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 document is used for placing Configuration Management Requirements on Defense Contracts after being tailored by the Acquirer. When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule. The planning and execution of Configuration Management (CM) is an essential part of the product development and life cycle management process. It provides control of all configuration documentation, physical parts and software representing or comprising the product. Configuration Management's overarching goal is to establish and maintain consistency of a product's functional and physical attributes with its requirements, design and operational information throughout its life cycle. When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule.