Wash Hall Management
Every wash batch audited, every garment accounted for
Vorrex Server builds wash batches automatically, enforces ISO 23616 temperature thresholds, and routes every garment to its next step without manual paperwork. Operators on Vorrex Terminal run the wash hall from a single scan-and-confirm workflow — no clipboards, no spreadsheets, no missed garments.
Batch Lifecycle
From cage to clean: six statuses, zero gaps
Vorrex Server tracks every garment through six distinct wash-hall statuses. When a sling arrives at the sort bench, Vorrex Terminal confirms receipt and locks the cage. Vorrex Server auto-groups compatible garments into batches based on PPE category, wash programme, and machine capacity — no operator assembly required.
Each status transition is written to the immutable audit trail on Vorrex Server. If a garment misses a scan — pulled for repair, wrong cage, set aside — it appears as an unresolved item on the Vorrex Terminal dashboard before the batch can be submitted to the machine.
Awaiting Sort
on cage
Sorted
bench clear
Batch Built
auto-grouped
In Wash
machine locked
In Drying
post-cycle
Awaiting Inspect
dry complete
Smart Priority Queue
The system decides what gets washed first
Critical
Wearer below minimum PPE coverage. Escalated immediately.
Urgent
SLA breach within 4 hours at current throughput.
Standard
Normal cycle. SLA window open.
Deferred
Awaiting reproof chemical or repair clearance.
Vorrex Server calculates queue priority from wearer protection status, SLA dwell time, and contract service level. Operators on Vorrex Terminal see their next batch pre-selected — they confirm and load, not decide. Every auto-decision is logged to the smart decision record with the threshold values used.
Temperature Compliance
ISO 23616 wash temperatures enforced at the machine
Each PPE category carries a minimum wash temperature defined in Vorrex Manager. When a batch completes, Vorrex Server records the programme used against the category requirement. A structural jacket washed below the required threshold cannot progress — Vorrex Terminal shows a hard-fail, and the garment is held pending supervisor decision.
Temperature records are part of the garment's full lifecycle history. During a client audit, wash temperature data for any individual garment — across every cycle it has completed — is retrievable from Vorrex Manager in seconds. No manual log book required.
Consumable & Reproof Tracking
Reproof chemicals and wash consumables tracked per batch
Garments flagged for reproofing during inspection are routed to a reproof batch on Vorrex Server. The chemical lot number and application date are recorded against the garment, giving a full reproofing history for each structural jacket or proximity suit in the fleet.
Wash consumable usage — detergent batch, water softener dosing — is configurable in Vorrex Manager against each machine. When thresholds are reached, Vorrex Server raises a reorder alert visible in the Vorrex Manager operations dashboard.
Post-Dry Routing
Clean garments go exactly where they need to go next
Once drying is confirmed on Vorrex Terminal, Vorrex Server evaluates each garment's condition flags set at sort and routes it to the correct next step: inspection bench, repair queue, or reproof station. Operators do not make routing decisions — they scan and follow the destination shown on screen.
Garments that return clean from wash with no flags go directly to the inspection queue. The inspection checklist used is determined by PPE category — configured in Vorrex Manager, not in code. The entire wash-to-inspect chain runs without supervisory intervention on a standard cycle.
FAQ
Common questions
How does Vorrex track wash temperature compliance?
Every wash batch on Vorrex Server records the programmed wash temperature against the garment category requirements from ISO 23616. If a batch completes below the minimum threshold, Vorrex Server blocks the batch from progressing to dry and raises a compliance alert. The temperature record is written to the immutable audit trail and is available in Vorrex Manager.
How does Vorrex build wash batches automatically?
The wash batch service on Vorrex Server groups garments by compatible wash programme — temperature, reproof requirement, PPE category — and respects machine capacity from the machine register. Operators on Vorrex Terminal confirm the batch before loading; they do not build it manually.
Can different garment categories be washed together?
Compatibility rules are configured in Vorrex Manager against each PPE category. Structural fire kit and proximity suits have separate programmes by default. The wash batch service enforces these rules; operators on Vorrex Terminal cannot override a category conflict without a supervisor capability.
How does Vorrex prioritise which garments are washed first?
Vorrex Server calculates priority from SLA thresholds, wearer protection status, and dwell time on the sort bench. Garments whose wearers have fallen below minimum PPE coverage are escalated automatically. Operators on Vorrex Terminal see a colour-coded queue — red for critical, amber for approaching SLA, blue for standard.
What happens after the wash cycle completes?
Vorrex Server routes completed garments to the next required step — drying, reproof, or inspection — based on the garment type and any flags raised during sort. Operators on Vorrex Terminal scan each garment out of the machine; the system confirms the destination bin.
Related reading
See it on your data, or start with the checklist.
Either path works. Pick whichever fits where you are today.