Critical service boundaries and dependencies · Lesson 1

Translate an asset inventory into a service boundary and performance threshold

8 min read

Lesson objectives

  • Translate an asset inventory into a service boundary and performance threshold for a documented critical-service case.
Reading tools

Outcome and method By the end of this lesson, the learner can turn an asset inventory into a measurable boundary for a critical service and identify the threshold at which that service becomes unacceptable. Asset condition describes what the operator owns; service condition describes what a user actually receives at the necessary quantity, quality, place, and time. Two pumps may run while contaminated water cannot be used. Conversely, one pump may stop while a reservoir sustains delivery for a limited period. A resilience decision therefore starts with the service function, its users, and its minimum acceptable level, then traces the assets and dependencies that support it. ISO's published overview of ISO 55000:2024 relates asset-management objectives to organizational value across the asset life cycle, while CISA's planning framework emphasizes dependencies. These orientations do not establish conformity with a standard or local law for this teaching case.

Specify five fields before ranking assets: the user group, the usable product, the delivery point at which the operator measures performance, the demand rate for the scenario, and a quantity, quality, and time threshold that triggers action. Distinguish the physical boundary from the contractual boundary. The operator's pipe may end at the entrance to a healthcare facility, yet a loss within the facility still matters when analyzing service consequences. State the conditions that make a threshold meaningful: sufficient pressure, verified water quality, and the demand period represented by the figure. Do not declare continuity simply because some water can move. A user-facing measure might be cubic metres of usable water delivered each hour to a defined critical function. Specify the unit, aggregation window, and monitoring point.

Draw the boundary in three levels. The first is the service outcome that matters to the decision maker. The second lists functions required for that outcome, including pumping, treatment, distribution, monitoring, and control. The third lists supporting assets and resources such as grid power, operators, telemetry, storage, and emergency fuel. Starting at the third level and treating every item in the register as equally critical reverses the causal question. In a hypothetical hospital, a supply pump serving intensive care may be more important in the first hours than a pump serving landscape irrigation, even if the assets have the same age. That is a consequence-based priority for a specified disruption, not an instruction to neglect maintenance on the other pump. A valve that both flow paths share may be more consequential than the technical age ranking of either pump.

Define a minimum viable service as a package rather than a single flow number. A nominal 18 cubic metres per hour may meet volume demand while failing the service if the alternate path bypasses a required treatment step or fails to reach the critical ward. Conversely, demand curtailment can be a defensible temporary response if evidence shows that 12 cubic metres per hour serves the critical functions for a defined period and the curtailment authority is clear. Record who can approve this level, how water quality will be verified, and when the temporary decision expires. All figures in the example are fictional training inputs, not observed data about a real healthcare facility.

Before using a number in an investment case or response plan, ask where and when it was measured. Peak-hour demand may not represent the overnight pattern; a monthly average may be unsuitable for a four-hour outage. A meter covering two buildings cannot be treated as if its denominator were one critical ward. Add an evidence-status column to the boundary register: measured at delivery, inferred from pump operation, or assumed pending a test. The first is stronger evidence of service. The second still needs checks for leakage, valves, routing, and quality. The third supports only a conditional planning decision. Record the data owner, measurement date, and trigger for replacing an estimate with operational evidence. Without a critical-function flow meter, a declared approximate calculation can support planning, but a claim that service is continuing needs a delivery-point test or an agreed alternative observation. This distinction keeps a small theoretical margin from becoming unwarranted reassurance.

Lesson summary

Outcome and method By the end of this lesson, the learner can turn an asset inventory into a measurable boundary for a critical service and identify the threshold at which that ser