Search Results

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 was developed by the SAE AS-1B5 CLARA Task Group to explain and document background information and decisions with associated rationale made in development of the CLARA Interface Control Document (ICD), AIR5682. This rationale document is published separately to preserve information that is not required or provided in the ICD but may be important to users.

This document was developed by the SAE AS-1B5 CLARA Task Group to explain and document background information and decisions with associated rationale made in development of the CLARA Interface Control Document (ICD), AIR5682. This rationale document is published separately to preserve information that is not required or provided in the ICD but may be important to users.

This Handbook is intended to provide useful information on the application of AS5716A. It is for use by System Program Offices, aircraft prime contractors, avionics and store system designers, system integrators and equipment manufacturers and users. This Handbook was prepared to provide users of the standard of the rationale and principles considered during the development of the standard. It is anticipated that the handbook will serve to assist developers in introducing new technology to achieve compliance with the standard and the underlying principles of the standard. It is intended that the Handbook be used alongside the standard, as it does not contain significant extracts of the standard.

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 SAE Aerospace Information Report (AIR) will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.

This SAE Aerospace Information Report (AIR) will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.

This SAE Aerospace Information Report (AIR) defines a Generic Aircraft-Store Interface Framework (GASIF). This is a common framework for modeling and specifying aircraft-store logical interfaces. GASIF complies with the OSI Basic Reference Model (ITU-T Rec. X.200 | ISO/IEC 7498-1) in that it describes operations and mechanisms which are assignable to layers as specified in the OSI Basic Reference Model. This AIR provides a mapping of the Interface Standard for Aircraft-store Electrical Interconnection System (AEIS), MIL-STD-1760, in Appendix C.

This SAE Aerospace Information Report (AIR) defines a Generic Aircraft-Store Interface Framework (GASIF). This is a common framework for modeling and specifying aircraft-store logical interfaces. GASIF complies with the OSI Basic Reference Model (ITU-T Rec. X.200 | ISO/IEC 7498-1) in that it describes operations and mechanisms which are assignable to layers as specified in the OSI Basic Reference Model. This AIR provides a mapping of the Interface Standard for Aircraft-store Electrical Interconnection System (AEIS), MIL-STD-1760, in Appendix C.

This interface standard applies to fuzes/fuzing systems (referred to as fuzing system hereafter) in airborne weapons that use a MIL-STD-1760 interface. It defines the powers, the discrete signals and the serial data interface for the communications at the interface between the fuzing system and the remainder of the weapon, including the weapon control unit, for Class 1 interfaces. Future issues of the standard will provide for additional fuzing system related functionality defined as Class 2 and Class 3 interfaces. For future issues of this standard, the connector definition is contained in AS5680. This standard does not impose any safety requirements and does not supersede or replace any existing applicable safety standards.

This interface standard applies to fuzes/fuzing systems (referred to as fuzing system hereafter) in airborne weapons that use a MIL-STD-1760 type interface. It defines the powers, the discrete signals and the serial data interface for the communications at the interface between the fuzing system and the remainder of the weapon, including the weapon control unit. The Class 1 interface is an electrical only interface that facilitates use of MIL-STD-1760 type platform store interfaces for the fuze to monitor intentional release and defines the fuze interface bus communications protocol to allow sending and receiving data from fuzing systems. Class 2 interfaces add a defined connector and additional interfaces to facilitate the exchange of compatible fuzing systems. Class 3 interfaces add further interface definitions to facilitate the exchange of AS5680A compatible fuzing systems components.