Criteria

Text:
Content:
Display:

Results

Viewing 1 to 30 of 84
2017-10-25
WIP Standard
ARP1340B
This document specifies those requirements and procedures for periodic tests to insure maintenance of balance machine capabilities for balancing jet engine components.
2017-10-12
WIP Standard
J2931/7
This SAE Information Report J2931/7 establishes the security requirements for digital communication between Plug-In Electric Vehicles (PEV), the Electric Vehicle Supply Equipment (EVSE) and the utility, ESI, Advanced Metering Infrastructure (AMI) and/or Home Area Network (HAN).
CURRENT
2017-10-02
Standard
J2931/7_201710
This SAE Information Report J2931/7 establishes the security requirements for digital communication between Plug-In Electric Vehicles (PEV), the Electric Vehicle Supply Equipment (EVSE) and the utility, ESI, Advanced Metering Infrastructure (AMI) and/or Home Area Network (HAN).
CURRENT
2017-08-09
Standard
ARIS834-7
This document defines an Aircraft Data Interface Function (ADIF) developed for aircraft installations that incorporate network components that are based on commercially available technologies. This document defines a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. The goal is to provide a common set of services that may be used to access specific avionics parameters. The ADIF may be implemented as a generic network service, or it may be implemented as a dedicated service within an ARINC 759 Aircraft Interface Devices (AID) such as those used with an Electronic Flight Bag (EFB).
CURRENT
2017-05-09
Standard
EIASTD4899C
This document applies to the development of Plans for integrating and managing electronic components in equipment for the military and commercial aerospace markets; as well as other ADHP markets that wish to use this document. Examples of electronic components, as described in this document, include resistors, capacitors, diodes, integrated circuits, hybrids, application specific integrated circuits, wound components, and relays. It is critical for the Plan owner to review and understand the design, materials, configuration control, and qualification methods of all “as-received” electronic components, and their capabilities with respect to the application; identify risks, and where necessary, take additional action to mitigate the risks. The technical requirements are in Clause 3 of this standard, and the administrative requirements are in Clause 4.
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-21
Standard
AS4074B
This standard specifies the characteristics of the SAE Linear Token Passing Bus (LTPB) Interface Unit. The LTPB provides a high reliability, high bandwidth, low latency serial interconnection network suitable for utilization in real time military and commercial applications. Multiple redundant data paths can be implemented to enhance reliability and survivability in those applications which require these attributes. The token passing and data exchange protocols are optimized to provide low latency and fast failure detection and correction. Physical configurations with bus lengths up to 1000 m can be accommodated. This specification defines the following: General Description (3.1): An overview of the LTPB protocol. Physical Media Interface (3.2): This portion of the standard defines the physical interface to both optical and electrical bus media.
2017-02-16
WIP Standard
J3138
On-Board Diagnostic (OBD) regulations require passenger cars, and light and medium duty trucks, to provide a Data Link Connector to support communication of diagnostic information to off-board devices. Legislated diagnostic information is also required to be communicated in a timely fashion to the off-board devices. Many vehicle manufacturers also provide access to enhanced diagnostic information and vehicle systems/subsystems via this connector. Generally, there are two forms of communication methodologies used in current vehicles: a. Open access to communication busses b. Communication busses isolated via a gateway This document provides guidelines for securing communications with any off-board device for vehicles utilizing either methodology.
CURRENT
2017-01-12
Standard
AS5609A
This SAE Aerospace Standard (AS) defines the editorial format and policies necessary for the publication of Interface Control documents. The Common Interface Control Document Format Standard defines a common format for aircraft/store interface documents to foster increased interoperability. It is designed with the versatility to serve differing “ICD” philosophies and organizations. This aerospace standard defines the common technical data sections for the Common Interface Control Document Format down to the third header level for the majority of sub-sections. The Common Interface Control Document Format Aerospace Standard provides a structured document format in appendixes supported by example paragraphs, drawings, etc.
CURRENT
2016-10-21
Standard
AIR5683A
MIL-STD-1553 establishes requirements for digital command/response time division multiplexing (TDM) techniques on military vehicles, especially aircraft. The existing MIL-STD-1553 network operates at a bit rate of 1 Mbps and is limited by the protocol to a maximum data payload capacity of approximately 700 kilobits per second. The limited capacity of MIL-STD-1553 buses coupled with emerging data rich applications for avionics platforms plus the expense involved with changing or adding wires to thousands of aircraft in the fleet has driven the need for expanding the data carrying capacity of the existing MIL-STD-1553 infrastructure.
CURRENT
2016-10-21
Standard
AIR4271A
This Aerospace Information Report (AIR) has been prepared by the Systems Applications and Requirements Subcommittee of SAE Committee AS-2. It is intended to provide guidance primarily, but not exclusively, for specifiers and designers of data communication systems for real time military avionics applications within a platform. The subject of high speed data transmission is addressed from two standpoints: (1) the influence of developments in technology on avionics architectures as a whole and (2) the way in which specific problems, such as video, voice, closed loop control, and security may be handled. While the material has been prepared against a background of experience within SAE AS-2 relating to the development of a family of high speed interconnect standards, reference to specific standards and interconnect systems is minimized.
CURRENT
2016-10-21
Standard
AS15532A
The emphasis in this standard is the development of data word and message formats for AS15531 or MIL-STD-1553 data bus applications. This standard is intended as a guide for the designer to identify standard data words and messages for use in avionics systems and subsystems. These standard words and messages, as well as the documentation format for interface control document (ICD) sheets, provide the basis for defining 15531/1553 systems. Also provided in this standard is the method for developing additional data word formats and messages that may be required by a particular system but are not covered by the formats provided herein. It is essential that any new word formats or message formats that are developed for a 15531/1553 application follow the fundamental guidelines established in this standard in order to ease future standardization of these words and messages. The standard word formats presented represent a composite result of studies conducted by the U.S.
CURRENT
2016-10-21
Standard
AS4074/3B
This slash sheet specifies the operational parameters and characteristics of a particular implementation of the SAE Linear, Token Passing Bus (LTPB) Interface Unit. This slash sheet defines the following: The physical media interface: This slash sheet specifies the characteristics of the electrical interface to the physical bus media. The minimum and maximum timing requirements for operation of this implementation of the LTPB. The data coding used to encode and decode the data for transmission. The default values to be loaded into the timers of the LTPB interface at power-up prior to intervention by the host processor.
2016-10-13
WIP Standard
J3005-2
SAE J3005-2 describes OBD interface security guidelines for J1979 communications and best practices for telematic devices connected with the SAE J1962 OBD vehicle connector.
2016-08-26
WIP Standard
J3061-2
This document serves as the initial framework for defining the subject. The document serves as a detailed breakdown of security testing methods related to software and hardware testing. it is to remain vendor agnostic and focus on the type of testing available at the time of release. This is not a comprehensive list and is intended to be updated on a yet to be defined timeline.
2016-08-26
WIP Standard
J3061-3
This document serves as an internal list of manufacturers of security related tools and their capabilities. This list is not intended as an endorsement of any manufacturer but rather a list of examples and capabilities that exist within the market.
2016-07-06
WIP Standard
J1674
The purpose of this SAE Standard is to offer simplified and prioritized guidelines for collecting and preserving on-scene data related to motor vehicle accidents. It is intended that these guidelines improve the effectiveness of data collection, which will assist subsequent analysis and reconstruction of a particular incident. The document is to guide early data collectors whose objectives include documenting information related to the incident. it may be used by law enforcement personnel, safety officials, insurance adjusters and other interested parties. The document identifies categories of scene physical features that deteriorate relatively quickly and recomends documentation task priorities. Detailed methods of collecting data are not part of this document. However, some widely used methods are described in the references in Seciton 2.
2016-06-15
WIP Standard
J3061-1
Review existing classification schemes from other industries and existing ideas that were presented at SAE or that may be being proposed or used in other organizations. Determine to use either an existing scheme or create a new classification scheme specific for the automotive industry from the existing or proposed methods or ideas (an integration or merging of the ideas). A Threat Analysis and Risk Assessment Method that would work with the classification scheme or from which we could map into a specific level in the cybersecurity integrity classification scheme a. This will require reviewing existing TARA methods and deciding on one or a tailored version of one Determine how to relate the ACSIL for safety-related threats to the ASIL from ISO 26262
2016-04-14
WIP Standard
AIR5925B
The report shows how the methodology of measurement uncertainty can usefully be applied to test programs in order to optimize resources and save money. In doing so, it stresses the importance of integrating the generation of the Defined Measurement Process into more conventional project management techniques to create a Test Plan that allows accurate estimation of resources and trouble-free execution of the actual test. Finally, the report describes the need for post-test review and the importance of recycling lessons learned for the next project.
CURRENT
2016-03-30
Standard
J2735SET_201603
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.
CURRENT
2016-03-30
Standard
J2735ASN_201603
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.
CURRENT
2016-03-16
Standard
AS6296
This SAE Aerospace Standard (AS) specifies minimum performance standards for Electronic Flight Information System (EFIS) displays that are head-down and intended for use in the flight deck by the flight crew in all 14 CFR Part 23, 25, 27, and 29 aircraft. This document is expected to be used by multiple regulatory agencies as the basic requirement for a technical standard order for EFIS displays. The requirements and recommendations in this document are intended to apply to, but are not limited to, the following types of display functions: Primary Flight and Primary Navigation displays, including vertical situation and horizontal situation functions. Displays that provide flight crew alerts, which may include engine instrument, aircraft systems information/control. Control displays including communication, navigation and system control displays.
2016-02-19
WIP Standard
J3061
This recommended practice provides guidance on vehicle Cybersecurity and was created based off of, and expanded on from, existing practices which are being implemented or reported in industry, government and conference papers. The best practices are intended to be flexible, pragmatic, and adaptable in their further application to the vehicle industry as well as to other cyber-physical vehicle systems (e.g., commercial and military vehicles, trucks, busses). Other proprietary Cybersecurity development processes and standards may have been established to support a specific manufacturer’s development processes, and may not be comprehensively represented in this document, however, information contained in this document may help refine existing in-house processes, methods, etc. This recommended practice establishes a set of high-level guiding principles for Cybersecurity as it relates to cyber-physical vehicle systems.
CURRENT
2016-01-14
Standard
J3061_201601
This recommended practice provides guidance on vehicle Cybersecurity and was created based off of, and expanded on from, existing practices which are being implemented or reported in industry, government and conference papers. The best practices are intended to be flexible, pragmatic, and adaptable in their further application to the vehicle industry as well as to other cyber-physical vehicle systems (e.g., commercial and military vehicles, trucks, busses). Other proprietary Cybersecurity development processes and standards may have been established to support a specific manufacturer’s development processes, and may not be comprehensively represented in this document, however, information contained in this document may help refine existing in-house processes, methods, etc. This recommended practice establishes a set of high-level guiding principles for Cybersecurity as it relates to cyber-physical vehicle systems.
CURRENT
2015-12-27
Standard
AIR5631A
The purpose of this document is to provide a listing for current commercial and military aircraft landing gear systems and their types and manufacturers. Data has been provided for the following commercial aircraft types; wide body jet airliners, narrow body jet airliners, and turboprop/commuter aircraft and the following military aircraft types; fighter, bomber, cargo, attack, surveillance, tanker and helicopter categories. The aircraft that have been included in this document are in operational service either with airlines, business, cargo or military operators. No information is presented for aircraft that are currently being developed or that are not in extensive usage. This document will provide an informational reference for landing gear engineers to access when evaluating other gear and aircraft systems. Future revisions of this document will add aircraft as they enter into service.
CURRENT
2015-12-11
Standard
ARIS814
ARINC 814 defines an XML encoding and compression standard for aviation. It is based on the Open Geospatial Consortium (OGC) Binary XML document. Binary XML encoding is extended in a way that is both flexible and robust. Compression is added on top of the binary encoding. ARINC 814 is expected to be used with Aeronautical Databases, and in particular, the Airport Map databases defined by ARINC 816 and the proposed ARINC Project Paper 815 Terrain and Obstacle databases.
2015-10-16
WIP Standard
AS6347
This document applies to the development of Plans for integrating and managing electronic materials and processes in equipment for the military and commercial aerospace markets; as well as other ADHP markets that wish to use this document.
CURRENT
2015-08-01
Standard
ARIC735B-2
This document defines a Traffic Surveillance capability for NextGen and SESAR airspace environments. Supplement 2 adds hybrid surveillance functionality. It satisfies recent updates to FAA Airworthiness Circular AC 20-151B - Airworthiness Approval of Traffic Alert and Collision Avoidance Systems (TCAS II), and Technical Standard Order TSO-119d requiring the annunciation of a hybrid surveillance failure. Supplement 2 also adds strobe program pinning, updates TCAS inputs status, improves aircraft troubleshooting, and supports recent central maintenance computer function block point updates.
CURRENT
2015-07-28
Standard
AS8055A
This SAE Aerospace Standard (AS) specifies minimum performance standards for airborne binocular Head-Up Displays (HUDs) in fixed wing (14 CFR part 23, 25) aircraft; while this document is also applicable to rotorcraft (14 CFR part 27, 29) additional performance standards may be required for rotorcraft. This aerospace standard covers basic display standards, but does not include specific application requirements. Specific applications can include flight instrumentation, navigation, engine and system status, alerting, surveillance, communication, terrain awareness, weather, enhanced vision, synthetic vision and other displays. This document covers criteria for conformal and non-conformal HUD systems that are intended for use in the flight deck by the pilot or copilot. Display minimum performance characteristics are specified for standard and other environmental conditions for the purpose of product qualification.
CURRENT
2015-07-01
Standard
EIACALS
This report documents the findings of an industry study panel convened by the Electronic Industries Association (EIA) under the auspices of the Computer-aided Acquisition and Logistics Support (CALS) Industry Steering Committee to determine the best utilization of product data description standards for electronic configuration items in the near term. Appendix A contains a brief outline of the CALS Program. The study group's objective was to determine the most advantageous mix of existing standards for application in specifying digital delivery of product data items in support of weapon system development and support contracts. The evaluation was accomplished by means of a product data requirements matrix in which types of data required by the government throughout the development process were mapped against the applicability of the various standards. A delphi approach, in which users of all of the standards participated, was used to determine applicability.
Viewing 1 to 30 of 84

Filter

  • Standard
    84