The right questions before the next step.

A concise overview of WinGuard, integration and operation. Scroll on: thirteen terms build up into a map that shows how everything fits together.

To the explanations →Glossary A–Z

01 Technical background

Knowledge for your WinGuard project.

Technical decisions start with a clear idea of what the system should do. Five questions we clarify in almost every project.

What is a PSIM, and where does WinGuard fit?

PSIM stands for Physical Security Information Management, in German-speaking countries usually called a “Gefahrenmanagementsystem” (GMS). It means a higher-level layer that brings together information from physical security systems. With WinGuard, depending on the integration, building, communication and IT systems also form part of the overall picture.

What matters is not the number of connections, but how information comes together for handling an event.

In short: a PSIM brings things together. WinGuard is a PSIM that looks beyond security technology.In detail: what is a PSIM? →

What needs to be clarified before integrating an interface?

Manufacturer and product name are not enough as a basis. What matters is the version in use, the available driver, the required messages and operating functions, licensing and the behaviour if the connection fails.

This results in verifiable requirements against which the integration can be measured.

In short: version, driver, messages, commands, licence, fault behaviour.

Why does a migration need a fallback concept?

A changeover alters a defined starting state. Beforehand, it must be clear which components are backed up, how long a changeover may take and under which conditions you go back.

The fallback procedure is part of the preparation and is assessed for the specific system.

In short: the way back is planned before the first step is taken.In detail: migration to WinGuard X5 →

What does redundancy achieve, and what else needs to be planned?

A standby system can cover part of the possible failures. Network, power supply, data storage, interfaces and organisational procedures have their own dependencies.

That is why the required availability is secured by an overall concept and suitable tests.

In short: Hot Standby protects the server. The rest needs its own answers.

What belongs in a good response procedure?

For each event, an operator needs understandable information and clearly assigned steps. Responsibilities, decision paths and documentation must match the actual organisation.

A procedure for a real security system is defined and approved by the responsible specialists.

In short: understandable, unambiguous, suited to the organisation, approved.

02 Glossary

Terms from A to Z.

Briefly defined, to look up and quote. Information on licences and modules according to the WinGuard X5 manual, as of 03/2023.

Adapter Integration: Software component that connects a system such as a fire alarm control panel, access control or video system to WinGuard. Manufacturer-specific or via standards such as OPC. Depending on the adapter, only messages are received or commands are sent as well.
AIM Identities: Advanced Identity Manager by Advancis. Keeps identities, group rights and badge data in sync across several access control systems.
AOP Platform: Advancis Open Platform: the system architecture of WinGuard X5. An open application programming interface (API) allows extensions, adapters and custom interface components to be connected.
CAD Support Floor plans: WinGuard module for DWG, DXF and DGN drawings: display, import, control layers. CAD Support plus also links detectors automatically.
Data point Basics: A single element with a state, for example a detector, a door or a camera. When its state changes, an event can be created.
Data point unit (DPU) Licensing: Licence unit in WinGuard. Each data point uses the units of its highest-weighted function: camera 8, door 4, analogue value 2, all others 1. Structural points without a link do not count.
Edition Licensing: Base system of WinGuard: Express, Basic, Professional or Enterprise. Determines, among other things, data point units, connections, workstations and redundancy.
Event Basics: Created when a data point changes its state, for example on alarm, fault or maintenance. WinGuard presents it for handling with priority, location and response procedure.
Event report Documentation: PDF document with header, details, log, operator commands and graphics for an event. Created manually or automatically.
Event Routing Operation: Rules that determine which workstation receives which event, for example depending on time of day or site.
Floor plan Floor plans: Graphic that shows where a data point is: site, building, floor, area. Often prepared from existing CAD drawings.
Guided Operation Operation: Guided operation: the right information and prepared steps are ready for each event. What is necessary and what may be triggered is defined in the project.
Hot Standby Availability: Additional server that continuously synchronises with the main server and takes over with the same functions if it fails. Up to two per system, from Professional.
Interface server Availability: Server that bundles device connections and so relieves the main server. Up to ten connections per interface server.
Location server Availability: Local server in a distributed system. Keeps workstations and interfaces on site running if the connection to the main server fails. Enterprise edition.
Log Documentation: Record of messages and operator actions with a time stamp. Basis for traceability and the event report.
Lone worker monitoring Operation: The operator confirms their presence within defined time windows. If the confirmation does not come, an alarm is raised.
Mobile credential Identities: Access right on the smartphone instead of on a card, for example via the AIM app at compatible readers.
OPC Integration: Open industrial standard for data exchange between systems. WinGuard can connect systems via OPC when no manufacturer-specific adapter is needed.
Operator workstation Operation: Workplace at which events are handled. How many workstations are possible depends on the edition.
PIAM Identities: Physical Identity and Access Management: management of identities and access rights across several access control systems. AIM is such a solution.
Priority Operation: Number from −1 to 999 that determines how important an event is. Preset levels run from Alarm 7 to Maintenance 1. Priority 0 does not open automatically, −1 creates no event.
PSIM Basics: Physical Security Information Management: higher-level software that integrates several security systems and makes them operable through a common interface. WinGuard is a PSIM.
Response procedure Operation: Predefined steps for handling an event, with decision paths and mandatory entries. Defined and approved by the responsible specialists.
Security management system Basics: Term used for a PSIM: higher-level software that brings together messages from fire, intrusion, access control, video and building systems and guides the handling of events. WinGuard by Advancis is such a system.
Subsystem Basics: Technical domain of building and security technology, for example video, access control, fire detection, intrusion detection or building automation.

Questions

Your question wasn’t here?

Ask us directly. We answer personally and, if it fits, this can become a first conversation about your system.

Ask a question →+41 78 784 68 09