Group autonomy policy
One policy model for the group with per-site override and approval chains. Tag allow-lists and limits reviewed and versioned like code.
Enterprise
One policy. Every line. Every plant.
Multi-site wire and cable groups standardise on Draweon for the governance as much as the control: one autonomy policy with per-site override, one audit trail, fleet-managed plant-edge nodes, and conductor, insulation and tolerance models that stay private to each plant.
Illustrative scenario: EX-3 · 2.5 mm² class 2 PVC building wire, changeover, no spark faults
Enterprise features
What the Enterprise tier adds
Items marked planned follow the 6 to 12 month roadmap.
SSO, SCIM and tag-level RBAC
Named approvers, role-based access down to the tag. Planned for the 6 to 12 month release.
Plant-edge fleet management
Model versions promoted by line with canary rollout and automatic fallback across every plant. On-prem and air-gapped options.
Custom conductor, insulation and tolerance models
Per-site process models built on the plant's own constructions and kept private to that tenant.
Cross-plant benchmarks
Scrap, give-away, breaks, energy and first-pass quality compared across plants without moving recipes across tenant boundaries. Data-network tiers are planned.
Dedicated engineer, SLAs
A dedicated deployment engineer, quarterly model review per plant and SLA terms set per agreement.
Deployment
Where it runs
The plant edge is always local. The control plane can be cloud, on-prem or absent.
| Option | Plant edge | Control plane | For |
|---|---|---|---|
| Cloud control plane | Jetson nodes at the line | Draweon cloud, per-tenant isolation | Most plants; cloud training optional |
| On-prem control plane | Jetson nodes at the line | In the plant's data centre | Sensitive producers, strict IP controls |
| Air-gapped | Jetson nodes at the line | In the plant, no external link | Defence and specialty constructions |
| Edge-only degradation | Returns to controller last known-good | Unreachable | What happens on any control-plane loss |
Enterprise
Standardise autonomy across the group
One policy model, one audit trail, one benchmark across every line in every plant, with the conductor, insulation and tolerance models kept private to each site.
- SSO and role-based access down to the tag level, planned for the 6 to 12 month release
- Group-wide autonomy policy with per-site override and approval chains
- Cross-plant benchmarking on scrap, give-away, breaks, energy and first-pass quality
- On-prem and plant-edge deployment, with air-gapped operation for sensitive producers
- Edge autonomy that survives control-plane loss by returning to the controller's last known-good state
- Dedicated deployment engineer and quarterly model review per plant
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.
Guardrails
An agent that can move a screw speed needs a leash
Draweon writes to production equipment. Every capability is scoped, every write is policy-checked, and every action is written to an append-only audit log the plant owns.
- Bounded action space. Each agent writes only to an explicit tag allow-list, inside per-tag rate and magnitude limits.
- Policy engine before every write. Autonomy level, shift, construction, interlock state and operator presence are evaluated before a setpoint moves.
- Human-in-the-loop gates. Anything above the site threshold, such as line-speed ramps, die changes and reel release, waits for a named approver.
- Immutable audit log. Append-only and exportable. Every action records source signals, retrieved procedures, predicted impact, allowed range, rollback condition, approver and reel scope.
- Hard fallback. Loss of the edge node, the network or a model returns control to the line controller's last known-good state.
- Tenant and IP isolation. Construction recipes, defect libraries and process memory never cross a customer boundary. On-prem deployment is available for sensitive producers.
Compliance posture
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | QUEUED Planned, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Planned, 6 to 12 months |
| SSO and RBAC | Console and approvals | QUEUED Planned, 6 to 12 months |
| Standards-cited reasoning | UL, IEC, IPC, USCAR documents | RUNNING In the design, every answer cites its source |
| Per-tenant isolation | Recipes, models, memory | RUNNING In the design from day one |
| On-prem and plant-edge deployment | Sensitive producers | RUNNING Design option |
Autonomy
Four levels, set per agent and per tag
A plant does not go from manual to unattended in one step. Draweon makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then graduated autonomy.
| Level | What the agent does | What the human does | Where it sits in a pilot |
|---|---|---|---|
| L1 · Advisory | Recommends setpoints and explains why, with citations | Enters every change manually | Shadow mode, weeks 1 to 3 |
| L2 · Supervised | Proposes a write; it executes on approval | Approves each write in the review console | Assist mode, weeks 4 to 8 |
| L3 · Bounded | Writes inside tag, rate and magnitude limits | Approves ramps, die changes and reel release | Graduated autonomy, from week 9 if the plant is satisfied |
| L4 · Unattended | Runs the envelope without prompting | Sets the envelope; reviews the shift record | Planned; after qualification on the construction |
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
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
Standardise the group
Start with one drawing, stranding or extrusion line and one measurable baseline. A paid pilot on wall and concentricity, break prediction or spark prediction shows the number before you commit further.