Skip to main content

Six Reasons to Read the Microsoft Operations Framework (MOF)

The Microsoft Operations Framework (MOF) is a well written, meaningful, asset-rich framework that is often overlooked in favor of its higher profile cousins ITIL, Cobit and ISO/IEC 20000.   Unfortunately, the big "M" that stands in front of the framework has created the perception that MOF is only relevant to Microsoft environments.  Nothing could be further from the truth - Microsoft has invested a great deal of resource and effort in creating MOF intellectual property and assets - giving it all away for free for anyone, in any environment, that is interested in learning more.  In fact, Microsoft considers you a Microsoft customer if you are working at a desktop or laptop running a Microsof operating system.

Microsoft's goal in developing MOF was to improve the effectiveness and efficiency of IT service providers, thereby enabling those providers to get a better return on their infrastructure, applications and tools.  

Here are six good reasons to consider learning more about MOF:
  1. It is compatible with ITIL.  You can "cherry pick" the guidance that makes sense from both frameworks.   If you are already down the ITIL path, some of the guidance, assets and templates may help you overcome some of your bottlenecks and challenges.  MOF may also help to clarify some of the more complex ITIL concepts such as service models - MOF's service maps are easier to understand
  2. It is much more prescriptive and offers up scripted questions at the task or activity level
  3. It uses familiar IT vocabulary - do your clients want "utility and warranty" or do they want "reliability".   
  4. There are many job aids and templates available.  Microsoft has invested quite a bit in creating MOF assets as part of its' Solution Accelerator program.
  5. It is tool independent.  Microsoft does not tie MOF back to any of it's products or services.
  6. It's free - need I say more?

Comments

Unknown said…
Thanks for sharing this. I had unfairly dismissed MOF as a useful resource.

Popular posts from this blog

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, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 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 1. 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.      ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...