Refine Your Search

Search Results

Viewing 1 to 17 of 17
Standard

Earned Value Management Systems

2019-01-08
CURRENT
EIA748D
An Earned Value Management System (EVMS) for integrated program management will effectively integrate the work scope of a program with the schedule and cost elements for optimum program planning and control. The primary purpose of the system is to support integrated program management. The system is owned by the organization and is governed by the organization’s policies and procedures. The principles of an EVMS are: Plan all work scope for the program to completion. Break down the program work scope into finite pieces that are assigned to a responsible person or organization for control of technical, schedule and cost objectives. Integrate program work scope, schedule, and cost objectives into a performance measurement baseline plan against which accomplishments are measured. Control changes to the baseline. Use actual costs incurred and recorded in accomplishing the work performed. Objectively assess accomplishments at the work performance level.
Standard

SAE-1001 Application Guide

2018-10-23
WIP
SAE1001/1
The Application Guide will provide additional information on the application and use of SAE1001, including different development approaches, specialties and domains, as well as scalability to different project and system scope. (SAE-1001/1 - Information Report)
Standard

Integrated Project Processes for Engineering a System

2018-10-09
CURRENT
SAE1001
This standard is applicable to the engineering or the reengineering of: a Commercial or non-commercial systems, or portions thereof; b Any system, small or large, simple or complex, software-intensive or not, precedented or unprecedented; c Systems made up of hardware, software, firmware, personnel, facilities, data, materials, services, techniques, or processes (or combinations thereof); d A new system or a legacy system, or portions thereof. The requirements of this standard, or a designated subset, are intended to be applied by projects establishing policies and procedures for project implementation of the adopted process and process elements of this standard. The requirements of this standard may be tailored as follows: a Processes – Processes may be tailored to be applicable for a given type of project or system.
Standard

Technical Reviews

2018-09-26
WIP
SAE1011
The Technical Reviews standard will address a broadly applicable set of reviews for the development and maturation of systems, consistent with SAE1001 and other related technical standards
Standard

Integration Engineering for System Effectiveness

2016-06-16
CURRENT
EQB2
Program Managers have considered the subject of effectiveness quantification from three diverse points of view. The first viewpoint, in conjunction with the system effectiveness analyst, is to quantify everything and to consider everything quantifiable into a figure of merit. The result is a numerical decision aid that usually has some undesirable attributes such as oversimplification, non-sensitivity to critical parameters, hidden calculations, and difficulty in exercise of the model. This technique is characterized by mathematical models, computer programs, and attempted optimizations. The second viewpoint, in conjunction with the controller, is to consider the effectiveness as specified and concentrate on cost reduction, This has a danger of formulating all technical problems in terms of cost or economic considerations. This technique is characterized by closely controlled work packages.
Standard

Support System Analysis

2016-06-16
CURRENT
EQB3
The Electronic Industries Association (EIA) G-47 Effectiveness QuantificationCommittee has a basic task to quantify system effectiveness. Since the support parameters underly any prime parameter quantification, the topic of support system analysis is a fundamental one to this basic committee task. The charts contained in this bulletin were developed and used for presentations to aircraft support engineering groups, to comunicate the logic and scope of system analysis applied to support system optimization.
Standard

Quantification of Essentiality and Utilization Terms

2016-06-16
CURRENT
EQB4
This report on quantification of Essentiality (W) and Utilization (U) terms extends the scope of the basic expression for system effectiveness (Es = ADC) to include the additional "W" and "U" paramenters needed for the quantification of multi-functioned and multi-missioned systems. Methods and procedures for applying these terms to system effectiveness quantification are discussed and simple examples to demonstrate the principles of usage are included. The need to look at the system being quantified in terms of its level in the mission/function hierarchical tree is explained. The relationships between system elements (hardware, software, and personnel) and performance functions are discussed and illustrated with examples. Two methods for applying the "W"'and "U" weight factors, LOGIC AND (weak link model) and LOGIC OR (degraded operational modes model) are described and examples are shown for these cases.
Standard

Systems Engineering Capability Model Appraisal Method

2016-06-16
CURRENT
EIAIS731_2
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.
Standard

Systems Engineering Capability Model

2016-06-16
CURRENT
EIAIS731_1
The purposeo f this Interim Standard is to support the development and improvement of systems engineering capability. The scope of this standard includesa ll activities that associate with or enable systems engineering. 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 either Systems Engineering organizations or Systems Engineers do. Rather it is the interaction of many people, processes, and organizations resulting in the accomplishment of the required activities.
Standard

Systems Engineering

2016-06-16
CURRENT
EIAIS632
This standard defines a total system approach for the development of systems. The standard requires: establishing and implementing a structured, disciplined. and documented systems engineering effort incorporating the systems engineering process; multidisciplinary teamwork; and the simultaneous development of the products and processes needed to satisfy user needs. The systems engineering process is defined generically to facilitate broad application. This standard defines the requirements for technical reviews. The tasks in this standard provide a methodology for evaluating progress in achieving system objectives. This standard provides a comprehensive, structured, and disciplined approach for all life-cycle phases, including new system product and process developments, upgrades, modifications, and engineering efforts conducted to resolve problems in fielded systems.
Standard

Unit Production Cost Tracking Model UPCT 6

2016-05-31
CURRENT
EDIB1B
This userguide contains a description of the Unit Production Cost Tracking Model for use in design tradeoffs and control and reporting tasks of a Design-to-Cost program. This model is designed to compare two Cost Breakdown Structures (CBS) to show elemental and summary cost differences. The two Cost Breakdown Structures may represent design alternatives, or a target allocation and the current design approach for comparison.
Standard

System Engineering

2015-07-01
CURRENT
SYSB1
The purpose of this EIA Bulletin is to provide a clearer, more definitive description of system engineering in order to promote greater recognition, more effective application, and the further development of this technical discipline that can be shared among systems contractors, subcontractors, engineering institutions, process tool developers and DoD.
Standard

Processes for Engineering a System

1999-01-01
CURRENT
EIA632
The purpose of this Standard is to provide an integrated set of fundamental processes to aid a developer in the engineering or reengineering of a system. Use of this Standard is intended to help developers a) establish and evolve a complete and consistent set of requirements that will enable delivery of feasible and cost-effective system solutions; b) satisfy requirements within cost, schedule, and risk constraints; c) provide a system, or any portion of a system, that satisfies stakeholders over the life of the products that make up the system.
X