Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Quick guide to pm3 - version 2.3Why do we need a maintenance management model?A maintenance management model is needed bec...
Well-defined maintenance assignmentsA well-defined maintenance assignment ensures that the maintenance activities support ...
Upcoming SlideShare
Loading in …5
×

Pm3 quick guide

Why do we need a maintenance management model?
A maintenance management model is needed because maintenance assignments always involve multiple parties in one or more organizations.

  • Login to see the comments

  • Be the first to like this

Pm3 quick guide

  1. 1. Quick guide to pm3 - version 2.3Why do we need a maintenance management model?A maintenance management model is needed because maintenance assignments always involve multiple parties inone or more organizations. Those parties that utilize the result of the maintenance activities (business solutions)and those parties engaged in maintenance activities. This means that the base organization (e.g. the line manage-ment) is not a powerful enough instrument for maintenance management, but needs to be supplemented withso-called maintenance organizations. In much the same way as when adding project organizations to achieve a specificobjective. The business parties and the IT parties have a joint assignment with responsibility for different parts, themaintenance management model assists in clarifying these responsibilities. The implementation of pm3 thus resultsin a steerable maintenance assignment which achieves a higher degree of business benefits.What is pm3?pm3 is a governing model which aims to organize maintenance activities to be conducted in a business-like manner.Using pm3 enables, among other things, the establishment of decision mandates, decision forums, roles of respon-sibility, and monitoring an organization’s total amount of maintenance objects. pm3 thus provides the opportunity togovern the entire maintenance portfolio. The decision structure that is created with pm3, is advantageously used forthe development-/project portfolio as well. pm3 version 2.3 is described in “pm3 model description”1 .The basis forpm3 is described in the book “More Business-like Maintenance Management”2 and in På-syn 007 ”Affärsmässig för-valtningsobjektarkitektur – vägen till IT-governance för vidmakthållande och vidareutveckling”3 (only available in Swedish)What effects can be achieved by using pm3?A pm3 implementation results in a number of effects. The following are examples of effects achieved;• A common way of working for maintenance management within the entire organization• Cooperation between business parties and IT parties• Structure for management by objectives connected to the maintenance portfolio• Governing structure for maintenance portfolio and development-/project portfolio• A clearer link between business management and maintenance management• A defined and measurable maintenance portfolio with set objectives• Staffing maintenance assignments according to resource calculationsWhat does pm3 contain?pm3 is built around four key components that all have to be ensured in order for maintenance activities to be costeffective. These four components are briefly described below. For a more detailed description please refer to “pm3model description, version 2.3”.• Well-defined maintenance assignments• Effective maintenance objects• Business-like maintenance organizations• Described, understood and accepted maintenance processes1 Tillgänglig via webshop www.pm3.se2 Nordström och Welander (2007).3 Nordström (2009).
  2. 2. Well-defined maintenance assignmentsA well-defined maintenance assignment ensures that the maintenance activities support the objectives andintentions set in business plans and IT strategies. This is done by implementing management by objectives for themaintenance activities, and by formulating a maintenance plan that is renewed annually. The maintenance planis the agreement regarding what is to be done during the year and is the steering document for the maintenanceorganization. The organization’s total amount of maintenance assignments is described in a maintenance portfolio,which is a part of the organization’s assignment portfolio.Effective maintenance objectsThe effective maintenance object defines what is to be maintained, and is thus also delimiting the responsibilities of themaintenance organization. A maintenance object contains business solutions, which in turn contains both business com-ponents and IT components. A maintenance object often contains multiple IT components. In order to achieve a highdegree of business benefit the mainenance object should be delimited from the business activities it is supporting.Closely related maintenance objects form an object family (OF). The organization’s total amount ofmaintenance objects are described in a Maintenance Object Architecture (MOA), whose purpose is to facilitatestrategic decisions related to maintenance (upholding and evolution) and development.Business-like maintenance organizationsThe maintenance organization has similarities with project organizations in that it is based on the roles that arestaffed from the base organization. There should be one maintenance organization for each maintenance object.The decision structure from a maintenance object up to MOA Steering Committee is illustrated in the figure below. Often consists of an existing management MOA Steering Committee team/function. Mandate to decide on the organization’s total assignment portfolio (maintenance and development) OF Steering Committee 1 OF Steering Committee 2 OF Steering Committee 3 Staffed by Business solution owners and IT solution owners within the family.Maintenance Mandate to decide about maintenance andmanagement development within the family. groups per object Staffed by Business solution manager and IT solution manager. Mandate to make decisions about activities within theDescribed, understood and accepted maintenance processes approved maintenance plan.For activities involving multiple organizational parties, it is of value to describe a common way of working. This wayof working should be common for all maintenance organizations. In pm3, a distinction is made between governingprocesses and operational processes. pm3 contains support for governing processes.How do we implement pm3 and manage in accordance with pm3?The pm3 range includes a carefully selected supply of model and methods, as well as supportive and instructionaltemplates and tools. When implementing pm3 in an entire organization, the steps in the figure below haveproved to be the most effective. MOA and Portfolio Governance of Decision about pm3 implementation IT-governance implementation maintenance structure and compilation assignmentsAn organization intending to implement pm3 would benefit from signing up for a pm3 license. The license iselectronic and contains a model description, methods and tools both to support the implementation of pm3, andsubsequently to govern and manage in accordance with pm3. The pm3 license entitles to annual upgrades to securethat the licensee always has access to the latest of pm3.Where can I find out more about pm3?På AB owns and develops the pm3 model. Visit www.pm3.se or call På AB (08-544 961 70) to learn more about howpm3 can be applied to your organization’s overall governance of maintenance and development!

×