John Ca
- hn Carter
ter
Cit City y of
- f Ot
Ottaw tawa
John Ca ohn Carter ter Cit City y of of Ot Ottaw tawa My - - PowerPoint PPT Presentation
John Ca ohn Carter ter Cit City y of of Ot Ottaw tawa My Organization Cit ity of Ottawa 15,000 Clients Over 100 lines of business 400 different locations 300 full-time ITS staff My Position Information Technology Services
Cit City y of
Ottaw tawa
15,000 Clients Over 100 lines of business 400 different locations 300 full-time ITS staff
Information Technology Services
My team Operational support
➢Marval Service Management
➢City of Ottawa has been a client for over 10 years ➢Fits the need for ITS and for Non-IT clients ➢We are making rapid improvements with our Marval toolset
➢Many organizations find CMDB population challenging
➢We support increasingly complex systems ➢Agile development and rapidly changing technology presents challenges
➢Utilize CSI principles when improving Configuration Management
➢Incremental improvement ➢Separate technical assets into separate CI types ➢ Start with infrastructure layer
DB Applications Network Devices Telecom Devices PC/Laptops Servers
Metadata Relationships
➢Link Configuration Management to Request Fulfillment, Incident Management, Change Management
➢Make CI attachment to requests mandatory ➢Technology changes too quickly to wait for a separate Configuration Management update process or CI audit to catch the data change
Metadata Relationships
➢We traditionally think of CIs as technical assets ➢Think of them as entities / artifacts that have relationships to one another
➢Relationship could be a technical dependency, or a business dependency
➢How do I know if an asset could / should be managed in the CMDB?
➢Think about what it means if it were to be removed
➢Match the experience with their personal lives
Purchasing IT Goods Searching for content Self-Serve Problem Solving
➢Change Management processes are typically so rigid and laborious that IT staff are hesitant to comply
➢Find an appropriate level of rigour
➢Service Management tools typically don’t make the RFC logging process intuitive and user friendly
➢Investigate ways to make the tool user friendly ➢Change initiators are your users, treat them the way you would other clients
Simple process with 3 key elements:
➢Make sure your solution has your identity, your philosophy
➢Create a Brand
➢Clients should feel the service is coming from YOU, not the tool
➢Client notifications and surveys ➢Self-Service Portal or Service Catalogue
➢Helps partnership with other IT teams
➢Remove ego, remove biases ➢Integrate to leverage what’s available to provide the best service
➢Walk in Service Centre shared the branding ➢URL to get to our online “IT Service Centre” was simply http://its
➢All of ITS is now branded as “City Tech” ➢Online self service presence now known as “City Tech Portal”
➢No excuses any more with open source concepts and integration focus
➢Enhancing the tool is a must
➢You must grow with your Service Management tool
➢Activate unused functionality ➢Don’t be afraid to push the vendor
Get support from vendor because we’re using their framework Increase your buy in internally because you are solving business challenges
Operational work Project work
Plugin Framework
➢Reporting will be your top value realized ➢Ensure the tool is broad & diverse to get the reports you need
➢Flexible enough to have dashboards ➢Abstracts away technical nuances on backend
➢Focus should be ease to get at data and making reporting easy
➢Same people who develop the data model should produce reports
➢Don’t let reporting be an afterthought
➢Don’t wait until people ask for reports ➢Make reporting part of initial business requirement intake ➢Have relevant metadata fields and classification
Talking to ITSM people is like going to the dentist...it’s a necessity but no one wants to do it… But you still have the opportunity to have happy clients…
➢Build relationship with those you build processes & solutions for ➢Build trust
➢When approached with ideas ➢Listen to the audience ➢Look for opportunities to address challenges and business problems ➢Do some market research
Common Language Common Language
➢Tier 0 support level offers automated or self-service solutions where users can help themselves ➢There are various levels of maturity in a Tier 0 implementation
➢Self-service presence ➢Add classification / routing to self-service ➢Self-help articles on self-service platform ➢Self-help videos (hosted or linked) ➢Text chat (with some form of AI) ➢Virtual Support Agent
*based on 2018 trend analysis
➢Why the Marval ITSM tool has worked for them:
➢Request Type Segregation ➢Flexible Licensing model ➢Classification ➢Request attributes / Metadata ➢Reporting
➢Service Management as an integrated solution
➢HR / Payroll / ITS SAP integration ➢ITS and Supply integration
➢Renewable Contracts as CIs
➢Unification of business processes ➢Centralization management of solution
➢You already have the expertise
1) Don’t Give Up On Your CMDB 2) Re-think the Scope of Configuration Management 3) Make Your Consumable Services Sexy 4) Create an Easy to Follow Change Management Process 5) Don’t Let the Tool Dictate the Brand of Your Service 6) Don’t Be Afraid to Be Creative 7) Reporting, Reporting and More Reporting 8) Build a Trust Model 9) Get Serious About Tier Zero Support 10)Go Enterprise Wide with Service Management