4.1 Typical System Topology

The reference topology for underground security surveillance systems follows a three-tier hierarchical architecture: Central Platform, Distribution Layer, and Field Zone. This structure mirrors the physical organization of underground facilities — a central control room at the surface or in a protected basement, intermediate distribution points at zone boundaries, and field cabinets distributed throughout each monitored zone. The topology is designed to minimize copper cable runs (which are susceptible to EMI and corrosion), maximize fiber utilization for inter-tier links, and provide independent zone operation in the event of uplink failure.

The distribution layer uses ERPS (Ethernet Ring Protection Switching) to provide sub-50 ms failover when a fiber segment is cut or a switch fails. Each field zone cabinet connects to the ring via two independent fiber paths, ensuring that no single fiber break can isolate a zone. Critical cameras in each zone are configured with onboard SD card recording as a fallback, ensuring evidence continuity even during network outages.

Underground Security Surveillance System Network Topology
Figure 4.1: Typical System Topology — Three-Tier Architecture with ERPS Ring, Field Zone Cabinets, and Central Platform

Central Platform

VMS cluster, storage array, ACS server, alarm engine, operator workstations, NMS. Redundant uplinks to distribution layer. Located in protected, climate-controlled room.

Distribution Layer

Aggregation switches in ERPS ring topology. Fiber connections to central platform and all field zone cabinets. Provides sub-50 ms failover on any single fiber break.

Field Zone

IP65 cabinet with industrial PoE switch, fiber media converter, SPD, and UPS. Connects to cameras, readers, controllers, intercoms, and sensors within the zone.

TierKey EquipmentConnection TypeRedundancyFailure Impact
Central PlatformVMS cluster, storage, ACS, alarm engine10GbE to core switchActive-active cluster, RAID6 storageFailover to secondary VMS node; no recording loss
Distribution (Ring)Aggregation switches (2–4 per ring)Single-mode fiber, 1–10 GbEERPS ring, <50 ms failoverSingle fiber break: ring heals; dual break: zone isolated
Field Zone CabinetIndustrial PoE switch, media converter, SPDFiber uplink + PoE copperSD fallback on critical camerasCabinet failure: zone offline; SD preserves evidence
Field DevicesCameras, readers, controllers, intercomsPoE Cat6, RS-485, dry contactOnboard SD (cameras), offline rules (ACS)Individual device failure; no zone-wide impact

4.2 Device Wiring & Connection Diagram

The field cabinet wiring diagram defines the physical connection standard for all underground zone cabinets. It specifies cable types, conductor gauges, maximum run lengths, connector types, and grounding requirements for each device category. Adherence to this standard is mandatory for all installations and must be verified during the acceptance inspection. Deviations require written engineering justification and approval before installation.

The diagram shows a single IP65 field cabinet with its internal DIN rail layout and all external device connections. Key wiring rules include: fiber uplink uses single-mode LC connectors with factory-terminated pigtails; PoE camera cables use Cat6 UTP with RJ45 connectors and maximum 90 m horizontal run (plus 10 m patch); RS-485 bus for access control readers uses 2-wire shielded cable with shield grounded at one end only (cabinet end); door lock power uses 18 AWG 2-core with maximum 50 m run at 12 VDC; and all cable entries use IP67 cable glands with appropriate strain relief.

Underground Security Field Cabinet Wiring Diagram
Figure 4.2: Field Cabinet Wiring Diagram — IP65 Cabinet Internal Layout with All Device Connections, Cable Types, and Grounding
ConnectionCable TypeConductorMax RunConnectorNotes
Fiber UplinkSMF OS2 9/125 µm10 km (standard)LC/APCFactory-terminated pigtails; no field splices in cabinet
PoE CameraCat6 UTP23 AWG90 m horizontalRJ45 T568BAvoid parallel runs with power cables; steel conduit in EMI zones
RS-485 (ACS readers)2-wire shielded24 AWG1200 m (OSDP)Terminal blockShield grounded at cabinet end only; 120 Ω termination at far end
Door Lock Power2-core stranded18 AWG50 m at 12 VDCTerminal blockVoltage drop <0.5 V at full load; fused at cabinet
Dry Contact (sensor/button)2-core stranded22 AWG100 mTerminal blockUse shielded cable in high-EMI areas
IP IntercomCat6 UTP23 AWG90 mRJ45 T568BSame rules as PoE camera; verify PoE class compatibility
GroundingGreen/yellow stranded6 AWG<5 m to earth barLug + earth barResistance <1 Ω; verify with earth tester at acceptance

Wiring Safety Rule: Never run PoE camera cables in the same conduit as 230 VAC power cables. Maintain a minimum 300 mm separation between low-voltage signal cables and high-voltage power cables. In areas with VFD (variable frequency drive) equipment, use shielded Cat6 or fiber for all camera connections within 5 m of the VFD.

4.3 Network Design Parameters

Network design for underground surveillance systems must account for the high bandwidth demands of multi-megapixel video streams, the latency sensitivity of access control and alarm events, and the reliability requirements of a 24/7 critical infrastructure system. The following parameters define the minimum acceptable network design for each solution package.

ParameterPackage A (Standard)Package B (Hardened)Package C (High Availability)
Uplink Bandwidth1 GbE per zone1 GbE per zone + 10% headroomDual 1 GbE or 10 GbE per zone
Ring TopologyOptionalMandatory (ERPS)Mandatory (ERPS + dual ring)
Failover Time<30 s (STP)<50 ms (ERPS)<50 ms (ERPS) + VMS HA
VLAN SegmentationCCTV + ACS VLANsCCTV + ACS + IoT VLANsCCTV + ACS + IoT + Mgmt VLANs
QoSVideo priority (DSCP AF41)Video + ACS priorityFull QoS policy with policing
NTP Accuracy±1 s±100 ms (NTP with monitoring)±1 ms (PTP for critical cameras)
Bandwidth Utilization Target<80% peak<70% peak<60% peak (30% headroom)

Bandwidth Calculation Reminder: Use the calculator in Chapter 9 to compute the total video bandwidth for your camera count and resolution mix. Add 20% overhead for control traffic, SNMP, and NTP. The result should not exceed the target utilization percentage for the selected solution package.