A skills matrix that tells you who can safely do the work.
Role lanes, qualifications backed by evidence, and the risk dashboard that names the task resting on one person - before the resignation letter does.
The demo plant has this module switched on. Open it and look around.
Lanes, not job titles
A role is the work it is expected to cover. Each lane lists its skills and required levels, so "qualified" means something you can point at.
Evidence behind every checkmark
A qualification is granted against evidence - the certificate, the assessment, the sign-off. A matrix built on nods is a wish list.
Risk you can see coming
Single points of failure, departure risk, and coverage gaps surface on a dashboard, ranked by how much they would hurt.
Training plans that answer to the plant.
A plan exists because a gap exists: the skill the area is missing, the person leaving, the machine arriving. Progress is tracked against the matrix, not a spreadsheet.
- Plans trace to a reason. Every development plan names the gap or the event that justified it.
- Qualification is the finish line. A plan completes when the matrix cell changes level, with evidence attached.
- Certifications with expiry dates nag before they lapse, not after.
Each bar is the plans that closed that quarter, showing up as coverage.
Complete on its own, stronger on the suite.
Plenty of plants need a real skills matrix before they need anything else. The module sells alone - and if the rest of the suite arrives later, the crew is already in it.
- Works for any maintenance discipline, not just lubrication - lanes are yours to define.
- Assignable work meets qualified people. With the lubrication module on, a route can warn when it lands on somebody outside the lane.
- Corporate sets the floor, sites go further, the same scoping every collection in the suite uses.
Ranked by how alone the last qualified person is.
Every module reads the same records.
The asset registry you build for this module is the one every other module runs on. Add the next one and it starts loaded.
Root cause analysis
Investigations with cause trees, evidence, and corrective actions that actually close.
Criticality and maintenance strategy
Rank what matters, then build the PM program those rankings justify.
Asset Health
One number over every critical asset: healthy or at risk, and the named reasons why.
Capital Projects
Stage-gate reliability readiness, so no machine starts up with ten years of problems already installed.
Lubrication management
Tag every point, run every route, and catch a failing bearing while it is still a planning problem.
Know your crew like you know your machines.
Open the demo plant's matrix and find the pale column. It takes one look.