Efficiency and metrics

The production snapshot carries scheduled minutes, run minutes, total units, ideal cycle minutes, good units and scrap units. These observed fields are the context for an efficiency result. The analyst invokes efficiency computation for one snapshot revision in the workspace. Its operation run records the attempt and reaches Succeeded only after the result-field update has been read back. That distinction matters when the calculation request succeeds but the persisted source has not changed as expected.

Metric observations hold numerator, denominator, value, unit and a coverage period, linked both to the production source and a captured source snapshot. Metric results keep their own period, dimension key, numerator, denominator, value and result status, with references to a metric definition and the operation run. Those links let a reviewer ask which rule and source window produced a displayed figure. The workspace computation is checked against fields on the production snapshot; a period and dimension result is read through its own linked result record.

• Inputs. Keep production time and unit quantities on the dated source that owns the result.
• Readings. Use metric observations for period-bounded values tied to a source capture.
• Results. Read calculated, suppressed and invalid outcomes with their reason and run reference.

Decide the unit for ideal cycle minutes and how planned downtime affects scheduled and run minutes. Agree which result dimensions are meaningful to the operations manager. A source with zero or incomplete denominator data needs a reviewed handling rule before an efficiency trend is trusted. Keep the period boundaries aligned with production dates and the capture window. An analyst and reviewer should rehearse the same case together so the displayed value, source fields and run identity can be reconciled. They should also decide which captured readings belong to the production date before comparing results from different windows.

Take a dated source with observed time and units. The analyst confirms the source revision and invokes the computation. Inspect the run number, its input hash and the numbered steps. Read back the source fields and compare the displayed result with the observed inputs. For a separately recorded metric result, open its window and check its period, dimension, definition, run and status. If a source capture is stale or a value is invalid, keep that result separate from a calculated result when preparing the manager’s trend.

• Result windows — Values by metric, period and dimension with their calculation status.
• Production results for review — Analyzed sources ready for a person’s decision.

Read efficiency calculation and result review. The reports page frames the questions a production meeting can answer.