{"id":6658,"date":"2016-11-01T16:29:22","date_gmt":"2016-11-01T16:29:22","guid":{"rendered":"https:\/\/multiacademstg.wpengine.com\/20000academy\/?p=6658"},"modified":"2025-01-10T13:15:13","modified_gmt":"2025-01-10T13:15:13","slug":"what-is-the-role-of-the-service-asset-and-configuration-manager-according-to-itil-iso20000","status":"publish","type":"post","link":"https:\/\/staging.advisera.com\/20000academy\/blog\/2016\/11\/01\/what-is-the-role-of-the-service-asset-and-configuration-manager-according-to-itil-iso20000\/","title":{"rendered":"What is the role of the Service Asset and Configuration Manager according to ITIL\/ISO 20000?"},"content":{"rendered":"

From the questions that I get, I have a feeling that many of you see Service Asset and Configuration Management (SACM) as complicated. I have to tell you that you are not alone. I do ITIL<\/a>\u00a0\/ ISO 20000<\/a>\u00a0trainings and consulting projects, and I have to admit that many people share that thought. We can argue whether that\u2019s justifiable or not, but the fact is that it is so.<\/p>\n

The SACM process<\/a> affects almost everyone in the company and has interfaces to almost all other IT Service Management (ITSM) processes and functions. Even more, the SACM process goes beyond IT and ITSM. The SACM process has a strong interface to corporate finance and assets employees use, like PCs, printers, servers, network devices, etc. ISO 20000 sets direct requirements for such interfaces.<\/p>\n

What\u2019s the importance?<\/h2>\n

Both ITIL and ISO 20000 emphasize the importance of this process. There is a slight difference in the vocabulary, i.e., naming. ITIL uses \u201cService Asset and Configuration Management process,\u201d whereas ISO 20000 uses \u201cConfiguration Management process<\/a>.\u201d The requirements of both of them are pretty similar. Therefore, the person responsible for the process can have the same job description.<\/p>\n

But, how about the importance of the process and its result? To avoid theoretical explanations, just ask people involved in, e.g., Incident Management<\/a>\u00a0(e.g., incident diagnosis) or, even better, Change Management<\/a>\u00a0(e.g., change evaluation\/assessment, planning, etc.). Those processes are, basically, inefficient without SACM in place. But, those are not the only ones; actually, these were just a few of them. SACM is important for Release and Deployment Management, Problem Management, Capacity Management, Availability Management, Knowledge Management\u2026 etc.
\n

<\/div>