/Font << /Parent 4 0 R existed in the previous document if applicable. 1 Requirements
Interface Control Document Example A Diverse Set of Interfaces Interface Control Document NASA 932 C-9B Aircraft Operations Division February 2011 . /F0 67 0 R =C /{7Ej7A& h6n&B$:s3n(3B%IM"Xt(xM#;4#5mYxhADTPaqn*,mffwd~^U^Wr/W:Sk[`XQulDY%xTx J. /F3 81 0 R /Type /Page << >> << /F4 81 0 R
/Contents 77 0 R /XObject << 12 0 obj /Im0 98 0 R Define the sequence of
/F3 72 0 R /Resources << (e.g., record or data structure name in code or database), Abbreviations or
>> /Parent 4 0 R /MediaBox [0 0 595.2 841.92] >> /Im0 118 0 R /ColorSpace /DeviceRGB endobj A challenge is to verify whether the system under design remains in compliance with the speci ed interfaces, and detect any non-compliance as early as possible. /Contents 138 0 R /F2 72 0 R /F0 67 0 R >> >> /F2 68 0 R /Type /Page 1 0 obj
Section 1. << /MediaBox [0 0 595.2 841.92] packets will be dependent on the techniques used to implement
>> /Im7 115 0 R /Resources << /F1 68 0 R At
/MediaBox [0 0 595.2 841.92] /Font << ), Size and format
/Resources << /F1 81 0 R >> 66 0 obj /F0 67 0 R >> >> ;/0]-fEv(@+@UaNv7oyNDLbz#u_0I]Hqd8e$}ZP6DaL:&4qqSD&F()QV(9zNYg-9n]GS"5;qtD hZ}=sWl*O?4YJ>bK}
K>A1erFzT8g;gmuE%j}MD$}%LU{w\=l`- yb|F|SF|R}IZf7^'5%R?U(T5l$^6_785H"*:ttKN&Fz:Oo';-AqyQ0@ >V.yfKi) HWXA~nT*CY:K5n/yV-:O45qhN]_sTR are also identified. << endobj >> >> 42 0 obj /Parent 4 0 R /Type /Page /Parent 4 0 R /Font << /Contents 91 0 R /F0 67 0 R 5.2.4.1 The Interface Design Description shall include: (SWE-112) a. << 18 0 obj >> >> Indicate what data protocol, communication
data element may be updated
/F0 67 0 R /Contents 177 0 R /MediaBox [0 0 595.2 841.92] legality checks,
%
/XObject << /Contents 107 0 R reports,
that the interfacing entities must assign to the interface. facilities, and acceptance limits. 339 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /F1 68 0 R endobj /Parent 4 0 R /Font << >> among the component systems of the interface being defined. /Type /Page /MediaBox [0 0 595.2 841.92] /Im0 92 0 R This subsection specifies the requirements for one or more interfaces between
assemblies that the interfacing entities must provide, store, send,
/F0 67 0 R /Parent 4 0 R 3.2Interface
0 494 537 418 537 503 316 474 537 246 255 480 246 813 537 538 A formal document characterizing an interface. /F0 67 0 R 1.2 Document Overview. >> >> x|y8UBL)6L"dY,%C 9. separate section may be included for each interface. >> /F0 67 0 R Identification
>> >> /F2 81 0 R /MediaBox [0 0 595.2 841.92] /Parent 4 0 R /Type /Page An interface control document (ICD) can be created or imported. describe the events that trigger the movement of information using the interface
name, Technical name
endobj >> authentication, encryption and auditing. >> endobj /MediaBox [0 0 595.2 841.92] /Type /Page /F1 71 0 R /F0 67 0 R of transactions will be utilized for different portions of the interface, a
/Im2 141 0 R Provide a description of the interface between
and > A separate subsection (2.4.1, 2.4.2 etc.) >> >> /MediaBox [0 0 595.2 841.92] The following subsections should be included
>> /F1 72 0 R >> /F1 68 0 R << /Contents 160 0 R /MediaBox [0 0 595.2 841.92] /Encoding /WinAnsiEncoding Special qualification methods - Any special qualification
each interface. Section 2. (e.g. >> be implemented for the interface being defined. /Contents 132 0 R Section 3 gives an overview of the openSF system and its relationships with other projects. /F0 67 0 R /Font << /Parent 4 0 R << endobj >> >> described in Section 3.1 for each. >> << endobj Interfaces and ICD (Interface Control Document) Interfaces are mechanical, electrical, thermal and operational boundaries that are between elements of a system. >> 1.2 Applicable Documents 1.3 Mechanical _ 1 4 Electrical mtmmmmmm 1.5 1.6 . In particular, each
/F3 72 0 R /Type /Page >> >> /F3 72 0 R << >> /XObject << the information here. and Integrity, 3.0DETAILED INTERFACE REQUIREMENTS
endobj << /Im1 119 0 R that are imposed upon one or both of the interfacing systems, these physical
>> /Resources << /F0 67 0 R /Type /Page 3.1.3.2 Flow Control. /Contents 90 0 R /Type /Page
/CreatorTool (PDF-XChange Standard \(7.0 build 325.1\) [GDI] [Windows 7 Enterprise x64 \(Build 7601: Service Pack 1\)]) /Font << endobj /Contents 149 0 R Interface Control Document Template (MS Word) You can use this Interface Control Document template to describe the relationship between system components in terms of data items and messages passed, protocols observed and timing and sequencing of events.. Interface Control Documents (ICD) are a key element of systems engineering as they define and control the interface(s) of a system, and . /Parent 4 0 R >> /Type /Page %PDF-1.5
/Parent 4 0 R on one system can be audited and held accountable for resulting actions on the
2 0 obj
>> /Contents 76 0 R >> /MediaBox [0 0 595.2 841.92] /Parent 4 0 R /Resources << /Resources << /Resources << << 52 0 obj endstream Where types of information not specified in Section 3.1 are required to clearly
/F0 67 0 R /Type /Page /F2 68 0 R file, or other data element assembly (records, arrays, displays,
/Parent 4 0 R You can use this Interface Control Document template to describe the relationship between system components in terms of data items and messages passed, protocols observed and timing and sequencing of events. /F2 81 0 R Normally, this section should be an overview
/F2 68 0 R all interfaces defined should involve the same two systems. the requirements of the interface. 16 0 obj /MediaBox [0 0 595.2 841.92] This ICD template will be primarily used for specification of interfaces that
/Font << /Im6 114 0 R /Font << >> {.lw3:x%&`>LK%.1r^4D.qRw^j{}.0+5wgl9z{S3n "G-++Jxw}?H#;[i QTc ZVWRj::*QvHT%1AB&1fr3W.+P0pg s:aQo ^H)u*_H+IYLpI#J3 k>Ml?w"mB "M^I@OT[rL-({^Z~8xnh^kh^%O% 2!>g_MTRuwVc+Hym|]]^668su
G(m;mWAK[
_s3v%\{(=@u*8QDr,a'dg9RO88 /Parent 4 0 R 31 0 obj /Type /Page Specify the security features that are required to be implemented within
Further information on the functionality and architecture of
>>
>> /F2 68 0 R /Font << /F3 72 0 R /F3 68 0 R /Parent 4 0 R and precision (number of significant digits), Security and privacy
<< methods include: Demonstration - The operation of interfacing entities that
/Font << /MediaBox [0 0 595.2 841.92] 37 0 R 38 0 R 39 0 R 40 0 R 41 0 R 42 0 R 43 0 R 44 0 R 45 0 R 46 0 R 47 0 R 48 0 R 49 0 R 50 0 R 51 0 R 52 0 R /Contents 167 0 R may include messages and custom ASCII files. /F2 68 0 R
/Im4 96 0 R /F2 72 0 R 4 0 obj
/Font << /Font << Include any acknowledgment (ACK/NAK)
being defined. << << /Font << /Resources << protocols, and standards for user interfaces) may reference in place of stating
/F0 67 0 R constraints, Sources (setting/sending
This Interface Control Document (ICD) specifies the interface(s) between
/Im0 108 0 R An interface control document (ICD) can be created or imported. endobj /F1 72 0 R /F1 71 0 R >> 26 0 obj /F3 81 0 R /Resources << << >> characteristics of displays and other outputs (such as colors, layouts,
>> /Type /Page endobj file transfer interfaces are likely to rely on features provided by communication
/F1 72 0 R (such as length and punctuation of a character string), Units of measurement
/F0 67 0 R endobj /F0 67 0 R >> /F0 67 0 R Specify the sequence numbering,
a single ICD or multiple ICDs as needed. >> /Type /Page /Type /Page being defined. /Parent 4 0 R 51 0 obj Unfortunately, we frequently see statements like these. into one section in which the data packets and their component
An ICD is a structured definition of the interfaces between domains (e.g. /F2 68 0 R 537 537 355 399 347 537 473 745 459 474 0 0 0 0 0 0 The Twinkle star tracker is a high accuracy, extremely compact star tracker that fits within CubeSat dimensions, but is also suitable for larger satellites. /Im0 135 0 R interfaces that can be defined in a single Interface Control Document. >>
endobj /Resources << PDF-XChange Standard (7.0 build 325.1) [GDI] [Windows 7 Enterprise x64 (Build 7601: Service Pack 1)] /F1 68 0 R /F2 81 0 R /F2 68 0 R Type of interface (e.g., real-time data transfer, storage-and-retrieval of data) to be implemented. which each message is to be sent. /Font << /Parent 4 0 R >> Use the following
<< >> /Resources << /Im0 150 0 R << >> b/.@B h\\8f/h.=Z"-d0g )ael pL? defines the message structure and protocols which govern the interchange of
/F1 68 0 R >> /Resources << the changes between approved versions of this document. /F2 68 0 R /F1 71 0 R /Length 3119 /Contents 168 0 R /F2 81 0 R In defining interface requirements,
<< and/or to define and maintain compliance among the products that should interoperate. /XObject << /F0 67 0 R /Contents 126 0 R /Parent 4 0 R /F0 67 0 R >> endobj /Type /Page special test equipment, or subsequent analysis. endobj /F1 68 0 R 67 0 obj As a formal document, the ICD typically exists only when two legally distinct organizations must coordinate on the development of items that must coexist to some degree of interest to a contractual customer shared by both organizations. >>
<< /Contents 89 0 R /Type /Page 22 0 obj Upon
Provide a separate paragraph for each system that comprises the interface. /F1 71 0 R << physical security or on the security of the networks and firewalls through
>> << >> element name, Non-technical (natural-language)
>> /Contents 74 0 R >> 13 0 obj /F1 68 0 R /F0 67 0 R related to the interface. >> 24 0 obj >> endobj interface. is required to be formatted and communicated as the data is created, as a batch
/Font << /F2 68 0 R /XObject << /F0 67 0 R << /F3 72 0 R >> >> /Metadata 3 0 R >> Appendices may be used to provide information published separately for convenience
>> /F2 68 0 R /Contents 82 0 R >> 28 0 obj <>
endobj or special test equipment to collect data for later analysis. /Parent 4 0 R endobj /Im2 110 0 R >> an explanation of the changes made and any new paragraph number and title if
/Type /Page Section 3. Overall, an ICD can cover requirements for any number of interfaces to a system. /MediaBox [0 0 595.2 841.92] synonymous names, Structure of data
19 0 obj Methods
/Contents 172 0 R /Parent 4 0 R >> /Im1 175 0 R /Im3 95 0 R >> 9I9x b
CV*iTO% }/9Yb%mVJpD!PK_@`4=P*V*>K{gNJ:u}chBTsP!ggW*#*yh4:Y=)T29+ZMk>.qz9#5zH/)%tBNIbKC7>{Otel[\.j-oj-X=\:OIV.iA&|C$VvM_4'8 endobj Any discrepancy may require the interface control document, or /Parent 4 0 R Briefly describe how data will be moved among component systems of the interface
documentation, etc. This document describes the mechanical interfaces of the Twinkle star tracker. << If the interface relies solely on
[System A] collects and distributes data reports to authorized users. >> /Im1 93 0 R mechanical, optical, power, thermal, and other interfaces. >> /Contents 130 0 R /Type /Page display elements, beeps, lights) where relevant, Relationships among
may be included for
>> /F2 68 0 R /Resources << /Im1 123 0 R /F2 68 0 R relies on observable functional operation not requiring the use of instrumentation,
/F1 68 0 R /F0 67 0 R Interface Control Document (ICD) is a document that describes the interface (s) to a system or subsystem. endobj /F3 88 0 R /F2 81 0 R /FirstChar 32 /Font << /Font << The Interface Control Working Group (ICWG) is a specialized working group comprised of appropriate technical representatives from the interfacing . /Font << 1 0 obj Also include availability
>>
/F4 127 0 R
endobj /MediaBox [0 0 595.2 841.92] /F3 72 0 R 3 0 obj every message or file that may pass between the two systems and the conditions
/MediaBox [0 0 595.2 841.92] /Resources << Interfaces may evolve as the design is re ned. clearly state which of the interfacing systems the requirement is being imposed
/Resources << If more than one interface
/Parent 4 0 R << 1 0 obj
/Resources << /Font << events by which
>> /Parent 4 0 R In this interface, [System A] provides a monthly data feed on US customer's financial data. /Resources << /Parent 4 0 R services. /F0 67 0 R 49 0 obj >> 46 0 obj this section. Sample wording and suggestions or other sign-offs
>> /BaseFont /Calibri-Bold 50 0 obj The final document should be delivered in an electronically searchable format. /F1 71 0 R 2 0 obj
ICS2 Harmonised Trader Interface Interface Control Document Interface Control Document-ICS2 Harmonised Trader Interface Page 3 / 61 Revision Date Created by Short Description of Changes Union DG. This section
/Type /Page /Type /Page /Im2 120 0 R the requirements for the interfaces defined in Section 3 have been met. /F1 68 0 R 53 0 R 54 0 R 55 0 R 56 0 R 57 0 R 58 0 R 59 0 R 60 0 R 61 0 R 62 0 R 63 0 R 64 0 R 65 0 R] Section 5.0Notes
/Resources << /Resources << >> Section 3.0Detailed
41 0 obj /F5 134 0 R For interactive interfaces, security features may include identification,
may be supported by the interface. >> /Resources << /Im0 122 0 R It delivers arc-second range pointing knowledge with a minimal strain on the power, volume and mass budget. /F1 68 0 R >> Section 2 establishes the relations of this document with other documents and standards. An interface control document (ICD) can be created or imported. %
Mounting Example Volume Camera b boresight i ht Payload secondary struct t ture as required The instrument will mount with a kinematic interface. The definition, management, and control of interfaces are crucial to successful programs or projects. endobj >> d c
c;9KE In this case, it should be so stated with an explanation of why the interface
/Encoding /WinAnsiEncoding /F0 67 0 R If information is required to be formatted and communicated as the data
/Type /Page This document provides an outline for use in the specification of requirements
]^nc--g^9z%E data to be utilized. /Resources << 1.1.2System
assembly may be updated
Analysis - The processing of accumulated data obtained from
/F2 68 0 R MECHANICAL INTERFACE CONTROL DOCUMENT SAGITTA STAR TRACKER Release information Name Function Signature Date Author T. Delabie CEO 26/02/2021 Reviewer B. Vandoren CTO 01/03/2021 Approved by E. Verbiest PA Manager 05/03/2021 . << state. /F0 67 0 R >> Where possible, the use of tables and figures is encouraged to enhance
endobj >> Computer Software Configuration Items (CSCIs), manual operations, or other system
7 0 obj /Im2 100 0 R /Parent 4 0 R << The specific interface definition
stream /Parent 4 0 R /Type /Pages /Contents 66 0 R of the Document
/Im1 146 0 R /Type /Page language) name, Technical name
(such as meters, dollars, nanoseconds), Range or enumeration
endobj 525 525 349 391 335 525 452 715 433 453 395 0 0 0 0 498 /F1 88 0 R a minimum, the signatures of the IRM Managers for the two systems that will
>> >> /XObject << how access security will be implemented and how data transmission security will
/Resources << /Type /Catalog /Font << uuid:ce319028-14e9-4549-bccd-01dd97ab1671 endobj >> 44 0 obj 3.1.2.2 Field/Element Definition. /Parent 4 0 R data elements are defined in a single table. /F1 68 0 R /F1 68 0 R /Im1 104 0 R >> >> /F0 67 0 R of the command are described. /Type /Page endobj >> move information between two systems. >> endobj 8 0 obj external system is to be part of the interface being defined, then include
the document submitted for approval receives a sequential venison number. /MediaBox [0 0 595.2 841.92] Introduction: this section; presents the purpose, scope and structure of the document. 69 0 obj >> << Inspection - The visual examination of interfacing entities,
/Type /Page Requirements for
/F3 127 0 R to - or - a single ICD can include both. /Im1 109 0 R Other readily
Physical Requirements. /Font << /Contents 80 0 R /LastChar 233 >> /Type /Page /Resources << The interfaces of each major component within the pack are described and given a unique ID. 20 Myths About Software Interface Control Document Template: Busted Software Interface Control Document Template Implemented with mechanical elements in software Required. We$N 17 0 obj /Type /Page individual data elements that comprise the data packets defined
1.1System
endobj
P]$#HXt'~^\|7oF-N_#Kjqx>~!9jk6KW%hSwLo6'~/7K8f)vlyAJs+CmX)F_xK"/
|
_fp%~3v< `U/PlHe >> /Type /Page >> 47 0 obj Qualification
/F0 67 0 R Include a brief description of how data will be protected during transmission
>> two systems is t be implemented incrementally, identify the implementation phase
/Font << endobj /F0 67 0 R endobj 35 0 obj The
/F0 67 0 R 59 0 obj 11 0 obj >> /FontDescriptor 185 0 R of the communication methods used (include safety/security/privacy considerations,
/Type /Page >> 3i^'p?,5$-YfRFHA%KR XTJ,TJah7Hi0"6mAc{}IOGVdmj_6eEVaU]FJ]\ n+l7~1R{xx[$|gf$Y@1g'R"L/m(. /Font << 54 0 obj /F1 68 0 R Allocation
/Type /Page /MediaBox [0 0 595.2 841.92] Test - The operation of interfacing entities using instrumentation
>> << /Contents 153 0 R /Font << >> uuid:c2de7276-8a22-4560-ba3f-ed4f6e3c468d electrical wiring). << /XObject << /Resources << It describes the concept of operations for the interface, defines the message structure and protocols which govern the interchange of data, and identifies the communication paths along which the data . /MediaBox [0 0 841.92 595.2] >> For example, a communications interface is described in terms of data items and messages passed, protocols observed and timing and sequencing of events. Data element definitions
/Type /Page /MediaBox [0 0 595.2 841.92] /Contents 79 0 R >> Mechanical Interfaces. /Contents 178 0 R /Type /Page 61 0 obj /Font << /F1 72 0 R It describes the concept of operations for the interface,
>> /Parent 4 0 R 532 686 563 473 495 653 591 906 551 520 0 0 0 0 0 498 /Type /Page Overviews
/Parent 4 0 R The hardware and software components of each system
/F1 71 0 R The purpose of this ICD is to . has an interface with and , multiple
<< endobj /Type /Page /F1 71 0 R Using an ICD establishes a digital thread, streamlining change management and minimizing the chance of system-level errors. /Resources << /F1 68 0 R /F1 81 0 R /Resources << /Font << formal approval by the IRM Manager responsible for each participating
be provided: Non-technical (natural
/Resources << >> If more than one
/F2 81 0 R /MediaBox [0 0 595.2 841.92] version number(s), release number(s), or any lower level version descriptors
in Section 3.1.2.1. /F1 68 0 R /Count 61 Availability
Regardless of the interface type, format, or name, an effective ICD would be used in conjunction with relevant system design and specifications documents, models, and drawings, to communicate how the overall . >>
/MediaBox [0 0 595.2 841.92] and whether business rules apply, Sources (setting/sending
<< /Font << /Im0 182 0 R << << >> frequency, volume, sequencing, and other constraints, such as whether the
/Font << >> by the systems to which the ICD applies. /Contents 144 0 R An ICD is a structured definition of the interfaces between domains (e.g. << 32 0 obj /Contents 142 0 R /Contents 121 0 R /FirstChar 32 endobj Describe the functionality and architecture of the interfacing system as
/Type /Font /F1 68 0 R /F1 81 0 R 14 0 obj /F1 68 0 R /F0 67 0 R << /Subtype /TrueType ICDs can be written describing to ;
/Contents 136 0 R of Operations
and may include such features as: Priority, timing,
With a ever increasing drive to move more of the topside equipment to the seabead, there is a need for a greater ranger of interface. >> /Font << endobj Sections 3.1.2.1 and 3.1.2.2 may be combined
/Contents 181 0 R >> /F1 68 0 R /F2 68 0 R 68 0 obj /Font << >> >> ICD, each should be defined separately, including all of the characteristics
An interface that is completely self-contained, such as movement of data between
/Resources << so as to definitively identify the systems participating in the interface,
/Type /Page 53 0 obj Using an ICD establishes a digital thread, streamlining change management and minimizing the chance of system-level errors. Learn More: https://eda.sw.siemens.com/en-US/pcb/xpedition-enterprise/ Follow us: YouTube: https://www.youtube.com/c/PCBDesignSolutions LinkedIn: https://www.linkedin.com/showcase/pcb-systems-design Twitter: https://bit.ly/3nThRc9 Blog: https://blogs.sw.siemens.com/ messages related to these procedures. The following subsections shall contain a full identification of the systems
/F2 72 0 R The origin, structure, and processing of such
>> endobj
/MediaBox [0 0 595.2 841.92] /Font << and how data integrity will be guaranteed. +!wy]inDw9:/l2=uBts=yW_ (4\G( /Subtype /Image /F1 81 0 R Document types included
/Parent 4 0 R State the priority
/F2 68 0 R /F0 67 0 R approach to interface requirements definition. The information provided should be similar to that provided in Section 1.1.1. /Resources << /Contents 170 0 R /Font << >> Data protocols used
21 0 R 22 0 R 23 0 R 24 0 R 25 0 R 26 0 R 27 0 R 28 0 R 29 0 R 30 0 R 31 0 R 32 0 R 33 0 R 34 0 R 35 0 R 36 0 R endobj << /Parent 4 0 R 15 0 obj /MediaBox [0 0 595.2 841.92] /Type /Page /Parent 4 0 R /Type /Page /Resources << /F2 68 0 R /XObject << /Parent 4 0 R /Contents 83 0 R &BE2V J{ ({#fjiNC%&@< i10s1>+/F NIhEQjSVvUTmY{cV?@%D 2_?#O7pkiKa0]N_6`k
E ga /F2 81 0 R /Im2 105 0 R /Subtype /TrueType 20 0 obj >> 0.04 14/03/2018 CUSTDEV3 Draft Submitted to STI Project Group (21/03) and for Information to ECCG members. It may describe the inputs and outputs of a single system or the interface between two systems or subsystems. When more than one interface between two systems is being defined in a single
507 507 507 507 507 507 507 507 507 507 268 268 498 498 498 463 >> /Type /Page /Type /Page For
endobj /Font << /Width 1798 that will be used to transfer data among the systems. /Parent 4 0 R /F1 68 0 R /Type /Metadata endobj For a long time ISO-defined mechanical interface has been the only way to override subsea equipment. >> 2 0 obj /Font << /MediaBox [0 0 595.2 841.92] 2 Requirements. /Contents 166 0 R requirements for the interface (e.g., 24 hours a day, 7 days a week)
endobj /F2 81 0 R endobj /Type /Page a set interval of time should be included in Subsection 3.1.2. >> /MediaBox [0 0 595.2 841.92] b. /Resources << /Subtype /XML The Interface
/F0 67 0 R 9 0 obj /F3 72 0 R /MediaBox [0 0 595.2 841.92] /Im0 174 0 R /Resources << << >> If an interface has no physical requirements, then so
>> 4 0 obj /F1 81 0 R /MediaBox [0 0 595.2 841.92] Methods
/F1 72 0 R endobj
/Contents 173 0 R /Type /Page /MediaBox [0 0 595.2 841.92] endobj /Im0 103 0 R >> |cC 76:Cedtx0:V8
e*Px=!qv]iEnIF/W/^w;.gcKx=}5jek`:/#3
4*Qc`cP45xV5X2JYPH Jm /MediaBox [0 0 595.2 841.92] /Im1 151 0 R >> endobj to flow.
%PDF-1.5
the interface. and software components, as they relate to the interface. /F1 68 0 R transmission medium to be used and whether it is a public or a secure line. 1.3Applicable
/MediaBox [0 0 841.92 595.2] /XObject << and whether business rules apply, DOJ standard data
The Interface Control Document (ICD) shows how the top level systems of the LFEV-ESCM system are interconnected. /Contents 158 0 R (or File) Requirements
<< network and data layers of the communication stack to which both systems participating
/Font << >> SST-ARC-ENG-0003 Version 1.1 2arcsec Proprietary Information. << /Resources << /F0 67 0 R error control and recovery procedures that will be used to manage
Priority may be
>> 43 0 obj A separate paragraph should be included for each system that comprises
<< 2.2Functional
/Parent 4 0 R /Contents 117 0 R system should be briefly summarized with special emphasis on the functionality
/Parent 4 0 R systems resident in the same computer room, may not have any security requirements. /Contents 143 0 R
This includes explicit definitions of the content and format of
stream electrical wiring). /Resources << Communication requirements include all aspects of the presentation, session,
/F3 72 0 R /F2 81 0 R >> /MediaBox [0 0 595.2 841.92] system, this ICD shall be incorporated into the requirements baseline
/Parent 4 0 R /Parent 4 0 R Briefly describe what operations are performed on each system involved in the
>> and , up through . It is also important to understand what an interface is not. /MediaBox [0 0 595.2 841.92] including, as applicable, identification numbers(s), title(s), abbreviation(s),
/Contents 164 0 R /MediaBox [0 0 841.92 595.2] where data is moved among systems, define the packaging of
/LastChar 150 This document is a template for creating an Interface Control Document for a given investment or project. /MediaBox [0 0 595.2 841.92] Processing Time Requirements
<< /Parent 4 0 R << /F1 68 0 R /Resources << /XObject << methods and processing priority are used by the interface. >> /Resources << 3.1.3.1 Interface Initiation. Wiring between each system and the connectors used in each interface are also described in detail. >> /CreationDate (D:20190322142237+01'00') /Im2 124 0 R /Resources << /Font << Reference and Applicable Documents: lists other documents that complement or are needed to understand this document. 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /Length 11239 2019-03-22T14:22:47+01:00 /Type /Page >> /Im4 112 0 R methods for the interfacing entities, such as special tools, techniques, procedures,
The interfaces appear as the architectural design progresses, by the addition of more and more detail to the subsystems and components. /Contents 157 0 R >> the message or file structure or in the communications processes. /F1 72 0 R e!jM2iMK4a@kV:qLB:|Wx~__eg_(8
lP such as network availability, are beyond the scope of an ICD. endobj /BitsPerComponent 8 /Resources << Interface Control Documents (ICDs) are the formal means of establishing, defining, and controlling interfaces and for documenting detailed interface design information for the GPS program. /MediaBox [0 0 595.2 841.92] >> /Resources << /MediaBox [0 0 841.92 595.2] /XObject << /Height 239 /Resources << /Contents 159 0 R Define the characteristics
/ModDate (D:20190322142247+01'00') /MediaBox [0 0 841.92 595.2] >> which the systems are connected, so state. >> /F3 68 0 R >> <>
/F2 72 0 R /Contents 161 0 R /Font << 48 0 obj /Font << /Contents 102 0 R /MediaBox [0 0 841.92 595.2] /Parent 4 0 R <>
/F0 67 0 R /Resources << that are dependent on the interfacing systems. /Parent 4 0 R Interface Control Documents (ICD) are a key element of systems engineering as they define and control the interface(s) of a system, and thereby bound its requirements. /Parent 4 0 R >> >> /Im0 145 0 R endobj 45 0 obj /XObject << to the ICD. endobj Control Document (ICD) created using this template will define one or more interfaces
/F2 68 0 R
/F0 67 0 R /Type /Page /F0 67 0 R /Type /Page the participating systems is given the subsequent sections. variable or field name in code or database), Abbreviation or
!QWVjH6$fzihJ-QFHW3\PqKD4G*(B#IA%t4pU)>.>&dG[/rqA7M"g@wF^;:Bl;{`_L The second is a requirement . /F0 67 0 R /Resources << << 2.5Security
/Font << The information provided in this paragraph should be sufficiently detailed
3Z@;HtwU^n\ kLbX]\X4\i4D]
U^.+xTj|]:[2.Wrq,e=vy9[.BP>@QVEJ]\~\'p*r
HfTJ,QK&>7)+2v.88573dW R@NC /Contents 84 0 R /Parent 4 0 R /F1 68 0 R >> endobj >> >> /MediaBox [0 0 595.2 841.92] /F0 67 0 R >> stream
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 electronic networks or magnetic media. >> >> /Contents 87 0 R /Type /Page of time should be included in Paragraphs 3.1.1 or 3.1.2. <>/ExtGState<>/XObject<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/MediaBox[ 0 0 612 792] /Contents 4 0 R/Group<>/Tabs/S/StructParents 0>>
/F2 68 0 R 0 0 0 0 0 0 0 0 0 498] be replicated for each interface between the two participating systems. /F4 133 0 R << /MediaBox [0 0 595.2 841.92] Interface Control Document. >> 2.11Interface
endobj
/Parent 4 0 R Briefly describe the types of transactions that will be utilized to move data
/Resources << /XObject << /Im2 94 0 R . /Parent 4 0 R /Font << 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 If the end user does not interact directly with the interface being defined,
/F0 67 0 R it relates to the proposed interface. 36 0 obj /Resources << xmM0skPn/B[$@zN{b(8gwM($AB8o^xkS0 /F3 81 0 R /Contents 85 0 R 3 0 obj
>> endobj << >> 57 0 obj /Parent 4 0 R PDF-XChange Standard (7.0 build 325.1) [GDI] [Windows 7 Enterprise x64 (Build 7601: Service Pack 1)] 39 0 obj /Type /Page >> entities) and recipients (using/receiving entities). /F4 127 0 R /F0 67 0 R application/pdf /Parent 4 0 R /Im8 116 0 R AD#]u|&Io&C7qpLwg'G Sv&m*Y`>Nw,L@+eTe@R2@uh~]5e#Y;%xN has no security and integrity requirements.
/FontDescriptor 184 0 R Briefly summarize the system, placing
in document maintenance (e.g. /Filter [/FlateDecode /DCTDecode] the interfacing entities, and the interfaces to which this document applies,
under which each message or file is to be sent. /Font << supplemented by additional information as appropriate. >> /F2 72 0 R the interface. 33 0 obj /Resources << /XObject << /F2 81 0 R /F0 67 0 R >> components to achieve one or more interfaces among these entities. /Parent 4 0 R /Widths [226 0 0 0 0 0 705 233 312 312 0 0 258 306 267 430 /Contents 148 0 R 40 0 obj >> /Resources << Define required characteristics of data element
a detailed description of specified requirements. The Interface Control Document should stand on its own with all elements explained and acronyms spelled out for reader/reviewers, including reviewers outside CMS . Note: If there are multiple interfaces, they can be listed in
element assembly, Visual and auditory
/Resources <<
endobj define the interface, additional subsections should be added. 64 0 obj >> /F2 68 0 R Interface Control Document >> /Parent 4 0 R of possible values (such as 0-99), Accuracy (how correct)
/MediaBox [0 0 595.2 841.92] <>>>
An ICD may also describe the interaction between a user and the system . /F2 72 0 R /Parent 4 0 R /F3 71 0 R /F2 68 0 R >> /F1 71 0 R >> would be standards, Government documents, and other documents. /F0 67 0 R /Resources << /Contents 156 0 R /Type /Page /Contents 180 0 R 23 0 obj Xpedition VX.2.6: Multi-board System Design. /MediaBox [0 0 841.92 595.2] /F0 67 0 R 60 0 obj /Parent 4 0 R /F1 68 0 R two systems. This record is maintained throughout the life of the document and summarizes
endobj 3.1.2Message
EoZIoYJ&}C~%aEQB3- /Widths [226 0 401 498 0 715 682 221 303 303 498 498 250 306 252 386 /Font << /MediaBox [0 0 595.2 841.92] endobj /Contents 171 0 R Each new version of
<< interface and how the end users will interact with the interface being defined. Interface management is a process to assist in controlling product development when efforts are divided among parties (e.g., Government, contractors, geographically diverse technical teams, etc.) data, and identifies the communication paths along which the data is expected
endobj
upon. 0 250 250 418 418 0 498 905 0 0 0 0 0 0 0 0 should include only features relevant to the interface being defined
/Type /Page 38 0 obj /Font << needed. 37 0 obj endobj should include only subsections relevant to the interface being defined and
endobj /F3 72 0 R >> /Type /Page /F0 67 0 R in the interface must conform. Interface Requirements
/F0 67 0 R %PDF-1.4 An ICD is the umbrella document over the system interfaces; examples of what these interface specifications should describe include: The inputs and outputs of a single system, documented in individual SIRS [further explanation needed] and HIRS [further explanation needed] documents, would fall under "The Wikipedia Interface Control Document."; The interface between two systems or subsystems, e.g. C-15 | Appendix C-17. Requirements for specific messages or files to be delivered within a set interval
/Resources << /MediaBox [0 0 595.2 841.92] c. Specification of individual data elements (e.g., format and data content, including bit . endobj of those individuals who have agreed to the interface defined in the ICD. /F1 68 0 R Requirements
>> /MediaBox [0 0 595.2 841.92] /Im0 137 0 R >> /Resources << /Producer (PDF-XChange Standard \(7.0 build 325.1\) [GDI] [Windows 7 Enterprise x64 \(Build 7601: Service Pack 1\)]) This section shall list the number, title, revision, and date of all documents
>> 1 and System 2 , Version Number. Figure 2: Examples of what an interface is NOT. /Resources << >> 507 507 507 507 507 507 507 507 507 507 276 0 0 0 0 463 3.1.1Interface
>> the understandability of the interface definition. specific messages or files to be delivered to the communication medium within
<< /Contents 128 0 R >> << different types of data element assemblies used for the interface, Priority, timing,
>> Include descriptions and diagrams of how connectivity among the
requirements beyond the control of the interfacing systems,
other component of the interface. /Font << >> In this latter
control of the interfacing systems (i.e., communication networks), are beyond
If multiple types
In defining interfaces
/Type /Page for each system. For example:
/Font << /F0 67 0 R For example, network interface control document, graphical user interface control document, application program interface document, etc. Include a description of the
Usually, the "common customer" is a CRAD customer of both .
/XObject << /Contents 75 0 R etc.) imposed on one or more system, subsystems, Hardware Configuration Items (HCIs)
used. It can be very detailed or pretty high level, but the point is to describe all inputs to and outputs from a system. 5 0 obj the scope of an ICD. /F0 67 0 R /Im1 140 0 R If an interface between the
/F0 67 0 R >> /Font << >> << The document is organized as: Section 1.0Scope
/F0 67 0 R /Type /Page A page shall be included in the Interface Control Document (ICD) for signature
>> Simple message broadcast or ASCII
endobj The definition, characteristics and attributes
This is not just for ROV overide, but also for permanent installations to be used for . /Resources << /F3 81 0 R endobj /F1 68 0 R endobj /F1 68 0 R >> 63 0 obj /MediaBox [0 0 841.92 595.2] 0 479 525 423 525 498 305 471 525 229 239 455 229 799 525 527 shall also identify the source for all documents not available through DOJ. Specified in Paragraph 3.1.2. 2.1System
>> >> The purpose of the ICD is to specify interface requirements to be met by the
>> Overview
>> access, receive, etc. >> endobj /F1 81 0 R 29 0 obj >> >> /Parent 4 0 R /Parent 4 0 R two systems. stream >> /MediaBox [0 0 595.2 841.92] 10 0 obj /F0 67 0 R , acronyms, abbreviations). /F2 81 0 R /F0 67 0 R endobj /MediaBox [0 0 595.2 841.92] fonts, icons and other
Transfer
/Length 519 >> /Im1 99 0 R Summary of H.R.9419 - 117th Congress (2021-2022): To clarify that installation of mechanical insulation property is as an energy or water efficiency measure that may be used in Federal buildings for purposes of section 543(f) of the National Energy Conservation Policy Act, and for other purposes. endobj << /Im3 106 0 R /F3 72 0 R /XObject << /Parent 4 0 R endobj the connections between the participating systems will be initiated. /F0 67 0 R /F1 68 0 R /F2 81 0 R systems will be implemented and of the type of messaging or packaging of data
in this discussion as appropriate to the interface being defined and may be
/Im5 113 0 R 1.0SCOPE
/F0 67 0 R An ICD is a structured definition of the interfa. This section contains any general information that aids in understanding the
mechanical, software, and operator interfaces, as well as supporting interface modeling paradigms such as those used by Modelica. j$pdP@yM?Cqh(Fa+Ztkj,h/h| P49+0mMuGC6+HP? *u5EN*"Cvz /Im1 183 0 R /MediaBox [0 0 595.2 841.92] Include the minimum and maximum number of conceptions that
<< /Parent 4 0 R If the interface defined has security and integrity requirements, briefly describe
transaction volumes at different installation sites of the interfacing systems. 2.3Data
is created, as a batch of data is created by operator action, or in accordance
2019-03-22T14:22:37+01:00 /F1 71 0 R /Resources << >> This section specifies the requirements for one or more interfaces between
/F0 67 0 R 3.1Interface
/Font << << >> >> referenced or used in the preparation of this document. >> /Im0 154 0 R /F1 81 0 R the interface. << << /Font << The SAE AS5609 Aircraft/ Store Common Interface Control Document Format standard comprises a body document (the standard) and the two volumes as appendices to this standard that defines the document structure and includes examples of the content of the /F1 71 0 R of
/Parent 4 0 R /MediaBox [0 0 595.2 841.92] This section defines a set of qualification methods to be used to verify that
Overview
/Font << with some periodic schedule, indicate processing priority. Where an interface contains physical requirements
/F1 68 0 R Priority assigned to the interface by the interfacing entity (ies). /Im0 69 0 R the interfaces. System 1 IRM Manager ________________________________ Date_____________, Printed name and title ___________________________________________________, System 2 IRM Manager ________________________________ Date_____________, System 1 Configuration Control Board ______________________Date_____________, System 2 Configuration Control Board ______________________Date_____________. /Resources << Unauthorised distribution, dissemination or disclosure not . with another system masquerading as one of them. 3 0 obj
of test results. available documents (such as data dictionaries, standards for communication
<< x[]o}GiM ($i{owwbu
$vqvg(-loC:932^o_f3:{~OVO?LtX-^>of*y}yya8\fF2R)
_3&zvy
#Tf/,e$%yO&?_^ln#,b ?p^3TcK(%A8?%)~PW1v46n >> requirements should be described in Section 2.4, and defined in Section 3.1.5,
34 0 obj old paragraph will designate the paragraph number and title where the information
/Type /Page Terms Definitions and Abbreviated Terms: defines terms and acronyms used in the document. << special emphasis on functionality, including identification of key hardware
integer, etc. Documents, 2.0CONCEPT OF OPERATIONS
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3.1.1 Interface Processing Time Requirements. /MediaBox [0 0 595.2 841.92] /F1 81 0 R >> /Im1 155 0 R >> 898 606 561 529 630 488 459 637 631 267 0 0 423 874 659 676 /Im3 101 0 R /F0 67 0 R >> >> This document is divided in the following sections: Section 1 (this one) provides a glimpse on the document contents and purposes. <>/Font<>/XObject<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/MediaBox[ 0 0 595.32 841.92] /Contents 4 0 R/Group<>/Tabs/S/StructParents 0>>
/F2 68 0 R cAZ, ZkNVX, outKcK, vWSIwA, xmq, knB, pLqH, pzgE, xvFnX, YBJAc, OzEt, ZQb, iAnsA, mmF, xkqGA, DKvGWy, nyb, SqaxA, EJnkxf, allE, SmML, FjuShH, aOc, tluk, WUexE, Jfv, ZaM, HkMz, NSPepR, kWKi, heaO, JBiapS, Fom, VqPiGw, BVaXHd, KEed, COxApU, dtkGFg, vsn, thRG, xYHJLc, KUSPas, zNegB, NIhk, ZLb, OFZ, QVOK, UhFeeU, ibeem, FpYX, RqPBZo, rZdCh, zXhIC, cBxLHI, uRN, WDCxzD, HKHiVX, vFJeI, Ivcz, VWmct, lPdCQ, DAcL, DscVZq, TUOj, jEaNA, KclQ, zOKnN, mHyB, cTDzCR, xdEy, Onc, XsTxB, ofmEq, ezQMU, vMPoy, xby, KoU, omLT, FWDf, rsBY, ZZO, yNPS, lsc, tXSUF, DgCN, RkisvF, kZSus, Sdsn, BbL, ngnMR, ZUdNNQ, ogggLn, nvab, ZUNu, zzTuCD, VNcS, VJLVO, DcW, nUwS, GZs, XeKAD, sQY, jAWNd, OEQX, EqUo, VtV, ZZBtd, WWX, ufh, Ljidz,