YaSM and ISO 20000: Difference between revisions
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
<meta property="fb:admins" content="100002035253209" /> | <meta property="fb:admins" content="100002035253209" /> | ||
<meta property="fb:admins" content="100002592864414" /> | <meta property="fb:admins" content="100002592864414" /> | ||
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/iso-20000/Yasm-iso-20000-processes.jpg" /> | <meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/iso-20000/16x9/Yasm-iso-20000-processes.jpg" /> | ||
<meta property="og:image:width" content="1200" /> | <meta property="og:image:width" content="1200" /> | ||
<meta property="og:image:height" content=" | <meta property="og:image:height" content="675" /> | ||
<meta name="twitter:card" content="summary_large_image"> | <meta name="twitter:card" content="summary_large_image"> | ||
<meta name="twitter:site" content="@yasmcom"> | <meta name="twitter:site" content="@yasmcom"> | ||
<meta name="twitter:creator" content="@yasmcom"> | <meta name="twitter:creator" content="@yasmcom"> | ||
<meta name="twitter:title" content="YaSM and ISO/IEC 20000 | <meta name="twitter:title" content="YaSM and ISO/IEC 20000"> | ||
<meta name="twitter:description" content="YaSM and ISO/IEC 20000: service management process flows and document templates for every ISO 20000 requirement."> | <meta name="twitter:description" content="YaSM and ISO/IEC 20000: service management process flows and document templates for every ISO 20000 requirement."> | ||
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/iso-20000/Yasm-iso-20000-processes.jpg"> | <meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/iso-20000/16x9/Yasm-iso-20000-processes.jpg"> | ||
<meta name="twitter:image:alt" content="YaSM and ISO/IEC 20000: Process and document templates for every ISO 20000 requirement. The ISO 20000 Bridge provides: Service management processes; related evidence: documents, policies and records; checklists and document templates."> | <meta name="twitter:image:alt" content="YaSM and ISO/IEC 20000: Process and document templates for every ISO 20000 requirement. The ISO 20000 Bridge provides: Service management processes; related evidence: documents, policies and records; checklists and document templates."> | ||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
Line 35: | Line 35: | ||
<meta itemprop="height" content="900" /> | <meta itemprop="height" content="900" /> | ||
<meta itemprop="representativeOfPage" content="true"/> | <meta itemprop="representativeOfPage" content="true"/> | ||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/iso-20000/16x9/Yasm-iso-20000-processes.jpg" /> | |||
<meta itemprop="width" content="1200" /> | |||
<meta itemprop="height" content="675" /> | |||
<meta itemprop="dateCreated" content="2019-05-10" /> | |||
<meta itemprop="datePublished" content="2019-05-10" /> | |||
</span> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | <span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | ||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/Yasm-iso-20000.jpg" /> | <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/Yasm-iso-20000.jpg" /> | ||
Line 61: | Line 68: | ||
To meet these requirements, organizations typically must define and implement a set of service management processes which comply with the standard. But ISO 20000 does not prescribe specific processes, nor does it provide detailed descriptions that organizations could use as guidance. | To meet these requirements, organizations typically must define and implement a set of service management processes which comply with the standard. But ISO 20000 does not prescribe specific processes, nor does it provide detailed descriptions that organizations could use as guidance. | ||
<html>Some more guidance can be found in the popular service management frameworks and approaches, such as <a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" title="YaSM and the IT Infrastructure Library ITIL®">ITIL</a><sup><small>®</small></sup>, <a href="https://yasm.com/wiki/en/index.php/YaSM_and_CMMI_for_Services_ | <html>Some more guidance can be found in the popular service management frameworks and approaches, such as <a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" title="YaSM and the IT Infrastructure Library ITIL®">ITIL</a><sup><small>®</small></sup>, <a href="https://yasm.com/wiki/en/index.php/YaSM_and_CMMI_for_Services_-_CMMI-SVC" title="YaSM and CMMI® for Services (CMMI-SVC)">CMMI-SVC</a><sup><small>®</small></sup>, <a href="https://yasm.com/wiki/en/index.php/YaSM_and_COBIT" title="YaSM and COBIT (Control Objectives for Information and Related Technologies)">COBIT</a><sup><small>®</small></sup>, <a href="https://yasm.com/wiki/en/index.php/VeriSM" title="What is VeriSM™?">VeriSM</a>™, <a href="https://yasm.com/wiki/en/index.php/SIAM" title="What is SIAM Service Integration and Management?">SIAM</a>™, etc. But some of these frameworks provide only high-level descriptions of service management processes, while others are not well aligned with ISO 20000, especially regarding the requirements related to the service management system.</p> | ||
<p>As a result, there is a need for <a href="https://yasm.com/wiki/en/index.php/Service_Management_Processes" title="Service management processes">detailed process descriptions</a> that are based on established service management frameworks and concepts and, at the same time, offer better alignment with ISO 20000:</p> | <p>As a result, there is a need for <a href="https://yasm.com/wiki/en/index.php/Service_Management_Processes" title="Service management processes">detailed process descriptions</a> that are based on established service management frameworks and concepts and, at the same time, offer better alignment with ISO 20000:</p> | ||
Line 68: | Line 75: | ||
<span id="md-webpage-description" itemprop="description">The YaSM service management model thus provides a solution for every ISO 20000 requirement, and implementing the [[Service Management Processes|YaSM processes]] is a straightforward approach for obtaining ISO 20000 certification.</span><br style="clear:both;"/> | <span id="md-webpage-description" itemprop="description">The YaSM service management model thus provides a solution for every ISO 20000 requirement, and implementing the [[Service Management Processes|YaSM processes]] is a straightforward approach for obtaining ISO 20000 certification.</span><br style="clear:both;"/> | ||
==<span id="iso-20000-yasm-processes">ISO 20000 requirements and related service management processes</span>== | ==<span id="iso-20000-yasm-processes">ISO 20000 requirements and related service management processes</span>== | ||
Line 83: | Line 89: | ||
<li><a href="#Improvement" title="ISO/IEC 20000, section 10: Improvement">Section 10: Improvement</a></li> | <li><a href="#Improvement" title="ISO/IEC 20000, section 10: Improvement">Section 10: Improvement</a></li> | ||
</ul> | </ul> | ||
<p><b>Notes:</b></p> | <p><b>Notes:</b></p> | ||
Line 94: | Line 99: | ||
<p>A detailed cross-reference between the YaSM service management processes and every single ISO 20000 requirement is available in the form of the <a href="https://yasm.com/en/products/yasm-iso-20000-bridge" title="YaSM - ISO 20000 Bridge">YaSM - ISO 20000 Bridge</a>, an additional component to the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p> | <p>A detailed cross-reference between the YaSM service management processes and every single ISO 20000 requirement is available in the form of the <a href="https://yasm.com/en/products/yasm-iso-20000-bridge" title="YaSM - ISO 20000 Bridge">YaSM - ISO 20000 Bridge</a>, an additional component to the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p> | ||
<p><a href="https://yasm.com/en/products/yasm-iso-20000-bridge"><img src="https://yasm.com/en/content/videos/yasm-iso-20000-bridge/yasm-iso-20000-processes-video.jpg" width="422" height="238" class="thumbimage" alt="Video: YaSM and ISO 20000. - The YaSM process model is perfectly aligned with ISO 20000 (ISO/IEC 20000:2018). The process diagrams and document templates contained in the YaSM model make the task of designing ISO 20000 compliant processes for your organization manageable." title="Watch the video: YaSM Service-Management and ISO 20000" style="display: block; float: right; margin-right: 10px; margin- | <p><a href="https://yasm.com/en/products/yasm-iso-20000-bridge"><img src="https://yasm.com/en/content/videos/yasm-iso-20000-bridge/yasm-iso-20000-processes-video.jpg" width="422" height="238" class="thumbimage" alt="Video: YaSM and ISO 20000. - The YaSM process model is perfectly aligned with ISO 20000 (ISO/IEC 20000:2018). The process diagrams and document templates contained in the YaSM model make the task of designing ISO 20000 compliant processes for your organization manageable." title="Watch the video: YaSM Service-Management and ISO 20000" style="display: block; float: right; margin-right: 0px; margin-bottom: 10px; margin-top: 10px; margin-left: 30px" /></a> | ||
<p style="margin-top: | <p style="margin-top: 10px;">The ISO 20000 Bridge makes the task of designing ISO 20000 compliant processes for your organization manageable.</p> | ||
<p>Watch the video: "<a href="https://yasm.com/de/videos/einfuehrung-yasm">YaSM und ISO 20000</a>" (6:15 min.) | <p>Watch the video: "<a href="https://yasm.com/de/videos/einfuehrung-yasm">YaSM und ISO 20000</a>" (6:15 min.) | ||
<br style="clear:both;"/></p></html> | <br style="clear:both;"/></p></html> | ||
<p> </p> | <p> </p> | ||
Line 123: | Line 125: | ||
|} | |} | ||
<p> </p> | <p> </p> | ||
Line 156: | Line 157: | ||
|} | |} | ||
<p> </p> | <p> </p> | ||
Line 183: | Line 183: | ||
|} | |} | ||
<p> </p> | <p> </p> | ||
Line 212: | Line 211: | ||
|} | |} | ||
<p> </p> | <p> </p> | ||
Line 225: | Line 223: | ||
!style="background:#eeeeee; font-size: 100%; width:55%"|Notes | !style="background:#eeeeee; font-size: 100%; width:55%"|Notes | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|8.1 Operational planning and control | |<span id="Operational-planning-and-control">8.1 Operational planning and control</span> | ||
| | | | ||
*[[SP1: Set up and maintain the service management system]] | *[[SP1: Set up and maintain the service management system]] | ||
Line 235: | Line 233: | ||
* Outsourced services and processes are controlled via the supplier management process. This includes specifying requirements for service suppliers in line with the SMS requirements. | * Outsourced services and processes are controlled via the supplier management process. This includes specifying requirements for service suppliers in line with the SMS requirements. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|8.2 Service portfolio | |<span id="Service-portfolio">8.2 Service portfolio</span> | ||
| | | | ||
*[[LP1: Set the strategic direction]] | *[[LP1: Set the strategic direction]] | ||
Line 252: | Line 250: | ||
* The attributes to be recorded for each CI are specified in the configuration model. | * The attributes to be recorded for each CI are specified in the configuration model. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|8.3 Relationship and agreement | |<span id="Relationship-and-agreement">8.3 Relationship and agreement</span> | ||
| | | | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
Line 268: | Line 266: | ||
* External service agreements and associated service definitions specify the properties of the services to be delivered, as well as the obligations and responsibilities of the contractual parties. | * External service agreements and associated service definitions specify the properties of the services to be delivered, as well as the obligations and responsibilities of the contractual parties. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|8.4 Supply and demand | |<span id="Supply-and-demand">8.4 Supply and demand</span> | ||
| | | | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
Line 282: | Line 280: | ||
* If performance needs to be improved, improvement initiatives can be managed through the service improvement plan. | * If performance needs to be improved, improvement initiatives can be managed through the service improvement plan. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|8.5 Service design, build and transition | |<span id="Service-design-build-and-transition">8.5 Service design, build and transition</span> | ||
| | | | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
Line 294: | Line 292: | ||
* Services are built according to the specifications in the service definitions, requirements specifications and in the service implementation blueprint. The service build process includes activities to create test cases and perform tests, to verify if all service components have been deployed successfully, and to take corrective action if necessary. | * Services are built according to the specifications in the service definitions, requirements specifications and in the service implementation blueprint. The service build process includes activities to create test cases and perform tests, to verify if all service components have been deployed successfully, and to take corrective action if necessary. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|8.6 Resolution and fulfilment | |<span id="Resolution-and-fulfilment">8.6 Resolution and fulfilment</span> | ||
| | | | ||
*[[LP4.6: Resolve incidents and service requests]] | *[[LP4.6: Resolve incidents and service requests]] | ||
Line 307: | Line 305: | ||
* Known errors are documented in problem records with identified root causes and workarounds. | * Known errors are documented in problem records with identified root causes and workarounds. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|8.7 Service assurance | |<span id="Service-assurance">8.7 Service assurance</span> | ||
| | | | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
Line 324: | Line 322: | ||
|} | |} | ||
<p> </p> | <p> </p> | ||
Line 355: | Line 352: | ||
|} | |} | ||
<p> </p> | <p> </p> | ||
Line 379: | Line 375: | ||
* Improvement initiatives are only approved if submitted with clearly defined, measurable objectives and a business case. | * Improvement initiatives are only approved if submitted with clearly defined, measurable objectives and a business case. | ||
|} | |} | ||
<p> </p> | <p> </p> | ||
Line 389: | Line 384: | ||
<li><a href="https://yasm.com/wiki/en/index.php/FAQ:_ISO_20000_Certification" title="FAQ: ISO 20000 Certification">FAQ: ISO 20000 Certification</a></li> | <li><a href="https://yasm.com/wiki/en/index.php/FAQ:_ISO_20000_Certification" title="FAQ: ISO 20000 Certification">FAQ: ISO 20000 Certification</a></li> | ||
<li>Product page: <a href="https://yasm.com/en/products/yasm-iso-20000-bridge" title="The YaSM - ISO 20000 Bridge">The YaSM - ISO 20000 Bridge</a></li></ul></html> | <li>Product page: <a href="https://yasm.com/en/products/yasm-iso-20000-bridge" title="The YaSM - ISO 20000 Bridge">The YaSM - ISO 20000 Bridge</a></li></ul></html> | ||
==References== | ==References== | ||
*[ISO, 2018] International Organization for Standardization: ISO/IEC 20000-1:2018, Information technology - Service management - Part 1: Service management system requirements. - Geneva, Switzerland, September 2018. | *[ISO, 2018] International Organization for Standardization: ISO/IEC 20000-1:2018, Information technology - Service management - Part 1: Service management system requirements. - Geneva, Switzerland, September 2018. | ||
== Notes == | == Notes == |
Revision as of 16:17, 10 May 2019
Comparison: YaSM and ISO 20000 (ISO/IEC 20000:2018)
Part of: YaSM vs. other service management frameworks and standards
One of the objectives when creating YaSM® was to provide a process model that is closely aligned with ISO/IEC 20000 ('ISO 20000'), the internationally acknowledged standard for service management.
Organizations often seek certification to ISO 20000 because it enables them to prove that they are customer-oriented, efficient and effective suppliers of services. The certification can thus be used for marketing purposes, or to gain access to customers and markets which require their service suppliers to be ISO 20000 certified.
ISO 20000 sets out "requirements for establishing, implementing, maintaining and continually improving a service management system (SMS)".
To meet these requirements, organizations typically must define and implement a set of service management processes which comply with the standard. But ISO 20000 does not prescribe specific processes, nor does it provide detailed descriptions that organizations could use as guidance.
Some more guidance can be found in the popular service management frameworks and approaches, such as ITIL®, CMMI-SVC®, COBIT®, VeriSM™, SIAM™, etc. But some of these frameworks provide only high-level descriptions of service management processes, while others are not well aligned with ISO 20000, especially regarding the requirements related to the service management system.
As a result, there is a need for detailed process descriptions that are based on established service management frameworks and concepts and, at the same time, offer better alignment with ISO 20000:
The YaSM process model provides such detailed descriptions as process templates in a graphical, easy-to-read format, including document templates for the policies and other documented information that usually needs to be prepared for the certification audit.
The YaSM service management model thus provides a solution for every ISO 20000 requirement, and implementing the YaSM processes is a straightforward approach for obtaining ISO 20000 certification.
YaSM is designed to be well aligned with ISO 20000, and there are one or several related service management processes for every section in ISO/IEC 20000:2018, Part 1 (Mandatory requirements), as exemplified in the following tables:
- Section 4: Context of the organization
- Section 5: Leadership
- Section 6: Planning
- Section 7: Support of the service management system
- Section 8: Operation of the service management system
- Section 9: Performance Evaluation
- Section 10: Improvement
Notes:
- This overview omits sections 1 to 3 of ISO 20000, part 1, as they do not contain actual requirements (sections 1 to 3 cover scope, normative references, as well as terms and definitions).
- The following tables are based on ISO/IEC 20000:2018, part 1. Learn more about the new edition of the ISO 20000 standard:
A detailed cross-reference between the YaSM service management processes and every single ISO 20000 requirement is available in the form of the YaSM - ISO 20000 Bridge, an additional component to the YaSM Process Map.
The ISO 20000 Bridge makes the task of designing ISO 20000 compliant processes for your organization manageable.
Watch the video: "YaSM und ISO 20000" (6:15 min.)
Context of the organization
ISO 20000 section | Related service management processes | Notes |
---|---|---|
4 Context of the organization |
|
Leadership
ISO 20000 section | Related service management processes | Notes |
---|---|---|
5 Leadership |
|
Planning
ISO 20000 section | Related service management processes | Notes |
---|---|---|
6 Planning |
|
Support of the SMS
ISO 20000 section | Related service management processes | Notes |
---|---|---|
7 Support of the service management system |
|
Operation of the SMS
ISO 20000 section | Related service management processes | Notes |
---|---|---|
8.1 Operational planning and control |
| |
8.2 Service portfolio |
| |
8.3 Relationship and agreement |
| |
8.4 Supply and demand |
| |
8.5 Service design, build and transition |
| |
8.6 Resolution and fulfilment |
| |
8.7 Service assurance |
|
Performance Evaluation
ISO 20000 section | Related service management processes | Notes |
---|---|---|
9 Performance Evaluation |
|
Improvement
ISO 20000 section | Related service management processes | Notes |
---|---|---|
10 Improvement |
|
More about ISO 20000
- What is ISO 20000?
- Use cases: How the YaSM model supports your ISO 20000 project
- The new edition of ISO 20000:2018
- FAQ: ISO 20000 Certification
- Product page: The YaSM - ISO 20000 Bridge
References
- [ISO, 2018] International Organization for Standardization: ISO/IEC 20000-1:2018, Information technology - Service management - Part 1: Service management system requirements. - Geneva, Switzerland, September 2018.
Notes
[1] ITIL® is a registered trade mark of AXELOS Limited. - IT Infrastructure Library® is a registered trade mark of AXELOS Limited.
Is based on: The YaSM - ISO 20000 Bridge.
By: Andrea Kempter and Stefan Kempter , IT Process Maps.
Closely aligned with ISO/IEC 20000 - the YaSM model › ISO 20000 requirements and related service management processes › Context of the organization › Leadership › Planning