By now, you have seen doors, alarms, and cameras behave like small computers on your network in Part One, and how access control data can support comfort, safety, and smarter use of space in Part Two. We also explored the governance habits that prevent small issues from becoming major incidents in Part Three.
In this part, we focus on one of Gallagher’s real strengths: turning that collection of smart devices into a coherent security integration architecture, with Command Centre as the hub that brings your wider systems together.
Less “new gadget”, more “how do we make all this stuff work as one”.
This part is designed for CIOs and IT leaders who want a practical and strategic view of access control integration, how Command Centre fits into your enterprise ecosystem, and which systems should be connected first. Treat this like a CIO guide to physical security integration with Command Centre.
We will look at five common access control integration areas:
- Video and CCTV
- Visitor and contractor management
- Building management systems
- Perimeter fencing
- Open interfaces and REST APIs
Along the way, we will pull in real examples from Gallagher sites and finish with a simple integration roadmap you can take into your next project or review.
Key takeaways
- Command Centre works best as the hub that ties your security and business systems together
- The highest-value integrations are video, visitors, building management, perimeter, and open APIs
- Decide what should connect based on real stories, not just what can connect
- Give every integration a named owner and a clear system of record for master data
Video and CCTV Integration: Using doors and cameras as one system
CCTV is often the first security system integration people think about. The goal is simple: When something happens at the door, the right video should appear immediately, without someone hunting through a wall of camera feeds.
What the integration does
Gallagher provides integrations between Command Centre and a long list of video management systems (VMS), so operators can:
- View live and recorded video inside the Command Centre client
- Automatically display the relevant camera view when an alarm or event occurs
- Control pan, tilt, and zoom from the same interface
- Jump straight to recorded clips linked to an event
From a physical security integration point of view, this is classic VMS integration: access control events tell you what happened, and cameras show you exactly how.
The benefit for your teams is a single view of what is happening. They do not have to juggle between an access screen and a separate video application while trying to respond to an alarm.
Where it is used
You see this pattern everywhere, from corporate offices and universities to critical infrastructure:
- Operations teams use Command Centre as their main screen and bring in video views as needed
- Security control rooms use the VMS wall for big-picture monitoring and Command Centre for detailed actions and audit
Either way, the operator experience is “one incident, one workflow” rather than “three systems and a headache”.
Questions for CIOs and IT
When you look at video management system integration, consider:
- Which VMS platforms are strategic
- Where operators should spend most of their time: in the VMS, in Command Centre, or in both
- How to align permissions and audit across both systems
- Where the system of record is for camera locations and naming
The technology can usually integrate. Your real task is deciding how you want to operate day to day and where master data lives.
Visitor and Contractor Management Integration: Creating a smooth front-door experience
Reception is where technology, people, and patience meet. Done badly, you get queues, lost visitors, and manual sign-in books. Done well, visitor access feels simple and secure.
What the integration does
- Visitors can be pre-registered before they arrive
- Hosts receive clear notifications when guests check in
- Temporary cards or mobile credentials can be issued with the right access
- Health and safety steps, such as inductions and acknowledgments, are recorded
- Visitor and contractor details and access permissions sit alongside employee data in the same access control system
This is visitor management integration in practice: the front desk, the access system, and your records all telling the same story.
Where it is used
In real environments:
- Corporate buildings use Command Centre to guide guests smoothly through shared spaces while keeping tight control of who can reach sensitive areas, such as data rooms
- Campuses and flexible offices customize visitor workflows on top of Command Centre, so tenants and departments can welcome guests in their own way while still capturing essential audit information
- Construction sites use a sign-in kiosk for contractors that enables further site access on sign-in and enforces health and safety policies at the boundary of hazardous areas
From your point of view, the important idea is that visitor data is not scattered across sign-in books, spreadsheets, and separate badge printers. It sits in the same access control integration platform as your employee and contractor data.
Questions for CIOs and IT
For visitor management integration, consider:
- Where visitor identity and history should live
- How long visitor data is kept for privacy and compliance
- Whether pre-registration should integrate with your email and calendar platforms
- How visitor and host notifications fit into your standard messaging tools
This integration provides a clean foundation for later topics covered in Part Five of this series, such as safety, competencies, tag boards, and broadcast notifications.
Building Management System Integration: Linking comfort, energy, and security together
Heating, cooling, and lighting used to sit in a different world from access control. Today, many Gallagher sites use building management system (BMS) integration to match comfort settings to real occupancy.
What the integration does
Command Centre can integrate with building management systems (BMS), so that:
- Areas only go into comfort mode when people are actually present
- Lights and HVAC can be turned down or off when areas are empty
- Simple rules match energy use to real occupancy instead of fixed schedules
This is building management system integration for access control data: using live knowledge of who is in the building to drive comfort and energy decisions.
Where it is used
A well-known example is at St Peter’s School in Cambridge, where Command Centre acts as the hub for building and access control workflows. Access events and schedules drive how buildings open, which areas are lit or conditioned, and how different parts of the campus respond out of hours.
Read the case study: St Peter’s School Case Study
The same pattern appears in offices and campuses. One platform knows when areas are occupied. The BMS applies comfort rules accordingly. You avoid a mess of separate timers and overrides dotted around the building.
Questions for CIOs and IT
When you look at BMS integration, consider:
- Which system is the master for locations, zones, and schedules
- How access control events feed into building automation without creating a tangle of point-to-point scripts
- How to test and monitor comfort rules so they do not fight with local controls
- Which team owns the integration: facilities, IT, or both
In short, your BMS integration should look like any other part of your integration architecture: clear masters, simple flows, and no mystery spreadsheets in the middle.
Perimeter Fencing Integration: Joining the outer ring with the inner platform
Gallagher’s smart pulse fencing is well known in high-security and critical infrastructure environments. Its true value appears when perimeter events connect directly into Command Centre alongside your doors and alarms.
What the integration does
In many sites, fence controllers send events into Command Centre, so operators can:
- See live fence voltages and alarm states on site plans
- Link fence alarms to nearby cameras for instant visual checks
- Trigger macros that lock internal doors or guide guards to the right gate
- Include fence events in the same audit trail as internal access events
From an integration point of view, perimeter security integration is another event stream feeding Command Centre. The fence becomes an intelligent sensor in the wider physical security platform, not a separate world.
Where it is used
Critical sites show this working in the real world:
- Substations and utilities use fence and gate events to drive guard responses, with a single audit trail of both fence events and internal access events
- Prisons and zoological parks combine perimeter alarms, camera presets, and internal door controls to keep people and animals where they should be
Read the case study: Balasaheb Thackeray Gorewada International Zoological Park Case Study
The pattern is the same everywhere. Treat the perimeter as part of the same command-and-control fabric, not as an isolated system with its own screens and habits.
Questions for CIOs and IT
On the perimeter side, consider:
- How perimeter devices are connected and segmented on the network
- How perimeter events appear in Command Centre and whether they trigger the right internal actions
- Which system is the master for perimeter zones and naming
- How you will test and report on fence and perimeter health as part of normal operations
Perimeter security integration should look and feel like any other security system integration: one operator story, not three.
Open Interfaces and REST APIs: The glue that connects your wider estate
Not every system you care about has a Gallagher logo on it. That is where open APIs and server-based interfaces come in.
Gallagher provides a set of server-based interfaces and REST APIs so that other systems can share data with Command Centre. For your integration architecture, these are the tools that make clean, repeatable access control integration possible.
What the integration does
- Cardholder APIs create, update, and remove people from Command Centre using systems such as HR, student enrollment, or contractor databases
- Status APIs let other applications ask Command Centre for the current state of doors, areas, and alarms, so you can overlay this on dashboards or building management screens
- Inbound event APIs let third-party systems send events into Command Centre, so operators can see everything in one place, show instructions on site plans, and build a single audit trail
- Override APIs allow third-party systems to push through commands to open doors, arm or disarm zones, or switch relays
In practice, these interfaces are used to connect systems such as HR, CRM, student management, visitor tools, parking, lift control, room booking, building platforms, and tenant portals, so that people and space data stay in step without constant re-typing.
These are the tools that create reliable, repeatable access control integration patterns.
This is where phrases like “Gallagher Command Centre integration” and “security system integration” really mean something practical: less copying and pasting, and more systems quietly agreeing on who people are and where they can go.
Where it is used
Examples include:
- In schools, integrating the school’s student management system with Command Centre means that when a student’s enrollment details change, their access in Command Centre updates automatically, saving time and reducing errors
- In multi-tenant and commercial buildings, Command Centre integrates with lift and room-booking systems so that tenants can go from the street to their floor and booked rooms with a single credential, while landlords keep a clear audit trail
For you, REST APIs and server interfaces are simply the tools that let you avoid re-typing the same data into five different systems.
Questions for CIOs and IT
When you sit down with architects and integrators, ask:
- Which systems are masters for people, locations, and roles
- Where changes should originate, for example in HR or in a contractor portal
- How often data should sync, and how failures are monitored
- Where you need command-level integration (such as unlocking doors) versus data-only integration
The goal is a small set of well-understood patterns, not a forest of one-off scripts that only one consultant understands.
Your Role as CIO: Decide What Should Talk, Not Just What Can
Modern platforms like Command Centre can integrate with a huge number of things. The real question is not whether an integration is possible, but whether it is valuable.
A practical way to approach your access control integration strategy is:
Start with a story, not a product
For example: “When a critical alarm occurs, we want the right camera view and a simple set of actions on one screen.”
List the systems involved
Access control, video, building management, visitor tools, HR, student management, contractor portals, and others.
Decide where the truth lives
Define which systems are masters for people, locations, schedules, and competencies.
Use Command Centre and its interfaces as the hub
Pull master data from the systems of record. Push access and alarm events out where others need them.
Keep ownership clear
Make sure each integration has a named owner on both sides and a simple support plan.
You do not need to connect everything. A few well-chosen integrations that start from real stories will bring far more value than a giant tangle of connections.
A Simple Physical Security Integration Roadmap
If you are planning a new Gallagher deployment or reviewing an existing one, try this short exercise as a mini roadmap.
Step 1: Map people and space masters
List your current systems that already know about people and spaces: HR, student management, contractor portals, room booking, building management, video, and payroll. Mark which ones are the master data sources for each of the following: people, locations, roles, and departments.
Step 2: Decide which systems feed Command Centre and which listen to it
Mark which systems should feed data into Command Centre, and which ones should receive data or events from it.
For each, note whether you will use a standard REST API, a server interface, or a cloud integration pattern. Gallagher has a wide range of Technology Partners that have developed their own integrations to Command Centre. You can explore our integrations here.
Step 3: Pick one high-value use case per area
Choose scenarios for each integration. For example:
- Video: when alarm X occurs, operators see camera Y automatically
- Visitors: pre-registered visitors walk straight to a kiosk, and hosts are alerted automatically
- Building management: after 19:00, only occupied areas stay in comfort mode
- Perimeter: fence-zone alarms trigger nearby cameras and lock inner doors
Step 4: Work with your integrator or Gallagher Channel Partner
Ask your integrator or Gallagher Channel Partner to map which interfaces or APIs support those use cases.
Confirm how identity, roles, and locations will stay in step across systems.
Step 5: Measure outcomes, not just connections
Agree on simple measures of success, such as “time saved at reception”, “seconds shaved off alarm response”, or “energy use out of hours reduced”.
Capture the before and after in one slide so you can show a clear story to your steering group or board. That keeps the project focused on outcomes, not just connectors, and gives you a security system integration roadmap you can explain in plain language.
What Comes Next
You now have a clearer picture of how Gallagher’s Command Centre sits as the hub of physical security integration for video, visitors, buildings, perimeters, and business systems.
In the next part, we will bring health and safety into the frame and look at how access control data, tag boards, competencies, and broadcast notifications turn your access system into a core part of your wider safety, compliance, and data landscape.