Electricity
OperatingWhat 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.
Change the inputs, pin a scenario and compare the result. Four system labs lead into a fifth experiment connecting the whole city.
Change both demand and available upward response in a fictional grid. Pin one set of assumptions as A, then compare the live result B.
How do demand and available upward response change the supply margin?
Add to or remove from the 100-unit baseline supply capability. Compare the same demand with different headroom.
Demand is met by 100 baseline units plus 0 units of response. 20 of the chosen 20 units of upward headroom remain.
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.
| Setting or result | A · Not pinned | B · Current |
|---|---|---|
| Demand relative to baseline | — | 100 % |
| Available upward headroom | — | 20 units |
| Scheduled supply | — | 100 units |
| Available headroom | — | 20 units |
| Unmatched demand | — | 0 units |
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.
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
Change outage duration and water demand while a fictional reservoir receives no inflow. Compare two assumptions about the same 600 m³ store.
How does demand change the amount of time a fixed store can bridge?
The usable store stays at 600 m³. A higher withdrawal rate uses the same volume sooner.
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.
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.
| Setting or result | A · Not pinned | B · Current |
|---|---|---|
| Time without pump inflow | — | 2 hours |
| Water demand | — | 100 m³/hour |
| Usable volume | — | 400 m³ |
| Volume buffer | — | 4 hours |
| Unmet volume | — | 0 m³ |
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.
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
Disconnect a link, then change the alternate path’s illustrative delay. Compare reachability and delay without treating the drawn route as a speed guarantee.
Can an alternate route preserve reachability while changing the assumed delay?
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.
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.
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.
| Setting or result | A · Not pinned | B · Current |
|---|---|---|
| Preferred connection | — | A–B available |
| Alternate path delay | — | 40 ms |
| Selected path | — | A → B → D |
| Illustrative delay | — | 20 ms one way |
| Destination | — | Connected |
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.
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
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.
How do the planned interval and longer stops combine to constrain frequency?
A wider planned gap provides more simplified margin, but schedules fewer trains through 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.
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.
| Setting or result | A · Not pinned | B · 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 |
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.
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
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.
0 h pump backup · 2 h internet reserve · 60 m³/h drainage
Grid restoration applies to the power interruption only.
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.
Hour 0: no incident selected. Four connected services are operating. Change the incident to see which dependency acts immediately and which buffer buys time.
Local grid supply serves the chosen pumps, access network and electric railway.
Continue ordinary operation; no disturbance is selected.
600 m³ of usable drinking-water storage remains full because inflow matches the chosen demand.
Maintain supply and monitoring. Stormwater drainage is a separate flow in this model.
The selected local access path is powered. The wider internet and user equipment are assumed available.
The backup reserve is ready; it is not being consumed.
The chosen electric line has grid supply and no selected track obstruction.
Routine operation continues; this model does not calculate a timetable.
Listed times are thresholds in this example. A reached time does not mean that a real service has been cleared to resume.
Supply matches demand. Elapsed time alone does not create an outage.
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.
| Assumption | Limited buffers | More prepared |
|---|---|---|
| Initial usable drinking-water store | 600 m³ | 600 m³ |
| Drinking-water demand | 100 m³/h | 100 m³/h |
| Backup pumping at 100 m³/h | 0 h | 4 h |
| Backed-up local internet path | 2 h | 8 h |
| Stormwater drainage capacity | 60 m³/h | 140 m³/h |
| Backup traction supply | None | None |
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.
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.
“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.
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.