1. ITSM Status: Metrics,Problem Management, FUSION12 and the ITSM Program Page ITS Quarterly Staff Meeting Friday November 30 th 2012 ITS Team

2. Overview ITSM Program Status Process Metrics Problem Management Fusion12 Conference ITSM Program Page

3. ITSM Program Status

4. Interim Major Incident Process Jan ‘10 Interim Major Change Process Feb ‘10 Distinguished Incidents vs Requests Apr ‘10 MIS trained in ITIL Foundations Apr-Nov ’10 Teams Designed Incident, Request, and Problem Management Processes 2011 MPD IT trained ITIL Foundations Jul-Oct ‘11 ITSM Program highlights (1/3)

5. Change Management Process Oct ‘11 Incident and Request Processes Feb ‘12 Change Process (CSI) Mar ‘12 Project Management integration Mar ‘12 High level Metrics for Incident Apr ’12 Internal Process Maturity Assessment Jul ‘12 ITSM Program highlights (2/3)

6. ITSM aligned ITSD reorg Jul ‘12 Upgrade KBOX to 5.3 Jul ‘12 Major Incident Process (CSI) Aug ‘12 MPD service staff using KBOX Aug ‘12 CSI Register established Oct ’12 Org Sections in ticket report Nov ’12 Incident Volume metric drill down by ITS Sections and Service Categories Nov ’12 Problem Management Process Jan ’13 ITSM Program highlights (3/3) Since the Aug ’12 Staff meeting Soon

7. ITSM Program What’s Next (1/2) Implementation sequence mostly TBD Change Management (CSI) APFY12 Remaining Metrics for Incident Process Metrics for Request & Project Service Asset & Config. Process APFY12,13  IT Asset Management Process APFY12,13 Event Management Process

8. ITSM Program What’s Next (2/2 Implementation sequence TBD Service Level Management Process APFY13 Release and Deployment Process APFY12 Continual Service Improvement APFY12 Customer Service Portal Info. Security Management Process APFY12,13 Knowledge Management Process KBOX 5.4 Upgrade (release in Dec) Acquire and implement real ITSM support tool More

9. ITSM Program Status conclusion We’ve done a bunch All working together Plenty available yet to be done Figuring out what is possible and best value for next step(s)

10. Process Metrics

11. Process Metrics Since Oct 2011 for Change Since Feb 2012 for Incident (high level) Last reviewed at Aug 10 th staff meeting

12. Change Management Metrics

13. Big volume increase for October

14. performance metrics OK Closed Unsuccessful Emergency Triggered Incident Closed Cancelled

15. Incident Management Metrics

16. Caveats, Constraints & Next steps Caveats  Still early in development of Incident metrics  Data not information  Don’t draw conclusions Constraints  Volume of closed incidents vs time (month)  Closed Incidents only  Incident Start date only Next steps  Raise questions  Take next steps in Incident metric development

17. Resolved on first contact dipped in September and October

18. All ITS Sections.

19. Applications and Information Management Section (Susan’s team)

20. Customer Services and Support (Leecia’s Team)

21. Technology Operation Services (Bill Conant’s team)

22. Drilling in on a Service Category. SAN Admin hit a 38 ticket peak in June.

23. Answers but more Questions Answers  What’s breaking  Who’s fixing it  How Incident volume trends over time Questions / Next steps  How long is it taking to fix stuff? Incident Duration metric is next  Are incident tickets getting closed? Ticket aging reports

24. Problem Management

25. The Team (not the problem) The Problem Management Team:  Thatcher – Project Manager  Bill Conant – Problem Process Owner  Grace and Sonia Team members  Lynn and Ricky (first PM team members)

26. Problem Management: the Missing Piece What is it? What isn’t it? Why do we need it? How are we doing PM today? What will we have to do differently? When does PM go live?

27. PM: What is it? Process to detect, prioritize, and permanently resolve the unknown cause of recurring Incidents Process to detect and resolve situations before they cause Incidents

28. Incident vs Problem Management Review Incident Management  Restoring broken service(s) ASAP Problem Management  Identifying and permanently resolving the cause of Incidents

29. PM: What isn’t it? Problems are not a more important type of Incident A Problem is not a higher priority Incident A Problem is not any type of Incident Repeat after me …. Problems are not just about technology  It’s also about People, Policy, Process

30. PM: Why do we need it? To reduce recurring Incidents To stop Incidents before they happen To have a prioritized, multi pronged process of attack on lingering stuff Ensure that Problem workarounds are available to staff Complete Incident process Improve Change success Get rid of the red! Example: Service Availability

31. PM: How are we doing PM today? Mostly we aren’t doing it Where we are doing PM, its not tracked well:  Putting PM information into individual Incident tickets  People’s brains Started a tracking ticket in KBOX for candidate Problem tickets

32. PM: What will we have to do differently? Consult Problem list when creating Incident tickets  To determine if incident needs to be associated to an existing Problem  To share & apply workarounds in related Problem ticket Section Heads only – Create, assign and prioritize Problem Tickets per Section  Intended to hold the volume of Problems to a feasible level Some staff – Work assigned Problem ticket(s)

33. When does Problem Management Go Live? After the PM process description is complete After KBOX support for PM is developed and tested Probably January ’13

34. FUSION 12 Conference

35. IT Service Management Foundation (USA) and Help Desk International

36. Largest USA ITSM Specific Conference Two and half days Seventy-two regular sessions Fifteen Breakfast briefings By spreading out we attended 1/3 of all sessions And of course the vendors…. Lasting knowledge resource  Summary presentation posted  All session presentations available off line

37. Top Takeaways We are on the right track We implemented processes in reasonable order We’ll always be learning … COBIT 5, ISO 20000 Need to make our own decision what’s next Ready to think about real ITSM support tool  Aligned tool can accelerate process delivery  Improve integration and workflow  Request intake support  Pre build metrics

38. ITSM Program Page

40. How to find this page Navigate Home > Feature Links > Departments > Department of Management > IT Services Division > IT Service Management (ITSM) Program HomeFeature LinksDepartments Department of ManagementIT Services Division Search ITSM Bookmark in FF Toobar  Recommended Desktop Shortcut Take your pick

41. What’s there Process templates and examples  RFC, Project Charter FAQ  KBOX and Processes How do I …A – Z.  KBOX and email IT Policies Process Executive Summaries Process Flowcharts Process Procedures (KBOX step by step)

42. Wait, there’s more Customer Survey, Internal Assessments Presentations  From prior Staff Meetings  Key Concepts  New Process Rollouts Training gateway to SkillSoft  ITIL Foundations supporting material  Jumpstart presentations

43. Process and KBOX FAQRFC Project Charter templates and examples Presentations, Policies and Training

44. KBOX Process FAQ

47. How to find this page Navigate Home > Feature Links > Departments > Department of Management > IT Services Division > IT Service Management (ITSM) Program HomeFeature LinksDepartmentsDepartment of ManagementIT Services Division Search ITSM Add to FF Bookmarks Toolbar  Recommended Desktop Shortcut http://hi-mauicountyintranet.civicplus.com/index.aspx?NID=737 Take your pick

48. End of Presentation ITSM Program Status Process Metrics Problem Management Fusion12 Conference ITSM Program Page Questions? Comments.

49. Revision History 11/16/2012 TDeane Got place holders in for all the sections. Missing summary page for Fusion12 and Process Asset Library screen shots. 11/21/2012 T with B. Conant revised Fusion12 slides. 11/21/2012 B.Conant revised PM slides ever so slightly 11/26-27/2012 T Deane added animations and made adjustments based on 11/21 preview with Jacob. 11/28/2012 T Deane added animations to PAL section and screen shots from FAQs. Also latest Incident Volume Graphs with ‘open’ line …. Shows very low % of open tickets.

50. Slides not used