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 Description Test Incident Severity Description 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 Description 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. Note: In respect of Services that are not yet in live use with DCC Service Users a...
Sample 1
AutoNDA by SimpleDocs

Related to TEST INCIDENTS

  • Data Incidents Merchant must report all instances of a Data Incident (as defined in the American Express Merchant Operating Guide) immediately to ISO after discovery of the incident. Merchant must ensure data quality and that Transaction Data and customer information is processed promptly, accurately, and completely, and complies with the American Express Technical Specifications. THE FOLLOWING SERVICES ARE PROVIDED BY ISO ONLY. Bank shall not have any obligation or liability of any nature in connection with such services. PART THREE

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Reporting Security Incidents The Business Associate will report to the County any Incident of which the Business Associate becomes aware that is:

  • Significant Incidents In addition to notifying the appropriate authorities, Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx significant incidents involving substantial disruption of Grantee’s program operation or affecting or potentially affecting the health, safety or welfare of the System Agency funded clients or participants within three (3) calendar days of discovery.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Reporting Unsuccessful Security Incidents Business Associate shall provide Covered Entity upon written request a Report that: (a) identifies the categories of Unsuccessful Security Incidents; (b) indicates whether Business Associate believes its current defensive security measures are adequate to address all Unsuccessful Security Incidents, given the scope and nature of such attempts; and (c) if the security measures are not adequate, the measures Business Associate will implement to address the security inadequacies.

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Critical Illness Three (3) days per year, with pay, shall be granted in the case of a critical illness or accident to a member of the employee's immediate family as defined in Section 9.4.2. A statement by the physician verifying the need for the employee to be present with the immediate family member shall be attached to the absence form.

Time is Money Join Law Insider Premium to draft better contracts faster.