Unassigned
0
Needs allocation
Open Work Orders
0
Live tickets
Escalated
0
Rule triggered
Awaiting Verification
0
Customer confirmation
PM Compliance (90d)
—
Target ≥90% · 0 overdue
Active Work Orders View all →
| WO | Issue | Assigned | Status | Overdue |
|---|
Repair Cost by Asset
Upcoming PM View all →
Engineer Workload Manage →
WO by Status
| WO | Raised | Complainer | Location | Problem | Assigned | Est. Finish | Overdue | Esc. | Status | Action |
|---|
| Asset | PM Task | Criticality | Frequency | Trigger | Next Due | Grace | Engineer | Status | Action |
|---|
These rules live in the database and are evaluated by a Postgres function. Change a threshold and press Run Escalation Engine — every open ticket is re-scored server-side.
Escalation Rules Re-evaluate now →
Escalation Levels
| Level | Role | Notified via |
|---|---|---|
| L0 | Assigned Engineer | App push |
| L1 | Chief Engineer | App + WhatsApp |
| L2 | General Manager | App + WhatsApp + Email |
| L3 | Directors / MD | Email + board report |
| Name | Type | Ref / Dept | Phone | Complaints | Action |
|---|
| Part | Part No. | Stock (this store) | Total All Stores | Reorder Lvl | Lifetime Used | Vendor | Status |
|---|
Most Frequently Used Parts
| Part | Qty Used | Withdrawals | Top Asset |
|---|
Store Access & Control
Accounts are created server-side by a secured function. Only admin and GM roles can reach it — the privileged key is never present in this page.
| Name | Role | Linked Engineer | Last Sign-in | Status | Action |
|---|
What each role can do
| Role | Permissions |
|---|---|
| admin | Everything, including creating logins |
| gm | Everything, including creating logins |
| chief_engineer | All maintenance data; add assets, parts, engineers, PM, escalation rules |
| director | Full visibility and master data; no login management |
| engineer | View everything; create and progress work orders, issue parts |
| storekeeper | View everything; issue and transfer parts |
| viewer | Read only |
Renaming a value updates every asset using it automatically. A value cannot be deleted while assets still reference it — reassign those assets first.
Every create, update and delete on work orders, assets, PM schedules, contracts, people and parts is recorded here with who did it and which fields changed. Records are written by the database itself, so they cannot be bypassed by the app.
| When | Who | What | Action | Fields Changed |
|---|
| Date | Vendor | Contract | Attended By | Received By | Assets | Issues | Counts |
|---|
Repair vs Replacement Value
Work Orders by Status
Repair vs Replace — Lifetime Cost Analysis
| Asset | Failures | Total Repair Cost | Replacement | Repair % | Recommendation |
|---|
Parts vs Assets Consumption Matrix
| Asset | Part Types | Total Qty | Parts Cost | Most Used Part |
|---|