Part C - Alternatives, Conflicts, Combinations, and Timing

EAM.7 - Generate Ways to Supply an Asset-Dependent Service

Type: Method Status: Stable

EAM.7:1 - Problem frame

Use this pattern when a needed service contribution has become a proposal to acquire or modify an asset. A team has a preferred machine, supplier or design, but materially different ways of obtaining the contribution could change cost, risk or feasibility.

Begin by separating the required contribution from the first bearer assumption. Return a small, technically meaningful alternative set, including the realization conditions the next comparison needs.

EAM.7:2 - Problem

Searching only within the familiar equipment category can exclude sharing, leasing, reconfiguration or demand change. The opposite mistake lists attractive concepts without showing how their contributions could be realized. A vendor’s availability claim then substitutes for an applicable engineering answer.

EAM.7:3 - Forces

Ownership can provide control while creating continuing support and exit burdens. Shared or leased service can reduce initial capital while adding dependency and recurring cost. A technically novel arrangement can improve value but require evidence and integration work that the decision window cannot support.

EAM.7:4 - Solution

Recover the required outside contribution, recipients, conditions and horizon from EAM.1 and EAM.2. Identify which feature of the incumbent arrangement is an assumption rather than a requirement.

Form materially different ways to supply the contribution. Depending on the problem, these can include changing an existing asset, acquiring a new one, redistributing capability, sharing a provider, leasing a service or changing demand. A renamed supplier offering with the same relevant behavior is not a distinct architectural alternative.

Describe how each option could work. Identify the asset or provider, integration with the present arrangement, interfaces, access, support and changes to operation. Use an applicable SYSE.5 result when functional organization and bearer allocation determine the option. Obtain subject-specific engineering where physics or other specialist constraints decide feasibility.

State the realization conditions and consequences at the same service basis. Include procurement and integration time, interruption, continuing cost, dependency, reversal and exit. Preserve what remains unknown; a proposed interface is not demonstrated compatibility.

Compare the set with the incumbent or a no-build response. Explain why withdrawal, demand change or another contribution is included or excluded in this case. If an option requires amending a service commitment, identify that separate decision rather than assuming the amendment.

Return enough alternatives for EAM.9 to make a genuine comparison. Stop adding options when further generation is unlikely to improve the requested answer at a worthwhile burden. Keep the precise unsupported dependency that prevents a promising option from being used.

EAM.7:5 - Archetypal Grounding

CityWater’s wet-season North requirement exceeds the present 1,000 m³/h capability by 100. The shortlisted C modification and leased service each add a qualified 200. The modification requires €3 million initial capital and €0.20 million annually; the leased service requires no initial capital and €1.20 million annually, under the supplied five-year terms.

The alternatives differ in funding, continuing cost, realization time and dependence on the service provider. Their common quantity contribution does not make them interchangeable. The lease can free capital for D replacement, while its recurring cost changes the whole portfolio comparison.

If the proposed leased service has no applicable evidence for the required connection and delivery conditions, it remains conditional. A quotation and a nominal pump rating do not establish that service. The practitioner asks for the needed engineering result rather than silently treating the option as available.

EAM.7:6 - Bias-Annotation

A procurement channel can narrow the set before the asset question is answered. Supplier information can favor purchase or service contracts according to commercial interest. Preserve the costs and dependencies borne by the utility and service users.

EAM.7:7 - Conformance Checklist

Are the alternatives materially different ways to provide the same needed contribution? Are their realization conditions and continuing consequences visible? Can the recipient distinguish a supported candidate from a concept awaiting a decisive result?

EAM.7:8 - Common Anti-Patterns and How to Avoid Them

Three bids for effectively the same arrangement can conceal a missing service alternative. Challenge the bearer assumption before counting options.

Treating a service contract as removal of engineering dependence hides the provider and interface conditions. State the actual contribution and evidence required.

EAM.7:9 - Consequences

The comparison can reveal a lower-capital, more reversible or otherwise valuable alternative. Some concepts remain conditional, and more engineering may be required for a consequential choice. Generating a set does not choose or realize an option.

EAM.7:10 - Architectural Rationale

The pattern separates desired contribution from physical or contractual form. That preserves meaningful alternatives while allowing the engineering and financial consequences to be reconciled later. It complements EAM.8’s policies for existing assets instead of making acquisition the default beginning.

EAM.7:11 - SoTA-Echoing

For finding materially different ways to obtain an asset’s required contribution, adopt SYSE.5:4.1’s joint development of functional organization, bearers, interfaces and realization conditions. Adapt it to the receiving asset comparison by retaining the few alternatives whose capital, continuing burden, service or dependency differences can change the choice. In CityWater, modification and qualified leased service provide the same additional flow but compete differently for capital and continuing expenditure. The Solution therefore establishes the contribution before fixing ownership or a particular construction.

A serious alternative is specification-led acquisition: hold an already justified asset arrangement fixed and compare designs or suppliers able to realize it. GFMAM’s Asset Management Landscape, third edition, June 2024, section 6.2 (pp. 72–73), provides the acquisition and integration comparator; its section 3.4 also keeps new, existing and non-asset responses available at planning scope. Retain specification-led comparison when the bearer decision is already supported. Where ownership is only an initial assumption, selecting it first could exclude C’s service option before its funding consequence is examined. The broader contribution comparison costs some additional provider/interface analysis, accepted because it can change the feasible asset programme; it stops short of detailed engineering for every conceivable option. These sources supply operations and professional scope, not the lease’s actual availability or compatibility. Reopen the choice when a required interface cannot be realized, a provider qualification changes, an incumbent assumption becomes an actual requirement, or a newly supported arrangement could improve the decision enough to justify examining it.

EAM.7:12 - Relations

EAM.2 and EAM.4 supply the need; EAM.3 and EAM.6 supply configuration and capability conditions. SYSE.5 supports bearer and interface alternatives. EAM.8 supplies existing-asset policies, EAM.9 compares value and EAM.11 tests realization timing.

EAM.7:End

EAM.8 - Generate Maintenance, Renewal, and Retirement Alternatives

Type: Method Status: Stable

EAM.8:1 - Problem frame

Use this pattern when an engineered asset’s future use is in question: retain it with maintenance, renew it, replace it, repurpose it or withdraw it. A feasible repair has been proposed, but the decision maker needs comparable asset policies over the relevant service horizon.

Return a small set of supported or explicitly conditional alternatives, with the consequences needed for value comparison. An adequate existing set can be reused. If the only question is which intervention maintains the already chosen function, the maintenance recommendation may answer it directly.

EAM.8:2 - Problem

A repair estimate describes one intervention. It can omit years of energy, inspection, support and further work. A replacement estimate can omit commissioning, service interruption, exit cost or remaining value. Comparing those estimates as if they described the same service policy produces a misleading choice.

Continued use can also become a fictitious zero-cost alternative when its required maintenance and fallback are omitted. Ending a spreadsheet after two years does not establish that the asset stops working then or that its remaining contribution is worthless.

EAM.8:3 - Forces

Early replacement can reduce continuing burden but discard useful service life. Renewal can preserve infrastructure while retaining a limiting design. Withdrawal can avoid future cost while removing a needed contribution. Long-horizon comparisons need enough detail to expose those consequences without pretending that future duty or condition is certain.

EAM.8:4 - Solution

EAM.8:4.1 - Establish the service that each policy must support

Recover the required service, asset configuration and horizon. Use the relevant condition and diagnostic account to establish which maintained-use responses are supported. MNT.4 supplies condition interpretation; MNT.6 supplies the diagnosis and intervention recommendation. Their result must apply to this asset and proposed duty.

Form policies rather than isolated job labels. A continued-use policy includes its initial intervention, recurring maintenance, permitted duty, contingency and exit conditions. A renewal policy states what capability or useful life it changes. Replacement includes the new asset’s integration and the old asset’s disposition. Repurposing names the different receiving use; withdrawal names how a still-required service will be supplied or the decision that ends that requirement.

Lay out the period covered by each technical qualification. An initial repair supported for three years cannot by itself supply a four-year policy. Obtain the further intervention, replacement or service alternative that closes the remaining interval. Where condition determines the next work, state the observation and threshold that trigger it, the time needed to respond and how service remains supported while responding. A conditional forecast retains its duty and mechanism assumptions.

Keep technical eligibility separate from preference. Label an option conditional when a decisive engineering, support or permission result is missing. A proposal can be worth discussing while that result is sought, but it cannot be treated as a feasible immediate act.

EAM.8:4.2 - Construct the dated consequence account

For each policy, follow the work and use through time: initial preparation and integration, recurring operation and support, subsequent interventions, interruptions and temporary provision, and the intended ending. Attach each consequence to its cause and date. Include the whole intervention and return to service supplied by MNT.7; the time spent physically repairing equipment alone can understate the interruption. Carry the resulting work and service conditions into EAM.11.

Then obtain the economic consequences of that same policy. FIN.6 develops a dated incremental cash account: compare the proposed policy with its actual alternative, include changed operating and investment cash, and distinguish historical expenditure from future avoidable consequences. Identify the asset and configuration, receiving service, comparison perspective and date, price and discount-rate basis, relevant tax and financing treatment, and ending premise. Ask the finance supplier to return the amounts and dates, significant assumptions and unresolved limits. Its corporate-finance assumptions apply only where appropriate to the receiving case.

A recurring service price may already include maintenance, response or replacement. Check those inclusions before adding separate allowances. Conversely, a required future overhaul is still a consequence when it falls outside the current capital request. Preserve unpriced service loss, safety, environmental or other material consequences for EAM.9 instead of silently treating them as zero. A finance result values the stated policy; it does not establish that the policy can supply the service.

EAM.8:4.3 - Reconcile horizon and ending

Place the alternatives on a common service and analysis horizon. If their technical lives differ, describe the further work needed to cover that horizon or obtain an applicable value of remaining service. A repeating replacement chain needs supported availability, duty and cost assumptions; extending an annuity factor cannot supply them.

Distinguish the end of the study from the end of use. If the asset continues beyond the explicit account, obtain a remaining-value estimate consistent with that continuation and its further support needs. FIN.7 develops valuation under a stated continued-use or disposal premise. If the asset will actually be withdrawn, use realizable proceeds and the dated cost of disconnection, disposal, closure or replacement service as applicable. Book value alone supplies neither answer. Do not add liquidation proceeds for resources whose continuing use is already included in the terminal value.

When only the explicit table endpoint moves, reconcile the value at the new endpoint with the same later payments and ending premise. The whole policy’s present cost remains the same. If a supplied valuation disagrees, use FIN.7 to identify the changed cash, dates, rights or assumptions before relying on it.

Use constant prices with a real discount rate, or a consistent current-price basis with its corresponding rate. Changing the required service horizon calls for reconsidering which interventions occur, which support still applies and what ending is being valued. If the service itself ends, reconsider withdrawal and other alternatives.

EAM.8:4.4 - Return comparable choices and their conditions

Compare eligible policies using the applicable criterion in EAM.9. Return their service and configuration, dated work and consequences, ending premise, technical support and material conditions. EAM.10 can then combine them without losing a later funding need or counting shared work twice.

Retain the smallest alternative set that includes materially different feasible ways to meet the need. Obtain more diagnosis or costing only when an attainable answer could change eligibility, preference or the requested claim enough to justify its full burden. If EAM.13 reports a changed duty, price or support result, revise the affected policy and its recipients; an unrelated qualified policy need not be reconstructed.

EAM.8:5 - Archetypal Grounding

EAM.8:5.1 - Constructing a four-year policy

Consider a separate constructed asset E supplying the same required service under two technically qualified policies. All amounts are constant-price €million; the comparison uses a 3% real rate, year-end cash and sufficient resources for either policy. Tax and financing differences are held equal. These assumptions do not supply rates or technical support for a real asset.

Policy X retains E: initial work costs 0.40 and supports its duty through year three; a 0.90 overhaul at the end of year three supplies the further support needed for year four. Policy Y replaces E initially for 1.50 and has qualified support throughout the four years. The following account includes recurring operation and routine maintenance separately from the overhaul.

The teaching qualifications include permitted eight-hour work windows and temporary service sufficient to preserve the requirement during initial work and X’s later overhaul. The corresponding costs are included in the initial and overhaul amounts. That makes the policies service-comparable; omitting the later window or temporary provision would leave X conditional. No other material consequence distinguishes the eligible policies in this example.

At 3%, the four-year annuity factor is 3.717098, the year-three discount factor 0.915142 and the year-four factor 0.888487. X’s present cost is 0.40 + 0.30 × 3.717098 + 0.90 × 0.915142 − 0.20 × 0.888487 = 2.161060. Y’s is 1.50 + 0.15 × 3.717098 − 0.50 × 0.888487 = 1.613321. Replacement has the lower comparable cost. Omitting the overhaul would report X as 1.337432 and reverse the recommendation while removing the work needed to support year four.

Now move the end of the explicit cash table to year two, keeping both complete policies, the required service, the rate and all later amounts unchanged. Express the remaining year-three and year-four cash, including the stated year-four continuing value, as an equivalent net value at year two:

• X: V_X(2) = −(0.30 + 0.90)/1.03 + (0.20 − 0.30)/1.03² ≈ −1.259308.
• Y: V_Y(2) = −0.15/1.03 + (0.50 − 0.15)/1.03² ≈ 0.184278.

These values represent the same remaining account on the cost-comparison basis. X’s negative value means its later support payments exceed its discounted year-four continuing value. The common required service remains the same and its equal benefits are outside both cost accounts. The calculation does not estimate a sale price.

Let a₂ = 1/1.03 + 1/1.03² and d₂ = 1/1.03². Using unrounded values, the shortened explicit accounts give X: 0.40 + 0.30 × a₂ − V_X(2) × d₂ = 2.161060; Y: 1.50 + 0.15 × a₂ − V_Y(2) × d₂ = 1.613321. Replacement remains cheaper. Moving the table boundary has moved later consequences into the ending value; it has removed neither their cost nor their service obligations. A different supplied appraisal needs reconciliation of its changed assumptions before it can support a different recommendation.

Actual withdrawal at year two is another case. If the authority ends the service and X incurs a net exit cost of 0.10 while Y yields net sale proceeds of 0.60, replace the continuing values with those consequences. Present costs are then 1.068300 and 1.221463. X is cheaper in this different case because the service requirement and exit consequences have changed. There is no year-three service obligation in this case. If the service remains required, withdrawal alone is incomplete: a qualified replacement service and its consequences must join the policy.

EAM.8:5.2 - Comparing the complete supplied policies for D

For the constructed D case, both policies supply the same required service for five years under their stated engineering qualifications. Continued use needs €0.50 million initially as operating expenditure and €1.00 million at each year end, with zero terminal value. Replacement needs €3.00 million capital, €0.35 million each year and has €1.20 million terminal value. These are teaching inputs, not estimates for a real pump.

At a 3% real rate, the five-year annuity factor is 4.579707 and the terminal factor is 0.862609. The comparable present costs are 0.50 + 1.00 × 4.579707 = 5.079707 and 3.00 + 0.35 × 4.579707 − 1.20 × 0.862609 = 3.567767 million. The comparison therefore favors replacement when both options are eligible and resources are available.

The continued-use policy is supported for the stated horizon; a one-year forecast alone would not justify five-year use. If a new finding invalidates that support, the practitioner marks the policy ineligible before comparing cost. If instead the service is no longer required, withdrawal becomes a new alternative with its own exit consequences. EAM.10 examines D’s choice together with competing assets.

EAM.8:6 - Bias-Annotation

Retaining an asset can be favored because its purchase cost is remembered; replacing it can be favored because a supplier reports only purchase savings. Use the same receiving service and future-cost boundary, and disclose where data come from interested parties.

EAM.8:7 - Conformance Checklist

Can the practitioner trace each policy from required service through supported intervals, later work and ending? Are its cash dates, unpriced consequences, horizon and valuation premise compatible? Can the recipient distinguish a supported option from a conditional proposal and identify what would change that distinction?

EAM.8:8 - Common Anti-Patterns and How to Avoid Them

Treating “do nothing” as free hides maintenance and service consequences. Write the actual continued-use policy.

Treating a maintenance recommendation as the asset decision loses alternative service and lifetime-value questions. Preserve the recommendation and compare its policy with the other relevant options.

Using a valuation for a different date or continuation can create a false change in preference. Reconcile the remaining cash and ending premise before comparing.

EAM.8:9 - Consequences

Decision makers obtain alternatives whose differences can be explained and recalculated. Some options are excluded, some remain conditional and some investigations stop. The result supports asset choice. The maintenance team carries out the intervention and returns the equipment to service under the applicable maintenance and operating decisions.

EAM.8:10 - Architectural Rationale

This pattern joins maintained-functioning results to the asset-value question without merging them. A policy description exposes continuing consequences that a list of interventions hides. Keeping repurposing and withdrawal available prevents replacement from becoming the assumed end of a universal lifecycle.

EAM.8:11 - SoTA-Echoing

NIST HB135e2025, chapter 4, develops the timing of initial, recurring, replacement and residual consequences on a common study period. That discipline supports the dated account here; its federal rates and programme rules are not adopted. A payback-only screen loses later support and the ending premise.

FIN.6 supplies the incremental financial construction, and FIN.7 supplies a valuation consistent with continued use or actual disposal. Use their developed treatment when financial construction or appraisal is needed; retain a sufficient qualified local answer when it already supplies the result. EAM connects those returns to the technically supported asset policy. The numerical cases demonstrate this conditional connection and do not estimate financial or engineering performance in practice.

EAM.8:12 - Relations

EAM.3 and EAM.5 supply applicable asset and condition information. MNT.6 supplies the maintenance recommendation and MNT.7 the whole intervention and return. EAM.7 supplies alternative ways of obtaining a changed service contribution. FIN.6 and FIN.7 supply the dated financial account and qualified ending value; their perspective and conditions must match the asset policy. EAM.9 compares the policies, EAM.10 tests combinations and EAM.11 tests timing. EAM.13 returns changed premises. FPF C.11.DUA governs the worth of further inquiry.

EAM.8:End

EAM.9 - Compare Asset Alternatives and Reconcile Decisions When They Conflict

Type: Method Status: Stable

EAM.9:1 - Problem frame

Use this pattern when a proposed asset choice must satisfy different technical, service, financial or operating conditions, or when individually reasonable decisions cannot hold together. It also provides the comparison for one asset whose feasible alternatives have different lifetime consequences.

Begin with the conflict or difference that can change the choice. Return a reconciled comparison, a supported recommendation or the precise unresolved conflict. A transparent cost comparison can be sufficient when service and other eligibility conditions are equal.

EAM.9:2 - Problem

A local saving can move downtime, cost or risk to another participant. A favorable financial score can conceal an unavailable service or unsupported asset policy. Conversely, building a universal weighted score can add assumptions that nobody is authorized or able to justify.

EAM.9:3 - Forces

Different interests and quantities need a usable decision without pretending that they share one scale. Binding conditions restrict the feasible set, while preferences compare its members. More evidence or negotiation can resolve a conflict, but it must be attainable and worth its full burden.

EAM.9:4 - Solution

Name the alternatives, receiving service and horizon. Recover the conditions that determine eligibility and their sources. A funding allocation sets a spending limit; a service mandate sets required delivery; engineering evidence supports the proposed functioning. State their different consequences for the choice.

Identify the actual couplings behind a conflict. The same assets can participate in an operating network, a crew schedule, a maintenance programme and a funding decision. Relate their common subjects and dependencies without treating those structures as identical. Use OPS.11, MNT.15 or FPF C.32.MWA when their specific coordination question is needed.

Exclude unsupported alternatives from the eligible comparison or retain them explicitly as conditional proposals. An invalid qualification for D continuation cannot be offset by a low cost. If no option remains, report the unmet service or resource condition and the decision or specialist result that could change it.

Compare eligible alternatives on compatible consequences. For equal required service and admitted nonfinancial conditions, present cost can be a useful criterion. With initial capital K, initial operating cash O, annual costs Ct, terminal value S, rate r and horizon n, use K + O + Σ Ct/(1+r)^t − S/(1+r)^n. Use a consistent price/rate basis and account for costs and residual value once.

When important consequences differ, preserve those differences. An alternative is dominated only when another is at least as good on every relevant criterion and better on at least one under the same conditions. Retain a non-dominated set when no justified priority resolves the trade-off; identify who can make that choice. Do not invent weights to force a ranking.

Test assumptions that can reverse eligibility or preference. A range, scenario or break-even can be enough. Select additional inquiry by the answer it could change and the work, delay and disruption it requires.

Return the recommendation with its reasons, conditions and remaining conflict. Use EAM.10 for a genuine combination decision and EAM.12 for the requested asset decision or authorization. Stop when sufficient advice has been delivered.

EAM.9:5 - Archetypal Grounding

For D alone, the constructed five-year present costs are €5.079707 million for the supported continued-use policy and €3.567767 million for replacement. With equal required service, applicable technical support and resources for either, the practitioner recommends replacement on cost: the difference is €1.511940 million.

Keeping replacement inputs fixed, continued use becomes equally costly at about €0.669861 million annual cost. A justified range of 0.95–1.05 does not reverse the answer; a credible 0.60 estimate would. The calculation identifies a potentially useful inquiry boundary without giving that lower estimate a probability or treating it as fact.

At the portfolio scope, the same D replacement needs capital that C modification and other work also need. EAM.10 compares the whole combinations. The independent D comparison is not wrong; its resource assumption differs from the shared decision.

In a separate constructed choice, three policies are technically supported and affordable. The service mandate permits up to six hours of planned interruption for the same users in the same work window. All three meet that condition; their only material preference differences on the supplied five-year basis are:

R is dominated: P costs less and interrupts service for less time, and Q also improves both consequences. P and Q remain: P is cheaper, while Q avoids three more hours of interruption for an additional €0.4 million in present cost. The infrastructure committee is authorized to choose within the mandate, but no priority between these two consequences has been supplied. The practitioner returns P and Q with that specific trade-off for the committee’s decision. Inventing monetary weights for the interruption would conceal the unresolved preference. If a changed mandate permits only two hours, P becomes ineligible and Q is the sole eligible policy on these premises.

EAM.9:6 - Bias-Annotation

A single monetary criterion can hide losses to groups outside the accounting perspective. Preserve nonfinancial requirements and material unpriced consequences. A familiar model can also hide false precision about future costs or terminal values.

EAM.9:7 - Conformance Checklist

Are eligibility conditions separated from preferences? Do the quantities share a justified comparison basis? Are transferred burdens and real conflicts visible? Does the recommendation state the assumptions that can reverse it and the recipient’s remaining decision?

EAM.9:8 - Common Anti-Patterns and How to Avoid Them

A weighted score that compensates for failed required service admits an ineligible option. Apply the service condition before comparing preferences.

Treating different views as one aligned hierarchy hides shared dependencies. Recover the actual assets, work, resources and decisions that connect them.

EAM.9:9 - Consequences

The decision maker receives an explainable preference or a bounded unresolved trade-off. Some options are excluded and some inquiries stop. The comparison can remain conditional without pretending that a budget or service amendment establishes technical feasibility.

EAM.9:10 - Architectural Rationale

Eligibility, preference and actual authority answer different questions. Keeping them separate permits simple economic comparison where justified and richer multi-criterion judgement where needed. The asset-specific consequence account is what connects general comparison guidance to this domain.

EAM.9:11 - SoTA-Echoing

The common NIST source supports compatible lifecycle-cost comparisons, while the professional landscape recognizes wider value and risk. This pattern uses minimum present cost only under its stated equality and eligibility conditions. Payback, condition rank or an unexplained weighted sum cannot replace that decision basis.

EAM.9:12 - Relations

EAM.5–EAM.8 supply assessments and alternatives. EAM.10 compares combinations, EAM.11 timing and EAM.12 the decision. OPS.11 and MNT.15 supply their bounded coordination results; FPF C.11, FPF C.11.DUA and FPF C.32.MWA support comparison, useful inquiry and synthesis across relevant structures.

EAM.9:End

EAM.10 - Compare Engineered-Asset Portfolio Combinations

Type: Method Status: Stable

EAM.10:1 - Problem frame

Use this pattern when asset choices compete for shared funding, service, people, outages or other resources. Several individually attractive projects cannot all be performed, choosing one changes the feasible alternatives for another, or performing them together changes their consequences.

Begin with the actual combination question and its constraints. Return the preferred feasible combination, a justified non-dominated set or the precise condition that prevents one. An isolated single-asset comparison can remain in EAM.9.

EAM.10:2 - Problem

Ranking assets by condition or ranking projects by a benefit ratio can miss a better feasible combination. Options can be indivisible, mutually exclusive or dependent. A low-capital alternative at one station can release funding for a valuable option elsewhere, while separate project approval hides that interaction.

Adding standalone costs can also count shared preparation twice or omit a cost caused by the combination. Calling the difference a portfolio saving without identifying its cause leaves the decision dependent on an unsupported discount.

EAM.10:3 - Forces

Shared allocation must preserve required service and actual technical eligibility while comparing value. A more complete model can reveal a better combination but costs effort and relies on input quality. Deferral can preserve flexibility or create unacceptable risk, depending on its supported policy.

EAM.10:4 - Solution

EAM.10:4.1 - Define complete choices and different kinds of coupling

State the portfolio scope, requested result and horizon. Recover the alternatives and their eligibility from EAM.7–EAM.9. Identify which choices are mutually exclusive, mandatory, optional or dependent, and why. Include continued use or no new work when it is a qualified alternative. An omitted asset can still matter through a shared service or resource.

Distinguish three questions about a proposed combination. A prerequisite or exclusion determines which selections can coexist: a new unit may need an enabling connection, while two replacements for the same role may be mutually exclusive. A shared resource limit constrains the work or use at a particular time: two eligible jobs may need the same crew or exceed an outage allowance. A joint consequence changes what happens when the choices are taken together: common mobilization may reduce cost, while simultaneous demand can require additional provision. One arrangement can create all three, but each needs its own evidence.

For each material relation, identify the affected alternatives, its operating or engineering cause, the time and conditions under which it holds, and the resulting constraint or consequence. EAM.6 supplies service and dependency conditions. A promised saving cannot make a combination technically eligible.

EAM.10:4.2 - Construct the whole consequence account

Start from compatible policies on the same service boundary, perspective and horizon. If a policy omits later support or its ending, return to EAM.8. Then describe what work and service the combination actually entails. Identify shared preparation, enabling work, recurring operation, temporary service and ending consequences. Obtain amounts and dates for those actual operations.

Reconcile this whole account with the separate accounts. For costs on the same basis, joint adjustment = whole-combination cost − sum of standalone costs. A negative amount is a saving; a positive amount is an additional cost. Explain what causes it and when it occurs. Where effects differ by date, construct the dated differences first and obtain their financial value through FIN.9 on the applicable basis. FIN.9 develops this interaction comparison and dated funding constraints; its return must identify the combination, common baseline, perspective, amounts, dates and significant assumptions.

Count each shared consequence once. If two estimates each contain the same mobilization, the combination that uses one mobilization retains one payment. If three jobs share it, reconstruct their common account; summing all three pairwise discounts could remove more mobilizations than were included. If sharing requires extra supervision or temporary service, include that cost too. An allocation of common cost among departments does not by itself create a saving in the whole payment.

Keep unpriced consequences visible. Shared disruption can change a service or environmental result even when the expenditure sum is unchanged. Use EAM.9’s actual criteria to compare those consequences; a cash adjustment cannot silently settle them. When the combination changes a demand or recovery premise, return that premise to EAM.4 or EAM.6 before relying on its qualification.

EAM.10:4.3 - Test constraints and compare the feasible combinations

Write the constraints at the whole-combination scope. Separate initial capital, initial operating expenditure and recurring operating envelopes where they are different decisions. Include later commitments when they bind: the year-three overhaul in an EAM.8 policy needs its funding, crew and service window at that time. A low initial outlay does not establish that later provision. Do not count a resource twice or assume unused funding must be spent.

Enumerate a small finite set of indivisible choices. For the CityWater shortlist, choose exactly one of two options for each of four stations and compare all sixteen. For a different question, the feasible no-work, single and combined choices depend on what service is mandatory. Remove combinations excluded by a supported prerequisite, technical condition or resource limit, retaining the reason. Obtain a feasible service-preserving calendar through EAM.11 where timing can defeat an otherwise eligible selection.

For a larger problem, select an optimization or scenario method whose objective, choices, constraints and interactions represent the actual question. Specify what is selectable, which selections imply or exclude others, dated resource use and the joint effects. Model contingent actions with the information available when each action is chosen; the combination cannot assume different early choices for future outcomes that are not yet known. A mathematical optimum applies to the represented set and basis.

Compare eligible combinations using the actual value criteria. When required service and other material consequences are equal, minimize total present cost. Otherwise preserve justified trade-offs or a non-dominated set. A cheaper programme that requires more scarce resources does not automatically dominate a dearer one.

EAM.10:4.4 - Explain the choice and the condition that could change it

Show the preferred combination and the consequential alternatives it displaces. Test a changed funding limit, engineering qualification, demand driver, shared-work condition or resource date when it could alter the answer. Use coherent conditions across the combination; a common disruption cannot be favorable for one component and absent for another without grounds.

Return the recommendation, the whole consequence account, feasibility conditions and the decision-changing uncertainty to EAM.11 and EAM.12. EAM.13 later returns observations to the premise they affect. If a missing shared-work fact can change the choice, obtain it only when its attainable answer warrants the inquiry’s full burden. A project that remains locally useful can be deferred for a qualified portfolio reason without being relabelled technically poor.

EAM.10:5 - Archetypal Grounding

EAM.10:5.1 - A shared operation changes the comparison

Consider a separate constructed service requirement. Two interventions P and Q together and a different complete solution Z are both qualified to supply it over the same horizon. P or Q alone is insufficient. Their subsequent operating, ending and other material consequences are equal; all different costs are payable now in €million, and funding is sufficient for either whole solution. Thus their initial cost difference decides this bounded comparison.

P costs 2.0, including 0.2 mobilization, and Q also costs 2.0 including 0.2. Z costs 3.9. The operating practitioner establishes that P and Q can be performed sequentially during one qualified visit, using one 0.2 mobilization. Required service remains supported during the work; the shared visit incurs no additional consequence outside the supplied account.

The whole P+Q account is 1.8 + 1.8 + 0.2 = 3.8. Adding the separate estimates would prefer Z at 3.9; the supported joint account prefers P+Q by 0.1. That result concerns one actual payment saved through a feasible work arrangement.

Suppose incompatible access windows require two visits and two mobilizations. P+Q returns to 4.0 and Z becomes cheaper at 3.9. If instead the proposed shared visit fails the service condition, remove that arrangement as ineligible and compare any qualified two-visit arrangement with Z. Reducing its price cannot repair the lost service. EAM.11 establishes which visit arrangement is feasible; EAM.10 uses its consequences.

The example does not infer a common saving for CityWater’s separate station jobs. A proposed CityWater sharing arrangement would need its own work, service and financial account before altering the following result.

EAM.10:5.2 - The sixteen supplied CityWater combinations

The common CityWater application supplies four two-option choices. Initial capital must not exceed €8 million, initial operating expenditure €0.60 million, annual operation €3 million and the available team/outage time twelve days. All amounts and eligibility results are constructed.

FFMK—refurbish A and B, modify C, continue D—uses €7 million capital, €0.50 million initially for operation, €1.85 million annually and eight days. Its present cost is €14.592284 million, the lowest among the declared eligible combinations. The common application provides all sixteen rows, so this conclusion is reproducible.

Adding D replacement while retaining the other choices gives FFMR: €10 million capital and lower present cost of €13.080344 million. It is infeasible at the €8 million allocation. Switching C to leased service permits D replacement within capital, but FFLR costs €15.350138 million overall.

If the funding board raises capital to €10 million, FFMR becomes preferred. If D continuation instead loses its engineering qualification, FFLR becomes preferred at the original limits. These changed outcomes follow from changed conditions, not from changing the ranking arbitrarily.

EAM.10:6 - Bias-Annotation

A portfolio objective can conceal which users bear losses and which costs are left outside the model. Document material omissions and the authority for trade-offs. Model size and numerical precision do not establish that the options or consequences are complete.

EAM.10:7 - Conformance Checklist

Are all required choices, prerequisites and exclusions represented? Does the selected combination meet the dated whole-set constraints and admit a feasible schedule? Can its joint effects be traced to actual work or use and counted once? Can the recipient reproduce the preference and identify a condition that would reverse it?

EAM.10:8 - Common Anti-Patterns and How to Avoid Them

Funding the highest-ranked items until money runs out can miss a feasible combination of different options. Evaluate the relevant combinations.

Accepting each project separately does not establish the shared condition. Construct the actual whole demands and consequences, then test their dependencies at portfolio scope.

A generic synergy percentage hides which work or cash changes. Reconcile the whole account with the separate accounts and retain the conditions that make the difference possible.

EAM.10:9 - Consequences

The portfolio can deliver more useful service or value within actual constraints. Some individually preferred projects are displaced. The result’s quality still depends on the eligible option set, consequence model and supported feasibility; it does not authorize work.

EAM.10:10 - Architectural Rationale

The combination is the subject because shared constraints and joint consequences can change which option should be selected at each asset. This differs from both single-asset value comparison and maintenance scheduling. Enumeration is selected for small cases because the assumptions and omitted alternatives remain inspectable.

EAM.10:11 - SoTA-Echoing

NIST HB135e2025, chapters 4, 7 and 8, supplies common-period costing, comparison of alternatives and programmes, and sensitivity reasoning. Those operations support the explicit consequence comparison; its federal rates and programme rules are outside this use.

FIN.9 develops whole incremental cash under interactions, dated constraints and service continuations. Its B+C example shows that a negative joint cash effect can reverse the allocation even when the combined initial funding remains feasible. Use that financial construction together with the actual engineering and operating conditions; financial interaction and physical feasibility answer different questions.

Enumeration fits a small indivisible shortlist because every permissible combination and exclusion can be inspected. Independent ranking is defensible only when the relevant choices and consequences are independent and the allocation rule fits the constraints. The value-per-capital ranking in FIN.9 requires divisible, linearly scalable investments and one initial capital limit; indivisibility, minimum scale, interactions or later funding needs can defeat it. These conditions do not hold merely because each asset has a score.

An optimizer can help when enumerating a larger set becomes burdensome, provided the actual selection rules, interactions, dates and criteria can be represented. If a consequential relation remains unqualified, retain that uncertainty or obtain the missing result. Solver precision supplies no missing alternative or engineering support. A tutorial for a particular solver is unnecessary when the finite comparison already answers the asset question.

EAM.10:12 - Relations

EAM.7–EAM.9 supply supported policies and comparison criteria. EAM.4 supplies applicable demand; EAM.6 supplies service and dependency conditions. FIN.9 supplies compatible joint financial consequences and dated funding comparison. EAM.11 establishes timing; EAM.12 receives the recommendation for decision; EAM.13 returns changed premises. FPF C.11 supports multi-criterion comparison, and FPF C.11.DUA supports proportionate additional inquiry.

EAM.10:End

EAM.11 - Time Asset Interventions and Manage Dependencies

Type: Method Status: Stable

EAM.11:1 - Problem frame

Use this pattern when the timing of an asset intervention can change whether the service or portfolio plan is feasible. A job estimate fits the window, but its preparation, shutdown, testing, return or shared resources do not.

Begin with the complete intervention and its service conditions. Return a feasible timing arrangement or the exact unmet condition. A value recommendation can be delivered before a particular work window has been authorized.

EAM.11:2 - Problem

Task hours are often substituted for elapsed outage time. Local plans can share the same crew or remove each other’s fallback. Reordering work can improve feasibility, but cannot reduce the total demand on one exclusive resource below its actual work requirement.

EAM.11:3 - Forces

A larger window and more contingency improve recoverability while consuming service and resources. Combining work can reduce repeated access but increase interference. Deferral can preserve an opportunity only when the continued-use policy remains supported.

EAM.11:4 - Solution

Recover the selected or proposed interventions, the required service and the actual calendars. Use the whole-outage arrangement from MNT.7 where applicable and the operating envelope from OPS.10. Identify the duty, configuration, access and protection assumptions those results need.

Separate preparation possible during operation from work requiring the outage. Include supported shutdown, protected access, intervention, testing and return. Establish whether estimates already include allowance before adding contingency. Distinguish person-hours, exclusive-team occupancy and elapsed service-loss time.

Represent the dependencies that determine timing. Some activities must precede others; some can overlap only with independent providers and compatible service conditions. A shared standby unit, isolation or recovery resource can prevent overlap even when labor is available.

Place the complete demands in actual windows. A necessary resource bound is total exclusive demand no greater than available time. Passing it is not sufficient when release dates, simultaneous resources or service dependencies prevent a schedule. Use a finite schedule for a small known set.

If the arrangement fails, compare a real change: another window, another supported option, a qualified provider, a service-preserving fallback or justified deferral. Include its cost and moved burden. Changing the written estimate does not change the work.

State what happens if an important condition changes during the window. Identify the time, personnel, access or fallback needed to return this asset to a supported operating state, and keep those resources available. Agree with the people controlling maintenance and operation when they must decide on a supported hold or return before that option is lost. Obtain the required allocation or operating decision before relying on reassigned resources, an extended window or changed service.

Return the timing arrangement to the people controlling the work and operation. Stop when the requested planning question is answered. Actual protected work and resumption require their own applicable permissions and evidence.

EAM.11:5 - Archetypal Grounding

For FFMK in CityWater, the supplied whole durations are A two days, B two, C three and D one. One qualified team is available for twelve comparable work days. A on days 1–2, B on 3–4, C on 5–7 and D on 8 uses eight days, and every asset is restored before the next begins.

North’s A and C outages cannot coincide: their combined loss would reduce delivery below the dry-window minimum. East’s B and D outages have the same incompatibility. The serial schedule respects both conditions and the shared team. The four remaining days are uncommitted allowance, not permission to omit a return condition.

If only seven days are available, the eight-day plan fails. The declared options permit FRLK—A refurbishment, B replacement, C leased service and D continuation—in seven days at higher present cost. The practitioner compares that real option or another qualified arrangement; shortening the original estimates would not solve the conflict.

EAM.11:6 - Bias-Annotation

Optimistic duration estimates can favor a preferred option. Treat estimate uncertainty, readiness and actual staffing explicitly. An apparent schedule saving can transfer fatigue, recovery burden or service loss to another participant.

EAM.11:7 - Conformance Checklist

Does the schedule include the complete outage and return? Are exclusive resources and actual dependencies respected? Do service conditions hold in each interval, and is there a supported response if the work exceeds its plan?

EAM.11:8 - Common Anti-Patterns and How to Avoid Them

Summing labor-hours and calling them an outage mixes quantities. Model the actual elapsed dependencies.

Assuming that two individually feasible outages can overlap can remove the fallback supporting each. Check their combined service and resource conditions.

EAM.11:9 - Consequences

The programme can be planned against real windows and revised when a constraint changes. Some apparently cheaper options become infeasible. The schedule remains a prospective arrangement; actual work, functioning and resumed-use authority require their own results.

EAM.11:10 - Architectural Rationale

Timing follows the whole intervention’s participation in service rather than a universal lifecycle. This keeps scheduling, technical support and authority distinct while allowing a small finite plan to settle the current question.

EAM.11:11 - SoTA-Echoing

MNT.7 supplies whole-outage reasoning and OPS.10 qualified service analysis. The common asset-management sources recognize outage and resource planning. This pattern uses those results at the asset programme’s horizon rather than prescribing a particular project-management tool or mandatory scheduling sophistication.

EAM.11:12 - Relations

EAM.6 supplies the service envelope; EAM.8–EAM.10 supply options and combinations. MNT.7 supplies intervention timing and MNT.15 shared-work coordination. EAM.12 receives the feasible arrangement for the asset decision, and EAM.13 revisits its assumptions after relevant observations.

EAM.11:End