Library / Maintenance Engineering and Management Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:40:10 UTC

MNT.12:1 - Problem frame

Use this pattern when a maintenance decision depends on connecting service history to the correct unit, installed part, configuration or applicable description. The work log says a bearing was replaced, the stock system says it was returned and the condition trend still carries the previous unit’s identifier.

Restore a usable information basis for the receiving maintenance question. Reuse SYSE.13’s configuration identity and effectivity contribution; this Method adds the service-event and exposure continuity that maintenance decisions consume. A new database, complete digital twin or plant-wide inventory is unnecessary when a smaller reconciliation answers the question.

For practice with entry dates, replacement events and component intervals, use the first-use task.