module cc3002 post implementation issues lecture for week 5 ay 2013 spring

35
Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Upload: emily-lawson

Post on 01-Jan-2016

219 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Module CC3002

Post Implementation IssuesLecture for Week 5

AY 2013 Spring

Page 2: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Support Issues

•What do we need from System Support?• IS Support Service: The Help

Desk• Service Level Agreements• Enhancement Request

Page 3: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Service Level Agreements

Two Way AgreementsBetween

Service ProviderAnd

Service Receiver-Czegel, 1999

Page 4: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Service Level Agreements

Help Desk might have SLA betweenBetween

Help Desk (Service Provider)And

Group of Customers (Service Receiver)

-Czegel, 1999

Page 5: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SLA

• Agreements typically specify–What services the provider provides–What targets it must meet

• SLA also specifies–Responsibilities of ‘receivers’ using

the services

Page 6: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SLA

• What is SLA ?• Why do we need to define Service

Levels ?• What SLA can we make about

Support Service?

Page 7: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SLA

• How should we define these Service Levels?• How do we use these defined

Service Levels ?• Should we exclude certain events

from our service level monitoring?

Page 8: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Why define Service Level?

• A Written Commitment or Agreement between two parties–The provider–The receiver (recipient)

Page 9: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Why define Service Level?

• Is SLA Legally Binding ?• Possibly, between two legal

entities (two separate companies)• Between departments of same

organization (IT and Service)

Page 10: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Why define Service Level?

• SLA is used to:Measure performance

Of Service Provider

In the Delivery of That Service

Page 11: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SLA and Support Plan

• Assignment asks for Support Plan• Broadly similar to idea of SLA

Page 12: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SLA and Support Plan

• Support Plan should define–What the service provider will

provide–The targets you plan to meet–Customer responsibilities

Targets are defined in Service Levels

Page 13: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SL Targets/Measures

• Targets to measure Help Desk Performance–How well the intended service is

being delivered–Success of Support Plan

Page 14: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SL for Support Service

Support Service Levels may relate to

Different Category of

Support Issue

Page 15: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SL for Support Service

• Specify how quickly certain things should be done• Define how often (as %) done

within the specified time

Page 16: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

SL for Support Service

Example target: New User Account• Target–New accounts should be set up within 1

working day• Service Level Statement–Aim for 90% of Accounts set up within 1

working day

Page 17: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Example Targets

Priority

Impact Target Response

Target Resolution

1 Critical Component Down 15 Mins 1 Hr

2 Critical Components Degraded 45 Mins 4 Hrs

3 Non Critical Component Failed 4 Hrs 8 Hrs

4 Other Requests/Questions 8 Hrs 12 Hrs

Page 18: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Example

Service Measures to be met by Help Desk

• 95% of Priority 1 calls responded to within target

• 90% of Priority 1 calls resolved within target• 90% of Priority 2,3,4 calls responded within

target• 85% of Priority 2,3,4 calls resolved within target

Page 19: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Example

Service Measures to be met by Help Desk

• 90% of telephone calls answered within 1 minute

• 2% or fewer calls re-opened within 2 weeks

Page 20: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Example

Service Measures to be met by Customer

• 10% or fewer calls of training type category

Calls as a result of lack of knowledge/training, not a problem with

system itself

Page 21: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Service Level Target/LondonMet

Page 22: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Service Desk – Opening Hours

• Specified within Knowledge Base– Gives days and time of availability– Gives method of contact– Gives detail of document (date, author)

• Allows document to be evaluated

Page 23: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Opening Hours

Page 24: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

User Defined Service Levels

•Weekly•Monthly• Quarterly• Annual

Page 25: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

User Defined Service Levels

• Performance Report might include–Total number of calls–Number of calls by category–Response rate within specified

target–Resolution rate within specified

target

Page 26: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

User Defined Service Levels

• Reports delivered to –Management representative of

Service Provider organization–Specified representative in Support

Recipient organization

Page 27: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

User Defined Service Levels

• Allows both parties to measure the performance of the support service• Helps in adjustments to improve

service quality(Frequent calls might indicate bugs

or training needs)

Page 28: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

EVERYTHINGCOVERED ?

Page 29: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Coverage

• In reality, things are more complicated• May need to define special

exception–Cope with issues outside our immediate

control

Page 30: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Possible Problems

• A call has been logged• Unable to contact user for further

information• Meanwhile target resolution time

passes• Who is responsible?

Page 31: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Possible Problems

• Perhaps put the call ‘on hold’–Unable to act without further

information

Page 32: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Possible Problems

• A call has been logged• A bug in third party software

is responsible for cause• Third party company is taking

time to supply the fix• Meanwhile target resolution time

passed

Page 33: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Possible Problems

• Put call ‘on hold’ while waiting for response• Keep users informed of progress

Page 34: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Summary – SLA

• Priority (identify category)

• Setting targets (response/resolution)

• Customer responsibilities• Exclusions• Monitor performance

Page 35: Module CC3002 Post Implementation Issues Lecture for Week 5 AY 2013 Spring

Thanks Y

Thank You.