Interface Control Document Sample Clauses

The Interface Control Document clause establishes the requirement for a formal document that defines and manages the technical and functional interfaces between different systems, subsystems, or components within a project. This document typically details the specifications, protocols, and data formats that must be adhered to by all parties involved, ensuring compatibility and integration. By mandating the creation and maintenance of an Interface Control Document, the clause helps prevent misunderstandings and technical conflicts, thereby facilitating smooth system integration and reducing the risk of costly errors or rework.
POPULAR SAMPLE Copied 1 times
Interface Control Document. The Contractor shall provide an ICD that describes both physically and functionally all internal and external system interfaces. It shall be compatible with existing satellite segment, IP Network, OSS/BSS, and 3G Core/IMS ICDs. The IP Network and 3G Core/IMS ICDs will be provided by TerreStar as described in section 2.
View SourceView Similar (2)
Interface Control Document. The Contractor shall specify all external and internal interfaces in a Subsystem ICD. This document shall [***].
View SourceView Similar (3)
Interface Control Document. 3.4.1 The construction and execution of the interface implementation will be fully documented by Pacific in an Interface Control Document. The Interface Control Documents for the interfaces are listed in Section 2.2, Scope.
View SourceView Similar (2)
Interface Control Document. The Contractor shall develop an ICD that defines external and internal interfaces and is compatible with the terminal vendor interfaces.
View SourceView Similar (2)
Interface Control Document. The national contact points shall prepare a legally non-binding Interface Control Document (ICD) containing the further technical and procedural details referred to in the Articles 2 through 10 of this ATIA.
View SourceView Similar (2)
Interface Control Document. The Section Developer, at its expense, shall design, install, operate, and maintain the ETCS and interconnections of the ETCS with MDTA's Host. Such design and installation shall be consistent with, and meet all requirements of, the Interface Control Document (the "ICD"). The Section Developer shall collaborate with MDTA and adopt detailed requirements to be set out in the ICD developed by MDTA to ensure the correct processing of each Trip to be sent to MDTA. The ICD shall be based on the current ICD for MDTA's toll systems in the State, and MDTA shall discuss any modifications suggested by the Section Developer to improve the transmission of Trip data for both parties. The ICD applicable to the Section shall be finalized prior to commencement of tolling operations for the Section. The ICD is subject to change with reasonable advance written notice from MDTA. The Section Developer must comply with the new interface requirements set out in any updated ICD at no cost to MDTA. The Section Developer acknowledges that the ICD is intended to be a framework for the interface between a third party and MDTA; it supports many different types of systems with different unique needs, requirements, and contractual obligations; and it is subordinate to, and is not intended to supersede or alter, any of the express provisions of the TSA or the Section P3 Agreement.
View SourceView Similar (2)
Interface Control Document. The Contractor shall provide an Interface Control Document that describes both physically and functionally all internal and external system interfaces. It shall be compatible with existing satellite segment, IP Network, OSS/BSS, and 3G Core/IMS ICDs. The IP Network and 3G Core/IMS ICDs will be provided by TerreStar as described in section 2.
View Source
Interface Control Document. The Contractor shall provide an Interface Control Document that describes both physically and functionally all internal and external system interfaces. TerreStar Satellite Chipset SOW
View Source
Interface Control Document. The Contractor shall provide an Interface Control Document that describes both physically and functionally all internal and external system interfaces.
View Source

Related to Interface Control Document

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central ▇▇▇▇▇▇ Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: ▇▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/guides/signer-guide- signing-system-requirements.