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.