Recipe, Routing & Process Design

Design production processes visually, with versions under control

A routing turns a production order into a sequence of steps that can genuinely be run on the shop floor. Build the process visually, use specifications as its basis, and manage every change with version control without disrupting orders already in flight.

What you can design

  • Process Specification (Master Recipe) Define how a product is made, from process steps and parameters to the resources required and the quality checks. A specification becomes a reusable reference across many production orders.
  • Visual Routing Designer Build the production flow directly on a canvas with drag-and-drop. Create sequential steps, branches, parallel processes, conditions, and rework loops without writing code.
  • Material & Multi-Level BOM Manage raw materials, components, and sub-assemblies in a multi-level BOM structure, versions and revisions included, so production always uses the right materials and structure.
  • FEFO & FIFO Decide how material is allocated to production using FEFO or FIFO. The system helps ensure the right lot is used under the applicable rule and keeps expired material out of production.

Sequential, parallel, and conditional in one routing

Real production processes do not always run in a straight line. A job can branch, several steps can run at once, and an inspection result can decide whether a unit moves on or goes back for rework. All of it can be modelled on one canvas.

StepHow it behaves
10 · Material preparationSequential: the next process starts once preparation is complete.
20 · Sub-assembly ARuns as one branch of the process.
30 · Sub-assembly BRuns in parallel with step 20, and both must finish before the process continues.
40 · Final assemblyRejoins the output of the two parallel paths.
50 · Functional testThe test result determines the next path.
60 · Pack & shipUnits with a PASS result continue. Units with a FAIL result return to step 40 for rework.

Branches are decided by the conditions that actually occur during execution. The routing defines the rules and the possible paths, while the final decision follows the real result on the shop floor.

The Routing Designer with a multi-stage process flow showing parallel and rework paths

Version control without disrupting orders in flight

  • Every change becomes a new version When a routing is updated, orders already released keep running on the previous version. The change applies to subsequent executions.
  • Specifications are reusable One specification can underpin many routings, complete with its operations, qualified resources, standard times, work instructions, and quality checks.
  • AI helps draft it Describe the process you want in plain language and the AI Routing Designer produces a draft routing for review. Nothing is saved or used until a person confirms it.

Frequently Asked Questions

The questions that usually come up as process and IT teams start designing routings.

Can a routing branch on an operator's decision?

Yes. Operators record a result at a conditional step, and the system determines the next path from it. A PASS continues to the next process, while a FAIL sends the unit to rework.

What happens to orders already running when a routing changes?

Orders already released keep using the routing version assigned to them. The change is created as a new version and used for subsequent orders.

Do we need an engineer to create a routing?

Not necessarily. Routings can be built on a visual canvas with drag-and-drop. AI can also draft one from a plain-language description of the process, and that draft is then reviewed and confirmed before use.

Keep reading