Recipe Management

A version-controlled system for managing bulk processing recipes, procedural steps, and integrated quality control points.

RECIPE · MES

Interactive Product Demo

Scroll to walk through Recipe Management

HIERARCHY 01

VERSIONING 02

CONTROL POINTS 03

CALC ENGINE 04

RECIPE · MES

Every Level, One View

A five-level tree — recipe, operation, phase, step, ingredient/control point — gives process engineers complete process definition in a single structured editor.

Revise Without Losing History

Each revision increments the version number and links back to its predecessor — every previous version stays intact so historical batches remain traceable and rollback is always available.

Actuals From the Historian

Control point readings are auto-populated directly from the SCADA historian — operators see real instrument values without any manual entry or transcription.

Formulas Built Into Recipes

Named formula variables and an embedded optimisation solver let recipes automatically derive ingredient quantities and additive ratios from batch size or quality targets.

Recipe Management

A version-controlled system for managing bulk processing recipes, procedural steps, and integrated quality control points.

RECIPE · MES

What It Does

Recipe Management treats process instructions as structured, versioned, machine-readable data rather than documents. Every recipe defines its process as a five-level hierarchy that the Batch Log reads directly to guide operator execution — an active recipe is a precondition for creating a batch job, not an optional reference.

Versioned Recipe Hierarchy

Recipes define process as five levels: recipe → operation → phase → step → ingredients and control points. Each change creates a new version; the prior version deactivates but is fully preserved. Historical batch jobs always link to the exact version that governed their execution — the answer to "which spec ran this batch" is always deterministic.

SCADA-Integrated Control Points

Each control point step links to its automation source in the SCADA historian. During execution, the Batch Log reads the current historian value automatically. Target, minimum, and maximum limits defined in the recipe are evaluated against the incoming reading before the step closes — out-of-spec conditions are visible to the operator immediately.

Calculation Engine

Named calculation variables support algebraic formula expressions referencing other variables or batch parameters. An optimisation solver can find ingredient quantities that satisfy a cost or yield objective within configured bounds, deriving exact values at job creation time.

PDM Integration

The Calculation Engine is the same engine driving the Additive Calculator in PDM. Recipe-defined formula parameters compute additive dosages from batch size, keeping calculation logic in one governed location across planning, recipe execution, and loading stages — a spec change propagates everywhere automatically.

See RECIPE in Your Operation

Schedule a demo and we'll walk through Recipe Management alongside the full MES suite — and where it fits in the AI-Native platform we're building.

Back to MES