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 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.

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 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.

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.

This document was prepared by the SAE AS-1B1 IMM Task Group to explain and document background information and design decisions made during the development of AS5726. This handbook is published separately to preserve information that is not required or provided in the AS5726 but may be important to system designers to ensure interoperability between the Micro Munition Host and Micro Munition. As a handbook, it cannot be invoked as a requirement in a contract. The structure and numbering of this document mirrors that of AS5726 for the convenience of readers. Headings such as “Requirements” in this handbook should not be interpreted as invoking requirements.

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.

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.

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.

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.

This interface standard applies to fuzes used in airborne weapons that use a 3-Inch Fuze Well. It defines: a Physical envelope of the fuze well at the interface with the fuze. b Load bearing surfaces of the fuze well. c Physical envelope of the fuze and its connector. d Mechanical features (e.g. clocking feature). e Connector type, size, location and orientation. f Retaining ring and its mechanical features (e.g. thread, tool interface). g Physical envelope of the retaining ring at the interface with the fuze. h Physical space available for installation tools. i Torque that the installation tool shall be capable of providing. This standard does not address: j Materials used or their properties. k Protective finish. l Physical environment of the weapon. m Explosive interface or features (e.g. insensitive munitions (IM) mitigation). n Charging tube. o Torque on the retaining ring or loads on the load bearing surfaces.

This standard only defines interconnect, electrical and logical (functional) requirements for the interface between a Micro Munition and the Host. The physical and mechanical interface between the Micro Munition and Host is undefined. Individual programs will define the relevant requirements for physical and mechanical interfaces in the Interface Control Document (ICD) or system specifications. It is acknowledged that this does not guarantee full interoperability of Interface for Micro Munitions (IMM) interfaces until further standardization is achieved.