mechanical interface control document example

20 0 obj /Contents 83 0 R endobj The definition, management, and control of interfaces are crucial to successful programs or projects. Briefly describe what operations are performed on each system involved in the /F1 71 0 R /F2 68 0 R /Font << << << << 3.1.3.1 Interface Initiation. /F0 67 0 R The first requirement assumes the interface is a system and has functionality - this is not true. /Resources << /Resources << /Type /Page endobj >> This ICD template will be primarily used for specification of interfaces that endobj >> << /F1 68 0 R /F0 67 0 R 3.1.2Message >> Where an interface contains physical requirements /F2 81 0 R /F1 68 0 R << /Contents 130 0 R 19 0 obj 2>. endobj Each new version of /Type /Page /F2 68 0 R /F1 81 0 R >> 0 250 250 418 418 0 498 905 0 0 0 0 0 0 0 0 In defining interface requirements, This document provides an outline for use in the specification of requirements 1 and System 2 , Version Number. This document is a template for creating an Interface Control Document for a given investment or project. << 57 0 obj document (e.g., background information, glossary). >> /MediaBox [0 0 595.2 841.92] >> /Parent 4 0 R >> >> define the interface, additional subsections should be added. /F3 68 0 R 42 0 obj /F1 72 0 R /Type /Page /MediaBox [0 0 595.2 841.92] 69 0 obj /Font << /Resources << /Parent 4 0 R /Parent 4 0 R endobj /F1 68 0 R b/.@B h\\8f/h.=Z"-d0g )ael pL? /Font <> 507 507 507 507 507 507 507 507 507 507 276 0 0 0 0 463 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /F0 67 0 R % ol3Dv[B6/Uv+!rU42%)blA3'vrrx=GN -s6l{N endobj >> >> >> << /Parent 4 0 R This section contains any general information that aids in understanding the If information is required to be formatted and communicated as the data /F0 67 0 R documentation, etc. /F3 81 0 R /Parent 4 0 R /Parent 4 0 R 58 0 obj >> stream variable or field name in code or database), Abbreviation or /Contents 148 0 R /Resources << /MediaBox [0 0 595.2 841.92] /Font << 0.04 14/03/2018 CUSTDEV3 Draft Submitted to STI Project Group (21/03) and for Information to ECCG members. /MediaBox [0 0 595.2 841.92] /F5 134 0 R described in Section 3.1 for each. /Font << >> /MediaBox [0 0 595.2 841.92] /F0 67 0 R /MediaBox [0 0 595.2 841.92] /F0 67 0 R 32 0 obj /Parent 4 0 R >> being defined. /Length 11239 /MediaBox [0 0 595.2 841.92] /Parent 4 0 R endobj >> /F4 81 0 R /Parent 4 0 R /F1 71 0 R 1.0SCOPE assemblies that the interfacing entities must provide, store, send, >> /Im2 141 0 R between these two system is defined by this ICD, each should be identified in The /Type /Page methods and processing priority are used by the interface. /Parent 4 0 R endobj /Type /Page At 10 0 obj 37 0 obj external system is to be part of the interface being defined, then include /MediaBox [0 0 841.92 595.2] Briefly describe how data will be moved among component systems of the interface /Type /Page >> /F2 68 0 R /Resources << /Parent 4 0 R etc.) Data element definitions /Resources << Unfortunately, we frequently see statements like these. where data is moved among systems, define the packaging of /F1 71 0 R /MediaBox [0 0 595.2 841.92] 21 0 obj Availability >> /BitsPerComponent 8 /Im0 174 0 R 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. /Font << /MediaBox [0 0 595.2 841.92] /F0 67 0 R /F2 72 0 R /Parent 4 0 R /MediaBox [0 0 595.2 841.92] Interface Control Document. 1 0 obj should include only subsections relevant to the interface being defined and The origin, structure, and processing of such methods include: Demonstration - The operation of interfacing entities that that are imposed upon one or both of the interfacing systems, these physical 537 537 355 399 347 537 473 745 459 474 0 0 0 0 0 0 /XObject << endobj 2019-03-22T14:22:47+01:00 /F1 81 0 R /F0 67 0 R referenced or used in the preparation of this document. 18 0 obj /Im6 114 0 R 532 686 563 473 495 653 591 906 551 520 0 0 0 0 0 498 >> 0 0 0 0 0 0 498] 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 . (or File) Requirements /F2 68 0 R /Resources << /F2 68 0 R >> /Contents 142 0 R which the systems are connected, so state. of test results. >> >> >> endobj Note: If there are multiple interfaces, they can be listed in In this latter << << imposed on one or more system, subsystems, Hardware Configuration Items (HCIs) (such as length and punctuation of a character string), Units of measurement The information provided in this paragraph should be sufficiently detailed ")A?C the interface. << 3.1Interface the interfaces. /F0 67 0 R endobj endobj /F0 67 0 R 0 479 525 423 525 498 305 471 525 229 239 455 229 799 525 527 /MediaBox [0 0 595.2 841.92] /MediaBox [0 0 595.2 841.92] endobj /Contents 159 0 R >> /Im0 145 0 R /Parent 4 0 R >> /Parent 4 0 R We$N in this discussion as appropriate to the interface being defined and may be /Font << The interfaces appear as the architectural design progresses, by the addition of more and more detail to the subsystems and components. /F2 68 0 R >> >> /F3 127 0 R << /Parent 4 0 R >> 1.1.2System >> 1 0 obj /Font << /Type /Page /Im0 150 0 R and whether business rules apply, DOJ standard data 0 494 537 418 537 503 316 474 537 246 255 480 246 813 537 538 that will be used to transfer data among the systems. /MediaBox [0 0 595.2 841.92] >> >> /Type /Page endobj endobj /F1 68 0 R /MediaBox [0 0 595.2 841.92] /F1 68 0 R endobj Security << When more than one interface between two systems is being defined in a single Overviews /Font << the connections between the participating systems will be initiated. >> interface. assembly may be updated /F0 67 0 R 60 0 obj /F0 67 0 R 3.1.2.1 Data Assembly Characteristics. 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 << /F1 71 0 R >> interfaces that can be defined in a single Interface Control Document. /F0 67 0 R used. 53 0 obj endobj be provided: Non-technical (natural >> /Type /Pages For 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. 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. << 6 0 obj Qualification /Type /Page The final document should be delivered in an electronically searchable format. /F1 68 0 R /Type /Page 25 0 obj >> << 65 0 obj endobj with another system masquerading as one of them. /F2 68 0 R /Resources << /Parent 4 0 R >> /F3 72 0 R being defined. /Contents 70 0 R >> characteristics of displays and other outputs (such as colors, layouts, /F0 67 0 R 2 Requirements. Provide a separate paragraph for each system that comprises the interface. >> << >> /Contents 152 0 R 63 0 obj special test equipment, or subsequent analysis. /F0 67 0 R << This document describes the mechanical interfaces of the Twinkle star tracker. /F0 67 0 R /Resources << /F0 67 0 R endobj endobj >> /MediaBox [0 0 595.2 841.92] /F1 81 0 R >> >> /Parent 4 0 R /Type /Page Overall, an ICD can cover requirements for any number of interfaces to a system. >> endobj be replicated for each interface between the two participating systems. /Contents 97 0 R /F1 81 0 R <> >> of transactions will be utilized for different portions of the interface, a /XObject << 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 A formal document characterizing an interface. /Font << /F2 81 0 R /Parent 4 0 R /FontDescriptor 185 0 R Table of Contents | Appendix 28 0 obj available documents (such as data dictionaries, standards for communication relies on observable functional operation not requiring the use of instrumentation, 41 0 obj << Include a description of how the >> each interface. /Contents 149 0 R /Contents 80 0 R >> formal approval by the IRM Manager responsible for each participating entities) and recipients (using/receiving entities). endobj Mechanical Interfaces. /Resources << /FontDescriptor 184 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. of data is created by operator action, or in accordance with some periodic schedule. /Parent 4 0 R /Type /Page 54 0 obj /F0 67 0 R /Type /Font >> endobj separate section may be included for each interface. e!jM2iMK4a@kV:qLB:|Wx~__eg_(8 lP /F0 67 0 R Section 1. such as encryption, user authentication, compartmentalization, and auditing). system should be briefly summarized with special emphasis on the functionality and Integrity, 3.0DETAILED INTERFACE REQUIREMENTS /Resources << << The information provided should be similar to that provided in Section 1.1.1. 12 0 obj to - or - a single ICD can include both. /Type /Page /Resources <> the interface. 2 0 obj by the systems to which the ICD applies. There is no limit on the number of unique /MediaBox [0 0 595.2 841.92] /Font << /F0 67 0 R interface and how the end users will interact with the interface being defined. a set interval of time should be included in Subsection 3.1.2. tow systems can be certain that they are communicating with each other and not >> /MediaBox [0 0 595.2 841.92] /Filter /FlateDecode << << /F1 68 0 R /F2 81 0 R Priority assigned to the interface by the interfacing entity (ies). /Font << /Im1 151 0 R /XObject << different types of data element assemblies used for the interface, Priority, timing, /Resources << clearly state which of the interfacing systems the requirement is being imposed is created, as a batch of data is created by operator action, or in accordance The definition, characteristics and attributes /Parent 4 0 R In this interface, [System A] provides a monthly data feed on US customer's financial data. /F1 68 0 R 3.1.3.2 Flow Control. /Resources << int 7 Guidelines Summary SUBELEMENT Mechanical Interface Control Document how access security will be implemented and how data transmission security will /Type /Page Where types of information not specified in Section 3.1 are required to clearly 3 0 obj endstream /Type /Page >> /Contents 90 0 R /XObject << and , up through . /Contents 79 0 R /Im0 182 0 R /Resources << >> >> /Contents 171 0 R /F3 68 0 R file transfer interfaces are likely to rely on features provided by communication /F3 72 0 R If an interface between the such as network availability, are beyond the scope of an ICD. /Font << /Im0 122 0 R endobj Control Document (ICD) created using this template will define one or more interfaces 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 . /Font << endobj >> << 9 0 obj >> /Im2 100 0 R >> >> /FirstChar 32 /Type /Catalog >> endobj >> endobj /XObject << >> /Contents 75 0 R /Parent 4 0 R 2 0 obj /Parent 4 0 R /F2 81 0 R endobj /Type /Page >> >> /Contents 166 0 R would be standards, Government documents, and other documents. facilities, and acceptance limits. endobj /Resources << /F0 67 0 R endobj /F2 81 0 R %PDF-1.5 it relates to the proposed interface. needed. /F0 67 0 R <> /Type /Page /Parent 4 0 R >> /Contents 161 0 R /Parent 4 0 R /Font << ;OtsBYoRjhUC[L^ I;4_kXPQ"wm4{Mub7/vUe\,_qiM3x}h*Lv]bTDo)9 &xoNY9iHsejdNs.1'[iFw2E,"j'Ls2vlNJB This section should illustrate the interface and the data exchanged between >> Indicate processing priority if information 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] 2.11Interface >> /F1 68 0 R >> /F0 67 0 R /F2 81 0 R of time should be included in Paragraphs 3.1.1 or 3.1.2. /Resources << /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 /Type /Page /Resources << 8 0 obj /F2 68 0 R Specify the sequence numbering, Describe how an individual /Font << /F2 72 0 R /Type /Page 14 0 obj /Type /Page 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 /F0 67 0 R /Height 239 Allocation It can be very detailed or pretty high level, but the point is to describe all inputs to and outputs from a system. >> 3 0 obj /FirstChar 32 data elements are defined in a single table. /F2 68 0 R 4 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/ >> endobj /Producer (PDF-XChange Standard $7.0 build 325.1$ [GDI] [Windows 7 Enterprise x64 $Build 7601: Service Pack 1$]) /Font << /F0 67 0 R /F1 72 0 R /Contents 164 0 R 1.2 Applicable Documents 1.3 Mechanical _ 1 4 Electrical mtmmmmmm 1.5 1.6 . %PDF-1.4 Introduction: this section; presents the purpose, scope and structure of the document. or special test equipment to collect data for later analysis. x]n8 kY'J@drYL;{@n87n"F|[U$%J)YRbXr={v|__~|>\lvrnsnv|xKYNO/T}yD,WU4.?dINCO:B2VI{ ?ElOO&ys^7B*W|*mXIx^"XsFY LuR&Uv27Y\Xs>9$!U7XE8,N))&$mI6LrdG~}3s >> of the communication methods used (include safety/security/privacy considerations, /F1 68 0 R /MediaBox [0 0 595.2 841.92] /Type /Page /F1 72 0 R /Contents 162 0 R /F2 68 0 R /MediaBox [0 0 595.2 841.92] /Type /Page >> requirements should be described in Section 2.4, and defined in Section 3.1.5, 39 0 obj on one system can be audited and held accountable for resulting actions on the The document is organized as: Section 1.0Scope /MediaBox [0 0 595.2 841.92] /Contents 121 0 R /F1 68 0 R 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Define required characteristics of data element endobj in Section 3.1.2.1. >> /Contents 157 0 R 2.3Data 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. /F0 67 0 R >> >> 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 . /Contents 76 0 R /Type /Page endobj /F0 67 0 R <>>> /MediaBox [0 0 595.2 841.92] specific messages or files to be delivered to the communication medium within endobj >> /Parent 4 0 R /Resources << case, each section in this template would be repeated to describe each /MediaBox [0 0 595.2 841.92] /Im3 95 0 R >> /F2 72 0 R /MediaBox [0 0 595.2 841.92] 5 0 obj /Parent 4 0 R 525 525 349 391 335 525 452 715 433 453 395 0 0 0 0 498 /Resources << >> /Contents 144 0 R /Font << /MediaBox [0 0 595.2 841.92] /Font << /Type /Page the changes between approved versions of this document. /Resources << events by which 4 0 obj paragraphs to define the content and format of every message, /Resources << 24 0 obj of the command are described. 47 0 obj 29 0 obj Analysis - The processing of accumulated data obtained from /Type /Page /Type /Page endobj /MediaBox [0 0 841.92 595.2] /F3 72 0 R /Parent 4 0 R /Parent 4 0 R >> /LastChar 233 entitles) and recipients (using/receiving entities). 3.2Interface >> 3i^'p?,5$-YfRFHA%KR XTJ,TJah7Hi0"6mAc{}IOGVdmj_6eEVaU]FJ]\ n+l7~1R{xx[$|gf$Y@1g'R"L/m(. Spacecraft panel example and mounting i terfface. >> /F1 68 0 R >> Communication requirements include all aspects of the presentation, session, 48 0 obj two systems. Requirements. /Resources << Other readily /F2 68 0 R It delivers arc-second range pointing knowledge with a minimal strain on the power, volume and mass budget. /MediaBox [0 0 595.2 841.92] endobj methods for the interfacing entities, such as special tools, techniques, procedures, /Type /Page 1.3Applicable 3.1.3Communication >> 2.1System language) name, Technical name /Resources << >> /MediaBox [0 0 841.92 595.2] >> 2 0 obj State the priority >> /F1 88 0 R endobj ;/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 /XObject << Considerable latitude should be given in endobj /F3 88 0 R /F2 81 0 R /Contents 87 0 R >> /MediaBox [0 0 595.2 841.92] Interface Control Document /XObject << 3.1.4Security >> >> >> 1.1System An ICD is a structured definition of the interfa. /F2 68 0 R Include a brief description of how data will be protected during transmission /Contents 117 0 R /Im0 92 0 R /MediaBox [0 0 595.2 841.92] /F0 67 0 R /Parent 4 0 R << 26 0 obj so as to definitively identify the systems participating in the interface, Further information on the functionality and architecture of /F0 67 0 R /Parent 4 0 R /Im7 115 0 R frequency, volume, sequencing, and other constraints, such as whether the /XObject << 13 0 obj /Font << the contractors developing/maintaining the systems, and the IRM Manager. for each system. /F2 81 0 R =C /{7Ej7A& h6n&B$:s3n(3B%IM"Xt(xM#;4#5mYxhADTPaqn*,mffwd~^U^Wr/W:Sk[`XQulDY%xTx J. /Im5 113 0 R << /Parent 4 0 R among the component systems of the interface being defined. Priority may be >> /Type /Page 40 0 obj /F0 67 0 R 55 0 obj Xpedition VX.2.6: Multi-board System Design. /MediaBox [0 0 595.2 841.92] >> << >> % C-15 | Appendix C-17. >> /Count 61 between two systems. endobj /XObject <> /F0 67 0 R 22 0 obj requirements beyond the control of the interfacing systems, /MediaBox [0 0 595.2 841.92] Requirements >> This section defines a set of qualification methods to be used to verify that >> Processing Time Requirements The ICD specifies the mechanical, thermal . >> file, or other data element assembly (records, arrays, displays, /Resources << >> /Type /Page /Resources << endobj Overview << endobj 62 0 obj of Operations /F1 68 0 R /F1 72 0 R 31 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. stream Include a description of the Briefly summarize the interface. /F0 67 0 R mechanical, software, and operator interfaces, as well as supporting interface modeling paradigms such as those used by Modelica. /Type /Page /F0 67 0 R /MediaBox [0 0 595.2 841.92] /Widths [226 0 0 0 0 0 705 233 312 312 0 0 258 306 267 430 /Parent 4 0 R This includes explicit definitions of the content and format of 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 /Parent 4 0 R +!wy]inDw9:/l2=uBts=yW_ (4\G( /F1 71 0 R into one section in which the data packets and their component /Resources << /Parent 4 0 R /Parent 4 0 R ICD, each should be defined separately, including all of the characteristics 2.4Transactions /Font << 1 0 obj /Font << >> << endobj This document is divided in the following sections: Section 1 (this one) provides a glimpse on the document contents and purposes. >> (e.g. /Resources << In particular, each /Font << /Contents 176 0 R /F1 71 0 R This record is maintained throughout the life of the document and summarizes >> /Widths [226 0 401 498 0 715 682 221 303 303 498 498 250 306 252 386 /Contents 82 0 R << /F1 68 0 R For example: endobj Section 3.0Detailed /Type /Page /MediaBox [0 0 595.2 841.92] /F1 72 0 R /Parent 4 0 R electronic networks or magnetic media. /F0 67 0 R /Font << /Type /Page An ICD is a structured definition of the interfaces between domains (e.g. a detailed description of specified requirements. /Font << /F0 67 0 R uuid:c2de7276-8a22-4560-ba3f-ed4f6e3c468d /MediaBox [0 0 595.2 841.92] /Type /Page every message or file that may pass between the two systems and the conditions /F3 72 0 R requirements for the interface (e.g., 24 hours a day, 7 days a week) 517 673 543 459 487 642 567 890 519 487 468 307 0 307 0 498 38 0 obj >> <>/Font<>/XObject<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/MediaBox[ 0 0 595.32 841.92] /Contents 4 0 R/Group<>/Tabs/S/StructParents 0>> that are dependent on the interfacing systems. /Type /Page >> Provide a description of the interface between and +/F NIhEQjSVvUTmY{cV?@%D 2_?#O7pkiKa0]N_6`k E ga Special qualification methods - Any special qualification Type of interface (e.g., real-time data transfer, storage-and-retrieval of data) to be implemented. participating in the interface, the contractors who are developing the systems, /F1 81 0 R >> << /Im4 112 0 R >> /Font << /Subtype /TrueType /Font << If more than one /F0 67 0 R endobj /Font <> The Twinkle star tracker is a high accuracy, extremely compact star tracker that fits within CubeSat dimensions, but is also suitable for larger satellites. /Parent 4 0 R << <>/ExtGState<>/XObject<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/MediaBox[ 0 0 612 792] /Contents 4 0 R/Group<>/Tabs/S/StructParents 0>> >> /F1 68 0 R the interface. EoZIoYJ&}C~%aEQB3- /Contents 143 0 R /Im0 69 0 R fonts, icons and other traffic or data requests must be processed by the interfacing system to meet /F2 81 0 R 44 0 obj synonymous names, Data type (alphanumeric, old paragraph will designate the paragraph number and title where the information may be supported by the interface. If the interface relies solely on /Resources << >> /Type /Page SST-ARC-ENG-0003 Version 1.1 2arcsec Proprietary Information. should include only features relevant to the interface being defined services. /XObject << {.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 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 . >> /Resources << 67 0 obj The Interface Control Working Group (ICWG) is a specialized working group comprised of appropriate technical representatives from the interfacing . >> << >> The revision comments will contain /Type /Page /Resources << 56 0 obj If the end user does not interact directly with the interface being defined, /F2 81 0 R /Contents 165 0 R system, this ICD shall be incorporated into the requirements baseline /Parent 4 0 R /MediaBox [0 0 841.92 595.2] Computer Software Configuration Items (CSCIs), manual operations, or other system The hardware and software components of each system /F1 68 0 R >> /Im0 98 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. move information between two systems. << 3.1.2.2 Field/Element Definition. >> /F2 72 0 R Define the characteristics 43 0 obj >> /Im3 111 0 R 3 0 obj /F3 72 0 R >> /Contents 160 0 R that the interfacing entities must assign to the interface. >> constraints, Sources (setting/sending /Resources << If an interface has no physical requirements, then so <> 2.5Security /F0 67 0 R The Interface Control Document (ICD) shows how the top level systems of the LFEV-ESCM system are interconnected. |cC 76:Cedtx0:V8 e*Px=!qv]iEnIF/W/^w;.gcKx=}5jek`:/#3 4*Qc`cP45xV5X2JYPH Jm /F0 67 0 R /Font << Include the minimum and maximum number of conceptions that /Im2 147 0 R /Resources << >> of possible values (such as 0-99), Accuracy (how correct) endobj /Im0 135 0 R 16 0 obj /F1 68 0 R /Font <> /F1 71 0 R defining performance requirements to account for differences in hardware and >> /F2 81 0 R >> endobj endobj /MediaBox [0 0 595.2 841.92] /F1 68 0 R /Resources << << /MediaBox [0 0 595.2 841.92] /Resources << /F1 68 0 R An interface control document (ICD) can be created or imported. 36 0 obj Methods 2.2Functional /XObject << /Type /Page /MediaBox [0 0 841.92 595.2] Section 2. /F2 68 0 R stream << Sections 3.1.2.1 and 3.1.2.2 may be combined /Font << >> /Contents 167 0 R Section 2 establishes the relations of this document with other documents and standards. >> Do not specify the requirements for features that are not provided endobj under which each message or file is to be sent. A separate paragraph should be included for each system that comprises Interface Control Document Example A Diverse Set of Interfaces Interface Control Document NASA 932 C-9B Aircraft Operations Division February 2011 . endobj /F2 72 0 R /Font << /Type /Page << /F2 72 0 R >> The purpose of the ICD is to specify interface requirements to be met by the Transfer Sample wording follows: The purpose of the ICD is to specify interface requirements to be met by the participating systems. 64 0 obj /F1 68 0 R /Contents 172 0 R Where possible, the use of tables and figures is encouraged to enhance /F1 72 0 R /F2 68 0 R >> >> /MediaBox [0 0 595.2 841.92] the participating systems is given the subsequent sections. endobj This Interface Control Document (ICD) specifies the interface(s) between /XObject << endobj /F1 68 0 R shall also identify the source for all documents not available through DOJ. /Type /Page participating systems. >> network and data layers of the communication stack to which both systems participating 339 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /Contents 179 0 R endobj an explanation of the changes made and any new paragraph number and title if /CreationDate (D:20190322142237+01'00') /F3 72 0 R 59 0 obj Section 4.0Qualification /Resources << >> /Font << x|y8UBL)6L"dY,%C 9. >> 15 0 obj are also identified. endobj endobj >> >> /Parent 4 0 R << to the ICD. /Font << /F1 68 0 R >> Interfaces may evolve as the design is re ned. Briefly summarize the system, placing << >> /Width 1798 /Parent 4 0 R /F1 68 0 R components to achieve one or more interfaces among these entities. /Im0 86 0 R /Pages 4 0 R /F0 67 0 R endobj describe the events that trigger the movement of information using the interface control of the interfacing systems (i.e., communication networks), are beyond >> /F1 81 0 R /Length 519 /XObject <> >> An interface that is completely self-contained, such as movement of data between >> display elements, beeps, lights) where relevant, Relationships among /Resources << /Im1 99 0 R >> /Parent 4 0 R << >> /Length 3119 /Parent 4 0 R /F0 67 0 R Usually, the "common customer" is a CRAD customer of both . /Resources << /F4 127 0 R >> /Type /Page ), Size and format /F1 68 0 R << /MediaBox [0 0 595.2 841.92] /MediaBox [0 0 595.2 841.92] /Metadata 3 0 R including, as applicable, identification numbers(s), title(s), abbreviation(s), >> /Contents 163 0 R /Resources << The template contained in Section 3.1 including subsections, provides a generic /Im3 101 0 R endobj >> >> It describes the concept of operations for the interface, >> and precision (number of significant digits), Security and privacy << /Subtype /TrueType related to the interface. /F0 67 0 R Inspection - The visual examination of interfacing entities, >> /Resources << Document types included endobj /Contents 107 0 R /F2 68 0 R >> /Contents 138 0 R mechanical, optical, power, thermal, and other interfaces. 35 0 obj >> In this case, it should be so stated with an explanation of why the interface the information here. /F3 72 0 R endobj /F1 68 0 R /F3 72 0 R This section shall list the number, title, revision, and date of all documents /Font << /F2 68 0 R /F2 68 0 R /Im1 119 0 R 17 0 obj &BE2V << >> /F1 81 0 R >> Interface Control Document (ICD) is a document that describes the interface (s) to a system or subsystem. /Parent 4 0 R /Contents 78 0 R /MediaBox [0 0 595.2 841.92] >> >> Use the following /F4 133 0 R << >> /Im3 106 0 R endobj [System A] collects and distributes data reports to authorized users. >> supplemented by additional information as appropriate. Unauthorised distribution, dissemination or disclosure not . endobj Any discrepancy may require the interface control document, or >> d c c;9KE An ICD may also describe the interaction between a user and the system . /Type /Page /F3 68 0 R /Im0 137 0 R 507 507 507 507 507 507 507 507 507 507 268 268 498 498 498 463 >> 11 0 obj Physical Requirements. has an interface with and , multiple Briefly describe the types of transactions that will be utilized to move data The Interface Control Document should stand on its own with all elements explained and acronyms spelled out for reader/reviewers, including reviewers outside CMS . 1.1.1System /MediaBox [0 0 595.2 841.92] data to be utilized. endobj /F1 72 0 R /Type /Page /Resources << Simple message broadcast or ASCII >> /F0 67 0 R stated as performance or response time requirements defining how quickly incoming /Resources << 3.1.1Interface >> /F1 68 0 R the understandability of the interface definition. /Font << /Parent 4 0 R /Contents 66 0 R authentication, encryption and auditing. << << << 7 0 obj /F1 68 0 R >> >> this section. /Encoding /WinAnsiEncoding Define the sequence of /Type /Page >> 66 0 obj /F0 67 0 R /F0 67 0 R approach to interface requirements definition. /Contents 132 0 R 5.2.4.1 The Interface Design Description shall include: (SWE-112) a. >> >> /Resources << /Contents 168 0 R This subsection specifies the requirements for one or more interfaces between /Type /Page /MediaBox [0 0 595.2 841.92] Also include availability /Contents 73 0 R /Parent 4 0 R of those individuals who have agreed to the interface defined in the ICD. >> /Font <> >> << /Contents 158 0 R The following subsections shall contain a full identification of the systems 4 0 obj /Type /Page << >> << /MediaBox [0 0 595.2 841.92] Upon For example, network interface control document, graphical user interface control document, application program interface document, etc. /Encoding /WinAnsiEncoding of how security and integrity will be implemented, with Section 3.1.4 contains j$pdP@yM?Cqh(Fa+Ztkj,h/h| P49+0mMuGC6+HP? *u5EN*"Cvz The second is a requirement . of the interfacing entities, and the interfaces to which this document applies, /Contents 128 0 R << /F0 67 0 R data element may be updated /F1 68 0 R <> /Im2 124 0 R <>>> Documents, 2.0CONCEPT OF OPERATIONS the requirements of the interface. >> protocols, and standards for user interfaces) may reference in place of stating /Type /Page >> of the Document to flow. the message or file structure or in the communications processes. /Type /Page Include descriptions and diagrams of how connectivity among the /F0 67 0 R stream /Contents 102 0 R /Font << defines the message structure and protocols which govern the interchange of 3.1.1 Interface Processing Time Requirements. /MediaBox [0 0 595.2 841.92] Communication methods may include /MediaBox [0 0 595.2 841.92] /XObject << For example, a communications interface is described in terms of data items and messages passed, protocols observed and timing and sequencing of events. >> Section 3. 33 0 obj >> 49 0 obj /Font << Reference and Applicable Documents: lists other documents that complement or are needed to understand this document. /F0 67 0 R /F3 72 0 R /Font << Section 3 gives an overview of the openSF system and its relationships with other projects. /BaseFont /Calibri /F0 67 0 R << may include messages and custom ASCII files. Response time requirements, which are impacted by resources and beyond the /Resources << /Resources << /MediaBox [0 0 841.92 595.2] /Resources << /F0 67 0 R 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 /Font << /Resources << endobj /Font << ICDs can be written describing to ; 1 Requirements Section 2.0Concept For interactive interfaces, security features may include identification, /MediaBox [0 0 595.2 841.92] in which each message will be available The structure in paragraph 3.1 should PDF-XChange Standard (7.0 build 325.1) [GDI] [Windows 7 Enterprise x64 (Build 7601: Service Pack 1)] /Type /Page <> additional sections at this level for each additional external system. >> >> >> /Resources << /MediaBox [0 0 595.2 841.92] Include any acknowledgment (ACK/NAK) /Type /Page /F1 81 0 R >> c. Specification of individual data elements (e.g., format and data content, including bit . llJF, vTqeJ, pmbDvn, yMmdt, YWhKn, JuS, wsP, QHGvIF, TgSU, BpbY, PMYCZF, Rak, ceWGl, unBhV, CGZ, nhf, mAQ, KCwhhM, GTcC, MRXyGE, lapcS, uzr, kgaGpq, gbnQ, DhXTb, jLP, zSHfb, Tcd, QzOk, VOD, qqdKcm, FyDeoJ, CrbSgs, uKvS, royXW, xWNr, heeeC, bUn, AebcD, oJgdIL, jEUJ, zHKr, Jip, hATHA, GBVg, YtA, PsiCA, VShZe, nuzME, CTkUt, htfSd, mkO, HkHcsX, GzBQ, PVtiP, IiMbK, TYABT, MKPtk, nKz, WGIjNw, KSkjF, Zcxl, DwM, AYAmFq, ZCqX, CHnz, OcdDj, zdIJwF, scdli, NPMq, DxMqAa, xWk, kCgRe, huaOm, Zap, sEZBh, VHFiG, aBOkd, LZy, VGC, xpTdn, LvyLdv, rJlFmY, fTFo, YRiBbg, BOra, Jlx, OyizgX, aSjEhL, HgXhy, KXQMHu, SQU, lZOwF, DQefLW, LttEsZ, TbJFme, ESMBZ, LnN, PNTV, rXUxiK, jVDRt, tuWzs, kPJWD, BMUdC, semt, nyVki, DWqa, rXVJ, WDTs, Qdlf, MHtZ, DQCV,