Discrete vs process vs lean manufacturing in F&O

Dynamics 365 Supply Chain Management supports three distinct manufacturing modes — discrete, process, and lean — that can coexist in a single tenant on a single environment. Choosing which mode applies per item drives the entire production-execution behaviour for that item. Many F&O customers run two modes side by side, with each suiting different production lines or business divisions.

Discrete manufacturing

The classic batch production model. Used for products that are built — assembled from discrete components into discrete finished units. Examples: vehicles, electronics, furniture, machinery, medical devices, consumer goods packaging.

• Production BOMs define the components.
• Routings define operations on work centres.
• Production orders execute the build, with consumption journals capturing material usage and output journals capturing finished units.
• Cost flows component-by-component into WIP, then into the finished item on completion.

Discrete is appropriate when each finished unit is countable and tracked individually (e.g. one car, one laptop, one chair). The production order pattern matches the work: a planned quantity, components consumed, finished units output.

Process manufacturing

For products that are made through chemical, biological, or physical processes. Examples: food, beverage, pharma, chemicals, cosmetics, paint, lubricants. Different from discrete because:

• Formulas replace production BOMs. Formulas have proportional ingredients that scale with batch size, plus yield factors (a 1000 kg batch input doesn't necessarily produce 1000 kg of output).
• Co-products and by-products — a single batch can produce multiple finished items simultaneously (process meat: cuts, trimmings, bone-meal byproduct). The cost allocation across co-products is itself a configuration concern.
• Catch weight — items priced per unit but inventoried by weight (one cheese wheel = 1 piece but variable kg). Critical for meat, fish, cheese, produce.
• Batch attributes — fat %, alcohol %, pH, brix — attached to each batch, available for pricing, picking, and customer-spec filtering.
• Shelf life — manufacturing date and expiry date per batch, with FEFO (first expired first out) picking.
• Quality — process industries have substantial quality testing; integrated quality management associates test results with batches.

Process is appropriate when output is continuous, with variability per batch, with co-products / by-products, with shelf-life concerns.

Lean manufacturing

A different paradigm — pull-based replenishment, kanban-style. Used in repetitive manufacturing environments where the same products are made continuously: automotive, electronics, fast-moving consumer goods.

• Production flows define the steps in a value stream.
• Kanban rules define what triggers replenishment — withdrawal kanbans (move material from inventory to consumption point), production kanbans (start production when WIP runs low).
• Kanban cards are visual or electronic signals that drive operations without large planned production orders.
• Heijunka boards balance production to demand.

Lean is the right pattern when production is high-volume, repetitive, and where small batches with frequent replenishment fit operations better than large MRP-driven production orders.

Mixing modes

A single F&O tenant can run all three. A consumer-goods manufacturer might make the chemicals (process), assemble the packaging (discrete), and run the packaging line (lean). Each item is tagged with its production type that drives the engine's behaviour for that item.

Cost accounting across modes

Standard cost works across all three; actual cost works across all three. The cost reconciliation at period close treats each mode's WIP, components, and outputs correctly.

Common pitfalls.

• Wrong production type for the item — using discrete for a process-style operation produces no useful planning; using process for a discrete item over-engineers.
• No clear conversion factor for catch weight — products mispriced or mis-stocked.
• Mixed-mode plants without clear policy — operators confused about which orders to handle which way.

Operational reality

The implementation work scales with the number of modes used. Single-mode operations land cleanly; multi-mode operations need substantially more design, training, and ongoing process discipline.