eTOM Process ITIL Release and Deployment Management

Category: (2) eTOM Process Type

Extended Description

Release & Deployment Management is defined within ITIL, and further information is available at:

http://www.itsmf.co.uk/Shop/Products/9780113310616TheOfficialIntroductiontotheITILServiceLifecycle.aspx

Its role here is as a model or template for how other process areas should operate to align with the ITIL approach, where this is relevant for the enterprise concerned. Note that not all organizations will choose to follow the ITIL approach, and thus other models for Release & Deployment Management (or equivalent) may apply in such cases.

Release and Deployment Management includes all of the processes required to package, build, test and deploy a new or changed service into the live environment.  This means that service delivery is managed across any service provider interfaces.

Terminology

Before considering the terminology of the eTOM and ITIL approaches it is first necessary to contrast the perspectives which each take of the enterprise. These perspectives affect the concepts and terms used.

Due to the nature of the Service Provider enterprise - where SPs typically manage their products, services and resources distinctly - the eTOM is structured into layers (effectively high-level process groupings) which relate to these concerns. These layers are Customer Relationship Management, Service Management and Resource Management. In contrast, ITIL does not have a layered view of this kind. Its perspective is to represent the IT Services and their support, through a lifecycle view built around a set of ITIL processes that address particular, significant, areas of IT capability. It is then a matter for individual users / enterprises to relate these to their businesses.

From the eTOM perspective, ITIL Release  eTOM Product Release, Service Release, Resource Release

ITIL Service eTOM CFS and RFS distinction

Linkage with eTOM process areas

ITIL Release & Deployment Management relates to several eTOM process areas.  The eTOM processes affected include: Within Operations: Process Identifier: 1.1.1.1

Process Element: CRM Support & Readiness

Process Impact:

Where ITIL Release and Deployment Management is employed as a guiding mechanism, then the CRM Support & Readiness processes operate in line with this. Affected processes are:

Support Order handling: Test order handling

Process Identifier: 1.1.2.1

Process Element: SM&O Support & Readiness

Process Impact:

Where ITIL Release and Deployment Management is employed as a guiding mechanism, then the SM&O Support & Readiness processes operate in line with this. Affected processes are:

Enable Service Configuration & Activation: Test Service Configuration

Process Identifier: 1.1.3.1

Process Element: RM&O Support & Readiness

Process Impact:

Where ITIL Release and Deployment Management is employed as a guiding mechanism, then the RM&O Support & Readiness processes operate in line with this. Affected processes are:

Enable Resource Provisioning: Test Resource Provisioning

Within Strategy, Infrastructure & Product

Process Identifier: 1.2.1.3

Process Element: Product & Offer Capability Delivery

Process Impact:

Where ITIL Release and Deployment Management as a guiding mechanism, then the Product & Offer Capability Delivery processes operate in line with this. Affected processes are:

Manage handover to Product Operations: manage product transition into operations

Process Identifier: 1.2.2.2 Process Element: Service Capability Delivery

Process Impact:

Where ITIL Release and Deployment Management is employed as a guiding mechanism, then the Service Capability Delivery processes operate in line with this. Affected processes are:

Manage Service Capability Delivery: ensure service capability are in place

Manage handover to Service Operations: manage service transition into operations

Process Identifier: 1.2.2.3

Process Element: Service Development & Retirement

Process Impact:

Where ITIL Release and Deployment Management is employed as a guiding mechanism, then the Service Development & Retirement processes operate in line with this. Affected processes are:

Manage Service Deployment: manage service transition into operations

Process Identifier: 1.2.3.2

Process Element: Resource Capability Delivery

Process Impact:

Where ITIL Release and Deployment Management is employed as a guiding mechanism, then the Resource Capability Delivery processes operate in line with this. Affected processes are:

Manage Handover to Resource Operations: manage resource transition to operations

Process Identifier: 1.2.3.3

Process Element: Resource Development & Retirement

Process Impact:

Where ITIL Release and Deployment Management is employed as a guiding mechanism, then the Resource Development & Retirement processes operate in line with this. Affected processes are:

Manage Resources Development: manage resource transition to operations

 

Process Identifier: 1.3.1.5

Brief Description

Release & Deployment Management is defined within ITIL. Its role here is as a model or template for how other process areas should operate to align with the ITIL approach, where this is relevant for the enterprise concerned. Note that not all organizations will choose to follow the ITIL approach, and thus other models for Release & Deployment Management (or equivalent) may apply in such cases.

Process Context

This process element has a different status from many elsewhere in the overall Business Process Framework. This process is not directly instantiated within the enterprise but represents a corporate policy that, where applied, guides the operation and behavior of other process areas. Note also that some enterprises may choose not to use this process for guidance, which does not invalidate general alignment with the Business Process Framework (although clearly, in such cases, alignment with this specific process would not apply.)

Maturity Level: 4

Appears on

eTOM Processes (belongs to horizontal grouping of)

eTOM Processes (belongs to vertical grouping)


Go to Top of This Page| Return to the Contents Page
Created from the Casewise Model eTOMv9 and TAM4 on 1/15/2011 at 15:31