Uniqcli

UniQ platforms

UniQ Security

One access-control platform across Johnson Controls, HID, Mercury, LTS and DMP hardware — built for federal installation requirements, Navy CNIC programs and their Army and Air Force equivalents.

UniQ Security

One platform. Any provider's hardware.

Access control on a government installation usually means five incompatible head-ends — one per building era, one per vendor, none talking to each other. UniQ Security is our platform practice for unifying that: one management layer operating panels, readers and controllers from Johnson Controls, HID, Mercury Security, LTS and DMP, so the badge office manages ONE system while the hardware underneath stays competitive, replaceable and §889-screened.

Why UniQ Security

Your doors shouldn't belong to a vendor.

Every proprietary head-end is a future hostage negotiation: the panels age, the license renews, and the replacement quote assumes you can't leave. Running a provider-agnostic platform over open-controller hardware (Mercury-based lines and their peers) breaks that cycle — the platform stays, the hardware competes.

For defense and federal customers we design to the installation's actual program: Navy CNIC access-control requirements and their Army and Air Force counterparts, PIV/CAC credential flows and FICAM-aligned architectures where required — quoted line-by-line and staged like every Uniqcli delivery.

  • One management plane over JCI, HID, Mercury, LTS and DMP hardware
  • PIV/CAC-ready, FICAM-aligned where the program requires
  • §889-screened components, TAA country-of-origin confirmed
  • Migrate panel-by-panel — no forklift rip-out
Badge card being presented to an access-control reader.
Badge card being presented to an access-control reader.
The platform

UniQ Security, in depth

Provider-agnostic PACS

UniQ Security decouples the management layer of physical access control (PACS) from the field hardware: panels and controllers from Johnson Controls, HID — including Mercury-based lines — LTS and DMP operate from one platform, while doors, readers, request-to-exit devices and locks are inventoried and standardized building by building.

Open-controller architecture is what makes that possible. Mercury controller firmware became the closest thing physical access control has to a lingua franca: multiple manufacturers build on the same controller platform, so the software above it can be replaced without ripping out the panels below. That is the structural break from proprietary head-ends — the platform stays, the hardware competes, and every future bid has more than one qualified answer.

  • One operator console across every building era
  • Open-controller hardware keeps future bids competitive
  • Standardized door kits — reader, lock, REX, position switch
  • Alarm and event streams normalized into one queue

Installation programs

UniQ Security is designed to support the access-control requirements that Navy installations operate under CNIC, and the equivalent programs at Army and Air Force installations — with visitor management and gate operations integrated locally as the program directs.

Installation access programs share a common shape: identity proofing at enrollment, credential validation at every opening, and an audit trail that can answer who passed which door and when. The platform is built around those requirements — normalized event streams, readable audit records, credential lifecycle management — and each site is scoped against its own program's controls. Acceptance belongs to the program and attaches to a deployment, never to a shelf product.

  • Designed to support Navy CNIC installation access-control requirements
  • Army and Air Force equivalent programs addressed the same way
  • Visitor and gate workflows integrated as the program directs
  • Audit trails your assessors can actually read

Credential to door

PIV, CAC and derived credentials are first-class: reader and panel selections are made for the credential population actually in the field, with FICAM-aligned deployments where the program requires them, and graceful handling of visitor and contractor populations that don't carry the primary credential.

PIV (Personal Identity Verification) is the federal civilian smart-card credential; CAC (Common Access Card) is its DoD counterpart. FICAM — Federal Identity, Credential and Access Management — is the government-wide architecture for how those credentials are issued, validated and used; a FICAM-aligned PACS validates the credential cryptographically at the door rather than trusting the card's mere presence. Designing to that model from the start means the credential path doesn't have to be rebuilt when the program tightens.

  • PIV/CAC-ready reader and panel selections
  • FICAM-aligned architecture where the program requires it
  • Visitor and contractor credentials handled without weakening the employee path
  • Credential lifecycle — issue, rotate, revoke — in one place

Migrate without rip-out

Migration starts with an audit of what's installed — every door, panel, reader and credential population, documented. Wiring, locks and doors that still serve are kept; head-ends and dying panels are replaced first; and old and new systems run in parallel during cutover so a door never goes dark.

The sequencing is deliberately boring. The head-end migrates first because it's the layer that unifies; panels follow as they age out, one building at a time, on a schedule your project manager can actually hold. Parallel-run cutover means each opening is proven on the new platform while the old one still stands behind it — the failure mode is a fallback, not a locked building.

  • Wiring and locks that still serve are kept
  • Head-end first, panels as they age out
  • Parallel-run cutovers — a door never goes dark
  • Per-building schedule your PM can hold
How engagements run

From door schedule to unified platform, in four steps

1 · Audit

Every door, panel, reader and credential population, documented.

2 · Design & quote

Target architecture + migration order, line-item BOM, §889-screened.

3 · Stage & configure

Panels bench-configured, door kits labeled per opening.

4 · Cutover & sustain

Parallel-run migration, then support and expansion under one partner.

Questions

UniQ Security — common questions

Which manufacturers does the platform operate?

Johnson Controls, HID (including Mercury-based controllers), LTS and DMP today; the open-controller approach extends coverage as programs need.

Is it approved for Navy/CNIC use?

Installation access programs approve DEPLOYMENTS, not shelf products. UniQ Security is designed to support CNIC-governed requirements and Army/AF equivalents, and we scope each site against its program's controls.

PIV/CAC support?

Yes; reader and panel selections are made for the credential population, FICAM-aligned where required.

Do we have to replace everything?

No; the platform's point is keeping what serves and replacing only the layers that fail the mission, panel by panel.

Cameras and intrusion too?

Access control is the core; video and intrusion integrate through the same event plane, with hardware sourced through our security storefront.

Ask AI about Uniqcli

UniQ Security

Unify your doors

Bring the door schedule — or just the list of head-ends you're tired of — and we'll map the migration, the hardware and a firm line-item quote.