Criteria

Text:
Content:
Display:

Results

Viewing 151 to 180 of 5710
2016-12-21
WIP Standard
ARP6915
This Aerospace Recommended Practice (ARP) offers best practice regarding the implementation of IVHM systems taking into account Human Factors, both the vehicle crew and the maintenance staff. The document will include considerations regarding both military and civil fixed wing aircraft. Safety implications will also be addressed.
CURRENT
2016-12-21
Standard
AS6070/2A
SCOPE IS UNAVAILABLE.
CURRENT
2016-12-20
Standard
AS6349
This SAE Aerospace Standard (AS) establishes the minimum performance standards for equipment used as secondary alternating current (AC) electrical power sources in aerospace electric power systems.
CURRENT
2016-12-20
Standard
AIR6521
This platform specific Interface Control Document (ICD) provides an example mapping to the Object Management Group’s (OMG) Data Distribution Service (DDS) infrastructure middleware. The mapping is based on the Unmanned Systems (UxS) Control Segment (UCS) Architecture: Model, AS6518. A series of non-normative implementation choices have been made that are specific to this ICD. These implementation choices may not be appropriate for different system implementations. The machine readable ICD and result of this mapping and implementation choices are provided with AIR6521. Use and understanding of this document assumes a working knowledge of the UCS Architecture, the model structure and its contents.
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
AIR6517
This User Guide describes the content of the Rhapsody version of the UCS Architectural Model and how to use this model within the Rhapsody modeling tool environment. The purpose of the Rhapsody version of the UCS Architectural Interface Control Document (ICD) model is to provide a model for Rhapsody users, derived from the Enterprise Architect (EA) model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6517 Rhapsody Model, have been validated to contain the same content as the AS6518 model for: - all UCS ICD interfaces - all UCS ICD messages - all UCS ICD data directly or indirectly referenced by ICD messages and interfaces - the Domain Participant, Information, Service and Non Functional Properties Models
CURRENT
2016-12-20
Standard
AIR6516
This User Guide describes the content of the Rational Software Architect (RSA) version of the UCS Architectural Model and how to use this model within the RSA modeling tool environment. The purpose of the RSA version of the UCS Architectural Interface ICD model is to provide a model for Rational Software Architect (RSA) users, derived from the Enterprise Architect (EA) ICD model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6516 RSA Model, have been validated to contain the same content as the AS6518 model for: - all UCS ICD interfaces - all UCS ICD messages - all UCS ICD data directly or indirectly referenced by ICD messages and interfaces - the Domain Participant, Information, Service and Non Functional Properties Models
CURRENT
2016-12-20
Standard
AIR6515
This User Guide describes the content of the Enterprise Architect (EA) version of the UCS Architectural Model and how to use this model within the EA modeling tool environment. The purpose of the EA version of the UCS Architectural Interface Control Document (ICD) model is to provide a working model for Enterprise Architect tool users and to serve as the source model for the Rational Software Architect (RSA) and Rhapsody models (AIR6516 and AIR6517). The AIR6515 EA Model has been validated to contain the same content as the AS6518 model for: - all UCS ICD interfaces - all UCS ICD messages - all UCS ICD data directly or indirectly referenced by ICD messages and interfaces - the Domain Participant, Information, Service, and Non Functional Properties Models
CURRENT
2016-12-20
Standard
AS6513
This document is the authoritative specification within the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture for establishing conformance requirements for UCS products. The UCS products addressed by this specification are UCS software components and UCS software configurations that provide one or more UCS services, and UCS systems that employ one or more UCS services. The conformance of UCS products is determined by assessing the conformance of the UCS product description to the UCS Architecture. The UCS product description includes test artifacts.
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-12-20
Standard
AIR6520
Governance of the Unmanned Aircraft System (UAS) Control Segment (UCS) Architecture was transferred from the United States Office of the Secretary of Defense (OSD) to SAE International in April 2015. Consequently, a subset of the UCS Architecture Library Release 3.4(PR) has been published under SAE as the Unmanned Systems (UxS) Control Segment (UCS) Architecture, AS6512. This Version Description Document (VDD) describes the correspondence and differences between the two architecture libraries.
CURRENT
2016-12-20
Standard
AIR6514
This interface control document (ICD) specifies all software services in the Unmanned Systems (UxS) Control Segment Architecture, including interfaces, messages, and data model.
CURRENT
2016-12-20
Standard
AS6512
This document is the Architecture Description (AD) for the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture. This AD serves as the official designation of the UCS Architecture - SAE AS6512. The UCS Architecture is expressed by a library of SAE publications as referenced herein. The other publications in the UCS Architecture Library are: AS6513, AIR6514, AIR6515, AIR6516, AIR6517, AS6518, AIR6519, AIR6520, AIR6521, and AS6522.
CURRENT
2016-12-20
Standard
AS6518
This brief User Guide recaps the content of the AS6518 UCS Architectural Model described in detail in AS6512 UCS Architecture: Architecture Description. The purpose of the UCS Architecture Model is to provide the authoritative source for other models and products within the UCS Architecture as shown in the AS6512 UCS Architecture: Architecture Description.
2016-12-17
WIP Standard
J2394
This SAE standard establishes the minimum construction and performance requirements for seven conductor 1/8 2/10 4/12 cable for use on trucks, trailers and converter dollies. Where appropriate, the standard refers to two types of cables, (Type F and S, described later in the standard), due to the variation in the performance demands of cables used in flexing and stationary applications. While the document’s title refers to ABS Power to differentiate the document from the SAE J1067 standard that it supersedes, the scope applies to both the primary green cable for powering ABS and lighting and the yellow auxiliary cable of the same construction.
2016-12-14
WIP Standard
ARP5890B
This document establishes guidelines for a Reliability Assessment Plan (herein also called the Plan), in which Electronic Engine Control manufacturers document their controlled, repeatable processes for assessing reliability of their products. Each Electronic Engine Control manufacturer (the Plan owner) prepares a Plan, which is unique to the Plan owner. This document describes processes that are intended for use in assessing the reliability of Electronic Engine Controls, or subassemblies thereof. The results of such assessments are intended for use as inputs to safety analyses, certification analyses, equipment design decisions, system architecture selection and business decisions such as warranties or maintenance cost guarantees.
CURRENT
2016-12-13
Standard
AIR6212
This document collates the ways and means that existing sensors can identify the platform’s exposure to volcanic ash. The capabilities include real-time detection and estimation, and post flight determinations of exposure and intensity. The document includes results of initiatives with the Federal Aviation Administration (FAA), the European Aviation Safety Agency (EASA), the International Civil Aviation Organization (ICAO), Transport Canada, various research organizations, Industry and other subject matter experts. The document illustrates the ways that an aircraft can use existing sensors to act as health monitoring tools so as to assess the operational and maintenance effects related to volcanic ash incidents and possibly help determine what remedial action to take after encountering a volcanic ash (VA) event.
CURRENT
2016-12-13
Standard
J2012_201612
This document supersedes SAE J2012 DEC2007, and is technically equivalent to ISO 15031-6:2010 with the exceptions described in 1.2. This document is intended to define the standardized Diagnostic Trouble Codes (DTC) that On-Board Diagnostic (OBD) systems in vehicles are required to report when malfunctions are detected. SAE J2012 may also be used for decoding of enhanced diagnostic DTCs and specifies the ranges reserved for vehicle manufacturer specific usage.
CURRENT
2016-12-13
Standard
J2012DA_201612
The J2012 Digital Annex of Diagnostic Trouble Code Definitions Spreadsheet provides DTC information in an excel format for use in your organization's work processes. The column headings include the same information as contained in the J2012 standard.

There is also a column heading denoting which DTC have been updated in the current version.

2016-12-08
WIP Standard
AS6294/1
1. Review existing standards for PEM qualification & screening  NASA: PEM-INST-001, MSFC-STD-3012  QML Class N, Class Y (non-hermetic microcircuits)  QML Class F, Class L (non-hermetic hybrids)  etc. 2. Provide recommendations for unification  Address concerns for Space & terrestrial applications  Address possible holes in current documents  Make recommendations to improve QML Class N and Class Y 3. Be resource to industry when questions come up that are not being addressed by current PEM flows
CURRENT
2016-12-08
Standard
J3114_201612
The aim of this Information Report is to provide terms and definitions that are important for the user’s interaction with L2 through L4 driving automation system features per SAE J3016, which provides a basis for this document.
2016-12-07
WIP Standard
J983
This SAE Recommended Practice applies to mobile, construction type, crane and cable excavator hand and foot controls. It should not be construed to limit the use of, or to apply to combination controls, automatic controls, or any other special operating control requirements.
CURRENT
2016-12-06
Standard
J1939/11_201612
This document defines a physical layer having a robust immunity to EMI and physical properties suitable for harsh environments. CAN controllers are available which support the CAN Flexible Data Rate Frame Format. These controllers, when used on SAE J1939-11 networks, must be restricted to use only the Classical Frame Format compliant to ISO 11898-1:2015. These SAE Recommended Practices are intended for light- and heavy-duty vehicles on- or off-road as well as appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of interest include but are not limited to: on- and off-highway trucks and their trailers; construction equipment; and agricultural equipment and implements.
CURRENT
2016-12-06
Standard
J2601_201612
SAE J2601 establishes the protocol and process limits for hydrogen fueling of light duty vehicles. These process limits (including the fuel delivery temperature, the maximum fuel flow rate, the rate of pressure increase and the ending pressure) are affected by factors such as ambient temperature, fuel delivery temperature and initial pressure in the vehicle’s compressed hydrogen storage system. SAE J2601 establishes standard fueling protocols based on either a look-up table approach utilizing a fixed pressure ramp rate, or a formula based approach utilizing a dynamic pressure ramp rate continuously calculated throughout the fill. Both protocols allow for fueling with communications or without communications. The table-based protocol provides a fixed end-of-fill pressure target, whereas the formula-based protocol calculates the end-of-fill pressure target continuously.
2016-12-06
WIP Standard
AS35051A
No scope available.
CURRENT
2016-12-01
Standard
J1939/14_201612
CAN controllers are now available which support the Flexible Data Rate Frame Format. These controllers, when used on SAE J1939-14 networks, must be restricted to use only the Classical Frame Format compliant to ISO 11898-1:2015. This SAE Recommended Practice is intended for light- and heavy-duty vehicles on- or off-road as well as appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of interest include but are not limited to: on- and off-highway trucks and their trailers; construction equipment; and agricultural equipment and implements.
Viewing 151 to 180 of 5710