1、MIL-HDBK-2222 NOTE: MIL-STD-2222 has been redesignated as a handbook, and is to be used for guidance purposes only. This document is no longer to be cited as a requirement. For adminispive expediency, the only physical change from MIL-STD-2222 is this cover page. However, this document is no longer
2、to be cited as a requirement. If cited as a requirement. contractors may disregard the requirements of this document and interpret its contents only as guidance. NOT MEASUREMENT I SENSITIVE MIL-HDBK-2222 (AS) 29 SEPTEMBER 1997 SUPERSEDING 12 AUGUST 1992 MIL-STD-2222 DEPARTMENT OF DEFENSE HANDBOOK FO
3、R INTERFACE CONTROL DOCUMENTATION FOR AVIONIC SYSTEMS This handbook is for guidance only. Do not cite this document as a requirement. AMSC NIA AREA GDRQ DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. - -* Provided by IHSNot for ResaleNo reproduction or networking p
4、ermitted without license from IHS-,-,-MIL-HDBK-2222 = 9999970 02b4LL7 44T MIL-STD-2222(AS) FOREWRD 1. This military standard is approved for use by the Naval Air Systems Wand, Department of the Navy, and is available for use by all Departments and Agencies of the Department of Defense. 2. Beneficial
5、 comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to: Commanding Officer, Naval Air Warfare Center Aircraft Division Lakehurst, Systems Requirements Department, Code SR3, Lakehurst, NJ 08733-5 Proposa 3. Contro
6、l 1 1 O0 by using the self-addressed Standardization Document Improvement (DD Form 1426) appearing at the end of this document or by. letter. This standard provides. information for understanding the Interface Document (ICD) system, the ICD requirements and participant obligations for the support of
7、 the IC0 process. This standard serves as a useful tool for government personnel, contractors and airframers .by specifying hardware and software .detailed interfaces. This standard can be used to document the interfaces between various avlonic systems. 4. The Naval Atr Systems Command has adopted a
8、 unique format for the ICD. This format includes “A“ size sheets measuring 8.5 inches by 11 inches and“6“ size sheets mea.suring li inches by 17 inches. The “A“ size sheets contain the text data information and the “B“ site sheets contain the interface schematic diagrams for the Ia Samples of “A“ an
9、d “B“ sited ICDs . are provided in appendi x B. 5. Statement of work information is given in 4.10. Use of th information will enable equipment manufacturers (henceforth refer 1 contractors) and airframers to readily complete aconttactual bid .o the ICD work. Typical contractor and airframer IC0 task
10、s are as fol a. Contractors and airframers shall provide data for the cmen t i ssues and approve the final i zed ICDs . is to as s uppot t lows: . I CD b. Contractors and airframers shall furnish interface design data at an agreed future date .(both contractors -and airframers must precisely agree a
11、s to what missing data is required, when it wi 11 be furnished, and which contractor or airframer is responsible). 6. Benefits of the ICDs are as fol lows: a. The documents provide a mutual interface agreement which is approved by the two affected contractors and airfrmers at a very early stage of t
12、he program. b. The “living“ documents exist for the duration of the program so C. The format optimizes the information on sheets that are readily. that changes can be accommodated. reproducible. . i i- Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
13、d. Th.e documents are easily understood and eliminate unnecessary verbiage. e. The ICOs provide a means to control cost and schedule. iiiliv Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-2222 9999970 0264LL9 212 H CONTENTS PARAGRAPH PAGE .
14、 1 . SCOPE . 1 1.1 Scope 1 1.2 Appl icabi 1 i ty 1 2 . 2.1.1 2.2 3 . 3.1 3.1.1 3.1.2 3.1.3 3J . 4 3.1.5 3.1 -6 3.1.7 3.1.8 3.1.9 3.2 4 . 4.1 4.2 4.2.1 4.2.2 4.2.3 4.3 4.4 4.5 4.5.1 4.5.2 4.5.3 4.5.4 4.5.5 4.5.6 4.5.7 4.6 4.7 4.8 4.9 4.9.1 4.9.2 APPLICABLE DOCUMENTS 2 Specifications and standards 2 O
15、rder of precedence . 2 DEFINITIONS AND ABBREVIATIONS . 3 Definitions 3 Change notice 3 Change request . 3 Design specification differences table . 3 Government field activity 3 Interface control document . 3 Interface Coordination Working Group . 3 Interface design data requirement 3 Statement of wo
16、rk . .i . 3 Unreleased documents . 3 Abbreviations 3 GENERAL REQUIREMENTS . ICD purpose ICD types . Systems on pl atforms System to system . Data exchanges . Requirements for ICDs . Initiation of ICDs Coordination process . ICD process Government field activity Unreleased documents Preliminary Comme
17、nt issues . Required signatures for released documents . Interface Coordination Working Group meetings Interface Design Data Requirement (IDOR) . ICD document structure . ICD data content . Change procedures Change request . Standard CR form . 5 5 5 5 5 6 6 6 6 6 6 6 8 8 8 8 8 8 8 9 9 9 V Provided b
18、y IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- NIL-HDBK-2222 9999970 02b4L20 T34 CONTENTS PARAGRAPH PAGE . 4.9.3 Change notice 9 4.10 Statement of work 10 5 . 5.1 5.2 5.2.1 5.2.2 5.2.3 5.3 5.3.1 5.3.2 5.4 5.4.1 5.4.2 5.4.2.1 5.4.2.2 5.4.2.3 5.4.2.4 5.4.3 5.4
19、.4 5.4.5 5.4.6 5.4.6.1 5.4.6.2 5.4.6.3 5.4.6.4 5.4.6.5 5.4.6.6 5.4.6.7 5.4.6.8 5.4.6.9 5.4.6.10 5.4.6.11 5.4.6.12 5.4.6.13 5.4.6.13.1 5.4.6.13.2 5.4.6.14 DETAILED REQUIREMENTS 17 ICD process 17 IDDR document structure 17 IDDR format 17 IDDR origin 17 Status reporting 17 ICD document structure . 17 I
20、CD numbering method . 17 Document structure :. . 18 ICD data content . 18 Commcn items . 18 . IDDRs. techni cal approval, and design differences table 18 IDDR table . 18 Revisions 19 Design specification differences table . 19 Completed IDDR table . 19 Effective sheets . 19 Change request record 19
21、Document structure . 19 Table of contents 19 List of tables -19 Li st of abbreviations and acronyms 20 Applicable documents . 20 Introduction . 20 Notation 20 Requirements , 20 Functional block diagram 20 System interface block diagram . 20 Bus and data interfaces 21 Discrete interfaces 21 Operation
22、al description 21 Software . 21 Sys. tern software configuration . 21 Bus and data interface software messages . 21 Meckanical interfaces . 21 Technical approval . 19 vi Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MI L-STD-2222 (AS 1 CONTENTS PAR
23、AGRAPH 5.4.6.15 5.4.6.16 5.4.6.17 5.4.6.18 5.5 5.5.1 5.5.2 5.5.3 5.5.4 5.5.5 5.5.6 6 . 6.1 6.2 6.3 FIGURE 1 . 2 . 3 . 4 . 5 . 6 . 7 . TABLE I II APPENDIX A B Power 21 RF transmission specifications . 22 Equipment location . 22 Cable and connector specifications . 22 Statement of work 22 Applicabilit
24、y 22 ICD preparation 22 Data for ICDs 22 Method of transmittal 22 ICD ICWG meetings 23 .Coordination cycle . 23 NOTES 24 Intended use . 24 Issue of DoDISS 24 Subject term (key word) listing 24 PAGE ICD development and management process 7 Change request cover sheet 11 First sheet change request samp
25、le . 12 Fol low-on sheet of change request . 13 Sample of change request cover sheet . 14 Sample of the first sheet of the change request . 15 Sample of a follow-on sheet of the change request . 16 PAGE . Typical coordination cycle . 23 Matrix of interface control responsibilities 27 ICWG PROCEDURES
26、 . 25 PARTIAL LIST AND SAMPLES CF U.S. NAVY ELECTRONIC WARFARE SYSTEMS ICDs 29 SAMPLE I . PLATFORM-TO-SYSTEM ICD 31 SAMPLE II . SYSTEM-TO-SYSTEM ICD (DIRECT INTERFACE) . 127 SAMPLE III . SYSTEM-TO-SYSTEM ICD (INDIRECT INTERFACE) 213 SAMPLE IV . SHEETS FOR PLATFORM-TO-SYSTEM ICDS WITH RF INTERFACES 2
27、41 vi i/vi i i Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-1.1 Scope. s tandardi zed ICDs ICD, of the coord these.contractua1 and airframers to MIL-HDBK-2222 m 9999970 0264122 807 m 1. SCOPE This document provides guidelines for developing and us
28、ing . It informs the users of these documents how to initiate an ination process, and of the methods implemented to change instruments. It also provides information to contractors allow a thorough understanding of the type of data required for ICDs on new systems. 1.2 Applicability. This standard is
29、 intended for use by any government agency, contractor or airframer who desires to use an ICD or generate data to be, incorporated into an ICD. The document is not intended to be a cookbook approach on how to draft an ICD. It is, instead, intended to assist government, contractor and airframer perso
30、nnel with the use of existing ICDs or for estimating the scope of information for a prospective ICD. 1 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-2222 2. APPLICABLE DOCUMENTS 2.1 Government documents. “ 2.1.1 Speclfications and standard
31、s. The following standard forms a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those listed in the issue of the Department of Defense Index ofSpecifications and Standards (DODISSI and supplement thereto, cited in the solicitation
32、 (see 6-21. STANDARDS MILITARY MIL-STD-1553 Aircraft Internal Time Division Command/response Multiplex Data Base (Unless otherwise indicated, copies of the military standard is available from the DODSSP, 3tndardization Documents Order Desk, 700 Robbins Avenue, Bldg. 4D, Philadelphia, PA 19111-5094.)
33、 2.2 Order of precedence. 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 thi s document, however, supersedes appl i cable 1 aws and regulations unless a specific exemption has been obtained 2 Provid
34、ed by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-2222 9999970 0264324 b8T 3. DEFINITIONS AND ABBREVIATIONS 3.1 Definitions. 3.1 .I Change notice. A change request which has been approved and signed by Wo contractors or contractor and airframer, and
35、 the government. 3.1.2 Change request. Document submitted to the government by a user request i ng a change in an ICD. 3.1.3 Design specification differences table. The table in the ICD which highlights all the design specification differences which may cause incompatibilities between contractor,(s)
36、 and airframer. 3.1.4 Government field activity. The activity responsible for the review and coordination of the interface design documentation. 3.1.5 Interface control document. The document that defines interface requirements and responsibilities between two contractors or a contractor and airfram
37、er for specific systems or platforms. 3.1.6 Interface Coordination Workinq Groue. Group composed of the government field activity, contractors .and airframers which reviews and coordinates an ICD prior to approval by the government field activity. 3.1.7 Interface des.ign data requirement. The portio
38、n of the ICD that identifies missing data and potential conflicts. 3.1.8 Statement of work. Document submitted by the government field activity to the affected contractors and airframers with the data requirements to be included in the ICD. 3.1.9 Unreleased documents. Initial drafts of ICDs which ar
39、e circulated by the government field activity to the appropriate airframers and contractors for comment . 3.2 Abbreviations. The abbreviations used in this document are defined as fol lows : Size 8.5“ x 11“ sheet Associate Contractor Agreement Airframe Change Acqui si tion Management Systems and Dat
40、a Requirements Control Li st Airborne Self-protection Jammer Advanced Special Receiver Automated Test Equipment Avionics Size 11“ x 17“ sheet 3 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-BOL CLC 1, - .CMOS CN CR Do0 DODISS DWG ! ECP EMC EM1 FA R
41、 HARM I CD I CWG IDDR . I SM M LV MU X MWS NAVAI R PMA RF RWR RWS SE STD TBS GEN-X W RA. MIL-STD-2222(AS) Bofors Launcher Command Launch Computer Countermeasures Dispensing System Change Noti ce Change Request Department of Defense Department of Defense Index of Specifications and Standards Drawing
42、Engi neeri ng Change Proposal Electromagnetic Compatibility Electromagnetic Interference Federal Acquisition ,Regulation Generic Expendable High Speed Anti-Radiation Missile Interface Control Document Interface Coordination Working Group Interface Design Data Requirement Industrial Security Manual M
43、emory Loader Veri f i er Mu1 ti.plexed Missi le Warning System Naval Air Systems Command Program Management Activity Radio Frequency Radar Warning Receiver Radar Warn i ng System Support Equipment Standard To Be Suppl ied Weapon Rep1 aceabl e Assembly Provided by IHSNot for ResaleNo reproduction or
44、networking permitted without license from IHS-,-,-4. GENERAL REQUIREMENTS . 4.1 ICD yJrDose. The ICD clearly establishes the interface requirements and the interface responsi Si 1 i ties between two contractors or contractor and airframer. This unique format optimizes information on readily reproduc
45、ible sheets. The Government is the central authority for control of any changes; yet the two affected contractors or contractor and airframer signify compliance by signing the ICD. The format of the IC0 provides a disciplined method for identifying, assigning and scheduling responsibilities for unde
46、fined interfaces (i .e., Interface Design Data Requi,rement (IDDR) as descri bed in 4.6). The ICDs are interface management tools. They provide the means for al 1 parties (Government, contractor and airframer personnel) to maintain the latest information on the interfaces. Changes to the interface a
47、re not allowed unlessfirst coordinated and agreed to by all parties of the aff-cted ICD(s1. The coordination process is described in 4.5. The IC9 is an effective tool used to minimize system integration problems by ensuring that al 1 interface; are clearly understood by all contractors and airframer
48、s early in he design stage. Cost and schedule savings have been experienced by this disciplined approach from design start to final systems integration. 4.2 CD types. All ICDs follow the same basic format. There ar? instances where data in or;e ICD directly affects another ICD. This data is accompan
49、ied with “flagj“ to indicate the affected ICDs. 4.2.1 Systems on platforms. System interfaces on the aircraft contain al 1 types of data. A sarnpl e of the AN/ALE-47 to F/A-lBC/D ICD i s provided in appendix 3. Common data (e.g., mechanica! installation data) are marked with flags to indicate other affected platform ICDs. This flag information is essential to the syste
