Twin
A living digital twin of the park.
Every lamp, every pile, every leash in motion. A common operational picture.
Bajsogat · Twin v3.7·System operational
41Municipalities1,154,000Inhabitants47Recurrences
Latency 65 ms·SLA 99.6%·14:23:00.0
14:23:11 DNA MATCH P3 98.7%14:22:58 LAMP L3 DARK GAP14:22:41 LEASH KPL-04 BEARING 047°14:22:19 PREDICT STK-04 ELEVATED14:21:03 FIELD TEAM ETA 4 MIN14:20:44 ISO 17025 CHAIN OK14:23:11 DNA MATCH P3 98.7%14:22:58 LAMP L3 DARK GAP14:22:41 LEASH KPL-04 BEARING 047°14:22:19 PREDICT STK-04 ELEVATED14:21:03 FIELD TEAM ETA 4 MIN14:20:44 ISO 17025 CHAIN OK
59.33°N
18.07°ÖPOLYGON STK-04 · LIVEEvidence 3
18.07°ÖPOLYGON STK-04 · LIVEEvidence 3
Now
Ask the picture
Use
Five ways the municipality reads the park.
01
The lamp network
Every lamp is a node. Operating status, dark gaps and patrol routes sit in the same picture.
02
The piles
Every anomaly stays in the twin until it is cleared, matched and entered in the register.
03
Leash flow
Motion in the park, not stills. A leash in motion becomes a track.
04
The case drawer
A click on a node opens the case: DNA, polygon, chain of custody. Export when the committee asks.
05
Ask the picture
Put the question to the twin. Not to a form. The answer is nodes, not prose.
Twin FAQ