Incident Reporting Process. If an incident occurs in respect of a Client, the Operator shall promptly report the matter to AHS and shall thereafter comply with all requirements of AHS in accordance with the Incident Reporting Process set out in Schedule "D", Appendix 4.
Incident Reporting Process. The Operator will immediately put in place processes whereby all Critical Incidents are immediately reported in writing to the RHA in sufficient detail necessary to enable the RHA to fulfill any emergent responsibilities as a health authority and health care provider and to respond to the incident in accordance with the RHA’s established incident reporting process.
Incident Reporting Process. The Operator will immediately put in place processes whereby all Critical Incidents are:
Incident Reporting Process. Any U.S. Federal Government entity discovering a security incident will report it in accordance with the organization’s incident reporting procedures. NCCIC TAXII shall report security incidents to the DHS Security Operations Center (SOC). DHS SOC contact information is: • DHS OneNET Support: 1-877-DHS1NET or 0-000-000-0000 o Option 1 = NOC o Option 2 = SOC • DHS SOC Direct Line: (000) 000-0000 Individual U.S. Federal Government agencies will report incidents in accordance with their individual policies concerning incidents. Timeframes for reporting suspected or confirmed incidents are outlined in the DHS TAXII system incident response procedures and align with DHS 4300A Attachment F, Appendix F3, “Response Guidelines.” Each organization will ensure that the other connecting organization is notified when security incidents may have affected the confidentiality, integrity, or availability of the shared data or systems being accessed. Notification for security incidents will be done, at a minimum, to the appropriate SOC and the security point of contacts (POCs) listed in this Interconnection Security Agreement that companies are required to sign.
Incident Reporting Process. 3.5.1 Communicating Incidents DECE Licensee(s) will communicate incidents to Coordinator in the following manner: • DECE Licensee(s) will open trouble tickets with Customer Support. Trouble tickets can be reported via phone, e-mail, or web ticketing system at any time. Such a report shall initiate or open a trouble ticket. • DECE Licensee(s) will set the initial classification of the Severity Level of the trouble ticket based upon the criteria outlined above. Coordinator has the right to change the initial classification set by the impacted DECE Licensee(s) if the classification does not meet the criteria in Table 2. If Coordinator changes any initial classification a notification will promptly be sent to DECE Licensee with the reason for such change. If DECE Licensee(s) fail to set the initial classification of the Severity Level, then Coordinator will assign a Severity Level, based on the criteria in Table 2 and will notify DECE Licensee(s) of the Severity Level assigned. As to any incident not described in Table 2, the Parties will attempt in good faith to agree upon the final determination as to the classification of such incident and, in the event they are not able to agree, DECE Licensee(s) will determine such classification. Coordinator will generate a single response for each trouble ticket that is received from DECE Licensee(s) to acknowledge receipt of the incident notice – within 15 minutes.
Incident Reporting Process. (a) All accidents and incidents resulting in injury must be reported to the Orchestra Manager.
(b) When reporting a condition or breach of this policy:
(i) contact the Orchestra Manager to apply or resolve the issue. If the musician would like the issue to be given further consideration then:
(ii) contact your OHS representatives.
Incident Reporting Process. 5.1 The Client shall report incidents to the Supplier in accordance with the Incident Reporting Procedure.
5.2 Incident reports shall only be accepted from individuals named as part of the Authorised Contacts or as otherwise agreed in writing with the Supplier from time to time.
5.3 The Supplier shall provide a set of user accounts to the Client prior to the Go-Live Date to allow the Authorised Contacts to access the Managed Services for the purpose of logging incidents.
5.4 Incidents that are not reported to the Supplier in accordance with the Incident Reporting Procedure shall be informally investigated by the Supplier to gather more information about the incident before the incident reporting process begins.
Incident Reporting Process. 5.1.1. To report an Incident, one of the Clients’ nominated representatives will contact the Supplier’s Help Desk via telephone or email to the contact details set forth above. As well as reporting potential Incidents within the Services, the Client is to notify the Supplier whenever there is an incident within the Client’s infrastructure which could affect one or more of the Supplier’s Services.
Incident Reporting Process. Implement a process to ensure that Information Security Events are reported through appropriate management channels as quickly as possible. [***] = CONFIDENTIAL TREATMENT REQUESTED
Incident Reporting Process. The Open implementation methodology integrates throughout the project life cycle, a complete defect tracking process. This process is supported by a web tool (SAO) which manages the workflow needed to register, diagnose and resolve any incident on Open Smartflex, and provides data and dashboards related to times, severities, who is managing the incident, and in which state it is. The incident management flowchart for each type of error is described below: • Basic client data (client configuration) and operating data (converted data) errors: If, because of the diagnosis, the incident is determined to be caused by a problem in the basic data or operating data, the customer’s first-level support team must: o Report the incident to the City’s functional leader, detailing the basic data, configuration and operating data to be adjusted.
