Library / Engineering DPF Suite Reference
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:10:20 UTC

Choose how to use and change engineered assets

The Engineering Asset Management DPF helps compare value, service, costs and risks over the lives of engineered assets. The question can concern one pump, an interacting asset system or a portfolio. Its sixteen patterns support the questions below; enter with the result you need and the inputs already available.

Four practical entries show connected use:

  • Compare continued use and change for one asset: use EAM.8 for the alternatives and EAM.1 when the question or boundary needs clarification. A supported recommendation can complete an advice request; EAM.12 supplies the separate asset-decision work.
  • Choose asset work under shared constraints: use EAM.10 with EAM.9 for conflicts and EAM.11 for timing. Obtain a feasible programme recommendation or identify the condition requiring another option or decision.
  • Reconsider a decision after a changed condition: use EAM.13 and return to the affected information, demand, condition or capability assessment. Retain an adequate plan; investigate further when the attainable answer can usefully change it.
  • Improve how asset decisions are made: use EAM.14 for organizational provision, EAM.15 for reusable methods and EAM.16 for the practice people continue or change. Identify which contribution explains the recurring difficulty before selecting a change.

In the CityWater worked case, replacing pump D is preferable in the single-asset comparison, while the programme under a shared capital limit continues D and modifies C. The two recommendations answer different questions with different constraints. For a condition or maintained-functioning result used in such a comparison, return to the maintenance methods.

Your questionOpenWhat you can obtain
Which options should we compare for this asset or portfolio, for what service and period?EAM.1 - Frame the Engineered Assets and Required OutcomesAgree the asset options, required service, comparison period and decision maker.
What required contribution must the assets support?EAM.2 - Relate Assets to Strategy, Services, and Required CapabilityRelate proposed asset work to an actual service outcome and its authority.
Which information applies to this asset and comparison?EAM.3 - Establish the Asset Information and Configuration BasisResolve the answer-changing mismatch with a sufficient information basis.
What service will be needed under the conditions that matter?EAM.4 - Assess Demand and Service Need for Asset DecisionsSeparate demand evidence and forecasts from the mandated service.
What do observed condition and delivered performance support?EAM.5 - Assess Asset Condition and PerformanceReturn a qualified account for the asset decision.
Can the assets support service during normal use and disturbance?EAM.6 - Assess Asset Capacity, Resilience, and InterdependenceCompare required service with qualified available capability and fallback.
Which acquisition or change can provide the needed contribution?EAM.7 - Generate Ways to Supply an Asset-Dependent ServiceGenerate comparable qualified alternatives with their whole burden.
Which continued-use or change option is worth considering?EAM.8 - Generate Maintenance, Renewal, and Retirement AlternativesCompare supported policies at a common service, horizon and cost basis.
Which asset alternative is supported, and what unresolved conflict remains?EAM.9 - Compare Asset Alternatives and Reconcile Decisions When They ConflictCompare eligible asset alternatives and identify any conflicting service, funding or work condition and the decision needed to resolve it.
Which eligible asset combination should receive the allocation?EAM.10 - Compare Engineered-Asset Portfolio CombinationsCompare complete programmes under the actual binding conditions.
Can the selected programme be completed while preserving service?EAM.11 - Time Asset Interventions and Manage DependenciesConstruct a supported calendar or expose the limiting prerequisite.
What supported answer is requested and who makes the asset decision?EAM.12 - Integrate Specialist Results for an Asset Recommendation or DecisionIntegrate applicable results and distinguish advice from actual authorization.
What has actually changed, and should the asset plan be retained or revised?EAM.13 - Track Realized Outcomes and Reconsider Asset PlansCompare obtained outcomes with the decision premises at the same scope.
What in the organization of asset work prevents timely, supported decisions?EAM.14 - Decide Whether and How to Change the Asset-Management SystemCompare feasible changes to responsibilities, information flow or support with keeping the current arrangement.
Should this way of making asset decisions be retained or changed?EAM.15 - Decide Whether and How to Change Engineering Asset-Management MethodsCompare ways of answering the same asset question, including the effort of applying and maintaining them.
Which asset-management practices do people use, and should they continue or change?EAM.16 - Deliberately Continue and Change Engineering Asset-Management CultureEstablish what the evidence supports and compare continuation, change, a qualified branch or stopping.

Use the qualified returns from related practice to connect maintenance condition and intervention results, operating service and capacity, engineering alternatives and configuration, organizational ability, and method or cultural development. Preserve the asset and configuration, receiving use, period, assumptions and limits that make each result applicable. The source table gives the exact supplying and receiving patterns.

The worked cases state their supplied service requirements, engineering possibilities, finance assumptions and decision authority. In an actual project, obtain those inputs from the responsible practice and decision makers. A pattern’s method helps produce or examine a result; the case’s inputs remain assumptions of that case.