Thanks for your interest in my posts and your feedback.
A littlebit background about myself: I've been employed within Service Management for about 10 years; most of the time with Change Management, but recently switched to Problem Management.
ICT is not the primary business process in our (manufacturing) company; so keeping the business going is more important then becoming an ITIL expert.
Yes, I've done the Foundation courses: V2.0 some years ago and V3.0 some months ago. Also passed both exams.
So I think I'm well aware of the basics. With my posts I'm trying address some practical topics for which ITIL - as a framework - doesn't provide the answers.
Like this one about workarounds to deal with issues for which I see 2 possibilities. Let me clarify with an example what I mean. Suppose your color printer ran out of red toner.
One possibility would be to prevent issues by only sending black and white prints to that printer or by using another printer.
Another possibility would be that you still send your color print to the printer, get the error message that the printer ran out of red toner and then solve this issue by adjusting the settings for this print to black an white.
So I was (and still am) wondering if both possibilities (preventing and solving) would fit in the definition of a workaround.
Indeed, "Known Resolution" is not an ITIL term (that's why I put it between quotes).
Thanks again. I'll be looking forward to any additional feedback.
I have this theory about workarounds (oooh no! Another one from MarcelBeug ). A bit philosophical though.
Consider a timeline. Somewhere on that timeline an issue starts and somewhere further ahead it ends.
Wouldn't a workaround then just be anything that was done in dealing with past issues, anything that is being done in dealing with current issues and anything that is currently being done in dealing with (preventing) future issues?
From that point of view, ITIL provides a lot of guidelines to have/get some usefull workarounds in place (instead of just doing anything).
In other words: there is always a workaround, but we'd better provide a usefull one.
Joined: Dec 30, 2005 Posts: 21 Location: Navi Mumbai, Maharashtra, India
Posted: Mon Aug 15, 2011 5:13 pm Post subject:
When it comes to true meaning of work around, it is definitely not anything that was done in dealing with incident.
In that case, for any Incident with unknown cause, re-installing the application and restoring last backup will always look like a work around. However it does not serve purpose of Incident Manager as his/her objective is to restore services as early as possible to reduce overall impact on business.
Hence In my opinion, the ‘something’
(1) that can be done (or was done in past) to restore affected services
(1) and it takes shortest possible time
(2) and that can be applied generically,
(3) and that does not have any unwanted ‘side effects’
will qualify as a true workaround.
In case of Printer toner issue you have referred,
If the business unit which uses this printer ‘must’ print in color (as a business requirement and/or as agreed in SLA), the Incident does not stand resolved unless the printer is capable of printing in color again. Setting it to print black & white will not qualify as work around.
In such business critical cases,
(1) while designing availability (and hence maintainability) the service designer would always incorporate arrangement of spare cartridge(s) to replace empty one, as soon as possible.
(2) while designing capacity, a process will be implemented to monitor consumption of Toner either automatically or manually (As mentioned by UKVIKING)
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