Design and Topology of the Vendor Network Sample Clauses

Design and Topology of the Vendor Network. Vendor will utilize its Global Network Infrastructure (GNI) backbone for transport of broadband traffic to Customer data centers; provided that in order to provide last mile diversity, at Customer's request, for up to [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] percent of the GNI last mile capacity to Customer's facilities, Customer and Vendor agree to exchange local facilities, at no cost to either Party, for equivalent bandwidth exchanged. The Parties agree to establish a mutually acceptable bandwidth-exchanging and circuit-management process, including with respect to co-location space, facility access, and helping hands where both Parties have local facilities in each geography.
View SourceView Similar (3)
Design and Topology of the Vendor Network. Vendor will utilize its Global Network Infrastructure (GNI) backbone for transport of broadband traffic to Customer data centers; [*Material Omitted and Separately Filed Under an Application for Confidential Treatment]. The Parties agree to establish a mutually acceptable [*Material Omitted and Separately Filed Under an Application for Confidential Treatment], including with respect to [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] where both Parties have [*Material Omitted and Separately Filed Under an Application for Confidential Treatment].
View Source

Related to Design and Topology of the Vendor Network

  • CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services. § 3.1.1 The Architect shall manage the Architect’s services, research applicable design criteria, attend Project meetings, communicate with members of the Project team, and report progress to the Owner. § 3.1.2 The Architect shall coordinate its services with those services provided by the Owner and the Owner’s consultants. The Architect shall be entitled to rely on, and shall not be responsible for, the accuracy, completeness, and timeliness of, services and information furnished by the Owner and the Owner’s consultants. The Architect shall provide prompt written notice to the Owner if the Architect becomes aware of any error, omission, or inconsistency in such services or information. § 3.1.3 As soon as practicable after the date of this Agreement, the Architect shall submit for the Owner’s approval a schedule for the performance of the Architect’s services. The schedule initially shall include anticipated dates for the commencement of construction and for Substantial Completion of the Work as set forth in the Initial Information. The schedule shall include allowances for periods of time required for the Owner’s review, for the performance of the Owner’s consultants, and for approval of submissions by authorities having jurisdiction over the Project. Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner. With the Owner’s approval, the Architect shall adjust the schedule, if necessary, as the Project proceeds until the commencement of construction. § 3.1.4 The Architect shall not be responsible for an Owner’s directive or substitution, or for the Owner’s acceptance of non-conforming Work, made or given without the Architect’s written approval. § 3.1.5 The Architect shall contact governmental authorities required to approve the Construction Documents and entities providing utility services to the Project. The Architect shall respond to applicable design requirements imposed by those authorities and entities. § 3.1.6 The Architect shall assist the Owner in connection with the Owner’s responsibility for filing documents required for the approval of governmental authorities having jurisdiction over the Project.

  • Synchronization, Commissioning and Commercial Operation 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including RTU for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG shall immediately after each synchronization/tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • Technology Upgrades Notwithstanding any other provision of this Agreement, Verizon shall have the right to deploy, upgrade, migrate and maintain its network at its discretion. The Parties acknowledge that Verizon, at its election, may deploy fiber throughout its network and that such fiber deployment may inhibit or facilitate Covista’s ability to provide service using certain technologies. Nothing in this Agreement shall limit Verizon's ability to modify its network through the incorporation of new equipment or software or otherwise. Covista shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.