Circuit layouts generated in one step instead of drawn by hand
Heat-Exchanger Circuit Router
Generates refrigerant circuit (CKT) routing layouts for fin-and-tube heat exchangers from the coil grid, target circuits, parity, flow direction and dummy holes. It applies the design team's bend, drainage and coverage rules, balances circuit sizes across the face, and exports an SVG/PDF reference with every run saved for audit and reuse.
CKT view · 20 × 8 coilFront bendRear bend20 circuits · 160 / 160 holes
Outcomes
What changes on your line.
Design rules enforced on every layout, with deviations explained
Every run stored with inputs and output for traceability
Inputs
What the engineer enters
- Vertical holes (rows) & hole columns
- The front-face grid of the coil
- Target circuits & minimum holes per circuit
- How many circuits, and the smallest allowed
- Parity
- Even, odd or any: even circuits exit on the front face, odd on the rear
- Circuit direction
- Incline (upward flow, evaporator and water coils) or decline (downward flow, condensers)
- Dummy holes
- Holes excluded from every circuit, marked by clicking the grid
Design rules
Design rules enforced on every run
- Every bend joins a true neighbour on the staggered lattice: no long skip bends, and no bends cross
- Circuits stack as compact horizontal bands that only step in the flow direction, so there are no traps
- A wrong-way move is at most a single half-pitch dip, never in the final two steps
- Circuit sizes are interleaved across the face, not clustered
- If the exact target can't be met, the count is reduced and the deviation is explained
- Isolated holes are offered as suggested dummies, applied in one click
Integrations
What it connects to.
Coil grid & design inputs
SVG / PDF export
Run history & audit log
Engineer review
Data residency
Your data, your residency.
AI that runs within your firewall, with your total control. On-premise or private cloud is your call, and we engineer for either.
Edge gateways
Inference next to the camera or sensor, for sub-second decisions at the station.
On-premiseLine-side compute
One compact node per line, running inspection, counting and monitoring together.
On-premisePrivate plant servers
Central models, dashboards and the copilot, inside your own network and under your own IT policies.
On-premisePrivate cloud
Your own cloud tenancy, inside your security perimeter, when that suits your IT strategy better.
Private cloud
From pilot to production
From scoping call to a working pilot.
01
Assess & Design
A scoping call and a short plant walk-through to pick one line, one asset or one workflow, define success metrics, and confirm data access.
02
Pilot & Validate
A working pilot on your line within 4–8 weeks, validated against the agreed metrics with a measurable business case.
03
Scale & Govern
Roll out across lines and plants with qualification protocols, audit trails and change-control governance.
Related
Related programs.
P-04·Agentic / copilot
Production Planning
Improved on-time delivery against customer commitments
View program
P-01·Computer vision
AI Visual Inspection
Reduced escaped-defect rate and less end-of-line manual sampling
View program
P-02·Computer vision
Packaging & Bin-Count Verification
Miscounts caught at the packing station in seconds, not at the customer dock
View program