Preface
EAM.Preface:1 - The working problem and practical gain
Engineering asset management concerns the value obtained through engineered assets over time. A practitioner may need to compare the continued use of one pump, choose an interacting set of renewals, reconsider a service contribution, or improve the practice that makes those decisions. Asset count does not determine which of these questions is present.
An equipment register can identify property without explaining what service needs it. An alarm can justify investigation without deciding replacement. A project with attractive savings can consume the funding that a necessary programme needs elsewhere. A completed intervention can leave its promised service unestablished. Each difficulty calls for a result that a particular recipient can use.
This language helps the practitioner establish the required contribution, compare supported alternatives, reconcile their interactions and return the asset answer that was requested. The answer can be sufficient advice, a decision to retain an option, an authorized programme or an exact unmet condition. A whole-enterprise study is not the default price of answering one asset question.
An asset is considered here for the value its use can contribute. The governed objects are engineered assets, an interacting asset System and a portfolio of assets or interventions. A portfolio groups assets for management; evidence of functional interaction is still needed before treating it as one System. The framework governs decisions about their contribution, use and change, and the continuation of that decision practice. It leaves equipment diagnosis, design realization, protected maintenance work and service operation with their relevant Methods.
The Russian plain designation is управление техническими активами. The English name makes the engineered-asset scope visible. Enterprise Asset Management is a serious overlapping professional usage that includes maintenance, information and cross-functional practice. It is neither confined to software nor to large enterprises. Here the Engineering qualification states this language’s subject; portfolio management names only one of its questions.
EAM.Preface:2 - Forces and working distinctions
A decision needs enough scope to include an answer-changing dependency and enough restraint to remain usable. A longer horizon can expose renewal and residual value while increasing uncertainty. Equal financial units help comparison but cannot turn a service obligation or unsupported engineering claim into an acceptable option. Local efficiency can move cost, work or loss of service to someone else.
The practitioner therefore keeps several distinctions visible in ordinary working language. Required service differs from observed demand and usable capacity. An installed unit differs from its description. A condition observation differs from diagnosis and a qualified forecast. An option differs from a selected programme; a forecast benefit differs from an obtained outcome.
A recommendation also differs from authorization. An analyst can answer a committee’s request by giving the supported option, reasons and conditions. The committee separately makes the decision within its authority. A funding board may control allocations, a service authority may control delivery commitments, and maintenance or operating authorities may control work and resumption. Supplying a cost estimate does not grant any of those powers.
Use the detail that can change the answer. Existing evidence can be sufficient. Where a missing result matters, ask what an attainable inquiry could resolve and include obtaining, interpreting and maintaining its evidence, delay, disruption and displaced work in its burden. C.11.DUA supplies the general guidance for that choice.
EAM.Preface:3 - Architectural Rationale
The sixteen contributions are related by the results they supply, rather than by one lifecycle diagram. Four publication parts help navigation; they are not stages.
EAM.1–EAM.3 establish what asset contribution is being decided and which information applies. EAM.4–EAM.6 assess service need, actual condition and performance, and capability under the relevant dependencies. When the demand basis is missing, EAM.4 constructs a scenario from compatible observations and explicit driver changes; EAM.6 receives its quantity, location, period and conditions. For an interacting asset system, EAM.6 derives lost contributions from shared dependencies and follows service and reserve through recovery intervals. A clear existing result can enter directly into a later comparison; every use need not reconstruct those accounts.
EAM.7 and EAM.8 generate materially different ways of obtaining or continuing the contribution. Acquisition, modification, maintenance, renewal, lease, changed use and withdrawal can compete at that scope. EAM.8 connects the technically supported intervals of a continuing policy to its dated work, economic consequences and ending. FIN.6 and FIN.7 supply financial construction and valuation where needed; their return must retain the same service policy, perspective, dates and assumptions. EAM.9 resolves conflicts among proposed decisions; EAM.10 compares the full combination where allocations and interactions matter. It distinguishes technical prerequisites, shared resource limits and joint consequences, reconstructing costs or benefits from the actual combined work. FIN.9 supplies the financial interaction and dated funding comparison when needed. EAM.11 establishes a complete feasible timing proposal using the requisite operating and maintenance results. A project ranking, capacity bound or sum of job durations cannot substitute for all three questions.
EAM.12 integrates the qualified inputs and distinguishes the advice requested from the asset decision actually made. EAM.13 tests the retained plan against obtained outcomes and changed premises. The return may go to demand, configuration, engineering support, an option or its authority. There is no requirement to restart every earlier pattern.
EAM.14–EAM.16 address three different continuing subjects. The management system arranges responsibilities, information flows and provision. A Method supplies reusable operations for obtaining an asset-management result. Culture concerns the continuation and change of practice among people: transmission, actual use, recognition, selection and retention have distinct evidence. A new application, a revised comparison rule and a teaching initiative can affect one another without becoming the same change.
The asset’s functional dependencies, the portfolio allocation, the team calendar, configuration evidence and actual authority are different structures related through identifiable assets, services and decisions. A single decomposition loses some of those relations. A.22 gives guidance for selecting the constituents, actual relations and constraints needed for a particular structural question. C.32.MWA helps combine contributions from the different structures needed for the practice.
Maintenance can fully answer a maintained-functioning question for one asset or a fleet. EAM adds the question of value among asset options, including for one asset. Operations Management supplies a qualified account of service, demand, operating capability or coordination where needed. Systems Engineering supplies an applicable functional alternative or configuration account. EAM uses those results for the asset choice rather than reproducing their full disciplines.
This division avoids three losses. A portfolio-only language would exclude the D comparison. A maintenance-only language would leave its common-horizon value question unanswered. A universal financial score would conceal ineligible service, engineering or authority conditions. A complete enterprise application is one possible support, not the definition of the practice.
Constituent actions in ongoing work. While assessing an asset’s service capability, interpreting a condition reading can constitute part of that assessment, and the assessment can constitute part of an ongoing renewal comparison. A changed service requirement can make a formerly acceptable reading inadequate for the comparison. The team needs the measurement interpretation and service reasoning that connect the reading to the decision. EAM.6 develops the capability question, and EAM.10 retains the shared operating, financial and specialist constraints on the combination. If these connections are unclear, use B.1.5.EW to recover how the reading interpretation participates in the ongoing assessment and renewal comparison, and which constituent operations the team must perform or obtain. Carry the conditions of the larger work through those connections: merely supplying a result for later use does not make an action part of that ongoing work. A good local condition result leaves the whole renewal choice open.
EAM.Preface:4 - Recognition, assurance and ordinary stops
Recognition begins with the working cue: an estimate for the wrong unit, an alarm presented as a diagnosis, a forecast treated as a mandate, two feasible jobs that fail together, or a promised benefit treated as achieved. The relevant pattern identifies a useful first move.
Assurance follows the requested claim. Technical eligibility needs applicable engineering support. Cost comparison needs consistent perspective, cash timing, horizon and sensitivity. Programme feasibility needs the actual allocation, service and whole-work conditions. An authorization claim needs the responsible decision. Actual effectiveness, causation and cultural retention each need evidence of their own subjects.
The checklists ask whether those contributions can be recovered; they do not supply missing domain evidence. Complete information, a causal model, an optimizer or a new trial is unnecessary when the available supported result already answers the request. A smaller truthful answer remains useful when a stronger claim is unsupported.
The two common applications demonstrate conditional economic and allocation reasoning. They do not establish real pump reliability, hydraulic behaviour, investment performance or equipment-work permission. A practitioner must obtain the actual inputs and authority required by the intended use.
EAM.Preface:5 - Predictable mistakes, consequences and bias
Starting from “replace this asset” can remove a viable maintenance or service alternative before comparison. Ranking condition scores can spend money on a less useful programme. Comparing purchase prices over unequal horizons can hide operating burden and remaining service value. Adding a generic risk allowance to costs that already include the same response can count them twice.
The positive corrections are small and specific: restate the required contribution, compare qualified whole options, retain separate conditions, and reconcile the complete programme. The CityWater cases show that an individually sound replacement recommendation can coexist with a different programme recommendation.
The process can still privilege those who fund or request a project. Identify whose service, work, access and future costs change. Do not silently turn an unpriced consequence into zero or a missing observation into evidence of no effect. A technology supplier’s claim and an available template establish neither applicable performance nor actual use.
Using the language adds some comparison and coordination burden. Its benefit is a decision whose scope, conditions and consequences the recipient can understand. Retaining a supported option or correcting a small information mismatch can be the useful outcome. The appropriate depth depends on the decision, possible consequences and attainable evidence.
EAM.Preface:6 - Current sources and what they support
The GFMAM Asset Management Landscape, third edition (2024), and IAM’s Asset Management — an Anatomy, version 4 (2024), locate this work within broad professional asset-management practice. This framework turns selected concerns into explicit practitioner operations and examples; those publications do not establish the effectiveness of these particular Methods.
Public ISO/TC 251 material locates the management-system relationship. NIST Handbook 135, 2025 edition, supplies dated cost and ending treatment, common horizons and choice under funding constraints. Its federal application conditions are not imported into CityWater. The water-planning guidance supplies the component and critical-period construction adapted in EAM.4; IAM’s recovery treatment informs EAM.6. Corporate Finance supplies the developed cash, ending-valuation and joint-consequence operations used in EAM.8 and EAM.10. Their qualified returns are identified below.
General evidence, comparison, information and cultural distinctions remain with FPF. The references identify the specific contributions and receiving uses. Those source relations support reasoned use and refresh; a cited Method description still needs to yield a qualified result for an actual asset case.