Skip to main content

Financial Management and SACM KPIs

A learner who is working towards developing a Cost Management department recently asked about key performance indicators (KPIs) for the Financial Management and Service Asset and Configuration Management (SACM) processes.    

ITIL 2011 actually maps Critical Success Factors (CSFs) to KPIs for each process.  Key performance indicators for Financial Management can be found in section 4.3.8 of the Service Strategy book while those for SACM can be found in section 4.3.8 of the Service Transition book.

While I cannot list all of the KPIs for both processes, here is a good sample:

Financial Management
  • The financial management for IT services framework specifies how services will be accounted for, and regular reports are submitted and used as a basis for measuring the service provider’s performance.
  • All strategies have a comprehensive analysis of investment and returns, conducted with information from financial management for IT services.
  • Internal service providers receive the funding required to provide the agreed services – showing a break-even at the end of the financial planning period.
  • Customer and service assets are recorded in the configuration management system, and all required financial information is complete.
  • Regular reports are produced on the costs and utilization of customer and service assets and action plans are targeted for any deviations from required performance or utilization.
  • The cost of each service is reported on a monthly, quarterly and/or annual basis, and compared with the return achieved by that service
  • The service provider uses an accounting system, and this is configured to report on its costs by service.
  • Regular reports are provided on the costs of services in design, transition and operation.
  • Improved accuracy in budgets and charges for the assets utilized by each customer or business unit
  • Increase in re-use and redistribution of under-utilized resources and assets
  • Reduction in the use of unauthorized hardware and software
  • Reduction in the average time and cost of diagnosing and resolving incidents and problems
  • Improved ratio of used licences against paid-for licences
  • Improvement in time to identify poor-performing and poor-quality assets
  • Reduction in risks due to early identification of unauthorized change
  • Increased quality and accuracy of configuration information
Service Asset and Configuration Management
  • Improved accuracy in budgets and charges for the assets utilized by each customer or business unit
  • Increase in re-use and redistribution of under-utilized resources and assets
  • Reduction in the use of unauthorized hardware and software
  • Reduction in the average time and cost of diagnosing and resolving incidents and problems
  • Improved ratio of used licences against paid-for licences
  • Improvement in time to identify poor-performing and poor-quality assets
  • Reduction in risks due to early identification of unauthorized change
  • Increased quality and accuracy of configuration information

Comments

annasalvator said…
I like your post and truly speaking it was awesome. Anyways keep it up and keep continue with your valuable thoughts.Thanks for sharing this. high interest savings account

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service Offe

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