Condition Monitoring
What is the condition of each unit's compartments and systems — and what should be done about it? — results of examining a unit (oil samples, vibration surveys, thermography, inspections), each value rated against the maintenance group's own statistics or an engineered limit, the current standing per unit and SMCS code, the rate of change per 100 SMU, alerts, and urgent alerts sent to Work as draft work orders.
It also reads combinations: values that rise together are recognised as one developing problem (a wear pattern), and the mean time between removals (MTBR) is shown beside an alert as context.
Its central question:
TRUCK-17's transmission oil showed 240 ppm iron a week before the transmission failed: was that urgent for a 793F, did anyone act on it, and is TRUCK-09's engine iron following the same path?
It is a member of the Work & Supply network. It keeps the unit and the SMCS code, never which component was fitted (a fitment event only restarts the trend). The SMU is Lifecycle's value at the date taken; the unit's maintenance group comes from the Asset Register; an urgent alert asks Work Management for a draft work order from a template.
| Page | What's in it |
|---|---|
| 00 — Overview | What the app is, the models, the demo results, the wear patterns |
| 01 — Quick Reference | How a value is rated, trends, series resets, alerts, settings, everyday tasks |
| 02 — System Diagram | The model as a diagram, plus the interactive viewer |
| 03 — Integration | What it publishes, consumes, accepts and answers on the network |
Port 5100 · application code condition_monitoring · network domain condition.