1 / 23

Fairfax County Public Schools

Fairfax County Public Schools. Introductions. Terri Pendleton IT Service Management, Service Management Programmer Jennifer Sponheimer IT Service Management, Functional Application Specialist. About FCPS. Outside of the Nation’s Capital 11 th Largest School System 184,000 Student

sunila
Télécharger la présentation

Fairfax County Public Schools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Fairfax County Public Schools

  2. Introductions • Terri Pendleton IT Service Management, Service Management Programmer • Jennifer Sponheimer IT Service Management, Functional Application Specialist

  3. About FCPS • Outside of the Nation’s Capital • 11th Largest School System • 184,000 Student • 23,000+ Full Time Employees (400 IT)

  4. About IT Support in FCPS • Every year we see approximately 250,000 incidents/service requests via:(graphs show data 8/1/12-present)

  5. FCPS Service Catalog History2007 State of IT Service: • 200+ locations each with their own way of requesting service • Employees did not know who to contact for service, support or information Applied Solution: • HTML based service catalog with Cold Fusion forms

  6. FCPS Service Catalog History2007 – First Version • 125 services: • Redirects • Simple (CF) forms that create a Remedy INC • Self reporting uses Remedy Requester Console

  7. FCPS Service Catalog History2010 State of IT Service: • Existing services have been revised to have a consistent look and feel for customers • Still HTML based using Cold Fusion forms Solution for Moving Forward: • Conversion of all services to Kinetic

  8. FCPS Service Catalog History2010 – Next Iteration • Conversion Process • Redirect services • Simple services • Hurdles • Need to have two actions on the page that move to the request page

  9. FCPS Service Catalog2010 – Evolution with Kinetic How using Kinetic moved us forward: • Now added approvals • Questions connecting to Remedy data: • Importance of good data for integrating • Sites • People • Formatting with visual appeal on request page

  10. FCPS Service Catalog History2012 State of IT Service: • Still HTML Sub Index pages but pointing to Kinetic services • Mechanism for searching the catalog in Cold Fusion Solution for Moving Forward: • Base entirety of service catalog in Kinetic

  11. FCPS Service Catalog History2012 – Current Version • New Additions with Kinetic: • Move to using Kinetic as replacement for Remedy Requestor Console • Dynamic Requests table • Dynamic Survey and Approvals tables

  12. Successes with Kinetic • New Task Engine – more accomplished with less effort • Replacement of paper based multi level approvals • The story of EDSL • Replacement of Remedy templates with Kinetic forms • The story of BYOD

  13. The Story of EDSL • What is EDSL? • Prior method for requesting access • New method for requesting access

  14. The Story of EDSL Old - Paper New - Kinetic

  15. Successes with Kinetic • New Task Engine – more accomplished with less effort • Replacement of paper based multi level approvals • The story of EDSL • Replacement of Remedy templates with Kinetic forms • The story of BYOD • Required data easier to gather • Non support users can use as well

  16. The Story of BYOD • What is BYOD? • Prior method for reporting devices • New method for reporting devices • Required data easier to gather • Non support users can use as well • Automatically assign and resolve the ticket/multiple tickets

  17. The Story of BYOD Old - Template New - Kinetic

  18. Successes with Kinetic

  19. Lessons LearnedReporting • BYOD – Fields that do not inherently exist in Remedy • Anticipating Report requests from customers • “Generic” fields in Remedy to push Kinetic data to

  20. Lessons LearnedGathering Requirements • Customers don’t know what they don’t know • Get customers to tell us their big dreams • A service for preliminary data collection

  21. Where do we go from here?FCPS Service Catalog Future • Role based services • More and Different Data Integrations • Using Kinetic Survey to collect feedback from customers

  22. Questions?

More Related