Controller Memory and Database Configuration

Overview

This guide details the Integriti Controller database entities, their IDs, on-board memory limits, and global entity status. It covers firmware V20 and later (where all Controllers support the maximum expansion capacity) as well as earlier firmware versions where Smart Card Level Licences apply.

Most database entities have a 1- to 3-character Entity ID used to quickly identify the entity type. This is particularly useful when choosing an entity in a programming option where different entity types may be selected, and when performing operations from an LCD Terminal.

Prerequisites

  • Access to the Integriti Controller
  • For firmware versions prior to V20: appropriate Smart Card Level Licence installed
  • Familiarity with the Integriti System Configuration Handbook for Data Synchronisation settings

Step-by-Step

Understanding Entity IDs

Each entity has a short ID used across the system. For example:

  • U = Users
  • Z = Zone Inputs
  • D = Doors
  • A = Cards
  • IA = Area List
  • CL = Actions Lists
  • MG = Menu Groups
  • PG = Process Groups
  • QG = Permission Groups (Q-pair groups)

When selecting an entity from a Terminal or programming option, the ID prefix helps distinguish between entity types that may share the same number space.

V20 Firmware (or Later)

From V20 firmware onwards, all Controllers support the maximum expansion capacity:

  • 250 Doors
  • 100,000 Users
  • 3,000 Inputs
  • 100,000 Events

Smart Card Level Licences were removed in V20. The Smart Card is now only used to enable a small number of high-level product features.

Firmware Versions Prior to V20

In earlier firmware versions, the number of Zone Inputs, Doors, Users, and Review Events is limited by the Smart Card Level Licence:

Permission LevelZonesDoorsUsersReview Events
No Smart Card1001620010,000
Level One200402,00020,000
Level Two6008010,00030,000
Level Three2,00016065,00060,000
Level Four3,000240100,000100,000

Note: LAN Module counts are not limited by Smart Card licensing, but the number of Zone Inputs and Doors allowed will affect how many LAN Expansion Modules can effectively be utilized.

Entity Maximums Table (V20+)

Entity DescriptionIDMaximumGlobal
Actions listsCL250Yes
Analogue CalibrationsAC4No
Area listIA250Yes
Automation Point (BMS)AP250Yes
Auxiliary ListAL10,000Yes
CardsA250Yes
Card TemplatesAU128Yes
Comparisons (Compare entities)XL1,000No
DNS names250No
Door typesStored in user recordYes
EOL configurationsCF128Yes
FloorsTM250Yes
General TimersCT10Yes
HolidaysCP250No
LAN ModulesCE250Yes
— Max. of any one typeDS32Yes
LCD message250No
Lift GroupsDL10,000No
Lift typesDT250No
LockersD250No
Locker BanksLK1,000No
Macro linesEL8No
Menu groupsMG1000Yes
Named actionsPA500No
Network interface cardNIC24No
Offline accessFE250No
Process groupsPG250Yes
Permission Groups (Q-pair)QG25,000Yes
Qualified door typesQD250Yes
Qualified lift typesQL250Yes
RF remote templatesFT250Yes
SchedulesSK1,000Yes
Telephone number listsTL250No
Telephone numbersTN1,000No
Time PeriodsTP1,000Yes
UsersU100,000Yes
Zone InputsZ3,000No

LAN Module Types (8 types): LCD Terminal (T), Graphic Terminal (G), Expander (E), Radio Expander (F), Reader (R), Intelligent Reader (I), LAN Power Supply (P), Virtual Module (V).

User Database Expansion

Users can be expanded beyond the 100,000 limit using:

  • AURM (Automatic User Record Management) — Used with Integriti Pro, Business, or Corporate editions for dynamic on-board database updates. Supports 1,000,000+ users.
  • Level 5 User Expansion Kit — Local hardware expansion providing an expanded user database on the Controller itself.

Note: The maximum number of User records is reduced if extended User data is assigned (more than 1 Card, 1 RF Remote, 8 Permissions, or 8 User Qualifications per user).

Global Entities

Many entities are global entities — common across all Controllers in a multi-Controller system. The Integriti Pro software handles these in one of two ways:

  1. Exact copy maintained in every Controller — e.g., Menu Groups, Process Groups, Door Types, Time Periods, Holidays, Card Formats & Templates, Calibrations. (Users and Permission Groups without individual-entity permissions also fall here.)

  2. Copy created per Controller with Controller-specific permissions — e.g., Lists (Area/Door/Lift Car/Floor/Auxiliary), and Users/Permission Groups with individual-entity permissions.

For global entities, the Maximum records value is the maximum for the whole system as well as for each individual Controller.

Recommendation: In multi-controller sites, perform all programming in the Integriti Pro software, not from a Terminal or Integriti CS software. When incorporating an existing Controller into a multi-controller site, plan carefully to ensure global entities that need to be retained are not overwritten.

Further Expansion

When entity counts exceed a single Controller’s limits (Areas, Doors, Lift Cars, Zone Inputs, Lockers, etc.), add one or more additional Controllers. Integriti Pro, Business, or Corporate editions provide seamless multi-Controller integration.

Verification

  1. In Integriti System Designer, right-click the Controller and verify the serial number and firmware version under Panel Information.
  2. Check entity counts in the relevant system lists (Users, Doors, Inputs) against the maximums above.
  3. For multi-controller systems, verify Data Sync Mode settings under Connection Details → Synchronisation.

Troubleshooting

IssueResolution
Cannot add more Users/Door/Inputs beyond limitCheck Smart Card Level (pre-V20) or consider AURM / Level 5 expansion for Users. For Doors/Inputs, add another Controller.
Entities overwritten when joining multi-controller sitePlan the integration order carefully. Use Integriti Pro software exclusively for programming in multi-controller systems.
User count lower than expectedCheck for extended user data (multiple Cards, RF Remotes, 8+ Permissions/Qualifications) which reduces effective user capacity.