Introduction

File lastly updated: April, the 11th, 2007

The following standards are dedicated to electronics industry and/or to the systems engineering area.
Keywords: Standard,electronics, System engineering, standard, handbook

Summary list of Standards

ANSI/GEIA EIA-632 Processes for Engineering a System Doc Date: 01-Sep-2003

ANSI⁄GEIA EIA-649-A National Consensus Standard for Configuration
Management Doc Date: 01-Apr-2004

GEIA EIA-731-1 Formerly EIA⁄IS 731.1 Systems Engineering Capability Model
Doc Date: 01-Aug-2002

GEIA EIA-731-2 Systems Engineering Capability Model Appraisal Method Doc
Date: 01-Aug-2002

ANSI⁄GEIA EIA-748-A (R2002) Earned Value Management Systems Doc Date:
01-Jun-1998

GEIA HB-748-1 GEIA Engineering Bulletin: Handbook - The Program Managers'
Guide to the Integrated Baseline Review Process Doc Date: 01-May-2004

ANSI⁄GEIA EIA-836-2002 Configuration Management - Data Exchange and
Interoperability Doc Date: 01-Jun-2002

ANSI/GEIA EIA-927 draft Doc Date: 200X

Detailed list of Standards


Document Number: ANSI⁄GEIA EIA-632

Title: Processes for Engineering a System
Doc Date: 01-Sep-2003
Description:
The purpose of this Standard is to provide an integrated set of fundamental processes to aid a developer in the engineering or re-engineering of a system.

Use of this Standard is intended to help developers:

• Establish and evolve a complete and consistent set of requirements that will enable delivery of feasible and cost-effective system solutions;
• Satisfy requirements within cost, schedule, and risk constraints;
• Provide a system, or any portion of a system, that satisfies stakeholders over the life of the products that make up the system;
• Provide for the safe and⁄or cost-effective disposal or retirement of a system.
  

Document Number: ANSI⁄GEIA EIA-649-A
Title: National Consensus Standard for Configuration Management
Doc Date: 01-Apr-2004

Description:
Configuration Management, a discipline popularized by its use in the acquisition of defense systems, is widely used for commercial products and services. When Configuration Management principles are applied using effective practices, return on investment is maximized and product life cycle costs are reduced. This standard is intended to be used when establishing, performing, or evaluating Configuration Management processes in any industry, business enterprise or government organization.
This standard describes Configuration Management functions and principles and defines a neutral Configuration Management terminology for use with any product line. Configuration Management (CM) applies appropriate processes and tools to establish and maintain consistency between the product and the product requirements and attributes defined in product configuration information. A disciplined CM process ensures that products conform to their requirements and are identified and documented in sufficient detail to support the product life cycle. CM assures accurate product configuration information and enables product interchangeability and safe product operation and maintenance to be achieved. Although product configuration information does not include project
or administrative types of information (e.g., schedules, plans, and cost information), these types of information may also be placed under Configuration Control.
The small investment in resources necessary for effective Configuration Management is returned many fold in cost avoidance. CM implementation requires a balanced and consistent implementation of CM functions, principles, and practices throughout the product life cycle. CM facilitates orderly identification of product attributes and provides control of product information and product changes used to improve capabilities; correct deficiencies; improve performance, reliability, or maintainability; extend product life; or reduce cost, risk or liability.

 

Document Number: GEIA EIA-731-1 Formerly EIA⁄IS 731.1
Title: Systems Engineering Capability Model
Doc Date: 01-Aug-2002

Description:
The purpose of the Standard is to support the development and improvement of systems engineering capability.
Systems engineering is an inter-disciplinary approach and means to enable the realization of successful systems. In this context, systems engineering is not limited to what eigher Systems Engineering organization or Systems Engineers do.
Rather it is the interaction of many people, processes, and organizations resulting in the accomplishment of the required activities.

This Standard is intended to provide complete coverage of EIA-632, Processes Engineering a System, and be consistent with both it and IEEE 1220-1994, IEEE Trial-Use Standard for Application and Management of the Systems Engineering Process.

Document Number: GEIA EIA-731-2
Title: Systems Engineering Capability Model Appraisal Method
Doc Date: 01-Aug-2002
Description:
This document describes the Appraisal Method (AM) for the Systems Engineering Capability Model (SECM). An appraisal compares an organization's Systems Engineering capabilities against the Specific Practices of the Focus Areas and the Generic Characteristics defined in EIA-731, part 1.


Document Number: ANSI⁄GEIA EIA-748-A (R2002)
Title: Earned Value Management Systems
Doc Date: 01-Jun-1998

Description:
The Earned Value Management System incorporate best business practices to provide strong benefits for program or enterprise planning and control. The processes include integration of program scope, schedule, and cost objectives, establishment of a baseline plan for accomplishment of program objectives, and use of earned value techniques for performance measurement during the execution of a program. The system provides a sound basis for problem identification, corrective actions, and management replanning as may be required.

 

Document Number: GEIA HB-748-1
Title: GEIA Engineering Bulletin: Handbook - The Program Managers' Guide to the Integrated Baseline Review Process
Doc Date: 01-May-2004

Description:

The Program Managers' Guide to the Integrated Baseline Review (IBR) Process was developed to improve the consistency of the overall IBR Process. This guide identifies the purpose of the IBR Process and conveys the need to make it a continuous process. This guide also integrates the IBR with risk management, within the framework of the IBR Process. This handbook clearly defines the purpose, goals, and objectives of an Integrate Baseline Review. 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 Program Managers. The IBR Process enables managers to effectively utilize the project Performance Measurement Baseline (PMB) to assess performance, and to better understand inherent risks.

Document Number: ANSI⁄GEIA EIA-836-2002
Title: Configuration Management - Data Exchange and Interoperability
Doc Date: 01-Jun-2002

Description:
EIA-836 facilitates the interoperability and exchange of CM data by clearly delineating CM data elements and their relationships, and by providing the information content of CM data exchanges. The level of interoperability between dissimilar systems is determined by trading partner agreement. The extensible markup language (XML) facilitates data sharing and exchange among different systems. EIA-836 provides a set of standard definitions and business objects that can be used by XML frameworks in interfacing the content elements among one or more systems or databases.
EIA-836 is designed to have wide applicability across vertical industries. The process employed to provide access, sharing or exchange, is typically accomplished using one of many available product data management tools or systems, often customized to a specific organizational environment. To be most effective, the capabilities of the process, tools or systems, should embody the CM principles in ANSI⁄EIA-649 "National Consensus Standard for Configuration Management;" in conjunction with the business objects and data element definitions in EIA-836.

 

Document Number: ANSI⁄GEIA EIA-927 draft
Doc Date: 200X

Description:
GEIA-927 specifies the data concepts to be exchanged to share product information pertaining to a complex system from the viewpoints of multiple disciplines. It supports the exchange of data across the entire life cycle for the product from the concept stage through disposal. It embraces several aspects:
technical aspects which lead to the definition of functional and physical architectures (what the system is doing, how it is doing it and how well);

• technical management (work schedule, document generation, concurrent engineering, validation, and verification procedures);
• project aspects which include project management issues (traceability management, configuration management, and trade-off analysis);
• industrial management (management of co-operation between partners).

The following discipline views are within the scope of GEIA-927:

• definition of other systems the system interacts with;
• context for the system in each life cycle phase;
• support of hierarchical break down modeling techniques;
• functional and non-functional requirements of the system in each life cycle phase;
• definition of the static and dynamic behavior of the system.
  

The following life cycle stages are within the scope of GEIA-927:

• systems engineering;
• feasibility assessment;
• domain engineering;
• system realization;
• system operation;
• system support;
• system maintenance;
• decommissioning of the system.