Criteria

Text:
Topic:
Content:
Display:

Results

Viewing 1 to 30 of 821
2017-10-12
WIP Standard
J1814
General criteria are presented as guidelines for: control device location, resistance, and actuation of hand and foot controls by the machine's operator. The criteria are based upon physical limitations as defined by human factors engineering principles. This SAE Recommended Practice applies to upright seated operators of Road Building and Maintenance, and Specialized Mining Machinery categories of off-road, self-propelled work machines as identified in SAE J1116. The criteria presented should apply to most situations. Each situation, however, must be evaluated as to its own function and its relationship to other functions to achieve the desired operation action in normal and emergency situations with high probability. The values for control displacement and resistance apply only to what is required to achieve the desired performance of the function being controlled for the 5th through the 95th percentile person as defined in ISO 3411.
CURRENT
2017-10-11
Standard
AS6089
This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Controller (NC) complies with the NC requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all of the requirements invoked by documents that are referenced by AS5653. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653 and in this verification document.
2017-09-21
WIP Standard
AIR8012
The purpose of the document is to provide the guidelines of the technological approach for developing a PHM system for EMAs with particular reference to their possible use as primary flight control actuators. It provides a basic description of the physics of the most common degradation processes,a reliability assessment and a discussion on the signals, with the associated data processing, required to build up an effective health monitoring system.
2017-09-20
WIP Standard
AS6062A
This document defines a set of standard application layer interfaces called JAUS Mission Spooling Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Mission Spooling Services represent the platform-independent capabilities commonly found across all domains and types of unmanned systems. At present, 1 service is defined in this document (more services are planned for future versions of this document): • Mission Spooler: Stores mission plans, coordinates mission plans, and parcels out elements of the mission plan for execution The Mission Spooler service is described by a JAUS Service Definition (JSD) which specifies the message set and protocol required for compliance. The JSD is fully compliant with the JAUS Service Interface Definition Language [JSIDL].
CURRENT
2017-09-13
Standard
AS5659/4
This Aerospace Standard (AS) 5659/4 Physical Layer Specification provides guidance for the physical layer of optical networks which use Wavelength Division Multiplexing (WDM), within the AS5659 WDM LAN specification document family. The physical layer consists of the optical interconnections between the functional components of the network. Performance requirements for general interconnections are described. For guidance, standards are identified, corresponding to each of several environments, which describe physical layer design, installation, maintenance, and training.
2017-09-12
WIP Standard
SAE6419
The Loran-C Radionavigation System, managed by the U.S. Coast Guard, is the federally provided radionavigation system for civil marine use in the U.S. coastal waters. It is also designated by the Federal Aviation Administration (FAA) as a supplementary system in the National Airspace System (NAS). This system provides accurate radionavigation and timing services to users in the United States of America and Canada. Loran-C is also being used and developed by several other countries in Europe and Asia. Estimates of Loran-C system accuracy must take into consideration the transmitted signal, signal propagation, signal reception, interference or errors from outside sources such as natural and man-made electromagnetic noise, skywave contamination, geometric dilution of precision, other Loran-C signals, communication information superimposed on the navigation signal, and coordinate conversion.
2017-09-12
WIP Standard
SAE6806
This interface control document defines the (e)Loran based alternate PNT interface for the EGI. It provides technical descriptions of definitions, specifications, and explanations for general distribution to providers, manufacturers, and consumers.
2017-09-12
WIP Standard
SAE6856
This recommended practice provides users with the technical requirements and methods for accessing, viewing, and processing raw GNSS receiver measurements for improved unmanned vehicle navigation solutions.
2017-09-12
WIP Standard
SAE9992
This recommended practice provides guidance for using the eLoran signal for timing, phase, and frequency.
2017-09-12
WIP Standard
SAE9991
This information report provides an overview of the eLoran PNT system.
2017-09-12
WIP Standard
SAE6857
This recommended practice defines the technical requirements for a terrestrial-based PNT system to improve vehicle (e.g. unmanned, aerial, ground, maritime) positioning/navigation solutions and ensure critical infrastructure security, complimenting GNSS technologies.
2017-09-12
WIP Standard
SAE9990
This eLoran transmitted signal standard provides technical descriptions of the waveform, specifications, and explanations. The data channel, receiver specification, and recommended practices are described in the SAE9990 family of standards.
CURRENT
2017-08-22
Standard
AS5506/3
This Behavior Annex provides a standard sublanguage extension to allow behavior specifications to be attached to AADL components. The aim of the Behavior Annex is to refine the implicit behavior specifications that are specified by the core of the language. The Behavior Annex targets the following goals: - Describe the internal behavior of component implementations as a state transition system with guards and actions. However, the aim is not to replace software programming languages or to express complex subprogram computations. - Extend the default run-time execution semantics that is specified by the core of the standard, such as thread dispatch protocols. - Provide more precise subprogram calls synchronization protocols for client-server architectures.
CURRENT
2017-08-18
Standard
AS4113A
This test plan is broken into three major sections for the testing of bus controllers Electrical, Protocol and Noise tests.
CURRENT
2017-08-15
Standard
AS4115A
This test plan consists of two major sections for testing of MIL-STD-1553B data bus systems: Bus Network and System Integration Tests.
CURRENT
2017-08-14
Standard
AS4116A
This Aerospace Standard (AS) defines the test requirements for determining that bus monitors meet the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.
CURRENT
2017-08-14
Standard
AS4114A
This test plan consists of two major sections for the production testing of bus controllers: Electrical tests and Protocol tests.
CURRENT
2017-08-10
Standard
AS4112A
This test plan is broken into two major sections for the production testing of remote terminals: Electrical and Protocol.
CURRENT
2017-08-10
Standard
AS4111A
This SAE Aerospace Standard (AS) contains a sample test plan for AS15531 or MIL-STD-1553B Remote Terminals (RT) that may serve several different purposes. This document is intended to be contractually binding when specifically called out in a specification, Statement of Work (SOW), or when required by a Data Item Description (DID). Any and all contractor changes, alterations, or testing deviations to this section shall be separately listed for easy review.
CURRENT
2017-08-10
Standard
AS4117A
This test plan defines the requirements of data bus components which comply with the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.
2017-08-09
WIP Standard
AS42702
This document establishes techniques for verifying that a Mission Store Interface (MSI) complies with the interface requirements delineated in MIL-STD-1760 Revision E.
2017-08-01
WIP Standard
ARP7208
This ARP establishes guidelines for the use of IEEE-802.3 as a data bus network in military and aerospace vehicles. It encompasses the data cable and its connections for a system utilizing 10Base-T, 100Base-T, 1000BASE-T and 10GBASE-T over copper medium dependent interfaces (MDI). This document contains extensions/restrictions to “off-the-shelf” IEEE-802.3 standards, and assumes that the reader already has a working knowledge of IEEE-802.3.
CURRENT
2017-07-19
Standard
ARP798B
This SAE Aerospace Recommended Practice (ARP) covers the general requirements and test procedures recommended for use with white incandescent integrally lighted instruments. Its use should provide uniformity of illumination from instrument to instrument and legibility under daylight operation. An appendix is provided to familiarize the designer with some of the techniques used to obtain uniformity of color and illumination in various types of instruments.
CURRENT
2017-07-18
Standard
ARP4386D
This SAE Aerospace Recommended Practice (ARP) provides the technical terms and nomenclature, together with their definitions and abbreviations/acronyms that are used in aerospace fluid power, actuation and control systems. NOTE: ARP490 and ARP4493 are sources for definitions specifically for electrohydraulic servovalves.
CURRENT
2017-07-10
Standard
AIR5565
This aerospace information report (AIR) provides historical design information for various aircraft landing gear and actuation/control systems that may be useful in the design of future systems for similar applications. It presents the basic characteristics, hardware descriptions, functional schematics, and discussions of the actuation mechanisms, controls, and alternate release systems.
CURRENT
2017-06-28
Standard
AS47641A
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760B Notice 3. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies.
CURRENT
2017-06-28
Standard
AS47642B
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760C. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies. For validation of aircraft designed to MIL-STD-1760B Notice 3 AS47641 Issued 1999-08 applies.
CURRENT
2017-06-27
Standard
AS4764A
This document establishes techniques for validating that an aircraft station complies with the interface requirements delineated in MIL-STD-1760.
CURRENT
2017-06-27
Standard
AS4270A
This document establishes techniques for validating that a mission store complies with the interface requirements delineated in MIL-STD-1760.
2017-05-23
WIP Standard
AS5680B
This interface standard applies to fuzes used in airborne weapons that use a 3-in fuze well. It defines: - Physical envelope of the fuze well at the interface with the fuze. - Load bearing surfaces of the fuze well. - Physical envelope of the fuze and its connector. - Mechanical features (e.g., clocking feature). - Connector type, size, location and orientation. - Retaining ring and its mechanical features (e.g., thread, tool interface). - Physical envelope of the retaining ring at the interface with the fuze. - Physical space available for installation tools. - Torque that the installation tool shall be capable of providing. This standard does not address: - Materials used or their properties. - Protective finish. - Physical environment of the weapon. - Explosive interface or features (e.g., insensitive munitions (IM) mitigation). - Charging tube. - Torque on the retaining ring or loads on the load bearing surfaces.
Viewing 1 to 30 of 821