From ranking assets to a running PM program, and the reasoning behind each step.
A criticality assessment scores consequence on your model and goes through approval before anything changes.
An approved assessment publishes the criticality every module shows on that machine, everywhere in the suite.
Once a plant has an approved assessment, the manually set letter goes read-only. One source of truth, deliberately.
The cut that separates assets deserving engineering attention from the rest, drawn and visible.
Each strategy is built on the ways the asset fails, so every task exists for a reason that is written down.
"Why do we do this PM?" has an answer on file: the failure mode it manages.
Bring your asset list and existing PMs in from a spreadsheet and start from what you have.
Lay the existing PM program against failure modes: keep, revise, add, retire - with the wasted hours quantified.
The module never prescribes an interval. It shows the case and records the call, because a wrong interval costs bearings.
Proposed changes queue for review instead of editing the live program directly.
The approved program exports in a file your CMMS takes.
What has actually been loaded, area by area, so "deployed" is a fact rather than a feeling.
The parts an important asset needs on the shelf, listed from its failure modes.
The whole program summarized with its scope and dates stated, so the quoted number means what the reader thinks.
The demo plant has this module switched on, with records already in it.