Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
Joined: Mar 14, 2005 Posts: 26 Location: Brussels, Belgium
Posted: Thu Sep 15, 2005 5:27 pm Post subject: Escalation to 2nd level
Ladies and Gentlemen,
if the 1st level helpdesk is not able to solve an Incident (no known workaround, not a known error, unsuccessfull trouble shooting, ..) and needs to escalate the incident to 2nd level support, does it then become a Problem automatically?
Posted: Thu Sep 15, 2005 6:52 pm Post subject: Re: Escalation to 2nd level
wolfhard wrote:
Ladies and Gentlemen,
if the 1st level helpdesk is not able to solve an Incident (no known workaround, not a known error, unsuccessfull trouble shooting, ..) and needs to escalate the incident to 2nd level support, does it then become a Problem automatically?
Kind regards
Wolfhard Aring
Hi,
No, it would still be an incident. However, if Servicedesk finds several incidents of the same type (e.g. your incident) Problem management would pick this up and issue a Problem record. Also, if the incident is of major impact to the IT infrastructure, a Problem record could be issued in order to find the root cause of the incident.
Your example incident could be escalated through both second and third line (and more) support without a Problem record being issued.
Joined: May 27, 2005 Posts: 79 Location: Madrid-Spain
Posted: Sat Sep 17, 2005 12:38 am Post subject: Difference between Service Desk and Incident management
Hi
I fully agree with Leif, I only want to remark about this issue that there is a difference between Service Desk and Incident management, some times this issues tracked and recorded by Service Desk are called "calls" while only those issues escalated to Incident Management are called "incidents" and afterwards as Leif explained could be raised a problem or not for problem management.
From my point of view:
Level 0 or 1 --- Service Desk
Level 2 ------- Incident Management
Level 3 ------- Problem Management
Joined: Mar 14, 2005 Posts: 26 Location: Brussels, Belgium
Posted: Tue Sep 20, 2005 1:25 am Post subject: Service Desk <--> Incident Management
Thanks for all the help.
My situation is as follows:
1st level (Support Technician with us):
* handles all incoming calls (technical as well as informational)
2nd level (Resource Technician with us):
* handles all imcoming calls (technical aswell as informational)
* assist 1st level
* manage knowledge base
* customer liason
* escalate unresolved calls/incidents to 2nd level (at client site, not with us)
--------------------------------------------------------------------------------------
2nd level (at client site not with us, different country):
* call back initial caller to resolve incident/call (not solved by 1st and 2nd level above)
* manage object/update distribution via mainframe
* liason with 3rd level support
3rd level (at client site not with us, different country):
* on-site support if necessary
* server/mainframe/DB administration
--------------------------------------------------------------------------------------
4th level (same company as client but on different continent)
* development
* root cause analysis
As you can see it is quite difficult to get everybody together
Because MantisBT is a web application and allows for different user levels (admin, user) and opening and closing of 'problems' it seems to be well suited, or not?
Even a nod into the right direction will be greatly appreciated Thanks once again.
Joined: Mar 14, 2005 Posts: 26 Location: Brussels, Belgium
Posted: Mon Sep 26, 2005 5:38 am Post subject: Incident --> Problem
Is it sufficient to look at incidents that occur frequently and incidents that have a sizeable impact on the IT environment for submittance to problem management?
Who does the actual submitting ? A first-level technician?
Joined: May 27, 2005 Posts: 79 Location: Madrid-Spain
Posted: Tue Sep 27, 2005 3:47 am Post subject: Work Around solutions
Hi Wolfhard,
It is a very good approach,
I only want to add that "work-around" solutions should not be "sent back" to Incident Management, should be stored in your knowledge data base, and of course this data base should be visible from Incident Management and Problem Management teams.
I really agree with you about the possibility of Incident Management people to open Problems, may be Incident Mangement manager should review all problems that have been arised by Incident management team, before passing this problems to problem management team for a more carefull investigation.
Joined: Nov 01, 2004 Posts: 83 Location: Sask, Canada
Posted: Tue Sep 27, 2005 6:51 am Post subject: Re: Incident --> Problem
wolfhard wrote:
Is it sufficient to look at incidents that occur frequently and incidents that have a sizeable impact on the IT environment for submittance to problem management?
Who does the actual submitting ? A first-level technician?
Kind regards
Wolfhard Aring
Oh, my interest is piqued! Are you in the process of defining the problem management role in your organization? I have found that depending on Incident volume & available manpower, it makes sense to select a sample set of incidents to follow through Problem Mgmt. Choosing your sample set could be based on frequency or impact as you suggest, if that makes sense to your organization. Other criteria might be - who is the client, or where do you see the best chance of actually getting resources to do the investigation required for Problem Mgmt? A defined sample set that is defensible provides some consistency over time for metrics. (why defensible? Because I have run into the 'why are you picking on me' stonewall, and have to prove unbiased objectivity). Here, I am able to view & select all the incidents in the current sample sets in our Incident reporting tool (Clarify) so incidents are not 'submitted' to me per se.
I am interested in understanding more of what you are trying to accomplish
Posted: Tue Sep 27, 2005 5:42 pm Post subject: Re: Service Desk <--> Incident Management
wolfhard wrote:
Thanks for all the help.
My situation is as follows:
1st level (Support Technician with us):
* handles all incoming calls (technical as well as informational)
2nd level (Resource Technician with us):
* handles all imcoming calls (technical aswell as informational)
* assist 1st level
* manage knowledge base
* customer liason
* escalate unresolved calls/incidents to 2nd level (at client site, not with us)
--------------------------------------------------------------------------------------
2nd level (at client site not with us, different country):
* call back initial caller to resolve incident/call (not solved by 1st and 2nd level above)
* manage object/update distribution via mainframe
* liason with 3rd level support
3rd level (at client site not with us, different country):
* on-site support if necessary
* server/mainframe/DB administration
--------------------------------------------------------------------------------------
4th level (same company as client but on different continent)
* development
* root cause analysis
As you can see it is quite difficult to get everybody together
Because MantisBT is a web application and allows for different user levels (admin, user) and opening and closing of 'problems' it seems to be well suited, or not?
Even a nod into the right direction will be greatly appreciated Thanks once again.
Kind regards
Wolfhard Aring
(1) Thanks Javier for confirming. I thought of a situation where all first level technicians can submit incidents to 'problem management/ manager' on their own accord.
(2) The in-house problem management will look at the incidents and try to find a solution or else escalate to second level (external customer).
(3) Maybe it is also possible to provide a reward to those technicians who submitted an incident(s) for investigation and a 'solution' has been added to the knowledge base by problem management.
eisbergsk, I have 'quoted' a previous post of mine into this response where you can see what our setup is.
I want to implement a Problem Management process that starts with an outsourced first-level service desk (that's us) and continues to technical support/ develpment teams at the customer's site.
Any comments or suggestions are always highly valued.
Kind regards
Wolfhard
Joined: Nov 01, 2004 Posts: 83 Location: Sask, Canada
Posted: Wed Sep 28, 2005 8:14 am Post subject:
Hi, Wolfhard. Your plan sounds good. The only wrinkle I can think of revolves around the gap between defining a process - and having people actually follow it! Possibly my employer has jaded my optimism. Let us know how things evolve.
Best regards,
/Sharon
Joined: Mar 14, 2005 Posts: 26 Location: Brussels, Belgium
Posted: Mon Oct 10, 2005 5:13 am Post subject: HDFS - HelpDeskFieldService Peoplesoft
Ladies and Gentlemen,
Does anybody have any experience with HDFS - HelpDeskFieldService by Peoplesoft with regards to Problem Management?
How many people would you need to do Problem Management when supporting 4-5 business critical applications, if you have about 800 Incidents per day with 30 incidents needing to be escalated to second level support per day?
Posted: Thu Aug 24, 2006 2:41 pm Post subject: Re: HDFS - HelpDeskFieldService Peoplesoft
Quote:
How many people would you need to do Problem Management when supporting 4-5 business critical applications, if you have about 800 Incidents per day with 30 incidents needing to be escalated to second level support per day?
That is 160 incidents each application. Can you pls tell how big is the user base for these applications (put together if there isn't a big difference)?
Joined: Apr 17, 2007 Posts: 36 Location: Cape Town
Posted: Tue May 01, 2007 5:20 pm Post subject:
Quote:
if the 1st level helpdesk is not able to solve an Incident (no known workaround, not a known error, unsuccessfull trouble shooting, ..) and needs to escalate the incident to 2nd level support, does it then become a Problem automatically?
Not necessarially. For example, a user cannot use an application and calls in an incident. SD cannot fix it so they call 2nd level support for the application, who determine that it seems to be a network problem, but cannot pinpoint where as the WAN is outsourced. They in turn call 3rd level support (the supplier) who tell them there is a temorpary fault on a line that will be resolved within the hour. The user is informed and one hour later the service is resumed and the incident is closed - user satisfaction verified!
So you have escalated all the way up the support ladder, but no problem record is required as the incident is considered a one-off.
However, the same outage now reoccurs at the same time every day, at which point the Service Manager will be screaming at the supplier for a root cause analysis - and this is definitely a problem record.
As for who can raise problems? Well that's up to you, but it seems logical to me that as the 1st/2nd/3rd level support staff are the frontline they should be able to raise problems. You should define some guidelines and examples for them particularly emphasising the difference between an incident and a problem. Training is key.
Also the Service manager will want to be able to raise problems, he will certainly demand RCA's even in the case of a one-off incident such as the example above.
Finally the problem management group itself should be able to identify problems from periodic reviews of the incident records. Note that problem records may also be generated automatically from software scanning the incident records or other management systems.
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
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
Thanks once again.
