Invisible
Infrastructure.
Explore
FIVE CONNECTED EXPERIMENTS

Change one thing.
Follow the effect.

Change the inputs, pin a scenario and compare the result. Four system labs lead into a fifth experiment connecting the whole city.

01
Electricity / Grid balance

What if demand rises?

Interactive model

Change both demand and available upward response in a fictional grid. Pin one set of assumptions as A, then compare the live result B.

A small grid, a changing loadDemand covered
GENERATIONDISTRIBUTIONDEMAND 100 units supplied100 units requested DemandSupply 120 limit0160 ILLUSTRATIVE UNITS · STEADY BALANCE AFTER RESPONSE
Baseline: 100 demand units · 20 units of upward headroom

A small grid, a changing load

Scroll or use the arrow keys to explore the enlarged diagram. Close with the button or Escape. Baseline: 100 demand units · 20 units of upward headroom.

01 / Change the inputs
100%
60%140%

How do demand and available upward response change the supply margin?

20units
0 units60 units

Add to or remove from the 100-unit baseline supply capability. Compare the same demand with different headroom.

02 / Read the responseAgainst starting conditions: demand unchanged; headroom unchanged.
Scheduled supply
100units
Available headroom
20units
Unmatched demand
0units
Supply can match demand

Demand is met by 100 baseline units plus 0 units of response. 20 of the chosen 20 units of upward headroom remain.

03 / Compare A and B

TWO INPUTS. TWO CONDITIONS.

Pin the current settings as A, then change either input to test B. A stays in memory only while this page is open. Shared links include the current B inputs, never the pinned A.

No A is pinned. Enable the interactive controls, choose settings and pin them to compare.

Compare both inputs and the model response. A stays fixed until you replace or clear it; B follows the controls.
Setting or resultA · Not pinnedB · Current
Demand relative to baseline—100 %
Available upward headroom—20 units
Scheduled supply—100 units
Available headroom—20 units
Unmatched demand—0 units
Inside the modelAssumptions, limits & sources

The balancing principle is informed by grid-operation sources; all capacities are editorial teaching values. With demand of 140 and response capability of 20, supply is capped at 120 and 20 units remain unmatched. Raising the assumed response capability to 40 covers that demand. This changes a chosen limit, not a forecast of what real equipment can deliver.

  • The baseline demand and scheduled supply are both 100 arbitrary power units, not measurements from a real system.
  • Available upward response is a second control, ranging from 0 to 60 units with a starting value of 20. Supply is assumed able to reduce to match demand below 100 units.
  • Scheduled supply = min(demand, 100 + available upward response). Unmatched demand = max(0, demand − scheduled supply). Available headroom = 100 + available upward response − scheduled supply.
  • The result is a static balance after response. Network losses, location, ramp rates, stored-energy duration and contingency reserves are omitted. Changing the response control does not explain how that capability would be obtained.
  • The model does not calculate frequency, blackout probability, cost or emissions. An uncovered shortfall means the chosen illustrative resources are insufficient, not that a particular real protection action will occur.

Model references: Australian Energy Market Operator: Guide to Frequency Control Ancillary Services · U.S. Environmental Protection Agency: Electricity Delivery and its Environmental Impacts · U.S. Energy Information Administration: Electricity glossary

02
Water / Storage & resilience

How long can stored water bridge an outage?

Interactive model

Change outage duration and water demand while a fictional reservoir receives no inflow. Compare two assumptions about the same 600 m³ store.

A reservoir buying timeDrawing on storage
PUMP OFFLINEUSABLE STORAGE OVER TIME 600 m³ initial 400m³ remaining 0 inflow100 m³/h demand 6003000 0612 h Empty after 6 h at 100 m³/hELAPSED 2 h · VOLUME BALANCE, NOT A PRESSURE FORECAST
Baseline: 600 m³ usable storage · 100 m³/h demand · no inflow

A reservoir buying time

Scroll or use the arrow keys to explore the enlarged diagram. Close with the button or Escape. Baseline: 600 m³ usable storage · 100 m³/h demand · no inflow.

01 / Change the inputs
2hours
0 h12 h

How does demand change the amount of time a fixed store can bridge?

100m³/hour
50 m³/hour200 m³/hour

The usable store stays at 600 m³. A higher withdrawal rate uses the same volume sooner.

02 / Read the responseSince the pump stopped: 200 m³ delivered. Full-store buffer: 6 h, compared with 6 h at the starting demand.
Usable volume
400m³
Volume buffer
4hours
Unmet volume
0m³
400 m³ of usable storage remain

Demand removes 100 m³ each hour while the pump supplies nothing. At hour 2, 400 m³ remain: 4 more hours at this assumed demand. Storage volume alone cannot establish pressure or water quality.

03 / Compare A and B

TWO INPUTS. TWO CONDITIONS.

Pin the current settings as A, then change either input to test B. A stays in memory only while this page is open. Shared links include the current B inputs, never the pinned A.

No A is pinned. Enable the interactive controls, choose settings and pin them to compare.

Compare both inputs and the model response. A stays fixed until you replace or clear it; B follows the controls.
Setting or resultA · Not pinnedB · Current
Time without pump inflow—2 hours
Water demand—100 m³/hour
Usable volume—400 m³
Volume buffer—4 hours
Unmet volume—0 m³
Inside the modelAssumptions, limits & sources

Conservation of water connects inflow, outflow and the change in storage. At the starting demand of 100 m³/h, 600 m³ lasts six hours with no inflow. At 200 m³/h it lasts three hours. Pin a scenario before changing demand to compare these assumptions directly; neither result predicts service at a particular tap.

  • The chosen starting usable storage is 600 m³. This is an editorial teaching value, not a measured or typical reservoir.
  • Pump inflow is zero throughout the selected interval. Requested demand is constant within each scenario and can be set from 50 to 200 m³/h; its starting value is 100 m³/h.
  • Remaining usable volume = max(0, 600 − demand × elapsed hours). Unmet volume = max(0, demand × elapsed hours − 600). Total storage duration = 600 / demand.
  • Remaining volume buffer = max(0, 600 / demand − elapsed hours). No alternate supply, leakage, evaporation or changing demand is included.
  • Storage is assumed deliverable until its usable volume reaches zero. Real pressure can become inadequate before a tank is empty. No water-quality or pressure calculation is performed.
  • The references explain real storage, pumping and pressure dependencies. The selected values and calculated durations are original illustrative arithmetic, not operational standards.

Model references: Sydney Water: Water System Planning Guideline · US Environmental Protection Agency: How to Conduct a Sanitary Survey of Drinking Water Systems · US Environmental Protection Agency: Protecting Water Quality Through Distribution System Pressure Management

03
Internet / Network resilience

What if a network link fails?

Interactive model

Disconnect a link, then change the alternate path’s illustrative delay. Compare reachability and delay without treating the drawn route as a speed guarantee.

Two ways across the networkPreferred route selected
ILLUSTRATIVE TOPOLOGYALL LINKS AVAILABLE AYour access networkBPreferred transitCAlternate transitDDestination network A → B → D20 ms chosen delayA → C → D40 ms chosen delay Selected pathAvailable connection
Baseline: Preferred path 20 ms · alternate path 40 ms · all links available

Two ways across the network

Scroll or use the arrow keys to explore the enlarged diagram. Close with the button or Escape. Baseline: Preferred path 20 ms · alternate path 40 ms · all links available.

01 / Change the inputs
Normal route

Can an alternate route preserve reachability while changing the assumed delay?

40ms
20 ms120 ms

This is an illustrative one-way delay for the whole path through C. Disconnect A–B to use it; it does not change whether the path exists.

02 / Read the responseSelected delay remains 20 ms. Disconnect A–B to test the 40 ms alternative.
Selected path
A → B → D
Illustrative delay
20ms one way
Destination
Connected
Traffic follows A → B → D

The selected route through B has a chosen one-way delay of 20 ms. The alternative through C is set to 40 ms. Changing that assumption does not change the selected path while A–B remains available. Real routing depends on protocols and policy; it is not simply the shortest line on this drawing.

03 / Compare A and B

TWO INPUTS. TWO CONDITIONS.

Pin the current settings as A, then change either input to test B. A stays in memory only while this page is open. Shared links include the current B inputs, never the pinned A.

No A is pinned. Enable the interactive controls, choose settings and pin them to compare.

Compare both inputs and the model response. A stays fixed until you replace or clear it; B follows the controls.
Setting or resultA · Not pinnedB · Current
Preferred connection—A–B available
Alternate path delay—40 ms
Selected path—A → B → D
Illustrative delay—20 ms one way
Destination—Connected
Inside the modelAssumptions, limits & sources

Routing references explain how an alternative can be selected; delay measurements are a different question from reachability. Here the selected path has an assigned one-way delay: 20 ms through B, or the chosen delay through C after failure. The model does not derive latency from distance, measure bandwidth or calculate page-load time.

  • The topology is invented: path A → B → D is preferred and A → C → D is available as an alternative. It does not represent providers, locations or actual links.
  • The first control changes link A–B from available to failed. All other links and both endpoints remain available.
  • After failure, routing is assumed to have converged to an allowed alternate route with sufficient capacity. Detection time, convergence, packet loss, queues and transport recovery are omitted.
  • The preferred path is assigned an illustrative one-way delay of 20 ms. The alternate path delay is a second control from 20 to 120 ms, starting at 40 ms. These are editorial values, not measurements or a geographic estimate.
  • The alternate-delay control affects the selected path only when A–B has failed. Real routing follows protocols and policy rather than necessarily choosing the lowest-delay path.
  • A surviving path means reachability under these assumptions. It does not guarantee seamless recovery, application performance or independence from shared physical dependencies.

Model references: IETF / RFC Editor; F. Baker (editor): RFC 1812: Requirements for IP Version 4 Routers · IETF / RFC Editor; Y. Rekhter, T. Li, and S. Hares (editors): RFC 4271: A Border Gateway Protocol 4 (BGP-4) · IETF / RFC Editor; W. Eddy (editor): RFC 9293: Transmission Control Protocol (TCP) · Internet Society: The Internet Way of Networking: Defining the critical properties of the Internet · IETF / RFC Editor; G. Almes, S. Kalidindi, and M. Zekauskas: RFC 2681: A Round-trip Delay Metric for IPPM

04
Urban rail / Capacity & time

A few more seconds at the platform

Interactive model

Change the planned interval and add the same extra dwell to every train at one critical station. Compare spare time and the resulting rate at this one bottleneck.

One platform, a repeating serviceWithin planned interval
A REPEATING BOTTLENECKILLUSTRATIVE · NOT TO SCALE PLATFORM / CONSTRAINED SECTION 120 s repeat interval StartingCurrent 0120240360 s SOLID BLOCK: OCCUPIED TIME · GAP: SIMPLIFIED MARGIN
Baseline: 120-second planned interval · 90-second occupation

One platform, a repeating service

Scroll or use the arrow keys to explore the enlarged diagram. Close with the button or Escape. Baseline: 120-second planned interval · 90-second occupation.

01 / Change the inputs
15seconds
0 s60 s

How do the planned interval and longer stops combine to constrain frequency?

120seconds
90 seconds180 seconds

A wider planned gap provides more simplified margin, but schedules fewer trains through this bottleneck.

02 / Read the responseAgainst starting conditions: repeat interval unchanged; rate 30 versus 30 trains/hour.
Repeat interval
120seconds
Implied rate
30trains / hour
Margin left
15seconds
30 trains/hour at this bottleneck

The 105-second occupation still fits within a 120-second interval. 15 seconds of simplified margin remain, so the implied rate is 30 trains/hour. Other constraints and recovery time are outside this model.

03 / Compare A and B

TWO INPUTS. TWO CONDITIONS.

Pin the current settings as A, then change either input to test B. A stays in memory only while this page is open. Shared links include the current B inputs, never the pinned A.

No A is pinned. Enable the interactive controls, choose settings and pin them to compare.

Compare both inputs and the model response. A stays fixed until you replace or clear it; B follows the controls.
Setting or resultA · Not pinnedB · Current
Additional dwell at the critical station—15 seconds
Planned interval—120 seconds
Repeat interval—120 seconds
Implied rate—30 trains / hour
Margin left—15 seconds
Inside the modelAssumptions, limits & sources

At the starting planned interval of 120 seconds, 15 extra seconds make the station occupation 105 seconds and leave 15 seconds of margin. With 45 extra seconds, occupation is 135 seconds and the implied rate is about 26.7 trains per hour. Changing the planned interval changes the comparison; it does not establish an achievable timetable for a real railway.

  • This is an original steady-state teaching model of repeated longer stops, not a simulation of one delayed train or a real timetable.
  • The planned interval is a second control, from 90 to 180 seconds with a starting value of 120 seconds. A 120-second interval is equivalent to 30 trains per hour if sustained.
  • The chosen baseline station occupation is 90 seconds, including the relevant occupation and clearance effects. All other constraints remain fixed.
  • Effective headway = max(planned interval, 90 + extra dwell), in seconds. Illustrative sustained throughput = 3600 / effective headway.
  • Remaining margin = max(0, planned interval − 90 − extra dwell). A shorter planned interval can offer more trains per hour while leaving less margin at this bottleneck.
  • No passenger-crowding feedback, variable braking, junction conflict, turnback, fleet or recovery behaviour is simulated. Actual railway analysis requires these and other details.

Model references: Transportation Research Board / National Academies: Transit Capacity and Quality of Service Manual, Third Edition, Chapter 8: Rail Transit Capacity · National Academies of Sciences, Engineering, and Medicine / Transportation Research Board: Transit Capacity and Quality of Service Manual, Fourth Edition · Network Rail: The timetable

THE CONNECTED CITY / A SHARED SYSTEM

One incident.
Different clocks.

Change a fictional local incident. Follow electricity, water, internet access and rail together—and see why buffers delay some effects while recovery needs more than elapsed time.

An original teaching model, not a real-city forecast. Every quantity, threshold and backup duration below is deliberately chosen. The diagram shows selected dependencies, not a complete network.

01 / Set the conditions

0 h pump backup · 2 h internet reserve · 60 m³/h drainage

0hours

Grid restoration applies to the power interruption only.

Selected dependencies / Four services, one place
01 / PUMPINGGrid supply 02 / ACCESS NETWORKPowered equipment 03 / ELECTRIC TRAINSTraction power 04 / DRAINAGE → TRACK NORMAL OPERATIONHOUR 0 / LIMITED BUFFERS 01ElectricityOperatingSupply available02Water & drainageOperating600 m³ stored03Internet accessOperating2 h backup reserve04Urban railOperatingSelected line availableCONCEPTUAL DEPENDENCIES · ORIGINAL TEACHING VALUES

Arrows name a dependency. Dashed power links mean the selected local supply is interrupted; status text explains whether a buffer still covers it. Water storage and stormwater drainage are separate flows.

The connected city

Scroll or use arrow keys to explore. Close with the button or Escape. The complete current explanation is also written in the four service panels.

02 / READ THE CONSEQUENCES

Hour 0: no incident selected. Four connected services are operating. Change the incident to see which dependency acts immediately and which buffer buys time.

01

Electricity

Operating

What still works

Local grid supply serves the chosen pumps, access network and electric railway.

What needs to happen next

Continue ordinary operation; no disturbance is selected.

02

Water & drainage

Operating

What still works

600 m³ of usable drinking-water storage remains full because inflow matches the chosen demand.

What needs to happen next

Maintain supply and monitoring. Stormwater drainage is a separate flow in this model.

03

Internet access

Operating

What still works

The selected local access path is powered. The wider internet and user equipment are assumed available.

What needs to happen next

The backup reserve is ready; it is not being consumed.

04

Urban rail

Operating

What still works

The chosen electric line has grid supply and no selected track obstruction.

What needs to happen next

Routine operation continues; this model does not calculate a timetable.

The causal links

Time is only one condition

Listed times are thresholds in this example. A reached time does not mean that a real service has been cleared to resume.

  1. 0 h
    Normal operation

    Supply matches demand. Elapsed time alone does not create an outage.

03 / HOLD ONE STATE STILL

Compare A with B.

Save the current state as A, then change a control to compare it with B. The snapshot stays on this page only; a shared URL carries the current controls.

Inside the city model Rules, equations & sources +

Two profiles. Chosen values.

Original teaching assumptions, not minimum standards or typical performance
AssumptionLimited buffersMore prepared
Initial usable drinking-water store600 m³600 m³
Drinking-water demand100 m³/h100 m³/h
Backup pumping at 100 m³/h0 h4 h
Backed-up local internet path2 h8 h
Stormwater drainage capacity60 m³/h140 m³/h
Backup traction supplyNoneNone

Power interruption

The local grid is unavailable until “Grid restored now” is selected. Rail pauses immediately in both profiles. Backup pumping, where included, exactly matches water demand until it ends; the store then drains. The internet assumption covers the chosen access equipment and user equipment; the wider path is unaffected. Real backup arrangements differ.

Water remaining = max(0, 600 − 100 × max(0, hours − pump-backup hours))

Internet reserve remaining = max(0, backup hours − elapsed hours)

For the limited profile, the internet reserve ends at hour 2 and the water volume at hour 6. For the prepared profile, pumping backup ends at hour 4, internet reserve at hour 8, and water volume at hour 10. These are arithmetic consequences of the chosen values. They do not establish real water pressure, quality or network availability.

Heavy rain

The fictional storm produces 120 m³/h of runoff for three hours, then stops. Drainage has an adequate receiving outfall and no hidden blockage. Limited drainage allows 180 m³ to accumulate by hour 3, then clears it by hour 6. Prepared drainage keeps up with the chosen runoff. The drinking-water store stays full in this event because pumping and demand remain balanced.

Ponding = max(0, (120 − drainage capacity) × min(hours, 3) − drainage capacity × max(0, hours − 3))

Any positive ponding pauses the fictional exposed rail line and triggers a water-quality assessment in this exercise. Volume is not flood depth, a railway operating limit or evidence of contamination. Once that gate has been triggered, elapsed time never signs off the inspection or assessment. Grid and internet equipment are assumed unexposed to this particular storm.

Restoration is a separate step

“Grid restored now” returns power at the selected hour, with no time simulated afterward. It preserves the remaining water and battery quantities. A network that stayed on backup can remain available during the assumed transfer; one that lost power needs a successful restart. Rail remains paused pending its own checks. This is a dependency lesson, not an emergency plan or a procedure for operating infrastructure.

Evidence and boundaries

CISA describes dependencies between infrastructure services and the role of backup resources. EPA explains water-sector power resilience and runoff. Communications guidance distinguishes power at user equipment from availability of the wider path. Network Rail explains why disruption can continue after floodwater clears. These sources support the relationships; none supplies the numbers, trigger rules or promised recovery times in this model.

Artwork and model rules are original. No source illustrations or operating instructions are reproduced. Real systems add location, demand variation, asset damage, staffing, equipment condition, fuel, communications dependencies and many other constraints.