Waiting for Problem vs Work In Progress vs Incident Resolved

[ITILDUDE]

Essentially, this topic should be under Incident Management, but I could not find such section in the forum. My first post by the way. I am looking for some experienced guidance on the following matter:

We are in the process of introducing few ITIL processes in our organization - Problem and Incident being two of them. The tool we use is ServiceNow, although the question is more process related.

Imagine the following situation - you have an Incident, no workaround is available, no permanent solution, nothing. I know, it is a rare case, but it happens. Even 3rd level of support are unable to find solution.

You decide to open a Problem ticket for more detailed investigation. Once you do that, what happens to the Incident? The argument we are having is whether it should be set to Waiting for Problem or left as Work In Progress until solution/workaround is found, or even Resolved as No Solution Found.

What is the most appropriate solution in your view and experience?

[eisbergsk]

[UKVIKING]

ITIL DUDE

You are doing IT Service Management processes regardless of whether you use ITIL to assist in the design of the process.

The tool is just that... a tool.

The purpose of Incident mgmt. is to restore service - not find the reason for the service interruption.

The purpose of problem mgmt. is to identify the unknown cause of one or more incidents.

The incident should remain open until the service is restored

The problem record will be in parallel trying to find the underlying root cause

However, the incident mgmt process must include some basic diagnosis and analystical work needed to restore the service

If as Sharon says reboot the device is the way to restore the service - do so
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter