Criteria

Text:
Content:
Display:

Results

Viewing 121 to 150 of 43615
2016-12-24
WIP Standard
TAHB0009A
This handbook provides "how to" guidance to industry and government for the reliability Activities and Methods contained in ANSI/GEIA-STD-0009 for developing reliable products and systems, successfully demonstrating them during test and evaluation, and sustaining them throughout the system/product life cycle. ANSI/GEIA-STD-0009 requires the developers and customer/users working as a team to plan and implement a reliability program that provides systems/products that satisfy the user's requirements and expectations using a systems engineering approach. The four Objectives of ANSI/GEIA-STD-0009 are listed below: Objective 1: Understand Customer/User Requirements and constraints. The team (developer, customer, and user), includes 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 are generated. Objective 2: Design and redesign for reliability.
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.
2016-12-21
WIP Standard
AMS2808E
This specification covers requirements for identification of forgings, including die forgings, hand forgings, and rolled rings.
CURRENT
2016-12-21
Standard
AS6070/2A
SCOPE IS UNAVAILABLE.
2016-12-21
WIP Standard
AS81765A
This specification covers requirements for material used in electrical insulating heat shrinkable components. The continuous operating temperature of these materials shall range from -75°C to +200°C (-103°F to +392°F).

Classification: The properties of heat shrinkable molded components shall be as specified in the applicable specification sheet.

2016-12-21
WIP Standard
AMS2800E
This specification covers the requirements for identification of finished parts.
2016-12-21
WIP Standard
AMS3582B
This specification covers a crosslinked polyvinyl chloride plastic in the form of flexible, thin-wall, heat-shrinkable tubing. Primarily for use as a flexible, electrical insulation tubing whose diameter can be reduced to a predetermined size by heating to 175 degrees C (345 degrees F) or higher. This tubing is stable for continuous exposure from -20 to +105 degrees C (-5 to +220 degrees F).
2016-12-21
WIP Standard
AMS3579E
This specification covers a non-crosslinked polyvinyl chloride plastic in the form of flexible, thin-wall, heat-strinkable tubing with a low recovery temperature.

These products have been used typically as a flexible, electrical insulation tubing whose diameter can be reduced to a predetermined size by heating to 150 degrees C (302 degrees F) or higher, but usage is not limited to such applications. This tubing is stable for continuous exposure from -20 to +105 degrees C (-4 to 221 degrees F).

2016-12-21
WIP Standard
AMS3593B
This specification covers an irradiated, thermally-stabilized, flame-resistant, modified-polyvinylidene-fluoride plastic in the form of extra-thin-wall tubing. Primarily for use as a semi-rigid, electrical insulation tubing and marker sleeves in short lengths whose diameter can be reduced to a predetermined size by heating to temperatures of 175 degrees C (347 degrees F) or higher.
2016-12-21
WIP Standard
AMS3683B
This specification covers a thermally-stabilized, irradiated modified fluoropolymer in the form of very-thin-wall tubing. This tubing has been used typically as a flexible, electrical insulation tubing whose diameter can be reduced to a predetermined size by heating to 150 degrees C (302 degrees F) or higher, but usage is not limited to such applications.
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
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
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
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
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
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
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
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
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
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
Viewing 121 to 150 of 43615