PoC 3.5: Regional Manager (Multi-Depot Oversight & Allocation)

Functional Objective: Covers the 5 Regional Manager (RM) Offices (Delhi, Khadki, Guwahati, Lucknow, BD Bari). Features unified multi-depot monitoring dashboards, supplementary demand approvals, inter-depot stock diversion during regional shortages, depot inspection audits, variance threshold approvals, and high-level KPI reporting.

---

🎥 PoC Video Demonstration

Regional Manager Command Dashboard & Inter-Depot Balancing

Demonstrates multi-depot inventory visibility across the region, supplementary demand authorization, and stock variance audit sign-off.

---

📋 Core Functional Capabilities

• Regional Multi-Depot Dashboard: Real-time aggregate view of stock levels, transit stock, pending indents, and supplier delivery performance across mapped area depots.
• Supplementary Demands: Validation and forwarding of emergency/additional quota requests from URCs and Depots to CSD HO.
• Inter-Depot Diversions: Orchestrating stock transfers from surplus depots to deficit depots within the regional command zone.
• Stock Variance Governance: Maker-checker approval for physical stock adjustments exceeding depot manager discretionary thresholds.

---

🏗️ Technical Architecture & DocType Mapping

In Business M and Framework M, this domain is powered by native, metadata-driven DocTypes, async controllers, and distributed ledger adapters:

Active Business M DocTypes

Region, DistributionCenter, Warehouse, StockVariance, ManagementApproval, MaterialRequest

graph LR
    User["Stakeholder Portal / Desk"] --> Gateway["API Gateway"]
    Gateway --> Controller["Domain Controller & RBAC"]
    Controller --> DB[("PostgreSQL / RLS Master")]
    Controller --> Relay["Outbox Relay Worker"]
    Relay --> TB[("TigerBeetle Immutable Ledger")]

---

🧪 Verifiable Test Script (Human Review Flow)

Follow these steps in the running Business M instance to replicate the live PoC demonstration:

1. Access Domain Desk: Log into the web desk or local POS at the designated endpoint for this role.
2. Execute Transaction Flow: Follow the standard maker-checker workflow to create and submit the source document.
3. Verify Audit Trail & Ledger: Inspect the generated transfer ID, status transitions, and read-model balances.
4. Inspect Air-Gapped Sync (if applicable): Ensure zero cloud secrets on disk and verify cryptographic signing.