How the Key2XS Mobile App Creates a Seamless Operational Layer Across CLIQ, iLOQ and the Key2XS Platform

Critical-infrastructure operators run on tight operational windows, distributed field teams, and strict compliance demands. Physical access is a core control, yet in most organisations still fragmented across mechanical keys, offline cylinders and outdated handover procedures. The Key2XS mobile app removes this fragmentation by creating a real-time operational layer that sits directly on top of ASSA ABLOY CLIQ, iLOQ and the Key2XS platform.

The result: one workflow, one identity, one audit trail, regardless of the underlying lock technology.

Unified Activation for ASSA Abloy's CLIQ and iLOQ Keys

The mobile app is built to handle both CLIQ and iLOQ ecosystems without operational overhead.

CLIQ & Protec

• Users activate or re-activate their electronic keys directly from the app.

• Rights are retrieved from the Key2XS platform and written to the key via Bluetooth or programming device.

• Daily refresh cycles, emergency rights, time-restricted rights and incident access paths are all supported.

• No dependency on local desktops or separate programming stations in the field.

iLOQ (S5 / SS10)

• The app reads the key via NFC and writes the updated access profile.

• Temporary or ad-hoc access can be granted instantly through the Key2XS rules engine.

• Multi-vendor environments e.g., CLIQ for remote sites, iLOQ for buildings, operate identically from a user perspective.

Ad-Hoc Access Rights Without Dispatch Delays

Key2XS removes the need for dispatchers or on-call engineers to manually approve access. The app ties into the platform’s policy engine:

• Users request access to a site or asset directly in the field.

• Approval flows follow the organisation’s IAM structure (manager, OT lead, contractor supervisor, etc.).

• Once approved, rights are pushed instantly to the user’s key (CLIQ or iLOQ).

• Every action is logged for NIS2/CER auditability.

This converts a process that normally takes hours into one that takes seconds.

Alarm Control Integrated Into the Access Workflow

In hybrid setups, the app becomes the single control point for key access and alarm states.

Examples:

• CLIQ key with integrated MIFARE (EV3) chip writes the PIN to iLOQ readers through the app. The MIFARE chip controls the alarm on/off setting.

• In case of managed alarm systems, such as for traffic management systems, the app disables alarms before the cylinder is opened and re-enables them automatically after a configured timeout and/or if the user left the location.

• Every alarm change is registered in Key2XS for incident reconstruction.

This removes the last manual “phone-call workflow” in physical access operations.

Lost Key Management Without Operational Downtime

Users can directly report a lost CLIQ or iLOQ key in the app.

The platform instantly:

• Revokes rights,

• Flags the key for investigation,

• Triggers operational workflows (replacement, contractor notification, compliance reporting).

No backlog, no excel sheets, no gaps in the audit chain.

Field Intelligence: Map-Based Critical Infrastructure Locator

The app receives infrastructure data from the Key2XS platform:

• Geolocation of cylinders, cabinets, bridges, tunnels, pumping stations, traffic controllers, transformer houses, etc.

• Associated risk category (per CER classification).

• Required competencies or safety instructions.

• Active access windows and audit trails.

A field engineer sees exactly where to go, what they can open, and what conditions apply, no need for local knowledge or outdated PDFs.

6. Real-Time Orchestration Through the Key2XS Platform

All app actions run through one identity-driven backend:

• IAM integrations: such as Entra ID, One Identity, Okta, SailPoint, Omada.

• Policy engine: time windows, zones, emergency access, contractor rules, CER/NIS2 requirements.

• Vendor-agnostic key and cylinder mapping for CLIQ, iLOQ, card systems and hybrid deployments.

• Full auditability: who requested, who approved, what was opened, when, and why.

This architecture makes multi-vendor landscapes feel like a single, coherent system.

7. Operational Impact

For IT:

One mobile workflow tied to IAM. No separate CLIQ or iLOQ consoles for daily operations.

For OT:

Real-time visibility of field access from tunnels to transformer houses, critical for incident response and CER compliance.

For Facilities / Contractors:

No more logistics around programming stations or key handovers. Users self-service their keys on-site.

For Compliance:

End-to-end auditability embedded into every action.

Conclusion

The Key2XS mobile app binds together what used to be operational islands: electronic keys, offline cylinders, alarm systems, and field asset data.

For operators running critical infrastructure, it replaces outdated workflows with a unified, identity-driven and fully auditable process that works transparently across CLIQ, iLOQ and any future access technology added to the Key2XS platform.