How to build an effective work program

David Berger explains the 7 steps to a planned environment.

By David Berger, P.Eng., contributing editor

1 of 2 < 1 | 2 View on one page

There are two categories of work done by maintainers, namely, work that is expected and work that is unexpected or anomalous. Work that is expected is built into your work program, complete with work plans for assets regardless of maintenance policy, including “run to fail.” Your objective should be to build a work program that balances the cost and effectiveness of the work program, with the risk that the unexpected will either happen infrequently or with little consequence if it does.

Companies are said to be in “firefighting” mode when the work program must be abandoned due to the volume and severity of unexpected “fires” each day. This column describes initial steps in moving to a more planned environment, including key elements of a work program.

1. Asset hierarchy: The first step in developing a comprehensive work program is to establish a logical hierarchy on the CMMS for all of your assets. This includes parent-child relationships from the highest level down to individual components and even failure modes. For example, the highest level might be a particular building for facility assets, production line for plant equipment, vehicle for mobile equipment, and 40-mile highway for infrastructure assets. The lowest-level components might be a fire extinguisher in a building, motor in a production line, headlight assembly in a vehicle, or 30-foot road segment as part of a highway.

One of the difficulties companies encounter in defining the asset hierarchy is deciding what level of granularity is required. Should each floor in a building be an asset? What about each room? Is a door an asset or part? Determining how many levels in the hierarchy will depend on several factors such as:

  • will be there be sufficient history collected for this asset to warrant the additional administrative effort
  • could failure modes and cause codes defined at the parent level provide sufficient clues as to the history of lower level assets; for example, for the asset “exhaust system,” cause codes like “corroded muffler” and “corroded exhaust pipe” allow users to treat mufflers and exhaust pipes as parts not assets.

2. Failure tree: For each asset or asset group, the problem, cause, and action codes are identified. The more advanced CMMS packages present these codes as nested and hierarchical, allowing users to associate a short list of problem codes to a given asset, a specific list of cause codes only relevant to each of the short-listed problem codes, and a selection of action codes tied to each cause code. The failure tree forms the basis for analytics on the CMMS, such as root cause analysis (RCA) and Pareto analysis for troubleshooting and continuous improvement.

David Berger, a Certified Management Consultant (C.M.C.) registered in Ontario, Canada, is a Principal of Western Management Consultants, based in the Toronto officeDavid Berger, a Certified Management Consultant (C.M.C.) registered in Ontario, Canada, is a Principal of Western Management Consultants, based in the Toronto office. David has written more than 200 articles on a variety of topics such as maintenance management, operations management, information technology, e-commerce, organizational design, and strategy. In Plant Services magazine, he has written a monthly column on maintenance management in the United States, as well as three very extensive reviews of maintenance management systems available in North America. David has done extensive work in the areas of strategy, information technology and business process re-engineering. He can be reached at
Subscribe to the Asset Manager RSS feed

3. Asset master: Fundamental to any work program is a complete record of static information for each asset in the asset hierarchy. This includes tombstone data such as asset type, manufacturer, make, model, serial number, and date of installation. Most CMMS packages also allow user-definable templates for asset groups such as pumps, flooring, bridges, and forklifts. Templates can be used to describe assets using attributes relevant to a given asset group. For example, length, width, and wall thickness are typical characteristics of piping, as opposed to horsepower, current, and speed used to describe motors. The asset master should also contain any relevant attachments including drawings, manuals, and videos.

One of the most important fields on the asset master is “asset criticality.” Some CMMS packages use a sophisticated scoring algorithm to generate criticality, while others use a single-digit, user-definable drop-down, ranging from low to high criticality. The asset criticality is essential for prioritization when planning, scheduling, assessing risk, and determining areas of focus for continuous improvement. For example, when creating a work program, always start with the most critical assets.

1 of 2 < 1 | 2 View on one page
Show Comments
Hide Comments

Join the discussion

We welcome your thoughtful comments.
All comments will display your user name.

Want to participate in the discussion?

Register for free

Log in for complete access.


No one has commented on this page yet.

RSS feed for comments on this page | RSS feed for all comments