KTS · OPS
LIVEMAJOR EVENT EXECUTION SVC03/06 EVT180,000 PAX WIN71 H INC0 AEGISV29 OK
Major Event Execution · 03/06

Crowd and Flow Architecture

A hundred and eighty thousand people. One coherent movement.

STATUS · OPERATIONAL
180,000
Pax single day
71h
Window
12
State visits
0
Incidents
9
Agencies integrated
100%
AEGIS V29
Phase architecture · current phase highlighted
Concept
Architecture
Execution
Wrap + Legacy
OP · 01

Why flow is the real security question

Most public incidents at scale are not security failures in the conventional sense. They are flow failures: a movement that was correct in a diagram and wrong under the loading of real bodies. Flow is the architecture that protects the sovereign day long before any other defence is needed.

We design flow as a first-class discipline, not as a subordinate of staging or security.

OP · 02

Instruments of flow architecture

01
Site flow model
gated zones, loading curves, rest-state durations, re-flow vectors, all simulated against realistic arrival distributions.
02
Contingency rerouting
pre-signed alternate flow maps with activation thresholds (weather, medical, protocol delay).
03
Synchronisation with protocol
principal movements deconflicted against public flow, never sharing a contested corridor.
04
Post-event reconciliation
actual flow reconciled against model, becoming the baseline for the next engagement.
OP · 03

Proof point

On the 180,000-attendee day, average rest-state duration held within 4% of the model across the full 71-hour window. Zero medical incidents attributable to flow. The model became the precedent.

Flow is not a diagram. Flow is a promise the state has made to the people inside the perimeter.

Map my event risk.

Map my event risk →