Search Results

This document will contain methods to verify all aspects of the AS5725 interface, similar to how AS47643 contains verification methods for MIL-STD-1760.

This document specifies the CLARA interfaces of the CLAR Truth Data Generator as shown in Figure 1. The solid bold arrows are defined in Table 1 and Table 2. The dashed arrows from the CLAR Coefficient Generator and Truth Database to the CLAR Data Space Generator indicate a feedback loop and are defined in the CLAR Data Space Generator ICD (Reference 1). The dashed arrow from the Truth Database to the CLAR Coefficient Generator is defined in the CLAR Coefficient Generator ICD (Reference 2). The objective for the CLAR Truth Data Generator is to produce impact data sets to be used in the CLAR Coefficient Generator first to score and form LAR boundaries, and then to generate coefficients. A model of the weapon system that predicts weapon delivery performance to a predefined accuracy is to be used for this purpose. The model can be the Six-Degree-Of-Freedom (6DOF) equations of motion or another mathematical representation that meets the objective for the weapon system LAR.

This document specifies the CLARA interfaces of the CLAR Truth Data Generator as shown in Figure 1. The solid bold arrows are defined in Table 1 and Table 2. The dashed arrows from the CLAR Coefficient Generator and Truth Database to the CLAR Data Space Generator indicate a feedback loop and are defined in the CLAR Data Space Generator ICD (Reference 1). The dashed arrow from the Truth Database to the CLAR Coefficient Generator is defined in the CLAR Coefficient Generator ICD (Reference 2). The objective for the CLAR Truth Data Generator is to produce impact data sets to be used in the CLAR Coefficient Generator first to score and form LAR boundaries, and then to generate coefficients. A model of the weapon system that predicts weapon delivery performance to a predefined accuracy is to be used for this purpose. The model can be the Six-Degree-Of-Freedom (6DOF) equations of motion or another mathematical representation that meets the objective for the weapon system LAR.

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.

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.

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.

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.

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.

CLARA identifies four functions: Data Space Generator, Truth Data Generator, Coefficient Generator, and Reconstructor. Together these four functions standardize the solution to the LAR problem.

CLARA identifies four functions: Data Space Generator, Truth Data Generator, Coefficient Generator, and Reconstructor. Together these four functions standardize the solution to the LAR problem.

The technical architecture defined in this document outlines mandatory, emerging, and needed standards to provide interoperability at key interfaces in the aircraft/store system (including an associated NATO Network Enabled Capability environment), as required to support a future plug-and-play aircraft/store integration capability. These standards relate to services and protocols associated with the subject interfaces. Modeling standards to facilitate the Model Driven Architecture® (MDA®) approach to system definition and implementation are also included. Note that the status of referenced standards as reflected in this document is as of August 2007, and document users should check to see if there has been a subsequent change of status relative to applicable standards.

The technical architecture defined in this document outlines mandatory, emerging, and needed standards to provide interoperability at key interfaces in the aircraft/store system (including an associated NATO Network Enabled Capability environment), as required to support a future plug-and-play aircraft/store integration capability. These standards relate to services and protocols associated with the subject interfaces. Modeling standards to facilitate the Model Driven Architecture® (MDA®) approach to system definition and implementation are also included. Note that the status of referenced standards as reflected in this document is as of August 2007, and document users should check to see if there has been a subsequent change of status relative to applicable standards.

This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760 Revision E.

This document establishes techniques for validating that an aircraft station complies with the interface requirements delineated in MIL-STD-1760.

This document establishes techniques for validating that an aircraft station complies with the interface requirements delineated in MIL-STD-1760.

This document establishes techniques for validating that a mission store complies with the interface requirements delineated in MIL-STD-1760.

This document establishes techniques for validating that a mission store complies with the interface requirements delineated in MIL-STD-1760.

The information presented in this AIR is intended to provide designers of armed unmanned systems with guidelines that may be applied to ensure safe integration and operation of weapons on unmanned platforms. The guidelines have been developed from experiences gained in the design and operation of weapons on manned aircraft that have been accepted by relevant safety authorities in the USA and Europe and proven effective over many years. Whilst the guidelines have been developed from experience with aircraft operations, the concepts are considered equally applicable to non-aircraft systems, such as those used on the surface or undersea environments. This document does not attempt to define or describe a comprehensive safety program for unmanned systems. System Safety is a system characteristic and a non-functional requirement. It has to be addressed at each level of system design, system integration and during each phase of system operation.

The information presented in this AIR is intended to provide designers of armed unmanned systems with guidelines that may be applied to ensure safe integration and operation of weapons on unmanned platforms. The guidelines have been developed from experiences gained in the design and operation of weapons on manned aircraft that have been accepted by relevant safety authorities in the USA and Europe and proven effective over many years. Whilst the guidelines have been developed from experience with aircraft operations, the concepts are considered equally applicable to non-aircraft systems, such as those used on the surface or undersea environments. This document does not attempt to define or describe a comprehensive safety program for unmanned systems. System Safety is a system characteristic and a non-functional requirement. It has to be addressed at each level of system design, system integration and during each phase of system operation.

CLARA identifies four functions: Data Space Generator, Truth Data Generator, Coefficient Generator, and Reconstructor. Together these four functions standardize the solution to the LAR problem. This ICD defines the logical interfaces of the four functions.