NERSA • Pennsylvania & Mid-Atlantic

Fiber Backbones for Security Systems

Plan the network connections behind cameras, access control and security equipment rooms.

Start with security operations

Identify what each connection must support: camera streams, recording access, door-controller communications, intercom calls or operator workstations. Record what happens if the link fails. A cable specification alone cannot define the operational result.

Map the dependencies

Document field devices, aggregation switches, uplinks, servers and management stations. Ask whether video stays local or crosses a backbone, and which services depend on a shared cabinet or power supply. Assign IT, facilities and security responsibilities before selecting equipment.

Separate the design decisions

• Passive plant: pathway, cable rating, fiber count, labels and terminations.
• Active network: supported optics, switch ports, capacity, configuration and monitoring.
• Power: local supply, PoE load, UPS objectives and recovery behavior.
• Applications: recording, access events, remote operation and user permissions.

Plan capacity around the application

Camera count alone is not a bandwidth calculation. Stream settings, concurrent viewing, recording destinations and failover traffic can change the uplink load. Access control may use modest bandwidth but still have strict availability and recovery requirements. Work from the selected system’s documented behavior.

Acceptance needs two layers

Require optical evidence tied to labeled links, then separately verify security functions. Confirm that authorized staff can retrieve video, receive relevant events and operate the system under the agreed conditions. A passing fiber test does not prove security-system commissioning.