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 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. 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 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 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. 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.
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. 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
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

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 The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • 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 Xxxxxx 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.

  • 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.

  • 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 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: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements. Acknowledging your access and consent to receive and sign documents electronically To confirm to us that you can access this information electronically, which will be similar to other electronic notices and disclosures that we will provide to you, please confirm that you have read this ERSD, and (i) that you are able to print on paper or electronically save this ERSD for your future reference and access; or (ii) that you are able to email this ERSD to an email address where you will be able to print on paper or save it for your future reference and access. Further, if you consent to receiving notices and disclosures exclusively in electronic format as described herein, then select the check-box next to ‘I agree to use electronic records and signatures’ before clicking ‘CONTINUE’ within the DocuSign system. By selecting the check-box next to ‘I agree to use electronic records and signatures’, you confirm that: • You can access and read this Electronic Record and Signature Disclosure; and • You can print on paper this Electronic Record and Signature Disclosure, or save or send this Electronic Record and Disclosure to a location where you can print it, for future reference and access; and

  • Compliance Control Services (1) Support reporting to regulatory bodies and support financial statement preparation by making the Fund's accounting records available to the Trust, the Securities and Exchange Commission (the “SEC”), and the independent accountants.

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopts or introduces for the Employer, management and municipal staff of the Employer.

  • 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)

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

Time is Money Join Law Insider Premium to draft better contracts faster.