EAM.6:4 - Solution
EAM.6:4.1 - Establish the contribution being tested
Recover demand, required service, configuration and horizon. Keep quantities and time units compatible. EAM.4 can supply scenario demand and its place, period and driver conditions; EAM.5 can supply the applicable condition concern. Use OPS.10 or a specialist result to distinguish nominal capability from usable contribution.
State where the service must be delivered and which population or function it protects. An aggregate spare capacity elsewhere is useful only if the arrangement can deliver it where and when needed. Begin with a supply or load bound that the available inputs support.
EAM.6:4.2 - Derive the disturbance from actual dependencies
Identify the asset contributions and the dependencies that can change the answer. Follow shared power, control, providers, access, storage or another asset’s functioning to the service they enable. Explain which contributions cease, degrade or remain usable when a selected dependency is lost. Include a common dependency even when it crosses the portfolio’s ownership boundary.
Test a fallback against that same loss. A second pump on the failed feeder supplies no replacement flow until its needed power is restored. An alternative is independent of that feeder loss only when its power, control, connection and other necessary support remain usable under the stated scenario. This is a dependency claim for the named disturbance; a separate statistical independence claim needs its own evidence.
Choose adverse conditions because their consequences can change the asset decision: a named outage, common-provider loss or credible demand burst. Use an existing qualified scenario where it matches. Preserve simultaneous calls on shared reserve; one standby contribution cannot be allocated twice to incompatible users.
Compare material alternatives on the same disturbance and service criterion. An alternative may change the dependency itself, so recalculate the remaining contributions rather than carrying over the old consequence account.
EAM.6:4.3 - Follow service through recovery
Divide the disturbance into intervals at which demand, usable contribution or restoration changes. Use times to usable service, including the necessary access, work, testing and return conditions. A repair-completion estimate alone may omit the time before the contribution can actually be used.
For each interval, compare required service with supported available contribution. Where an additive bound is applicable, the positive difference is the deficit. Multiply a constant deficit by the interval length to obtain the reserve volume or resource needed during it. Carry the remaining usable reserve forward; test both its deliverable rate and its remaining amount. Account for other users’ simultaneous demands on it.
Credit replenishment only when its route, rate, timing and operating conditions are supported. If flows or demand vary materially within an interval, refine the intervals or obtain an appropriate time-dependent result. A total-volume comparison alone cannot establish pressure, quality or other delivery conditions.
The service requirement may include an allowed interruption, minimum contribution or restoration deadline. Apply that actual criterion to each interval. Report where and for how long it fails. Keep evidence for restoration timing separate from a proposed recovery plan: an unqualified time leaves the dependent conclusion conditional.
EAM.6:4.4 - Compare remedies and return the conditions
Compare additional capability, demand changes, sequencing, reserve, another fallback or changed recovery. Preserve burden and lost service moved to other users. An option that meets this scenario becomes a qualified candidate for the asset comparison, with its costs and remaining conditions.
Obtain a hydraulic, electrical, structural or stochastic result when that relationship determines the answer. Specify the arrangement, disturbance, required service and intervals it must address. A supported specialist result can replace an inadequate simple bound without restarting unrelated parts of the assessment.
Return the service envelope, failed scenario or precise missing result to EAM.7–EAM.10, and the relevant outage and recovery conditions to EAM.11. Stop when the receiving question is answered. Reopen on changed demand, dependencies, recovery support or operating conditions. Passing the selected scenarios supports only their stated scope.