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 10:15:17 UTC

MNT.1:11 - SoTA-Echoing

The practice question is which boundary makes maintenance advice useful. This pattern adapts the function-and-maintenance-regime relationship in IAM’s 2024 Anatomy of Asset Management, §7.7.5, and uses SYSE.13 for configuration identity. Against a register-only starting point, it adds the required-use and control reasoning in the Solution and PS17 case. It accepts a small identification cost to avoid a wrong-subject or wrong-service answer. IAM’s broader discipline does not become this pattern’s scope. Reopen the boundary when a changed use, installed configuration or shared dependency changes the maintenance decision. See IAM’s account.