MNT.Preface:1 - The working problem and practical gain

A useful maintenance result connects knowledge of a System’s condition to the functioning that someone needs. The practitioner may be an engineer choosing policy, a technician preparing an intervention, a planner coordinating access, an operator receiving control or a programme lead comparing fleet history. Their questions are related, but their results differ.

The name makes both engineering and management visible. Engineering includes failure interpretation, intervention choice and functioning verification. Management includes policy, service capability, information, programme, coordination and continuation of actual practice, not just scheduling or resource administration. Maintenance Engineering and Maintenance Management are both established expressions; the shorter engineering name also has broad uses. This framework’s compound name makes its connected contribution explicit without dividing the sixteen Methods into two separate products.

An abnormal signal alone does not decide the response. The relevant failure may be uncertain, a suitable part may be unavailable, or testing and restoration may not fit the loss-of-service window. At fleet scale, raw counts can favour the wrong group. At practice scale, a revised manual can be available while the older Method remains in use.

The language helps readers make those connections without imposing a complete intervention-and-return sequence on every request. Its gain is a supported maintenance decision, feasible selected work and a truthful account of what can be used afterwards. A recommendation or a decision to retain an adequate policy can be that complete result. A stronger claim is withheld only by the limit that actually affects it.

The maintained subject is the functioning of Systems in use, especially physical and cyber-physical equipment under identifiable operating conditions. Maintenance includes preserving or restoring the required contribution and selecting its policies, support and programme. It interacts with engineering design, operation, organizational provision and asset management. A choice about an asset’s continued use, renewal, replacement, repurposing or withdrawal retains its own value-oriented decision, as do a new service concept and a changed engineered design.

For one pump, selecting maintenance policy or an intervention to preserve or restore required functioning is a maintenance result. Comparing whether to continue its use or choose another asset option by value, costs, risks and service effects is an asset-management result, even for that single pump. Conversely, coordinating a fleet’s maintenance programme remains MNT.13. A replacement may occur in either question; the verb, horizon, job title and number of assets do not decide the boundary. One case can need both contributions.

The adjacent Engineering Asset Management Principles Framework concerns engineered assets, asset Systems and portfolios. Related Enterprise Asset Management terminology also includes substantial physical-asset, maintenance, information and cross-functional practice; it does not mean software alone. The two field expressions do not make every external source’s scope identical. A particular receiving question identifies which asset-management contribution is needed. Asset existence and use over time are distinct from how engineering Work is organized; no universal sequence of engineering stages follows.