Skip to main content

SACM (Configuration Management)

Service Asset & Configuration Management (SACM) is genuinely the one process that touches all of the other ITIL processes. SACM delivers accurate and up-to-date data and information to every other process across the lifecycle.  What is really cool about SACM is that in many cases it depends on those other processes through their defined, documented and agreed to activities, to help insure that the data and information about those assets is up to date , accurate and properly recorded through the Configuration Management System (CMS),  No organization can be truly efficient and effective without having a configuration management process to insure we understand how and where that infrastructure, application, tools, documentation and sometimes even people are being utilized in delivering business outcomes and creating value.

Service Asset & Configuration management ensures that CIs (configuration items) are properly identified; baselined and that changes made to them are properly controlled and recorded.  Most organizations have a process that will track and report on the value and ownership of fixed assets throughout their lifecycle.  Much of this is done by a part of the business known as fixed asset management or financial asset management. They tend to keep financial information on these resources and in most cases they are not usually within the same business unit as Information Technology.  They also tend not to record the relationships between these resources, how these assets are being utilized and what IT and business services they support.  SACM must ensure the proper care and maintenance of these CI that are under the control of IT services.  There should be well established intersections between these groups in order to provide the overall business a more defined and detailed view of these capital assets.

By having an accurate representation and clear visibility to your service assets:
  • Staff is better able to forecast and plan changes.
  • IT staff have a better understanding of the relationship between CIs and the services they support
  • More accurate assessments for Availability, Capacity and Continuity planning.
  • Greater effectiveness in delivery of service levels.
  • Ability to precisely identify the costs of a service.
  •  Provide greater flexibility to the business in meeting market opportunities.




Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with