The Infrastructure Risk Outside Your Fence
A hospital can test its generators, maintain its equipment, and still discover that its most consequential vulnerability is a water pumping station across town. A telecommunications operator can protect its core network while overlooking the fuel delivery route that keeps backup power available. The asset that changes your outcome may belong to somebody else.
Consider a hypothetical flood. Your facility remains dry, its electricity supply is available, and the local operations dashboard looks reassuring. Yet a bridge closure prevents a chemical delivery to the water treatment plant. The plant reduces output, pressure falls, and your cooling process must slow. No asset inside your perimeter has failed. Your organization has nevertheless lost operating capacity.
One useful distinction is between a dependency that affects ordinary production and one that becomes critical only during recovery. A factory may operate normally without a particular road because routine supplies arrive elsewhere. After an outage, that road may be the only route that can carry a replacement component. The relationship is dormant during normal operations and decisive during restoration. Capturing both conditions prevents a normal-day assessment from becoming the entire resilience plan.
The planning implication is straightforward: resilience assessments need to follow services across ownership boundaries. NIST’s Community Resilience Planning Guide identifies dependencies and cascading effects as central to restoring infrastructure services [1]. The difficult work begins when that principle meets real contracts, incomplete information, and different operating priorities.
At GINOM, we frame the problem around the services an organization needs to function and the consequences when those services degrade. That broadens the question from a component’s condition to the conditions required to keep a mission running.
An effective dependency conversation starts with a specific output: safe drinking water, emergency care, reliable communications, or accessible transport. It then works backward through the resources required to sustain that output. This makes the exercise relevant to leaders who cannot inspect every technical detail but remain accountable for continuity.
A line between two assets is a useful beginning. To support a decision, the relationship needs conditions. How much input is necessary? Is there a substitute? How long can the receiving service operate without replenishment? What changes when demand increases? A dependency becomes operationally meaningful when you have answers to those questions.
In the flood scenario, a storage tank may initially protect the facility from reduced water pressure. That protection changes over time. A decision taken while the tank is nearly full can be wrong several hours later. The dependency hasn’t changed location; its urgency has.
Take a simple planning example, using invented values rather than a GINOM result. A facility has six hours of usable reserve at the assumed demand. The expected external repair takes four hours, but the delivery needed to restart the service adds three more. Looking only at repair duration suggests adequate protection. The full service chain reveals a one-hour gap. The next question is whether demand reduction, an alternative supply, or faster delivery can close it.
GINOM’s documented approach combines infrastructure relationships, scenario simulation, and recovery recommendations. Applied here, the platform can help teams examine how an interruption propagates and compare interventions against an agreed mission. The quality of that comparison depends on the relationships, capacities, and timing assumptions the model represents.
Start with a deliberately small network. Select one essential service, identify its immediate external inputs, and follow the most consequential input another step upstream. Ask the relevant owner to validate each relationship. Record unknowns as unknowns, with a named person responsible for resolving them.
That process often produces a more useful first result than a large unverified asset inventory. It identifies a decision that can change: whether to increase reserve capacity, establish an alternate delivery route, coordinate a restoration priority, or bring another operator into the exercise. A model earns its place when it helps people choose among those actions.
The next challenge is coordination. A bridge owner may prioritize traffic volume; the water operator may prioritize treatment capacity; the hospital may prioritize continuity of critical care. All three can make reasonable local decisions and still delay the shared outcome. The missing element is an agreed view of consequences.
A practical GINOM exercise would compare restoring the bridge, arranging an alternative delivery, and reducing nonessential demand. Participants would assess the service preserved, time required, resource conflicts, and assumptions that could reverse the preferred choice. Technical feasibility and safety remain with the responsible operators.
The shared plan also needs an exception process. If the bridge inspection contradicts the expected reopening time, the water operator should know when to revise its delivery assumption, and the hospital should know when to activate its alternative. Agreeing this trigger before the event can be as valuable as collecting another layer of asset data. It makes clear how new evidence travels across the same organizational boundaries as the disruption.
Measure progress through observable changes. How many important dependencies have been confirmed by their owners? Which continuity assumptions changed after simulation? How quickly can the team identify a viable alternative when a supplier fails? These measures reveal whether a dependency map is becoming a usable decision resource.
The future challenge is maintaining that resource as infrastructure changes. New digital services, electrified processes, and shared suppliers can alter the network faster than an annual review captures. Revisit relationships when contracts, operating configurations, or critical service requirements change. Tie updates to decisions people already make.
GINOM’s contribution is to make the consequences of those relationships easier to explore before an emergency, and more visible when priorities must change during one. The value lies in the actions that become possible once an external dependency is understood.
The question for your next resilience meeting is specific: which service outside your ownership boundary could stop your organization before your own contingency plan takes effect?
