Drawing, stranding, extrusion
Lines shipped Draweon-ready, with the controller tags and limits declared at the factory. The agent runs on the OEM line; the OEM keeps the machine relationship.
Partners
The channel is the machinery.
Draweon's distribution plan runs through the companies already on the plant floor: drawing, stranding, extrusion and inspection machinery OEMs, MES vendors and the integrators who connect them. The programme opens with the design-partner cohort; nothing here is a signed partnership.
Illustrative scenario: EX-3 · 2.5 mm² class 2 PVC building wire, changeover, no spark faults
Partner types
Who fits, and how
How each kind of partner fits the plan.
Laser, eddy-current, spark, vision
Gauge and tester data fused into Eddix. The vendor keeps the measurement; Draweon adds the prediction and the upstream correction.
Orders, genealogy, quality
Reel and length genealogy written back into the system of record. Evidence packets for customer and regulatory review.
OT and plant networks
Connection, tag inventory and the shadow-mode weeks of a pilot, delivered by people the plant already trusts.
Design partners
The first three to five plants shape the roadmap and get written access terms. See the customers page.
UL, IEC, IPC, USCAR
Keeping the reasoning layer's citations current as standards change.
How it works
What a partner does and gets
The outline of the programme as planned.
A partner does
- Declares the tags, limits and interfaces on the systems they ship or support
- Co-delivers the shadow-mode and assist-mode weeks of a pilot
- Brings a plant with a metric and a signed baseline
A partner gets
- A Draweon-ready designation for the line, gauge or MES, once the connector is proven
- A share of the Line and Plant subscription on plants they bring
- Early access to the SDK and the twin for their own engineering
Integrations
It speaks line, not cloud
Draweon reads and writes through the systems already on the floor. No rip and replace, no parallel historian, no new HMI to learn. Vendor names are examples of systems found on cable lines; connector availability is confirmed per site.
PLC and SCADA on drawing, stranding and extrusion lines (Siemens, Rockwell and OEM controllers)
Setpoint reads and guarded writes
Laser gauges and X-ray wall scanners (Sikora, Zumbach, Beta LaserMike and NDC class systems)
Wall, diameter, eccentricity traces
Eddy-current heads and spark testers
Fault events with length position
Line-scan and area cameras on the line
Frames for lumps, neckdowns, surface faults
Rod breakdown, intermediate and fine drawing, annealers (Niehoff and Properzi class lines)
Tension, die force, annealer current, conductivity
Bunchers, planetary, rigid and tubular stranders (Gauder, Pourtier, Nextrom class lines)
Payoff tension, take-up, lay, geometry
Insulation and jacket lines (Maillefer, Rosendahl Nextrom, Troester, Davis-Standard class lines)
Screw, zones, melt pressure, cooling
Cable MES, quality systems and in-house records
Orders, constructions, reel genealogy
Run timeline · scenario
One scenario run, step by step
Every Draweon run is an ordered, inspectable sequence. This is run_3d7a1e on EX-3 · 2.5 mm² class 2 PVC building wire. Scenario completes in 10 steps with one approval gate. Wall settles at 0.80 mm nominal, minimum 0.66 mm, concentricity 0.93, no spark faults, reel R-30417 released with full genealogy.
run_3d7a1e
EX-3 · 2.5 mm² class 2 PVC building wire
illustrative scenario
SUCCEEDED
-
01
ingest.order
SUCCEEDED
0.6 s
Plant Orchestrator · Pulled the construction spec for 2.5 mm² class 2 PVC building wire from MES: 7 × 0.67 mm conductor, 0.80 mm nominal wall, 0.62 mm minimum spot wall, 6 kV spark test, 48 km order. Locked the target envelope.
-
02
twin.simulate
SUCCEEDED
41 s
Line Twin · Simulated 36 candidate recipes on the as-run line twin for draw schedule, lay length and extrusion setpoints, ranked on wall variance, concentricity, predicted spark risk and polymer give-away.
-
03
draw.tension
SUCCEEDED
1 m 48 s
Draw-and-Anneal · Capstan tension on RB1 stepped down 6% as the die-wear estimate crossed its threshold. Diameter held at 0.670 mm ± 0.004 mm and the break-risk score fell from 0.31 to 0.09.
-
04
anneal.current
SUCCEEDED
54 s
Draw-and-Anneal · Annealer current trimmed against the live conductivity reading to hold the softness target without over-anneal through the speed change.
-
05
strand.lay
SUCCEEDED
1 m 12 s
Strand-and-Cable · Lay length set to 28 mm on bunching line ST2 with payoff tension balanced across 7 spools. Roundness index held above 0.97 into the extrusion payoff.
-
06
extrude.wall
SUCCEEDED
2 m 36 s
Insulate-and-Jacket · Screw speed and zone 3 temperature re-cut against melt pressure and material-lot moisture. Wall settled at 0.80 mm nominal, minimum 0.66 mm, concentricity 0.93.
-
07
inspect.fuse
SUCCEEDED
continuous
Defect-and-Inspect · 6 cameras, the laser gauge, the eddy-current head and the spark tester fused at the edge. One neckdown precursor at 12,480 m flagged and cleared by a screw-speed trim before it reached the reel.
-
08
approve.human
APPROVAL
38 s
Plant Orchestrator · Line-speed ramp 1,100 to 1,250 m/min exceeded the site autonomy threshold. Held for the shift process engineer and approved at 06:41:52.
-
09
reel.change
SUCCEEDED
2 m 05 s
Robot-and-Handling · Reel change on take-up TU3 planned and executed by the handling robot. Payoff aligned and tension re-established inside the changeover window.
-
10
reel.release
SUCCEEDED
1 m 10 s
Quality-and-Conformance · Reel R-30417 released: genealogy written (conductor lot, draw and anneal record, lay, wall and concentricity trace, defect map, approvals) and checked against the construction spec.
Accelerated computing
Physical AI, at the die train
Conductor moves at over a thousand metres a minute. Perception has to be local, deterministic and fast, so Draweon runs GPU inference at the plant edge and keeps training, simulation and optimisation in the cloud or on-prem.
Edge perception
4 to 12 cameras per line plus laser, eddy-current and spark streams fused at the line. Sub-50 ms alerting and sub-250 ms bounded control are the design targets. Jetson Thor is planned for higher sensor density.
Model serving
Vision, time-series, anomaly and quality models behind one orchestrator at the plant edge, with canary rollout by line and fallback to the previous validated version.
Training
Defect classifiers, sensor-fusion models, time-series prognostics and cable-process reasoning models trained on reel telemetry and engineer corrections. Dedicated training capacity is planned.
Line twin
As-run drawing, stranding, extrusion, thermal and tension simulation. Physics-informed surrogates are planned so recipes can be optimised at production cadence.
Synthetic data
Rare spark, pinhole, eccentricity, neckdown and break variants generated and validated against real gauge, spark and vision distributions before promotion. Planned.
Optimisation
Line sequencing, reel changeovers, energy allocation, takt and constrained setpoint proposals.
Robot handling
Spool, reel and payoff and take-up motion planned and validated in simulation before it runs next to moving conductor.
FAQ
Straight answers
The questions plant directors and process engineers ask in the first meeting.
Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, and only at the autonomy level your plant has set. Level 1 is advisory: Draweon recommends and a human enters everything. Design partners start there, in shadow mode, before supervised writes.
Control returns to the line controller's last known-good state. Draweon is a supervisory layer on top of the PLCs and gauges you already run, never a replacement for them, so an outage degrades the line to its current way of running, not to a stop.
Advisory recommendations start from the physics-based twin and the construction spec in the first weeks. Defect prediction and break prediction improve as line history and labelled events accumulate per construction. The first training sets are sized at 5 to 20 million labelled frames and events, a design target.
Only if you choose cloud training. Recipes, process models and defect libraries are isolated per tenant and never used to train another customer's models. A fully on-prem deployment at the plant edge is available for sensitive producers.
You are, the same as with any control strategy, which is why every write is policy-checked, bounded, logged and reversible, and why anything above your risk threshold waits for a named approver. The audit log records the request, the reasoning, the limits applied and the human decision.
A paid pilot on one line, scoped to a single workflow with a baseline agreed in writing. Weeks 1 to 3 are connection and shadow-mode observation, weeks 4 to 8 are assist mode with engineer approval, and bounded autonomy follows if the plant is satisfied with the recommendations.
Get started
Talk about partnering
Tell us what you ship or support and which plants run it.