Additional Electrical Design Specifications: Conduit Sample Clauses

Additional Electrical Design Specifications: Conduit. The parties agree that, in addition to the specifications and requirements referred to in Sections 6.01-6.04 above, facilities placed in SWBT’s conduit system after the effective date of this Agreement shall meet the electrical design specifications set forth in this section.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Additional Electrical Design Specifications: Conduit. The parties agree that, in addition to the specifications and requirements referred to in Sections 6.01-6.04 above, facilities placed in SBC NEVADA’s conduit system after the effective date of this Appendix shall meet all of the electrical design specifications set forth in this section.
Sample 1
Additional Electrical Design Specifications: Conduit. The parties agree that, in addition to the specifications and requirements referred to in Sections 6.01-6.04 above, facilities placed in AT&T’s conduit system after the effective date of this Appendix shall meet all of the electrical design specifications set forth in this section.
Sample 1

Related to Additional Electrical Design Specifications: Conduit

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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