POLYTRON National Stadium VMS — System Architecture

One EDGE block represents 35 independent stadium deployments. Video uses a separate path from the National Event Bus. “HQ video services” groups the specification’s central live-view, ingestion and playback capabilities; it does not prescribe a new product or physical cluster. The central store holds operational data and selected evidence; full-resolution recordings normally remain at their source stadium. Source: §§1–3, 9–14, 18–24, 37–42.

Principal video, event and operator paths are shown. The database is shared operational infrastructure: reads, additional service dependencies, direct device-health inputs, and management-to-AI model deployment are omitted from the connector layer for clarity. Live, control and event federation ports correspond to the national view above. Cluster placement is logical; final physical design and retention remain to be sized. Source: §§6–8, 15–18, 25–31, 37–39.

03 / SIZING AND OPERATING GUARDRAILS

Engineer the WAN for simultaneous viewing.

The specification’s bandwidth example uses up to 700 conventional 2K PTZ cameras per stadium. This is a sizing scenario within the broader 500–1,000-camera site capacity, not a camera-capacity ceiling.

HQ viewing profile / stadium	Engineered total / site	35-site aggregate	Recommended stadium WAN	HQ core implication
24 critical sub-streams only	22.5 Mbps	0.79 Gbps	Reserve 25–30 Mbps upstream	Baseline only; main streams are additional
24 sub-streams + 64 main streams	503 Mbps	17.6 Gbps	Dual 1 Gbps minimum	Redundant 25 Gbps minimum for controlled concurrency
24 sub-streams + 100 main streams	773 Mbps	27.0 Gbps	Dual 2.5 Gbps preferred	Redundant 40/100 Gbps preferred

Basis: 24 × 0.75 Mbps sub-streams, 6 Mbps main streams, and 25% engineering headroom. Each row includes the continuous baseline and assumes all 35 sites reach that concurrency simultaneously. At 1 Mbps per sub-stream, the baseline rises to approximately 1.05 Gbps nationally. A 25 Gbps HQ core cannot carry the 27 Gbps scenario. Validate camera bitrates, failover capacity and contractual viewing demand in detailed design. Source: §§10–14.

Local resilience

Recommended HA includes at least two management nodes, N+1 recording, clustered databases, dual switches and WAN paths, redundant storage, and UPS / generator-backed power. A site must remain operational without HQ.

Identity and trust

EDGE–HQ mutual TLS, device certificates, encryption at rest, MFA, scoped RBAC / ABAC, least privilege, network segmentation and audit. Prioritize critical alerts and command traffic over video transfers.

Time and evidence

Use one trusted time source. Evidence exports carry camera and stadium IDs, original and export timestamps, user identity, an audit record and a cryptographic hash.

Source: POLYTRON National Stadium VMS — System Architecture & Requirements Specification. Notion page 3d6830ac035c8103ab5dfb8e62646e4d, last edited 09 September 2026.

Scope: Requirements-derived logical architecture, with recommended capacity and HA patterns marked as such. The five planes are control, video, AI, spatial and event. Detailed UI panels, individual analytics, role matrices, storage-size examples and extreme all-camera streaming scenarios are consolidated or omitted. No cloud provider, messaging product, database engine or media transport is assumed.

Design decisions still required: camera mix and bitrate validation; peak viewing concurrency; protected retention capacity; failover / recovery objectives; final hardware and software products. This diagram does not claim these requirements have already been implemented.