TECHNICAL AND OPERATIONAL MATTERS Clause Samples
The "Technical and Operational Matters" clause defines the responsibilities and procedures related to the technical and operational aspects of the agreement. It typically outlines how the parties will manage technical requirements, coordinate operations, and address any technical issues that may arise during the course of their relationship. For example, it may specify standards for equipment, protocols for system integration, or processes for reporting and resolving technical problems. This clause ensures that both parties have a clear understanding of their technical and operational obligations, reducing the risk of misunderstandings and facilitating smooth collaboration.
TECHNICAL AND OPERATIONAL MATTERS a. Each party represents that the Interconnection Points set forth in Schedule 1 are, and during the term of this Agreement shall be, connected as part of an internal network architecture comprised of multiple, cross-country circuits of at least DS3 (45 Mbps) speed.
b. Neither party is obligated to accept third party routes from the other party. For purposes of this paragraph, any entity that peers with one party hereto but not with the other shall be considered a "third party." If third party routes are detected by either party, that party has the right to block the routes. The foregoing restriction shall not apply to routes of (i) Affiliates of a party, or (ii) customers whose transit traffic is carried by the other party or the other party's Affiliates. For purposes of this Agreement, "transit traffic" is traffic that a party agrees to transport to its final destination.
c. Both parties shall maintain a consistent routing announcement. Both parties will present the same autonomous system number at the Interconnection Points listed in Schedule 1.
(i) The parties will work together during the term of this Agreement to establish mutually agreed performance objectives and operational procedures to enable each party to provide the highest practical quality of service over its Internet Network and the interconnections provided hereunder, in a cost-effective fashion. In connection therewith, the parties shall make reasonable efforts to achieve a minimum end-to-end one-way packet delay.
(ii) Each of the parties will make reasonable efforts to achieve a mean time to repair of four hours or less for all outages at the Interconnection Points set forth on Schedule 1. The parties will cooperate with each other in each party's efforts under this paragraph 5.c.
(iii) Each of the parties will develop scheduled maintenance procedures that provide for notification by one party to the other of all scheduled maintenance that could cause end-to-end connectivity loss for any user of more than five minutes. Each party agrees to give the other three calendar days' advance notice for scheduled maintenance that is expected to result in 30 minutes or more of end-to-end connectivity loss.
d. Each party agrees to maintain a fully staffed network operations center ("NOC") that operates on a 24 hour/day, 7 days/week schedule.
(i) Each party will, at its own expense and on a reasonable efforts basis, provide NOC support in cooperation with the other to maintain the smooth operational ...
TECHNICAL AND OPERATIONAL MATTERS. 2.1 Each party shall have English-speaking technical support staff on duty 24 hours a day, 7 days a week.
2.2 Company shall adhere to all reasonable security and other procedures contained in this Agreement, the ITXC documentation or any materials otherwise provided by ITXC. ITXC shall notify Company of any changes to the ITXC documentation, and Company shall have 30 days after receipt of such notice to comply with the changes to the ITXC Documentation or sooner, if ITXC reasonably determines that the security of ▇▇▇▇.▇▇▇(SM) is at risk. ITXC may immediately suspend Services if Company fails to comply with the procedures set forth in Section 2 or in the Services Addendum.
2.3 If, by mutual agreement of the Parties, ITXC dispatches an agent (or agents) to a particular location to assist Company in the deployment of the Services, which assistance may include, but need not be limited to, technical support, and upon such agent's (or agents') arrival at such location, the agent (or agents') cannot provide the assistance for any reason other than a failure to perform by ITXC, including, but in no way limited to, Company's failure to provide bandwidth, utilities, additional equipment, or facilities in operable condition, then Company will pay ITXC an assistance fee (the "Assistance Fee") of $1,000 per agent per day that such agent remains at the location and cannot provide the assistance. If an Assistance Fee is warranted, it will be assessed, at ITXC's option, in one of two ways; (a) by ITXC adding it to any amount due to ITXC from Company, or (b) by ITXC deducting it from any amount due to Company from ITXC.
TECHNICAL AND OPERATIONAL MATTERS. If Microsoft and Limelight elect to exchange traffic as set forth in Section 8(a), then the Parties shall work together to establish mutually acceptable performance objectives and operational procedures to enable each Party to provide a high quality service over its network and the Interconnection Points in a cost effective manner.
TECHNICAL AND OPERATIONAL MATTERS. 4.1 Each Party will install, at its expense, all equipment within its own network reasonably necessary to provide the Services in the locations in which it is terminating calls as indicated in Attachment 1. The Parties will agree on a detailed schedule for testing, and trials of Internet Telephony Services and to use commercially diligent efforts to achieve deployment in a timely fashion.
4.2 In the event of interruption of or natural degradation of the quality of the Service, for purposes of a pre-service trial or otherwise, the Parties shall use commercially reasonable efforts to restore the normal operation of the Service with the least possible delay.
TECHNICAL AND OPERATIONAL MATTERS. Gas Quality
TECHNICAL AND OPERATIONAL MATTERS a. Each party represents that the Direct Connection Points set forth in Schedule 1 are connected as party of an internal network architecture comprised of multiple, cross-country (i.e., across the eastern, midwestern, and western portions of the United States) circuits of at least DS-3 (45 Mbps) speed. In addition, each Backbone Hub on an Internet Network shall be connected to at least two other Backbone Hubs in such Internet Network. For purposes of this Agreement, a "Backbone Hub" means a router at a major intersection of an Internet Network.
TECHNICAL AND OPERATIONAL MATTERS a. Each party represents that the Interconnection Points set forth in Schedule 1 are, and during the term shall be, connected as part of an internal network architecture comprised of multiple, cross-country circuits of at least (*) speed.
b. Neither party is obligated to accept third party routes from the other party. For purposes of this paragraph, any entity that peers with one party hereto but not with the other shall be considered a "third party." If third party routes are detected by either party, that party has the right to block the routes. The foregoing restriction shall not apply to routes of customers whose transit traffic is carried by the other party. The foregoing restriction shall also apply to any Verio Affiliates not integrated with the Verio network AS number 2914. For purposes of this Agreement, "transit traffic" is traffic that a party agrees to transport to its final destination.
TECHNICAL AND OPERATIONAL MATTERS. Unless agreed upon by both parties, the technical and operational methods of operations applied by the parties will be in accordance with the recommendations of the International of the Telecommunications Union (ITU) and any future revision of the same.