Platform · Layer 04
Operational Worlds
A simulation layer for the operations teams behind every Fox Haven deployment. Below are the five questions partners actually ask in the first call, with the answers we give.
- Why does a heat-relief operation need a simulation layer?
- Because heat operations have no rehearsal season. The first day a heat dome arrives is the day the plan gets tested for real. Operational Worlds is the place to test the plan before that day, against the same data the live system will see.
- What does a partner actually do with it on day one?
- Run a scenario against last summer. Pull the heat-stress data we observed, model the cooling-center inventory you actually had, and ask what would have changed if two more sites had been open from June to September. The answer comes back the same way a live recommendation would, with the signals it leaned on and the alternatives it considered.
- How is this different from a dashboard?
- A dashboard shows what happened. This layer lets you ask what would happen. The two share a model and a data layer; the simulation just runs the model forward with different inputs. Same engine, different timestamp.
- What does the data come from?
- For Phoenix, the same Civic Infrastructure feeds the live system uses, NWS, AirNow, Valley Metro, partner shelter and cooling-center inventories. Anything still pending in the pilot (vulnerability indicators from ACS, mobility partners) is clearly labeled in the scenario output so you never confuse modeled data for measured data.
- Who is supposed to be using it?
- Operations leads at partner organizations, primarily. City emergency-management staff. Hospital ops chiefs. The director of a community organization deciding whether to add a Saturday-shift outreach team for August. Not residents, Operational Worlds is for the people doing the planning.
If your team is staring at next summer’s operating plan and wondering what the alternatives look like, bring the data you have. We’ll model the rest with you.