00 — Overview

Work & Supply network member (Steps 5 and 6 of the asset-condition programme). The demo data is fictional; the wear patterns and their weights are placeholders until the reliability engineers set the real ones.

What Condition Monitoring is

A Result is one occasion on which a unit's compartment or system was examined: an oil sample, a vibration survey, a thermography run, an inspection. A ResultValue is one measured value from it. The app is generic: oil specifics (iron, soot, viscosity, make-up oil, oil hours) are ordinary parameters, not columns.

It is keyed by maintenance group + SMCS code + analysis method (and site for a site row; empty means overall). The modifier (LH, B1 …) is optional on a result and is not part of the population key. No component identity is stored anywhere.

The models

Results & alerts (4) - Result (condition.result, RS-…) — the unit, the maintenance group and site at the date taken (snapshots), the SMCS code, optional modifier, the method, taken_at (never the lab's date), the SMU (Lifecycle's value at taken_at), smu_reported (what the sheet said), the lab's own id and its comments. - ResultValue — one value: our severity, the standard it was rated against, and the rate per 100 SMU. - ConditionState — the current standing per unit + SMCS (+ modifier) + parameter, and when its series was last reset. - ConditionAlert (condition.alert, CA-…) — raised for an elevated or urgent value; links to the Work order raised for it.

Wear patterns (3) - WearPattern — several values that rise together read as one developing problem: for a maintenance group (or all groups) and an SMCS code, a score for possible and for confirmed, the wording (frozen on the alert), and a corrective Work template. - WearPatternMember — one value in a pattern: the lowest severity that counts (elevated or urgent), a weight (negative rules the pattern out) and whether it is required. - PatternEvaluation — how a result scored against a pattern, with the members met and missing, the confidence and whether the score is rising.

Standards (2) - ReliabilityEstimate — the mean time between removals (MTBR) for a group + SMCS code in the main SMU: computed from the failures once there are enough, otherwise an engineer's industry estimate with its source. Context beside an alert, never a rating. - ParameterStandard — one thresholds table: statistical (mean, SD, count; elevated at 1 SD, urgent at 2 SD) or engineered, per parameter, group, SMCS code and method; a site row or overall. Either level may be empty.

Methods & parameters (2) - AnalysisMethod — the population key's method (a spectrometer, an acid digestion). - MonitoringParameter — what is measured; descending (a falling value is worse, e.g. viscosity); rated false for context values (oil hours, make-up oil, oil changed).

The demo data