WinGuard connects video, access control, fire detection, intrusion, intercom, perimeter, building services, alerting and IT in one interface. Here you can see how the connection works, which subsystems are included, which integrations manufacturers document publicly and what we check before every connection.
01 Technology
Every system needs an interface driver, called an adapter in WinGuard. It translates the manufacturer’s protocol into data points with a state, which WinGuard shows on the floor plan and handles by priority.
For custom extensions, the Advancis Open Platform (AOP) offers open programming interfaces. Advancis, system partners and external developers use the same interfaces, SDKs and platform services. This means extensions can also be created independently of Advancis, on the same architecture (according to Advancis, 2026). Follow the path of a message step by step →
02 Subsystems
Which messages come from which system and what WinGuard does with them.
When a message comes in, WinGuard switches to the assigned camera: live view, camera views, PTZ control and archive access, provided the video system offers these functions.
Typical: camera assignment, live view, PTZ, archive, video analytics event
Door states and access events appear with location, time and camera image. Depending on the system and permissions, doors can be controlled directly from WinGuard.
Typical: door open or forced, access denied, door state
Fire alarms are located down to the individual detector and linked to response procedures. The fire detection system keeps its statutory protective function.
Typical: alarm, pre-alarm, fault, disablement, detector zone
Alarms and set and unset states are assigned to areas. Video and stored procedures help with verification.
Typical: alarm, tamper, set and unset, area state
Calls from intercom stations appear with their location and camera image. Door or barrier can be operated in the same procedure.
Typical: call, emergency call, call status
Detections at the fence or site boundary are assigned to the section and linked to its cameras.
Typical: fence detection, section, radar and analytics, tamper
Messages from ventilation, heating, lifts or energy come together with the security situation and go to the responsible team.
Typical: fault, threshold, plant status, maintenance message
Announcements, notifications and escalations reach the responsible people, acknowledgements flow back into the event.
Typical: notification, escalation, acknowledgement, announcement
Through IT interfaces and open standards, the status of networks, servers and applications flows into the situational overview.
Typical: network status, server status, SNMP, OPC, API
The connection to dispatch or ticketing systems hands events over for further processing and brings responses back.
Typical: ticket, dispatch, status, response
Logged messages and operator actions are the basis for reports, audits and improving procedures.
Typical: event log, operator action, handling time, export
03 Manufacturers
A selection of manufacturers who publicly describe their integration with WinGuard themselves. The list is deliberately not complete: Advancis has drivers for many more systems.
| Manufacturer and system | Subsystem | Source |
|---|---|---|
| Milestone XProtect | Video | Milestone Technology Partner Finder ↗ |
| MOBOTIX | Video | MOBOTIX Partner Society ↗ |
| dormakaba | Access | dormakaba technology partners ↗ |
| Gallagher | Access | Gallagher integration ↗ |
| LenelS2 (Honeywell) | Access | LenelS2 OAAP partner ↗ |
| C•CURE 9000 (Johnson Controls) | Access | Compatibility matrix data sheet ↗ |
| Commend | Intercom | Commend Integration Zone ↗ |
| 2N IP-Intercom | Intercom | 2N Wiki ↗ |
Sources: manufacturers’ integration pages, retrieved in October 2026. Usable functions depend on version, driver and licence.
04 Before connecting
An existing driver does not yet confirm every function you want. That is why we clarify these points before we promise anything.
Drivers are tied to systems and versions. We match your systems against the available WinGuard drivers.
Which states does your team need, which commands should be possible from WinGuard? Not every adapter can control.
The number of connections depends on the edition: up to 3 with Express, up to 5 with Basic, up to 15 with Professional, unlimited with Enterprise (as of 03/2023).
Network or serial, availability, behaviour if the connection fails: this determines hardware, network planning and alerting.
Every detector, every door and every camera is assigned to a location on the plan. For this, we prepare your CAD drawings.
We test every connection with real messages against agreed criteria before operation begins.
Questions
According to Advancis, more than 550 interface drivers for systems from well-known manufacturers are available (as of October 2025). In addition, there are open standards such as OPC and the programming interface of the Advancis Open Platform.
Yes. Milestone lists WinGuard as an integration in its Technology Partner Finder. We check in advance which XProtect version works with your WinGuard version and which functions can be used.
Then there are several options: open standards such as OPC, the programming interface of the Advancis Open Platform or a request to Advancis for a new driver. What makes sense, we clarify based on effort and benefit.
The editions limit the number of connections: Express up to 3, Basic up to 5, Professional up to 15, Enterprise unlimited (licence model according to the WinGuard X5 manual, as of 03/2023). Data point units also count.
With an adapter that can control, yes, for example open a door, lock down an area or pan a camera. Which commands are possible depends on the adapter, the version and the operator rights.
The next step
Tell us the manufacturer and version of your systems. We check the connection and tell you which messages and commands are possible.