PACOM GMS (Graphical Monitoring System)
PACOM Systems·AE_HSc_PacomGMSConnectorGuide
Overview
The PACOM GMS connector integrates AlertEnterprise Guardian with PACOM Graphical Monitoring System — PACOM Systems' established enterprise PACS, widely deployed in banking, government, and critical infrastructure verticals (especially in APAC and EMEA markets). This is the legacy SOAP-based integration path; for PACOM's newer cloud-native VigilCore platform, see pacom-vigilcore-rest.
The architecture has a mandatory Windows / .NET / IIS intermediary: the AE-side connector calls an Alert GMS Agent — a SOAP/WCF web service built on top of PACOM's GMS .NET SDK. The Agent must be deployed on Windows Server with .NET Framework 4.0+, IIS 8.0+, and a specific set of IIS Application Development features (ASP, ASP.NET, .NET Extensibility, ISAPI Extensions, ISAPI Filters, Basic/Windows/Digest Authentication, Static Content Compression, IIS 6 Management Console). The Agent can be co-located with the PACOM GMS server or run on a separate Windows host.
Notable PACS terminology / capabilities: PACOM models access via two parallel hierarchies — Global Access Groups (GAG) for area-based access and Floor Access Groups (FAG) for elevator/floor-based access — and supports both permanent and temporary variants of each. The connector exposes Add Temporary Badge as a discrete operation (assigning a temporary card linked to another user's primary card) — useful for visitor-borrowed-badge workflows.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
1 method supported
Authentication uses basic auth credentials configured in the AE connector and forwarded by the Alert GMS Agent's SOAP/WCF service to PACOM's GMS .NET SDK. SSL is enabled via IIS-bound certificates on the Agent host.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
Windows Server with .NET 4.0+ and IIS 8.0+ for the Alert GMS Agent
aeThe Alert GMS Agent — the .NET WCF intermediary that wraps PACOM's GMS SDK — must be deployed on a Windows Server with .NET Framework 4.0 or higher and IIS 8.0 or above. The IIS installation must include Application Development (Static Content, Default Document, Directory Browsing, HTTP Errors, ASP, ASP.NET, .NET Extensibility, ISAPI Extensions, ISAPI Filters), Health/Diagnostics (HTTP Logging, Request Monitor), Security (Basic/Windows/Digest Authentication, Request Filtering), Performance (Static Content Compression), and Management Tools (IIS 6 Management Console + Scripts + Compatibility).
PACOM GMS deployment with SDK access
customerAn operational PACOM GMS deployment with the GMS .NET SDK reachable from the Alert GMS Agent host. The Agent can be co-located with the GMS server or remote — both topologies are documented as supported.
AE GMS Connector Agent installer (ALNTGMSWS) deployed
aeCopy the contents of the ALNTGMSWS folder from the ALNTGMSConnector build to the target directory on the Agent host. Update the web.config to set a valid Windows folder path for log file generation (must have appropriate write permissions).
Known limitations
Documented constraints to set customer expectations before deployment.
Windows-only intermediary
importantThe Alert GMS Agent is Windows-only. Customers running fully Linux-based AE deployments must still provision a Windows Server for the Agent. This is a hard constraint of PACOM's GMS SDK, not an AE-side limitation.
Two access-group hierarchies must be reconciled separately
informationalPACOM's GAG (Global Access Group) and FAG (Floor Access Group) are parallel hierarchies. Customers expecting a single unified access-level abstraction must understand that user role mappings span both — and that the temporary variants of each must be handled distinctly from the permanent ones.
PACS specifics
PACOM models a User with one or more Cards. Each user has a designated Primary Card; additional cards are Linked Cards. Temporary Cards can be issued and linked back to another user's primary card — supporting visitor / borrowed-badge workflows where the temporary card carries access derived from a host user's permissions.
Access is granted via Global Access Groups (GAG) for area access and Floor Access Groups (FAG) for elevator/floor access. Both group types have Permanent and Temporary variants. A user's card may carry any combination — GAG-permanent, GAG-temporary, FAG-permanent, FAG-temporary.
Single PACOM GMS instance per AE→GMS Connector. Multi-site customers running federated GMS deployments require one connector + one Agent per GMS instance.
- Topology
- on-prem
- Event model
- polling
- Anti-passback
- unknown
- Holiday schedules
- unknown
- src/connectors/pacom-gms/source.pdf — Full connector guide — 30 pages, updated 2025-05-23
- src/connectors/pacom-gms/source.pdf — p5 — Supported Version
- src/connectors/pacom-gms/source.pdf — p7 — Connector Architecture