Incident Closure. The IMT will decide when an incident is over and will make a statement declaring this. The IMT will convene a meeting following the closure of the incident, which will act as a debrief, look at any lessons learned, and consider any further preventive actions required. Following this meeting a full and final report will be prepared by the lead organisation and will be agreed by members of the IMT and Xxxxxx Health Protection Group. The report should be suitable for confidential publication and will be circulated as appropriate.
Incident Closure. 2.6.1.When the Incident has been Resolved:
Incident Closure. All Incidents will be considered closed after verbal agreement with the Customer (which will not be unreasonably withheld) or, if Orange is unable to contact Customer, within 3 Business Days of the first attempt by Orange to contact Customer.
Incident Closure. Incidents will be closed as described in section 5.3 and 5.4
Incident Closure. LYP will verify requests from the previous day have been resolved and corrections entered. The incident will be closed when LYP personnel can verify the changes in DCRIS or CAMS have been made.
Incident Closure. Following confirmation of incident acknowledgement and subject to customer validation the ITSM ticket will be closed.
Incident Closure. A2.7.1 Following the resolution phase, the vNOC Helpdesk will contact the customer within two (2) weeks to confirm case resolution and satisfaction.
Incident Closure. On resolution of an incident, the supplier should, at the earliest opportunity, inform the customer of the resolution details, which will include: • Call reference number. • Time arrived on site (if applicable). • Specific actions taken to effect a resolution. • Time of resolution. • If the resolution was a “workaround”. • How and when the “workaround” will be resolved. Note: Calls may only be closed with the agreement of the End User. A workaround solution that reinstates the service to the user(s) is acceptable within the timescales detailed within this SLA. Further action will be required in due course to implement a permanent system tested resolution. Such activities are to be managed under the original call reference number, with a reduced priority. Recurring Incidents To ensure effective long-term solutions are put in place, the supplier will demonstrate a proactive resolution methodology, recognise recurrent problems and agree a plan for detailed investigation/long-term solution to be put in place.
Incident Closure. An Incident can only be closed when the User is satisfied with the resolution or work-around that has been implemented. The process requires that: The details of the remedial action are logged in the Incident Management product and that details are concise and comprehendible, That classification of the Incident is complete and accurate according to the root cause of the Incident, That the remedial action and the resolution is agreed with the User, and That all pertinent details applicable to the specific Incident are recorded for later reference.
Incident Closure. Yes Once an incident has been resolved, the root cause and remedies of the outage will be completed via the Reason For Outage (RFO) process. The RFO report provides information such as the duration of the outage, root cause and remedies performed to resolve the outage.
