jack schmidt and mark kaletka fermilab nlit 2009

23
TRANSFORMING A HELPDESK INTO AN ITIL SERVICE DESK Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Upload: marie-ventre

Post on 30-Mar-2015

221 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

TRANSFORMING A HELPDESKINTO AN ITIL SERVICE DESK

Jack Schmidt and Mark KaletkaFermilabNLIT 2009

Page 2: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Agenda Helpdesk Assessment IT Service Management Assessment Building the Service Desk What We Did Well What We Could Have Done Better Next Steps

Page 3: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Helpdesk Evolution

Computer Room Ops

ARS to Assist

Operators

24 x7 Automatic

Alerts

Single Point of Contact

Page 4: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Helpdesk Assessment Request Management initiated review to

improve service Why doesn’t the tool work as expected? Do we have the correct skill set? Where are the metrics?

Page 5: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Helpdesk Assessment Findings Unstructured customer support

mechanism Helpdesk lives in email Drive-by / Walk-Ins

Low customer confidence Scientists frustrated with response times

Repetitive Incidents No proactive problem management

Page 6: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Helpdesk Assessment Findings Uncoordinated and unrecorded changes

No defined processes for making changes. Notification of Helpdesk an afterthought.

Lack of scale Helpdesk morphed over years Homegrown tool based around Remedy

workflow engine

Page 7: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Helpdesk Assessment Recommendations Follow ITIL Best Practices to create a

Service Desk Stop living in email! Upgrade Remedy Workflow to ITSM

software with Incident Management tool

Page 8: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

But… Issues with getting started… New management requirements:

Changed scope of improvement from Helpdesk to all of IT, with a concentration on ‘classic’ IT Services

ISO20000 (International Standard for IT Service Management) certification

Page 9: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

ISO20K Assessment Findings ISO20k certification possible in ~2.5

years (with help) Many areas of tribal knowledge Pockets of excellence Consolidation of redundant areas of IT

support will free up resources

Page 10: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009
Page 11: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Iso20K Assessment Recommendations Use consultants to guide process design

and configure tools Use Fermilab staff for process owners Use Fermilab staff to help define and

implement processes

Page 12: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009
Page 13: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

What Is a Service Desk? Objectives

Provide a single point of contact for the users

Facilitate the restoration of service within agreed service levels

Provide an interface for other activities such as Change, Problem, Configuration, Release, Service Level, Availability and Capacity Management

Page 14: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

What Is a Service Desk? Functions

Record and track incidents and service requests

Keep customers informed on request status and progress

Assess, attempt to resolve or refer Close incident and follow up with customers Proactively keep users informed of all

service outages, changes or improvements

Page 15: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Service Desk Game Plan

Page 16: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Prepare Workshop Choose Incident Management

Owner/Service Desk Manager Install tool Identify workshop participants

Subject Matter Experts Make decisions Agent of Change

Page 17: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Conduct WorkshopWhat is the Vision?

High Level Business Objectives

Where are we now? Assessments

Where do we want to be?

Measurable Targets

How do we get where we want to be?

Process Improvement

How do we check our milestones have been

reached?

Measurements and Metrics

How do we keep the momentum going?

Page 18: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Develop Policies & Procedures Identify Business Requirements Define process and procedures to

restore services Guidance to communicate new

processes Defines policy to enable a consistent

repeatable process

Page 19: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Deploy Process/Configure Tool Configure tool with requirements gathered from

workshop Provide tool and process training Hold simulations to test tool and process Communications:

Posters Electronic articles Announce at major meetings

Staff Increase staff size Plenty of technical support for Go-Live

Page 20: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

What we did well Hired a Service Desk/Incident Management

Manager Provide ITIL training for key personnel Involved the right people in the workshop! Trained support people on tool usage Increased Service Desk Staff Followed defined processes and procedures Implement process improvement

procedures

Page 21: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

What we could have done better More Process and Tool Training Build reporting structure early Staged rollout Follow up on open tickets immeadiately Better explanation of future

enhancements

Page 22: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Next Steps Self Service support Provide central notification

infrastructure Service Level Agreements into the

Service Desk tool Schedule of Changes Develop Knowledge base

Page 23: Jack Schmidt and Mark Kaletka Fermilab NLIT 2009

Questions?