Give-away, energy per kilogram, pasteurization margin, acidification, escapes, CIP water. Each is a loop a dairy plant already measures, and each is where one Milkeon agent starts.
Illustrative scenario: Plant run · skim-milk-powder line + set-yogurt line · shared intake. Not a measured run.
No result is claimed here. Each card names the number a pilot would baseline in shadow mode from your own lab, meters and QA records.
The highest-volume step in the plant, run on lab-sample lag. Continuous composition estimation lets the blend sit at the minimum safe margin.
Baseline: Liters and dollars of fat and protein recovered per shift; composition variance against lab
The largest energy and water consumer in the plant, run with conservative margin. The twin finds the quality-safe frontier and the agent holds it.
Baseline: Energy per kilogram, moisture variance, fouling wash-outs avoided
Time-temperature verified continuously and logged against the HACCP plan; the interlock stays yours.
Baseline: CCP margin held, over-processing avoided, shelf-life prediction against lab
Living biology watched by hand today. The trajectory is predicted and held; the craft is captured as a model.
Baseline: First-pass quality, pH variance, downgrades avoided
Inspection at line speed with every reject traced back to the step that caused it.
Baseline: Escape rate, scrap, rejects attributed to cause
Scheduled around production and energy windows inside the validated program, with release checks enforced.
Baseline: CIP water and chemical use, release checks passed, energy-window placement
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Goal, plan, thought, action, observation, exactly as the orchestrator would record it.
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.
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.
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.
twin.simulate(candidates=24) → recipe #9: minimum safe composition margin, pasteurization margin unchanged, lowest predicted energy per kilogram of powder.
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.
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.
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.
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.
Gates, not dates. Each stage starts when the previous one has proven its number against your own baseline.
Milkeon is recruiting three to five design partners for the first cohort. These are the processor types the products were designed around and where each would start.
Separation and standardization at the highest volume in the industry. Starting wedge: Sepion, with Vizra on filling and capping.
Standardization feeding living fermentation. Starting wedge: Culvex on the vats, Sepion on the make-milk.
Cream-skim split and fat targets set the margin. Starting wedge: Sepion, with Vizra on packaging.
pH and texture on a curve, batch after batch. Starting wedge: Culvex, with the pasteurization agent on the make-up.
The most energy- and water-intensive lines in the plant. Starting wedge: Aridyn on one dryer.
Tight moisture and solubility windows, high value per batch. Starting wedge: Aridyn and Vizra together.
Separation and standardization touch every liter. Processors defensively over-standardize to avoid off-spec batches between lab samples, so fat and protein above spec leave the plant continuously. The lever is continuous composition estimation that lets the blend sit at the minimum safe margin. The baseline is measured in liters and dollars per shift.
Evaporation and spray-drying are the plant's largest energy and water consumers, run with margin because a moisture miss downgrades the batch and a fouling event forces a wash-out. The lever is a physics twin that finds the quality-safe frontier and an agent that holds it. The baseline is energy and water per kilogram of powder, from your own meters.
A qualified pilot targets one line or dryer where a single failure can create six- to seven-figure annualized margin, waste or recall exposure, and justifies the $14,000 per line per month entry price from verified savings or avoided risk.
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.
| Stage | What the agent does | What the person does | When |
|---|---|---|---|
| Shadow | Predicts composition, contamination, moisture and takt; writes nothing | Runs the plant as today; compares predictions to lab results | First phase with every design partner |
| Assist | Recommends separation, pasteurization, culture and drying moves with the evidence | A dairy technologist or process engineer approves or corrects each one | After accuracy is proven against the baseline |
| Bounded | Writes low-risk separation, drying and inspection setpoints inside explicit limits | Approves anything above the limits; reviews the shift record | After the food-safety and ROI gates agreed up front |
| Exceptions | Escalates anything outside its envelope, CCP-adjacent moves and release decisions | Always decides these; the agent never does | Permanent |
The numbers Milkeon is engineered against, from the GPU utilization plan.
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.
Two agents will want the same actuator. The orchestrator arbitrates on the run goal, with food safety above everything, and the handoff is logged like any other step.
Yield-and-Takt wants more flow through the pasteurizer so the powder stream starts earlier and the dryer is not left waiting.
Pasteurize-and-Homogenize requires the flow that keeps holding time at or above 15 s at 72 °C. That is the HACCP critical control point.
Food safety outranks takt under every run goal. The critical control point wins the actuator; the request for more flow is logged with its score and the reason it lost.
Yield-and-Takt recovers the schedule by starting the evaporator on the first standardized skim instead of waiting for the full tank. Takt is met without touching the CCP.
Nothing about a Milkeon run is implicit. The goal is declared, the plan is rehearsed on the twin, each step is typed, and the outcome is written to the batch genealogy.
A run starts as a goal, becomes a plan, and executes as a graph of typed steps. The active path is always visible, always logged, always reversible.
Shadow, assist, bounded, exceptions. Each plant sets the stage per loop, and anything above the threshold, every critical control point and every release decision waits for a named person.
The three people in a dairy plant whose week changes when the process runs itself, and what each of them needs from Milkeon.
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.
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.
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.
Milkeon reads and writes through the systems already on the floor. No parallel historian, no new HMI, no rip-and-replace. Connectors are built against each design partner's stack first; long-tail integrations are out of scope for the first release.
PLC and SCADA of separators, pasteurizers, homogenizers, culture vats, evaporators, spray dryers and CIP skids
Setpoint reads, guarded writes, interlocks untouched
NIR and mid-IR composition, inline pH, moisture, temperature and humidity
Continuous composition and process state
LIMS results, calibrations, antibiotic and micro screens
Calibration and release evidence
Orders, recipes, product specs, batch genealogy
Targets in, release records out
Multi-camera stations on filling, sealing, capping, labeling and powder lines
Frames, defect events, reject commands
Plant and asset-level meters
Hard constraints for the dryer and CIP schedule
Isaac-driven packaging, palletizing and handling cells
Perception and motion for packs and pallets
SSO and role-based access; SOC 2 on the roadmap
Named approvers, scoped roles
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.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | QUEUED Roadmap, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Roadmap, 6 to 12 months |
| HACCP · FSMA · ISO 22000 · FSSC · Codex | Grounding and record-keeping | RUNNING Design basis for retrieval and the audit log |
| Per-tenant isolation | Data, memory, models | RUNNING Design rule |
| On-prem deployment | Recipe-sensitive producers | RUNNING Design option |
Milkeon supports your food-safety records. It is not a certification and it does not replace your HACCP plan.
One policy model, one audit trail and one set of yield, loss, energy and water benchmarks across every plant in the group, with each site's recipes and tolerance models kept private to that site.
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.
Critical control points are not optimization variables. The pasteurization CCP, the flow-diversion interlock and release decisions stay with your HACCP plan and your people. Milkeon verifies readings, writes them to an immutable audit log and attaches them to the batch genealogy. It supports HACCP, FSMA, ISO 22000 and FSSC records; it is not a certification and does not replace your plan.
Milkeon sits above your existing automation as a supervisory layer. If it stops, the plant keeps running on its current PLC and SCADA control and the interlocks it already has. A Milkeon outage degrades the plant to the way it runs today, not to a stop.
The first phase is shadow mode on one line: Milkeon reads your analyzers, PLC history, lab results and MES while you run the plant as usual, and we measure its predictions against your lab. Recommendations start when accuracy is proven against that baseline, and improve as plant-specific history and technologist corrections accumulate.
Recipes, product specs, tolerance models and supplier data are tenant-scoped and never used to train another customer's models. Retrieval is multi-tenant isolated and permission-aware. On-prem deployment is available for processors protecting sensitive recipes.
You are, the same as with any control strategy. That is why every write is policy-checked, bounded, logged and reversible, every output carries a citation to the recipe or procedure it relied on, and anything above your threshold waits for a named approver. The audit log records the request, the reasoning, the limits applied and the human decision.
As a design partner, on one line, with one hard metric: fat or protein give-away, energy per kilogram of powder, moisture or composition variance, or contamination escapes. We instrument the line in shadow mode, measure the baseline, move to assist mode when accuracy is proven, and expand only when the number holds.
Full multi-module autonomy across the whole plant, long-tail integrations beyond the design partners' stacks, and self-serve onboarding. The first release is one wedge workflow, its connectors, the agent loop with human checkpoints, the review console and the food-safety audit log.
One line, one KPI, shadow mode first. Bring the line that costs you the most.
↑↓ navigate↵ openesc close
