Request Fulfilment: Process Introduction by IT Training Zone

video locked

About the Lecture

The lecture Request Fulfilment: Process Introduction by IT Training Zone is from the course ITIL® OSA - Operational Support and Analysis . It contains the following chapters:

  • Lesson Contents
  • Introduction
  • Purpose, Objectives
  • Value
  • Concepts
  • Exercise – Incidents and Requests

Included Quiz Questions

  1. Adding a new field to a database
  2. Re-setting a password
  3. Moving equipment
  4. Setting up a new user
  1. No delays waiting for authorizations
  2. Efficiency
  3. Cost savings
  4. Request can often be fulfilled by Service Desk staff
  1. This may be a bad idea, as it confuses reporting and therefore makes Problem Management more difficult
  2. This is a bad idea, as it would be better to log them as changes
  3. This is a good idea as the Service Desk analyst does not need to consider what sort of record to log
  4. This is a good idea because it ensures that the Service Desk passes the request to the correct team
  1. Requests which affect a CI should be logged as standard changes
  2. Requests which affect a CI should be logged as normal changes
  3. All requests should be standard changes
  4. Requests which affect a CI do not need to be logged as changes, the request record is enough
  1. Self-service is not as good as logging requests through the Service Desk
  2. Self-service can be extended to deal with other non-IT requests
  3. Some self-service requests may be fulfilled without ever coming to the Service Desk
  4. Self-service provides an improved service as it means that users can log requests 24 hours a day, 7 days a week
  1. The service desk owns all requests
  2. The service desk owns all requests EXCEPT those logged through self-service
  3. The support person assigned to fulfill a request owns that request until fulfillment is complete
  4. Self-service requests are owned by the requester
  1. Request models should only be used for requests which affect a CI
  2. Request models should be used for high volume, low risk requests
  3. Request models ensure consistency
  4. Request models include timescales
  1. Requests should be prioritized using impact and urgency assessments
  2. Request targets should be defined in SLAs
  3. Requests should be handled in the order in which they are logged
  4. Requests should be prioritized using impact and cost assessments
  1. Organizations may choose whether or not to charge for requests
  2. Normal rules regarding authorization of expenditure applies to requests
  3. Costs for different request types should be included in the service catalogue
  4. Requests should not be chargeable

Author of lecture Request Fulfilment: Process Introduction

 IT Training Zone

IT Training Zone


Customer reviews

(1)
5,0 of 5 stars
5 Stars
5
4 Stars
0
3 Stars
0
2 Stars
0
1  Star
0