Docstoc

Service Improvement - PowerPoint

Document Sample
Service Improvement - PowerPoint Powered By Docstoc
					Service Improvement
Part 3 The Strategic View
Robert.Gormley@ed.ac.uk http://www.is.ed.ac.uk/itil

Service Management “House”
Customers

Service Level Mgmt
Avail. Mgmt Capacity Mgmt Continuity Financial Mgmt Mgmt Service Delivery

Incident Mgmt Users SD

Problem Mgmt

Change Mgmt

Release Mgmt Service Support

Configuration Mgmt Part 1 – The Frontline Part 2 – Making Changes Part 3 – The Strategic View

Programme
• Service Support Recap • Service Level Management • Financial Management

• Coffee
• Capacity Management • Availability Management • Service Continuity Management • Where Now & Questions

Frontline Recap
The Service Desk handles Incidents and Service Requests. Incidents are caused by Problems and Known Errors. Problems are investigated to produce Workarounds and thus become Known Errors. Known Errors are investigated to produce Requests For Change.

Making Changes Recap
RFCs are assessed and approved by Change Management. Once approved, the Change is built, tested and implemented by Release Management. Release Management takes a holistic view of the Change. The Configuration Management Database underpins all other Service Management disciplines.

Service Level Management Goal
• To maintain and gradually improve business aligned Service quality, through a constant cycle of agreeing, monitoring, reporting and reviewing Service achievements and through instigating actions to eradicate unacceptable levels of Service.

SLM Process
Customer Demand
Service Level Requirements

Identify Needs
Define Service Create Agreements

Service Specification

Service Quality Plan

Service Catalogue Operational Level Agreement

Service Level Agreement Underpinning Contract

Monitor Service Report on Service Review Service
Service Level Reports Service Improvement Programme

Customer Demand
• Goal is services aligned with business, hence services driven by customer demand • Demand may be informed by the Service Catalogue

Definitions 1
• Service Catalogue
A database or structured document with information about all Services, including those available for deployment. The Service Catalogue is published to Customers, and is used to support the marketing and delivery of Services. The Service Catalogue includes information about deliverables, prices, contact points, ordering and request processes.

Service Catalogue
• Written from customer perspective
– End to end view of services – In customer language (not service speak)

• Ideally interactive (online ordering?) • Customer view into the CMDB as includes relationship information • Linked to greater detail, e.g. Service Level Agreements

Identify Needs
• Customers may require assistance in articulating needs • Service Level Management aims to build relationship with customer
– Partnership, dialogue, alignment

• Needs are documented in Service Level Requirements

Definitions 2
• Service Level Requirements (SLR)
A Customer requirement for an aspect of a Service. SLRs are based on business objectives and are used to negotiate agreed Service Level Targets.

• Service Level Target
A commitment that is documented in a Service Level Agreement. Service Level Targets are based on SLRs, and are needed to ensure that the Service design is fit for purpose. Service Level Targets should be measurable, and are usually based on Key Performance Indicators.

Definitions 3
• Key Performance Indicator (KPI)
A metric that is used to help manage a Process, Service or Activity. Many metrics may be measured, but only the most important of these are defined as KPIs and used to actively manage and report on the Process, Service or Activity. KPIs should be selected to ensure that efficiency, effectiveness, and compliance are all managed.

SMART Metrics Specific – Objectives should specify what they want
to achieve.

Measurable – You should be able to measure
whether you are meeting the objectives or not.

Achievable - Are the objectives you set, achievable
and attainable?

Relevant – Are they aligned with the plan, mission

or vision (business, customer or service provider)? set objectives?

Timely – When do you want to achieve the

Define Service
• Armed with customer’s SLRs, service specification drawn up
– In service language – In sufficient technical detail to permit costing, assessment and approval

• Draft Service Quality Plan created
– Includes Key Performance Indicators for all processes – Used to measure service based on SLRs

Create Agreements
• Service Catalogue • Operational Level Agreement
– Internal agreement with “backroom” teams

• Underpinning Contract
– Legal agreement with external partner

• Service Level Agreement
– Agreement with customer – Built upon OLAs and UPCs

Definitions 4
• Operational Level Agreement (OLA)
An agreement between a Service provider and another part of the same business that provides Services to them. For example there could be an OLA with a facilities department to provide air conditioning, or with the procurement department to obtain hardware in agreed times. An OLA may also be between two parts of the same Service Provider, for example between the Service Desk and a Support Group.

Definitions 5
• Underpinning Contract (UPC)
A Contract between a Service provider and an external organisation. The external organisation provides goods or Services that support delivery of a Service to a Customer. The Underpinning Contract defines targets and responsibilities that are required to meet agreed Service Level Targets in an SLA.

Definitions 6
•Service Level Agreement (SLA)
An agreement between a Service provider and a Customer. The SLA describes the Service, documents Service Level Targets, and specifies the responsibilities of the Service provider and the Customer. A single SLA may cover multiple Services or multiple Customers.

Agreement Differences
Language
SLA OLA UPC

Parties
Service Provider & Customer Internal Service Providers Service Provider and External Organisation

Legal

Customer Service Service

No No Yes

Monitor Service
• Monitor for effectiveness, efficiency and compliance • Effectiveness = meeting Service Level Targets, KPIs and functional requirements (what we do) • Efficiency = processes (how we do it) • Compliance = non-functional requirements (company policies, laws, code of practice)

Report on Service
• To Customer
– hence customer language – on areas of customer interest
• usage, service level targets, etc

• To Service provider
– on efficiency, compliance, cost (& profitability?)

Review Service
• • • • Regularly (on demand?) Were service level targets met? Identify any trends Develop Service Improvement Programme • Review Service Level Requirements • Negotiate changes to maintain alignment with business

Outputs to Service Support
Service Level Agreements Operational Level Agreements Customer based priority information Change freezes and release windows Service Level Targets, Service Quality Plans and Key Performance Indicators • Service Improvement Programmes • • • • •

Inputs from Service Support
User feedback from Service Desk Incident & Problem reports Major Incident Reviews SLA (threatened) breaches Projected Service Availability Forward Schedule of Change Assessment and approval of proposed Services & Changes • Service relationship information from CMDB • • • • • • •

Benefits
• Service meets customer requirements • Service provider has agreed targets • Customer and provider responsibilities understood • Improved relationship between customer and provider • Service improvements planned • Changes meet customer requirements

Breakout
Divide into two groups: • The first group are customers – what would you like to see in a Service Level Agreement? • The second group are part of the service provider – what would you like to see in a Service Level Agreement?

Financial Management
Goal
• To provide cost effective stewardship of the service assets and the financial resources used in providing services. To be able to account fully for the spend on services and to attribute these costs to the services delivered to customers.

Processes
• Budgeting
– Prediction of service costs

• Accounting
– Details of actual service costs

• Charging (optional)
– Recovery of service costs from customers

Cost Types & Elements
Type
People Accommodation Hardware Software

Elements
Payroll costs, benefits, relocation costs, consultancy, expenses Offices, storage space, workshops, shelving, utilities Computers, networks, servers Operating systems, office packages, databases Security services, outsourced services, disaster recovery Charges from other internal areas

External
Transfer

Cost categories
Capital
–Fixed assets

Operational
–Day to day running costs

Fixed
–Do not vary with usage

Variable
–Vary with usage

Direct
–Costs assigned to single customer

Indirect
–Costs apportioned between customers

Cost Model
• A framework used to calculate the costs of service provision • Could be customer or service based • Includes both direct and indirect costs • More detailed guidance on drawing up cost models is available in the ITIL® books.

Charging & Pricing
• Decision to charge taken by business, not service provider • Charging must be simple, fair & realistic • Pricing methods:
– No charging – Cost plus/minus – Cost recovery – Going rate – Market rate – Fixed price – Differential charging

Outputs to Service Support
• Budgets • Differential charging to modify user behaviour • Costing information for change assessment • Procurement guidance for Releases

Inputs from Service Support
• • • • Accounts Equipment failure rates Service utilisation information Staff utilisation information (time reporting) • Service relationship information from CMDB

Benefits
• Changes, service improvements and extensions are cost justified • Service budgets are transparent and understood • “Value for money” easier to demonstrate • Customer and user behaviour may be influenced • Greater cost efficiency

Capacity Management
Goal
• To ensure that the capacity of the Service matches the evolving demands of the customer in the most cost effective and timely manner.

Definitions 7
•Capacity
The maximum throughput that a Configuration Item (CI) or Service can deliver whilst meeting agreed Service Level Targets. For some types of CI, Capacity may be the size or volume, for example a disk drive.

Capacity “Horizons”
• Business Capacity Management
– Future

• Service Capacity Management
– Current

• Resource Capacity Management
– Component level

Business Capacity Mgt
• Works with customers on future requirements • Ensures that services supporting future business requirements are considered, planned and implemented in timely fashion • Ensures new services are appropriately sized • Ensures minimal undesirable impacts on existing services

Service Capacity Mgt
• Manages performance of current services • Monitors and measures services based on SLAs • Analyses capacity requirements, trends and failures • Tunes service and manages demand

Resource Capacity Mgt
• • • • • • Component focus Often technical Optimises individual CI performance Monitors, analyses and tunes CIs Profiles use of CIs Maintains awareness to feed into CI procurement

Iterative Activities
Tuning Implementation Monitoring Analysis

Predictive Activities
• Demand Management
– Shape user behaviour – Must be sensitively applied!

• Modelling
– Predict results of changes based on:
• • • • Guess Trends Mathematical models Simulation

• Application Sizing
– Designed in capacity

Capacity Plan & Database
• Capacity Plan
– Produced annually – Current & Future Capacity requirements
• Business, Service and Resource

– Costed options

• Capacity Management relies on many data feeds
– Hence collate into Capacity Database

Definitions 8
•Capacity Plan
A Capacity Plan is used to manage the resources required to deliver Services. The Plan contains scenarios for different predictions of Business demand, and costed options to deliver the agreed Service Level Targets.

Outputs to Service Support
Capacity related RFCs Demand management Appropriately sized services Capacity advice to CAB Component capacity advice to Release Management • Capacity trend analysis to Problem Management • • • • •

Inputs from Service Support
• Monitoring information on service and CI capacity • Service and CI relationship information from CMDB • User experience of performance • Forward Schedule of Change • Assessment and approval of Capacity changes • Handling of capacity incidents and problems

Benefits
• Increased efficiency
– Reduced unnecessary over capacity

• Reduced capacity related incidents & problems • Better budgeting
– No panic buying

• Planned, considered service growth
– Reduced pinch-points

• No surprises!

Breakout
Information Services has agreed to extend services to students of another local University. Consider how this planned change might impact on the Library Café. • What capacity issues should be considered? • What are the likely financial implications?

Availability Management
Goal
• To optimise the capability of the service and supporting organisation to deliver a cost effective and sustained level of availability that satisfies customer requirements.

Definitions 9
• Availability
Ability of a Configuration Item or Service to perform its agreed function when required. Availability is determined by Reliability, Maintainability, Serviceability, performance, and security. It is best practice to calculate Availability using measurements of the business output of the Service.

• Reliability
A measure of how long a Configuration Item or Service can perform its agreed function without interruption.

• Maintainability
A measure of how quickly and effectively a Configuration Item or Service can be restored to normal working after a failure.

• Serviceability
The ability of a Third Party Supplier to meet the terms of their Underpinning Contract.

Security Management
• Confidentiality
– Protecting against unauthorised access and use

• Integrity
– Accuracy, completeness and timeliness

• Availability
– Accessible at any agreed time

Measuring Availability
• Can’t maintain, can’t improve, can’t manage what can’t be measured!
• Measure from customer point of view
– Reports contain Service availability
• CI availability used to target improvements

– % Downtime, lost working hours, impact

Anatomy of an Incident
Time Between System Incidents
Time To Repair (Down Time)
Detection Response Time Time Repair Time

Time Between Failures (Up Time)
Recovery Time

Restoration

Detection

Diagnosis

Recovery

Incident

Repair

Incident

Availability Techniques
• CCRAM
– CCTA Risk Analysis Management Methodology

• • • •

Fault Tree Analysis Component Failure Impact Analysis Service Outage Analysis Technical Observation Post

Definitions 10
• High Availability
An approach or design that minimises or hides the effects of Configuration Item failure on the users of a Service. High Availability solutions are designed to achieve an agreed level of Availability and make use of techniques such as fault tolerance, resilience and fast recovery to reduce the number of Incidents, and the Impact of Incidents.

• Continuous Operation
An approach or design to eliminate planned downtime of a Service. Note that individual Configuration Items may be down even though the Service is Available.

• Continuous Availability
An approach or design to achieve 100% Availability. A Continuously Available Service has no planned or unplanned downtime.

Best Method
• The cheapest and most effective method of ensuring appropriate availability is to… …Design it in

Outputs to Service Support
Availability related RFCs Incident process enhancements Services with designed in availability Availability advice to CAB Analysis for proactive problem Management • Release window breach analysis • • • • •

Inputs from Service Support
• Monitoring information on service and CI availability • Service and CI relationship information from CMDB • User experience of availability • Projected Service Availability • Assessment and approval of Availability changes • Handling of Availability incidents and problems

Benefits
• Services have appropriate availability • Availability incidents and problems are reduced • Availability “designed in” • Customer and user confidence increased • Higher availability = reduced impact & happier customers

Service Continuity Mgt Goal
• To support the overall Business Continuity Management process by ensuring that the required services can be recovered within required and agreed customer time scales, minimising any impact.

Relationship to Availability
Service Continuity

Cost of countermeasures Impact of Incidents Scale of disaster Blood on the carpet

Availability

Definitions 11
•Vital Business Function (VBF)
A function of a business process which is critical to the success of the business. Vital Business Functions are an important consideration of Business Continuity Management, Service Continuity Management and Availability Management.

Process
Initiation Requirements & Strategy Implementation Operational Management

Initiation
• Initiate Business Continuity Management
– Service Continuity Management is not a substitute for BCM, it is part of BCM – No point investing in 1 day recovery of service if users don’t return for a week!

• Specify scope • Set policy • Allocate resources
http://www.safety.ed.ac.uk/resources/General/pandemic_flu_plan.shtm

Requirements & Strategy
• Business Impact Analysis
– Analyse business processes – Identify VBF

• Risk Assessment
– Which services support VBF? – What threatens them (hazard)? – How vulnerable are they? – Tool, e.g. CRAMM

• Business Continuity Strategy

Business Continuity Strategy
• Recovery Time Objective
– How long to recover?

• Recovery Point Objective
– What will the recovered system look like?

• Recovery Options

Recovery Options
• • • • • • • Countermeasures (avoid/mitigate) Do nothing (!) Manual working Reciprocal agreement Gradual recovery (>72 hours) Intermediate recovery (24 hours) Immediate recovery (<24 hours)

Implementation
• • • • • • Implementation planning Implement stand-by arrangements Develop recovery plans Implement counter measures Develop procedures Initial testing

Operational Management
• • • • • • Education & Awareness Training Change Management Reviews & Audits Testing Assurance

Outputs to Service Support
• • • • • • • Continuity Plans Roles & responsibilities Testing Highlighting of continuity problems Continuity RFCs Continuity advice to CAB Recovery instructions to Release

Inputs from Service Support
• Assessment and approval of Continuity changes • CAB considers Continuity implications of all changes • Release informs continuity of CI changes • Service and CI relationship information from CMDB • Testing results from Service Desk • Handling of Continuity problems

Benefits
• Business continues after disaster! • Recovery is in business priority order • Customer and user confidence improved • Plans in place – reduced panic & ill-considered action • Reduced impact of continuity incidents

Breakout
Consider a service operating from the Main Library Building. • What would you like to see covered in the Service Continuity Plan? • How might continuity improvements be used to improve service availability?

Where Now?
• “Foundations of IT Service Management based on ITIL”
– Van Haren Publishing, £23.80 via itSMF – Exam preparation chapters

• “Introduction to ITIL”
– TSO, £25.29 via itSMF – Covers more of ITIL

• E-learning Foundation Course – now v3
– http://www.ucs.ed.ac.uk/usd/cts/courses/elearning.html

• Exam
– Onsite, £117.50

• Full Foundation Course?

Questions?

Thought
Can I use the ITIL processes of Service Level Management, Financial Management, Capacity Management, Availability Management and Service Continuity Management to improve the services I offer to my users?

Acknowledgements
ITIL ® is a Registered Trade Mark of the Office of Government Commerce © Crown copyright material is reproduced with the permission of the Controller of HMSO and Queen's Printer for Scotland. itSMF copyright material is reproduced with the permission of the itSMF


				
DOCUMENT INFO
Shared By:
Tags:
Stats:
views:384
posted:8/10/2009
language:English
pages:79