Chapter 4: Architecture Design

Security Systems Lightning Protection and Grounding Design Guide

4.1 Typical System Topology

The typical security system lightning protection architecture follows a hierarchical network topology that places fiber optic links at every inter-building and inter-zone boundary, reserving copper connections for the final segment between field cabinets and end devices. This "fiber-first" topology eliminates the most significant surge paths — long outdoor copper runs between buildings — while maintaining the cost-effectiveness of copper for short indoor and cabinet-level connections.

The topology diagram below illustrates the complete system from the WAN/internet boundary through the core network layer, distribution switches on building floors, field switches in outdoor cabinets, and finally to end devices. SPD symbols are shown at every copper link entry point, and MEB/LEB bonding bars are shown at the core room and each field cabinet. Fiber links are shown as dashed lines to distinguish them from copper links, which require SPD protection.

Figure 4.1: Typical System Topology — Hierarchical Network with Fiber Isolation and SPD Boundaries

Topology Design Principles

The topology design is governed by five principles that together minimize surge risk while maintaining network performance and maintainability. First, fiber is used for all inter-building and inter-zone links, eliminating the most energetic surge paths. Second, copper links are limited to short runs within a single zone, where induced surge energy is lower and SPD protection is more effective. Third, redundant core switches with ring topology provide path diversity for both normal traffic and post-surge recovery. Fourth, field cabinets serve as the primary surge control boundary for their associated endpoints, with LEB bonding and SPD protection for all incoming lines. Fifth, the topology supports remote SPD monitoring, enabling proactive maintenance before the next storm event.

4.2 Performance Indicators & Acceptance Criteria

The architecture design must be validated against a set of measurable performance indicators that cover both the electrical protection performance and the system availability performance. These indicators are organized into three groups: protection effectiveness indicators (ground resistance, bond continuity, SPD Up coordination), system performance indicators (packet loss, PoE stability, false alarm rate), and operational indicators (MTTR, documentation completeness, post-event recovery). All indicators must be baselined during commissioning and re-measured after any significant modification or storm event.

4.3 Equipment Connection Diagram

The equipment connection diagram illustrates the complete wiring arrangement for a typical field cabinet installation, showing the correct sequence and routing of all power, data, and bonding connections. The diagram emphasizes the critical importance of SPD placement — before sensitive equipment, not after — and the requirement for short, straight earth leads from SPD terminals to the LEB. The comparison between correct and incorrect wiring practices provides a practical reference for installation teams and quality inspectors.

Figure 4.2: Equipment Connection Diagram — Correct Wiring (AC SPD → CB → UPS → PDU; Ethernet SPD at entry; all earths to LEB) vs. Common Incorrect Practices

Connection Sequence Requirements

The correct connection sequence for field cabinet wiring follows a strict order that ensures each protective element is in place before the next element that depends on it. For AC power, the sequence is: utility input → Type 2 SPD → circuit breaker → UPS (if present) → rack PDU → loads. The SPD must be installed before the circuit breaker, not after, to ensure that the breaker's overcurrent protection is not bypassed by the surge current path. For data connections, the sequence is: external copper cable → Ethernet SPD (bonded to LEB) → PoE switch → end devices. Fiber connections require no SPD but the media converter enclosure must be bonded to the LEB.

4.4 Business Logic & Exception Handling

The system's operational logic must account for both normal operating conditions and the exception scenarios that arise during and after lightning events. A well-designed exception handling workflow reduces mean time to recovery and prevents secondary failures caused by incorrect responses to surge-induced alarms or link flaps. The three primary exception scenarios are SPD failure, link instability during storms, and false alarm spikes — each requiring a distinct response workflow.