Criteria

Text:
Content:
Display:

Results

Viewing 1 to 30 of 91
CURRENT
2017-11-21
Standard
AS6294/1
This document establishes common industry practices and recommended screening, qualification, and lot acceptance testing of Plastic Encapsulated Microcircuits (PEMs) for use in space application environments.
2017-11-15
WIP Standard
J1698/1
This Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. The document is intended to govern data element definitions, to provide a minimum data element set,and to specify EDR record format as applicable for light-duty motor vehicle Original Equipment applications.
2017-11-13
WIP Standard
AS6522A
The UCS technical governance comprises a set of policies, processes, and standard definitions to establish consistency and quality in the development of architecture artifacts and documents. It provides guidance for the use of adopted industry standards and modeling conventions in the use of Unified Modeling Language (UML) and Service Oriented Architecture Modeling Language (SoaML), including where the UCS Architecture deviates from normal UML conventions. This document identifies the defining policies, guidelines, and standards of technical governance in the following subjects: - Industry standards adopted by the AS-4UCS Technical Committee: These are the industry standards and specifications adopted by AS-4UCS in the generation and documentation of the architecture. - UCS Architecture Development: UCS specific policies on the development of the UCS Architecture. The AS-4UCS Technical Committee governance policies are intentionally minimal.
2017-10-31
WIP Standard
SAE1002
Latitude and Longitude is not a reference system commonly used by land-based First Responders. Street names and associated addresses are, but following disasters such as floods, fires, etc., they are often obscured or destroyed. The USNG is a point and area location grid reference system that provides a reliable and available geoaddressing capability that is an easy to use alternative to latitude and longitude.
2017-10-30
WIP Standard
J3016
This Recommended Practice provides a taxonomy for motor vehicle driving automation systems that perform part or all of the dynamic driving task (DDT) on a sustained basis and that range in level from no driving automation (level 0) to full driving automation (level 5). It provides detailed definitions for these six levels of driving automation in the context of motor vehicles (hereafter also referred to as “vehicle” or “vehicles”) and their operation on roadways. These level definitions, along with additional supporting terms and definitions provided herein, can be used to describe the full range of driving automation features equipped on motor vehicles in a functionally consistent and coherent manner.
2017-09-21
WIP Standard
SAE9990/1
This eLoran transmitted signal standard provides technical descriptions of a data channel based on the tri-state pulse position modulation technique.
2017-09-21
WIP Standard
SAE9990/2
This eLoran transmitted signal standard provides technical descriptions of the data channel using 9th pulse modulation technique.
2017-08-08
WIP Standard
GEIASTD0005_1B

This standard defines the objectives of, and requirements for, documenting processes that assure customers and regulatory agencies that ADHP electronic systems containing Pb-free solder, piece parts, and PBs will satisfy the applicable requirements for performance, reliability, airworthiness, safety, and certifiability throughout the specified life of performance.

It is intended to communicate requirements for a Pb-free Control Plan (LFCP), hereinafter referred to as the Plan, and to assist the Plan Owners in the development of their own Plans. The Plan documents the Plan Owner’s processes that assure their customers, and all other stakeholders that the Plan Owner's products will continue to meet their requirements, given the risks stated in the Introduction.

2017-07-06
WIP Standard
SAE1001
The purpose of the "Integrated Project Processes for Engineering a System(IPPES)" Standard is to provide an integrated set of fundamental technical processes to aid a project in the engineering or reengineering of a system over the full life cycle. Covers systems that can be any combination of people (humans); product (hardware or software); or process (service). Applicable to any type of system: commercial or non-commercial; small or large, simple or complex, precedented or unprecedented; new or legacy or any combination of these characteristics.
CURRENT
2017-06-09
Standard
J3098_201706
This SAE Recommended Practice applies to a decorative lamp(s) installed on the front of motor vehicles. This lamp(s) is intended only to be decorative and is not to impair the effectiveness of any required lighting device. This recommended practice establishes uniformity in use guidelines for the performance, installation, activation and switching of a front decorative lamp(s).
2017-06-07
WIP Standard
GEIASTD0005_2B
This Standard establishes processes for documenting the mitigating steps taken to reduce the harmful effects of Pb-free tin finishes in electronic systems. This Standard is applicable to Aerospace, Defense, and High Performance (ADHP) electronic applications which procure equipment that may contain Pb-free tin finishes.
2017-04-14
WIP Standard
STD0016A
This document defines the requirements for developing a DMSMS Management Plan, hereinafter also called the Plan, to assure customers that the Plan owner is using a proactive DMSMS process for minimizing the cost and impact that part and material obsolescence will have on equipment delivered by the Plan owner. The technical requirements detailed in clause 5 ensure that the Plan owner can meet the requirement of having a process to address obsolescence as required by Industry Standards such as EIA-4899 "Standard for Preparing an Electronic Components Management Plan" and DoD Programs as required by MIL-STD-3018 "Parts Management". Owners of DMSMS Management Plans include System Integrators, Original Equipment Manufacturers (OEM), and logistics support providers.
CURRENT
2017-02-24
Standard
J1698/1_201702
This Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. The document is intended to govern data element definitions, to provide a minimum data element set, and to specify EDR record format as applicable for light-duty motor vehicle Original Equipment applications.
2017-01-03
WIP Standard
AS6294/2
This standard documents and establishes common industry practices, and screening and qualification testing, of Plastic Encapsulated Microcircuits (PEMs) for use in military and avionics application environments.
CURRENT
2016-12-20
Standard
AIR6519
The Use Case Trace (UCTRACE) is SAE publication AIR6519 of the Department of Defense Unmanned Control Segment (UCS) Architecture. This document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: Use Case Trace (UCTRACE) Version 3.4(PR) approved for Distribution A public release 15.S-1859. This information is produced from a script run against the System Use Case Model contained in the UCS Architecture Model AS6518-MODEL.eap configuration item. The System Use Case Model includes, at its lowest level of elaboration, use cases Level 2/3 (L2/L3) that describe specific scenarios of message exchanges between Actors and internal system Participants via ServiceInterfaces. These message exchanges provide a way to create detailed traces that answer the question: “What UCS service interfaces must my components implement to satisfy functional requirements represented by a given Level 2/3 UCS use case?”
CURRENT
2016-12-20
Standard
AS6522
The UCS technical governance comprises a set of policies, processes, and standard definitions to establish consistency and quality in the development of architecture artifacts and documents. It provides guidance for the use of adopted industry standards and modeling conventions in the use of Unified Modeling Language (UML) and Service Oriented Architecture Modeling Language (SoaML), including where the UCS Architecture deviates from normal UML conventions. This document identifies the defining policies, guidelines, and standards of technical governance in the following subjects: Industry standards adopted by the AS-4UCS Technical Committee: These are the industry standards and specifications adopted by AS-4UCS in the generation and documentation of the architecture. UCS Architecture Development: UCS specific policies on the development of the UCS Architecture. The AS-4UCS Technical Committee governance policies are intentionally minimal.
CURRENT
2016-11-15
Standard
J2594_201611
While there are various types of Fuel Cell architectures being developed, the focus of this document is on Proton Exchange Membrane (PEM) fuel cell stacks and ancillary components for automotive propulsion applications. Within the boundaries of this document are the: Fuel Supply and Storage, Fuel Processor, Fuel Cell Stack, and Balance of Plant, as shown in Figure 1.
CURRENT
2016-07-12
Standard
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.
CURRENT
2016-06-16
Standard
EIAEDIF1
The increase in the number of silicon foundries and CAD/CAE system and workstation companies, and the problem of movement of data among in-house design systems has made a standard interchange format for electronic design data essential. The benefits of the general adoption of a standard interchange format are important and far reaching. The customer receives a much wider variety of feasible choices, and free competition in both CAEYCAD system/tool businesses and foundry businesses is enhanced. The electronic circuit designer and customer of CAE/CAD system and foundry service can expect compatibility among these products. The designer can choose equipment and services best suited for a particular task with a minimum of overhead. Foundries can work with customers regardless of the CAE/CAD equipment that the customer is using.
CURRENT
2016-06-16
Standard
EIAEP2F
The Electronic Industries Association is the national trade organization representing electronic industry interests in the United States. Its primary mission is to enhance the competitiveness of the American producer. EIA supports and advances national defense, economic growth, technological progress, and all interests of the electronic industries compatible with the public welfare. We represent the full spectrum of manufacturers in the electronic industries, from manufacturers of the smallest electronic part to corporations that design and produce the most complex systems used in defense, space and industry.
CURRENT
2016-06-16
Standard
EIAEP12A
Scope is unavailable.
CURRENT
2016-05-26
Standard
J2208_201605
To provide a Recommended Practice for validating the function and integrity of an automatic transmission park mechanism with its associated control system and environment.
2016-03-03
WIP Standard
EIA649C
When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule. This standard is intended to assist in establishing, performing, or evaluating CM systems. CM is an integrated system of processes that ensure consistency of a product's performance, functional and physical attributes with its requirements, design, and operational information. The essence of CM, as portrayed in this consensus standard, is the common application of CM functions and their underlying fundamental principles, which have universal applicability across the broad spectrum of commercial and government enterprises. The standard provides an understanding of what to do, why a customer/suppler should do it, and when it is necessary to tailor the application of CM functions. This standard fulfills the important function of providing a rational basis upon which to apply good judgment in both planning for and executing CM across the enterprise.
2016-03-03
WIP Standard
EIA649_1A
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.
2016-02-04
WIP Standard
J3131
SAE J3131 defines an automated driving reference architecture that contains functional modules supporting future application interfaces for Levels 3 through 5 (J3016). The architecture will model scenario-driven functional and nonfunctional requirements, automated driving applications, functional decomposition of an automated driving system, and relevant functional domains (i.e., functional groupings). Domains include, but are not limited to, automated driving (i.e., automation replacing the human driver), by-wire and active safety, and those related to automated recovery from faults and system failures (e.g., system bringing the vehicle to a safe state). The architecture will address Tier 1 and Tier 2 functional groupings. The document will include one example instantiation being divides the functionality into two functionality groupings, and will detail the functional and information interface between the groups.
2015-10-21
WIP Standard
GEIASTD0007C
This standard defines logistics product data generated during the requirements definition and design of an industry or government system, end item or product. It makes use of the Extensible Markup Language (XML) through the use of entities and attributes that comprise logistics product data and their definitions. The standard is designed to provide users with a standard set of data tags for all or portions of logistics product data and customer defined sub-sets of logistics product data. The standard can be applied to any indsutry or government product, system or equipment acquisition program, major modification program, and applicable research and development projects. This standard is for use by both industry and government activities. As used in this standard, the requiring authority is generally the customer and the customer can be a government or industry activity. The performing activity may be either a industry or government activity.
2015-10-21
WIP Standard
GEIAHB0007C
This handbook is intended to provide additional information on the use and tailoring of the data in GEIA-STD-0007. The standard provides a new approach to Logistics Support Analysis Record (LSAR) (i.e., MIL-STD-1388-2B) data with emphasis on data transfer (e.g., XML Schemas) versus data storage (e.g., relational tables). GEIA-STD-0007 identifies the range of logistics product data that is generated during the development and acquisition of a system or end item. It does not prescribe the supportability analyses required to generate logistics product data. How the data is generated via analysis techniques/tools, how it is stored and processed, and how the data is used to generate specific logistics support products, is left to the performing activity. GEIA-STD-0007 is a data transfer standard implementing the logistics data concepts of GEIA-STD-927, Common Data Schema for Complex Systems.
2015-10-13
WIP Standard
GEIASTD0008A
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.
2015-09-29
WIP Standard
ARP6348
This document provides additional guidance on performing lifetime assessments and mitigations for ARP6338. It is intended for use by designers, reliability engineers, and others associated with the design, production, and support of electronic sub-assemblies, assemblies, and equipment used in ADHP applications.
Viewing 1 to 30 of 91

Filter

  • Standard
    91