Everything the criticality and maintenance strategy module does, in plain language.
Consequence scored per asset, dimension by dimension, on the model your organization defines.
An assessment publishes only after it is approved.
The approved letter shows on the machine card in every module of the suite.
Once an approved assessment exists, the hand-set letter stops being editable.
A visible cut through the ranking: above it, full engineering attention.
Assessments carry review dates and the ones falling due are counted where you can see them.
The ways it fails, recorded as the foundation the strategy stands on.
Every PM task names the mode it prevents or catches.
Assets and existing PM programs come in from spreadsheets.
Strategies are versioned, so "what changed" has an answer.
See which tasks protect something and which protect nothing.
Each task gets a deliberate decision, recorded.
Hours per year spent on tasks that map to no failure mode, in one figure.
The module records your engineering decisions. It does not make them.
Changes to the live program queue for review and approval.
The approved program leaves in a format your CMMS loads.
What made it into the CMMS, tracked area by area.
Spares derived from failure modes for the assets that matter most.
A program summary that states its own scope, window, and provenance.
Rankings and strategies attach to the same machines every other module uses.
View-only unless granted a level in this module; administrators everywhere.
Ask which assets are critical or what changed and get figures with links.