Checklist Service Design Package SDP

From IT Process Wiki

diese Seite auf Deutsch esta página en español

DE - ES - Checklist Service Design Package SDP - Template Service Design Package SDP

Definition: The Service Design Packet (SDP) builds upon the Service Level Requirements. Information technology further specifies the requirements from the viewpoint of the client and defines how these are actually fulfilled from a technical and organizational point of view. It is assumed that a bundle of supporting services is combined in order to deliver a business service for the customer. In this context, the It organization may opt to supply the supporting service with its ain resources, or to employ an external service supplier.

The Service Blueprint Package is passed from Service Design to the Service Transition process and details all information required in order to develop the service solution, including a preliminary (intended) fourth dimension-schedule for the Service Transition phase.

ITIL Process: ITIL Service Pattern - Design Coordination

ITIL 4 Practice: Service blueprint

Checklist Category: ITIL Templates

Service Pattern Package - Contents

Service Design Package SDP

The Service Design Package contains the post-obit information (the actual level of detail volition vary, depending on the blazon of service):

This part describes the header data contained in a Service Design Package.

Proper name of the service

Service Owner responsible for delivering the service

Clearance data

(with location and appointment)

  1. Clearance of the Service Design Director
  2. Clearance of the Service Design Package by Service Management (confirmation that the requirements every bit laid out in this document are able to be fulfilled and where necessary, specification of whatever preconditions which must exist fulfilled before the service tin can go operational)
    1. Capacity Director
    2. Availability Managing director
    3. IT Service Continuity Managing director
    4. Information Security Director
    5. Compliance Director
    6. Financial Managing director

Part II: Detailed Requirements Specification every bit a Basis for Service Transition

This part builds upon the Service Level Requirements and specifies in more item what conditions the new service and its underlying applications and infrastructure must fulfill, providing all information which is needed for building the new service.

Service level requirements

(reference to the SLR document, where service level requirements are defined)

Functional requirements

(the SLR document contains a summary description of the desired customer outcome; however, functional requirements may need to be specified in greater detail, specially if new applications/ systems are to exist adult)

Information security requirements

(Information security requirements which are relevant for the service)

Compliance requirements

(Compliance requirements which are relevant for the service)

Architectural constraints

(e.g. specific technology or vendors)

Interface requirements

(e.m. if a new system needs to communicate with other systems)

Migration requirements

(e.1000. if information are to be migrated from an existing to a new application)

Operational requirements

(e.g. requirements for fill-in and restore mechanisms, compatibility with existing system monitoring tools)

Required admission rights

(which users or user groups volition require access to the service, and what levels of access must be provided)

Part III: Service Operation and Comeback Concepts

This function details how the service will be operated and continually improved, including the associated responsibilities, and what is required to do so.

Service Operation

  1. Approach to managing risks and problems
  2. Required monitoring, measuring and reporting
  3. Requirements with regards to operational functions, due east.chiliad. procedures and activities required on operational level to operate the service
  4. Required operational and stop-user documentation
  5. Human resources also every bit skills required to operate the service

Continual Service Improvement

  1. Approach and mechanisms to continually improve the service
  2. Human resources also every bit skills required to improve the service

Function Iv: Technical and Organizational Implementation Blueprint

This part details what must be washed during Service Transition to come across the specified requirements.

Decomposition of the Business Service into Infrastructure Services

  1. Internal Infrastructure Services on which this service is based
    1. Names of the infrastructure services
    2. Service providers (responsible Service Owners)
    3. References to Operational Level Agreements (OLAs)
    4. Required changes to OLAs, if existing OLAs are non sufficient for the service to exist established
  2. Externally supplied Supporting Services on which this service is based
    1. Names of the external services
    2. Name of the supplier
    3. Responsible Supplier Manager
    4. References to Underpinning Contracts (UCs)
    5. Required changes to UCs, if existing UCs practise not support the introduction of the new service

Transition strategy

(a brief outline of the selected approach to implementing the new service)

  1. Testing strategy
  2. Deployment strategy
  3. Migration concept
  4. Dorsum-out strategy in the example of a failed deployment
  5. Integration with other service transition projects

Details on technical changes

Details on technical changes required to build, test, deploy and operate the service.

  1. Development/ customization of base applications for the service (e.g. if the service to be introduced is based on the SAP organization or a custom application)
  2. Supporting tools
    1. Development/ customization of migration tools
    2. Evolution/ customization of testing tools
    3. Development/ customization of deployment tools
    4. Development/ customization of dorsum-out tools in the case of a failed release deployment
  3. Infrastructure modifications required to build, examination, deploy and operate the service
    1. Infrastructure components to be purchased and installed
    2. Infrastructure components to be (re-)configured
  4. Required changes to facilities

Organizational changes

Organizational changes required to implement and operate the service.

  1. Personnel resources to exist added
    1. Specification of required resources
    2. Strategy for acquiring the resources
  2. Skills to exist adult
    1. Specification of the required skills
    2. Strategy for acquiring the skills
  3. Changes to processes
    1. List of It processes which must be inverse or created, including process owners
    2. Detailed specification of required changes to Information technology processes, e.g. in the grade of procedure designs

Required fiscal resources

  1. Fiscal resource required to build the service (itemized)
  2. Financial resources required to operate the service (itemized)

Part Five: Transition Planning Data

This part sets an intended time frame for the service implementation and estimates the required resources; this information may be updated later past Alter Management, Release Direction or Project Management.

Preliminary Service Transition Plan

  1. Major projection phases and milestones
  2. Intended time schedule
  3. Required staff resources

Notes

Is based on: Checklist 'Service Blueprint Package (SDP)' from the ITIL Process Map

Past:  Stefan KempterAuthor: Stefan Kempter, IT Process Maps GbR, Information technology Process Maps.

Definition  › SDP: Contents  › Part 1  › Part 2  › Part 3