Defence & Military
Multi-garment fleets, unbroken custody, and a record that survives the audit
Vorrex was built for industrial laundries servicing fire and rescue services under ISO 23616. Defence PPE processing asks the same three questions in a harder setting: what is this garment, who had it, and can you prove what happened to it. Vorrex answers all three from a server that sits inside your own perimeter.
How Vorrex applies here
Built for fire kit. The compliance model is the same one.
Defence is a secondary market for us. We are not going to claim a standing contract we do not hold, and we are not going to pretend Vorrex ships with a defence rule set pre-loaded — it does not. What it ships with is a rule engine you configure.
The loop transfers without modification. You have wearers with entitlements. You have garments that are issued, soiled, washed, inspected, repaired, and eventually condemned. You have an auditor who wants the evidence, not the summary. Vorrex handles that loop whether the label says ISO 23616, EN ISO 11612, EN ISO 11611, or a standard specific to your contract. The rules live in Vorrex Manager and are yours to set — no code changes.
Multi-garment fleets
One plant, several fleets, different rules on each
A defence laundry rarely processes one garment type. FR combat clothing, chemical suits, structural firefighting kit for the site brigade, and general protective workwear can arrive on the same shift with different contract terms behind each of them.
Rules configured per garment type
Inspection checklists, wash programmes, maximum wash counts, calendar life, and inspection intervals are defined per type in Vorrex Manager. The compliance engine evaluates every garment against its own rules on every wash return — not against a plant-wide default.
Routing keeps fleets apart
The workflow engine routes each garment to the correct station and the correct wash batch. Fleets with different handling requirements or different owning units do not share a batch, and the routing decision is recorded rather than left to the operator to remember.
Inspection that cannot be skipped
Checklist items marked mandatory must be answered before the inspection can be closed at Vorrex Terminal. A hard-fail answer withdraws the garment from service immediately and generates a condemnation record naming the triggering rule and the inspector.
Chain of custody
Custody is a chain of scans, not a signature on a docket
Every handling event writes a lifecycle event against the garment UID. The events are append-only by database constraint — once written, a wash, inspection, or condemnation cannot be modified or removed through the application by any user, administrator, or developer.
- •
Collection — Garments leave the unit in a labelled decontamination bag or sealed cage. The container is scanned, and the garments inside it are bound to that container record.
- •
Transport — Vorrex Go records the driver leg — collection, load, and delivery — and runs offline between stops, syncing when it regains the plant network. The road leg is not a gap in the record.
- •
In plant — Goods in, sort bench, wash hall, inspection, repair, and dispatch each write a timestamped event carrying the operator and the station. Dwell time at each stage is tracked and flagged when it exceeds threshold.
- •
Return — Dispatch binds the garment to a delivery and a receiving location. The wearer sees the item reappear in Vorrex Me, and the H&S team sees the same movement in Vorrex Portal.
CBRN-adjacent protocols
Declared classes wash. Unidentified agents do not.
Vorrex tracks five contamination categories: standard soiling, chemical, biological, radiological or nuclear, and physical contamination such as fuel and oil. The category is captured at the sort bench or reported earlier by the wearer in Vorrex Me, and it determines the treatment pathway.
Where the contaminant is a declared class — identified, and covered by a protocol that permits decontamination — the garment routes to the specialist wash pathway. Wash parameters, cycle count, and the assessment that authorised the route are all recorded against the garment. Individual assessment mode in Vorrex Terminal walks the operator through the checklist item by item and photographs the garment before treatment.
Where the agent is unidentified, the garment is segregated. It is held in quarantine, blocked from re-entering the wash cycle, and passed to disposal or destruction under your own protocol and the local regulation that governs it. Vorrex records the segregation event, the assessment, the photographs, and the destruction record. It enforces your protocol; it does not write it.
Site security constraints
The plant keeps running with the outside world switched off
Plant operations do not depend on a cloud service. If your site policy forbids an outbound connection, the wash hall still runs.
On-premise by default
Vorrex Server runs as a supervised service on the plant LAN — systemd on Linux, a wrapped Windows Service on Windows. Compliance scheduling, protection checks, and overnight processing execute on that server. Vorrex Setup handles the install on your hardware, in your data centre, under your infrastructure team.
Plant-scoped data
Every query is scoped to the user’s plant at the database level. A user at one plant cannot see, update, or reference another plant’s data — the boundary is enforced by the database, not by application code.
Three isolated login contexts
Internal staff (six roles with granular permissions), Vorrex Portal for the client H&S team, and PIN-authenticated Vorrex Me for wearers. The guards are separate; a wearer sees only their own kit, a client sees only their own records.
Your data, standard formats
Records sit in a standard SQL database and documents in standard object storage — not a proprietary container. You can export at any time, and you can move storage provider without touching the application.
Relevant standards
What the rule engine can be configured against
Vorrex ships configured for ISO 23616. Defence rule sets are built in Vorrex Manager during onboarding, by your team or ours. These are the standards defence laundries most often need to evidence.
- •
EN ISO 11612 — Heat and flame protective clothing. Limited flame spread, convective heat, radiant heat, and molten metal splash performance. Inspection checklists and wash count limits are set per garment type.
- •
EN ISO 11611 — Protective clothing for welding and allied processes. Class 1 and Class 2 garments can carry their class as a garment attribute and be evaluated against class-specific condemn criteria.
- •
EN 1149-5 — Electrostatic dissipative protective clothing. Antistatic performance degrades with wash count, so the wash limit rule is the one that matters here — the engine flags the garment before the limit is exceeded, not after.
- •
ISO 15797 — Industrial washing and finishing procedures for workwear testing. Wash programme parameters — temperature, chemistry, cycle — are recorded per batch, so a non-compliant wash is visible before the garments move on.
- •
ISO 23616 — Cleaning, inspection and repair of firefighting PPE. The standard Vorrex was built against, and the one that applies directly to a site fire brigade operating alongside a defence estate.
Audit-ready records
The pack exists before the auditor asks for it
There is no reporting project at the end of a contract year. A compliance pack for any wearer, garment, or date range is generated on demand from Vorrex Manager: wash records, inspection results with the failing checklist item where one exists, repair history linked to the inspection that found the defect, condemnation certificates naming the triggering rule, and the wearer entitlement position at that moment.
Every garment label carries a QR code that resolves to the same digital history. An auditor at the rack scans the label and reads the record without asking anyone to run a report — and reads the same record three years later, because the audit trail cannot be altered.
Pre-first customer in defence
We are pre-first-customer here. This is where their words would go.
Vorrex holds no signed defence contract, and we will not put a placeholder crest on this page. If you run or supply a defence PPE laundry, we would rather walk you through the live system — including the on-premise install and the audit trail constraint — than describe what somebody else thinks of it. Yours could be the first name on this page.
FAQ
Common questions
Can Vorrex run entirely inside a site with no internet connection?
Yes. Vorrex Server runs as a supervised service on the plant LAN — systemd on Linux, a wrapped Windows Service on Windows. Compliance scheduling, wearer protection checks, wash batch processing, and every Vorrex Terminal scan are handled by that local server. No plant operation depends on an outbound connection. Vorrex Setup performs the first-time install on your own hardware, your infrastructure team holds the server, and you decide where backups go. The web surfaces — Vorrex Portal, Vorrex Me, Vorrex Go — are optional and can be published only on your internal network.
How does Vorrex maintain chain of custody for a garment between the unit and the laundry?
Custody is recorded as a chain of scans, not a paper note. A garment leaves the unit inside a labelled decontamination bag or a sealed cage, is scanned at goods in against that container, and every later handling event — sort, wash batch, inspection, repair, dispatch — writes an immutable lifecycle event carrying the garment UID, the operator, the station, and the timestamp. Vorrex Go records the driver leg between site and plant. Because the audit trail is append-only by database constraint, no user, administrator, or developer can edit or delete a link in that chain through the application.
How does Vorrex handle CBRN-adjacent contamination?
Contamination category is captured at the sort bench, or reported earlier by the wearer in Vorrex Me, and it drives the routing. A declared contamination class — a known chemical, biological, or radiological agent that your protocol says is washable — routes to the specialist wash pathway with its own parameters and its own dwell record. Where the agent is unidentified, the garment is segregated in quarantine, cannot re-enter the wash cycle, and is held for disposal or destruction under your own protocol and local regulation. Vorrex records the segregation, the assessment, the photographs, and the destruction certificate; it does not decide your disposal policy for you.
Can one plant process several garment fleets with different contract terms?
Yes. Garment types, inspection checklists, wash programmes, wash count limits, calendar life limits, and inspection intervals are configured per type in Vorrex Manager. A structural jacket, an FR combat coverall, and a chemical suit can sit on the same sort bench and still be evaluated against completely different rules on every wash return. Workflow routing keeps the fleets in their own lanes so that garments belonging to different units or classification levels do not share a batch.
What can we hand an auditor without preparing anything in advance?
A compliance pack for any wearer, any garment, or any date range, generated on demand from Vorrex Manager. It contains the wash records, inspection results with the failing checklist item where relevant, repair history, condemnation certificates, and the wearer entitlement position at that point in time. Each garment label carries a QR code that resolves to the same digital history, so an auditor standing at the rack can self-serve rather than asking for a report.
Who can see what, and how is that separation enforced?
Vorrex has three separate authentication guards. Internal plant staff have six roles with granular permissions. Vorrex Portal is a separate guard for the client H&S team and is scoped to their own records. Vorrex Me uses PIN authentication and shows a wearer only their own kit. Below that, every database query is scoped to the plant, so data belonging to one plant cannot be read or referenced from another. The isolation is enforced at the database level rather than in application code.
Related platform features
45 minutes. Your garment types. No slides.
We walk through the real system with your products, your compliance rules, and your contract structure.