What happens if the network or the cloud goes down?

The control loop lives at the mill edge. Inference, guardrails and the audit log run locally on the edge appliance, so a lost uplink degrades reporting and retraining, not machine control. Buffered telemetry syncs when the link returns.

How long does it take to see value?

Design partners start with one wedge line in shadow mode: connectors and telemetry first, then models scored against what the mill actually produced, then assist mode where the agent proposes and an engineer approves. Whole-mill rollout follows once the wedge holds its numbers. Durations depend on how instrumented the mill already is, so we quote them after the assessment, not before.

Do you need our dye recipes and construction library?

To predict recipes well, yes, and that IP never leaves your tenant. Retrieval is multi-tenant isolated, models fine-tuned on your data are yours, and on-prem deployment is available for groups that will not put recipes in any cloud.

How is this different from the inspection system our machine vendor sells?

Vendor inspection tells you a defect happened on one machine. Yarneon closes the loop across the mill: it links the defect to the yarn lot, the loom, the dye bath and the stenter, replans the cut and the schedule, and carries the evidence into the buyer packet.

Can it handle our fabric mix?

The models are conditioned on fibre, blend, construction and finish rather than assuming a single product. Mills running wide mixes see slower cold-start on rare constructions; synthetic data generation is used to cover rare defect and shade cases before they appear in production.

Who owns the models trained on our mill?

You do, for anything trained on your data. Yarneon retains the base models and the platform. Nothing from one tenant is used to train another tenant’s models, and that is contractual, not a policy page.

Frequently asked questions

Questions

Control, safety and autonomy

Both, in that order. Every workflow starts in observe mode, graduates to assist (the agent proposes, a human commits), and only then to bounded auto-control on the specific setpoints you authorise. Autonomy ceilings, approval gates and spend limits are policy objects you own, and every action is reversible and logged.

Tool-call stream

Every call the agent made, in order

Machines, spectrophotometers, the optimiser and the humans are all tools. Calls go out, results come back, and the whole exchange is real, copyable text, the same record your auditor sees.

tool-call stream · RUN-4471

04:02:11 mes.get_lot("DL-4471") → 14 rolls · 3,180 kg · poplin 40s SUCCEEDED

04:02:12 twin.simulate(recipe_candidates=3, machine="jet-07") RUNNING

04:02:58 twin.simulate → best ΔE 0.52 · cycle 118 min · water 46 L/kg SUCCEEDED

04:03:01 colour.predict_recipe(substrate="cotton", standard="19-4028 TCX") RUNNING

04:03:03 colour.predict_recipe → Navy RGB 2.14% · Blue BRF 0.61% · Black B 0.08% SUCCEEDED

04:03:04 policy.check(action="dose", deviation=7.2%) → requires human approval APPROVAL

04:18:22 human.approve(user="colourist-on-shift", decision="approve", note="ok, hold ramp") SUCCEEDED

04:18:24 plc.dose(machine="jet-07", schedule="ramp-B") RUNNING

05:41:07 spectro.read(bath) → exhaustion 96.4% · bath ΔE 0.41 SUCCEEDED

06:22:40 vision.scan(roll=09) → WEFT_STREAK 412–445 m · severity 3 FAILED

06:22:41 cuopt.replan(cut_plan, constraint="ship_thu_0600") RUNNING

06:22:43 cuopt.replan → 33 m to seconds · ship date held SUCCEEDED

06:25:02 quality.release(lot="DL-4471") → 13 Grade A · 1 Grade B · packet signed SUCCEEDED

Guardrail in action

policy.check → requires human approval

At 04:03:04 the proposed recipe deviated 7.2% from the standing card, above the 5% autonomy ceiling for dye dosing at this mill. The agent stopped and asked. Fifteen minutes later a colourist approved it, and that approval is attributed, timestamped and reversible.

APPROVAL GATEAPPROVED 04:18

Failure handled honestly

vision.scan → WEFT_STREAK, roll 09

A 33 m weft streak is a real defect, and the run shows it as failed rather than smoothing it over. The mechanical root cause, a stenter pin-chain slip, was correlated automatically and raised as a work order.

STEP FAILEDRUN RECOVERED

Questions

Data, integration and commercial

A Jetson-class edge device per inspection or control cell, one GPU server per mill for multi-model serving, line-scan cameras where in-line inspection is in scope, and a spectrophotometer feed for colour work. We survey the existing fleet first, most mills already have more sensing than they use.

Agent graph

One run, ten steps, one human decision

This is the shape of a dye lot on Yarneon, shown as an illustrative scenario rather than a customer run. Ingest and simulation fan out, converge on a colourist approval gate, then dosing, verification, finishing, inspection and release. The accent traces the active path; every node opens in the inspector.

RUN-4471 10 steps · 1 approval gate · 1 recovered failure · illustrative scenario COMPLETE

Scroll the graph sideways · or open the text equivalent below

SUCCEEDED APPROVAL FAILED RUNNING

Text equivalent, workflow steps, dependencies and status

Run RUN-4471 workflow graph, as a table
Step	Stage	Depends on	Status	Duration
ingest	conformance	none	SUCCEEDED	0.8s
twin	simulate	ingest	SUCCEEDED	46s
recipe	dye + colour	ingest	SUCCEEDED	2.4s
approve	human gate	twin, recipe	APPROVAL	4m 12s
dose	bath control	approve	SUCCEEDED	118m
shade	verify ΔE	dose	SUCCEEDED	9.1s
finish	stenter	dose	SUCCEEDED	64m
inspect	vision	shade, finish	FAILED	38m
rework	replan	inspect	SUCCEEDED	1.6s
grade	release	rework	SUCCEEDED	3.0s

Parallel branches2twin simulation and recipe prediction run together
Human gates1colourist approval, 15 minutes, attributed
Failures recovered1weft streak on roll 09, replanned in-run

Run timeline

RUN-4471 · Indigo poplin, 3,180 kg, due Thursday

The same scenario run as an ordered timeline: step, status, duration and the tool result behind it. Inspection failed on one roll, the run recovered, replanned the cut and still held the ship date.

RUN-4471 RUN COMPLETE Scenario mill · reactive exhaust jet dyeing · illustrative run, not a customer deployment

Goal: Dye lot DL-4471 · 3,180 kg · 40s combed cotton poplin · shade Indigo 19-4028 TCX · ΔE ≤ 0.8 · due Thu 06:00

01 ingest.lot_state SUCCEEDED 0.8s

Pulls greige genealogy for 14 rolls: yarn lots, loom, greige GSM 138, absorbency and residual size from the prep line.
Agent, input and output
```
agent   Quality-and-Conformance
result  ← 14 rolls · 3,180 kg · mean GSM 138.2 (σ 1.1) · prep OK
```
02 twin.simulate_lot SUCCEEDED 46s

Omniverse fabric-line twin simulates the exhaust curve, machine loading and takt for three candidate recipes before a drop of dye is used.
Agent, input and output
```
agent   Yield-and-Takt
result  ← 3 candidates scored · best predicted ΔE 0.52 · 118 min cycle
```
03 dye.predict_recipe SUCCEEDED 2.4s

Spectral recipe model proposes a 3-dye combination against the buyer standard, corrected for this substrate’s absorbency and the current water hardness.
Agent, input and output
```
agent   Dye-and-Color
result  ← 2.14% Navy RGB · 0.61% Blue BRF · 0.08% Black B · salt 62 g/L
```
04 human.approve_recipe APPROVAL 4m 12s

Recipe deviates >5% from the standing card, so autonomy is capped: the colourist approves, rejects or edits before any dosing. Guardrail policy MILL-02/DYE-APPROVAL.
Agent, input and output
```
agent   Dye-and-Color
result  → awaiting colourist · approved on shift 04:18
```
05 dye.control_bath SUCCEEDED 118m

Closed-loop dosing and ramp control against live bath spectrophotometry; two mid-cycle corrections applied when exhaustion ran 4% ahead of model.
Agent, input and output
```
agent   Dye-and-Color
result  ← exhaust 96.4% · 2 corrections · bath ΔE 0.41 at drain
```
06 shade.verify_lot SUCCEEDED 9.1s

Per-roll spectral read against Indigo 19-4028 TCX under D65/TL84/A; metamerism scored and rolls sorted into shade bands.
Agent, input and output
```
agent   Shade-and-Quality
result  ← mean ΔE 0.58 · 13 rolls band A · 1 roll band B
```
07 finish.control_stenter SUCCEEDED 64m

Stenter chemistry, overfeed and curing profile set to hold hand, 148 cm width and residual shrinkage under 3%.
Agent, input and output
```
agent   Finish-and-Hand
result  ← width 148.3 cm · shrink 2.1% warp / 1.4% weft
```
08 inspect.scan_rolls FAILED 38m

In-line vision flags a recurring 6 cm weft streak on roll 09 between 412 m and 445 m, traced to a stenter pin-chain slip, not a dye fault.
Agent, input and output
```
agent   Defect-and-Inspect
result  ← 1 defect cluster · roll 09 · 33 m affected · class WEFT_STREAK
```
09 plan.rework_route SUCCEEDED 1.6s

cuOpt re-plans the cut and rework route: 33 m diverted to seconds, remaining 14,890 m re-sequenced so the buyer’s Thursday ship date still holds.
Agent, input and output
```
agent   Yield-and-Takt
result  ← 33 m to seconds (0.22%) · ship date held
```
10 quality.grade_and_release SUCCEEDED 3.0s

Four-point grading, roll genealogy and the conformance packet (AATCC 61, ISO 105-C06, ZDHC MRSL declaration) are assembled and released to the buyer portal.
Agent, input and output
```
agent   Quality-and-Conformance
result  ← 13 rolls Grade A · 1 roll Grade B · packet signed
```

RUN OUTCOME

Lot released first time, on shade, on date.

Result of run RUN-4471
Measure	Value	Context
Final mean ΔE	0.58	against a 0.80 tolerance
Re-dyes avoided	1	the standing card would have missed shade
Seconds	0.22%	versus the scenario mill baseline of 1.9%
Water used	46 L/kg	versus 59 L/kg on the scenario recipe card
Human decisions	1	the recipe approval gate

Why this matters

A mill does not fail on the good lots. It fails on the lot where the substrate drifted, the recipe card was wrong, and nobody found out until the buyer opened the carton. Yarneon makes that lot legible while it is still in the machine.

Reasoning trace

The reasoning, written down

Goal, observation, plan, action, decision, handoff, outcome. A colourist can read this and disagree with it, which is the point. Autonomy a mill cannot argue with is autonomy a mill will not adopt.

Goal01 / 10

Land DL-4471 on Indigo 19-4028 TCX within ΔE 0.80, first time, before the Thursday 06:00 ship cut-off.
Observation02 / 10

Greige absorbency for this lot reads 8% above the card baseline, and incoming water hardness is 142 ppm, both push the exhaust curve faster than the standing recipe assumes.
Plan03 / 10

Simulate three recipes in the fabric twin before committing dye. Prefer the candidate with the lowest predicted ΔE that also fits the 118-minute machine slot.
Action04 / 10

twin.simulate(recipe_candidates=3, machine="jet-07")
Observation05 / 10

Candidate B predicts ΔE 0.52 and finishes 6 minutes inside the slot. Candidates A and C either overshoot shade or miss takt.
Decision06 / 10

Candidate B deviates 7.2% from the standing card, above the 5% autonomy ceiling for dye dosing. Escalate to the colourist rather than act.
Handoff07 / 10

Dye-and-Color → the colourist on shift, with the simulated curve, the deviation reason and a one-click revert attached.
Action08 / 10

plc.dose(machine="jet-07", schedule="ramp-B") after approval, with two mid-cycle corrections when exhaustion led the model by 4%.
Observation09 / 10

Vision flags a 33 m weft streak on roll 09 after finishing. Correlating stenter telemetry shows a pin-chain slip at 04:51, a mechanical cause, not a dye fault.
Outcome10 / 10

Lot released at mean ΔE 0.58 with 0.22% seconds. A maintenance work order is raised against the stenter pin chain, and the streak signature is added to the mill’s defect memory.

Human in the loop

Craft is captured, not replaced

Textile mills run on scarce craft: the colourist who knows this jet runs hot, the weaving master who hears a beam going wrong. That knowledge is retiring faster than it is being replaced.

Yarneon writes it down. Every approval, override and correction becomes per-mill memory scoped to your tenant, so the mill keeps improving after the person who taught it has gone home.

Per-colourist and per-operator performance memory
Overrides captured as training signal, not noise
Versioned memory, scoped per tenant, never shared across mills

Guardrails

An agent earns the right to touch a machine

Nothing here is a global "AI on" switch. Autonomy is granted per setpoint, bounded by policy, reversible by any operator and logged permanently.

Graduated autonomy: Every workflow moves observe → assist → bounded auto-control. Autonomy ceilings are per-setpoint policy, not a global switch.
Human-in-the-loop gates: Approval gates fire on deviation thresholds, new substrates, or any action outside the authorised envelope. Approvals are attributed and time-stamped.
Reversibility: Every control action ships with a revert path and a last-known-good setpoint. Operators can take manual control at any moment, from the HMI or the panel.
Immutable audit log: Assurance-grade, append-only record of every observation, decision, tool call, approval and actuation, exportable for buyer and regulatory audit.
Tenant isolation: Recipes, construction libraries and roll data are isolated per tenant. No cross-tenant training. Permission-aware retrieval with enforced citations.
Sandboxed tools: Agents call machines through a typed, scoped tool layer with rate and range limits. There is no path from a model output to an unbounded PLC write.

Read the security model

Compliance posture

The certifications buyers and auditors ask for

Textile buyers audit chemistry, labour and traceability. Enterprise IT audits everything else. Both get evidence rather than assurances.

SOC 2 Type I
In progress ASPIRATIONAL, Type II planned
ISO 27001
In progress ASPIRATIONAL
GDPR
Aligned
IEC 62443
OT security alignment
ZDHC MRSL
Reporting supported
OEKO-TEX / bluesign
Evidence export

Items marked ASPIRATIONAL are in progress and are stated as such deliberately. We would rather be boring about this than surprising.

Deployment

From first connector to bounded control, one phase at a time

No mill hands over a jet on day one. The path is deliberately slow at the start and faster once the numbers hold. Durations are quoted after the assessment, because they depend on how instrumented the mill already is.

Phase 1

Connect

Mill survey, edge appliance install, connectors to machines, MES and meters. Telemetry starts flowing; nothing is controlled.
Phase 2

Observe

Models run in shadow against live production. Predictions are scored against what the mill actually produced, on your data.
Phase 3

Assist

The agent proposes; a human commits. Approval gates, setpoint envelopes and revert paths are agreed with the process owners.
Phase 4

Control

Bounded auto-control on the setpoints you authorise, one at a time, with autonomy ceilings that you can lower at any moment.

Trust signals

What the runs actually produce

No customer results are published yet. These are platform facts and plan terms from our own documents. Outcomes will be measured against each mill’s own trailing twelve months, in shadow mode before anything is controlled.

9

Mill agents, one per stage, from spinning to release.

6

Products in the loop: Vireon, Spindra, Loomix, Shadeon, Doffex and Twinly.

3 to 5

Design partners we are onboarding first, one wedge workflow each.

$14k

Per line per month on the Line plan. Mill and Enterprise sit above it.

Items marked ASPIRATIONAL are design targets ahead of production validation.

Integrations

It speaks to the machines you already own

Yarneon is not a rip-and-replace. It connects to the looms, frames, jets, stenters, cameras, spectrophotometers and MES already on your floor.

Loom & knit controllers

Picanol, Toyota, Tsudakoma, Karl Mayer and Mayer & Cie controllers over OPC UA and vendor PLC tags.

Spinning frames

Rieter, Trützschler, Saurer and Murata frames, draft, twist, speed and end-break telemetry.

Dyeing & finishing

Thies, Fongs, Brazzoli jets and Monforts/Brückner stenters via PLC, recipe systems and dosing units.

Colour & lab

Datacolor and X-Rite spectrophotometers, colour libraries, Pantone TCX standards and lab-dip workflows.

Inspection hardware

Line-scan RGB and NIR cameras, Uster and Elbit inspection frames, existing light boxes.

MES / ERP

SAP, Datatex, TIM, Coats Digital and homegrown mill MES over REST, files and database CDC.

Utilities & sustainability

Water, steam and electricity meters; ZDHC Gateway, Higg FEM and OEKO-TEX reporting.

Robotics

Vision-guided manipulators and AMRs on NVIDIA Isaac and Jetson for doffing, beams and roll transport.

Vendor names are listed for compatibility reference only and do not imply endorsement or partnership.

Pricing

Land on one line. Expand across the mill.

Priced per line, per mill or per group, with outcome-based components on the workflows where the value is measurable.

Line

$14,000 per spinning, weaving/knitting or dye line, per month

Mills validating ROI on a single wedge workflow.

One agent workflow on one line, yarn/fabric control, dyeing, or inspection
Mill-edge inference appliance and connector for that line
Run timeline, tool-call log and immutable audit trail
Assist mode with human approval on every control action
Standard email and shared-channel support, 1 business-day response

Start with Line

Mill

Full loop

$90,000 per mill, per month

Scaling mills adopting the full perceive–decide–act loop.

All nine agents: spin, weave/knit, dye, finish, defect, shade, yield/takt, robotics, conformance
As-produced fabric digital twin with pre-run simulation
Graduated autonomy with per-workflow approval policies and spend limits
Mill-edge fleet management and offline fallback control
Roll genealogy, buyer conformance packets and sustainability reporting
Named mill engineer and quarterly outcome review

Start with Mill

Enterprise

Custom typical land $650k–$8.5M ACV

Integrated textile groups standardising on Yarneon.

Multi-site deployment with group-level benchmarking
Custom fibre, construction and shade models trained on your archive
On-prem or private-VPC deployment via NVIDIA AI Enterprise
SSO, SCIM, RBAC, data residency and signed SLAs
Outcome-based commercial components on yield, seconds, re-dyes and utilities
Dedicated solutions team and 24×7 support

Talk to sales

Annual prepay saves 15 to 20% depending on term. Full detail, including outcome-based terms, on the pricing page.

Still not answered?

Send the hard version of your question. We answer engineering questions with engineering answers.

Contact us Read the docs

The questions mills actually ask