Interface Control Document Sample Clauses

Interface Control Document. The Contractor shall specify all external and internal interfaces in a Subsystem ICD. This document shall [***].
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
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.
Sample 1Sample 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.
Sample 1Sample 2
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.
Sample 1Sample 2
Interface Control Document. The Contractor shall develop an ICD that defines external and internal interfaces and is compatible with the terminal vendor interfaces.
Sample 1Sample 2
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.
Sample 1Sample 2
Interface Control Document. The Contractor shall provide an Interface Control Document that describes both physically and functionally all internal and external system interfaces. Confidential treatment has been requested for portions of this exhibit and such portions have been filed separately with the Commission. The copy filed herewith omits the information for which confidential treatment has been requested and replaces it with [***]. AMENDMENT 4 TerreStar Satellite Chipset SOW
Sample 1
AutoNDA by SimpleDocs
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.
Sample 1
Interface Control Document. The Contractor shall provide an Interface Control Document that describes both physically and functionally all internal and external system interfaces.
Sample 1

Related to Interface Control Document

  • Control Documents (a) Each of the parties to the Control Documents has the legal right, power and authority to enter into and perform its/his/her obligations under each Control Document to which it/he/she is a party and has taken all necessary corporate action to authorize the execution, delivery and performance of, and has authorized, executed and delivered, each Control Document to which it/he/she is a party; (b) each Control Document constitutes a legally binding obligation of the parties thereto, enforceable in accordance with its terms; and (c) each Control Document is in full force and effect.

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Tax Documentation Xxxxxx agrees to provide a completed IRS 1099 for its payments to, and Xxxxxxx agrees to provide IRS W-9 forms for, each of the following payees under this Settlement Agreement:

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Service Level Agreement Subject to the terms and conditions of this Agreement, Bank agrees to perform the custody services provided for under this Agreement in a manner that meets or exceeds any service levels as may be agreed upon by the parties from time to time in a written document that is executed by both parties on or after the date of this Agreement, unless that written document specifically states that it is not contractually binding. For the avoidance of doubt, Bank’s Service Directory shall not be deemed to be such a written document.

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Force Majeure and Disaster Recovery Plans A. DST shall not be responsible or liable for its failure or delay in performance of its obligations under this Agreement arising out of or caused, directly or indirectly, by circumstances beyond its reasonable control, including, without limitation: any interruption, loss or malfunction of any utility, transportation, computer (hardware or software) or communication service; inability to obtain labor, material, equipment or transportation, or a delay in mails; governmental or exchange action, statute, ordinance, rulings, regulations or direction; war, strike, riot, emergency, civil disturbance, terrorism, vandalism, explosions, labor disputes, freezes, floods, fires, tornados, acts of God or public enemy, revolutions, or insurrection; or any other cause, contingency, circumstance or delay not subject to DST’s reasonable control which prevents or hinders DST’s performance hereunder.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!