1. Start With Security Zones and Threat Boundaries

Map the campus before choosing cable:

• Public boundary and visitor entry
• Vehicle gates and guardhouses
• Staff entrances
• Loading and delivery areas
• Offices and security control room
• Data halls and meet-me rooms
• UPS, battery and electrical rooms
• Generator and fuel areas
• Roof, yard and perimeter cameras
• Telecom entrance rooms
• Inter-building pathways
• Emergency exits and fire-compartment interfaces

For each zone, document the device, controller, switch, power source, recording destination, communication path, expected retention, failure response, and maintenance access.

Security functions should also be classified by criticality. A failed office camera and a failed mantrap reader do not create the same risk. Critical paths may need local controller intelligence, redundant servers, dual network paths, UPS-backed switches, diverse fibre routes or spare conductors.

2. Split Access Control Into Separate Circuits

A typical controlled door can include:

• Card or biometric reader
• Door controller or interface module
• Electric strike, maglock or motorized lock
• Door-position switch
• Request-to-exit device
• Break-glass or emergency release
• Sounder or indicator
• Intercom
• Fire alarm interface

These circuits have different data, voltage, current, conductor-size and life-safety requirements. A composite access-control cable may simplify pulling, but every component still needs to be electrically correct and accepted by the equipment manufacturer and AHJ.

Reader communication

Legacy Wiegand commonly uses multiple conductors in a point-to-point arrangement and lacks the security and bidirectional features available in modern OSDP implementations. SIA describes OSDP as a communication protocol for interoperable access-control devices and emphasizes Secure Channel for encrypted, authenticated communication.

Where supported by the approved reader and controller, specify:

• OSDP-capable equipment
• Secure Channel enabled after commissioning
• Correct RS-485 cable construction
• Addressing and baud-rate plan
• Bus topology and termination
• Shield bonding and grounding
• Unique key-management process
• Verified product compatibility

Do not assume that using an RS-485 cable automatically enables OSDP security. Secure Channel is a system configuration and key-management requirement.

Lock power

Lock circuits are driven by voltage drop and inrush or operating current. Confirm:

• Lock type and fail-safe/fail-secure behavior
• Nominal and worst-case current
• Supply voltage
• Route length
• Conductor size
• Local or centralized power supply
• Battery backup
• Fire alarm release logic
• Voltage at the lock under worst-case load

Do not use reader-data conductors to carry lock power unless the approved composite cable and device design explicitly allow it.

Door monitoring and release

Door contacts and request-to-exit devices may use low-current circuits but still require correct conductor count, supervision, routing and identification. Emergency release and fire-alarm interfaces must follow local life-safety and egress rules. Security availability must never override required safe egress.

3. Choose OSDP Cable as an RS-485 Channel

OSDP reader communication is based on RS-485. The cable schedule should state:

• One balanced twisted pair for data as required by the system
• Characteristic impedance required by the controller/reader manufacturer
• Conductor size and resistance
• Shield and drain-wire requirement
• Rated voltage and temperature
• Overall sheath and fire rating
• Indoor/outdoor and UV performance
• Maximum segment length and device count
• Topology, stubs and termination

SIA's implementation guidance recommends Secure Channel and stresses correct configuration. Use OSDP Verified products where the project requires verified interoperability. Cable is only one element; reader, controller, firmware and commissioning practices must work together.

4. Design CCTV Around Bandwidth, Power and Distance

For every camera, record:

• Resolution, codec and frame rate
• Main and secondary streams
• Analytics and metadata
• Audio, PTZ, heater, IR and illuminator loads
• PoE class and worst-case power
• Copper channel length
• Switch location and port budget
• UPS runtime
• Recording destination and retention
• Environmental enclosure and temperature
• Surge and lightning exposure

Copper Ethernet and PoE

Cat6 or Cat6A copper cabling is commonly used for IP cameras within an engineered Ethernet channel. The selection should consider bandwidth, PoE power, insertion loss, DC resistance, resistance unbalance, bundle heating, ambient temperature, pathway fill and future replacement.

IEEE 802.3af introduced standardized powering over the Ethernet interface, and IEEE 802.3bt expanded standardized higher-power PoE. The camera and switch must negotiate or support the same applicable PoE technology. A high-wattage camera with heaters, IR, PTZ or edge computing may require more than a basic PoE port can deliver.

Avoid selecting cable only by category. Confirm:

• Solid copper conductors, not copper-clad substitutes for permanent PoE channels
• Category and channel standard
• Conductor gauge and DC performance
• Shielding and bonding where required
• CPR, LSZH, plenum or riser requirement
• Outdoor, UV and water-blocked construction where needed
• Maximum ambient temperature and bundle size
• Patch cords, connectors and patch panels of a compatible category

Fibre for distance, isolation and campus backbones

Use optical fibre where copper distance, EMI, electrical-potential difference, lightning exposure or campus architecture makes copper unsuitable. Common applications include:

• Guardhouse to main security building
• Perimeter camera aggregation cabinets
• Links between data halls
• Remote electrical yards
• Redundant paths to the security operations center
• High-bandwidth video aggregation

Select OS2 or multimode fibre according to equipment, reach, bandwidth and upgrade plan. Define fibre count, spare fibres, indoor/outdoor transition, armour, duct, splice closure, ODF, patch cords, connector type and testing.

5. Verify ONVIF Conformance, Not Just the Logo

ONVIF profiles define standardized feature sets for IP-based physical-security products.

• Profile T supports advanced IP video streaming, including H.264/H.265-related capabilities, imaging settings, metadata and alarm events within its profile requirements.
• Profile G addresses recording and retrieval.
• Profile M addresses analytics metadata and events.
• Profile A addresses access-control configuration such as credentials, schedules and rules.

ONVIF states that only registered products conformant to a profile are considered ONVIF conformant. Procurement should verify the exact camera, recorder, VMS, access-control product and firmware against the ONVIF conformant-products database or project-approved evidence.

Cable does not create ONVIF interoperability, but insufficient bandwidth, unstable PoE or poor installation can make conformant products perform badly.

6. Plan Resilient Security Pathways

Security cabling should be coordinated with the data center's operational resilience plan:

• Avoid a single tray or riser for all critical cameras and controllers
• Separate redundant fibre paths where the risk analysis requires it
• Place security switches and controllers in protected, maintainable locations
• Provide UPS-backed power for selected network and controller equipment
• Keep local door operation safe during upstream network loss
• Segment networks and limit broadcast/failure domains
• Reserve fibre, rack space, switch ports and pathway capacity
• Protect outdoor cabinets against heat, dust, moisture and tampering
• Document isolation points for planned maintenance

Tier classification does not automatically prescribe the security topology. The owner, security consultant and operations team must define which functions need redundancy and how failures are handled.

7. Coordinate Fire Compartments and Egress

Access control interacts with fire alarm and emergency egress. Coordinate:

• Fail-safe or fail-secure lock behavior
• Emergency door release
• Fire alarm input to access-control panels
• Smoke-control or stair-door interfaces
• Cable penetrations and firestopping
• Fire-rated pathways where required
• Separation of security and life-safety circuits
• Local code and AHJ approval

A data center's security objective must not block legally required evacuation. Cable selection is only one part of the approved door and life-safety system.

8. Outdoor and Perimeter Requirements

Campus security devices can face:

• UV and temperature extremes
• Rain, condensation and humidity
• Rodents and insects
• Oil and chemicals
• Direct burial or underground ducts
• Lightning and surge events
• Vibration and mechanical damage
• Long pulling routes

Specify outdoor-rated or indoor/outdoor cable, water blocking, armour, UV resistance, jacket material, operating temperature, bend radius and pulling tension. Use properly designed surge protection and grounding. Fibre is often preferred between buildings because it provides electrical isolation, but metallic armour and strength members still require an engineered bonding approach.

9. Documentation and Commissioning

Submittal documents

• Security riser and topology
• Door and camera schedule
• Cable schedule with part numbers
• PoE and switch-port budget
• Voltage-drop calculations
• Fibre-count and loss budget
• Pathway and firestopping details
• Product certificates and CPR/LSZH evidence where required
• OSDP and ONVIF conformance evidence
• Outdoor and environmental ratings

Commissioning

• Verify door operation under normal, fire and power-loss states
• Confirm OSDP Secure Channel and unique key handling
• Test reader communication and tamper reporting
• Measure lock voltage at worst-case load
• Certify copper channels
• Test PoE operation at maximum device load
• Inspect camera image, frame rate, latency and analytics
• Test fibre loss and polarity
• Verify failover and redundant paths
• Save as-built routes, addressing and configuration

Common Planning Errors

• Using one generic “access-control cable” for reader, lock and monitoring circuits
• Installing OSDP devices but leaving Secure Channel disabled
• Ignoring lock voltage drop and inrush current
• Treating camera wattage as the complete PoE budget
• Using copper between buildings without surge and grounding analysis
• Selecting category cable without checking conductor material or PoE temperature
• Trusting an ONVIF logo without verifying the exact registered product
• Putting all critical security links in one pathway
• Omitting spare fibres, switch ports and rack capacity
• Failing to coordinate locks with fire alarm and egress requirements

How ZION Can Support the Campus

ZION can coordinate access-control, RS-485, security, CCTV coaxial, Cat6/Cat6A, indoor/outdoor fibre, armoured cable, ODF, patch panels, closures, patch cords and related connectivity against one approved campus schedule. Product-specific OSDP suitability, CPR class, fire performance, outdoor rating and third-party approvals must be confirmed for the exact offered item.

Related ZION Resources

FAQ