Common use of Problem Management Clause in Contracts

Problem Management. The purpose of this section is to set the parameters for problem management including the definition and escalation of problems. 4.1. Problem Definition and Escalation Common severity levels for the interoperation of the Data Pools and the Global Registry Support must be established. The Data Pool is required to comply with the escalation rules and communication expectations as set by the Global Registry (see Table below). The Party whose system is experiencing the issue is responsible to perform the “Action Required” unless otherwise agreed to as part of ” Getting Started” defined in section 1.2 herein or during the fault. All notifications outlined in Table One must also include the estimated time to resolution. Table One: Level 1 Critical Faults:Service interruption for any single customer on customer facing systems. Core functionality not accessible, with no work-around. Critical Faults also include issues related to Data Integrity, Confidentiality, and Security Violations. Coverage: 24x7 A broadcast message will be sent by the Party or Parties which will be implementing the corrective measure (Data Pool or the Global Registry) to the other party within 30 minutes of the fault verification and every 30 minutes thereafter until resolution is reached.

Problem Management. The purpose of this section is to set the parameters for problem management including the definition and escalation of problems. 4.1. Problem Definition and Escalation Common severity levels for the interoperation of the Data Pools and the Global Registry Support must be established. The Data Pool is required to comply with the escalation rules and communication expectations as set by the Global Registry (see Table below). The Party whose system is experiencing the issue is responsible to perform the “Action Required” unless otherwise agreed to as part of ” ”Getting Started” defined in section 1.2 herein or during the fault. All notifications outlined in Table One must also include the estimated time to resolution. Table One: Level 1 Critical Faults:: Service interruption for any single customer on customer facing systems. Core functionality not accessible, with no work-around. Critical Faults also include issues related to Data Integrity, Confidentiality, and Security Violations. Coverage: 24x7 A broadcast message will be sent by the Party or Parties which will be implementing the corrective measure (Data Pool or the Global Registry) to the other party within 30 minutes of the fault verification and every 30 minutes thereafter until resolution is reached.

Problem Management. The purpose of this section is to set the parameters for problem management including the definition and escalation of problems. 4.1. Problem Definition and Escalation Common severity levels for the interoperation of the Data Pools and the Global Registry Support must be established. The Data Pool is required to comply with the escalation rules and communication expectations as set by the Global Registry (see Table below). The Party whose system is experiencing the issue is responsible to perform the “Action Required” unless otherwise agreed to as part of ” ”Getting Started” defined in section 1.2 herein or during the fault. All notifications outlined in Table One must also include the estimated time to resolution. Table One: Level 1 Critical Faults:Service interruption for any single customer on customer facing systems. Core functionality not accessible, with no work-around. Critical Faults also include issues related to Data IntegrityInteGS1 GDSNty, Confidentiality, and Security Violations. Coverage: 24x7 A broadcast message will be sent by the Party or Parties which will be implementing the corrective measure (Data Pool or the Global Registry) to the other party within 30 minutes of the fault verification and every 30 minutes thereafter until resolution is reached.