| View previous topic :: View next topic |
| Author |
Message |
abu1
Itiler
Joined: Oct 26, 2011
Posts: 30
|
 Posted: Thu Apr 26, 2012 1:40 am Post subject: Pro-active problem management techniques |
 |
|
| Apart from looking at trends and reports what are other good ways to pro-activley look for problems.. |
|
| Back to top |
|
 |
UKVIKING
Senior Itiler
Joined: Sep 16, 2006
Posts: 3110
Location: London, UK
|
| Posted: Thu Apr 26, 2012 2:51 am Post subject: |
|
|
Hmmm
if you have microsoft as an operating system
you will have problems
Make sure your o/s and ios patch mgmt process is keepign the systems up to date
find single points of failure
make sure the DR plan is fit for purpose
review the incident tickets for patterns of outages
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter |
|
| Back to top |
|
|
elbow
Itiler
Joined: Feb 14, 2011
Posts: 33
|
| Posted: Thu Apr 26, 2012 4:48 pm Post subject: |
|
|
| Set up a weekly meeting with the engineers, people at the sharp end. They can give alot more insite than looking at reams of incidents. Also if the service desk is not profficient, this could mean the categorisation of Incidents is incorrect and even closure details wrong therefore throwing your trending into confusion. |
|
| Back to top |
|
|
Diarmid
Senior Itiler
Joined: Mar 04, 2008
Posts: 1883
Location: Newcastle-under-Lyme
|
| Posted: Thu Apr 26, 2012 6:54 pm Post subject: |
|
|
If you find that the categorization of incidents is not correct or reliable, then you should immediately open a problem to investigate and resolve that issue and this should have a high priority.
Looking for patterns amongst incidents is more often going to identify problems than merely looking at trends, and while talking to staff groups working at the sharp end can be rewarding, it will be much more so if you are armed with patterns and trends you have discerned for yourself.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718 |
|
| Back to top |
|
|
abu1
Itiler
Joined: Oct 26, 2011
Posts: 30
|
| Posted: Thu Apr 26, 2012 7:27 pm Post subject: |
|
|
| UKVIKING wrote: | Hmmm
if you have microsoft as an operating system
you will have problems
Make sure your o/s and ios patch mgmt process is keepign the systems up to date
find single points of failure
make sure the DR plan is fit for purpose
review the incident tickets for patterns of outages |
Company has recently completed project called SCOM which is a microsoft tool which provides alerts real time on condition of servers and hardware like HDD ,CPU and also software issues conflicts etc.
I agree if incident are not categorized properly then it makes trend analysis based on incident reports hard.. |
|
| Back to top |
|
|
elbow
Itiler
Joined: Feb 14, 2011
Posts: 33
|
| Posted: Thu Apr 26, 2012 7:59 pm Post subject: |
|
|
| Well i am at present looking at a cross section of Incident details over time to build a case for the mis-categorisation in fact and because of ther SD immaturity it has been sometimes more effective in my case to talk to other functions |
|
| Back to top |
|
|
UKIT
Itiler
Joined: Sep 26, 2007
Posts: 36
Location: England
|
| Posted: Fri Apr 27, 2012 11:31 pm Post subject: Re: Pro-active problem management techniques |
|
|
| abu1 wrote: | | Apart from looking at trends and reports what are other good ways to pro-activley look for problems.. |
I was involved with an incident resulting in the loss of IT services due to a simple server configuration oversight
A server designed to accommodate duel hot pluggable redundant power supplies had only been fitted with one.
The power supply failed resulting in the loss all IT services being hosted from this server.
A new power supply had to be sourced as a matter of urgency in order to restore full IT services.
Assigned to establish the root cause, it didn’t take long to see how this simple “oversight” could have been so easily avoided.
With a duel power supply configuration, a single power supply can fail without disrupting the live service.
A project to undertake a complete survey of the datacentre to indentify single points of failure (SPOF) was instigated.
The project also looked at servers configured with a single network cards where multi homed fault tolerance network card configurations could be implemented.
_________________
Change Management
"Bringing order to chaos" |
|
| Back to top |
|
|
|
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
