NERSA • Pennsylvania & Mid-Atlantic

Access Control and Intercom Network Dependencies

Document which door and visitor functions depend on connectivity—and which remain local.

Separate control from communication

Controllers, readers, management software and intercoms may have different network dependencies. Record where credentials, schedules and events are stored, how updates reach controllers, and what functions require a server or cloud connection.

Verify offline behavior

Do not assume every door stops working when a network link fails or that every controller works independently. Check the selected system’s documented offline behavior, event buffering and recovery. Network failure is also different from loss of power at the controller or locking hardware.

Intercoms and visitor workflows

Identify call destinations, network services, audio/video requirements and any remote-release integration. Test the actual visitor workflow from the entrance through the answering station. A reachable IP address does not prove intelligible audio or correct door-release authorization.

Safety and authority

Emergency egress, door hardware, fire-alarm interaction and gate safety are separate design responsibilities. Fiber connectivity does not establish their compliance. Coordinate changes with the owner and the qualified parties responsible for those systems.

Commissioning checklist

• Confirm authorized credential changes reach the intended controllers.
• Verify event reporting and time accuracy.
• Test documented communication-loss behavior in an approved window.
• Confirm recovery and buffered-event handling where supported.
• Record administrator ownership and support responsibilities.