Command Centre
Every zone. Every operator. One screen.
Live plant dashboard showing every zone, operator, and container. Smart work queue. Multi-plant management. Live compliance alerts.
Live Dashboard
Zone-by-zone status. Colour-coded. Always current.
The Command Centre shows every zone in the plant — goods in, sort bench, wash hall, dryers, inspection, clean stock, dispatch. Each zone displays the current container count, operator assignments, and a colour-coded status indicator.
Green means the zone is operating within capacity. Amber means containers are queuing beyond the target dwell time. Red means the zone needs attention — a bottleneck, an unattended station, or a compliance breach.
Container locations update as operators scan at each zone transition. No manual reporting. No whiteboards. The dashboard reflects reality, not what someone remembered to write down.
Zone statuses
The real system
The Command Centre from the ops manager's screen.
Live alerts, zone summary, replacement orders, work queue depth — all on one screen. Running against our demo environment with multiple fire brigade clients.
Smart Work Queue
Operators do not choose what to do next. The system tells them.
The work queue assigns tasks to operators based on their role, zone access, current capacity, and task priority. An inspector at the inspection zone sees only the garments queued for inspection, in priority order.
Emergency replacements — garments flagged by the Wearer Protection Engine — appear at the top of the queue. SLA-critical items are prioritised over routine processing. The operator does not need to know why. They work the queue top to bottom.
A new operator and a ten-year veteran see the same queue. Neither decides the order. The system enforces throughput priorities that no individual can override.
Queue assignment
- Role-based filteringinspector, washer, picker
- Zone access controloperator sees their zone only
- Capacity balancingauto-redistribute on absence
- Priority orderingemergency > SLA > routine
- No manual overridesystem-assigned, not chosen
Multi-Plant Management
Centralised view. Plant switcher. Every entity scoped.
Operators running multiple plants switch between them from one login. The plant switcher changes the dashboard context — zones, operators, containers, and queues all scope to the selected plant.
Every garment, batch, inspection, route, and operator record belongs to a specific plant. Switching plant context changes everything you see. Cross-plant reporting is available at the group level.
Group managers see aggregate KPIs across all plants: throughput, compliance rates, SLA performance, and condemned garment volumes. Drill into any plant for the full Command Centre view.
Plant scope
Plant-level entities
zones, operators, containers, batches, routes
Group-level aggregation
throughput, compliance %, SLA adherence, condemned volume
Complete isolation
Each plant's data is isolated — no cross-plant data leakage
Live Alerts
Compliance breaches. SLA warnings. Stock triggers.
The Command Centre surfaces alerts as they happen. No batch reporting. A compliance breach — a garment passing inspection when it should have been condemned — triggers an immediate alert.
SLA warnings fire when a client's turnaround time is at risk. Stock triggers fire when buffer inventory for a product type drops below the configured threshold. Both appear on the dashboard and push to the ops manager via SMS.
The dashboard auto-refreshes. Alerts are not dismissed by reading them — they require an action or acknowledgement. Every alert is logged as an immutable event in the audit trail.
Alert types
Compliance breach
Hard-fail override attempt. Auto-condemned garment re-entered.
SLA warning
Client turnaround at risk. Garments dwelling beyond target.
Stock trigger
Buffer below threshold. Reorder or reallocation needed.
SLA Breach Predictor
Predictive alerts before SLAs are missed. Not after.
The system calculates delivery feasibility against contracted turnaround times. If a client's garments are dwelling in the wash hall and the remaining processing time plus route schedule exceeds the SLA window, an alert fires — before the breach happens.
Ops managers see which clients are at risk and which zones are causing the delay. The prediction updates live as garments move through each zone. A breach that was predicted at 09:00 may resolve by 10:30 if throughput recovers — the system tracks both.
Exception Dashboard
Every operational anomaly. One view.
Overdue inspections. Missing garments. Temperature deviations. SLA risks. Condemned garments awaiting disposal. Unreconciled goods-in variances. Every exception the system detects appears in a single, prioritised view.
Exceptions are not informational — each one requires an action or acknowledgement. They cannot be dismissed by reading them. An ops manager either resolves the exception or records a reason code. Every interaction is logged in the audit trail.
Exception types
- Overdue inspectionsgarments past inspection interval
- Missing garmentsexpected but not scanned
- Temperature deviationswash cycle out of spec
- SLA risksturnaround time at threshold
- Goods-in variancesmanifest vs actual mismatch
Operator Performance
Throughput per operator. Training needs identified.
Every scan is attributed to an operator. The system tracks inspections per hour, scans per shift, and error rates — garments that had to be re-processed because of an incorrect routing decision or a missed defect at inspection.
Performance data identifies training needs before they become quality problems. An inspector with a higher-than-average miss rate on moisture barrier checks can be retrained on that specific checkpoint — not sent on a generic refresher course.
Tracked metrics
- Inspections per hourper operator, per shift
- Scans per shiftzone throughput contribution
- Error ratere-processing incidents
- Checkpoint accuracyper inspection item
- Training recommendationssystem-generated
Capability Matrix
Which operators are certified for which tasks. Auto-assigned.
Every operator has a capability profile — the tasks they are certified to perform. Inspection requires specific training. Wash programme selection requires certification on that machine. The system knows which operators can work which zones and assigns accordingly.
When work is assigned to the smart queue, the system checks operator capabilities before placing the task. An operator without inspection certification will never see inspection tasks in their queue — even if the inspection zone is short-staffed. Certification expiry dates are tracked and alerts fire before they lapse.
Shift Management
Calendar. Templates. Swap requests. Handover notes.
Staff scheduling is built into the platform. Shift templates define standard patterns — early, late, nights — and managers assign operators to templates via a calendar view. The system checks capability matrix coverage: every shift must have at least one certified inspector, one certified wash operator, and so on.
Swap requests flow through an approval process. Handover notes are recorded at shift end and displayed to the incoming team. Outstanding exceptions, in-progress batches, and pending dispatches are all visible in the handover summary.
Scheduling features
- Shift calendardrag-and-drop assignment
- Template patternsearly / late / nights
- Capability coverage checkauto-validated per shift
- Swap requestsapproval workflow
- Handover notesstructured shift-end summary
Cost Tracking
Cost Tracking
Track processing costs per garment, per client, per product type. See where the cost sits in the lifecycle — wash, inspection, repair, condemnation, replacement. Identify which clients and products are most expensive to service.
Plant Comparison
Plant Comparison
Side-by-side performance metrics across all plants. Throughput, compliance rates, SLA adherence, and condemned volumes compared in a single view. Identify which plant needs attention and which is setting the benchmark.
Dwell Time Monitoring
Every garment's time in every zone. Tracked. Alerted.
The system calculates how long every garment dwells in each zone. Wash hall, quarantine, inspection, clean stock — every zone has a configurable dwell threshold. If a batch sits in the wash zone longer than expected, the Command Centre flags it immediately.
Dwell checks run every 15 minutes. Every active garment is checked against the threshold for its current zone. Breaches generate alerts on the dashboard and push to the ops manager — before bottlenecks cascade into SLA breaches.
Quarantine dwell is tracked separately. Garments held for contamination assessment or pending disposal have their own thresholds. If a garment sits in quarantine beyond the limit, it surfaces as an exception requiring action. Nothing sits forgotten.
Zone dwell thresholds
- Wash hallbatch exceeds expected cycle time
- Quarantinecontamination hold beyond threshold
- Inspectionqueued garments awaiting inspector
- Clean stockprocessed but not yet picked
- Configurable per zoneadmin-set thresholds in minutes
Shift Handover
Structured handover. Nothing falls through the cracks.
When shifts change, the incoming ops manager sees a structured handover summary — not a verbal update, not a scribbled note. The system compiles everything the new shift needs to know: in-progress batches, queued work, emergency replacement orders, open alerts, and handover notes from the outgoing team.
The outgoing shift records notes against specific items — a batch that needs watching, a machine that ran hot, a client escalation in progress. These notes attach to the operational context, not a generic log. The incoming team sees them in the right place at the right time.
Shift handover is not optional. The system presents the summary automatically. The incoming ops manager sees exactly where things stand — which zones are behind, which dispatches are at risk, which emergency orders are in flight. No guesswork. No missed context.
Handover summary includes
- In-progress batcheswash, dry, inspection — current state
- Queued workpending tasks by zone and priority
- Emergency ordersProtection Engine replacements in flight
- Open alertsunacknowledged exceptions and breaches
- Outgoing shift notescontextual notes on specific items
Ambient Idle Screen
Always useful. Even when nobody is operating it.
After 60 seconds of inactivity, the plant floor interface transitions to a zone summary overlay. Live throughput per zone, queue depths, and alert counts — displayed at a glance on the ops office screen. Think digital signage, built into the platform.
The idle screen is not a screensaver. It is a real-time operational display. Throughput numbers update live. Alert counts reflect the current state. If a zone goes red, the idle screen shows it immediately — even if nobody is actively working at the terminal.
When an operator touches the screen or scans a barcode, the idle overlay dismisses instantly and returns to the active interface. No login required. No delay. The idle screen is a view mode, not a separate application.
Idle screen displays
- Zone throughputgarments processed per zone, live
- Queue depthspending items per zone
- Alert countsactive alerts by severity
- 60-second timeoutconfigurable inactivity threshold
- Instant dismisstouch or scan returns to active mode
45 minutes. Your garment types. No slides.
We walk through the real system with your products, your compliance rules, your contract structure. Pick a time that works.
What to expect
- Live walkthrough with your garment types and standards
- Compliance engine demo — see 14 rules enforced on real data
- Protection engine — watch a coverage gap get caught and resolved
- Client portal — what your fire brigade clients would see
- Pricing discussion — transparent, no pressure