Itsm

1,106 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,106
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
88
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Itsm

  1. 1. IT Service Management Mike Greene Mike Bohmbach Daniel Paulus
  2. 2. Are you ready? <ul><li>How many people are interested in a future career in some type of management? </li></ul><ul><li>How many people have a background in IT Service Management? </li></ul>
  3. 3. Scenario <ul><li>Your CIO orders your boss to a meeting and your boss decides to send you! </li></ul><ul><li>A great opportunity for your career, but also a possible set back if you are unprepared. </li></ul><ul><li>The topic of the meeting is IT service management….and you don’t know a thing! </li></ul>
  4. 4. What is ITSM? <ul><li>ITSM is a set of guidelines for different aspects of best-practice data management. </li></ul><ul><li>Split into two groups and eleven disciplines. </li></ul><ul><li>The two groups inside of ITSM are Service Delivery and Service Support. </li></ul>
  5. 5. What you will leave with today <ul><li>ITSM is aimed at the strategic level of a corporation, not the ground floor. </li></ul><ul><li>By understanding it’s main concepts, you will gain competitive advantage over others and be better prepared for a future in management. </li></ul><ul><li>ITSM is used in all companies to some degree, you can use it to improve the practice in your workplace. </li></ul>
  6. 6. Overview <ul><li>Service Delivery </li></ul><ul><ul><li>IT Financial Management </li></ul></ul><ul><ul><li>Capacity Management </li></ul></ul><ul><ul><li>Availability Management </li></ul></ul><ul><ul><li>IT Continuity Management </li></ul></ul><ul><ul><li>Service Level Management </li></ul></ul><ul><li>Service Support </li></ul><ul><ul><li>Change Management </li></ul></ul><ul><ul><li>Release Management </li></ul></ul><ul><ul><li>Problem Management </li></ul></ul><ul><ul><li>Incident Management </li></ul></ul><ul><ul><li>Configuration Management </li></ul></ul><ul><ul><li>Service Desk </li></ul></ul>
  7. 7. ITSM Service Delivery
  8. 8. Service Level Management <ul><li>Provides a way to align the IT services with the business requirements. </li></ul><ul><li>Customers and IT personnel can discuss and asses how well a service is being delivered. </li></ul><ul><li>Primary Objective: </li></ul><ul><ul><li>Provide a way for setting clear expectations with both customers and user groups </li></ul></ul>
  9. 9. Service Level Management <ul><li>The primary management of IT services </li></ul><ul><li>Service Level Management is dependent upon all the other areas of service delivery </li></ul><ul><li>Business processes associated with SLM: </li></ul><ul><ul><li>Reviewing existing services </li></ul></ul><ul><ul><li>Negotiating with the customers </li></ul></ul><ul><ul><li>Implementation of Service Improvement policies and processes </li></ul></ul><ul><ul><li>Planning for service growth </li></ul></ul><ul><ul><li>Involvement in accounting to asses costs of services </li></ul></ul>
  10. 10. Financial Management <ul><li>Financial Management includes budgeting, accounting, and charging for IT services being delivered to the customers. </li></ul><ul><li>Budgeting and accounting involves understanding the costs of providing various services </li></ul><ul><li>Financial Management ensures that any IT service proposed is justified from a budget point of view. </li></ul><ul><li>Allows IT departments to function as a business unit. </li></ul><ul><li>Allows customers to demand a value for their money. </li></ul>
  11. 11. Financial Management <ul><li>The discipline of ensuring the IT infrastructure is obtained at the most effective price </li></ul><ul><ul><li>Not necessarily the cheapest! </li></ul></ul><ul><li>Calculating the costs of providing the service so the organization can justify the costs of its IT services </li></ul><ul><ul><li>Costs can then be recovered from the customer of the service </li></ul></ul><ul><li>IT Costs can be divided into different units: </li></ul><ul><ul><li>Equipment </li></ul></ul><ul><ul><li>Software </li></ul></ul><ul><ul><li>Organization (staff, overtime, etc.) </li></ul></ul><ul><ul><li>Transfer (costs of 3 rd party service providers) </li></ul></ul><ul><li>Costs can also be divided into direct and indirect costs, and can be capital costs or ongoing costs. </li></ul>
  12. 12. Availability Management <ul><li>Main goal is to ensure the IT services are available to users when they need them. </li></ul><ul><li>Availability is usually calculated and reported as a percentage of the agreed service hours for which the service was available. </li></ul>
  13. 13. Availability Management <ul><li>Measuring availability: </li></ul><ul><ul><li>Agreement statistics – what is included within the agreed service </li></ul></ul><ul><ul><li>Availability – agreed service times, response times </li></ul></ul><ul><ul><li>Help Desk Calls – number of incidents raised, response times, resolution times </li></ul></ul><ul><ul><li>Capacity – performance timings for online transactions, report production, numbers of users, etc. </li></ul></ul><ul><ul><li>Costing Details – charges for the service, and any penalties should service levels not be met. </li></ul></ul>
  14. 14. Availability Management <ul><li>Calculating availability: </li></ul><ul><ul><li>Serviceability – when a service is provided by a 3 rd party, this is the expected availability of those components </li></ul></ul><ul><ul><li>Reliability – how long a component can be expected to perform under certain conditions without failing </li></ul></ul><ul><ul><li>Recoverability – how long it should take to restore a component back to its normal state after a failure </li></ul></ul><ul><ul><li>Maintainability – how easy a component can be maintained, which can be both corrective or preventative </li></ul></ul><ul><ul><li>Resilience – the ability to withstand failure </li></ul></ul><ul><ul><li>Security – the ability of components to withstand breaches of security </li></ul></ul>
  15. 15. Capacity Management <ul><li>Includes planning, sizing, and controlling service solution capacity to satisfy user demands. </li></ul><ul><li>This requires a collection of information about usage scenarios and patterns as well as stated performance requirements. </li></ul>
  16. 16. Capacity Management <ul><li>Inputs: </li></ul><ul><ul><li>Performance monitoring </li></ul></ul><ul><ul><li>Workload monitoring </li></ul></ul><ul><ul><li>Application sizing </li></ul></ul><ul><ul><li>Resource forecasting </li></ul></ul><ul><ul><li>Demand forecasting </li></ul></ul><ul><ul><li>Modeling </li></ul></ul>
  17. 17. IT Service Continuity Management <ul><li>Also known as contingency management </li></ul><ul><ul><li>Focuses on minimizing the disruptions to businesses caused by failure of “mission-critical” systems </li></ul></ul><ul><ul><li>Deals with planning to cope with and recover from an IT disaster </li></ul></ul><ul><ul><li>Provides guidance on safeguarding existing systems </li></ul></ul><ul><ul><li>Also considers what activities need to be taken in the event certain services are not available </li></ul></ul>
  18. 18. IT Service Continuity Management <ul><li>Basic steps: </li></ul><ul><ul><li>Prioritizing the businesses to be recovered by conducting a Business Impact Analysis (BIA) </li></ul></ul><ul><ul><li>Performing a Risk Assessment (Risk Analysis) for each of the IT Services to identify the assets, threats, vulnerabilities and countermeasures for each service. </li></ul></ul><ul><ul><li>Evaluating the options for recovery </li></ul></ul><ul><ul><li>Producing the Contingency/Recovery Plan </li></ul></ul><ul><ul><li>Testing, reviewing, and revising the plan on a regular basis </li></ul></ul>
  19. 19. IT Service Continuity Management <ul><li>Continuity management and disaster recovery are important, yet often overlooked, part of IT security and risk analysis </li></ul><ul><li>Inadequate contingency planning is looked at as a risk to the business, and is often overlooked until it is too late. </li></ul><ul><ul><li>When a security or other breach results in the loss of supporting IT systems or valuable information </li></ul></ul>
  20. 20. Part 2: ITSM Service Support
  21. 21. Service Support – Service Desk <ul><li>Service Support revolves largely around a strong service or help desk. </li></ul><ul><li>Service desks can be unskilled (used for incident tracking and call dispatching) or skilled (incidents are solved at the helpdesk). </li></ul><ul><li>Goal: </li></ul><ul><ul><li>Provide a single point of contact for the user for all their IT queries. </li></ul></ul><ul><ul><li>Proactively identify problems as well as create resolutions to incidents. </li></ul></ul>
  22. 22. Service Support – Service Desk <ul><li>Path: </li></ul><ul><ul><li>Customer needs and business needs are understood. </li></ul></ul><ul><ul><li>The service desk is an integral part of any organization, an effective service desk with strong communication can lower costs throughout the organization. </li></ul></ul><ul><ul><li>The #1 call received by a helpdesk is to help reset/restore a password </li></ul></ul><ul><ul><li>Provide alternate means to reset passwords, and other common helpdesk functions. </li></ul></ul><ul><ul><li>Answer the questions of: </li></ul></ul><ul><ul><ul><li>What permissions should the helpdesk receive? </li></ul></ul></ul><ul><ul><ul><li>What levels of expertise should the helpdesk have, and how can we train them in our organization? </li></ul></ul></ul><ul><ul><ul><li>How can we manage our lines of communication, and what happens when incidents become problems? </li></ul></ul></ul><ul><li>http://www.itil.org.uk/sm-activites.htm </li></ul>
  23. 23. Service Support – Incident and Problem Management <ul><li>Incident: Any event which is not part of the standard operation of a service and which causes, or may cause, an interruption to the quality of that service. </li></ul><ul><li>Problem: A problem is the result of multiple incidents that results in a RFC or Known Error instead of a fix. </li></ul><ul><li>Goals: </li></ul><ul><ul><li>Restore systems as quickly as possible with minimal impact to the business. </li></ul></ul><ul><ul><li>Ensure that the integrity, confidentiality, and availability of IT services are maximized throughout the organization. </li></ul></ul>
  24. 24. Incident Management Cont. <ul><li>Path: </li></ul><ul><ul><li>How do we reduce incidents and keep the organization aware of known errors? </li></ul></ul><ul><ul><li>How can we resolve RFC’s as quickly as possible? </li></ul></ul><ul><ul><li>Trend analysis, incident classification, and a healthy flow of information are all needed for good management. </li></ul></ul>
  25. 25. Service Support – Change Management <ul><li>If Change Management procedures are not effective, this may result in unauthorized changes to IT Services, which could have major impacts on the business even collapse of the business that the IT Services are there to support. </li></ul><ul><li>Goal </li></ul><ul><ul><li>Ensure that standardized methods and procedures are used for handling of changes. </li></ul></ul><ul><ul><li>Sarbanes-Oxley makes this more important than ever! </li></ul></ul><ul><li>Path: </li></ul><ul><ul><li>RFC’s should go through multiple checks and must pass some final decision making point, CAB or manager. </li></ul></ul><ul><ul><li>All RFC’s should be subjected to a routine scrutiny. </li></ul></ul><ul><ul><li>Good project management </li></ul></ul>
  26. 26. Service Support – Release Management <ul><li>Release Management is responsible for the management of software support, development, and installation. </li></ul><ul><li>Goal: </li></ul><ul><ul><li>Plan the rollout of software. </li></ul></ul><ul><ul><li>Implement procedures for the distribution of changes to the IT system. </li></ul></ul><ul><li>Path: </li></ul><ul><ul><li>Proper Release Management means to organize a way of controlling and monitoring distribution of software, often by creating a single point of storage for all software. </li></ul></ul><ul><ul><li>For internal software this also means creating a logical store to track releases, and store previous versions of software. </li></ul></ul><ul><ul><li>Create a standardized process for implementing software. </li></ul></ul>
  27. 27. Service Support – Configuration Management <ul><li>Configuration Management is a process that tracks all of the individual items in a system. A system may be a single server, or an entire IT department. </li></ul><ul><li>Goals: </li></ul><ul><ul><li>Create a list of every hardware and software item in the system and define their relationship while tracking their current status as well as their history. </li></ul></ul>
  28. 28. Service Support – Configuration Management cont… <ul><li>Path: </li></ul><ul><ul><li>Implementation of asset or configuration tracking tools such as SMS or Centurion Mangement. </li></ul></ul><ul><ul><li>There are five basic activities involved in Configuration Management: </li></ul></ul><ul><ul><ul><li>Planning – Handles the short term (three to six month) plan facing the IT department, and the changes that are to be expected. </li></ul></ul></ul><ul><ul><ul><li>Identification – This is the specification, identification of all IT components and their inclusion in the database. </li></ul></ul></ul><ul><ul><ul><li>Control – Make sure effective Change Management is in place </li></ul></ul></ul><ul><ul><ul><li>Status – Keeping the history of each item, as well as making sure that the current status of the item is up to date throughout it’s lifecycle. </li></ul></ul></ul><ul><ul><ul><li>Verification – Verification that the Item physically exists. </li></ul></ul></ul>
  29. 29. Review <ul><li>Service Support </li></ul><ul><ul><li>Change Management </li></ul></ul><ul><ul><li>Release Management </li></ul></ul><ul><ul><li>Problem Management </li></ul></ul><ul><ul><li>Incident Management </li></ul></ul><ul><ul><li>Configuration Management </li></ul></ul><ul><ul><li>Service Desk </li></ul></ul><ul><li>Service Delivery </li></ul><ul><ul><li>IT Financial Management </li></ul></ul><ul><ul><li>Capacity Management </li></ul></ul><ul><ul><li>Availability Management </li></ul></ul><ul><ul><li>IT Continuity Management </li></ul></ul><ul><ul><li>Service Level Management </li></ul></ul>
  30. 30. Things to remember… <ul><li>ITSM is the use of in-depth management techniques used to add value to IT! </li></ul><ul><li>Many companies miss this added value by not capitalizing on ITSM. </li></ul><ul><li>IT is a manageable business! Not just a bunch of computer geeks writing code! </li></ul><ul><li>View your career with this framework and you will be more prepared when you end up in a management level meeting! </li></ul>
  31. 31. Questions Dr. Hilton?

×