1、 AEROSPACE STANDARD Aircraft/Store Common Interface Control Document Format Standard SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and
2、suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions.
3、Copyright 2004 SAE International All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUME
4、NT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: 724-776-4970 (outside USA) Fax: 724-776-0790 Email: custsvcsae.org SAE WEB ADDRESS: http:/www.sae.org Issued 2004-07 AS5609 FOREWORD The Aircraft/Store Common Interface Control Document Format is a standard that defines a common document forma
5、t for aircraft-store logical, mechanical, and environmental interfaces. Its purpose is to assist and harmonize aircraft-store interface standardization and to provide a common document format for the development and comparison of aircraft-store interface control documents (ICDs). This document was p
6、repared by the AS-1B3 Task Group, Aircraft-Store System Integration, under the jurisdiction of the AS-1B Subcommittee, Aircraft-Store Integration, of the SAE AS-1 Committee, Aircraft Systems and System Integration. TABLE OF CONTENTS 1. SCOPE 31.1 Purpose 31.2 Field of Application. 32. REFERENCES. 32
7、.1 Applicable Documents . 32.1.1 SAE Publications 32.1.2 ANSI Publications 42.1.3 U.S. Government Publications. 42.2 Applicable References . 42.3 Definitions 42.3.1 Terminology . 5Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted
8、without license from IHS-,-,-SAE AS5609 - 2 - 3. AIRCRAFT/STORE COMMON INTERFACE CONTROL DOCUMENT FORMAT REQUIREMENTS 53.1 Background 53.2 Application Areas and Format Utilization . 83.2.1 Application Areas . 83.2.2 Utilization and Basic Considerations 83.3 Basic Structure and Generation Rules. 103.
9、3.1 Volume 1 Overview 113.3.2 Volume 2 Overview 183.4 Rules for the Interface Control Document Generation Using This Format. 213.4.1 Introduction 213.4.2 General 213.4.3 Design and Layout Rules. 223.4.4 Use of the Formats in Appendix A and B. 233.4.5 Classified Information. 234. NOTES. 234.1 Revisio
10、n Indicator. 234.2 Intended Use 234.2.1 Implementation. 234.3 Tailoring Guidance. 244.4 Keyword Listing 24APPENDIX A VOLUME 1: MECHANICAL/ELECTRICAL/PHYSICAL INTERFACE CONTROL DOCUMENT TEMPLATE 25APPENDIX B VOLUME 2: LOGICAL INTERFACE CONTROL DOCUMENT TEMPLATE 170Copyright SAE International Provided
11、 by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS5609 - 3 - 1. SCOPE: This SAE Aerospace Standard (AS) defines the editorial format and policies necessary for the publication of Interface Control documents. The Common Interface Co
12、ntrol Document Format Standard defines a common format for aircraft/store interface documents to foster increased interoperability. It is designed with the versatility to serve differing “ICD” philosophies and organizations. This aerospace standard defines the common technical data sections for the
13、Common Interface Control Document Format down to the third header level for the majority of sub-sections. The Common Interface Control Document Format Aerospace Standard provides a structured document format in appendixes supported by example paragraphs, drawings, etc. 1.1 Purpose: The Aircraft/Stor
14、e Common Interface Control Document Format defines the document format to be utilized to define and document aircraft/store interfaces. A common document format is desired to foster increased interoperability of stores and aircraft across platforms. 1.2 Field of Application: This standard applies to
15、 new Aircraft/Store Interface Control Documents, and may be applied to existing ICDs when they are being revised. 2. REFERENCES: 2.1 Applicable Documents: The following publications form a part of this document to the extent specified herein. The latest issue of SAE publications shall apply. The app
16、licable issue of other publications shall be the issue in effect on the date of the purchase order. In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws
17、and regulations unless a specific exemption has been obtained. 2.1.1 SAE Publications: Available from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001. AIR5532 Generic Aircraft Store Interface Framework AS15531 Digital Time Division Command/Response Multiplex Data Bus Copyright SAE Internation
18、al Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS5609 - 4 - 2.1.2 ANSI Publications: Available from ANSI, 25 West 43rd Street, New York, NY 10036-8002. ASCII American Standard Code for Information Interchange 2.1.3 U.S.
19、 Government Publications: Available from DODSSP, Subscription Services Desk, Building 4D, 700 Robbins Avenue, Philadelphia, PA 19111-5094. MIL-STD-1760-D DEPARTMENT OF DEFENSE INTERFACE MILITARY STANDARD FOR AIRCRAFT/STORE ELECTRICAL INTERCONNECTION SYSTEM MIL-STD-1553B Notice 4 Digital Time Divisio
20、n Command/Response Multiplex Data Bus NOTE: Revision B Notice 4 is specifically required. MIL-HDBK-1553 2.2 Applicable References: None 2.3 Definitions: AIRCRAFT: Any vehicle designed to be supported by air, being borne up either by the dynamic action of the air upon the surfaces of the vehicle, or
21、by its own buoyancy. The term includes fixed and movable wing airplanes, helicopters, gliders, and airships, but excludes air-launched missiles, target drones, and flying bombs. CARRIAGE STORE: Suspension and release equipment that is mounted on aircraft on a non-permanent basis as a store, and is i
22、ntended to carry other store(s). Carriage store includes both single adapters and multiple store carriers. Pylons and primary racks (such as an MAU-12 and BRU-10) shall not be considered carriage stores. DISPENSER: Equipment that is mounted on an aircraft on a non-permanent basis as a store and is i
23、ntended to carry devices that are dispensed. Dispensers include, but are not limited to, chaff and flare dispensers, rocket pods, and small munitions dispensers. STORE: Any device intended for internal or external carriage and mounted on aircraft suspension and release equipment, whether or not the
24、item is intended to be separated in flight from the aircraft. Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS5609 - 5 - 2.3.1 Terminology: SHALL: This Term in the Aircraft/Store Common Interfa
25、ce Control Document Format is to be used wherever the criterion for conformance with the specific recommendation requires that there be no deviation. SHOULD: This Term in the Aircraft/Store Common Interface Control Document Format is to be used wherever the criterion for conformance with the specifi
26、c recommendation is to meet a system objective. Failure to meet a “Should” statement shall be justified MUST: This Term in the Aircraft/Store Common Interface Control Document Format is used for a legislative or regulatory requirement (e.g. health and safety) with which the customer, the aircraft co
27、mpany and the store company shall comply. It is not used to express a requirement of the specification. WILL: This Term in the Aircraft/Store Common Interface Control Document Format is used for the future tense. It does not express a requirement of the specification. MAY: This Term in the Aircraft/
28、Store Common Interface Control Document Format expresses a permissible practice or action. It does not express a requirement of the specification. 3. AIRCRAFT/STORE COMMON INTERFACE CONTROL DOCUMENT FORMAT REQUIREMENTS: 3.1 Background: Prior to the establishment of this standard, there were two majo
29、r approaches to the definition of aircraft/store interface control documents. One approach was the “J-weapon” interface control document the United States store and airframe industry has developed. The second was several ICD structure proposals used in Europe on various aircraft programs with the mo
30、st common being the European Industrial Group working on the Typhoon fighter. In addition to the format differences between the two industry approaches, there is also a philosophical difference. Historically, the airframe industry in Europe writes an aircraft to store interface control document base
31、d on the inputs from the store contractor, i.e. manufacturing or qualification information or even a store interface control document. This was the case when an already developed store had to be integrated in an existing airframe. The interface control document itself may be a part of the contract d
32、ocumentation. Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS5609 - 6 - 3.1 (Continued): In the United States the store contractor writes the core interface control document with inputs from t
33、he airframe contractors through the interface control working group process. The core document defines the store mechanical, electrical, and environmental interfaces. The core document also defines the functional requirements for the store and aircraft to support integration of the interface. Each a
34、ircraft that integrates the store then writes an annex, to define aircraft peculiarities for specific requirements implementation. The aircraft annex is written to define aircraft dependent implementation of the mechanical, electrical, environmental and functional interfaces and optional capabilitie
35、s that are implemented from the core interface control document. If for example there is an optional capability, which the aircraft may use, it is described in the core as an “aircraft may“ and introduced in the aircraft annex as an “aircraft shall”. Since neither industrial group (Europe and United
36、 States) is expected to adopt the others approach to aircraft/store interface definition, the Aircraft/Store Common Interface Control Document Format is structured to serve both approaches. It can be used as a single form to describe the agreed interface or as the form to lay down store interface co
37、nsiderations and - as an annex - the aircraft side of the interface reflecting the same basic structure. Figure 1 and Figure 2 illustrate the dual uses of this document format. The Aircraft/Store Common Interface Control Document Format is split into two volumes. The reason the document is defined i
38、n two volumes is to separate the hardware driven elements of the interface, which tend to change infrequently from the software elements of the interface which historically change very frequently during the development process. Copyright SAE International Provided by IHS under license with SAENot fo
39、r ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS5609 - 7 - FIGURE 1 - CICD Format for a “J-ICD“ Approach for One Store with Multiple Aircraft Annexes FIGURE 2 - CICD Format for an “ICD“ Approach for a Single Store or Aircraft or Structure Copyright SAE Internationa
40、l Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS5609 - 8 - 3.2 Application Areas and Format Utilization: 3.2.1 Application Areas: The Aircraft/Store Common Interface Control Document Format is intended for use in all ar
41、eas and combinations of aircraft to store integration for all kinds of stores (including miniature stores, carriage stores and dispensers) of any origin (legacy or new products). 3.2.2 Utilization and Basic Considerations: In principle there exists just one interface, which shall be described within
42、 one Interface Control Document. That is the direct interface between the aircraft and the store mechanically and electrically directly connected (no intermediary system) together. However, depending on the interface control document approach (European verses United States) and on the stage of the d
43、evelopment or the integration, there may be a single point of view, that is the interface can only be described from one side. For example during European aircraft development with the requirement to integrate a specific set of stores, the store design authority will produce a document that provides
44、 baseline information describing the interface between the store and a non-specific or generic aircraft, sometimes referred to as a Generalized Aircraft Interface Specification (GAIS). The GAIS structure is identical to that of the ICD to be generated later, containing detailed information relevant
45、to the store and generic information on what is expected of the aircraft. For a United States interface control document approach, the document will contain the functional requirements for both sides of the interface and the mechanical, electrical, and environmental requirements for the store (calle
46、d the “Core Interface Control Document”), but the aircraft specific appendix, which describes the aircraft peculiar implementation of the functional, mechanical, electrical, and environmental interface, may not be available. If a carriage store is connected between the aircraft and the weapon, thing
47、s can become more complicated because the carriage store employs an interface to the aircraft and an interface to the store, but part of the carriage store interface to the aircraft may depend on which weapon is carried below the carriage store. For carriage stores with internal electronic boxes or
48、signal adaptation units, several different interface control documents approaches could be utilized. Two Volume 1 documents could be written, one for the carriage store to the aircraft and one for the carriage store to the weapon since each has unique mechanical, electrical, and environmental criter
49、ia. As mentioned above, this will be related to the point of view and the approach to integration (European or United States). Alternatively, for the logical interface defined in the Volume 2 content, the carriage store may act like a black box and simply routes the appropriate signals directly from aircraft to the store and vice versa. Thus only one Volume 2 could be written, because the carriage store interface to the aircr
