Incident Management activities

contains

Incident Closure The Service Desk should check that the incident is fully resolved and that the users are satisfied and willing to agree the incident can be closed. The Service Desk should also check the following:

- Closure categorization

- User satisfaction survey

- Incident documentation

- Ongoing ...

Incident Initial diagnosis If the incident has been routed via the Service Desk, the Service Desk Analyst must carry out initial diagnosis, typically while the user is still on the telephone – if the call is raised in this way – to try to discover ...

Incident Investigation and Diagnosis In the case of incidents where the user is just seeking information, the Service Desk should be able to provide this fairly quickly and resolve the service request – but if a fault is being reported, this is an incident and likely ...

Incident Resolution and Recovery When a potential resolution has been identified, this should be applied and tested. The specific actions to be undertaken and the people who will be involved in taking the recovery actions may vary, depending upon the nature of the fault.

Incident categorization Part of the initial logging must be to allocate suitable incident categorization coding so that the exact type of the call is recorded. This will be important later when looking at incident types/frequencies to establish trends for use in Problem Management, Supplier ...

Incident escalation - Functional escalation

- Hierarchic escalation

Incident identification Work cannot begin on dealing with an incident until it is known that an incident has occurred. It is usually unacceptable, from a business perspective, to wait until a user is impacted and contacts the Service Desk. As far as possible, all ...

Incident logging All incidents must be fully logged and date/time stamped, regardless of whether they are raised through a ServiceDesk telephone call or whether automatically detected via an event alert.

Incident prioritization Another important aspect of logging every incident is to agree and allocate an appropriate prioritization code – as this will determine how the incident is handled both by support tools and support staff.

see publication details, table of content or references of 'Service Operation'

Source: Service Operation (OGC)

  • 4.2 Incident Management

Lernen Sie mehr über Incident Management activities in einer unserer Schulungen:



Haben Sie Fragen zu diesem Thema? Oder kön­nen wir sonst et­was für Sie tun? Unsere Experten stehen Ihnen gerne zur Verfügung:

schreiben Sie uns

Dies ist ein Teil des Body of Service Knowledge der Continental Software GmbH, zusammengetragen aus den Best Practices der ITIL und CobiT und PMBOK Frameworks, der ISO 20000 Norm, sowie aus eigener Erfahrung.

© Continental Software GmbH; ITIL® und IT Infrastructure Library® sind eingetragene Warenzeichen des Office of Government Commerce (OGC). COBIT® ist eingetragenes Warenzeichen der Information Systems Audit and Control Association (ISACA). ISO® ist eingetragenes Warenzeichen der International Organization for Standardization. PMI und PMBOK sind eingetragene Marken des Project Management Institute, Inc. Andere hier erwähnte Inhalte, Produkt- oder Firmennamen können die Warenzeichen ihrer jeweiligen Eigentümer sein.