Skip to content
Duall Master
Multi-site centralized control use-case background

Use case

Run every site from one console — without flattening local control

Portfolios grow site by site, and so do the tools. Duall Master gives you one identity model, one policy framework, and one operating picture across every location — while each site keeps the local permissions and structure it needs.

One command surface

Module-by-module rollout

Audit-friendly operations

Multi-site centralized control operating context
Multi-site centralized control command view
Duall Master product interface for Multi-site centralized control

How it plays out

The scenario, step by step on one timeline.

Each step ties to a real platform action — not a slideshow.

  1. 01

    Foundation

    Identity, roles, and policy are defined once at the portfolio level.

  2. 02

    Onboard sites

    Each site joins the same foundation, keeping its own zones and local permissions.

  3. 03

    Operate

    One console shows access, visitors, and incidents across every location.

  4. 04

    Govern

    Policy changes, reporting, and audit run across the whole portfolio at once.

Before and after

Before Duall Master

Each site on its own system, with its own logins and exports

No portfolio-wide view of access, visitors, or incidents

Policy changes repeated by hand at every location

Onboarding a new site means standing everything up again

After Duall Master

Shared identity, policy, and site structure

Live events with module context attached

Governed operator actions with audit history

Phased expansion without replatforming

Most relevant modules

Module combinations for this use case

This use case starts with the module that solves the clearest operational pain, then expands on the same foundation.

Module stack

One operating picture, assembled module by module.

Shared foundation

Identity & policyRealtime eventsAudit historyAPIs & deployment
Duall Master module stack for Multi-site centralized control

Live operations layer

Access, visitors, parking, video, intercom, and audit events resolve into the same command surface.

Field references

Deployments that ground this use case

Real customer references delivering capabilities now packaged as Duall Master — scope, hardware, and figures sourced from project documentation.

Ministry of National Defense deployment reference

Access Control + Visitor Management + Parking · 2025

Ministry of National Defense

When one of Vietnam’s most security-critical institutions needed access control at national scale, it chose Duall Master — deployed across 15 military service branches under Project 06 (Đề án 06), unifying people, vehicles, and visitors on a single platform. Personnel are recognized by face, fingerprint, or card; vehicles by licence plate; visitors by chip-embedded citizen ID — every entry tied to a verified identity.

15 service branches~99% AI plate accuracyNationwide under Project 06
Read case study →
DHG Pharma deployment reference

Access Control + Parking + Video Management · 2026

DHG Pharma

DHG Pharma runs access control, vehicle entry, and CCTV across four manufacturing sites on Duall Master — people enter by face, vehicles by licence plate and RFID, and the gate opens only when both the driver’s face and the vehicle’s plate match.

4 manufacturing sitesFace + plate to enterLPR · RFID · CCTV
Read case study →
TIL International Port deployment reference

Access Control + Visitor Management + Time Attendance · 2026

TIL International Port

A busy international container port never really closes — workers, drivers, and visitors move through its gates around the clock. At TIL’s Hải Phòng terminal, Duall Master keeps that flow secure and accountable: staff enter by face or card, visitors are managed at the gate, and the same recognized entry becomes the attendance record.

International seaportFace ID · cardAccess · visitors · attendance
Read case study →

Scenario operating model

Multi-site centralized control needs connected site signals, not another point solution.

Modules in play

Access Control entry Visitor Management Parking Video Management (VMS)
Context-specific command layer
  1. 01

    Signal

    Doors, visitors, cameras, intercoms, and parking generate live signals — not isolated alerts.

  2. 02

    Context

    Identity, policy, site, zone, and related module records attach to every signal.

  3. 03

    Action

    Operators approve, deny, review, or escalate inside one governed workspace.

  4. 04

    Audit

    Every decision keeps the who, what, when, and evidence — ready for review.

Buyer-facing model for phased adoption: start with the clearest pain, then add adjacent modules on the same foundation.

Deployment and trust

Shared identity and tenant-aware permissions across sites
Central policy with per-site overrides
One cross-site operating picture and audit trail

Typical adoption path

  1. 01Establish shared identity and policy at the portfolio level
  2. 02Bring sites onto the same foundation one at a time
  3. 03Operate, report, and audit across the whole portfolio

Next step

Discuss Duall Master for Multi-site centralized control

Review module priorities, deployment constraints, integrations, and rollout path for your environment.