Part A - Outcomes and the Asset Information Basis
EAM.1 - Frame the Engineered Assets and Required Outcomes
Type: Method Status: Stable
EAM.1:1 - Problem frame
Use this pattern when an asset decision lacks a clear service or value question. A pump has become expensive to maintain, an asset register has been completed, or a replacement budget is available, but the practitioner still needs to establish what the choice should achieve.
Begin with the requested answer: for which asset and receiving use should the practitioner compare continued use or change, over what horizon? Agree with the decision maker which options to compare for the named asset, which service they must provide, and over what period. An existing adequate framing can be retained.
A single asset can need this work. When the question is only how to maintain an already selected function, use the applicable maintenance guidance directly.
EAM.1:2 - Problem
Ownership, a register boundary and a functional boundary often differ. One pump can serve several areas; a group of assets can share a budget without operating as one System. Beginning from the accounting list can therefore omit a service dependency or include equipment irrelevant to the decision.
An equally costly mistake begins with a favored action. Calling the question “replace the pump” hides whether the needed outcome could be obtained by maintenance, a different operating arrangement, shared service or withdrawal of an obsolete contribution.
EAM.1:3 - Forces
A narrow boundary makes comparison manageable, while a missing dependency can reverse the answer. Current users, future users and the people funding the asset can value different outcomes. A short horizon can conceal renewal costs; a remote horizon can invite unsupported forecasts. Select the boundary and precision needed for the actual decision.
EAM.1:4 - Solution
Name the recipient and the requested result. Distinguish advice about options, a choice among them and authorization to act. For advice, identify what the recipient needs to decide; the practitioner can finish by giving a sufficient supported recommendation.
Identify the engineered asset, interacting asset System or portfolio. State the service it contributes to, the receiving population and the conditions that matter. Use actual unit and configuration identifiers where differences can change the answer. A portfolio is a management grouping; establish functional interaction separately when the comparison relies on it.
Recover the required outcomes and their sources. A water-delivery commitment, desired reduction in energy use and available capital are different conditions. Name who can change each consequential commitment or allocation. Do not treat a proposed improvement as an existing obligation.
Choose the horizon and perspective of comparison. State whose costs, service, risk and continuing burden matter. Include an outside dependency when changing it could alter eligibility or preference: power supply, a shared standby unit, access, disposal or a receiving service can matter even outside ownership.
Write a short framing that identifies the assets, use, desired result, horizon and material constraints. It can be ordinary prose. Keep unresolved facts only when they change the next question. Use EAM.2 for an unclear service contribution and EAM.3 for an unclear information basis.
Stop when the framing allows the recipient to ask or answer the intended asset question. A request to compare two supported options does not require reconstructing the whole enterprise strategy or completing its asset register. Reopen when the service, asset boundary, horizon or actual decision scope changes.
EAM.1:5 - Archetypal Grounding
Consider CityWater’s pump D. The maintenance practitioner can recommend an initial intervention costing €0.50 million to support continued functioning under the supplied duty and five-year maintenance policy. The infrastructure committee asks a different question: should D continue under that policy or be replaced, given the same service and comparison horizon?
A useful framing is: compare D’s supported five-year continued-use policy with replacement for its contribution to East’s water delivery, using the stated cost perspective, technical qualification and actual funding and outage conditions. This is enough to compare continued use and replacement of D in EAM.8 and EAM.9. Assess other assets where their service, funding or outage conditions affect that choice.
If D competes with A, B and C for the same funding, extend the comparison to that combination under EAM.10. The other eight stations matter through their continuing service contribution; their inclusion in the utility’s register does not require eight additional investment analyses. The common CityWater applications provide the complete constructed premises.
EAM.1:6 - Bias-Annotation
The person requesting the investment can dominate the framing. Ask which service users bear a loss, whose continuing work increases and which costs fall outside the requesting department. Include those parties through the consequences that matter, rather than adding a universal stakeholder inventory.
EAM.1:7 - Conformance Checklist
Can the reader identify the asset and use, recipient, requested result and horizon? Are service commitments, aspirations and funding conditions distinguishable? Does every included dependency change the question, and does any omitted dependency plausibly reverse it?
EAM.1:8 - Common Anti-Patterns and How to Avoid Them
A replacement request presented as the problem forecloses alternatives. Restate the required contribution before comparing interventions.
Using asset count to separate maintenance from asset management misroutes both a fleet maintenance question and a single-asset value question. Select by the decision being made.
EAM.1:9 - Consequences
The next analysis can use a shared question and stop at a useful answer. Some apparent investment problems become maintenance, operating or service decisions. The boundary can remain provisional where a missing dependency matters; the practitioner reports that limit instead of giving an unqualified recommendation.
EAM.1:10 - Architectural Rationale
Framing comes from the use of assets because that use determines relevant value, performance and alternatives. A register-first or budget-first approach remains useful for information and constraints but cannot select the decision’s purpose. Keeping the first result small supports direct use without forcing a portfolio programme.
EAM.1:11 - SoTA-Echoing
For deciding what to compare for an engineered asset, select a service-and-value question with a stated recipient, horizon and material dependencies. Adopt the proportional decision reasoning in IAM’s An Anatomy of Asset Management, version 4, July 2024, decision-making and life-cycle investment discussion (pp. 72–75). Adapt it in the Solution by identifying the requested answer before expanding the asset or information boundary. The resulting question can concern D alone while retaining a shared funding or service condition that would change its answer.
A serious alternative is to begin by preparing or refreshing the broader asset-management plan. GFMAM’s Asset Management Landscape, third edition, June 2024, section 3.4 (pp. 35–36), supplies that planning comparator. Such a plan is useful when the organization needs to settle its connected activities, rather than one already bounded option choice. For D’s question, requiring that wider planning work first would also involve assets whose treatment cannot change the comparison. The selected framing retains the consequential dependencies with less preparatory work; it deliberately gives no conclusion about the whole register or enterprise plan. Neither source prescribes CityWater’s boundary or supplies its service facts. Reopen the framing choice when an omitted dependency changes an option’s eligibility or value, the decision maker asks for a wider plan, or a changed service or horizon makes the narrow question insufficient.
EAM.1:12 - Relations
EAM.2 relates outcomes to service and capability; EAM.3 establishes the information needed for the chosen boundary. MNT.1 supplies maintained-use facts, while OPS.1 supplies an operating service and commitment account. EAM.8–EAM.12 use the resulting asset question. FPF A.1.SCR supports boundary recovery and C.11.DUA supports a sufficient answer at proportionate effort.
EAM.1:End
EAM.2 - Relate Assets to Strategy, Services, and Required Capability
Type: Method Status: Stable
EAM.2:1 - Problem frame
Use this pattern when a desired outcome has been translated directly into an asset purchase or renewal, or when an existing asset’s continuing contribution is unclear. A requirement for reliable water delivery has become “buy another pump,” but the practitioner needs to establish which capability is actually missing.
Begin with the receiving service and show how the asset could contribute to it. Return the supported outcome–service–capability relationship and any gap that changes the option choice. A supplied local service mandate can be enough; a complete strategy document is not a prerequisite.
EAM.2:2 - Problem
An asset can be technically effective without serving the current purpose. Conversely, an important service can depend on several assets whose individual records do not explain their joint contribution. Broad strategic language leaves those relations unresolved and can make a familiar construction appear necessary.
EAM.2:3 - Forces
Long-term outcomes guide investment while immediate commitments constrain what can change now. An asset can support several services with competing priorities. A detailed model can expose a missing dependency, but excessive tracing can delay a decision already supported by a simple relationship.
EAM.2:4 - Solution
State the desired outcome and its recipient. Distinguish an aspiration from an adopted objective or service obligation. Identify the required service, population, location, conditions and horizon at the grain that changes the asset decision.
Describe the contribution needed to supply that service. Use quantities and conditions where they matter: flow at the delivery point, usable storage, response time or an available operating interval. A count of installed assets is not itself that contribution.
Relate the contribution to possible assets or arrangements. One contribution can require several interacting Systems, and one asset can support several contributions. Preserve the actual dependencies instead of forcing the relationships into a one-to-one hierarchy. Use SYSE.5 when the bearer or allocation alternatives need engineering development.
Compare the needed capability with an applicable account of the present arrangement. Identify the consequential gap and its evidence. A supplied qualified result can be used directly; otherwise obtain the specific service or engineering result required. Separate a known shortfall from an uncertain forecast.
Challenge the necessity of the first asset proposal. Consider a different bearer, shared service, operating change or demand change when it could satisfy the same need. Keep a materially different alternative only with the conditions that would make its contribution real.
Return the supported relations and the next asset question. Stop when they are sufficient to generate or compare options. Reopen when the service, outcome priority or a relied-on capability changes.
EAM.2:5 - Archetypal Grounding
CityWater’s North area requires at least 1,100 m³/h in the wet season, while the supplied account supports 1,000. The gap is 100 m³/h of delivered service. The two shortlisted C options each add 200: a modification or a leased service. Both therefore meet the quantity requirement, subject to their technical and operating qualifications.
The useful relationship is from the water-delivery requirement to additional usable service capability, then to those alternative arrangements. It is not from a general growth objective directly to ownership of a new pump. The extra 100 above the minimum can matter as margin, but it is not proof that every contingency is covered.
If an authorized demand-management arrangement could reduce the wet requirement to 1,000 without an unacceptable loss, it would be another alternative. A planner’s desire to reduce the requirement does not amend CityWater’s water-service mandate; its issuing authority must make that decision.
EAM.2:6 - Bias-Annotation
Internal objectives can omit losses experienced by customers or another service area. Trace the contribution to the actual recipient and identify whose outcome changes. Do not assume that a locally favorable utilization or accounting measure represents the service’s value.
EAM.2:7 - Conformance Checklist
Is the service requirement recoverable from its source? Does each relied-on asset contribution have the right quantity and conditions? Can the reader distinguish a demonstrated gap, a forecast and an alternative proposal?
EAM.2:8 - Common Anti-Patterns and How to Avoid Them
A line from “strategy” to a purchase request does not establish the missing contribution. State the service and capability relation.
Treating installed capacity as delivered service hides configuration, access and network constraints. Use a qualified operating or engineering result.
EAM.2:9 - Consequences
The practitioner can generate alternatives against a concrete need and identify assets whose contribution is no longer required. A missing relation becomes a bounded question, while unrelated strategic analysis can remain outside the current task.
EAM.2:10 - Architectural Rationale
This pattern connects outcomes to engineering capability because asset ownership is only one way of obtaining a contribution. It retains the strategy and service decisions with their actual sources and makes the engineering allocation a separate question. That structure supports both new investment and continued-use decisions.
EAM.2:11 - SoTA-Echoing
For deciding which asset contribution a strategic or service need requires, select an explicit comparison between the required service and a qualified present capability, followed by alternative ways to close the gap. Adopt OPS.1’s bounded service and commitment result and adapt SYSE.5’s functional-organization and bearer comparison to this asset question. The Solution therefore keeps the required contribution separate from the first proposed purchase and preserves many-to-many dependencies where they matter. In North, the comparison reveals a 100 m³/h shortfall and leaves both a modification and a leased contribution available.
A serious starting alternative is to trace the investment through the organization’s strategic asset-management objectives. GFMAM’s Asset Management Landscape, third edition, June 2024, section 3.1 (pp. 29–30), provides that strategic-alignment comparator. Its contribution is the link to organizational objectives; it does not qualify either CityWater option’s delivered flow. Adapt that alignment by asking what service must change before treating an aligned project as necessary. The extra effort is one explicit service/capability comparison where adequate results already exist. It can expose a different bearer or demand option that an objective-to-purchase shortcut misses. The trade-off is that this local result does not settle competing strategic priorities; obtain that decision from its responsible source when it can change the asset choice. Reopen the comparison when that priority, the service mandate or a relied-on capability changes, or when an option cannot be distinguished without a more detailed allocation analysis. The professional source does not require the one-to-one hierarchy that the shortcut assumes.
EAM.2:12 - Relations
EAM.1 supplies the asset question; EAM.4 qualifies demand and EAM.6 compares capability. EAM.7 develops alternatives. OPS.1 supplies service and commitment facts; SYSE.5 supplies functional-organization and bearer alternatives. FPF A.6.F supports function-like claims when their meaning requires restoration.
EAM.2:End
EAM.3 - Establish the Asset Information and Configuration Basis
Type: Method Status: Stable
EAM.3:1 - Problem frame
Use this pattern when a choice depends on matching asset, condition, cost and intervention records. Two records have the same station label but concern different installed units, or a proposal uses a description that no longer applies.
Start with the decision and identify which differences would change its answer. Return a usable information basis for those assets, with unresolved matches and their consequences. An adequate current basis can be reused.
For practice with record dates, installed state and quotation validity, use the first-use task.
EAM.3:2 - Problem
A station code, serial unit, design variant and configuration description can share a convenient name while denoting different things. Combining them can attach an old condition account to new equipment or price a modification of a configuration that is not installed. Requiring a complete database before any choice creates the opposite problem: useful work waits for irrelevant information.
EAM.3:3 - Forces
Stable identifiers support continuity while changing configuration changes applicability. More data can improve the answer but adds collection, reconciliation and maintenance work. A missing match can block one option without blocking the whole asset question.
EAM.3:4 - Solution
Name the receiving decision and select the information it requires. Identify the actual assets or intended asset referents, their locations and the configuration boundaries whose differences matter. Use SYSE.13 when identity, description edition or effectivity needs a fuller account.
For each relied-on record, recover its subject, source and applicable interval. Distinguish what was designed, observed, installed or proposed. A current database entry is evidence only to the extent that its source and maintenance support the claim being used.
Match the condition and performance observations to the actual unit, duty and measurement basis. Match the intervention proposal to the installed constituents and interfaces. Match costs to that same scope and horizon. State any correspondence used to join records with different identifiers.
Resolve conflicting records at their sources. A later timestamp alone does not make a record more applicable. An inspection, installation record or responsible specialist’s reconciliation may settle the particular conflict. Preserve a known mismatch rather than averaging incompatible values.
Consider the consequence of each gap. If every plausible value leaves the requested answer unchanged, qualify the answer and continue. If the value changes technical eligibility, cost or service, obtain the smallest worthwhile applicable result or keep the affected option conditional.
Return the information needed for the choice in a form its recipient can inspect. A small table can suffice. Identify the configuration, duty or source change that would reopen it. An enterprise data-model redesign belongs in EAM.14 only when that arrangement is the recurring problem being addressed.
EAM.3:4.1 - First use with two quotations
Use this practice when you can read asset and supplier records but still need to distinguish a record’s date, the installed state and the time for which a price applies. Keep your first answer before reading the explanation and discussion. The figures and dates below are constructed teaching inputs.
Make a first attempt. C-07 has had drive configuration V2 since time 8; its installed state is confirmed for the required decision time 15. Quotation Q1 was issued at 12 and covers V1. A separate, unwithdrawn Q2 was issued at 6 and expressly covers the required V2 modification, service and appraisal horizon; its commercial terms remain valid until 20. Neither quotation is treated as a successive edition of the other. Which quotation can support the modification-cost claim at 15, and why? Record any correspondence or fact you cannot yet establish.
Choose an available edition containing SYSE.13:4.4, Use a record for one configuration-dependent claim, including its uncertain-time explanation, and keep that copy available for the exercise. Read that bounded fragment with your attempted answer in view. Return here with the supported installed state, the quotation’s subject and conditions, and the period needed by the decision. The rest of SYSE.13 is needed only if another configuration question requires it.
Compare your reasoning. Q2 supports the specified cost claim at 15: it covers the actual V2 modification, the needed scope and the applicable commercial period. Q1 remains a quotation for V1 despite its later issue date. Q2’s issue before installation does not prevent it from describing the later installed configuration. If your actual records leave V2 or interface coverage unsettled, ask the supplier that specific question or retain a conditional cost. A quotation alone does not establish future service performance; independently applicable water-demand information remains usable.
Revise your answer where its grounds differ from this account. Then try the following changes before reading their discussions.
Changed time. The decision is now required at 21. Configuration and work scope are unchanged, and no renewed Q2 terms have been supplied. What remains supported?
Discussion. Q2 no longer supplies a valid price for the required time. Obtain applicable terms or leave the cost conditional. The installed-state account and independently usable demand information remain valid.
Uncertain installation time. For this separate variation, return to the decision at 15. Replace both the original installation-time premise and the confirmation of V2 at 15 with evidence of exactly one transition from V1 to V2 at a time τ in [14,16]. No independent evidence establishes the configuration at 15. Q2 covers only V2 and remains valid until 20. Can it now supply an unconditional cost?
Discussion. Its commercial period fits, but V2 at 15 is not established. Keep Q2’s cost conditional until evidence establishes the relevant state or another applicable cost result covers the remaining possibilities. Q1’s existence alone does not supply such a result. Where a requested conclusion is supported for every admissible state, retain that conclusion with its information limit; these inputs do not establish that condition for the Q2 price.
Use the same reasoning on one of your own records, stating what the available source supports and what would reopen the match. Comparing an answer with this discussion can guide correction; it does not establish independent ability on new material. If the remaining distinction is unclear, obtain competent feedback on that step before relying on an unsupported match.
EAM.3:5 - Archetypal Grounding
In a constructed C modification case, the station register names C, the installation record identifies serial unit C-07 with drive configuration V2, and a vendor estimate prices modification of V1. The estimate cannot yet supply C-07’s modification cost or feasibility.
The practitioner asks the supplier whether the proposed modification and price cover C-07/V2, giving the installed configuration and required service. A returned applicable estimate closes that gap; a statement that V2 needs another interface changes the option’s cost or timing. The water-demand account can remain usable throughout this repair.
If the discrepancy concerns only an old descriptive label and the source records establish that both labels denote the same installed state, record that correspondence and reuse the estimate. No new asset or design variant is created by the label difference.
EAM.3:6 - Bias-Annotation
Well-maintained records tend to make their assets easier to compare, which can disadvantage poorly documented sites. Treat missing evidence as an information limit rather than automatically poor condition. A vendor or asset owner may also describe scope in the way most favorable to its proposal.
EAM.3:7 - Conformance Checklist
Can each material observation, price and intervention be matched to the right asset, configuration and use? Are actual and proposed states distinct? Does every unresolved match have a stated consequence for the receiving decision?
EAM.3:8 - Common Anti-Patterns and How to Avoid Them
Using the latest record without checking its subject can replace applicable evidence with an unrelated revision. Match identity and effectivity first.
Completing every register field before giving advice burdens a decision that may need only one configuration fact. Select information by its use.
EAM.3:9 - Consequences
The practitioner can combine records without silently changing their subjects. Some options remain conditional while others can be compared. Keeping the basis current costs work, so its detail and refresh conditions follow the decisions that depend on it.
EAM.3:10 - Architectural Rationale
The information basis is organized around one decision rather than a universal asset schema. It relies on configuration guidance already available in Systems Engineering and supplies the asset-specific joins needed for condition, cost and intervention comparison.
EAM.3:11 - SoTA-Echoing
For deciding whether a condition observation and intervention estimate apply to the same installed asset, adopt SYSE.13’s decision-specific configuration basis: identify the unit, distinguish it from its descriptions, and establish their applicability under the relevant conditions. Adapt that result in the Solution by joining condition, proposal and cost only where the asset choice needs the correspondence. In the C-07/V2 case, asking whether the V1 estimate covers the actual configuration can resolve or expose the consequential mismatch without recollecting the usable demand information.
The serious broader alternative is a maintained configuration baseline within an integrated asset-information arrangement. GFMAM’s Asset Management Landscape, third edition, June 2024, sections 5.4–5.5 (pp. 66–69), supplies that organization-wide information/configuration comparator. Reuse such an arrangement when it already supports the needed match. Establishing or repairing the whole arrangement first can be worthwhile for repeated decisions, but its existence or a current-status label cannot settle this particular unit/estimate correspondence. The selected local reconciliation puts effort into the answer-changing gap and preserves its evidence for reuse; it accepts less coverage of unrelated assets. It does not relax applicable configuration-control requirements. SYSE.13 supplies the identity and effectivity distinctions, while the professional source describes the wider maintained capability; neither establishes C-07’s installed state. Reopen the comparison if an installation or source revision invalidates a match, an unresolved difference can change the option, or repeated reconciliation costs make a shared information repair the better answer under EAM.14.
EAM.3:12 - Relations
EAM.1 selects the concern. EAM.5 uses matched observations; EAM.7 and EAM.8 use applicable proposals; EAM.12 checks the results before decision. SYSE.13 governs the needed configuration basis, and MNT.4 supplies condition content with its measurement and duty conditions.