Scenarios

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

Milkeon has not run on a plant, 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 intake.receive ✓ SUCCEEDED 02 · orchestrator twin.simulate ✓ SUCCEEDED 03 · intake_separate separate.standardize ✓ SUCCEEDED 04 · pasteurize_homog pasteurize.verify ✓ SUCCEEDED 05 · ferment_culture culture.vat ✓ SUCCEEDED 06 · evaporate_dry dry.spray ✓ SUCCEEDED 07 · defect_inspect inspect.pack ✓ SUCCEEDED 08 · hygiene_cip cip.schedule ✓ SUCCEEDED 09 · orchestrator approve.human ◆ APPROVAL 10 · quality_conf release.genealogy ✓ SUCCEEDED

Illustrative scenario: Plant run · skim-milk-powder line + set-yogurt line · shared intake. Not a measured run.

Scenarios

Four walk-throughs

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

Fluid milk · standardizationSepion QUEUED

Give-away on a standardization line

Baseline. Fat and protein give-away in liters and dollars per shift, and composition variance against lab, measured in shadow mode over the first weeks.

Walk-through. Shadow mode reads the plant's inline NIR and mid-IR, the separator and the lab system while the line runs as usual. Once composition estimates track lab results, assist mode proposes blend-valve moves that bring the margin down from defensive over-standardization to the minimum safe margin. The technologist approves each move; corrections train the model. Bounded control follows only after the agreed gates.

Gate. Composition accuracy versus lab, then a give-away reduction that justifies $14,000 per line per month from verified savings.

Milk powder · spray-dryingAridyn QUEUED

Energy per kilogram on one dryer

Baseline. Energy and water per kilogram of powder, outlet moisture variance and fouling wash-outs, from the plant's own meters and lab.

Walk-through. A surrogate predictor of outlet moisture and solubility is trained on the dryer's existing telemetry and reconciled against lab results. Assist mode proposes inlet temperature and feed-solids moves toward the minimum-energy setpoint while predicted moisture stays inside spec. Fouling and stickiness prognostics give lead time to avoid a wash-out. The CFD twin follows for envelope discovery.

Gate. Energy per kilogram and moisture variance, with downgrades avoided, against the shadow-mode baseline.

Yogurt · fermentationCulvex QUEUED

Acidification trajectory on a set-yogurt line

Baseline. pH variance against the target curve, first-pass quality and downgrades, per culture lot.

Walk-through. Inline pH and temperature, the make-milk composition and the culture lot feed a trajectory model. Assist mode proposes temperature-profile and hold-timing moves and flags abnormal acidification early. The cheesemaker's or technologist's corrections are captured as per-product memory, so the next batch starts from what the last one taught.

Gate. pH variance and first-pass quality against baseline, and a technologist who trusts the alerts.

Packaging · inspectionVizra QUEUED

Seal and foreign-body escapes on a filling line

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

Walk-through. Multi-camera stations run fill, seal, cap and label 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. Robotic handling follows after safety validation.

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

Run timeline

Scenario: one tanker lot, two streams

Every Milkeon run is an ordered, inspectable sequence. This is run_scn_01, an illustrative scenario: Plant run · skim-milk-powder line + set-yogurt line · shared intake. Scenario complete · both streams inside spec · one human approval at the dryer.

run_scn_01 scenario · not measured SUCCEEDED
  1. 01 intake.receive SUCCEEDED 0.9 s

    Plant Orchestrator · Pulled both product specs, the HACCP plan with its pasteurization critical control point, the antibiotic screen for the tanker lot and the standing CIP window from MES and the lab system; locked the target envelope for the run.

  2. 02 twin.simulate SUCCEEDED 41 s

    Plant Orchestrator · Simulated 24 candidate recipes across separation, pasteurization, evaporation and spray-drying on the Lactwin as-processed twin; ranked them on composition margin, pasteurization margin, energy per kilogram of powder and takt, and discarded every candidate that thinned the pasteurization margin.

  3. 03 separate.standardize SUCCEEDED 3 m 05 s

    Intake-and-Separate · Fused inline NIR and mid-IR with the latest lab calibration, then trimmed the cream-skim split and the standardization blend valve so skim solids and the yogurt-stream fat sat at target with the minimum safe margin rather than the usual over-standardization.

  4. 04 pasteurize.verify SUCCEEDED continuous

    Pasteurize-and-Homogenize · Held HTST at or above 72 °C for 15 s through the holding tube with the flow-diversion valve armed; every critical control point reading was written to the audit log against the HACCP plan.

  5. 05 culture.vat SUCCEEDED 4 h 20 m

    Ferment-and-Culture · Predicted the acidification curve for the culture lot from inline pH and the upstream composition, held the vat temperature profile and timed the hold so pH landed on the set-yogurt target curve; no abnormal acidification was flagged.

  6. 06 dry.spray SUCCEEDED 2 h 10 m

    Evaporate-and-Dry · Ran the dryer against the twin's moisture and stickiness prediction; stepped inlet temperature and feed solids toward the minimum-energy setpoint while predicted outlet moisture stayed inside spec and fouling risk stayed low.

  7. 07 inspect.pack SUCCEEDED continuous

    Defect-and-Inspect · 16 camera streams across the two packing lines at the plant edge: fill, seal, cap and label checks on every unit, foreign-body and contamination models on the powder stream; two rejects were attributed back to a seal-jaw temperature drift and the packing line was notified.

  8. 08 cip.schedule SUCCEEDED 6 s

    Hygiene-and-CIP · Placed the pasteurizer and dryer CIP into the cheapest energy window, sequenced wash phases against tank availability and set the release checks that must pass before the next product.

  9. 09 approve.human APPROVAL 1 m 48 s

    Plant Orchestrator · The twin's lowest-energy candidate wanted a dryer inlet temperature above the site's bounded envelope. Held for the shift dairy technologist, who approved the step with a tighter outlet-moisture alarm.

  10. 10 release.genealogy SUCCEEDED 1 m 12 s

    Quality-and-Conformance · Both batches released: composition, CCP records, culture lot and pH curve, drying setpoints, inspection rejects and every human decision written to the batch genealogy and checked against spec.

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. 05:10:02mes.read_order({ lot: "T-0417", products: ["SMP", "SET-YOG"] })
  2. 05:10:02ok specs locked · HACCP plan v7 · CCP: pasteurization 72 °C / 15 s
  3. 05:10:03lab.read_results({ lot: "T-0417", test: "antibiotic_screen" })
  4. 05:10:03ok negative · lot accepted for intake
  5. 05:10:04twin.simulate({ candidates: 24, horizon: "shift" })
  6. 05:10:45ok best recipe #9 · pasteurization margin held · lowest energy per kg
  7. 05:10:46policy.evaluate({ recipe: 9, stage: "bounded" })
  8. 05:10:46ok 7 writes permitted · 1 write requires human approval
  9. 05:10:47plc.write_setpoint({ tag: "SEP1.BLEND_VALVE", basis: "nir+midir+lab" })
  10. 05:13:52ok skim solids on target · yogurt-stream fat at minimum safe margin
  11. 05:13:53plc.verify_ccp({ tag: "PAST1.HOLD_TUBE", min: "72 °C / 15 s" })
  12. 05:13:53ok CCP verified · divert valve armed · readings → audit log
  13. 05:14:10dose.culture({ vat: "Y2", lot: "C-2291", profile: "set-yogurt" })
  14. 05:14:10ok acidification curve predicted · hold timed to target pH
  15. 05:14:12approval.request({ action: "dryer.inlet", reason: "above bounded envelope" })
  16. 05:16:00ok approved by the shift dairy technologist · tighter moisture alarm set
  17. 05:16:01plc.write_setpoint({ tag: "DRY1.INLET_T", mode: "min_energy" })
  18. 05:16:01ok predicted outlet moisture inside spec · fouling risk low
  19. 05:16:02vision.stream({ cameras: 16, models: ["fill_seal", "foreign_body"] })
  20. 05:41:18reject: seal fault · unit 1184 · attributed to seal-jaw temperature drift
  21. 05:41:19defect.attribute({ event: "seal_fault", cause: "pack_line.jaw_temp" })
  22. 05:41:19ok packing line notified · second reject at 05:43:02 · drift corrected
  23. 05:41:20cuopt.schedule({ assets: ["PAST1", "DRY1"], window: "energy_low" })
  24. 05:41:20ok CIP sequenced · release checks armed
  25. 09:36:40mes.release_batch({ batches: ["SMP-0417", "YOG-0417"], genealogy: "full" })
  26. 09:37:52ok both batches released · scenario complete

Reasoning trace

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

GoalReceive tanker lot T-0417, standardize it once, pasteurize onc…

Receive tanker lot T-0417, standardize it once, pasteurize once, and run a skim-milk-powder stream and a set-yogurt stream to spec with full genealogy.

PlanSimulate the whole recipe on the twin first. Lead with composi…

Simulate the whole recipe on the twin first. Lead with composition so the dryer gets the right solids and the vat gets the right fat. Verify the pasteurization critical control point continuously. Let the dryer chase minimum energy only inside the bounded envelope; hold anything beyond it for a human.

ThoughtThe standing recipe over-standardizes both streams to protect …

The standing recipe over-standardizes both streams to protect against lab-sample lag. With continuous NIR and mid-IR estimates the blend can sit at the minimum safe margin. The saving is composition give-away, not safety margin: the pasteurization CCP is never a candidate for optimization.

Actiontwin.simulate(candidates=24) → recipe #9: minimum safe composi…

twin.simulate(candidates=24) → recipe #9: minimum safe composition margin, pasteurization margin unchanged, lowest predicted energy per kilogram of powder.

ObservationRecipe #9's dryer inlet temperature sits above the site's boun…

Recipe #9's dryer inlet temperature sits above the site's bounded envelope. The policy engine routes that single write to the shift dairy technologist and permits the other seven.

ActionExecute recipe #9 at the bounded stage: separation and standar…

Execute recipe #9 at the bounded stage: separation and standardization writes, CCP verification, culture dosing and the vat profile proceed; the dryer inlet write waits.

ObservationApproval granted at 05:16:00 with a tighter outlet-moisture al…

Approval granted at 05:16:00 with a tighter outlet-moisture alarm. Two seal rejects on the yogurt packing line were attributed to seal-jaw temperature drift and corrected by the packing line.

OutcomeScenario complete. Both batches released with composition, CCP…

Scenario complete. Both batches released with composition, CCP records, culture lot, drying setpoints, 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 shadow mode. The baseline comes from the plant's own lab, meters and QA records, never from Milkeon telemetry.

One metric

One line, one hard KPI agreed before anything is connected: give-away, energy per kilogram, variance or escapes.

Gates, not dates

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

Exclusions

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

Design targets

Design targets the scenarios assume

The numbers Milkeon is engineered against, from the GPU utilization plan.

50–150 ms p95 latency for reject and alert decisions at the plant edge
250–1,000 ms p95 latency for inline composition estimates
8–24 camera and inline-analyzer streams per line
10–40 concurrent models served per plant, routed by product, line and sensors
2k–10k GPU-hours of training across the first design-partner cohort
50k–250k synthetic rare-fault scenarios, each validated against real plant data

Design targets from the GPU utilization plan. Nothing on this page is a measured plant result; measurements start when the first design-partner line runs in shadow 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 processors instrument the wedge workflow in shadow mode. We measure the baseline on yield, loss and energy from your own lab and meters.
  2. Assist mode. The agent recommends separation, pasteurization or drying moves and predicts composition and contamination; your engineer approves. Accuracy and ROI are proven against the baseline.
  3. Graduated autonomy. Low-risk separation, drying 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 plant, then across sites.
Autonomy

Four stages, set per loop

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

Autonomy stages and the human role at each
StageWhat the agent doesWhat the person doesWhen
ShadowPredicts composition, contamination, moisture and takt; writes nothingRuns the plant as today; compares predictions to lab resultsFirst phase with every design partner
AssistRecommends separation, pasteurization, culture and drying moves with the evidenceA dairy technologist or process engineer approves or corrects each oneAfter accuracy is proven against the baseline
BoundedWrites low-risk separation, drying and inspection setpoints inside explicit limitsApproves anything above the limits; reviews the shift recordAfter 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 a dairy plant whose week changes when the process runs itself, and what each of them needs from Milkeon.

Economic buyer

Plant or Operations Director

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

Champion

Dairy Technologist or Process Engineer

Owns separation and standardization, pasteurization, culture and drying recipes, process windows and yield. Approves and corrects the agents in assist mode; those corrections train the models.

Approver

Quality and Food-Safety Manager

Owns HACCP, FSMA, ISO 22000 and FSSC conformance, composition and contamination conformance, and batch 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

Milkeon 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 stage the plant has set.
  • Critical control points are read, never written. Pasteurization time-temperature, flow diversion and release decisions stay with the HACCP plan and the people who own it.
  • Policy engine before every write. Autonomy stage, interlock state, product, 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, ISO 22000 and FSSC record-keeping.
  • Hard fallback. If the edge node, the network or a model stops, the plant keeps running on its existing PLC and SCADA control and interlocks.
  • Tenant and IP isolation. Recipes, supplier data 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 · ISO 22000 · FSSC · CodexGrounding and record-keeping RUNNING Design basis for retrieval and the audit log
Per-tenant isolationData, memory, models RUNNING Design rule
On-prem deploymentRecipe-sensitive producers RUNNING Design option

Milkeon 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, technologists and quality managers ask in the first meeting.

Only at the autonomy stage your plant has set, and only to an explicit allow-list of low-risk loops inside explicit limits. Every design partner starts in shadow mode, where Milkeon predicts and writes nothing. Assist mode follows, where a technologist approves each recommendation. Bounded autonomy on separation, drying 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