Scenarios

No case study yet. Here is how one would be measured.

Doughex has not run on a bakery line, so there are no results to report. These are scenario walk-throughs built from the product designs: what a pilot would instrument, what it would baseline, and the gate it would have to pass.

Book a plant review See the products

Four scenariosIllustrative, not measuredBaseline from your own records

run_scn_01 · agent graph · scenario 10 nodes · 1 approval gate
01 · orchestrator order.receive ✓ SUCCEEDED 02 · orchestrator twin.simulate ✓ SUCCEEDED 03 · dose_mix mix.dose ✓ SUCCEEDED 04 · ferment_proof proof.hold ✓ SUCCEEDED 05 · makeup_deposit deposit.trim ✓ SUCCEEDED 06 · orchestrator approve.human ◆ APPROVAL 07 · bake_cool bake.zone ✓ SUCCEEDED 08 · defect_inspect inspect.line ✓ SUCCEEDED 09 · robot_handling handle.pack ✓ SUCCEEDED 10 · quality_conf release.genealogy ✓ SUCCEEDED

Illustrative scenario: Plant run · one bread line, flour-lot change at the silo · shared oven. Not a measured run.

Scenarios

Four walk-throughs

Each follows the first-release plan: observe, recommend, then bounded control only after the agreed gates.

Biscuit · depositingGramex QUEUED

Giveaway on a depositing line

Baseline. Grams per unit above declared weight and dollars per shift, plus underweight rate, measured in observe mode over the first weeks from the line's own checkweigher.

Walk-through. Observe mode reads the checkweigher, the depositor and the dough-state sensors while the line runs as usual. Once weight predictions track the checkweigher, recommend mode proposes trim moves that bring the margin down from defensive overshoot to the minimum safe margin. The process engineer approves each move; corrections train the model. Bounded trim follows only after the agreed gates.

Gate. Weight-prediction accuracy versus the checkweigher, then a giveaway reduction that justifies $13,000 per line per month from verified savings.

Bread · ovenOvenix QUEUED

Energy per unit on one tunnel oven

Baseline. Gas and electricity per unit through the oven, crust-colour and crumb-moisture variance, and downgrade from under- or over-bake, from the plant's own meters and QA checks.

Walk-through. Colour and moisture sensing at oven exit feed an as-baked predictor trained on the oven's existing telemetry. Recommend mode proposes zone-temperature and band-speed moves toward the minimum-energy profile while predicted colour and moisture stay inside spec. The core-temperature kill step is verified on every reading and never a candidate for change. The CFD twin follows for envelope discovery.

Gate. Energy per unit and colour variance, with downgrades avoided, against the observe-mode baseline.

Buns · proofingProofa QUEUED

Rise consistency through a flour-lot change

Baseline. Rise variance against the target curve, dense or collapsed product and waste per lot, from the plant's QA records.

Walk-through. Inline height, temperature, humidity and CO2, the recipe and the flour lot feed a rise-curve model. Recommend mode proposes humidity and dwell moves and flags dough running fast or slow early. The head baker's corrections are captured as per-product memory, so the next lot starts from what the last one taught.

Gate. Rise variance and waste against baseline, and a baker who trusts the alerts.

Packing · inspectionVizra QUEUED

Foreign-body and seal escapes on a packing line

Baseline. Escape rate, downgrade and rejects by attributed cause, from the plant's complaint and QA records.

Walk-through. Multi-camera stations run colour, shape, foreign-body and seal models at the plant edge with reject control and an audit log from the first day. Each reject is attributed to an upstream cause and fed back. Synthetic rare defects, validated against the plant's real events, cover what the cameras rarely see. The plant's metal detector and X-ray interlocks stay exactly as they are.

Gate. Escape rate and downgrade against baseline, and an audit log the quality manager can take into a BRCGS audit.

Run timeline

Scenario: one bread line, one flour-lot change

Every Doughex run is an ordered, inspectable sequence. This is run_scn_01, an illustrative scenario: Plant run · one bread line, flour-lot change at the silo · shared oven. Scenario complete · every stage inside spec · one human approval at the oven.

run_scn_01 scenario · not measured SUCCEEDED
  1. 01 order.receive SUCCEEDED 0.8 s

    Plant Orchestrator · Pulled the product spec, the recipe, the HACCP plan with its bake kill-step and metal-detection control points, the allergen status of the line and the new flour lot's certificate from MES and the lab system; locked the target envelope for the run.

  2. 02 twin.simulate SUCCEEDED 38 s

    Plant Orchestrator · Simulated 24 candidate profiles across mix, proof, deposit and oven on the Bakesim as-baked twin for the new flour lot; ranked them on colour and moisture margin, weight margin, energy per unit and takt, and discarded every candidate that thinned the bake kill-step margin.

  3. 03 mix.dose SUCCEEDED 12 m 40 s

    Dose-and-Mix · Adjusted hydration and mix energy for the new lot's absorption so dough temperature and development landed on target; dough state was handed to the proofer with its predicted rise curve.

  4. 04 proof.hold SUCCEEDED 58 m

    Ferment-and-Proof · Predicted the rise curve from inline height, temperature, humidity and CO2, then trimmed proofer humidity and dwell so rise and volume landed on target instead of running fast on the fresher lot.

  5. 05 deposit.trim SUCCEEDED continuous

    Makeup-and-Deposit · Fused checkweigher readings with dough state and divider feedback and trimmed the divider in real time so portion weight sat at the minimum safe margin above the declared weight, with the underweight guardrail armed.

  6. 06 approve.human APPROVAL 1 m 36 s

    Plant Orchestrator · The twin's lowest-energy candidate wanted a zone-three temperature outside the site's bounded envelope. Held for the shift process engineer, who approved the step with a tighter colour alarm.

  7. 07 bake.zone SUCCEEDED continuous

    Bake-and-Cool · Ran the oven against the twin's colour and moisture prediction; stepped zone temperatures and band speed toward the minimum-energy profile while predicted crust colour and crumb moisture stayed inside spec and the core-temperature kill step was verified on every reading.

  8. 08 inspect.line SUCCEEDED continuous

    Defect-and-Inspect · 12 camera streams at oven exit, cooler exit and packing at the plant edge: colour, shape, holes, cracks, foreign-body and seal checks on every unit; two pale-top rejects were attributed to a draught at zone one and the oven agent was notified.

  9. 09 handle.pack SUCCEEDED continuous

    Robot-and-Handling · Robotic depanning, tray transfers and packaging handling paced to the line, with rejected units diverted off the belt and the safe zone around each cell monitored.

  10. 10 release.genealogy SUCCEEDED 1 m 05 s

    Quality-and-Conformance · Lot released: flour lot, recipe, mix and proof setpoints, portion weights, oven profile, kill-step readings, inspection rejects and every human decision written to the genealogy and checked against spec and the HACCP plan.

Tool calls

The tool calls behind the scenario

Every tool invocation, argument and result is written to an immutable, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the plant. The log below is the scenario run, not a measured one.

tool-call stream · run_scn_01
  1. 04:40:02mes.read_order({ line: "BR-2", product: "SANDWICH-800", flour_lot: "F-3312" })
  2. 04:40:02ok spec locked · HACCP plan v6 · CCPs: bake kill step, metal detection
  3. 04:40:03lab.read_results({ lot: "F-3312", test: "flour_certificate" })
  4. 04:40:03ok protein and absorption read · lot accepted at the silo
  5. 04:40:04twin.simulate({ candidates: 24, horizon: "shift" })
  6. 04:40:42ok best profile #7 · kill-step margin held · lowest energy per unit
  7. 04:40:43policy.evaluate({ profile: 7, level: "bounded" })
  8. 04:40:43ok 8 writes permitted · 1 write requires human approval
  9. 04:40:44plc.write_setpoint({ tag: "MIX1.ENERGY", basis: "lot absorption + dough temp" })
  10. 04:53:24ok dough temperature on target · development inside window
  11. 04:53:25plc.write_setpoint({ tag: "PRF1.DWELL", basis: "rise curve + humidity" })
  12. 05:51:30ok rise and volume on target · proof not running fast
  13. 05:51:31plc.write_setpoint({ tag: "DIV1.TRIM", mode: "min_safe_margin" })
  14. 05:51:31ok portion weight at minimum safe margin · underweight guardrail armed
  15. 05:51:33approval.request({ action: "oven.zone3", reason: "outside bounded envelope" })
  16. 05:53:09ok approved by the shift process engineer · tighter colour alarm set
  17. 05:53:10plc.write_setpoint({ tag: "OVN1.ZONE3_T", mode: "min_energy" })
  18. 05:53:10ok predicted colour and moisture inside spec · kill step verified
  19. 05:53:11vision.stream({ cameras: 12, models: ["colour_shape", "foreign_body", "seal"] })
  20. 06:21:48reject: pale top · unit 2231 · attributed to draught at zone one
  21. 06:21:49defect.attribute({ event: "pale_top", cause: "oven.zone1_draught" })
  22. 06:21:49ok oven agent notified · second reject at 06:23:12 · zone one corrected
  23. 06:21:50robot.execute({ cell: "DEPAN-1", mode: "guarded", pace: "line" })
  24. 06:21:50ok depanning and tray transfer paced · rejects diverted · safe zone clear
  25. 08:14:20mes.release_lot({ lot: "BR2-3312", genealogy: "full" })
  26. 08:15:25ok lot released · scenario complete

Reasoning trace

Goal, plan, thought, action, observation, exactly as the orchestrator would record it.

GoalStart flour lot F-3312 on bread line BR-2, hold development, r…

Start flour lot F-3312 on bread line BR-2, hold development, rise, weight, colour and moisture on target through the change, and release the lot with full genealogy.

PlanSimulate the whole profile on the twin first. Lead with the mi…

Simulate the whole profile on the twin first. Lead with the mixer so the proofer gets dough with a known rise curve and the divider gets dough with a known density. Verify the bake kill step continuously. Let the oven chase minimum energy only inside the bounded envelope; hold anything beyond it for a person.

ThoughtThe standing recipe overshoots portion weight and runs the ove…

The standing recipe overshoots portion weight and runs the oven hot to protect against lot variability. With continuous dough-state, weight and colour estimates the margins can sit at their minimum safe values. The saving is giveaway and energy, not safety margin: the kill step is never a candidate for optimisation.

Actiontwin.simulate(candidates=24) → profile #7: minimum safe weight…

twin.simulate(candidates=24) → profile #7: minimum safe weight margin, kill-step margin unchanged, lowest predicted energy per unit.

ObservationProfile #7's zone-three temperature sits outside the site's bo…

Profile #7's zone-three temperature sits outside the site's bounded envelope. The policy engine routes that single write to the shift process engineer and permits the other eight.

ActionExecute profile #7 at the bounded level: mixer, proofer and di…

Execute profile #7 at the bounded level: mixer, proofer and divider writes proceed; the zone-three write waits.

ObservationApproval granted at 05:53:09 with a tighter colour alarm. Two …

Approval granted at 05:53:09 with a tighter colour alarm. Two pale-top rejects at oven exit were attributed to a draught at zone one and corrected by the oven agent.

OutcomeScenario complete. The lot released with flour lot, setpoints,…

Scenario complete. The lot released with flour lot, setpoints, kill-step readings, inspection events and the human decision in the genealogy. No measured plant result is claimed; this is the run the platform is designed to execute.

Method

How we would measure, and what we would exclude

Baseline first

Every pilot starts in observe mode. The baseline comes from the plant's own checkweighers, meters and QA records, never from Doughex telemetry.

One metric

One line, one hard KPI agreed before anything is connected: giveaway, energy per unit, rise variance or escapes.

Gates, not dates

Recommend mode starts when prediction accuracy is proven. Bounded control starts when the food-safety and ROI gates pass. Neither is promised by calendar.

Exclusions

Weight and energy changes driven by product mix or flour supply are separated from the agent's effect using the baseline period's variance.

Design targets

Design targets the scenarios assume

The numbers Doughex is engineered against, from the GPU utilisation plan.

<100 ms reject decisions for inspection at the plant edge
10–60 FPS vision inference per station, depending on the station
8–24 synchronised cameras per high-speed line
1–5 s supervisory control interval for proof, bake and deposit loops
50–200 GPU-hours of fine-tuning per product family per release
100k–1M synthetic rare-event images per defect family, validated before use

Design targets from the GPU utilisation plan. Nothing on this page is a measured plant result; measurements start when the first design-partner line runs in observe mode.

Engagement

How a design-partner engagement runs

Gates, not dates. Each stage starts when the previous one has proven its number against your own baseline.

  1. Design partners. Three to five bakeries instrument the wedge workflow in observe mode. We measure the baseline on waste, giveaway and energy from your own checkweighers, meters and QA records.
  2. Recommend mode. The agent recommends mix, proof or oven moves and predicts bake, weight and foreign-body outcomes; your engineer approves. Accuracy and ROI are proven against the baseline.
  3. Graduated autonomy. Low-risk oven, depositing and inspection loops move to bounded automatic control with adaptive setpoints. Exceptions escalate to a person.
  4. Expansion. Adjacent modules are added within the same bakery, then across sites.
Autonomy

Five levels, set per loop

A bakery does not go from manual to bounded control in one step. Doughex makes the level explicit per loop, auditable and reversible at any time, and some decisions never leave the person.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the person doesWhen
ObservePredicts rise, weight, colour, moisture and defects; writes nothingRuns the bakery as today; compares predictions to QA checksFirst phase with every design partner
RecommendProposes mix, proof, deposit and oven moves with the evidence behind eachA process engineer or baker approves or corrects each oneAfter accuracy is proven against the baseline
Approve to applyPrepares the write; applies it only on a named person's approvalApproves per move; reviews the shift recordOnce recommendations are trusted
BoundedWrites low-risk oven, depositing and inspection setpoints inside explicit limitsApproves anything above the limits; reviews exceptionsAfter the food-safety and ROI gates agreed up front
ExceptionsEscalates anything outside its envelope, CCP-adjacent moves and release decisionsAlways decides these; the agent never doesPermanent
From the plant floor

Who this is built for

The three people in an industrial bakery whose week changes when the line runs itself, and what each of them needs from Doughex.

Economic buyer

Plant or Operations Director

Owns production rate, quality, waste, giveaway and yield, energy and food safety. Wants a bakery that holds spec at higher rate with fewer interventions, and a number that justifies the spend.

Champion

Bakery or Process Engineer

Owns recipes, dough development, proof and oven profiles, process windows and yield. Approves and corrects the agents in recommend mode; those corrections train the models.

Approver

Quality and Food-Safety Manager

Owns HACCP, FSMA, BRCGS, ISO 22000 and allergen conformance, foreign-body and defect conformance, and lot genealogy. Needs every action grounded, cited and written to an immutable record.

IT/OT and sustainability leads approve the deployment. There are no customer quotes on this site yet; design partners will speak for themselves when they choose to.

Guardrails

An agent that can move a setpoint needs a leash

Doughex writes to production equipment in a food plant. Every capability is scoped, every write is policy-checked, every output is cited, and every action is written to an append-only audit log the plant owns.

  • Bounded action space. Each agent can only write to an explicit tag allow-list, inside per-tag rate and magnitude limits, at the autonomy level the plant has set.
  • Critical control points are read, never written. The bake kill step, metal detection and X-ray rejects, allergen changeover and release decisions stay with the HACCP plan and the people who own it.
  • Policy engine before every write. Autonomy level, interlock state, product, allergen status, shift and operator presence are evaluated before a setpoint moves.
  • Grounded and cited. Every recommendation carries a citation to the recipe, spec or procedure it relied on. Retrieval is tenant-isolated and permission-aware.
  • Immutable audit log. Append-only, exportable and retained on the plant's own storage, aligned to HACCP, FSMA, BRCGS and ISO 22000 record-keeping.
  • Hard fallback. If the edge node, the network or a model stops, the line keeps running on its existing PLC and SCADA control and interlocks.
  • Tenant and IP isolation. Recipes, customer specs and tolerance models never cross a customer boundary. On-prem deployment available.

Assurance posture

ItemScopeStatus
SOC 2 Type ICloud control plane QUEUED Roadmap, first 6 months
SOC 2 Type IICloud control plane QUEUED Roadmap, 6 to 12 months
HACCP · FSMA · BRCGS · ISO 22000 · allergenGrounding and record-keeping RUNNING Design basis for retrieval and the audit log
Per-tenant isolationData, memory, models RUNNING Design rule
On-prem deploymentRecipe-sensitive bakeries RUNNING Design option

Doughex supports your food-safety records. It is not a certification and it does not replace your HACCP plan.

Read the security overview

FAQ

Straight answers

The questions plant directors, process engineers and quality managers ask in the first meeting.

Only at the autonomy level your plant has set, and only to an explicit allow-list of low-risk loops inside explicit limits. Every design partner starts in observe mode, where Doughex predicts and writes nothing. Recommend mode follows, where a process engineer approves each move. Bounded autonomy on oven, depositing and inspection loops comes after the food-safety and ROI gates agreed up front.

Get started

Run the real measurement on your line

A scenario becomes a case study when a design partner lets us baseline a line. That is the only way one gets written.

Book a plant review See pricing