City-infrastructure simulation

Civic Engine: A City-Infrastructure Simulation That Teaches Why Cities Work

Civic Engine is a free, in-browser simulation that puts you in charge of a small city’s roads, water, and power. It is less about building a pretty skyline and more about engineering: why pressure drops on a hillside, why one failure cascades into many, and why a dollar of maintenance beats five dollars of emergency repair.

Open Civic Engine

What Civic Engine is

Civic Engine (WorldWorks) is a city-infrastructure simulation built around three connected networks: roads that carry people and emergency crews, water from intake through treatment to homes, and power from generation to every building. The simulation runs day by day, and every problem comes with a “why” you can inspect — so you learn the systems thinking behind a working city, not just where to drag a tile.

It runs in your browser as a Learning tile on map.ca, with nothing to install. You manage a shared budget with three tools — inspect, repair, and bulldoze — across a campaign of missions in a hand-built valley.

Who it is for

Students of civics and engineering, urban-planning and public-works enthusiasts, educators, and anyone curious about why infrastructure fails and how the pieces connect. It rewards understanding cause and effect rather than memorising a build order.

The inspect-everything design makes it especially good for teaching: click any tile, pipe, road, or line and read exactly why it is — or is not — working, tied to the real-world principle behind it.

What it teaches

Homes only grow when they have road access, treated water, and power at the same time — so you learn that networks come first and growth follows. Water pressure depends on elevation, distance, and demand, which is why hillside districts need pumps or towers; power generation has to match demand every moment; and roads have a real peak-hour capacity that jams when you exceed it.

The deeper lessons are about resilience: redundancy so the loss of one component does not take down the city, preventive maintenance that is far cheaper than emergency repair, and cascade failures where one broken link — power to treatment to a pump to a clinic — knocks out everything downstream. Storms test all of it at once.

How to use Civic Engine

  1. Open Civic Engine. Launch the Civic Engine Learning tile on map.ca — it opens in your browser with nothing to install.
  2. Read the brief and build the basics. Start the first mission and place roads, a water intake, treatment, power, and homes within your budget.
  3. Inspect to learn the “why”. Use the inspect tool on any tile, pipe, road, or line to read why it is working or failing and the principle behind it.
  4. Use overlays and advance time. Turn on overlays for pressure, grid load, and response times, then tick days forward to watch the city respond.
  5. Repair, adapt, and finish missions. Fix aging assets before they fail, add redundancy, and meet each mission’s goals to unlock the next.

Frequently asked questions

Is Civic Engine free, and is it a city-builder?

It is free and runs in your browser on map.ca with nothing to install. It is a city-infrastructure simulation rather than a decorative city-builder — the focus is engineering systems (roads, water, power) and learning why they fail.

My homes have water but low pressure — why?

Usually elevation. Every metre of hill costs pressure, so uphill districts read low even when connected. A booster pump or a water tower restores it; the inspect tool shows the math behind the pressure drop.

Why does adding more roads sometimes make traffic worse?

Each road has a peak-hour capacity, and wider roads tend to fill back up with new trips (induced demand). The simulation teaches that shortening trips — jobs closer to homes — often beats simply adding lanes.

What does it teach about maintenance and resilience?

That preventive maintenance is far cheaper than emergency repair, and that redundancy matters: design so losing one component does not take down the city. Storms and cascade failures show why margin and backups are real engineering, not extras.