Architecture, workflows, rules and configuration intelligence.
Each spoke is a module wired into the Ops Core — edits cascade through the dependency graph below.
| Projects | Inventory | Procurement | Maintenance | Safety | Reports | Settings | |
|---|---|---|---|---|---|---|---|
| Operations Director | Full | Full | Full | Full | Full | Full | Full |
| Project Manager | Full | Edit | Edit | Edit | View | Full | View |
| Team Lead | Edit | Edit | View | Edit | Edit | View | Restricted |
| Engineer | Edit | View | Restricted | Edit | View | View | Restricted |
| Procurement Officer | View | Edit | Full | Restricted | Restricted | View | Restricted |
| Safety Officer | View | View | Restricted | View | Full | Edit | Restricted |
Every client event propagates through the chain — settings here change how each stage reacts.
Current workflow architecture is healthy, but procurement and inventory dependencies create the highest delay risk in the system. Two automation rules would absorb most of that exposure.
Auto PO when stock < threshold
Required before rooftop work
Region + workload weighted
1h critical / 4h high / 24h low
| Department | Manager | Staff | Status |
|---|---|---|---|
| Installation | Tunde Adebayo | 18 | Active |
| Site Surveys | Musa Bello | 6 | Active |
| Maintenance | Kelvin Eze | 12 | Active |
| Procurement | Grace Johnson | 5 | Active |
| Safety & Compliance | Daniel Etim | 4 | Active |