Repair & Condemn Workflow
Every defect recorded, every repair decision auditable
Vorrex Server manages the full repair lifecycle — from defect detection at inspection through to post-repair routing. Technicians on Vorrex Terminal work through guided repair tasks with patch limits, body map context, and condemn-threshold enforcement built in. Nothing relies on operator memory or a paper job card.
Repair Queue
The repair queue builds itself from inspection results
When an inspector raises a defect on Vorrex Terminal, Vorrex Server automatically creates a repair work item and places it in the technician queue. Priority is calculated from wearer protection status, SLA urgency, and defect severity. Technicians on Vorrex Terminal see one item at a time — their next task, chosen by the system.
Repair queue capacity is configurable in Vorrex Manager. If throughput falls behind — garments dwell in the repair queue beyond the SLA threshold — Vorrex Server escalates the alert to the operations dashboard in Vorrex Manager before the breach occurs.
Patch Constraints
Patch limits enforced — no garment stays in service past its safe life
Each PPE category in Vorrex Manager carries a maximum patch count and a maximum repaired area as a percentage of total garment surface. Vorrex Server tracks cumulative patches across the garment's full life. On Vorrex Terminal, the current patch count and remaining allowance are shown before each repair task.
When a garment reaches its patch limit, Vorrex Terminal blocks the repair workflow and presents a condemn prompt. The technician confirms, Vorrex Server transitions the garment to the condemned status, and a replacement is flagged to the protection engine to maintain wearer coverage.
Defect Documentation
Defect type, location, and repair method recorded at the bench
On Vorrex Terminal, technicians select defect type from a configured list — seam separation, outer shell tear, retroreflective degradation, hook-and-eye failure — then confirm the repair method applied. Every record includes technician identity and timestamp from the terminal session.
Vorrex Server stores the full defect and repair record against the garment lifecycle. For ISO 23616 audits, Vorrex Manager produces a repair history report showing every defect raised and resolved across the fleet, filterable by PPE category, garment, client, or date range.
Body Map Integration
Defect location pinned on the body map from inspection carries through to repair
When an inspector pins a defect on the body map during inspection on Vorrex Terminal, the coordinates are recorded on Vorrex Server. When the same garment arrives at the repair bench, the technician sees the defect location highlighted on the body map — no need to re-examine the whole garment to locate the fault.
Recurring defects in the same region — for example, repeated seam failures on the left shoulder of the same garment class — are visible in Vorrex Manager quality trend reports. Patterns that breach configured thresholds trigger a non-conformance report automatically.
Post-Repair Routing
Repaired garments routed back into service without manual intervention
When a technician confirms repair completion on Vorrex Terminal, Vorrex Server evaluates whether the garment requires a post-repair wash before re-inspection. If the repair involved any material application, the wash route is enforced automatically. Technicians do not decide the next step — they confirm the work and scan the garment out.
Post-repair inspection uses the same guided checklist as standard inspection, with defect markers from the repair record pre-populated. If the repaired region passes inspection, the garment proceeds to the clean stock zone. If it fails, it returns to the repair queue — with the new defect record linked to the previous one.
FAQ
Common questions
How does Vorrex decide whether to repair or condemn a garment?
The repair-versus-condemn threshold is configured in Vorrex Manager per PPE category. Vorrex Server evaluates defect severity, total wash cycle count, and remaining service life. If the garment exceeds the condemn threshold, Vorrex Terminal presents a hard-fail — the inspector cannot mark it as repairable without a supervisor override, which is logged.
How many patches can be applied to a structural jacket before it must be condemned?
Patch limits are set per garment category in Vorrex Manager, aligned with manufacturer guidance and ISO 23616 requirements. Vorrex Server tracks cumulative patch count and area. When a garment reaches the configured limit, Vorrex Terminal blocks further repair attempts and routes the garment to the condemn queue automatically.
How is repair work documented for a client audit?
Every repair on Vorrex Terminal is recorded with defect type, location from the body map, repair method applied, technician identity, and timestamp. This data is written to the garment lifecycle history on Vorrex Server. Vorrex Manager can export the full repair record for any garment or date range as part of an ISO 23616 audit package.
What happens to a garment after repair completes?
After a repair is confirmed on Vorrex Terminal, Vorrex Server evaluates whether the garment requires a post-repair wash before returning to service. If yes, it is routed to the wash queue. If the repair was minor and within category rules, it can proceed directly to inspection. The routing decision is automatic and based on rules configured in Vorrex Manager.
Can repair work trigger a non-conformance report?
Yes. Recurring defects on the same garment, or defect patterns above a configured frequency threshold, can automatically raise an NCR on Vorrex Server. NCR rules are configured in Vorrex Manager. The NCR links to the individual garment records as evidence.
Related reading
See it on your data, or start with the checklist.
Either path works. Pick whichever fits where you are today.