Network Latency Standard Sample Clauses

Network Latency Standard. The intent of the Provo Network Latency Standard is to limit the Latency Achievement Quotient (LAQ), as defined below, to 1.0 or less (the equivalent of average latency equaling 150 milliseconds or less) in a given month. Average Round-Trip Latency, with respect to a given month, is defined as the average time required for round-trip packet transfers between POP's on the Provo Network during such month, as measured by Provo. The measurement of the Latency Achievement Quotient is subject to Section 12 (Exceptions) of this SLA. Average Round-Trip Latency does not extend to Service Provider's connection into the Provo Network or to Service Provider's Customer Premise Equipment. LAQ will be measured by dividing the Average Round-Trip Latency on the Provo Network for a calendar month by the 150 milliseconds latency standard. LAQ Calculation: Actual Average Round-Trip Latency between POP's on the Provo Network for Month 150 Milliseconds (Example: 300 ms Actual Average Round-Trip Latency for Month = 300/150 or LAQ of 2) The Latency Achievement Quotient will be one of the factors in calculating any credits due the Retail ISP for the purpose of crediting their Subscribers. (See section 10.1) 2.1 Network Jitter Standard Both parties agree to consider adding mutually acceptable jitter standards for the Network at the initial six month review.
AutoNDA by SimpleDocs

Related to Network Latency Standard

  • Network Upgrades The Transmission Owner shall design, procure, construct, install, and own the Network Upgrades described in Attachment 6 of this Agreement. If the Transmission Owner and the Interconnection Customer agree, the Interconnection Customer may construct Network Upgrades that are located on land owned by the Interconnection Customer. Unless the Transmission Owner elects to pay for Network Upgrades, the actual cost of the Network Upgrades, including overheads, shall be borne initially by the Interconnection Customer.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

  • Software Upgrades All Software Releases (including all Error corrections made available pursuant to this Agreement) that RSA in its sole discretion: (a) deems to be logical improvements to the Software; (b) make generally available to all licensees of the Software; and (c) does not separately price or market.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

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