Skip to main content

Monitor Control Loops

One of the lesser utilized yet powerful ideas in ITIL is the concept of systems or feedback loops. ITIL defines a system as
A group of interacting, interrelated or interdependent components that form a unified whole, operating together for a common purpose.
There are two types of systems:

·         Open-loop systems – value of outcome has no influence on input; performs a specific activity regardless of environmental conditions
·         Closed-loop systems – value of outcome influences input; responds to changes in the environment
Using these concepts we can establish a powerful approach for managing and improving the ITIL processes we have implemented. One technique is called the Monitor-Control Loop. The loop consists of a set of steps that produces feedback to help improve individual process steps, the process as a whole, the stages of the lifecycle and the lifecycle as a whole.
·         Begin the loop by conducting an individual process step by taking inputs and creating outputs. While conducting the step monitor the activity and the output. Monitoring involves observing the activity and gathering data about the step or output.
·         Compare the data against an established norm. The norm will come from the targets established in the Service Level Agreements and in the Critical Success Factors (CSF) and Key Performance Indicators (KPI) determined for the process.
·         Control the process by making improvements or changes to the way you conduct the activity or step based on the variance or difference from the norm.
·         Continue to monitor-compare-control for the next step of the process.
You can then apply the monitor-compare-control steps to the process as a whole by monitoring the final output of the process, comparing against more tactical and strategic norms established through your service catalog and portfolio and controlling the process by making overall improvements to the process. The loop can then be expanded to monitor-compare-control the lifecycle stages and the whole lifecycle.

Monitor-Control Loops provide a simple and effective way of ensuring that your processes are delivering on the promises you make to customers and users in terms of value.

Comments

Unknown said…
I thought this was the most powerful element discussed in Managing Across the Lifecycle. Thanks for sharing this!

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