Round Trip Delay Sample Clauses

Round Trip Delay. 2.3.2.1 When the RTD SLA option is requested by the Customer, Verizon will provide an end-to-end RTD estimate as part of the Service Order Form. Actual RTD performance may vary at circuit completion. 2.3.2.2 Verizon will maintain the circuit within the specified RTD throughout the term of the service. The RTD SLA metric applies to the working channel (home route) of an IXC protected circuit and does not apply when the circuit is on the protect channel.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Round Trip Delay. 2.3.2.1 When requested by Customer, Verizon will provide an end-to-end RTD estimate as part of the Service Order Form. RTD performance may vary at circuit completion. 2.3.2.2 Verizon will maintain the circuit within the specified RTD throughout the term of the circuit.
Sample 1Sample 2
Round Trip Delay. For Premium Service and Extended Service, Orange will provide Service Levels on router-to- router Round Trip Delay. The RTD is measured from CE Router to Teleport PE Router, using values reported by the satellite network management system (NMS).‌ The RTD is calculated on a Monthly basis. The RTD Service Levels from the hub to the Customer’s remote Locations is 700 milliseconds. If the RTD Service Level is not achieved, Customer will receive a credit against the Qualifying Charges for the affected Locations, calculated as follows:  If the actual RTD is higher than RTD Service Level by less than or equal to 10%: No credit will be payable to Customer.  If the actual RTD is higher than RTD Service Level by greater than 10%: Customer will be entitled to receive a credit against the Qualifying Charges for the affected Location where the Outage occurred. The credit will be calculated as 1% of Qualifying Charges for every 1% by which actual RTD is higher than the RTD Service Level, up to a maximum credit of 50% of Qualifying Charges for the affected Locations. All credits will be pro-rated on a per millisecond basis. The RTD Service Levels set forth in this Clause 1.6 are indicative metrics only and are strongly dependent on the actual network size mutually agreed between Customer and Orange. During the 3 Months following the completion of the installation of Customer’s entire Business VPN Satellite Service network, Orange will evaluate these indicative Service Levels. If necessary, the Parties will execute an amendment to the Agreement containing the final committed RTD Service Levels. Customer will not unreasonably withhold, condition, or delay its consent to or execution of any such amendment.
Sample 1
Round Trip Delay. ‌ The RTD Service Level applies for the CPE-to-CPE RTD. (a) The RTD is measured from CPE switch to CPE switch and per Class of Service. Orange will measure the CPE-to-CPE RTD as follows: Orange will send 10 frames (each of which will be 128 bytes long) per second for 60 seconds every 5 minutes from CPE switch to CPE switch, and Orange will average the values received. (b) The Locations covered by the CPE-to-CPE RTD Service Levels will correspond to the Location pairs for the CPE-to-CPE RTD set out in Exhibit C (Customer Specific Service Levels). The CPE- to-CPE RTD Service Levels are limited to 20 Location pairs for Point-to-Multipoint connectivity. Also, if Customer has Multipoint-to-Multipoint connectivity with more than 5 CPE switches but less than 20 CPE switches, then Customer shall identify 2 CPE switches to be used for the CPE- to-CPE RTD Service Levels, and the CPE-to-CPE RTD shall be measured between the two CPE switches identified by Customer and all other Locations.. If Customer has more than20 CPE switches, multiple connectivity, or Dual Access, the CPE-to-CPE RTD Service Levels will be considered on a case-by-case basis. These CPE-to-CPE RTD Service Levels are indicative metrics only. During 3 months following the completion of the installation of Customer’s entire International Ethernet Link network, Orange will evaluate these indicative metrics and will replace them (if necessary) with the final committed CPE-to-CPE RTD Service Levels. This 3-month period will be extended to a total of 6 months in case of Service delivered in China. (c) The CPE-to-CPE RTD measurement value will be accounted for in the average monthly Service Level if the link load does not exceed 90%. (d) The actual CPE-to-CPE RTD is calculated on a monthly basis. (e) If the actual CPE-to-CPE RTD is greater than the CPE-to-CPE RTD Service Level, then Customer will be entitled to receive a credit equal to 5% of Qualifying Charges for every whole 10% by which actual CPE-to-CPE RTD is greater than the CPE-to-CPE RTD Service Level, up to a maximum credit of 20% of Qualifying Charges for the affected Location.
Sample 1
Round Trip Delay. If RTD exceeds targets listed in Section 1, SAVVIS will credit [**] of monthly billed site revenue per site on any sites connected to the affected POP, excluding local access.
Sample 1
Round Trip Delay. If RTD exceeds the Service Levels set forth above, SAVVIS will credit [**] of monthly billed site revenue per site on any sites connected to the affected POP, excluding local access. Notwithstanding the foregoing, if a Service Credit of [**] is due to Moneyline in any calendar month, and there exists a Service Failure in the same calendar month which would otherwise result in a Service Credit of [**], then the [**] Service Credit shall roll forward to the next calendar month, and shall apply [**] CONFIDENTIAL TREATMENT REQUESTED in full to the payments otherwise due from Moneyline in the next calendar month. This shall be subject to the Service Credit cap for such month. In addition to the foregoing, if a Service Credit is due to Moneyline in any calendar month, and there exists a Service Failure for the same Service in the next calendar month, then the Service Credit due to Moneyline shall be doubled. If there exists a Service Failure for the same Service in the third consecutive month, then the Service Credit due to Moneyline shall be trebled. This shall be subject to the Service Credit cap for such month. In addition to and cumulative of all other remedies available to Moneyline under the Agreement, in the event SAVVIS fails to achieve required RTD targets for any [**] month period, Moneyline may, at its sole option and upon not less than [**] prior written notice to SAVVIS, terminate the applicable Service, for the affected site, without penalty, cost or further obligation.
Sample 1
Round Trip Delay 
Sample 1Sample 2Sample 3See All (11)
AutoNDA by SimpleDocs

Related to Round Trip Delay

  • Payment Delay Notwithstanding any other terms of this Agreement, no payments will be made to CONTRACTOR until COUNTY is satisfied that work of such value has been rendered pursuant to this Agreement. However, COUNTY will not unreasonably withhold payment and, if a dispute exists, the withheld payment shall be proportional only to the item in dispute.

  • Performance Delay Time is of the essence in the Vendor’s performance of this Agreement. If at any time it appears to Vendor that it may not meet any of the performance schedules or the scheduled completion date of the services to be performed for any reason, including labor disputes, Vendor shall immediately by verbal means (to be confirmed in writing) notify Customer of the reasons for and the estimated duration of such delay. If requested by Customer, Vendor shall make every effort to avoid or minimize the delay to the maximum extent possible including the expenditure of premium time. Any additional cost caused by these requirements of Customer shall be borne by Vendor, unless the delay in performance arises out of causes beyond the control and without the fault or negligence of Vendor or its subcontractors within the meaning of the Cancellation- Default clause herein. The foregoing requirements are in addition to any of Customer’s other rights and remedies as may be provided by law or this Agreement.

  • Six-Month Delay Notwithstanding anything to the contrary in this Agreement, no compensation or benefits, including without limitation any severance payments or benefits payable under this Section 4, shall be paid to the Executive during the six-month period following the Executive’s Separation from Service if the Company determines that paying such amounts at the time or times indicated in this Agreement would be a prohibited distribution under Section 409A(a)(2)(B)(i) of the Code. If the payment of any such amounts is delayed as a result of the previous sentence, then on the first day of the seventh month following the date of Separation from Service (or such earlier date upon which such amount can be paid under Section 409A without resulting in a prohibited distribution, including as a result of the Executive’s death), the Company shall pay the Executive a lump-sum amount equal to the cumulative amount that would have otherwise been payable to the Executive during such period.

  • Delivery Delay The delivery of any certificate representing the Restricted Stock or other RS Property may be postponed by the Company for such period as may be required for it to comply with any applicable foreign, federal, state or provincial securities law, or any national securities exchange listing requirements and the Company is not obligated to issue or deliver any securities if, in the opinion of counsel for the Company, the issuance of such Shares shall constitute a violation by the Participant or the Company of any provisions of any applicable foreign, federal, state or provincial law or of any regulations of any governmental authority or any national securities exchange.

  • Six Month Delay for Specified Employees If any payment, compensation or other benefit provided to the Executive in connection with his employment termination is determined, in whole or in part, to constitute “nonqualified deferred compensation” within the meaning of Section 409A and the Executive is a “specified employee” as defined in Section 409A, no part of such payments shall be paid before the day that is six months plus one day after the Executive’s date of termination or, if earlier, the Executive’s death (the “New Payment Date”). The aggregate of any payments that otherwise would have been paid to the Executive during the period between the date of termination and the New Payment Date shall be paid to the Executive in a lump sum on such New Payment Date. Thereafter, any payments that remain outstanding as of the day immediately following the New Payment Date shall be paid without delay over the time period originally scheduled, in accordance with the terms of this Agreement.

  • Tenant Delay Except as otherwise provided in the Lease, Delivery of the Premises shall occur when Landlord’s Work has been Substantially Completed, except to the extent that completion of Landlord’s Work shall have been actually delayed by any one or more of the following causes (“Tenant Delay”): (i) Tenant’s Representative was not available to give or receive any Communication or to take any other action required to be taken by Tenant hereunder within a reasonable period of time (not to exceed 2 business days) after written request from Landlord; (ii) Tenant’s request for changes to the Building Shell, whether or not such changes are actually performed; (iii) The construction of any changes to the Building Shell requested by Tenant and agreed upon by Landlord; (iv) Tenant’s request for Change Requests (as defined in Section 4(a) below) whether or not any such Change Requests are actually performed; (v) Construction of any Change Requests; (vi) Tenant’s request for materials, finishes or installations requiring unusually long lead times (provided Landlord will request that the General Contractor inform Tenant of any long lead time items and identify substitutes for such items as soon as reasonably possible); (vii) Tenant’s delay in reviewing, revising or approving plans and specifications beyond the periods set forth herein; (viii) Tenant’s delay in providing any information that is reasonably required to come from Tenant which is critical to the normal progression of the Project within a reasonable period of time after request. Tenant shall provide such information as soon as reasonably possible, but in no event longer than one week after receipt of any request for such information from Landlord; (ix) Tenant’s delay in making payments to Landlord for Excess TI Costs (as defined in Section 5(d) below) for more than 10 business days after such Excess TI Costs are required to be paid to Landlord; or (x) Any other act or omission by Tenant or any Tenant Party (as defined in the Lease), or persons employed by any of such persons that continues for more than 1 business day after Landlord’s notice thereof to Tenant. If Delivery is delayed for any of the foregoing reasons, then Landlord shall cause the TI Architect to certify the date on which the Tenant Improvements would have been Substantially Completed but for such Tenant Delay and such certified date shall be deemed to be the Commencement Date for purposes of Tenant’s obligation to pay Base Rent, Operating Expenses, Excess TI Costs and TI Rent; however, Tenant will not have any obligation to pay any amounts to third parties pursuant to the Lease (and will not occupy the Premises) until the date upon which the Premises is Delivered to Tenant with the Landlord’s Work Substantially Complete. Upon request, Landlord shall advise Tenant of any materials, finishes or installations which are required as part of any Change Request that will result in unusually long lead times.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Equipment Failures In the event of equipment failures beyond the Administrator's control, the Administrator shall take reasonable and prompt steps to minimize service interruptions but shall have no liability with respect thereto. The Administrator shall develop and maintain a plan for recovery from equipment failures which may include contractual arrangements with appropriate parties making reasonable provision for emergency use of electronic data processing equipment to the extent appropriate equipment is available.

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.

  • Scheduled Outages (1) No later than five (5) Business Days prior to the dates required by the ISO for delivery of schedules for planned outages (which such ISO required delivery dates are currently January 15th, April 15th, July 15th and October 15th of each calendar year during the Facility Term), and at least sixty (60) days prior to the later of: (A) Initial Synchronization, or (B) SCE becoming Seller’s Scheduling Coordinator, Seller shall submit to SCE its schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty four-month period using the Web Client. If Seller fails to submit an Outage Schedule for any period as required under this Section 3.19, then Seller shall not be permitted to schedule or have any planned outages with respect to such period. The foregoing shall not prevent Seller from modifying its Outage Schedule in cooperation with SCE and the ISO. SCE shall provide Notice to Seller in the event that the ISO changes the ISO required delivery dates for schedules for planned outages. In addition, no later than thirty (30) days prior to October 15 of each year, Seller shall submit to SCE its estimate of its planned outages for the following year. (2) Seller shall provide the following information for each proposed planned outage: (A) Start date and time; (B) End date and time; and (C) Capacity expected to be online, in MW, during the planned outage. (3) Within twenty (20) Business Days after SCE’s receipt of an Outage Schedule, SCE shall notify Seller in writing of any reasonable request for changes to the Outage Schedule, and Seller shall, consistent with Prudent Electrical Practices and as permitted by the ISO, accommodate SCE’s requests regarding the timing of any planned outage. (4) Seller shall cooperate with SCE to arrange and coordinate all Outage Schedules with the ISO. (5) In the event a condition occurs at the Generating Facility which causes Seller to revise its planned outages, Seller shall provide Notice to SCE, using the Web Client, of such change (including an estimate of the length of such planned outage) as soon as practicable after the condition causing the change becomes known to Seller. (6) Seller shall promptly prepare and provide to SCE upon request, using the Web Client, all reports of actual or forecasted outages that SCE may reasonably require for the purpose of enabling SCE to comply with Section 761.3 of the California Public Utilities Code or any Applicable Law mandating the reporting by investor owned utilities of expected or experienced outages by electric energy generating facilities under contract to supply electric energy.

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