Service/Operation Readiness Testing Sample Clauses

Service/Operation Readiness Testing. 29.8.1 In addition to testing described elsewhere in this Section 29, GTE shall test the systems used to perform the following functions at a negotiated interval and in no event less than ten (10) business days prior to commencement of GTE's provision of Local Service to AT&T, in order to establish system readiness capabilities: 29.8.1.1 All interfaces between AT&T and GTE work centers for Service Order Provisioning; 29.8.1.2 Maintenance, Billing and Customer Usage Data; 29.8.1.3 The process for GTE to provide customer profiles; 29.8.1.4 The installation scheduling process; 29.8.1.5 Network alarm reporting; 29.8.1.6 Telephone number assignment; 29.8.1.7 Procedures for communications and coordination between AT&T SPOC and GTE SPOC; 29.8.1.8 Procedures for transmission of Customer Usage Data; and 29.8.1.9 Procedures for transmitting bills to AT&T for Local Service. 29.8.2 The functionalities identified above shall be tested in order to determine whether GTE performance meets the service parity requirements and other performance standards specified in Section 11. GTE shall make available sufficient technical staff to perform such testing. GTE technical staff shall be available to meet with AT&T as necessary to facilitate testing. GTE and AT&T shall mutually agree on the schedule for such testing. 29.8.3 At AT&T's request, GTE shall provide to AT&T any results of the testing performed pursuant to the terms of this Part. AT&T may review such results and may notify GTE of any failures to meet the requirements of this Agreement. 29.8.4 GTE shall provide to AT&T the same type and quality of loop testing information that it provides to and records for itself. Where GTE develops loop testing information as a matter of course, it will make that information available to AT&T where such information is relevant to AT&T’s business. Where GTE maintains the internal discretion to test loops as needed, GTE will provide similar testing discretion to AT&T. AT&T shall pay the full cost of any such discretionary testing. 29.8.5 Within 60 days of the Effective Date of this Agreement, AT&T and GTE will agree upon a process to resolve cooperative testing issues and technical issues relating to GTE’s provision of Local Services to AT&T. The agreed upon process shall include procedures for escalating disputes and unresolved issues up through higher levels of each company’s management. If AT&T and GTE do not reach agreement on such a process within 60 days, any issues that have not b...
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Service/Operation Readiness Testing. 5.9.1 In addition to testing described elsewhere in this Section, PACIFIC shall test the systems used to perform the following functions sixty (60) days prior to commencement of PACIFIC's provision of Local Service to CLEC, in order to establish system readiness capabilities. 5.9.1.1 All interfaces between CLEC and PACIFIC work centers for Service Order, Provisioning, 5.9.1.2 Maintenance, Billing and Customer Usage Data; 5.9.1.3 The process for PACIFIC to provide customer service records; 5.9.1.4 The installation scheduling process;
Sample 1Sample 2
Service/Operation Readiness Testing. 5.9.1. In addition to testing described elsewhere in this Section, NEVADA shall test the systems used to perform the following functions sixty
Sample 1Sample 2
Service/Operation Readiness Testing. 28.9.1 In addition to testing described elsewhere in this Section, BellSouth shall test the systems used to perform the following functions in a mutually agreed upon time frame prior to commencement of BellSouth’s provision of Local Service, in order to establish system readiness capabilities: 28.9.1.1 All interfaces between AT&T and BellSouth work centers for Service Order, Provisioning; 28.9.1.2 Maintenance, Billing and Customer Usage Data; 28.9.1.3 The process for BellSouth to provide Customer profiles; 28.9.1.4 The installation scheduling process;
Sample 1
Service/Operation Readiness Testing. 11.1 In addition to testing described elsewhere in this Attachment, the Parties will test the systems used to perform the non-exclusive list of functions shown below in order to establish appropriate system readiness capabilities: 11.1.1 All interfaces between CLEC and SWBT work centers for Pre-Service Ordering, Ordering, Provisioning, Maintenance, Connectivity Billing, Local Account Maintenance, and Usage Data Transfer. 11.2 The functionalities identified above will be tested in order to determine whether SWBT’s performance meets the applicable service parity requirements and other performance standards set forth herein. SWBT will make available sufficient technical staff to perform such testing. SWBT technical staff will be available to meet with CLEC as necessary to facilitate testing. SWBT and CLEC will mutually agree on the schedule for such testing. 11.3 At CLEC’s request, SWBT will provide to CLEC any results of the testing performed pursuant to the terms of this Agreement. CLEC may review such results and may notify SWBT of any failures to meet the requirements of this Agreement and this Attachment 1: Resale. 11.4 During the term of this Agreement, SWBT will participate in mutually agreed upon cooperative testing requested by CLEC whenever it is deemed necessary by CLEC to ensure service performance, reliability and customer serviceability.
Sample 1
Service/Operation Readiness Testing. 5.9.1. In addition to testing described elsewhere in this Section, NEVADA shall test the systems used to perform the following functions sixty (60) days or less if mutually agreed to by the Parties, prior to commencement of NEVADA’s provision of Local Service to CLEC, in order to establish system readiness capabilities: 5.9.1.1. All interfaces between CLEC and NEVADA work centers for Service Order, Provisioning; 5.9.1.2. Maintenance, Billing and Customer Usage Data; 5.9.1.3. The process for NEVADA to provide customer service records; 5.9.1.4. The installation scheduling process; 5.9.1.5. Telephone number assignment; 5.9.1.6. Procedures for communications and coordination between CLEC SPOC and NEVADA’s Local Operations Center (LOC); 5.9.1.7. Procedures for transmission of Customer Usage Data; and
Sample 1

Related to Service/Operation Readiness Testing

  • Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester. 7.2.2 No later than thirty (30) Days prior to the earlier of the Scheduled Substantial Completion Date or Substantial Completion, Design-Builder shall provide to Owner for review a detailed testing plan for the Performance Tests (other than for air emissions). Owner and Design-Builder shall agree upon a testing plan that shall be consistent with the Performance Test Protocol contained in Exhibit A hereto. After such agreement has been reached, Design-Builder shall notify the Owner five (5) business days prior to the date Design-Builder intends to commence the Performance Tests and shall notify the Owner upon commencement of the Performance Tests. Owner and Independent Engineer each have the right to witness all testing, including the Performance Tests and any equipment testing, whether at the Site or at the Subcontractor’s or equipment supplier’s premises during the course of this Agreement. Notwithstanding the foregoing sentence, Owner shall bear the costs of providing a witness to any such testing and all such witnesses shall comply at all times with Design-Builder’s, Subcontractor’s or equipment supplier’s safety and security procedures and other reasonable requirements, and otherwise conduct themselves in a manner that does not interfere with Design-Builder’s, Subcontractor’s or equipment supplier’s activities or operations. 7.2.3 Design-Builder shall provide to Owner a Performance Test report (excluding results from air emissions testing), including all applicable test data, calculations and certificates indicating the results of the Performance Tests and, within five (5) business days of Owner’s receipt of such results, Owner, Independent Engineer and Design-Builder will jointly inspect such Work and review the results of the Performance Tests to verify that the Performance Guarantee Criteria have been met. If Owner or Independent Engineer reasonably determines that the Performance Guarantee Criteria have not been met, Owner shall notify Design-Builder the reasons why Owner determined that the Performance Guarantee Criteria have not been met and Design-Builder shall promptly take such action or perform such additional work as will achieve the Performance Guarantee Criteria and shall issue to the Owner another notice in accordance with Section 7.2.2; provided however that if the notice relates to a retest, the notice may be provided no less than two (2) business days prior to the Performance Tests. Such procedure shall be repeated as necessary until Owner and Independent Engineer verifies that the Performance Guarantee Criteria have been met. 7.2.4 If Owner, for whatever reason, prevents Design-Builder from demonstrating the Performance Guarantee Criteria within thirty (30) Days of Design-Builder’s notice that the Plant is ready for Performance Testing, then Design-Builder shall be excused from demonstrating compliance with the Performance Guarantee Criteria during such period of time that Design-Builder is prevented from demonstrating compliance with the Performance Guarantee Criteria; provided however that Design-Builder will be deemed to have fulfilled all of its obligations to demonstrate that the Plant meets the Performance Guarantee Criteria should such period of time during which Design-Builder is prevented from demonstrating the Performance Criteria exceed thirty (30) Days or extend beyond the Final Completion Date.

  • ODUF Testing 6.6.1 Upon request from TWTC, AT&T shall send ODUF test files to TWTC. The Parties agree to review and discuss the ODUF file content and/or format. For testing of usage results, AT&T shall request that TWTC set up a production (live) file. The live test may consist of TWTC’s employees making test calls for the types of services TWTC requests on ODUF. These test calls are logged by TWTC, and the logs are provided to AT&T. These logs will be used to verify the files. Testing will be completed within thirty (30) days from the date on which the initial test file was sent.

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (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 Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer 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. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act. (B) All classes covered by this Agreement are designated special risk classes for drug testing purposes. Special risk means employees who are required as a condition of employment to be certified under Chapter 633 or Chapter 943, F.S. (C) An employee shall have the right to grieve any disciplinary action taken under section 112.0455, the Drug-Free Workplace Act, subject to the limitations on the grievability of disciplinary actions in Article 10. If an employee is not disciplined but is denied a demotion, reassignment, or promotion as a result of a positive confirmed drug test, the employee shall have the right to grieve such action in accordance with Article 6.

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Alcohol Testing Alcohol testing will be conducted by using an evidential breath-testing device (EBT) approved by the National Highway Traffic Safety Administration. A screening test will be conducted first. This initial screening may be accomplished using a saliva test kit. If the result is an alcohol concentration level of less than 0.02 percent, the test is considered a negative test. If the alcohol concentration level is 0.02 percent or more, a second confirmation test using the EBT will be conducted. The procedures that will be utilized by the lab for collection and testing of the specimen are attached hereto as Appendix A.

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