Recovery, resilience, decommissioning and lifecycle responsibility

Describe the function people need

Resilience concerns maintaining, adapting and recovering useful function under disruption. Specify the disturbance, service requirement, affected users and time horizon. Robustness against an initial loss and speed of restoration are related but different properties. A system that avoids damage and one that recovers quickly after damage can deliver different service histories.

Record dependencies and recovery resources. A spare asset may not help without trained people, access, compatible connections or information. A repair sequence can restore assets while leaving an essential end-to-end path incomplete. Recovery targets should therefore connect to service functions and the people needing them, rather than being inferred from an asset count.

Use a curve with a clear denominator

Let q(t) be delivered service divided by a fixed required service at elapsed time t. A value 0.4 means 40% of that specified quantity is delivered. It is a performance fraction, not a probability that the system survives. Quality, safety and distribution among users require separate checks; delivering the same quantity to the wrong location does not satisfy every service requirement.

Integrating 1−q(t) over time gives an equivalent full-service shortfall duration when the requirement is fixed and the quantity is meaningfully additive. For piecewise straight curves, rectangles and triangles are enough. This metric helps compare depth and duration, but it cannot by itself express all consequences of when or to whom the shortfall occurs.

Plan what remains after service ends

End-of-life decisions begin while the system’s materials, connections and records are still known. Inventory what will remain, who will receive it, and which information is needed for repair, reuse, disassembly or disposal. Stored energy, contamination and sensitive data can persist after ordinary operation ends; the appropriate transition needs qualified assessment and the relevant requirements.

Reuse can preserve useful material and function, but condition, compatibility and future responsibility still need evidence. Recycling a measured mass does not prove that every impact has been reduced. Compare a stated service over a consistent lifecycle boundary, including maintenance and the final transition. Retain records and assign custody so that unresolved obligations do not disappear with a change of owner.

Compare two original recovery curves

Both scenarios immediately deliver 0.4 of a fixed required service. A stays at 0.4 for two hours, then rises linearly to full service at hour six. Its shortfall is a rectangle 0.6×2 plus a triangle ½×0.6×4, totaling 2.4 equivalent full-service hours.

B stays at 0.4 for one hour and recovers linearly by hour three. Shortfall is 0.6×1+½×0.6×2=1.2 hours, half A’s. The figure assumes equal service meaning and quality. It does not estimate disruption likelihood, select a real recovery plan or establish how the remaining service is shared among users.

Try the reasoning

1. Can component restoration occur before usable service returns?

   Show the answer and reasoning

   Yes. Other dependencies, connections or operational checks can still prevent the required end-to-end function.

2. Does an integrated shortfall of 1.2 h mean the system was completely off for 1.2 h?

   Show the answer and reasoning

   No. It is an equivalent area under a service deficit; partial losses over longer periods can produce it.

3. Why preserve condition and material records when transferring an asset?

   Show the answer and reasoning

   The next custodian needs evidence for safe assessment, compatible reuse and responsible treatment of remaining materials and obligations.

What to carry forward

Evaluate recovered function and keep responsibility attached to the system through reuse, retirement and final disposition.