For Production Gateway Terminals Sample Clauses

For Production Gateway Terminals. Gateway Terminals that fail testing in accordance with the Production Acceptance Test Plan will be rejected by AIL. Contractor shall not deliver or ship such Gateway Terminals and Contractor will not be entitled to receive payment for such Gateway Terminals until Contractor corrects all items which failed and successfully completes a repeat Production Acceptance Test.
AutoNDA by SimpleDocs

Related to For Production Gateway Terminals

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Video Display Terminals ‌ The Employer shall ensure that any new office equipment or facility required for use in conjunction with VDTs shall meet the standards recommended by the Workers' Compensation Board.

  • Hosted Services 3.1 The Provider hereby grants to the Customer a worldwide, non-exclusive licence to use the Hosted Services for the business purposes of the Customer in accordance with the Documentation during the Term. 3.2 The Provider shall create an Account for the Customer and shall provide to the Customer login details for that Account to enable the Customer to configure and administer the Hosted Services and enable registration of Customer End Users. 3.3 Except to the extent expressly permitted in this Agreement or required by law on a non- excludable basis, the licence granted by the Provider to the Customer under Clause 3.1 is subject to the following prohibitions: (a) the Customer must not sub-license its right to use the Hosted Services; (b) the Customer must not make any alteration to the Platform; and (c) the Customer must not conduct or request that any other person conduct any load testing or penetration testing on the Platform or Hosted Services without the prior written consent of the Provider. 3.5 The Customer shall use reasonable endeavours, including appropriate organisational and technical measures relating to Account access details, to ensure that no unauthorised person may gain access to the Hosted Services using an Account. 3.6 The parties acknowledge and agree that Schedule 2 (Availability SLA) shall govern the availability of the Hosted Services. 3.7 The Customer must ensure that all persons using the Hosted Services with the authority of the Customer or by means of an Account comply with the Terms Of Use. 3.8 The Customer must not use the Hosted Services in any way that causes, or may cause, damage to the Hosted Services or Platform or impairment of the availability or accessibility of the Hosted Services. 3.9 The Customer must not use the Hosted Services: (a) in any way that is unlawful, illegal, fraudulent or harmful; or (b) in connection with any unlawful, illegal, fraudulent or harmful purpose or activity. 3.10 For the avoidance of doubt, the Customer has no right to access the software code (including object code, intermediate code and source code) of the Platform, either during or after the Term. 3.11 The Provider may suspend the provision of the Hosted Services if any amount due to be paid by the Customer to AWS for the benefit of the Provider under this Agreement is overdue, and the Provider has given to the Customer at least 30 days' written notice, following the amount becoming overdue, of its intention to suspend the Hosted Services on this basis.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Interconnection Customer (1) Interconnection Customer shall construct and, unless otherwise indicated, shall own, the following Interconnection Facilities: None (2) In the event that, in accordance with the Interconnection Construction Service Agreement, Interconnection Customer has exercised the Option to Build, it is hereby permitted to build in accordance with and subject to the conditions and limitations set forth in that Section, the following portions of the Transmission Owner Interconnection Facilities which constitute or are part of the Customer Facility: None Ownership of the facilities built by Interconnection Customer pursuant to the Option to Build shall be as provided in the Interconnection Construction Service Agreement.

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

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