Skip to content
Duall Master

Vehicle access and sessions

Operate vehicle movement with the same command platform

Plate recognition and RFID identify every vehicle at the barrier, sessions tie back to residents, tenants, and visitors, and high-control gates can require a face-and-plate match before they open.

Built for

Realtime status

Built for

Governed actions

Built for

Shared audit

Parking
Duall Master Parking module

Operating model

Signal enters the module, context comes from the shared platform, action is preserved in audit.

Capabilities

What Duall Master does for Parking

This module is designed as a command workflow, not a static admin screen.

01

License-plate (LPR) and RFID vehicle entry at every barrier

02

Parking sessions tied to identities, tenants, or visits

03

Operator review for exceptions and manual actions

04

Two-factor face-and-plate entry for gates that must verify both driver and vehicle

Vehicle access

From plate to barrier, every vehicle is matched

A vehicle pulls up and the gate does the work — it reads the plate and the in-car tag, decides in real time, and logs the session. No ticket, no guard hut, no guesswork about which vehicle came in.

01

Vehicle approaches

A car, truck, or motorbike rolls up to the gate. No stopping for a ticket or an intercom call.

02

Plate + tag read

License-plate recognition reads the plate while an RFID tag confirms the vehicle — matched to a known identity, tenant, or visit.

03

Barrier opens, logged

On a match the barrier lifts and a parking session starts — every entry and exit on one searchable, audited timeline.

Two-factor entry

The face and the plate both have to match

For controlled gates, Duall Master can require the driver and the vehicle to verify together. The barrier opens only when the plate Duall Master reads matches the face behind the wheel — so a permitted vehicle can’t be driven in by the wrong person.

Running today at DHG Pharma — face for people, plate + RFID for vehicles, two-factor face-and-plate entry across four sites.

  • Plate verified

    LPR confirms the vehicle is registered and allowed at this gate, right now.

  • Face verified

    Face recognition confirms the driver is the identity paired to that vehicle.

  • Both, or no entry

    A valid plate with an unknown driver is stopped at the gate, not waved through.

AI Assistant · for Parking

Just ask.

Operator

"How many free parking spots in basement B1 right now?"

get_parking_occupancy · live count

Meet the AI Assistant →
Parking workflow
Duall Master Parking module
1

Signal

Parking events enter the same realtime operating timeline as access, visitor, video, parking, and audit activity.

2

Context

Operators see identity, policy, site, zone, device, and linked module records before acting.

3

Action

Approvals, overrides, reviews, and notes are governed by role and preserved in audit history.

Hardware

Runs on real Duali devices

Face, card, QR, and NFC terminals, door controllers, and outdoor readers — the same hardware deployed on live sites.

View the full hardware ecosystem
DE-950

DE-950

IP65 outdoor proximity reader with Wiegand and serial output for access, attendance, or parking.

DE-960

DE-960

Wide-card reader for access, attendance, e-payment, and parking — broad card support with Wiegand and serial output.

ICU-300N

ICU-300N

I/O door controller — onboard lock-control circuit, emergency-exit I/O, and TCP/IP.

DQ-101

DQ-101

Desktop citizen-ID (CCCD) reader — verifies QR, NFC, and chip data in under 3 seconds, on Windows and Linux.

DF-970

DF-970

AI face terminal with touchscreen — face, RF card, and NFC mobile ID at premium doors.

Operating workflow

From signal to context to action

A parking workflow should not end in an isolated log. It should move operators from live signal, to useful context, to governed action.

  1. 01

    Register vehicles by plate and RFID tag, paired to a resident, tenant, or visit

  2. 02

    Monitor entries, exits, sessions, and exceptions

  3. 03

    Hand visitors a temporary parking pass that expires with their visit

  4. 04

    Review event history for disputes or incidents

Built on one platform

Parking runs on the same platform as every other module.

Signal

Context

Action

Audit

Built on a shared foundation

Identity

Users, roles, tenants

Devices

Doors, cameras, intercom

Events

Realtime timeline

Audit

Reviewable actions

APIs

Connectors & flows

Deploy

Cloud · on-prem · hybrid

Each module works on its own — but they share one identity, events, audit, and integration layer, so they are stronger together. Exact scope is confirmed per project.

Product proof

Built for operational review, not just administration.

The module experience is designed around live status, structured records, linked context, and audit-friendly decisions.

Live status and exceptions

Part of the shared Duall Master command foundation.

Identity and policy context

Part of the shared Duall Master command foundation.

Linked event history

Part of the shared Duall Master command foundation.

Reviewable operator actions

Part of the shared Duall Master command foundation.

For

Residential and mixed-use parking operations

For

Commercial buildings and multi-site portfolios

For

Industrial sites with staff and contractor vehicles

For

Facilities modernizing parking without replacing every system at once

Platform connection

Stronger because the foundation is shared

Each module uses the same identity, event, audit, integration, and deployment foundation.

Parking sessions can share identity and tenant context
Live events connect to operator workflows and alerts
Audit records cover manual actions and policy changes
APIs support phased modernization with surrounding systems

Next step

See Parking in context

Discuss your site, module priorities, and deployment model with the Duall Master team.