YaSM and USMBOK: Difference between revisions
No edit summary |
No edit summary |
||
Line 23: | Line 23: | ||
[http://usmbok.com/ USMBOK™] (Universal Service Management Body of Knowledge) [[#USMBOK|[1]]] is a service management framework that continues to gain in popularity. | [http://usmbok.com/ USMBOK™] (Universal Service Management Body of Knowledge) [[#USMBOK|[1]]] is a service management framework that continues to gain in popularity. | ||
As the authors of USMBOK state, "USMBOK includes a set of generally accepted terms, methods, concepts and best practices". The framework "introduces outside-in or customer centric thinking to the traditional ITSM thinking", while sharing many of its underlying principles with other service management frameworks and standards such as ITIL® [[#ITIL|[2]]] and ISO/IEC 20000 (USMBOK specifically refers to a "service management system", a term which figures prominently in ISO 20000). [[#ref-clayton-2012|[Clayton, 2012]]] | As the authors of USMBOK state, "USMBOK includes a set of generally accepted terms, methods, concepts and best practices". The framework "introduces outside-in or customer centric thinking to the traditional ITSM thinking", while sharing many of its underlying principles with other service management frameworks and standards such as [[YaSM and ITIL|ITIL]]® [[#ITIL|[2]]] and [[ISO 20000|ISO/IEC 20000]] (USMBOK specifically refers to a "[[SP1: Set up and maintain the service management system|service management system]]", a term which figures prominently in ISO 20000). [[#ref-clayton-2012|[Clayton, 2012]]] | ||
For those reasons, it was both desirable and feasible to take the guidance in USMBOK into account when developing YaSM. YaSM, however, cannot claim to be a "USMBOK process model". Organizations that want to achieve close alignment of their processes with the USMBOK recommendations are advised to obtain additional guidance from the USMBOK publications. | For those reasons, it was both desirable and feasible to take the guidance in USMBOK into account when developing YaSM. YaSM, however, cannot claim to be a "USMBOK process model". Organizations that want to achieve close alignment of their processes with the USMBOK recommendations are advised to obtain additional guidance from the USMBOK publications. | ||
Line 41: | Line 41: | ||
*Major activities performed during the stage. | *Major activities performed during the stage. | ||
<html><p><span id="md-webpage-description" itemprop="description">The following table provides an overview of how each stage in the USMBOK service lifecycle relates to one or several YaSM processes, to illustrate that YaSM and USMBOK share many basic principles.</span> Its aim is not to provide a detailed and scientifically correct cross-reference between the two frameworks.</html> | <html><p><span id="md-webpage-description" itemprop="description">The following table provides an overview of how each stage in the USMBOK™ service lifecycle relates to one or several <a href="https://yasm.com/wiki/en/index.php/Service_Management_Processes" title="YaSM processes">YaSM service management processes</a>, to illustrate that YaSM and USMBOK share many basic principles.</span> Its aim is not to provide a detailed and scientifically correct cross-reference between the two frameworks.</html> | ||
'''''Note:''''' ''This table is based on the 2012 edition of the USMBOK Guide.'' | '''''Note:''''' ''This table is based on the 2012 edition of the USMBOK Guide.'' | ||
Line 58: | Line 58: | ||
*[[SP3: Manage customer relationships]] | *[[SP3: Manage customer relationships]] | ||
| | | | ||
*YaSM's customer relationship management process is in charge of communicating with existing and potential new customers in order to identify the customers' needs and opportunities for providing services. | *YaSM's [[SP3: Manage customer relationships|customer relationship management process]] is in charge of communicating with existing and potential new customers in order to identify the customers' needs and opportunities for providing services. | ||
*Once the customers' needs and opportunities are identified, the strategic process is in a position to decide upon the range of services to be offered to customers. This includes initiating the introduction of new or significantly changed services. | *Once the customers' needs and opportunities are identified, the [[LP1: Set the strategic direction|strategic process]] is in a position to decide upon the range of services to be offered to customers. This includes initiating the introduction of new or significantly changed services. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|2 Require | |2 Require | ||
Line 65: | Line 65: | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
| | | | ||
*Requirements from the customer viewpoint for new or significantly changed services are defined as part of YaSM's service design process. | *Requirements from the customer viewpoint for new or significantly changed services are defined as part of YaSM's [[LP2: Design new or changed services|service design process]]. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|3 Define | |3 Define | ||
Line 71: | Line 71: | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
| | | | ||
*YaSM stipulates that services be defined in service definitions, which specify, for example, how service quality is managed and how support will be provided. | *YaSM stipulates that [[Customer vs. Operational Service Definitions and Agreements|services be defined in service definitions]], which specify, for example, how service quality is managed and how support will be provided. | ||
*The service design process will typically also create a service operation manual to describe in detail how the service will be operated. | *The [[LP2: Design new or changed services|service design process]] will typically also create a service operation manual to describe in detail how the service will be operated. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|4 Plan | |4 Plan | ||
Line 84: | Line 84: | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
| | | | ||
*Once the service properties are specified in a (draft) service definition, the service design process draws up a service implementation blueprint, which describes the components required for providing the service and how those components will be set up. | *Once the service properties are specified in a (draft) service definition, the service design process draws up a [[YaSM_Glossary#Service-implementation-blueprint|service implementation blueprint]], which describes the components required for providing the service and how those components will be set up. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|6 Approve | |6 Approve | ||
Line 90: | Line 90: | ||
*[[LP1: Set the strategic direction]] | *[[LP1: Set the strategic direction]] | ||
| | | | ||
*Approval for the design stage of a new or significantly changed service is given by the strategic process, as part of its decision to start a service development project. | *Approval for the design stage of a new or significantly changed service is given by the [[LP1: Set the strategic direction|strategic process]], as part of its decision to start a service development project. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|7 Design | |7 Design | ||
Line 108: | Line 108: | ||
*[[LP3: Build new or changed services]] | *[[LP3: Build new or changed services]] | ||
| | | | ||
*The YaSM process for building new services includes activities for testing the required service components before they are being deployed. | *The YaSM [[LP3: Build new or changed services|process for building new services]] includes activities for testing the required service components before they are being deployed. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|10 Deploy | |10 Deploy | ||
Line 121: | Line 121: | ||
| | | | ||
*This USMBOK lifecycle stage cannot be directly related to particular YaSM processes. | *This USMBOK lifecycle stage cannot be directly related to particular YaSM processes. | ||
*A number of YaSM processes may contribute to support services immediately after their deployment; for example, service operation may monitor particular parts of the (newly deployed) service infrastructure to verify if the service performs as expected under real customer workload. | *A number of [[Service Management Processes|YaSM service management processes]] may contribute to support services immediately after their deployment; for example, service operation may monitor particular parts of the (newly deployed) service infrastructure to verify if the service performs as expected under real customer workload. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|12 Operate and Support | |12 Operate and Support | ||
Line 190: | Line 190: | ||
*[[SP1: Set up and maintain the service management system]] | *[[SP1: Set up and maintain the service management system]] | ||
| | | | ||
*Service management policies are drawn up and maintained by YaSM's process for maintaining the SMS. | *[[YaSM_Glossary#Service-management-policy|Service management policies]] are drawn up and maintained by YaSM's process for maintaining the SMS. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|1.3 Customer Portfolio Management | |1.3 Customer Portfolio Management |
Revision as of 17:44, 11 October 2018
Comparison: YaSM and USMBOK™ (Universal Service Management Body of Knowledge)
Part of: YaSM vs. other service management frameworks and standards
About USMBOK™
USMBOK™ (Universal Service Management Body of Knowledge) [1] is a service management framework that continues to gain in popularity.
As the authors of USMBOK state, "USMBOK includes a set of generally accepted terms, methods, concepts and best practices". The framework "introduces outside-in or customer centric thinking to the traditional ITSM thinking", while sharing many of its underlying principles with other service management frameworks and standards such as ITIL® [2] and ISO/IEC 20000 (USMBOK specifically refers to a "service management system", a term which figures prominently in ISO 20000). [Clayton, 2012]
For those reasons, it was both desirable and feasible to take the guidance in USMBOK into account when developing YaSM. YaSM, however, cannot claim to be a "USMBOK process model". Organizations that want to achieve close alignment of their processes with the USMBOK recommendations are advised to obtain additional guidance from the USMBOK publications.
Note: YaSM is not endorsed by the authors of USMBOK.
The USMBOK guide includes a description of the service lifecycle, representing significant service stages from identification of an opportunity to provide a service to service retirement. For each lifecycle stage, USMBOK describes a number of elements:
- Primary inputs
- Primary outputs
- Major influences from the customer perspective
- Major influences from the service provider perspective
- Major activities performed during the stage.
The following table provides an overview of how each stage in the USMBOK™ service lifecycle relates to one or several YaSM service management processes, to illustrate that YaSM and USMBOK share many basic principles. Its aim is not to provide a detailed and scientifically correct cross-reference between the two frameworks.
Note: This table is based on the 2012 edition of the USMBOK Guide.
USMBOK™ service lifecycle stages | Related YaSM processes | Notes |
---|---|---|
1 The Opportunity Stage |
| |
2 Require |
| |
3 Define |
| |
4 Plan |
| |
5 Concept |
| |
6 Approve |
| |
7 Design |
| |
8 Develop (Build) |
| |
9 Assure |
| |
10 Deploy |
| |
11 Commission |
|
|
12 Operate and Support |
| |
13 Maintain |
| |
14 Revise |
| |
15 Retire |
|
|
The following tables provide an overview of how each USMBOK knowledge domain/ area relates to one or several YaSM processes:
- 1: Service Customer management
- 2: Service Fulfillment Management
- 3: Service Quality Management
- 4: Service Delivery Management
- 5: Service Operations Management
- 6: Service Infrastructure Management
- 7: Service Value Management
Note: This information is based on the 2012 edition of the USMBOK Guide.
1 - Service Customer Management
USMBOK™ knowledge domains/ areas | Related YaSM processes | Notes |
---|---|---|
1.1 Governance and Regulations Management |
| |
1.2 Policy Management System |
| |
1.3 Customer Portfolio Management |
| |
1.4 Customer Relationship Management |
| |
1.5 Customer Continuity Management |
| |
1.6 Customer Risk Management |
| |
1.7 Customer Requirements Management |
|
2 - Service Fulfillment Management
USMBOK™ knowledge domains/ areas | Related YaSM processes | Notes |
---|---|---|
2.1 Service Marketing |
| |
2.2 Service Planning |
| |
2.3 Service Provision Management |
| |
2.4 Provider Relationship Management |
| |
2.5 Service Request Management |
| |
2.6 Service Opportunity Management |
|
3 - Service Quality Management
USMBOK™ knowledge domains/ areas | Related YaSM processes | Notes |
---|---|---|
3.1 Service Quality Planning |
| |
3.2 Service Excellence | ||
3.3 Service Lifecycle Management | ||
3.4 Capability Management | ||
3.5 Performance Management | ||
3.6 Audit and Assessment Management |
4 - Service Delivery Management
USMBOK™ knowledge domains/ areas | Related YaSM processes | Notes |
---|---|---|
4.1 Service Level Management |
| |
4.2 Service Asset Management |
| |
4.3 Service Security Management |
| |
4.4 Service Capacity Management |
| |
4.5 Service Continuity Management |
| |
4.6 Service Availability Management |
|
5 - Service Operations Management
USMBOK™ knowledge domains/ areas | Related YaSM processes | Notes |
---|---|---|
5.1 Service Support Management |
| |
5.2 Operations Level Management |
| |
5.3 Service Supplier Management |
| |
5.4 Service Incident Management |
| |
5.5 Service Problem Management |
| |
5.6 Service Impact Management |
|
|
6 - Service Infrastructure Management
USMBOK™ knowledge domains/ areas | Related YaSM processes | Notes |
---|---|---|
6.1 Service Facilities Management |
| |
6.2 Service Application Management |
| |
6.3 Service Systems Management |
| |
6.4 Service Configuration Management |
| |
6.5 Service Change Management |
| |
6.6 Service Release Management |
|
7 - Service Value Management
USMBOK™ knowledge domains/ areas | Related YaSM processes | Notes |
---|---|---|
7.1 Financial Management of Services |
| |
7.2 Service Value Mapping |
| |
7.3 Service Lean Thinking |
|
|
7.4 Service Know-ledge Management |
|
|
References
- [Clayton, 2012] Clayton, Ian M.: The Guide to the Universal Service Management Body of Knowledge (USMBOK™). - Service Management 101; USA, March 2012.
Notes
[1] USMBOK™ is a registered trade mark of Virtual Knowledge Solutions International Incorporated (VKSII).
[2] ITIL® is a registered trade mark of AXELOS Limited.
Is based on: The YaSM Process Map. - Document: "USMBOK™ (Universal Service Management Body of Knowledge)"
By: Stefan Kempter and Andrea Kempter , IT Process Maps.
About USMBOK › USMBOK lifecycle stages and YaSM processes › USMBOK knowledge domains and YaSM processes