VIM (Visitor Identity Management)
The visitor-oriented sister discipline to PIAM. Where piam handles employees, contractors, and other long-lived identities, VIM handles short-lived visitor identities — pre-registration, host-sponsored access, day-pass issuance, sign-in/sign-out audit trails, and automatic expiry.
AE Guardian implements VIM as a first-class capability with its own object family (Visitors, Visitor Badges, Visitor Access). Not all PACS connectors expose VIM — both Lenel OnGuard (via lenel-open-access) and Software House C·CURE 9000 (via ccure9000-victor) support PIAM + VIM through the same connector. Other PACS connectors are PIAM-only.
Why this matters: an enterprise RFP asking "can your system handle 5,000 daily visitors at a Fortune 500 lobby" needs both connector-level VIM support *and* AE Guardian-side visitor workflows (pre-registration emails, kiosk-based ID capture, host notifications). The connector list alone doesn't answer it.
What other systems call it
Per-vendor / per-standard terminology for this same concept.
| System | Term / Notes |
|---|---|
| VIM (Visitor Identity Management) — Guardian capability | |
| LELenel | VIM via Lenel OpenAccess REST (Visitor, Visitor Badge, Visitor Access objects) |
| SHSoftware House C·CURE | VIM via CCURE 9000 Victor (Visitors, Visitor Badges, Visitor Access) |
Used by 3 connectors
Connectors in the catalog that reference this concept.