LV/Spacecraft Mechanical Interface Verification Sample Clauses

LV/Spacecraft Mechanical Interface Verification. The U.S. signatories will make available the appropriate hardware for performing a Fit Check between the LV and the spacecraft. This test will verify ICD mechanical compatibility between the LV and the Spacecraft including cable routing, connections, and any areas where there are potential interference issues. Results will be provided to the foreign signatories.
AutoNDA by SimpleDocs

Related to LV/Spacecraft Mechanical Interface Verification

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

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

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the End User’s 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 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.

  • CONTRACTOR PORTABLE DEVICES Contractor shall not place Data on any portable Device unless Device is located and remains within Contractor’s CONUS Data Center. For Authorized Users subject to ITS policies, the Data, and/or the portable device containing the Data, shall be destroyed in accordance with applicable ITS destruction policies (ITS Policy S13-003 Sanitization/Secure Disposal and S14-003 Information Security Controls or successor) when the Contractor is no longer contractually required to store the Data. TRANSFERRING OF DATA General Except as required for reliability, performance, security, or availability of the services, the Contractor will not transfer Data unless directed to do so in writing by the Authorized User. All Data shall remain in CONUS. At the request of the Authorized User, the Contractor will provide the services required to transfer Data from existing Databases to physical storage devices, to facilitate movement of large volumes of Data. The Authorized User may require several Cloud providers to share or transfer Data for a period of time. This will be provided for in the Authorized User Agreement or shall be assumed to be limited to a six month duration. Transfer of Data at End of Contract and/or Authorized User Agreement Term At the end of the Contract and/or Authorized User Agreement term, Contractor may be required to facilitate transfer of Data to a new Contractor. This transfer must be carried out as specified by the Authorized User in the Authorized User Agreement. Transfer of Data; Charges Contractor cannot charge for the transfer of Data unless the charges are provided for in response to an Authorized User RFQ. Transfer of Data; Contract Breach or Termination Notwithstanding Section 3.6.3, in the case of Contract breach or termination for cause of the Contract, all expenses for the transfer of Data shall be the responsibility of the Contractor.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • TECHNICAL TASKS Products that require a draft version are indicated by marking “(draft and final)” after the product name in the “Products” section of the task/subtask. If “(draft and final)” does not appear after the product name, only a final version of the product is required. Subtask 1.1 (Products) describes the procedure for submitting products to the CAM.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

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