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.