The autonomylayer for theappliance line.

Duromex closes the loop from perception to line-and-machine control. It runs at the factory edge, integrates deeply with the systems you already own, and earns autonomy one measured step at a time.

7
agents under one orchestrator
6
connector families
99.9%
uptime target
3
autonomy stages

How a unit moves through Duromex

01

Perceive

Fused vision, thermal, acoustic, pressure-decay, torque-tool, PLC and functional-test streams describe the panel, the surface, the assembly and the leak path on every unit — not a sample.

  • 20–60 camera and sensor streams per line Aspirational
  • Sub-100 ms station decisions where takt demands it Aspirational
  • Every unit carries a serialised perception record
02

Plan

The orchestrator plans the form-and-finish, foam, assemble-and-wire and leak/functional-test sequence for the product actually on the line — including model changeovers.

  • Product, BOM and recipe grounded planning
  • cuOpt line balancing and test sequencing
  • Changeover plans validated in the twin first
03

Act

Adaptive control writes back into the press, the enamel line, the foaming machine, the assembly stations and the testers — within the authority the plant grants.

  • Graduated autonomy: shadow → advisory → control
  • Idempotent steps with fail-safe line stop
  • Every write is scoped, logged and reversible
04

Sense & predict

Surface, weld and assembly defects, foaming voids, refrigerant and water leaks and functional performance are predicted before the tester confirms them.

  • Defect-to-cause attribution upstream
  • Void and density-gradient forecasting
  • Micro-leak signatures below tester thresholds
05

Optimise

First-pass yield, scrap, rework, energy and line balance are optimised continuously across the factory, not tuned once per quarter.

  • First-pass-yield uplift as the primary metric
  • Scrap and rework attributed to a station
  • Energy per unit tracked against the rating
06

Log & retrain

Every action lands in an immutable, assurance-grade quality and safety audit log. Every engineer correction trains the models.

  • Citation-backed, traceable outputs
  • Versioned per-tenant models and memory
  • Warranty outcomes fed back to the corpus

Four layers, one system of action

Every layer is replaceable individually and useless alone. Together they are the reason a press, a foamer and a tester finally behave like one machine.

Perception

Fused vision, thermal, acoustic, pressure-decay, torque-tool, PLC and functional-test streams, serialised to the unit.

  • Station-level inspection at takt
  • TensorRT-optimised edge inference
  • DeepStream and Holoscan sensor fusion

Reasoning

Fine-tuned defect, foam, leak, performance and yield models plus frontier reasoning for process and reliability questions.

  • Model-agnostic router by cost and risk
  • Physics-informed process models
  • RAG over BOMs, recipes and standards

Action

Adaptive write-back into presses, enamel lines, foamers, stations, testers and robots — within granted authority.

  • Idempotent, reversible steps
  • Human-approval checkpoints
  • Fail-safe stop and product handling

Assurance

Grounding, citations, immutable audit logging and twin validation before any change reaches the line.

  • Assurance-grade quality/safety log
  • Evaluation gating in CI
  • Runtime guardrails and schema safety

Every stage of the build, under one loop

Duromex does not stop at inspection. It owns the sequence — form, weld, enamel, foam, wire, test, rate and pack — and optimises across it, because the cause of a test failure almost never lives at the test station.

Form & stampWeld & seamEnamel & paintFoam & insulateWire & assembleLeak & function testRate & pack
PASS · A+++ 1 2 3 4 5 6 7

Decisions happen before the unit advances

Takt time is not negotiable. If a decision arrives after the cabinet has moved on, it is a report, not a control action. That is why Duromex runs inference on the line, not in a distant region.

The edge runtime is written in Rust and C++, deployed on K3s on site, and updated over the air with canary rollout and rollback. The cloud does training, fleet management and cross-site learning — never the time-critical decision.

What runs on site

  • Jetson Orin/Thor class edge inference Aspirational
  • Triton and NIM multi-model serving with per-tenant isolation
  • Local buffering so a WAN outage never stops the line
  • Signed OTA updates with canary and instant rollback
  • Fail-safe stop paths independent of the cloud

Deep write-back, not a read-only dashboard

A read-only integration can only tell you that you already lost the unit. Duromex reads and writes: forming press, paint and enamel line, foaming machine, assembly stations, leak and functional testers, and the appliance MES.

Connectors speak the languages your plant already speaks — REST, OPC UA, MQTT, PLC tags and file drops — and every write is scoped to the authority you granted for that line.

Connector families

  • Forming and stamping presses
  • Paint and enamel lines
  • Foaming machines and jigs
  • Assembly stations and torque tools
  • Leak, functional, performance and energy testers
  • Appliance MES and quality systems

Autonomy is earned in three measured stages

No plant hands control of a press to a vendor on day one. Duromex is designed for the way trust is actually built on a factory floor.

Shadow

The agent watches and predicts while your engineers and testers run the line. Nothing is written. We measure accuracy against your baseline on your product, and publish the gap.

Advisory

The agent recommends forming, foaming and assembly moves and predicts defects, leaks and functional performance. A human approves each action; every correction trains the model.

Graduated autonomy

Low-risk lines and test workflows run under adaptive control with automatic defect and leak triage. Exceptions escalate to a human. Authority is scoped per line and revocable.

Twin-gated change

Recipe, layout and changeover changes are validated in the line-and-product twin before they touch production.

Hit the quality target before the build

The most expensive way to learn that a new model runs badly is to build it. The Omniverse-based line-and-product twin simulates forming, foaming, assembly and functional performance first.

Line simulation

Layouts, robot cells, foaming chambers and test stations simulated before a single fixture is moved.

Product simulation

New product variants and platforms validated for quality, yield and takt before release to production.

Changeover planning

High-mix model changes sequenced and rehearsed so the line does not learn them the hard way.

Synthetic rare faults

Cosmos and Omniverse Replicator generate dent, seam, paint, wiring, foam, leak and robot-cell scenarios you cannot safely collect.

Auto-optimisation

cuOpt optimises line balancing, changeover sequencing, rework routing and tester scheduling against your constraints.

Pre-build acceptance

The twin produces a predicted first-pass yield and takt before the build — the number the plant is actually judged on.

Point tools stop where the loop starts

Every dimension below is the difference between a machine that measures and a system that acts.

DimensionIncumbents & copilotsDuromex
ScopeA single task or toolThe full autonomous loop — a system of action
LoopFixed motion or measurementClosed perceive–decide–act at the factory edge
DataLimited to one machineCompounding cross-factory appliance quality and yield network
IntegrationRead-only or shallowDeep write-back into forming, assembly and test
Change controlTry it on the lineValidated in the line-and-product twin first
OutcomeAssist a humanPerform the work; humans supervise exceptions

What the platform commits to

Reliability, latency and compliance targets that a plant can hold us to.

99.9%

uptime target

<100 ms

station decision latency where takt demands it

60

synchronised sensor streams per line Aspirational

100%

agent actions written to the audit log

Why teams choose the loop over another camera

“Our end-of-line functional testers told us what failed. They never told us which press stroke or foam shot caused it. That link is the whole product.”

Plant Director
Refrigeration OEM · design partner Illustrative

“Foam voids are invisible until the energy rating comes back wrong. Predicting density distribution before the cabinet cures is the part I could not buy anywhere else.”

Process Engineer
Cabinet line · design partner Illustrative

“If it writes to the press, it needs an audit trail a quality auditor accepts. Duromex started there instead of bolting it on.”

Quality & Test Engineer
Laundry OEM · design partner Illustrative

Implementation questions

How long does a first deployment take?

Design-partner deployments target shadow mode on one line within weeks, not quarters, because the wedge is deliberately narrow: one workflow, one line, one metric. Depth comes after the baseline is proven.

What if the network goes down?

The edge keeps running. Inference, control and the audit log are local; the cloud is for training, fleet management and cross-site learning. Buffered telemetry syncs when the link returns.

Can we keep everything on premises?

Yes. An on-prem option exists for sensitive producers, with per-tenant data and model scoping and strict recipe IP protection either way.

How do you avoid breaking a validated process?

Changes are gated: evaluated in CI against golden datasets, validated in the twin, then released under graduated autonomy with a human checkpoint for anything touching safety or warranty.

See the loop close on your line

Bring us your worst first-pass-yield number. We will instrument it in shadow mode and show you what it is actually made of.

Duromex is pre-launch. Figures shown are design-partner targets and modelled economics, not audited results. Ask us for the methodology.