Security System Integration
Integration is the work of making systems talk that were never designed to talk to each other. A video platform, an access controller, an intrusion panel, an intercom and an employee directory each arrived from a different manufacturer with a different data model, and none owe the others an explanation. 24/7 Security designs and maintains those connections for commercial facilities across the Central U.S.
The boundary of this page
Choosing a strike or a maglock for an opening is electronic door hardware. The visitor conversation and remote release at a lobby door is intercom and entry. Operator duty cycle, loops and vehicle queueing at a driveway is gate and vehicle access. A system already installed and simply failing is service and repair. This page starts where those end: the individual systems work, and the problem is that they work separately.
Four ways two systems get joined
- Native connector. Both manufacturers ship and support the link. Least effort, least flexibility, and the version pairing is theirs to define.
- Published API or webhook. One system pushes events or answers queries over HTTP. Flexible and inspectable, but you now own a credential, a retry policy and a schema that can change beneath you.
- Middleware. A translation service normalizes events between platforms that will never speak directly. Capable, and the piece most likely to become a dependency nobody can explain later.
- Dry contact. A relay closes and an input reads it. Crude, carries almost no information, and survives firmware updates that break everything above it.
Standards that reduce custom work
ONVIF splits its work into profiles worth naming precisely: Profile T for current video streaming, Profile G for recording and retrieval, Profile M for metadata and analytics events, Profile A for access control configuration such as credentials and schedules, Profile C for run-time door events, and Profile D for readers and peripherals. Conformance to one profile says nothing about the others, so “ONVIF compatible” on a data sheet begins a compatibility conversation rather than ending one.
At the door, OSDP carries reader traffic over two-wire RS-485 in both directions, supervises the connection so a removed or dead reader raises an alarm, and adds AES-128 encryption in Secure Channel mode. It was published internationally as IEC 60839-11-5, and SIA’s OSDP v2.2 is based on that standard. Legacy Wiegand is one-way, unsupervised and unencrypted, so credential data on a Wiegand run can be captured and replayed. Beyond those, SIP routes intercom calls, LDAP and SCIM synchronize cardholder records with a directory instead of retyping them, SAML or OIDC put operator sign-in behind the company identity provider, and SNMP reports device health to whatever already watches the network.
Where integrations fail
Almost never at the protocol. They fail at the boring edges, so those get designed deliberately.
- Time. Every device pulls from the same NTP source. A recorder and a controller a few seconds apart hand an investigator video that does not line up with the badge read.
- Ordering and buffering. An access-granted event and its video arrive at different speeds, so pre-roll and post-roll are set to contain the event, not begin after it.
- Event volume. One stuck door contact can emit thousands of state changes. Rate limits and deduplication are decided before that happens, not after an operator queue fills.
- Credentials and versions. Service accounts and the firmware each side was validated against get written down, because an unannounced update is the most common way a working integration goes quiet.
- Failure containment. If the middleware stops, doors still unlock, cameras still record and the panel still reports. Integration adds capability on top of systems that stand alone; it must never become what they depend on.
Central U.S. conditions that change the design
Storm-season outages across the plains do more than interrupt power. They restart a facility’s systems in an unpredictable order, so integrations here reconnect on their own and resynchronize missed events rather than wait to be noticed. Multi-building sites in the Chicago and Illinois industrial corridor and across Indiana logistics campuses depend on a link between buildings, so anything crossing that link queues locally and catches up instead of discarding data while it is down.
Bring us the seam
Send the platforms involved, their versions, and the outcome you want an operator to reach. Call (888) 360-0035 or write to 6201 Fairview Rd, Charlotte NC 28210. A longer look at designing around operator decisions rather than available APIs is on our integrated security event workflows page.