Service Design Package (SDP) and the Service Catalog

Both the Service Design Package (SDP) and the Service Catalog are produced in the service design stage of the service lifecycle and to some extent both drive the activities that happen in all subsequent stages of the service lifecycle. The SDP will detail all aspects of a service and its requirements throughout the entire lifecycle. A service design package is produced for all new services, major changes to an existing service or the removal of a retired service.

From a high level the service design package will contain the following:

· Business requirements

· Service applicability requirements (how/where used)

· Service contracts

· Service functional requirements

· Service and operational management requirements

· Service design and topology (including service definition and model

· Organizational readiness assessment

· Service Program (timescales and phasing of transition, operation and improvement of the new service)

· Service transition plan (overall transition strategy, objectives, policy and risk assessment).

· Service operational acceptance plan (overall operational strategy, objectives, policy and risk assessment).

· Service acceptance criteria (acceptance criteria for the progression through each stage of the lifecycle)

The service catalog provides a single source of information for all operational (live) services, services that are about to go live and are currently being prepared for deployment to the live environment. Your service catalog can initially start as a simple matrix, table or spreadsheet. As you grow your ITSM processes in maturity, your catalogs sophistication can grow along with them. Many organizations will integrate their service portfolio and their service catalog and maintain them as part of the Configuration Management System (CMS).

The service catalog can be produced with two distinct views available. You can have the business/customer view which relates IT services to business units and processes. This view represents what your customers will see. The second view is the technical/supporting service view. This relates IT services to supporting services and to the underlying components that underpin the delivery of the IT services and business functions. This includes items that will not be viewed by the customer. Both will enable proactive service level management and quicker more effective incident and change impact analysis.

Some critical success factors (CSF) that should be accomplished by the service catalog and service catalog management could be to produce an accurate and up to date catalog. This should lead to a greater awareness of the services being provided to the business and should also enhance the IT staffs ability to support these services and their related underlying technology more efficiently and effectively.

Comments

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Search