TEST INCIDENTS Sample Clauses

TEST INCIDENTS. 12.1 Where a Test Report identifies a Test Incident, the parties shall agree the classification of the Test Incident using the following criteria for Test Incident Severity: Test Incident Severity 1 An Incident which:  would prevent a DCC Service User from using the DCC Service User Systems and/or any DCC Services;  would have a critical adverse impact on the activities of the DCC;  would cause significant financial loss and/or disruption to the DCC Services; or  would result in any material loss or corruption of Data. Non-exhaustive examples:  an Incident leading to non-availability of the Services, the DCC Services, the DCC Data Services or the SMWAN; or  all Test progress is blocked. Test Incident Severity 2 An Incident which:  would have a major (but not critical) adverse impact on the activities of the DCC but the service is still working at a reduced capacity; or  would cause limited financial loss and/or disruption to the DCC. Non-exhaustive examples:  an Incident leading to non-availability of or to loss of resilience of a material part of the Services (such as a Prime CSP's network management centre, the DSP's security operations centre, the SMWAN, or any of the DCC Interfaces & Gateways);  large areas of functionality will not be able to be tested; or  Testing not completely blocked but has been significantly impacted. Test Incident Severity 3 An Incident which:  would have a major adverse impact on the activities of the DCC but which can be reduced to a moderate adverse impact through a work- around; or  would have a moderate adverse impact on the activities of the DCC. Non-exhaustive examples:  Testing can progress but the work-around will impact Test progress. Test Incident Severity 4 An Incident which:  would have a minor adverse impact on the activities of the DCC. Non-exhaustive examples:  minor service interruptions in the business process; or  minor service interruptions in the functionality of the DCC Environment and / or DCC Services. Test Incident Severity 5 An Incident which:  would have minimal impact on the activities of the DCC. Non-exhaustive examples:  trivial incidents with work-arounds which are noted for future releases but minimal impact of running existing Services; or  Tests can still pass but there are cosmetic issues. 12.2 Unless otherwise agreed: (a) the Contractor’s Test Incident Management Log shall log Test Incidents to reflect the Test Incident Severity classifications allocated to each Test Incid...
Sample 1
AutoNDA by SimpleDocs

Related to TEST INCIDENTS

  • CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.

  • 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.

  • Outputs Analogue and digital outputs of protected content are allowed if they meet the requirements in this section and if they are not forbidden elsewhere in this Agreement..

  • Positive Test Results In the event an employee tests positive for drug use, the employee will be provided, in writing, notice of their right to explain the test results. The employee may indicate any relevant circumstance, including over the counter or prescription medication taken within the last thirty (30) days, or any other information relevant to the reliability of, or explanation for, a positive test result.

  • 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.

  • Test Results The employer, upon request from an employee or former employee, will provide the confidential written report issued pursuant to 4.9 of the Canadian Model in respect to that employee or former employee.

  • Contract Goals A. For purposes of this procurement, OGS conducted a comprehensive search and determined that the Contract does not offer sufficient opportunities to set goals for participation by MWBEs as subcontractors, service providers, or suppliers to Contractor. Contractor is, however, encouraged to make every good faith effort to promote and assist the participation of MWBEs on this Contract for the provision of services and materials. The directory of New York State Certified MWBEs can be viewed at: xxxxx://xx.xxxxxxxxxxxxxx.xxx/FrontEnd/VendorSearchPublic.asp?TN=ny&XID=2528. Additionally, following Contract execution, Contractor is encouraged to contact the Division of Minority and Women’s Business Development ((000) 000-0000; (000) 000-0000; or (000) 000-0000) to discuss additional methods of maximizing participation by MWBEs on the Contract. B. Good Faith Efforts Pursuant to 5 NYCRR § 142.8, evidence of good faith efforts shall include, but not be limited to, the following: 1. A list of the general circulation, trade, and MWBE-oriented publications and dates of publications in which the Contractor solicited the participation of certified MWBEs as subcontractors/suppliers, copies of such solicitations, and any responses thereto. 2. A list of the certified MWBEs appearing in the Empire State Development (“ESD”) MWBE directory that were solicited for this Contract. Provide proof of dates or copies of the solicitations and copies of the responses made by the certified MWBEs. Describe specific reasons that responding certified MWBEs were not selected. 3. Descriptions of the Contract documents/plans/specifications made available to certified MWBEs by the Contractor when soliciting their participation and steps taken to structure the scope of work for the purpose of subcontracting with, or obtaining supplies from, certified MWBEs. 4. A description of the negotiations between the Contractor and certified MWBEs for the purposes of complying with the MWBE goals of this Contract. 5. Dates of any pre-bid, pre-award, or other meetings attended by Contractor, if any, scheduled by OGS with certified MWBEs whom OGS determined were capable of fulfilling the MWBE goals set in the Contract. 6. Other information deemed relevant to the request.

  • Temperature Measurement Temperature will be measured by the nearest automatic Melbourne Bureau of Meteorology Monitoring Station for example (but not limited to): Melbourne, Moorabbin, Dunns Hill, Melbourne Airport, Frankston, and Point Xxxxxx. At the commencement of each project, the onsite management and employee representatives shall agree which is to be the applicable automatic weather monitoring station.

  • Corrective Measures If the Participating Generator fails to meet or maintain the requirements set forth in this Agreement and/or the CAISO Tariff, the CAISO shall be permitted to take any of the measures, contained or referenced in the CAISO Tariff, which the CAISO deems to be necessary to correct the situation.

  • Performance Measure Grantee will adhere to the performance measures requirements documented in

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