Skip to main content

The Service Design Package (SDP)

I was recently asked by one of my followers if I might have an example of a Service Design Package (SDP). 

When seeking to implement ITSM and ITIL, we often seek to find examples and models we can use to give us more guidance. This is no less true of the SDP.  Unfortunately when we try to seek out specific examples of a SDP it can often be difficult, if not near impossible. So why is it hard to find actual examples of a SDP? It goes to the very nature of the guidance of what we call best practices. ITIL is not prescriptive as to what should go into a SDP or what one might look like. It provides best practice guidance on the types of items contained, but not the exact look and feel of the content. Therefore each SDP will be unique to the organization that creates it. The organization, type of content, what the content says, and how it is managed are all decisions made by each organization to meet the needs of their customers and users. Just like a Service Catalog or a set of Service Level Agreements are unique, the SDP may not mean anything to someone outside the organization that is providing that service and has that particular group of customers or users.  It may also contain proprietary or confidential information. 

At a minimum the SDP should address the Five Aspects of Design: the services, tool, architecture, metrics and processes needed to deliver value to the business or end users. For some organizations this might be a long list of items, for others a few diagrams, lists, or tables of data and information. The SDP is a formal collection of information that moves with the service as it proceeds through its lifecycle, rather than being an odd collection of randomly associated documents. The key to a successful SDP is that it contains all the information needed by the Service Transition processes to build, test, configure, release and deploy the services and their underpinning components.



Comments

Hi 'Professor'

Spot on message. Funny how folk expect ITIL to be simply rolled out to the 'edges' of an organization just by opening the Core Publications. We have put together a series of articles entitled ' Itil in Practice' which maybe of interest to you, take a look at www.itilnews.com . If you consider it we would like to publish your SDP article.
Anyway, great article and of great value and benefit to those thinking of or are adopting ITIL best management practices.
Kind regards
Steve
Brady said…
One of the big improvements with the recent publication of ITIL 2011 is that the guidance includes a lot of templates in the appendices. At the end of Service Design are appendices that list the typical contents of an SDP, the Capacity Plan, SLAs and OLAs, Service Acceptance Criteria, etc.
Brady said…
One of the big improvements with the recent publication of ITIL 2011 is that the guidance includes a lot of templates in the appendices. At the end of Service Design are appendices that list the typical contents of an SDP, the Capacity Plan, SLAs and OLAs, Service Acceptance Criteria, etc.
Unknown said…
I'm sure many companies have examples of how they follow the "guidelines", it is neither inappropriate or impossible. The whole point is not to reinvent wheels. Surely examples do not need to be prescriptive
Unknown said…
hi,

if i am designing an app for my university in order to pay the fees and all,what would be the compliance requirements ,Architectural constraints and interface requirements in designing the service design package?

Thanks
Poly
Hi Paul,

The short answer is that the SDP would have ALL of the documents and information related to how the app was designed and developed including any policies or known compliance or other constraints. The purpose of the SDP is to provide a living set of knowledge assets that can be passed around the lifecycle for use in each stage (e.g., deployment, operations, support, updating, etc.)

The Professor

Popular posts from this blog

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 th

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

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