Service Design Package (ITIL)

Last updated

The Service Design Package (SDP) contains the core documentation of a service and is attached to its entry in the ITIL Service Portfolio.

Contents

The SDP is described in the book Service Design, one of the five books that comprises the core of ITIL.

The SDP follows the lifecycle of a service from when it is first suggested as a possibility to when it is finally retired. It is the central reference point for all documentation of a service, so it contains many links to other documents.

A description of the sort of information that should be kept in an SDP is found in Appendix A of the Service Design book. [1]

The main categories described are:

At major stages through the life of a service, the "Service Design Package (SDP)"' will contain project plans, project progress and project outcomes, as well as the business case that justified the service or the transition of the service from one status to another.

Definition of a 'Service'

In the ITIL model, a 'Service' is defined as, "A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks." [2] The meaning is thus highly business-focused and assumes some degree of outsourcing, although this may just be outsourcing from within the functional business unit to some IT services group within the same overall business. [3]

'Service' in this context should not be confused with the IT meanings of 'service', such as a web service. This is somewhat confused by ITIL also recommending the adoption of service-oriented architecture, as expounded by OASIS. [4] In most technical contexts, SOA is widely assumed to imply the provision and interconnection of technical services. Although a fashionable buzzword for ITIL to have incorporated, they do not use the term according to its general meaning.

See also

Related Research Articles

Configuration management process for maintaining consistency of a product attributes with its design

Configuration management (CM) is a systems engineering process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. The CM process is widely used by military engineering organizations to manage changes throughout the system lifecycle of complex systems, such as weapon systems, military vehicles, and information systems. Outside the military, the CM process is also used with IT service management as defined by ITIL, and with other domain models in the civil engineering and other industrial engineering segments such as roads, bridges, canals, dams, and buildings.

A software company is a company whose primary products are various forms of software, software technology, distribution, and software product development. They make up the software industry.

Systems development life cycle Systems engineering term

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life-cycle, is a process for planning, creating, testing, and deploying an information system. The systems development life cycle concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.

Product lifecycle a period of time of a product being from inception, through engineering design and manufacture, to service and disposal

In industry, product lifecycle management (PLM) is the process of managing the entire lifecycle of a product from inception, through engineering design and manufacture, to service and disposal of manufactured products. PLM integrates people, data, processes and business systems and provides a product information backbone for companies and their extended enterprise.

IT service management (ITSM) is the activities that are performed by an organization to design, plan, deliver, operate and control information technology (IT) services offered to customers.

Change management is an IT service management discipline. The objective of change management in this context is to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to control IT infrastructure, in order to minimize the number and impact of any related incidents upon service. Changes in the IT infrastructure may arise reactively in response to problems or externally imposed requirements, e.g. legislative changes, or proactively from seeking improved efficiency and effectiveness or to enable or reflect business initiatives, or from programs, projects or service improvement initiatives. Change management can ensure standardized methods, processes and procedures which are used for all changes, facilitate efficient and prompt handling of all changes, and maintain the proper balance between the need for change and the potential detrimental impact of changes.

The Information Services Procurement Library (ISPL) is a best practice library for the management of Information Technology related acquisition processes. It helps both the customer and supplier organization to achieve the desired quality using the corresponded amount of time and money by providing methods and best practices for risk management, contract management, and planning. ISPL focuses on the relationship between the customer and supplier organization: It helps constructing the request for proposal, it helps constructing the contract and delivery plan according to the project situation and risks, and it helps monitoring the delivery phase. ISPL is a unique Information Technology method because where most other Information Technology methods and frameworks focus on development, ISPL focuses purely on the procurement of information services. The target audience for ISPL consists of procurement managers, acquisition managers, programme managers, contract managers, facilities managers, service level managers, and project managers in the IT area. Because of ISPL's focus on procurement it is very suitable to be used with ITIL and PRINCE2.

The Application Services Library (ASL) is a public domain framework of best practices used to standardize processes within Application Management, the discipline of producing and maintaining information systems and applications. The term "library" is used because ASL is presented as a set of books describing best practices from the IT industry.

Oracle Applications comprise the applications software or business software of the Oracle Corporation. The term refers to the non-database and non-middleware parts.

Microsoft Operations Framework (MOF) 4.0 is a series of guides aimed at helping information technology (IT) professionals establish and implement reliable, cost-effective services.

A product manager is a professional role that is responsible for the development of products for an organization, known as the practice of product management. Product managers own the business strategy behind a product, specify its functional requirements, and generally manage the launch of features. They coordinate work done by many other functions and are ultimately responsible for the business success of the product.

A service delivery platform (SDP) is a set of components that provides a service(s) delivery architecture for a type of service delivered to consumer, whether it be a customer or other system. Although it is commonly used in the context of telecommunications, it can apply to any system that provides a service. Although the TM Forum (TMF) is working on defining specifications in this area, there is no standard definition of SDP in industry and different players define its components, breadth, and depth in slightly different ways.

ITIL security management describes the structured fitting of security into an organization. ITIL security management is based on the ISO 27001 standard. "ISO/IEC 27001:2005 covers all types of organizations. ISO/IEC 27001:2005 specifies the requirements for establishing, implementing, operating, monitoring, reviewing, maintaining and improving a documented Information Security Management System within the context of the organization's overall business risks. It specifies requirements for the implementation of security controls customized to the needs of individual organizations or parts thereof. ISO/IEC 27001:2005 is designed to ensure the selection of adequate and proportionate security controls that protect information assets and give confidence to interested parties."

IT portfolio management is the application of systematic management to the investments, projects and activities of enterprise Information Technology (IT) departments. Examples of IT portfolios would be planned initiatives, projects, and ongoing IT services. The promise of IT portfolio management is the quantification of previously informal IT efforts, enabling measurement and objective evaluation of investment scenarios.

SAP Solution Manager is a product developed by the software company SAP SE. It offers end-to-end application lifecycle management to streamline business processes and proactively address improvement options, increasing efficiency and decreasing risk within SAP customers' existing maintenance agreements and managing the application lifecycle.

Software quality management (SQM) is a management process that aims to develop and manage the quality of software in such a way so as to best ensure that the product meets the quality standards expected by the customer while also meeting any necessary regulatory and developer requirements, if any. Software quality managers require software to be tested before it is released to the market, and they do this using a cyclical process-based quality assessment in order to reveal and fix bugs before release. Their job is not only to ensure their software is in good shape for the consumer but also to encourage a culture of quality throughout the enterprise.

Definitive Media Library

A Definitive Media Library is a secure Information Technology repository in which an organisation's definitive, authorised versions of software media are stored and protected. Before an organisation releases any new or changed application software into its operational environment, any such software should be fully tested and quality assured. The Definitive Media Library provides the storage area for software objects ready for deployment and should only contain master copies of controlled software media configuration items (CIs) that have passed appropriate quality assurance checks, typically including both procured and bespoke application and gold build source code and executables. In the context of the ITIL best practice framework, the term Definitive Media Library supersedes the term definitive software library referred to prior to version ITIL v3.

Tudor IT Process Assessment term

Tudor IT Process Assessment (TIPA®) is a methodological framework for process assessment. Its first version was published in 2003 by the Public Research Centre Henri Tudor based in Luxembourg. TIPA is now a registered trademark of the Luxembourg Institute of Science and Technology (LIST). TIPA offers a structured approach to determine process capability compared to recognized best practices. TIPA also supports process improvement by providing a gap analysis and proposing improvement recommendations.

The Service Portfolio is described in the ITIL books Service Strategy and Service Design. The Service Portfolio is the core repository for all information for all services in an organization. Each service is listed along with its current status and history. The main descriptor in the Service Portfolio is the Service Design Package (SDP).

ITIL, formerly an acronym for Information Technology Infrastructure Library, is a set of detailed practices for IT service management (ITSM) that focuses on aligning IT services with the needs of business.

References

  1. Service Design. Archived from the original on 2015-12-27. Retrieved 2015-12-27.
  2. ITIL Service Design (2011), p. 13.
  3. ITIL Service Design (2011), p. 75.
  4. ITIL Service Design (2011), pp. 73-74.

Bibliography