Posted: Fri Sep 30, 2016 12:01 am Post subject: Incident solved temp. change needed, problem??
Big discussion here at my Work. I am located in the Servicedesk and, my managers are discussing Incident/problem management. I am corious, and would love to have some people with ITIL knowledge, to give theyre thoughts on this. I will try and make it quick:
We have an incident, a powersupply has an error. An incident is created, powersupply is swapped with a temporarily one, services are back. We still need to change to an original which requires us to shut of power and cause downtime. So we need a Change. But what about the incident?
Here they discuss 2 scenarios:
1. Close incident, open change and refer to closed incident. When supply is changed and up, close change and job done.
2. Close incident, open problem and change. When supply is changed and up, close both.
What is the correct way, if any?
Joined: Sep 16, 2006 Posts: 3599 Location: London, UK
Posted: Fri Sep 30, 2016 4:09 pm Post subject:
First, there is no correct way. ITIL is a set of advice
The real answer is .. what ever is easier to manage
However, my take is as follows
1 - The incident is closed because you solved / restored service
2 - There could have been an E-cab/ retrospective change to swap out the bad power supply - depending on your change policy / process. . NOTE if there is not one, make one . If it is not clear, make it clear
3 - The change request - for the new power supply is due to the outage - which can be considered an independent change _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum