Sepion
Autonomous separation and standardization that ends fat and protein give-away.
Five products, one plant-edge runtime, one audit and genealogy backbone, one data flywheel. Sepion sets the composition that Culvex and Aridyn depend on, Vizra inspects the output and feeds each defect back to its cause, and Lactwin simulates the coupled process before every run.
Illustrative scenario: Plant run · skim-milk-powder line + set-yogurt line · shared intake. Not a measured run.
These are one coherent dairy-processing autonomy ecosystem, not separate bets. They share the plant-edge inference infrastructure, the food-safety audit and genealogy backbone, the multi-tenant data plane and one compounding flywheel.
Autonomous separation and standardization that ends fat and protein give-away.
Autonomous evaporation and spray-drying that hits moisture and solubility at minimum energy.
Autonomous fermentation and culture control for cheese and yogurt that hits pH and texture every batch.
Inline vision and robotic handling that catches contamination, foreign bodies and fill and seal faults before they ship.
The as-processed dairy-line digital twin that hits target composition, safety and takt before the run.
Autonomous separation and standardization that ends fat and protein give-away.
Separation and standardization set the economic floor of every dairy plant: milk is clarified, separated into cream and skim and re-blended to an exact fat and protein target before anything else happens. Today this runs on fixed separator setpoints, periodic lab checks and technologist craft, so composition drifts between samples and processors over-standardize to stay safe, giving away fat and protein on millions of liters.
Sepion fuses inline NIR and mid-IR analyzers, separator and clarifier telemetry, flow and temperature sensors and lab results into a continuous estimate of fat, protein and solids, then closes the loop on separator throughput, cream-skim split and the standardization blend valves to hold the target at the minimum safe margin. It predicts separator fouling and clarifier bacterial-load excursions before they force a stop.
| Capability | Status |
|---|---|
| Spectral-to-composition regression per milk supply and product, edge-served | design scope |
| Closed-loop standardization policy: shadow, assist, then bounded | bounded stage planned |
| Separator fouling and clarifier load prognostics | design scope |
| Cited reasoning over separation and standardization specs | design scope |
Jetson Orin/Thor at the separator with TensorRT and Triton; DeepStream and Holoscan for analyzer streams; cuOpt for silo and blend sequencing; NIM for packaged inference. DGX/HGX fine-tuning across the design-partner cohort is planned.
Autonomous evaporation and spray-drying that hits moisture and solubility at minimum energy.
Evaporation and spray-drying turn milk into powder and consume the most energy and water in the plant. Operators hold conservative inlet and outlet temperatures and feed rates to avoid stickiness, wall fouling, scorched particles and out-of-spec moisture, because a moisture or solubility miss downgrades a high-value batch and a fouling event forces a wash-out. Running conservatively wastes energy and throughput; running hot risks quality.
Aridyn fuses inline moisture and NIR, temperature and humidity, feed solids and pressure with a GPU-accelerated CFD and process twin of the evaporator and spray dryer to predict outlet moisture, solubility, particle size and fouling risk in real time, then closes the loop on inlet and outlet temperature, feed rate and solids, and atomization to hold powder spec at the minimum energy and water. It anticipates stickiness and fouling upsets and schedules drying around energy cost and CIP windows.
| Capability | Status |
|---|---|
| Physics-informed spray-drying and evaporation surrogates | design scope; full CFD-in-the-loop planned |
| Fouling and stickiness prognostics from telemetry | design scope |
| Energy-minimizing drying policy with graduated autonomy | bounded stage planned |
| Cited drying reasoning over specs and safety standards | design scope |
DGX/HGX and OVX for the CFD twin and surrogate training (planned); Jetson Orin/Thor at the dryer; Omniverse and Modulus for the physics-ML twin; TensorRT and Triton for edge serving; cuOpt for dryer scheduling; Cosmos and Replicator for rare drying-upset scenarios.
Autonomous fermentation and culture control for cheese and yogurt that hits pH and texture every batch.
Cheese and cultured-dairy quality is decided by living biology: cultures acidify milk to an exact pH on an exact curve, and the coagulation, cutting, cooking and texture windows all hinge on it. Culture activity swings with composition, season, phage pressure and inoculation variability, so master cheesemakers watch pH by hand and intervene by feel. The craft that manages this is retiring faster than it can be replaced.
Culvex fuses inline pH and temperature, milk composition from Sepion, culture lot and vat telemetry to predict the full acidification and texture trajectory in real time, then closes the loop on temperature profile, culture dosing and timing, coagulant addition and cut and cook timing to land target pH, moisture and texture. It detects abnormal acidification and probable phage or contamination events early and encodes the cheesemaker's craft into a reusable per-product model.
| Capability | Status |
|---|---|
| Biological curve models for acidification and texture | design scope |
| Anomaly detection for phage, contamination and abnormal fermentation | design scope |
| Closed-loop fermentation policy with graduated autonomy | bounded stage planned |
| Per-technologist craft memory, scoped per tenant | design scope |
Jetson Orin at the vat for trajectory inference; TensorRT and Triton with per-product and per-culture routing; NeMo for dairy-culture reasoning; cuOpt for vat and cook sequencing; Modulus for biology-informed curve modeling (planned); DGX/HGX training (planned).
Inline vision and robotic handling that catches contamination, foreign bodies and fill and seal faults before they ship.
Inspection is the last line of dairy food-safety defense: contamination, foreign bodies, fill-level errors, cap and seal defects, label faults and package damage have to be caught before product reaches consumers. Most plants rely on spot lab tests, manual visual checks and single-purpose detectors that miss subtle or rare defects, while packaging and palletizing are paced by a scarce workforce, and inspection data is disconnected from the process that caused the defect.
Vizra runs multi-camera vision and inline sensing at the plant edge to detect and predict contamination, foreign bodies, fill, seal, cap and label faults at line speed, rejects off-spec units and feeds each defect back to the upstream agent that caused it. It also drives Isaac and Jetson robotic packaging, palletizing and material handling, and covers events too rare to collect with validated synthetic defects.
| Capability | Status |
|---|---|
| Fine-tuned contamination, foreign-body, fill, seal and label vision at the edge | design scope |
| Defect prediction and root-cause attribution to upstream state | attribution in design scope; full causal closure planned |
| Robotic perception, grasp and motion policies for packaging | design scope via Isaac |
| Cited food-safety reasoning grounded in HACCP, FSMA and ISO 22000 | design scope |
Jetson Orin/Thor for 8 to 24 streams per line; Metropolis, DeepStream and TensorRT pipelines; Holoscan for deterministic fusion; Isaac Sim, ROS and Lab for robotics; Cosmos and Replicator for synthetic defects; Triton and NIM for serving; IGX and Fleet Command for the managed edge fleet.
The as-processed dairy-line digital twin that hits target composition, safety and takt before the run.
Plants commit to a run, a product, a milk supply, a set of setpoints and a schedule, and only discover composition misses, safety-margin problems, fouling or takt bottlenecks after milk and energy are spent. No tool simulates a batch as it will actually be processed across the coupled physics and biology of separation, heat exchange, fermentation, evaporation and spray-drying. Rare faults are also too rare and costly to collect enough real data to train robust models.
Lactwin couples GPU-accelerated CFD and process and biology simulation of separation, pasteurization and heat exchange, fermentation, evaporation and spray-drying with the live plant state to simulate a run before it happens, finding recipes and control envelopes that hit composition, safety and takt at minimum energy and water, and handing optimized setpoints to Sepion, Culvex and Aridyn. It also generates validated synthetic rare-fault scenarios that harden every Milkeon model.
| Capability | Status |
|---|---|
| CFD and process surrogates and physics-ML across separation, heat, fermentation and drying | surrogates in design scope; full multiphysics-in-loop planned |
| Recipe and envelope search with multi-objective optimization | design scope |
| Synthetic rare-fault generation with domain randomization, validated against plant data | design scope |
| Twin-versus-actual reconciliation and drift detection | design scope |
DGX/HGX and OVX for multiphysics twins and surrogate training (planned); Omniverse and Modulus for the physics-ML twin; Cosmos and Replicator for synthetic scenarios; cuOpt for scheduling; CUDA, TensorRT and Triton for kernels and surrogate serving; Jetson for distilled on-line envelope checks.
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.
Modules are licensed per line on the Line tier and bundled on Plant and Enterprise.
| Capability | Line | Plant | Enterprise |
|---|---|---|---|
| Lines covered | 1 | All on site | All in group |
| Agent modules | 1 of 9 | All 9 | All 9 + custom models |
| Lactwin twin | Not included | Included | Custom twin domains |
| Plant-edge node | Included | Per line | Fleet managed |
| Guarded PLC writes | Scoped tags | All scoped tags | Group policy |
| Batch genealogy | Included | Included | Included + export |
| Autonomy stages | Shadow, assist, bounded | Shadow, assist, bounded | Shadow, assist, bounded |
| Deployment | Plant edge + cloud | Plant edge + cloud | On-prem or private cloud |
| Outcome pricing | On request | Available | Standard |
| Indicative price | $14,000 / mo | $90,000 / mo | $650k – $8.5M ACV |
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.
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 |
Milk is perishable and the lines are continuous, so perception has to be local and fast. Milkeon runs GPU inference at the plant edge and keeps training, simulation and optimization in the cloud, in a private cloud or on-prem. Items marked planned are on the roadmap, not running.
8 to 24 camera and inline-analyzer streams per line. Design target: 50 to 150 ms reject and alert decisions, 250 to 1,000 ms composition estimates, all at the plant edge.
Defect, composition, shelf-life, process-state and dairy-reasoning models behind one orchestrator, with version routing by product, line and sensor package. Design target: 10 to 40 concurrent models per plant.
Vision, spectral, time-series and dairy-reasoning models fine-tuned from labeled batch outcomes, operator corrections, lab results and validated deviations. Initial design target: 2k to 10k GPU-hours.
GPU-accelerated CFD and process simulation of separation, heat exchange, fermentation, evaporation and spray-drying, run as-processed before the batch to find safe, low-energy recipes.
Rare contamination, foreign-body, fouling, seal, fill and drying-upset scenarios generated with domain randomization and always validated against real plant events before use.
Product sequencing, tank allocation, dryer scheduling, CIP timing, energy and water constraints and line balancing, recomputed on the GPU when the plant is disrupted.
Packaging, palletizing and material handling for product, packs and pallets, with perception and motion policies built in simulation before they touch the packing hall.
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.
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.
Most plants start with Sepion on a standardization line or Aridyn on a dryer. Tell us which number you need to move.
↑↓ navigate↵ openesc close