LIVE DEMO · SYNTHETIC DATA · PRESS RUN TO LOAD, 1.4 MBOpen full page →
Town 7 is a fictional town of nine estates and 922 buildings, run by seven owners, each with systems of its own. Pick a use case and the twin walks you down a ladder, from the town to an estate, a building and one piece of plant, in nine stops. At any figure you can ask Why? to trace it to its cause, open Evidence to see where it came from, or try What if? on a decision. Runs in your browser, phones included, and caches itself after the first visit. Synthetic data throughout.
LIVE DEMO · SYNTHETIC DATA · PRESS RUN TO LOAD, 1.4 MBOpen full page →
I was joint programme manager for a S$35M M&E technology refresh for a Government agency: an integrated command centre with a digital twin, coordinating more than ten suppliers across BMS, power SCADA, security and fire-alarm systems. That system belongs to its owner and cannot be shown, and a screenshot of it would explain very little. What makes an operations centre useful is the join: a meter owned by one party, a plant run by another and a work order raised by a third, all readable on one screen, with a clear line on who acts. Town 7 is a small town built to show those joins. It shares no layout, data or names with any system I have worked on, and every place, owner and reading in it is invented.
The twin has four rungs: Town, Estate, Building and Asset. With Explore you go down them freely, clicking an estate, then a building, then a piece of plant, and climb back with Up a level. With Use cases you pick one of twelve, grouped into four families (energy and cooling; building operations; water, waste and resilience; mobility and streets), and the twin walks you down in nine stops. The first states the objective at town scale. The next six follow the data through sense, connect, integrate, analyse, act and govern, across every place involved. Stop eight opens the main asset into its numbered parts, and the last says what was shown and whether it is Delivered or Explained.
Each stop carries one time-stamped moment from that use case's records, such as the minute a rule raised a watch or the minute a person confirmed an action, so pressing Next moves you through the event in the order it happened.
Town 7 is fictional, and every reading in it is synthetic and labelled as such on screen. The buildings and plant are drawn from simple shapes and resemble no real building, and no client's layout, system or data appears anywhere. Where a use case matches the kind of system on my track record, its card carries a Delivered tag that quotes that line and describes this kind of system; everything else is marked Explained, meaning the twin shows how that kind of system works. District cooling, PV and storage, EV charging, lifts and flood sensing are all Explained. The causes ranked in a Why trace come from written rules, and the What-if figures come from the textbook relations stated beside them; pump power rising with the cube of flow, for example, is quoted as an upper bound. A real operations centre is judged on integration breadth, data quality at the sensors and the people around the screen, and a browser demo can prove none of those. What it can show is how I think the screen should behave when someone asks where a number came from.
I treat a number on a screen as a claim. An operator should be able to trace it to a device, the device to its owner, and any action to the rule or the person behind it. That is the spine of every demo on this site; here it runs across a town of separate owners instead of one building.