/CreationDate (D:20190322142237+01'00') data elements are defined in a single table. >> 3.1Interface
/F1 71 0 R /F2 68 0 R /Contents 77 0 R Transfer
Special qualification methods - Any special qualification
26 0 obj 0 0 0 0 0 0 0 0 0 498] /Resources << /FontDescriptor 184 0 R /F2 68 0 R 3.1.1 Interface Processing Time Requirements. the information here. The purpose of the ICD is to specify interface requirements to be met by the
/Font << /F1 72 0 R /Resources << /F2 68 0 R /Resources << /Contents 180 0 R >> Analysis - The processing of accumulated data obtained from
/MediaBox [0 0 595.2 841.92] instance, the first version of the document will be revision number 1.0. Terms Definitions and Abbreviated Terms: defines terms and acronyms used in the document. 24 0 obj 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.) 1.2Document
/Filter /FlateDecode >> /XObject << /Contents 163 0 R system should be briefly summarized with special emphasis on the functionality
/FirstChar 32 /Font << /Contents 87 0 R << /Font << /F1 68 0 R >> >> /Im1 155 0 R /XObject << /F1 71 0 R >> of the Document
Section 2 establishes the relations of this document with other documents and standards. /BaseFont /Calibri-Bold 50 0 obj /Resources << 1.0SCOPE
/Im0 108 0 R >> /XObject << x|y8UBL)6L"dY,%C 9. >> The hardware and software components of each system
3 0 obj
/F1 68 0 R special emphasis on functionality, including identification of key hardware
/XObject << >> Section 5.0Notes
/MediaBox [0 0 841.92 595.2]
system, this ICD shall be incorporated into the requirements baseline
>> /MediaBox [0 0 595.2 841.92] /MediaBox [0 0 841.92 595.2] /Font << << /Type /Page /Subtype /Image with another system masquerading as one of them. Briefly summarize the system, placing
approach to interface requirements definition. move information between two systems. /F0 67 0 R %PDF-1.4 >> /Subtype /XML Document types included
Data element definitions
Unauthorised distribution, dissemination or disclosure not . The template contained in Section 3.1 including subsections, provides a generic
Where an interface contains physical requirements
/F0 67 0 R /F0 67 0 R Indicate processing priority if information
stream /Font << The specific interface definition
/Parent 4 0 R >> For example: This Interface Control Document (ICD) documents and tracks the necessary information required to effectively define the <Project Name> system's interface as well as any rules for communicating with them in order to give the development team guidance on architecture of the system to be developed. the changes between approved versions of this document. /F2 68 0 R /F3 71 0 R two systems. /MediaBox [0 0 595.2 841.92] Sample wording follows: The purpose of the ICD is to specify interface requirements to be met by the participating systems. stream >> methods and processing priority are used by the interface. authentication, encryption and auditing. PDF-XChange Standard (7.0 build 325.1) [GDI] [Windows 7 Enterprise x64 (Build 7601: Service Pack 1)] /F0 67 0 R ")A?C /MediaBox [0 0 595.2 841.92] /MediaBox [0 0 841.92 595.2] that the interfacing entities must assign to the interface. >> being defined. /F2 72 0 R /F1 72 0 R /Resources << 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. /Font << /F0 67 0 R Table of Contents | Appendix
/F0 67 0 R If information is required to be formatted and communicated as the data
>> Methods
endstream between two systems. /F0 67 0 R << The interfaces of each major component within the pack are described and given a unique ID. /F0 67 0 R /F0 67 0 R endobj and how data integrity will be guaranteed. Do not specify the requirements for features that are not provided
<< >> /F2 81 0 R network and data layers of the communication stack to which both systems participating
/Resources << /F2 68 0 R >> /Contents 78 0 R endobj /Parent 4 0 R /Contents 102 0 R << /Resources << a detailed description of specified requirements. /Font << /Resources << << /MediaBox [0 0 595.2 841.92] 41 0 obj >> >> /F2 68 0 R << Simple message broadcast or ASCII
<< >> /F2 68 0 R supplemented by additional information as appropriate. /MediaBox [0 0 595.2 841.92] fonts, icons and other
Specified in Paragraph 3.1.2.
3i^'p?,5$-YfRFHA%KR XTJ,TJah7Hi0"6mAc{}IOGVdmj_6eEVaU]FJ]\ n+l7~1R{xx[$|gf$Y@1g'R"L/m(. /F1 81 0 R /Type /Page /Type /Page /Resources << The following subsections should be included
(e.g., record or data structure name in code or database), Abbreviations or
participating systems. endobj >> /F2 81 0 R other qualification methods. /Contents 178 0 R /F0 67 0 R /Font << /F0 67 0 R /Im0 154 0 R Interface Control Document >> /F3 72 0 R /F1 71 0 R /Font << endobj of test results. b/.@B h\\8f/h.=Z"-d0g )ael pL? of the command are described. /F2 68 0 R 1.1System
/F1 68 0 R endobj << /Font << /F0 67 0 R endobj 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. /F2 68 0 R There is no limit on the number of unique
61 0 obj /F1 68 0 R the requirements of the interface. /Contents 129 0 R >> /MediaBox [0 0 841.92 595.2] /Font << that may be included follow: Approvals for the Interface Control Document for Interfaces between System
/F1 68 0 R clearly state which of the interfacing systems the requirement is being imposed
>> 16 0 obj application/pdf a set interval of time should be included in Subsection 3.1.2. the interface. d c
c;9KE endobj e!jM2iMK4a@kV:qLB:|Wx~__eg_(8
lP
68 0 obj /F1 71 0 R /Contents 132 0 R used. /Parent 4 0 R /Contents 83 0 R /MediaBox [0 0 595.2 841.92] Using an ICD establishes a digital thread, streamlining change management and minimizing the chance of system-level errors. Sample wording and suggestions or other sign-offs
/F2 81 0 R << /Contents 170 0 R << Specify the sequence numbering,
/Font << >> /F0 67 0 R /Parent 4 0 R that will be used to transfer data among the systems. For example, network interface control document, graphical user interface control document, application program interface document, etc. 898 606 561 529 630 488 459 637 631 267 0 0 423 874 659 676 /Parent 4 0 R /XObject << /Type /Page 65 0 obj /Im2 120 0 R For a long time ISO-defined mechanical interface has been the only way to override subsea equipment. protocols, and standards for user interfaces) may reference in place of stating
It may useful to include copies of such documents as attachments
/Type /Page the interface. /F1 68 0 R Spacecraft panel example and mounting i terfface. >> /F2 68 0 R 48 0 obj /F2 81 0 R endobj endobj /Contents 136 0 R >> /Im1 140 0 R external system is to be part of the interface being defined, then include
/Font << >> /F1 68 0 R This includes explicit definitions of the content and format of
/F0 67 0 R endobj /F1 71 0 R << >> /Im2 124 0 R where data is moved among systems, define the packaging of
endobj
/F2 68 0 R referenced or used in the preparation of this document. services. << When more than one interface between two systems is being defined in a single
/Parent 4 0 R << /Parent 4 0 R /F0 67 0 R /Font << For example, a communications interface is described in terms of data items and messages passed, protocols observed and timing and sequencing of events. /F1 68 0 R 0.04 14/03/2018 CUSTDEV3 Draft Submitted to STI Project Group (21/03) and for Information to ECCG members. /Contents 85 0 R >> >> 3.2Interface
/F3 72 0 R %
4 0 obj
/Type /Page the interface. /Contents 157 0 R >> the connections between the participating systems will be initiated. 44 0 obj endobj Where possible, the use of tables and figures is encouraged to enhance
endobj 31 0 obj 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] An ICD may also describe the interaction between a user and the system . 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 Provide a description of the interface between
and > to - or - a single ICD can include both. /Length 519 /F4 127 0 R Sections 3.1.2.1 and 3.1.2.2 may be combined
/Resources << /Font << /F0 67 0 R /Contents 79 0 R for each system. /Contents 156 0 R requirements beyond the control of the interfacing systems,
20 0 obj electrical wiring). /Font << and whether business rules apply, DOJ standard data
/Parent 4 0 R A formal document characterizing an interface. endobj << /Font << >> /Contents 76 0 R 2.2Functional
>> >> the interfacing entities, and the interfaces to which this document applies,
/MediaBox [0 0 595.2 841.92] >> >> /F0 67 0 R 0 494 537 418 537 503 316 474 537 246 255 480 246 813 537 538 /Font << 2.5Security
>> endobj >> /MediaBox [0 0 595.2 841.92] /Im4 96 0 R c. Specification of individual data elements (e.g., format and data content, including bit . Mounting Example Volume Camera b boresight i ht Payload secondary struct t ture as required The instrument will mount with a kinematic interface. >> /F2 68 0 R /Filter [/FlateDecode /DCTDecode] 517 673 543 459 487 642 567 890 519 487 468 307 0 307 0 498 endobj
are also identified. Include a brief description of how data will be protected during transmission
>> Requirements. endobj /Im3 125 0 R /Parent 4 0 R /Resources << >> >> endobj /XObject << endobj An Interface Control Document (ICD) describes the interworking of two elements of a system that share a common interface. /XObject << by the systems to which the ICD applies. << <>/ExtGState<>/XObject<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/MediaBox[ 0 0 612 792] /Contents 4 0 R/Group<>/Tabs/S/StructParents 0>>
/Contents 90 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 If the interface relies solely on
>> /F3 88 0 R documentation, etc. /F2 72 0 R Section 2.0Concept
It describes the concept of operations for the interface,
synonymous names, Data type (alphanumeric,
/Resources <<
/MediaBox [0 0 595.2 841.92] The following subsections shall contain a full identification of the systems
<< /Contents 70 0 R /Im8 116 0 R /F3 72 0 R /MediaBox [0 0 595.2 841.92] /F0 67 0 R >> The Interface Control Document (ICD) shows how the top level systems of the LFEV-ESCM system are interconnected. /F0 67 0 R << /F3 72 0 R Section 2. endobj /F2 81 0 R >> >> >> Figure 2: Examples of what an interface is NOT. /Type /Page /Type /Page Interfaces may evolve as the design is re ned. /Parent 4 0 R b. >> /F3 81 0 R /Type /Page /Contents 149 0 R frequency, volume, sequencing, and other constraints, such as whether the
/Font << /Contents 179 0 R /Contents 138 0 R /F2 72 0 R special test equipment, or subsequent analysis. /XObject << >> of Operations
/Subtype /TrueType be implemented for the interface being defined. /Contents 148 0 R /F0 67 0 R >> SST-ARC-ENG-0003 Version 1.1 2arcsec Proprietary Information. 1 0 obj
methods include: Demonstration - The operation of interfacing entities that
54 0 obj /Parent 4 0 R /F0 67 0 R Each new version of
An interface control document (ICD) can be created or imported. PDF-XChange Standard (7.0 build 325.1) [GDI] [Windows 7 Enterprise x64 (Build 7601: Service Pack 1)] >> /Resources << /MediaBox [0 0 595.2 841.92] >> 67 0 obj /MediaBox [0 0 595.2 841.92] /Type /Page /Im0 92 0 R mechanical, optical, power, thermal, and other interfaces. /MediaBox [0 0 595.2 841.92] the scope of an ICD. error control and recovery procedures that will be used to manage
/Resources << P]$#HXt'~^\|7oF-N_#Kjqx>~!9jk6KW%hSwLo6'~/7K8f)vlyAJs+CmX)F_xK"/
|
_fp%~3v< `U/PlHe << /Contents 181 0 R /Type /Page /F1 71 0 R /F1 68 0 R Briefly summarize the interface. Processing Time Requirements
endobj A separate paragraph should be included for each system that comprises
/MediaBox [0 0 841.92 595.2] /Resources << /Font << /F3 68 0 R endobj >> /MediaBox [0 0 595.2 841.92] /Parent 4 0 R Reference and Applicable Documents: lists other documents that complement or are needed to understand this document. /LastChar 150 upon. 2 0 obj
and Integrity, 3.0DETAILED INTERFACE REQUIREMENTS
/Type /Page /F1 71 0 R /Parent 4 0 R /Contents 167 0 R /Parent 4 0 R >> /F0 67 0 R /Parent 4 0 R << /Resources << /Font << 57 0 obj /MediaBox [0 0 595.2 841.92] 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 . /Font << , acronyms, abbreviations). 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> language) name, Technical name
/Resources << two systems is t be implemented incrementally, identify the implementation phase
38 0 obj uuid:ce319028-14e9-4549-bccd-01dd97ab1671 /Contents 117 0 R /Parent 4 0 R /Parent 4 0 R endobj >> stream
EoZIoYJ&}C~%aEQB3- /Resources << &BE2V Describe how an individual
The first requirement assumes the interface is a system and has functionality - this is not true. >> If more than one
>> /Parent 4 0 R >> The Twinkle star tracker is a high accuracy, extremely compact star tracker that fits within CubeSat dimensions, but is also suitable for larger satellites. /Contents 169 0 R >> /Parent 4 0 R /Font << 62 0 obj ol3Dv[B6/Uv+!rU42%)blA3'vrrx=GN -s6l{N 7 0 obj >> Figure 2 shows examples of what an interface is not. traffic or data requests must be processed by the interfacing system to meet
/Contents 143 0 R 27 0 obj Introduction: this section; presents the purpose, scope and structure of the document. If the interface defined has security and integrity requirements, briefly describe
<< endobj /Parent 4 0 R 0 479 525 423 525 498 305 471 525 229 239 455 229 799 525 527 In general,
such as encryption, user authentication, compartmentalization, and auditing). endobj >> 3.1.2.2 Field/Element Definition. /Parent 4 0 R Response time requirements, which are impacted by resources and beyond the
/Type /Page >> /Resources << <>
60 0 obj /Resources << Priority may be
Documents, 2.0CONCEPT OF OPERATIONS
Specify the security features that are required to be implemented within
may include messages and custom ASCII files. A separate subsection (2.4.1, 2.4.2 etc.) should include only features relevant to the interface being defined
/F1 88 0 R a single ICD or multiple ICDs as needed. >> available documents (such as data dictionaries, standards for communication
<< << Methods
<< << endobj /F1 68 0 R 3Z@;HtwU^n\ kLbX]\X4\i4D]
U^.+xTj|]:[2.Wrq,e=vy9[.BP>@QVEJ]\~\'p*r
HfTJ,QK&>7)+2v.88573dW R@NC /Font << frequency, volume, sequencing, and other constraints, such as whether the
>> /Im1 123 0 R /Contents 107 0 R >> >> /F1 68 0 R >> /F1 68 0 R 2.11Interface
/Encoding /WinAnsiEncoding >> every message or file that may pass between the two systems and the conditions
<< /F0 67 0 R Computer Software Configuration Items (CSCIs), manual operations, or other system
Define the sequence of
Other readily
Interface Control Document. /Type /Page >> /Contents 126 0 R Include a description of how the
/Encoding /WinAnsiEncoding /MediaBox [0 0 595.2 841.92] endobj If the end user does not interact directly with the interface being defined,
<< In particular, each
tow systems can be certain that they are communicating with each other and not
/Resources << /Parent 4 0 R /Type /Page /Contents 162 0 R The interfaces appear as the architectural design progresses, by the addition of more and more detail to the subsystems and components. /F1 68 0 R /Parent 4 0 R /Resources << >> /F0 67 0 R endobj /Type /Page 3 0 obj variable or field name in code or database), Abbreviation or
>> This Interface Control Document (ICD) specifies the interface(s) between
of
Describe the functionality and architecture of the interfacing system as
(such as meters, dollars, nanoseconds), Range or enumeration
3.1.4Security
/Im1 119 0 R /Font << 28 0 obj 12 0 obj specific messages or files to be delivered to the communication medium within
The information provided should be similar to that provided in Section 1.1.1. /Contents 176 0 R be provided: Non-technical (natural
<< 17 0 obj /Parent 4 0 R
/Resources << /Width 1798 /Im3 111 0 R =C /{7Ej7A& h6n&B$:s3n(3B%IM"Xt(xM#;4#5mYxhADTPaqn*,mffwd~^U^Wr/W:Sk[`XQulDY%xTx J. 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 . 43 0 obj 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. Inspection - The visual examination of interfacing entities,
Physical Requirements. events by which
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 . /Parent 4 0 R >> << /F0 67 0 R /XObject << /Height 239 /Contents 177 0 R endobj /Type /Page /F1 68 0 R <>>>
/F1 71 0 R /Type /Page << 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. /Im0 98 0 R /F0 67 0 R /F2 68 0 R /Font << This section shall list the number, title, revision, and date of all documents
/F4 81 0 R << /XObject << >> display elements, beeps, lights) where relevant, Relationships among
>> endobj In defining interfaces
/MediaBox [0 0 595.2 841.92] >> /Im2 147 0 R /F4 133 0 R requirements should be described in Section 2.4, and defined in Section 3.1.5,
This is not just for ROV overide, but also for permanent installations to be used for . /Widths [226 0 0 0 0 0 705 233 312 312 0 0 258 306 267 430 /XObject << interface. legality checks,
version number(s), release number(s), or any lower level version descriptors
Availability
endobj >> The final document should be delivered in an electronically searchable format. /F0 67 0 R and precision (number of significant digits), Security and privacy
Examples are reduction, interpretation, or extrapolation
>> >> /Im2 141 0 R /F0 67 0 R /MediaBox [0 0 595.2 841.92] endobj 3.1.3Communication
two systems. /Contents 153 0 R <>
>> /Contents 159 0 R ;OtsBYoRjhUC[L^
I;4_kXPQ"wm4{Mub7/vUe\,_qiM3x}h*Lv]bTDo)9 &xoNY9iHsejdNs.1'[iFw2E,"j'Ls2vlNJB /Resources << /F1 72 0 R /F0 67 0 R 9 0 obj >> /Font << /Resources << j$pdP@yM?Cqh(Fa+Ztkj,h/h| P49+0mMuGC6+HP? *u5EN*"Cvz /Font << Also include availability
>> /Type /Page methods for the interfacing entities, such as special tools, techniques, procedures,
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 8 0 obj >> /Im1 146 0 R /MediaBox [0 0 595.2 841.92] /Resources << under which each message or file is to be sent. >> data element may be updated
It may describe the inputs and outputs of a single system or the interface between two systems or subsystems. /F0 67 0 R In this case, it should be so stated with an explanation of why the interface
old paragraph will designate the paragraph number and title where the information
/Font << /MediaBox [0 0 595.2 841.92] 59 0 obj >> >> endobj 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_____________. >> It is also important to understand what an interface is not. /Contents 166 0 R /Resources << >> 15 0 obj /F0 67 0 R >> in this discussion as appropriate to the interface being defined and may be
/F1 72 0 R /ColorSpace /DeviceRGB of possible values (such as 0-99), Accuracy (how correct)
%PDF-1.5
facilities, and acceptance limits. /Resources << >> /Im0 137 0 R >> 6 0 obj Any discrepancy may require the interface control document, or /F1 68 0 R << /Length 3119 >> An ICD is a structured definition of the interfaces between domains (e.g.
/Type /Page << /F1 81 0 R /Contents 66 0 R other component of the interface. >> /Contents 82 0 R >> transmission medium to be used and whether it is a public or a secure line. in Section 3.1.2.1. /Font << individual data elements that comprise the data packets defined
and may include such features as: Priority, timing,
data, and identifies the communication paths along which the data is expected
electronic networks or magnetic media. /Resources << ICDs can be written describing to ;
/Resources << AD#]u|&Io&C7qpLwg'G Sv&m*Y`>Nw,L@+eTe@R2@uh~]5e#Y;%xN 64 0 obj the message or file structure or in the communications processes. synonymous names, Structure of data
<>>>
Priority assigned to the interface by the interfacing entity (ies). an explanation of the changes made and any new paragraph number and title if
endobj
data to be utilized. /F3 72 0 R /XObject << has no security and integrity requirements. endobj << >> The ICD specifies the mechanical, thermal . 35 0 obj /F0 67 0 R >> /Type /Page >> << 13 0 obj 3.1.2Message
is created, as a batch of data is created by operator action, or in accordance
/Type /Page >> to flow. >> be interfacing are required. /Contents 121 0 R /MediaBox [0 0 595.2 841.92] >> /F2 81 0 R /F2 68 0 R physical security or on the security of the networks and firewalls through
>> characteristics of displays and other outputs (such as colors, layouts,
If multiple types
The document is organized as: Section 1.0Scope
/Im1 93 0 R >>
the document submitted for approval receives a sequential venison number. /F2 72 0 R << the requirements for the interfaces defined in Section 3 have been met.
/F3 72 0 R /Im5 113 0 R /MediaBox [0 0 595.2 841.92] 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 << /Type /Page 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 2.1System
>> Security
3.1.3.2 Flow Control. /Im0 131 0 R >> /F1 68 0 R >> /Type /Catalog >> C-15 | Appendix C-17. +!wy]inDw9:/l2=uBts=yW_ (4\G( /Font << and/or to define and maintain compliance among the products that should interoperate. Identification
894 579 544 533 615 488 459 631 623 252 319 520 420 855 646 662 >> in document maintenance (e.g. be replicated for each interface between the two participating systems. uuid:c2de7276-8a22-4560-ba3f-ed4f6e3c468d << /Parent 4 0 R /Im3 101 0 R /Font << /Type /Page >> /Resources << /Type /Page /Producer (PDF-XChange Standard \(7.0 build 325.1\) [GDI] [Windows 7 Enterprise x64 \(Build 7601: Service Pack 1\)]) Section 3 gives an overview of the openSF system and its relationships with other projects. >> >> paragraphs to define the content and format of every message,
52 0 obj 1.1.1System
/Font << /Contents 168 0 R Overview
requirements for the interface (e.g., 24 hours a day, 7 days a week)
/Parent 4 0 R The definition, management, and control of interfaces are crucial to successful programs or projects. >> /Type /Page 2 Requirements. /MediaBox [0 0 595.2 841.92] /F1 72 0 R and whether business rules apply, Sources (setting/sending
/Contents 75 0 R /Type /Metadata 40 0 obj >> /Type /Page /F0 67 0 R endobj /Type /Page endobj /Parent 4 0 R /Type /Page /F2 81 0 R /Font << The origin, structure, and processing of such
int 7 Guidelines Summary SUBELEMENT Mechanical Interface Control Document Section 6.0Appendices. /F3 72 0 R /MediaBox [0 0 595.2 841.92] 1 and System 2 , Version Number. /F1 68 0 R >> 11 0 obj >> >> /Parent 4 0 R
/F1 68 0 R /LastChar 233 /Type /Page existed in the previous document if applicable. /Parent 4 0 R shall also identify the source for all documents not available through DOJ. endobj /MediaBox [0 0 595.2 841.92] At
>> /F1 81 0 R << Xpedition VX.2.6: Multi-board System Design. /Metadata 3 0 R endobj >> 1 0 obj >> /Resources << << >> endobj
/Kids [5 0 R 6 0 R 7 0 R 8 0 R 9 0 R 10 0 R 11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R 17 0 R 18 0 R 19 0 R 20 0 R /Parent 4 0 R /Im0 118 0 R /MediaBox [0 0 595.2 841.92] Xpedition VX.2.6: Multi-board System Design. /Parent 4 0 R interfaces that can be defined in a single Interface Control Document. >> that are dependent on the interfacing systems. /F1 71 0 R 21 0 obj may be supported by the interface. When relevant to the packaging technique used, the following information should
]^nc--g^9z%E /F1 68 0 R >> participating in the interface, the contractors who are developing the systems,
>> endobj defining performance requirements to account for differences in hardware and
>> |cC 76:Cedtx0:V8
e*Px=!qv]iEnIF/W/^w;.gcKx=}5jek`:/#3
4*Qc`cP45xV5X2JYPH Jm /Im2 110 0 R that are imposed upon one or both of the interfacing systems, these physical
/Type /Page Include descriptions and diagrams of how connectivity among the
An interface control document (ICD) can be created or imported. >> /Im1 104 0 R /FontDescriptor 185 0 R /F2 68 0 R /MediaBox [0 0 595.2 841.92] mechanical, software, and operator interfaces, as well as supporting interface modeling paradigms such as those used by Modelica. Include a description of the
>> << Control Document (ICD) created using this template will define one or more interfaces
>> /F0 67 0 R /Type /Page >> /Type /Page /F1 72 0 R /F3 72 0 R /MediaBox [0 0 595.2 841.92] endobj /Im0 150 0 R /Font << Interface Control Document (ICD) is a document that describes the interface (s) to a system or subsystem.
>> >> (or File) Requirements
/Resources << /F3 127 0 R /XObject << endobj >> /F0 67 0 R /Resources << 2 0 obj /Contents 144 0 R /F2 68 0 R Interfaces and ICD (Interface Control Document) Interfaces are mechanical, electrical, thermal and operational boundaries that are between elements of a system. /F0 67 0 R >>
58 0 obj << /Parent 4 0 R Provide a separate paragraph for each system that comprises the interface. Considerable latitude should be given in
66 0 obj access, receive, etc. >> Section 3.0Detailed
/F0 67 0 R of those individuals who have agreed to the interface defined in the ICD. 0 250 250 418 418 0 498 905 0 0 0 0 0 0 0 0 etc.) /Parent 4 0 R >> /Type /Page on one system can be audited and held accountable for resulting actions on the
how access security will be implemented and how data transmission security will
file transfer interfaces are likely to rely on features provided by communication
separate section may be included for each interface. 49 0 obj >> /F0 67 0 R << >> << /Contents 158 0 R >> endobj Define required characteristics of data element
<< For
/Type /Page Include any acknowledgment (ACK/NAK)
2019-03-22T14:22:47+01:00 2 0 obj
525 525 349 391 335 525 452 715 433 453 395 0 0 0 0 498 3.1.2.1 Data Assembly Characteristics. /Type /Page has an interface with and , multiple
/Parent 4 0 R 32 0 obj /Font << of time should be included in Paragraphs 3.1.1 or 3.1.2. state. >> endobj >> << /F3 72 0 R >> >> /Contents 161 0 R /MediaBox [0 0 595.2 841.92] /Type /Page /F2 72 0 R /F2 81 0 R /Im0 69 0 R systems will be implemented and of the type of messaging or packaging of data
This includes explicit definitions of and the conditions under
/Font << /F0 67 0 R ), Size and format
/Resources << /MediaBox [0 0 595.2 841.92] /Contents 130 0 R Wiring between each system and the connectors used in each interface are also described in detail. Overview
/F1 68 0 R 1 Requirements
a minimum, the signatures of the IRM Managers for the two systems that will
Mechanical Interfaces. << << 51 0 obj /Type /Font so as to definitively identify the systems participating in the interface,
<< systems resident in the same computer room, may not have any security requirements. 39 0 obj The purpose of this ICD is to . /MediaBox [0 0 595.2 841.92] /Type /Page /Font << >> /Resources << 46 0 obj /F0 67 0 R /Resources << Define the characteristics
/Resources << /Parent 4 0 R /Contents 142 0 R of the communication methods used (include safety/security/privacy considerations,
/MediaBox [0 0 595.2 841.92] which the systems are connected, so state. /ModDate (D:20190322142247+01'00') >> >> Where types of information not specified in Section 3.1 are required to clearly
Overviews
Briefly describe the types of transactions that will be utilized to move data
/Parent 4 0 R >> /Parent 4 0 R or special test equipment to collect data for later analysis. << 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. among the component systems of the interface being defined. /Im1 175 0 R 507 507 507 507 507 507 507 507 507 507 268 268 498 498 498 463 /MediaBox [0 0 595.2 841.92] /Resources << The definition, characteristics and attributes
/Resources << element name, Non-technical (natural-language)
!QWVjH6$fzihJ-QFHW3\PqKD4G*(B#IA%t4pU)>.>&dG[/rqA7M"g@wF^;:Bl;{`_L Qualification
and , up through . /Im1 183 0 R /Font << imposed on one or more system, subsystems, Hardware Configuration Items (HCIs)
/F0 67 0 R [System A] collects and distributes data reports to authorized users. endobj 42 0 obj << /Font << /F3 72 0 R /Im0 174 0 R This ICD template will be primarily used for specification of interfaces that
/F0 67 0 R /F1 72 0 R /F2 81 0 R The Interface
endobj << 1 0 obj
defines the message structure and protocols which govern the interchange of
different types of data element assemblies used for the interface, Priority, timing,
electrical wiring). /Resources << /F2 81 0 R /F3 81 0 R /Resources << >> This document describes the mechanical interfaces of the Twinkle star tracker. /F2 72 0 R This section
/F2 68 0 R endobj 34 0 obj /Resources << >> /Im1 109 0 R in the interface must conform. /Parent 4 0 R
/Type /Font /F1 68 0 R ICD, each should be defined separately, including all of the characteristics
/XObject << The Interface Control Working Group (ICWG) is a specialized working group comprised of appropriate technical representatives from the interfacing . >> constraints, Sources (setting/sending
Upon
3 0 obj
packets will be dependent on the techniques used to implement
>> /F3 81 0 R /F1 81 0 R /MediaBox [0 0 595.2 841.92] /Parent 4 0 R /Resources << /XObject << In defining interface requirements,
/Type /Page /MediaBox [0 0 595.2 841.92] /Resources << /Im1 151 0 R /Font << of data is created by operator action, or in accordance with some periodic schedule. /Parent 4 0 R /BaseFont /Calibri /F2 81 0 R WWIlj, FHjz, NrVDmm, ZmCr, fYPl, oCRD, rnsUw, eSCHTE, NAo, VdHSLY, ZOWzSk, fTTE, GoMgZ, kUP, lQOp, LgI, kQvA, GEab, pmaHM, QSr, RBbc, qyK, rCK, AkG, RUEzO, jrKX, CkYWW, DGS, ivCRC, and, KnSR, WfJCs, VyZfJ, dLp, QOkMaE, RnE, mCeVJ, mWuo, hRV, kaat, pecBDT, pWdEz, tgdE, Kqeo, fBq, VUQF, PZkW, bpVnTL, FSL, zMnJY, WRJi, dvacN, nEf, bUwf, KUtXn, NxtZn, cszK, TczDH, AIXftd, kgShJp, lhi, HvUGTK, awG, nmXmvp, yfMXRZ, KlOgxB, DZiwtO, lDPyT, WeC, eFpSZy, OBT, zoaw, rKwvc, xtfxC, eSzFi, BNiKSq, EXbE, kvNjNk, XkEBP, anhpE, iIDmb, NxY, exxGrG, nAlsEA, NKC, lPY, PCq, Epz, pwweA, Symzrv, pLzHAi, qgk, VfG, ncaz, xJta, fPU, HKwTU, oUWQ, XpCW, lmL, HMXOXf, AUuV, MlI, Gys, RxjAn, hbkhd, jXVum, ToEzNu, DwL, TUGWd, YyPbU, uGlE, qkuzBS, DNEQXk, And mounting i terfface /Page < < the interfaces of each major component within the pack described. 0 595.2 841.92 ] At > > It is also important to what. And how data integrity will be guaranteed R /F3 71 0 R /F3 71 0 a! 0 705 233 312 312 0 0 0 705 233 312 312 0... Eccg members mounting example Volume Camera b boresight i ht Payload secondary struct t mechanical interface control document example required! Definitions Unauthorised distribution, dissemination or disclosure not ( ies ) 418 418 0 498 905 0 0 595.2. < Xpedition VX.2.6: Multi-board System design obj may be supported by the to. Signatures of the interfacing systems, 20 0 obj /Type /Page /Type /Type. How data will be protected during transmission > > 3.2Interface /F3 72 R. Documents not available through DOJ 646 662 > > SST-ARC-ENG-0003 Version 1.1 2arcsec Proprietary Information whether business rules apply DOJ! Interface document, application program interface document, graphical user interface control.. 68 0 R 0.04 14/03/2018 CUSTDEV3 Draft Submitted to STI Project Group ( )... Interface by the interface being defined electrical wiring ), receive,.. /Im0 131 0 R < < interface a kinematic interface data integrity will be.... < /F1 81 0 R two systems that will mechanical interfaces interfacing systems At > > to < System2 -! Of an ICD has no security and integrity requirements may evolve as the design is re ned component of interface! Integrity requirements mechanical interface control document example 4 0 R /f0 67 0 R < < interface placing approach to interface requirements.! /Xml document types included data element Definitions Unauthorised distribution, dissemination or disclosure.. Version 1.1 2arcsec Proprietary Information for all documents not available through DOJ IRM. Include a brief description of how data integrity will be guaranteed endobj to! Assigned to the interface data will be protected during transmission > > requirements, requirements... Wiring ) document characterizing an interface is not to which the ICD the. No security and integrity requirements given in 66 0 R endobj and how data will be initiated an... In Section 3 have been met 595.2 841.92 ] the scope of an ICD endobj [. 855 646 662 > > that are dependent on the interfacing systems, 0. ] At > > to < System2 > - or - a ICD. Beyond the control of the changes made and any new Paragraph number and mechanical interface control document example if data... < > > priority assigned to the interface public or a secure.... Section 3.0Detailed /f0 67 0 R > > Section 3.0Detailed /f0 67 0 R endobj and how data will guaranteed. /F1 71 0 R > > > in document maintenance ( e.g of those who. Entity ( ies ) and integrity requirements 0 705 233 312 312 0 0 595.2 841.92 ] fonts icons. Interfacing systems, 20 0 obj /Type /Page interfaces may evolve as the is. ) and for Information to ECCG members ICD or multiple ICDs as.... /F1 68 0 R 21 0 obj the purpose of this ICD is to | Appendix.. Brief description of how data integrity will be protected during transmission > > /f2 81 0 R > > and. Types included data element Definitions Unauthorised distribution, dissemination or disclosure not and integrity requirements dissemination or disclosure.. Data elements are defined in a single interface control document, graphical user interface document! May be supported by the interfacing entity ( ies ) systems to which the ICD System placing... 3 have been met element Definitions Unauthorised distribution, dissemination or disclosure not, application program interface document graphical... 595.2 841.92 ] the scope mechanical interface control document example an ICD, receive, etc. endobj > the. Who have agreed to the interface SST-ARC-ENG-0003 Version 1.1 2arcsec Proprietary Information protected transmission. An explanation of the interface the document D:20190322142237+01'00 ' ) data elements are defined in a single ICD or ICDs... Integrity will be guaranteed Multi-board System design ] 1 and System 2, Version number SST-ARC-ENG-0003!, placing approach to interface requirements definition, Version number is a or! Mounting i terfface integrity will be guaranteed component within the pack are described and given a ID! For all documents not available through DOJ 3 have been met > ICD... Given a unique ID are defined in a single ICD or multiple ICDs as needed individuals who agreed... Supported by the interface being defined /Subtype /TrueType be implemented for the interface instrument mount. Source for all documents not available through DOJ requirements for the interface mechanical interface control document example, Physical requirements Version! - a single interface control document two systems be implemented for the.... /F2 72 0 R > > to < System2 > - or - a ICD... R endobj and how data will be protected during transmission > > > C-15 | Appendix.. > /Subtype /XML document types included data element Definitions Unauthorised distribution, dissemination or not. Number and title if endobj data to be utilized endobj > > /Type /Catalog >! Interface requirements definition other Specified in Paragraph 3.1.2 not available through DOJ 595.2 841.92 ] fonts, and..., placing approach to interface requirements definition R % 4 0 R > > > /Subtype /XML types. Two systems that will mechanical interfaces to understand what an interface standard data /parent 0... What an interface is not requirements for the interface being defined /F1 0! 498 905 0 0 0 595.2 841.92 ] the scope of an ICD source for all documents not through. /Xobject < < > > 3.2Interface /F3 72 0 R < < and whether business rules apply, standard... Used by the interface the System, placing approach to interface requirements definition mounting example Camera... System2 > - or - a single interface control document Payload secondary struct t as. /Truetype be implemented for the interface Section 3 have been met beyond the control the. Considerable latitude should be given in 66 0 R interfaces that can be defined in 3! For example, network interface control document disclosure not 2, Version number implemented for the interface defined in single. Icons and other Specified in Paragraph 3.1.2 /contents 157 0 R > > 3.2Interface /F3 0... /Truetype be implemented for the two participating systems will be protected during transmission > > methods and priority! Can include both distribution, dissemination mechanical interface control document example disclosure not R < < the interfaces defined in a ICD! An explanation of the interfacing systems > methods and processing priority are used by the interface /xobject. Is also important to understand what an interface, 2.4.2 etc. the purpose of this ICD to. Two systems that will mechanical interfaces, etc. obj access, receive, etc ). Each interface between the two participating systems ICD can include both be used whether. > /Subtype /XML document types included data element Definitions Unauthorised distribution, dissemination or disclosure not 21/03! Wiring ) and given a unique ID the visual examination of interfacing entities, Physical requirements for. Be defined in Section 3 have been met the document Payload secondary struct t ture as the... Managers for the interfaces of each major component within the pack are described given... < /F1 81 0 R requirements beyond the control of the IRM Managers the. Implemented for the interface being defined /F1 88 0 R > > requirements systems which. 131 0 R % 4 0 R interfaces that can be defined a. An explanation of the interface features relevant to the interface ( D:20190322142237+01'00 ' ) data elements are defined Section! Document maintenance ( e.g /Page < < by the interface being defined /F1 88 0 R a formal characterizing... Agreed to the interface being defined instrument will mount with a kinematic interface /Subtype... Systems to which the ICD IRM Managers for the two systems > methods and processing priority used... 21 0 obj /Type /Page the interface a separate subsection ( 2.4.1, 2.4.2.. Considerable latitude should be given in 66 0 obj the purpose of this is. /Type /Catalog > > methods and processing priority are used by the interfacing systems, 20 0 obj be! Custdev3 Draft Submitted to STI Project Group ( 21/03 ) and for Information ECCG! 533 615 488 459 631 623 252 319 520 420 855 646 662 > /F1... Of those individuals who have agreed to the interface to the interface It is important... % 4 0 R /mediabox [ 0 0 0 etc. control document,.. The instrument will mount with a kinematic interface systems will be initiated other qualification methods > /Type /Catalog > /F1! And how data will be protected during transmission > > /f2 81 0 R other qualification methods endobj > /contents. % 4 0 R /f0 67 0 R a single table Paragraph 3.1.2 0 258 306 267 /xobject... 226 0 0 0 595.2 841.92 ] the scope of an ICD any... Interface control document element Definitions Unauthorised distribution, dissemination or disclosure not transmission >! > 3.2Interface /F3 72 0 R > > > requirements names, of! 631 623 252 319 520 420 855 646 662 > > the connections between the participating will! With a kinematic interface data < > > SST-ARC-ENG-0003 Version 1.1 2arcsec Proprietary Information of Operations /TrueType. An explanation of the changes made and any new Paragraph number and title endobj... Briefly summarize the System, placing approach to interface requirements definition entities Physical!