SAE AS 5658-2009 Platform Subsystem Common Interface Control Document Format《平台 子系统通用接口控制文件格式》.pdf

《SAE AS 5658-2009 Platform Subsystem Common Interface Control Document Format《平台 子系统通用接口控制文件格式》.pdf》由会员分享，可在线阅读，更多相关《SAE AS 5658-2009 Platform Subsystem Common Interface Control Document Format《平台 子系统通用接口控制文件格式》.pdf（156页珍藏版）》请在麦多课文档分享上搜索。

1、_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 suitability for any particular use, including any patent infringement arising theref

2、rom, 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. Copyright 2009 SAE International All rights reserved. No part of this publication ma

3、y 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 DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: 724-776-4970 (outside USA)

4、Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/AS5658AEROSPACESTANDARDAS5658 Issued 2009-02Platform/Subsystem Common Interface Control Document F

5、ormat RATIONALEThe well adopted AS5609 Aircraft/Store Common Interface Control Document Format Standard leveraged the desire for a general avionics/platform to subsystem interface control document format. This facilitates an easier control and comparison of the products from different suppliers from

6、 the integrator or main contractor point of view and allows the generation of one ICD for different customers from the suppliers point of view. FOREWORDThe Platform/Subsystem Common Interface Control Document Format is a standard that defines a common document format for platform/subsystem logical,

7、physical, and environmental interfaces. Its purpose is to assist and harmonize platform-subsystem interface standardization and to provide a common document format for the development and comparison of platform/subsystem interface control documents (ICDs). This document was prepared by the AS-1C1 Av

8、ionics CICD Task Group, under the jurisdiction of the AS-1C Subcommittee, Avionic Subsystems, of the SAE AS-1 Committee, Platform Systems and System Integration. Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license fr

9、om IHS-,-,-SAE AS5658 Page 2 of 156TABLE OF CONTENTS 1. SCOPE 31.1 Purpose . 31.2 Field of Application 32. REFERENCES 32.1 Applicable Documents 32.1.1 SAE Publications . 32.1.2 ANSI Publications . 32.1.3 Object Management Group Publications 32.1.4 U.S. Government Publications 42.2 Applicable Referen

10、ces: . 42.3 Definitions . 42.3.1 Terminology 43. PLATFORM/SUBSYSTEM COMMON INTERFACE CONTROL DOC FORMAT REQUIREMENTS . 53.1 Background . 53.2 Application Areas and Format Utilization 53.2.1 Application Areas 53.2.2 Utilization and Basic Considerations 53.3 Basic Structure and Generation Rules . 53.4

11、 Volume 1 Overview . 63.4.1 Volume 1 Section 1 Introduction . 63.4.2 Volume 1 Section 2 Applicable Documents 63.4.3 Volume 1 Section 3 Mechanical Interface 73.4.4 Volume 1 Section 4 Electrical Interface 83.4.5 Volume 1 Section 5 Aerodynamics Interface 83.4.6 Volume 1 Section 6 System Safety . 93.4.7

12、 Volume 1 Section 7 Environmental Considerations . 93.4.8 Volume 1 Section 8 Pilot Vehicle Interface . 113.4.9 Volume 1 Section 9 Wireless Communication 113.4.10 Volume 1 Section 10 Support/Maintenance Interface 113.5 Volume 2 Overview . 123.5.1 Volume 2 Section 1 Introduction . 123.5.2 Volume 2 Sec

13、tion 2 Applicable Documents 133.5.3 Volume 2 Section 3 Functional Interface 133.5.4 Volume 2 Section 4 Communication Interface 143.5.5 Volume 2 Section 5 Wireless Communication Interface . 143.5.6 Volume 2 Section 6 Information Format Sheets . 143.5.7 Volume 2 Section 7 Wireless Information Format S

14、heets 143.6 Rules for the Interface Control Document Generation Using This Format . 153.6.1 Introduction . 153.6.2 General . 153.6.3 Design and Layout Rules 153.6.4 Use of the Formats in Appendix A and B 163.6.5 Classified Information . 164. NOTES 164.1 Change Bar Info 164.2 Intended Use . 164.2.1 I

15、mplementation 164.3 Tailoring Guidance 17 APPENDIX A - Volume 1 - Platform/Subsystem Interface Control Document .18APPENDIX B - Volume 2 - Platform/Subsystem Interface Control Document .109Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking p

16、ermitted without license from IHS-,-,-SAE AS5658 Page 3 of 1561. SCOPE This SAE Aerospace Standard (AS) defines the editorial format and policies necessary for the publication of platform/subsystem Interface Control documents. The Common Interface Control Document Format Standard defines a common fo

17、rmat for platform to subsystem interface documents to facilitate subsystem integration. This aerospace standard specifies the common technical data sections for the Common Interface Control Document Format down to the third header level for the majority of sub-sections. The Common Interface Control

18、Document Format Aerospace Standard provides a structured document format in appendixes supported by example paragraphs, drawings, etc.1.1 Purpose The Platform/Subsystem Common Interface Control Document Format standardizes the document format to be utilized to define and document platform/subsystem

19、interfaces. A common document format is desired to facilitate subsystem integration in new or already existing platforms. 1.2 Field of Application This standard applies to new Platform/Subsystem Interface Control Documents, and may be applied to existing subsystem ICDs when they are being revised. 2

20、. 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 applicable issue of other publications shall be the issue in effect on the date of the purchase order. In the event of a

21、 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 and regulations unless a specific exemption has been obtained. 2.1.1 SAE Publications Available from SAE Internationa

22、l, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or 724-776-4970 (outside USA), www.sae.org.AS5609 Aircraft/Store Common Interface Control Document Format Standard AS5506 Architecture Analysis and Design Language (AADL) 2.1.2 ANSI Publications Available

23、 from American National Standards Institute, 25 West 43rd Street, New York, NY 10036-8002, Tel: 212-642-4900, www.ansi.org.ASCII American Standard Code for Information Interchange 2.1.3 Object Management Group Publications Available from the Object Management Group (www.omg.org)UML Unified Modeling

24、Language SysML System Modeling Language Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS5658 Page 4 of 1562.1.4 U.S. Government Publications Available from the Document Automation and Productio

25、n Service (DAPS), Building 4D, 700 Robbins Avenue, Philadelphia, PA 19111-5094, Tel: 215-697-6257, http:/assist.daps.dla.mil/quicksearch/.MIL-STD-1472 Human Engineering MIL.-STD-130 Identification Marking of US Military Property MIL-STD-1553B Notice 4 Digital Time Division Command/Response Multiplex

26、 Data Bus NOTE: Revision B Notice 4 is specifically required. MIL-HDBK-1553A Notice 1 Multiplex Applications Handbook DoDAF Department of Defense Architecture Framework see http:/ Applicable References None2.3 Definitions PLATFORM: In the context of this standard a platform is regarded as any vehicl

27、e designed to be supported by air, being borne up either by the dynamic action of the air upon the surfaces of the vehicle, or by its own buoyancy. The term includes fixed and movable wing airplanes, helicopters, gliders, and airships, with or without on-board operator, but excludes air-launched mis

28、siles, target drones, and flying bombs. SUBSYSTEM: Any equipment intended for internal carriage and installed in a platform. 2.3.1 Terminology SHALL: This Term in the Platform/Subsystem Common Interface Control Document Format is to be used wherever the criterion for conformance with the specific re

29、commendation requires that there be no deviation. SHOULD: This Term in the Platform/Subsystem Common Interface Control Document Format is to be used wherever the criterion for conformance with the specific recommendation is to meet a system objective. Failure to meet a “Should” statement shall be ju

30、stified MUST: This Term in the Platform/Subsystem Common Interface Control Document Format is used for a legislative or regulatory requirement (e.g. health and safety) with which the customer, the platform company and the subsystem company shall comply. It is not used to express a requirement of the

31、 specification. WILL: This Term in the Platform/Subsystem 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 Platform/Subsystem Common Interface Control Document Format expresses a permissible practice

32、or action. It does not express a requirement of the specification. Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS5658 Page 5 of 1563. PLATFORM/SUBSYSTEM COMMON INTERFACE CONTROL DOCUMENT FORM

33、AT REQUIREMENTS 3.1 Background The SAE generated AS5609 Aircraft/Store Common Interface Control Document Format. This standard has been adopted by the military platform industry and demanded the generation of a comparable standard for platform to subsystem interfaces. Currently each supplier of subs

34、ystems either uses its own format for the subsystem interface or is required to use the format of the subsystem integrator i.e. the platform manufacturer. This standard facilitates the subsystem integration through easy identification of technical information in similar document locations and allows

35、 the generation of a single subsystem ICD for different manufacturers/platforms. Additionally, this standard can support the handling of a complex interface through the provision of a complete guideline of considerable points relevant in a subsystem integration. 3.2 Application Areas and Format Util

36、ization 3.2.1 Application Areas The Platform/Subsystem Common Interface Control Document Format is intended for use in all areas and combinations of platform to subsystem integration for all kinds of subsystems (including equipment and pods) of any origin (legacy or new products). 3.2.2 Utilization

37、and Basic Considerations There exists just one interface from the subsystem point of view, which shall be described within one Interface Control Document. That is the direct interface between the platform and the subsystem logically, mechanically and electrically directly connected (no intermediary

38、system) together. All other platform subsystems interfacing with the subsystem subject to integration are regarded as the platform itself.3.3 Basic Structure and Generation Rules The Platform/Subsystem Common Interface Control Document is split into two volumes. Volume 1 covers mostly hardware aspec

39、ts such as the mechanical or electrical interface, whilst Volume 2 specifies the logical part and provides the Signal Format Sheets. For simple interfaces, the two volume approach may be unnecessary. Dependent on the size and intent of the interface control document, the author may retain a single v

40、olume approach, but shall keep to the same section/paragraph sequence defined in the Platform/Subsystem Common Interface Control Document Format for that document. For example, if the subsystem has no logical interface requirements with the platform, the author may drop Volume 2 and only write a Vol

41、ume 1 document, but the entire format must be utilized. Parts that are not applicable can be simply marked as “Not Applicable” but they must not be deleted. However, all parts of the Platform/Subsystem Common Interface Control Document Format may be tailored to the authors needs. This may be necessa

42、ry to cope with special requirements or needs of a subsystems integration project, where test assets or subsystem prototypes (development models) may be necessary during the development phase. This may require a separate ICD to cover e.g. specific flight test instrumentation connections and recordin

43、g capability. Prior to commencing the writing of a platform/subsystem ICD it is necessary to understand the data that is required to be captured in the document. A checklist aligned against the section numbers in the two main volumes of the ICD can assist an ICD author in gathering the relevant data

44、. The checklist identifies the relevant section numbers and titles and provides check columns for the author to record if specific information is required in the ICD or not. Some sections are mandatory so these will already be checked in the list. The final column of the checklist then gives a brief

45、 outline of the type of datathat is required to populate each section of the ICD or where blank, acts as a working sheet for the ICD author to compile notes of project-specific information that needs to be gathered. Copyright SAE International Provided by IHS under license with SAENot for ResaleNo r

46、eproduction or networking permitted without license from IHS-,-,-SAE AS5658 Page 6 of 156If possible, reference to existing standards and definitions shall be given to avoid multiple specifications. Deviations shall be clearly identified. Whenever possible, favorably in the logical sections, modern

47、system design languages (e.g. UML, SysML, AADL) and system architecture description methods (DoDAF) shall be used. 3.4 Volume 1 Overview Volume 1 covers mostly hardware aspects such as the mechanical or electrical interface. The heading level 1 structure for Volume 1 is shown in FIGURE 1. Examples f

48、or each paragraph of the Volume 1 template are provided in Appendix A. 1 Introduction2 Applicable Documents3 Mechanical Interface4 Electrical Interface5 Aerodynamics Interface6 Safety7 Environmental Consderations8 Pilot Vehicle Interface9 Wireless Communication10 Support/ Maintenance InterfaceFIGURE 1 CICD FORMAT STRUCTURE VOLUME 1 LEVEL 1 3.4.1 Volume 1 Section 1 Introduction This section shall cover the introduction to the Volume 1 of the interface control document. An overview of the volume content and detailed