Refine Your Search

Topic

Search Results

Standard

Data Management

2012-04-01
CURRENT
GEIA859A
Data is information (e.g., concepts, thoughts, and opinions) that have been recorded in a form that is convenient to move or process. Data may represent tables of values of various types (numbers, characters, and so on). Data can also take more complex forms such as engineering drawings and other documents, software, pictures, maps, sound, and animation. For the purpose of this standard, Table 1 lists three broad types of data, indicates how each is used, and provides examples of each. Data management, from the perspective of this standard, consists of the disciplined processes and systems that plan for, acquire, and provide stewardship for product and product-related business data, consistent with requirements, throughout the product and data life cycles. Thus, this standard primarily addresses product data and the business data required for collaboration from the team level or extended through the trading partner level during product acquisition and sustainment.
Standard

Data Management

2014-09-23
WIP
GEIA859B
Data is information (e.g., concepts, thoughts, and opinions) that have been recorded in a form that is convenient to move or process. Data may represent tables of values of various types (numbers, characters, and so on). Data can also take more complex forms such as engineering drawings and other documents, software, pictures, maps, sound, and animation.

Data management, from the perspective of this standard, consists of the disciplined processes and systems that plan for, acquire, and provide stewardship for product and product-related business data, consistent with requirements, throughout the product and data life cycles. Thus, this standard primarily addresses product data and the business data required for collaboration from the team level or extended through the trading partner level during product acquisition and sustainment. It is recognized, however, that the principles described in this standard also have broader application to business data and operational data generally.

Standard

Implementation Guide for Common Data Schema for Complex Systems

2007-07-01
CURRENT
GEIAHB927
This section establishes modeling conventions and guidelines to be followed during the development of the GEIA-STD-927 top level schema. The following is within the scope of this document: Modeling rules, conventions and guidelines for the GEIA-STD-927 top level schema. The following are outside the scope of this document: An introduction to information modeling; An introduction to the EXPRESS modeling language.
Standard

Implementation Guide for Data Management

2006-01-01
CURRENT
GEIAHB859
As an integral part of the evolution to ANSI/GEIA-859 and the new environment, data management ensures that appropriate information support is available. Data requirements are established that ensure that data are properly timed and accessible, and provide the necessary visibility. The integrity of the data must be ensured regardless of their physical location. The DM process, implemented with rapidly maturing technologies, makes information available sooner and facilitates information sharing. It controls the digital format and the procedures necessary to exchange, index, store, and distribute or provide access to data.
Standard

Common Data Schema for Complex Systems

2013-05-01
CURRENT
GEIASTD927B
GEIA-STD-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.
Standard

Handbook: The Program Managers' Guide to the Integrated Baseline Review Process

2014-10-01
CURRENT
GEIAHB748_1
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.
Standard

Reducing the Risk of Tin Whisker-Induced Failures in Electronic Equipment

2014-10-01
CURRENT
GEIAGEB0002
This Bulletin provides a brief description of tin whisker formation and describes various methods recommended by government and industry to reduce the risk of tin whisker-induced failures in electronic hardware. It is not a mandate nor does it contain any requirements. A tin whisker is a single crystal that emerges from tin-finished surfaces. Tin whiskers can pose a serious reliability risk to electronic assemblies that have pure tin finish. The general risks fall into several categories: [1, 2, 3, 8, 16] Short Circuits: The whisker can create a short circuit, either by 1) growing from an area at one potential to an area at another or 2) breaking free and later bridging these areas. In some cases, these shorts may be permanent and cause catastrophic system failures. A transient short may result if the available current exceeds the fusing current of the whisker, and the whisker can fuse open.
Standard

IBIS Interconnect Modeling Specification

2015-07-01
CURRENT
GEIASTD0001
This document contains a specification for general purpose interconnect modeling in an IBIS (I/O Buffer Information Specification) compatible format. It was written to provide means for modeling all electrical interconnect types, including connectors, cables, packages, and printed circuit boards.
Standard

Standard Best Practices for System Safety Program Development and Execution

2008-10-01
CURRENT
GEIASTD0010
This document outlines a standard practice for conducting system safety. The system safety practice as defined herein provides a consistent means of evaluating identified risks. Mishap risk must be identified, evaluated, and mitigated to a level as low as reasonably practicable. The mishap risk must be accepted by the appropriate authority and comply with federal (and state, where applicable) laws and regulations, executive orders, treaties, and agreements. Program trade studies associated with mitigating mishap risk must consider total life cycle cost in any decision. This document is intended for use as one of the elements of project solicitation for complex systems requiring a systematic evaluation of safety hazards and mitigating measures. The Managing authority may identify, in the solicitation and system specification, specific system safety engineering requirements to be met by the Developer.
Standard

TechAmerica Technical Fellow and Associate Technical Fellow Nomination and Selection Handbook

2016-07-12
CURRENT
GEIAOP0003
This handbook details the TechAmerica Technical Fellowship Selection Process. It identifies the tasks to be performed and associates them with participants in the process. The focus is intended to keep the process implementation as uniform as possible. There are three types of information in this handbook: Process details Candidate Application Package format Process infrastructure and description Each Section of this handbook describes a significant segment of the selection process. There are also appendices that contain a variety of supporting material relevant to the different process participants.
Standard

Style Manual for Standards and Other Publications of TechAmerica

2015-07-01
CURRENT
GEIAOP0002
This style manual establishes requirements for the preparation of standards and certain other publications of TechAmerica). These requirements are intended to ensure that such documents are presented in as uniform a manner as practicable, irrespective of the technical content. Included are requirements for content; general style; and style for special elements such as equations, tables, and figures. They will help ensure that a standard is well organized and that it is consistent in style and presentation within itself and with other standards published by TechAmerica. Formulating committees and working groups should comply with the requirements set forth in this manual to make the product of the committee's work available for application in as short a time as possible. The TECHAMERICA Standards and Technology Department will use this manual to resolve nontechnical comments received as a result of public review of proposed standards.
Standard

Configuration Management Standard Implementation Guide

2016-03-01
CURRENT
GEIAHB649A
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.
Standard

Derating of Electronic Components

2011-08-01
CURRENT
GEIASTD0008
This Standard specifies the minimum derating requirements for using electronic components in moderately severe environments. These environments are assumed to include Airborne Inhabited Cargo (AIC), Airborne Inhabited Fighter (AIF), Ground Mobile (GM), and Naval Sheltered (NS) environments specified in MIL-HDBK-217. This Standard is intended to supersede the derating limits contained in Defense Standardization Program Office (DSPO) Standardization Directive SD-18, Naval Standard TE000-AB-GTP-010, and Air Force ESD-TR-85-148. It is intended that a future revision of this Standard will include additional requirements for derating for other environments (e.g. Airborne Uninhabited Cargo). Since this Standard specifies the minimum derating requirements, (sub)contractors may derate in excess of these requirements.
Standard

Reliability Program Standard for Systems Design, Development, and Manufacturing

2008-08-01
CURRENT
GEIASTD0009
This standard requires the developers and customer/user’s working as a team to plan and implement a reliability program that provides systems/products that satisfy the user’s requirements and expectations. The user’s requirements and needs are expressed in the form of the following four reliability objectives: The developer shall solicit, investigate, analyze, understand and agree to the user’s requirements and product needs. The developer, working with the customer and user, shall include the activities necessary to ensure that the user’s requirements and product needs are fully understood and defined, so that a comprehensive design specification and Reliability Program Plan can be generated. The developer shall use well-defined reliability- and systems-engineering processes to develop, design, and verify that the system/product meets the user’s documented reliability requirements and needs.
Standard

Requirements for Using Robotic Hot Solder Dip to Replace the Finish on Electronic Piece Parts

2016-02-24
CURRENT
GEIASTD0006A
This standard defines the requirements for fully replacing undesirable surface finishes using robotic hot solder dip. Requirements for qualifying and testing the refinished piece parts are also included. This standard covers the replacement of pure tin and Pb-free tin alloy finishes with SnPb finishes with the intent of subsequent assembly with SnPb solder. This dipping is different from dipping to within some distance of the body for the purposes of solderability; solder dipping for purposes other than full replacement of pure tin and other Pb-free tin alloy finishes are beyond the scope of this document. It covers process and testing requirements for robotic dipping process and does not cover semi-automatic or purely manual dipping processes. This standard does not apply to piece-part manufacturers who build piece parts with a hot solder dip finish.
Standard

Technical Guidelines for Aerospace and High Performance Electronic Systems Containing Lead-free Solder and Finishes

2007-11-01
CURRENT
GEIAHB0005_2
This document is intended for use as technical guidance by Aerospace system suppliers, e.g., Aerospace system Original Equipment Manufacturers (OEMs) and Aerospace system maintenance facilities, in developing and implementing designs and processes to assure the continued performance, quality, reliability, safety, airworthiness, configuration control, affordability, maintainability, and supportability of high performance aerospace systems (subsequently referred to as AHP) both during and after the transition to Pb-Free electronics. This document is intended for application to aerospace products; however, it may also be applied, at the discretion of the user, to other products with similar characteristics, e.g., low-volume, rugged use environments, high reliability, long lifetime, and reparability. If other industries wish to use this document, they may substitute the name of their industry for the word “Aerospace” in this document.
X