fpf.tools
Library / Engineering Asset Management Principles Framework
Jump to passage
In this reading
Source · lines 1820–1825

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:45:10 UTC

When a shared dependency changes recovery

A common dependency can require another option even when the normal-demand comparison passes. EAM.6’s separate feeder example shows both units losing their contribution together, reserve exhaustion before full recovery, and an independent supply whose time to usable service changes the result. Its qualified recovery conditions become inputs to EAM.7/.8’s alternatives and EAM.11’s calendar. A favourable price or available team does not restore the missing service.

To apply that construction to CityWater, obtain the relevant dependency, deliverability, usable reserve and restoration account for its actual service boundaries. Compare the resulting options in EAM.9/.10 and retain the relied-on recovery conditions in the recommendation. The original CityWater outage bounds remain useful for the situations they describe. If an observed restoration time or dependency changes, EAM.13 returns to the affected capability, option and timing rather than treating the former programme as qualified for the new loss.