Interconnection Maintenance and Administration Plan Sample Clauses

Interconnection Maintenance and Administration Plan. Within ninety (90) days after the Effective Date, or, as agreed upon by the Parties, by the date which is not less than sixty (60) days prior to the first Interconnection Activation Date hereunder, Requesting Carrier and Ameritech shall have jointly developed a plan (the “Plan”) which shall define and detail: (a) standards to ensure that the Interconnection trunk groups provided for herein experience a grade of service, availability and quality in accordance with all appropriate relevant industry-accepted quality, reliability and availability standards and in accordance with the levels identified in Section 3.6; (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the Interconnections (including signaling) specified in Article III and the trunk groups specified in Articles IV and V, including standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery and escalation provisions; (d) the respective duties and obligations with regard to the parties’ specific interconnection architure; and (e) such other matters as the Parties may agree.
Sample 1Sample 2Sample 3See All (14)
AutoNDA by SimpleDocs
Interconnection Maintenance and Administration Plan. Within ninety (a) standards to ensure that the Interconnection trunk groups provided for herein experience a grade of service, availability and quality in accordance with all appropriate relevant industry-accepted quality, reliability and availability standards and in accordance with the levels identified in Section 3.6; (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the Interconnections (including signaling) 6275755.2 101408 910C 96252093 specified in Article III and the trunk groups specified in Articles IV and V, including standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery and escalation provisions; and (d) such other matters as the Parties may agree.
Sample 1See All (4)
Interconnection Maintenance and Administration Plan. Within ninety (90) days after the Effective Date, or, as agreed upon by the Parties, by the date which is not less than sixty (a) standards to ensure that the Interconnection trunk groups provided for herein experience a grade of service, availability and quality in accordance with all appropriate relevant industry-accepted quality, reliability and availability standards and in accordance with the levels identified in Section 3.6; (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the Interconnections (including signaling) specified in Article III and the trunk groups specified in Articles IV and V, including standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery and escalation provisions; (d) the respective duties and obligations with regard to the parties’ specific interconnection architure; and (e) such other matters as the Parties may agree.
Sample 1
Interconnection Maintenance and Administration Plan. Within ninety (90) days after the Effective Date, or, as agreed upon by the Parties, by the date which is not less than sixty (60) days prior to the first Interconnection Activation Date hereunder, Requesting Carrier and Ameritech shall have jointly developed a plan (the “Plan” ) which shall define and detail:
Sample 1
Interconnection Maintenance and Administration Plan. Within ninety (a) standards to ensure that the Interconnection trunk groups provided for herein experience a grade of service, availability and quality in accordance with all appropriate relevant industry-accepted quality, reliability and availability standards and in accordance with the levels identified in Section 3.6; 4 Since this Agreement is the result of Requesting Carrier's adoption of the Digital Teleport Agreement (as defined in footnote 9 on Signature page) the term "Effective Date" for purposes of Section 18.1 shall mean April 1, 2000. 5 Since this Agreement is the result of Requesting Carrier's adoption of the Digital Teleport Agreement (as defined in footnote 9 on Signature page) the term "Effective Date" for purposes of Section 18.2 shall mean April 1, 2000." 8822090.1 102708 1111C 96252093 (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the Interconnections (including signaling) specified in Article III and the trunk groups specified in Articles IV and V, including standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery and escalation provisions; and (d) such other matters as the Parties may agree.
Sample 1
Interconnection Maintenance and Administration Plan. Within ninety (90) days after the Effective Date,1/ or, as agreed upon by the Parties, by the date which is not less than sixty
Sample 1
Interconnection Maintenance and Administration Plan. Within ninety (a) standards to ensure that the Interconnection trunk groups provided for herein experience a grade of service, availability and quality in accordance with all appropriate relevant industry-accepted quality, reliability and availability standards and in accordance with the levels identified in Section 3.6; (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the Interconnections (including signaling) specified in Article III and the trunk groups specified in Articles IV and V, including standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery and escalation provisions; (d) the respective duties and obligations with regard to the parties’ specific interconnection architure; and (e) such other matters as the Parties may agree.
Sample 1
AutoNDA by SimpleDocs

Related to Interconnection Maintenance and Administration Plan

  • Maintenance and Support Services 3.1 Subject to Client’s timely payment of applicable Maintenance and Support fees, MRI will provide to Client the Maintenance and Support services for the Maintenance and Support plan indicated in the Order Document during the specified period. All licenses in Client’s possession must be supported under the same Maintenance and Support plan. 3.2 Updates are provided if and when available and MRI shall notify Client of the availability of such Updates solely by posting such Updates at MRI’s client support portal. MRI is under no obligation to develop any future programs or functionality. MRI is under no obligation to provide Maintenance and Support with respect to: (i) Software that has been altered or modified by anyone other than MRI or its licensors; (ii) a release for which Maintenance and Support has been discontinued; (iii) Software used other than in accordance with the Documentation or other than on a XXX; (iv) discrepancies that do not significantly impair or affect the operation of the Software; (v) any systems or programs not supplied by MRI; or (vi) Configurations. 3.3 Subject to timely payment of the applicable fees, Maintenance and Support is provided for all Software, unless otherwise noted in the Order Document, provided however that with respect to Third Party Software, MRI’s obligation is limited to using commercially reasonable endeavours to obtain Maintenance and Support from the third party owner of such Software. 3.4 Maintenance and Support starts on the Effective Date and continues through the expiration of the initial term set forth in the Order Document (“Initial Term”). Following the end of the Initial Term, Maintenance and Support and the license grant under Section 2.1 shall automatically renew for the same length as the Initial Term (each renewal a “Renewal Term”), unless either Party gives written notice at least sixty (60) calendar days prior to the end of the Initial Term or any Renewal Term, as applicable, of its intention to not renew Maintenance and Support and the license grant. The pricing for the first twelve (12) months of any Renewal Term shall be provided in writing by MRI no less than ninety (90) days prior to the end of the Initial Term or any Renewal Term. Notice to not renew the Initial Term or any Renewal Term shall be given in accordance with section 10.8 of the Master Agreement and shall be deemed given upon delivery to the non-cancelling Party. For purposes of the pricing notice in this Section only, email or first-class mail will suffice. The Initial Term and Renewal Terms are collectively referred to as the “Term”. 3.5 In the event that Client’s Maintenance and Support is not renewed and is later reinstated, a reinstatement fee shall be assessed equal to 120% of the aggregate Maintenance and Support fee that would have been payable during the period of lapse. In order to reinstate Maintenance and Support, Client must Upgrade its Software to the most current release and pay for any applicable Upgrade fees. 3.6 If ordered by Client, Maintenance and Support must be ordered for all Software and all associated License Metrics licensed by Client and its Affiliates. Client may not purchase or renew Maintenance and Support for less than all of the Software licensed by Client. 3.7 Fees for Maintenance and Support do not include implementation, training and other Professional Services, such as project management, conversion, report writing, and external systems interface development. 3.8 It is Client’s responsibility to ensure that all appropriate users receive initial training services sufficient to enable Client to effectively use the Software. Failure to do so could result in additional Maintenance and Support fees if service requests are deemed excessive as a result of insufficient training, at MRI’s discretion. 3.9 The System will need to be installed on Client’s servers and technology infrastructure. If utilizing Professional Services or Maintenance and Support in the installation of the System, Client shall ensure that MRI’s assigned technical personnel are able to access the System remotely. Client shall be responsible for providing access through any security measures it deems necessary. MRI alone shall decide whether access to the System is sufficient for Maintenance and Support purposes. Certain functionality of the System may require connections to or interaction with MRI after such System is running on Client’s infrastructure, and Client agrees to permit and facilitate such connections

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Record Maintenance and Retention A. Grantee shall keep and maintain under GAAP or GASB, as applicable, full, true, and complete records necessary to fully disclose to the System Agency, the Texas State Auditor’s Office, the United States Government, and their authorized representatives sufficient information to determine compliance with the terms and conditions of this Grant Agreement and all state and federal rules, regulations, and statutes. B. Grantee shall maintain and retain legible copies of this Grant Agreement and all records relating to the performance of the Grant Agreement, including supporting fiscal documents adequate to ensure that claims for grant funds are in accordance with applicable State of Texas requirements. These records shall be maintained and retained by the Grantee for a minimum of seven (7) years after the Grant Agreement expiration date or seven (7) years after all audits, claims, litigation or disputes involving the Grant Agreement are resolved, whichever is later.

  • Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at xxxxx://xxxx.xxxxxxxx.xxx.

  • Management and Administration 5.1 TxDOT Responsibility for Policy Decisions

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