NV Operator
Access Control
| User Email | Role | Added Date |
|---|
Role Permissions Matrix
Quick reference for what each role can access and do across the system
| Role | Create Route | Edit Route | Bulk Upload | Force Complete | Approve Driver | Archive | Vendor Mgmt | Access Ctrl | Navigation |
|---|---|---|---|---|---|---|---|---|---|
|
Superuser
Full override, user mgmt |
✓ | ✓ All | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | All Views + System Setup |
|
Admin
Full access, no override |
✓ | ✓ All | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | All Views |
|
Ops Admin
Create & archive routes |
✓ | ✓ All | — | — | — | ✓ | — | — | Create · Monitor · BI · Shippers · Tickets |
|
Transport Admin
Legacy role — not assignable via UI |
— | ✓ All | — | — | ✓ | ✓ | ✓ | ✓ | Assign · Monitor · BI · Drivers · Shippers · Tickets · Vendors · Access |
|
Transport Operator
Assign & monitor active routes |
— | ✓ Active | — | — | ✓ | — | — | — | Assign · Monitor · Drivers · Tickets |
✓ All = can edit active & completed/failed routes · ✓ Active = edit only while route is in-progress (not confirmed/completed/failed)
Email Templates
Configure the invite email templates sent to vendors and shippers. Changes are saved to Firestore and immediately applied to Firebase Auth.
Vendor Invite Email
Sent when inviting a new vendor (transport company) to the Vendor Portal.
Shipper Invite Email
Saved to Firestore and applied to Firebase Auth each time a shipper invite is sent.
Create Route
Deploy New Route
Configure shipper, driver, multiple waypoints with GPS coordinates, contact details and SLA times — all in one form before saving.
CSV Template Format
Route_ID (leave blank for auto), Shipper_Global_ID, Route_Date (Driver assigned separately via Driver Assignment)
Then per drop (Drop0 → Drop30):
DropN_Address, DropN_LatLng, DropN_ContactName, DropN_ContactNumber, DropN_StartTime, DropN_EndTime, DropN_PlannedDeliveryDate, DropN_Instructions
• Route_Date format: YYYY-MM-DD | LatLng format: "13.7563, 100.5018"
• StartTime / EndTime: HH:MM format — minutes must be 00 or 30 (e.g. 09:00, 14:30). Leave blank for Anytime.
• PlannedDeliveryDate: YYYY-MM-DD — D1+ drops only, defaults to Route_Date if blank.
• If Route_ID exists and Drop0 is COMPLETED, that row will be skipped (cannot bulk-update completed routes)
• Drop0 = Pickup from shipper | Drop1–30 = Delivery stops
Drag & Drop CSV File
or click to browse from your computer
Upload Issues
Pending Vendor Reassignment Requests
Route Monitoring
Today's Completion Rate
--%
| Route Details | Entities | Progress | Status | Actions |
|---|
Driver Fleet & Approvals
Audit Logs
Track of all key actions performed by operators and admins.
Shipper Directory
Register New Enterprise Shipper
Add credentials, pickup location, geofence settings and LINE invite access
CSV Template Format
Global_ID, Shipper_Name, Pickup_Location, Pickup_LatLng, Liaison_Name, Phone_Number, Login_Email, Login_Password, Geofence_Enabled, Geofence_Radius_M
• Geofence_Enabled: true / false | Geofence_Radius_M: metres (e.g. 1000)
Drag & Drop Shippers CSV
or click to browse
| Enterprise | Login / LINE | Pickup Details | Actions |
|---|
Driver Assignment
Assign approved drivers to routes. Search routes by ID, shipper, or date.
Pending Vendor Reassignment Requests
| Route | Shipper | Route Date | Assigned Driver | Action |
|---|
Ticketing
Track driver penalties, shipper issues, and address complaints.
| Ticket | Type | Route / Shipper / Driver | Status | Lead Time | Assigned To | Created | Actions |
|---|
Vendor Fleet Management
Create and manage transport company vendor accounts.
BI Analytics
Filters
Transport Performance
Overall OTP
--%
completed drops vs SLA
D0 Pickup OTP
--%
Drop 0 within timeslot
Delivery OTP
--%
Drops 1–N (excl. DOC)
DOC Return OTP
--%
Returned within next day
Avg Time at Drop
—
arrived → success/fail
Timeslot Compliance
--%
arrived within timeslot
Planned Date OTD
--%
D1+ on/before planned date
Completed Drops
0
COMPLETED status
Total Routes
0
0 routes matched
Timeslot Performance (by Arrived Time)
drops with a timeslot set — % of drivers who arrived within the window
Route Breakdown
| Route ID | Shipper | Date | Drops | Avg Dwell | Distance | Status |
|---|
Ticketing Performance
Working days: Mon–Sat · Sundays & BOT public holidays excluded · SLA target = resolved within 2 working days
Active Tickets
0
open + working
Total Tickets
0
raised in date range
Resolved
—
resolved or not-do
Avg Lead Time
—
open → resolved (working hrs)
SLA Compliance (≤2 working days)
--%
% of resolved tickets closed within 2wd
By Issue Type
resolved %, avg working-day lead time, SLA
By Assignee
total assigned · resolved · avg lead time