When Should You Specify Enterprise Access Control Instead of a Standard Door Controller?

Enterprise access control becomes useful when governance, integration and operational scale exceed what a straightforward door-controller installation can manage comfortably. The decision is not simply a door-count threshold. NZ specifiers should compare workflows, administrative boundaries, resilience and support against the exact platforms proposed.

Identify the operational trigger

List the problems that need solving: multiple sites, separate operator teams, complex permissions, integration ownership or demanding evidence requirements. Describe how the client works today and where that process fails. A small high-risk site can need sophisticated governance, while a larger simple site may have modest administration needs. Avoid selecting an enterprise platform solely because the term sounds more secure.

Define governance and operator boundaries

Specify who can issue credentials, change schedules, view events and approve exceptions. Separate site operators from central administrators and confirm what each can see. Require an audit trail appropriate to the client's investigation needs. Test a representative delegated role rather than relying on a marketing statement. Administrative separation should be clear enough that a regional operator cannot accidentally change unrelated locations.

Specify integration as owned workflows

Turn each proposed integration into an event, action, data exchange and failure case. Examples include an approved identity update, a door event opening video or an expired contractor credential being withdrawn. Name the support owner on both sides. A list of integration logos does not demonstrate the required workflow on the proposed versions. Verify licences, API access and upgrade responsibilities before accepting it.

Assess resilience and recovery

Define the behaviour during server, network and controller failures. Distinguish local access decisions from functions requiring central services. Agree backup, recovery objectives and an approved restoration test. Enterprise features do not remove the need for a power and communications plan. Ask how administrators recover from a failed change and how pending credential updates reconcile after a site reconnects.

Compare specific RBH platform proposals

RBH Integra32 and Axiom configurations are distinct proposals, not interchangeable brand labels. Obtain current model, version, licence and expansion information for each shortlist. Include reader protocols, controller topology and the required management workflow. The existing Essential Security Supplies RBH platform guide provides context, while the manufacturer documentation and supplier design establish the final scope. Avoid unsupported maximum-door claims copied between editions.

Evaluate lifecycle and migration

Ask who supplies commissioning, training, updates and ongoing support in New Zealand. Include the process for migrating existing credentials and preserving necessary event records. Test a sample migration where reuse is important. Compare confirmed inclusions and dependencies without publishing unapproved costs. Select the proposal that satisfies the written requirements and has clear delivery ownership, rather than inventing an overall platform winner.

Apply the design to the actual project

Use a requirement matrix that separates essential functions from desirable ones. For each essential row, request written support evidence and a demonstration using the proposed edition. Give the supplier a realistic operator role and workflow rather than a broad instruction to show enterprise features. Mark whether the result is included, optional, dependent on another service or unverified. This makes the comparison usable for a decision and prevents a long feature list from obscuring a critical gap.

Review the client's capacity to operate the system. A platform can offer extensive control while requiring training, account governance and maintenance the client has not assigned. Identify the future administrator, the support organisation and the owner of each integration. Include a sample recovery and change-approval process in acceptance. Where migration is required, test representative credentials and permissions before the final rollout. Keep unsupported reuse assumptions separate from confirmed scope and use a phased implementation when that is needed to preserve reliable operation.

Calculate power and prove operation during outages

Make a load schedule using the manufacturer's current figures for each lock, reader, controller and accessory. Separate continuous load from momentary or motor starting load. Check what happens when several openings operate together and when batteries recharge after a mains outage. Measure voltage at the furthest device under the worst intended load, because adequate voltage at the cabinet does not prove adequate voltage at the lock. Cable resistance, protection and connection quality all affect the result.

Agree the required behaviour for mains failure, controller communication loss and loss of the management server. Test these conditions safely under the commissioning plan and record which functions remain local and which depend on a server or external service. A cached credential might remain usable while a new revocation has not yet reached the controller. Recovery therefore needs a test of restored communication and database synchronisation as well as a simple successful door opening.

Standard door controller versus enterprise access control: selection matrix

The practical distinction is less about the number of doors than the cost and risk of operating them. Use the following criteria to frame the tender, then have each supplier demonstrate the requirement using the proposed software version, controllers and licences. A capable smaller platform may fulfil many of these criteria, so treat this table as a selection aid, not a claim that every enterprise-labelled product supports each feature.

Questions to settle before approving the platform

Who owns access rights? Document the staff member or role that approves new access, changes group permissions and removes contractors. Include joiner, mover and leaver processes. Show how a location-specific administrator is restricted, and test an attempted unauthorised change.

What happens when connectivity fails? Record whether controllers can continue to decide access locally, whether a revoked credential will remain valid temporarily, and which event data is queued for later transfer. Test the exact loss-of-communication scenarios in the approved design rather than assuming all systems behave identically.

Can existing hardware be retained? Check the controller generation, reader electrical interface, credential encoding, firmware and supported migration tooling. Reusing a physical card does not necessarily mean its security characteristics or management workflow remain suitable. Document every proposed reuse decision, including items that should be replaced.

What constitutes successful handover? Require an as-built equipment schedule, backed-up configuration, administrator training, commissioning evidence, escalation contacts and a recorded restoration exercise appropriate to the project's risk. Identify who will maintain integrations when either platform is upgraded.

For related design decisions, see our RBH Integra32 versus Axiom platform guide and access control equipment range. Confirm capabilities with current RBH technical documents and the supplied licence schedule before final sign-off.

Commissioning acceptance checklist

Agree the expected result before testing. Use the installed configuration and retain evidence of each outcome, including a failure that must be corrected. The following checks supplement the exact manufacturer procedures and the approved project design.

Repeat affected checks after a material equipment, software or site change. Keep the test record with the as-built schedule so the next maintainer can understand which configuration passed and which assumptions still need review.

Equipment candidates and specification checks

These are relevant active catalogue candidates for a project review, rather than a universal recommendation or a promise of immediate stock. Use the full product page and current manufacturer information to confirm the supplied variant and its role in your design.

• RBH-AXA-PRO - RBH Axiom X Professional Security Management Software. Confirm the exact supplied configuration, relevant interfaces and installation requirements before including it in the equipment schedule.
• RBH-INT32-SOFT - Integra32Software - 64/128 Doors, Includes Web and Mobile Client. Confirm the exact supplied configuration, relevant interfaces and installation requirements before including it in the equipment schedule.
• RBH-IRC-2000 - RBH Integra32 2-Door Controller (UL Listed) includes Enclosure with 13.8VDC, 2A power supply. Confirm the exact supplied configuration, relevant interfaces and installation requirements before including it in the equipment schedule.

Review the relevant Essential Security Supplies equipment range alongside the intended workflow. For further context, read our related installer guide.

Frequently asked questions

Is enterprise access control only for large sites?

No. A smaller site with regulated areas, separate tenant operators, complex identity processes or critical integrations can justify an enterprise assessment. Define the actual operational requirements first, then compare the available platforms on demonstrated functionality and ongoing support.

Does enterprise software eliminate local controller limits?

No. Software licences do not change a controller's physical inputs, outputs or supported reader interfaces. Confirm the exact model, firmware, topology, permissible expansion and any edition-specific restrictions with the manufacturer or supplier before preparing the door schedule.

Can existing credentials always be reused?

Not always. Assess the existing card technology, reader interface, credential format, encryption or key-management requirements and the chosen platform's supported migration methods. Test a representative card and access level before committing to reuse; replace credentials that do not meet the new security requirements.

Primary references and technical scope

Use the primary manufacturer or technical reference for the claims it covers. General design guidance does not replace the selected product's installation manual. Confirm current firmware, model variants and the approved project requirements before ordering or commissioning.

Get specification help from Essential Security Supplies

Send your site layout, equipment schedule, intended workflow and any existing model details to Essential Security Supplies for specification help and a project quotation. Identify the functions that must be demonstrated and the interfaces owned by other contractors. Our enquiry route supports a documented equipment review without publishing prices or assuming unverified compatibility.