User Documentation
User Documentation
Breadcrumbs

Requirements

General prerequisites

  • The PACS must be registered within HID Integration Service via the PACS registration endpoint.

  • You need an Agent Technical Account with AgentInstance role to be able to connect the agent to HIS.

  • You need to download the agent for your PACS system.

Agent X PACS Compatibility matrix

PACS system name

PACS system version

Agent Compatibility

Avigilon Alta

Cloud service
(tested 4/2026)

HIS Avigilon Alta Agent version 1.0

Avigilon Unity Access

7.6

Unity Access Agent version 1.0

C•CURE 9000

3.0, 3.1

CCure Agent version 1.0

DSX

6.1

HIS DSX Agent version 1.0

Genetec Security Center

5.12, 5.13

Genetec Agent version
1.0 - 1.3

Hirsch Velocity

3.8

HIS Hirsch Velocity Agent version 1.0

Honeywell ProWatch

6.5

Honeywell ProWatch version 1.0

LenelS2 NetBox

5.6, 6.2

HIS LenelS2 NetBox Agent version 1.0

LenelS2 OnGuard

8.2, 8.3

Lenel Agent version 1.0, 1.1

Nedap AEOS

2024.2.4

HIS Nedap AEOS Agent version 1.0

PACOM GMS

4.60

HIS PACOM GMS Agent version 1.0

RS2 Access It!

11.2, 12.0

RS2 Access It! version 1.0

Schneider Security

4.3

HIS Schneider Security Agent version 1.0

Siemens SiPass integrated

3.0

HIS Siemens SiPass integrated Agent version 1.0

How to download a Docker image of an agent

Please use user portal as part of your onboarding to obtain docker image of your agents.

System requirements

  • HIS agents are distributed as Docker images, which are intended to be run on the customer's on-prem environment.

  • HIS agents require network access to the HID Integration Service and to the HID Authentication Service.

  • HIS agents require local network access to manage the PACS system.

  • HIS agents require a local administrator account on the managed PACS system.

  • A configuration with 2 CPUs, 2 GB of RAM, and 10 GB of storage should be sufficient for most cases.

HID Integration Service addresses