Integration means a camera event, a door event or an occupancy count reaches the building management system and triggers something: lights, a schedule, an alarm, a report. It is a mapping exercise between two systems, and it succeeds or fails on the event list and the network rather than on the camera.
A camera system and a building management system can share a wall for a decade and never speak. Integration is the deliberate work of deciding which events matter, where they are processed, and what the other system does when one arrives.
This page covers what actually gets connected on a Colorado commercial property, the documentation that keeps it working, and the failure modes that surface six months after commissioning.
What integration actually connects
Most commercial buildings already run a platform for HVAC, lighting, energy and sometimes access control. Cameras join through a video management system that exposes events: motion in a zone, a line crossed, a door forced, a camera offline.
The link itself is usually one of four: dry-contact inputs and relays, a protocol gateway, an API over the network, or a shared platform where the camera vendor is a module inside the building system.
Start with the event list, not the platform
Write down every event anyone wants to act on, who receives it, and what should happen next. Ten well-chosen events beat a hundred that nobody reads, and the short list is also what the integrator can test.
- Door held open past sixty seconds at the dock.
- Person detected in the yard after the building closes.
- Camera offline for more than ten minutes.
- Occupancy count above the design load for a floor.
Who owns the time clock
Every system stamps its own events. If the cameras and the building system disagree by a few minutes, the combined record is worth less than either system alone, and an incident timeline turns into an argument about sequence.
Point both at the same time source, confirm the time zone and daylight handling, then check the offset again after a month. This is the cheapest integration work available and the most frequently skipped.
Keep the camera network separate
Cameras are appliances with firmware, and the building network runs the plant. Put video on its own segment with controlled routes to the management system, and do not let a camera reach the internet unless a specific feature needs it.
The integration should also survive a video outage. If the building stops adjusting schedules because a recorder rebooted, the design is wrong and the fault will be blamed on the cameras.
Occupancy data and its limits
A camera that counts people is a sensor, and a sensor has error. Counts drift in crowded scenes, and an entrance with a queue will undercount because two people crossing a line close together read as one.
Use counts for trend and scheduling, not for compliance or headcount reporting. If a number drives a decision with consequences attached, cross-check it against a second source before acting on it.
Commission it, then document it
Integration that is not tested is a guess. Test each event end to end, record what the building system did, and note the delay you measured. Then write it down: the event list, the address plan, the credential owner and the person to call.
The next technician will not inherit your memory. An as-built with a mapping table is the difference between a system that can be maintained and one that gets ripped out when it misbehaves.
Frequently asked questions
Do I need to replace my recorder to integrate?
Not always. Many recorders expose events over an API or dry contacts. The limits are usually the age of the firmware and whether the manufacturer documents the interface well enough to build against.
Can cameras turn the lights on?
Yes, through a relay or a gateway, and it is one of the simplest useful integrations. The catch is reliability: a trigger that misses leaves a floor dark, so pair it with a schedule as a fallback.
What happens when the network drops?
A well-designed system fails to a safe state, with local recording continuing and the building system falling back to its schedule. Decide that behavior explicitly, because the default configuration is rarely what you want.
Related:Commercial securityWhat a VMS doesAccess control systems
