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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:25:14 UTC

MNT.1:10 - Architectural Rationale

Function, configuration and control are identified together because each can invalidate the same apparently sensible repair. Making them one entry Method is less costly than diagnosing the wrong unit and correcting the plan later. It does not make this entry compulsory: direct condition, policy or fleet questions can start from already adequate identification.

Maintenance retains the function-in-use question. Broader investment, disposal and service redesign remain decisions of their own practices.