PublishedISO 9001:2026 published 16 Sept 2026 · 2015 certificates must transition by 30 Sept 2029What changed →
Internal Auditor course (ISO 19011:2026):free until 31 Oct · then $59 for three monthsStart free now →
← All value stream map examples

Food & beverage · worked example

Value stream map example: a sauce bottling line

A shared cooking kettle works to a weekly plan, the filling line loses more than a fifth of its time to stoppages and flavour flushes, and six days of finished pallets cover for it. Run through the guide, the line gets supermarkets after cooking and filling, a labelling-and-packing cell that sets the pace, and SMED and TPM on the filler.

The current state

Table sauces, 750 ml glass (6 flavours): 96 000 bottles a month (customer: Retail distribution centre), on 2 shifts of 8 hours. That makes 4 800 bottles a day and a takt time of 11.3 seconds. Filling & capping is over takt once stoppages and rework are counted (Filling & capping: 11.7 s effective against 11.3 s).

Lead time
18 days
raw material to customer
Processing time
32 s
actually worked on
Flow efficiency
0.003%
processing ÷ lead time
Schedule points
4
places told what to make
CURRENT STATEExample — table sauce, 750 mlMonthly forecastDaily orders8-week forecastWeekly orderWeekly cook planWeekly scheduleWeekly scheduleDaily ship schedulePackaging andingredient suppli…Bottles, caps, ingr…WeeklyRetaildistribution cent…96 000 bottles/month4 800 bottles/dayTakt 11 sPack 12 bottles2 shiftsProduction controlERPWeeklyDailyI24 000 bottlesIngredients & glass24 000 bottles = 5 days of customer demandI9 600 bottlesSauce in holding tanks9 600 bottles = 2 days of customer demandI14 400 bottlesFilled, unlabelled14 400 bottles = 3 days of customer demandI9 600 bottlesLabelled9 600 bottles = 2 days of customer demandI28 800 bottlesFinished pallets28 800 bottles = 6 days of customer demandBatch cooking2SharedLoad50% of taktEffective C/T 5.6 s (C/T ÷ uptime ÷ yield) against takt 11 sC/T5 sC/O45 minUptime90%FPY99%Batch8 000 bottlesFilling & capping2Load104% of taktEffective C/T 12 s (C/T ÷ uptime ÷ yield) against takt 11 sC/T9 sC/O40 minUptime78%FPY98.5%Batch8 000 bottlesLabelling1Load82% of taktEffective C/T 9.2 s (C/T ÷ uptime ÷ yield) against takt 11 sC/T8 sC/O15 minUptime88%FPY99%Batch8 000 bottlesCase packing2Load94% of taktEffective C/T 11 s (C/T ÷ uptime ÷ yield) against takt 11 sC/T10 sC/O5 minUptime95%FPY99.8%Batch—5 days5 s2 days9 s3 days8 s2 days10 s6 daysWAITING (STOCK)PROCESSING (VALUE-ADDED)Lead time18 daysProcessing32 sFlow eff.0.003%Flavour change: full flush
Current-state map. Every company, name and number in this example is invented.

What the improvement guide recommends

Run through the builder's nine future-state questions, accepting each recommendation, this value stream gets one pacemaker (Labelling + Case packing) and these 10 actions — each one a kaizen burst on the future-state map:

  1. 1Pull (kanban)Set up a kanban supermarket after Batch cooking (about 7 200 bottles); Batch cooking makes only what Filling & capping withdraws
  2. 2SMEDCut Filling & capping changeover from 40 to 20 min (SMED)
  3. 3TPMRaise Filling & capping uptime from 78% to 95% (TPM: find and fix the stoppages)
  4. 4Pull (kanban)Set up a kanban supermarket after Filling & capping (about 7 200 bottles); Filling & capping makes only what Labelling + Case packing withdraws
  5. 5Continuous flowBuild a continuous-flow cell: Labelling + Case packing (3 operators, one piece at a time)
  6. 6TPMRaise Labelling uptime from 88% to 95% (TPM: find and fix the stoppages)
  7. 7PacemakerSend the customer schedule to Labelling + Case packing only — every other process is triggered by kanban or FIFO
  8. 8HeijunkaLevel the mix and volume at Labelling + Case packing: release one pitch of work (12 bottles) at a time from a load-leveling box
  9. 9Pull (kanban)Hold finished goods in a supermarket of about 7 200 bottles (1.5 days) that shipping withdraws from
  10. 10Supplier pullAgree daily deliveries with Packaging and ingredient suppliers and refill a raw-material supermarket from kanban

The future state: 18 days down to 6 days

Lead time
6 days
from 18 days (−67%)
Stock
28 800 bottles
from 86 400 (−67%)
Working capital freed
R1.04 million
at R18 a unit
Schedule points
1
from 4
FUTURE STATEExample — table sauce, 750 mlMonthly forecastDaily orders8-week forecastKanban call-offOXOXPitch 2.3 minPackaging andingredient suppli…Bottles, caps, ingr…DailyRetaildistribution cent…96 000 bottles/month4 800 bottles/dayTakt 11 sPack 12 bottles2 shiftsProduction controlERPDailyDaily7 200 bottlesIngredients & glass7 200 bottles = 1.5 days of customer demand7 200 bottlesSauce in holding tanks7 200 bottles = 1.5 days of customer demand7 200 bottlesFilled, unlabelled7 200 bottles = 1.5 days of customer demand7 200 bottlesFinished pallets7 200 bottles = 1.5 days of customer demandBatch cooking2SharedLoad50% of taktEffective C/T 5.6 s (C/T ÷ uptime ÷ yield) against takt 11 sC/T5 sC/O45 minUptime90%FPY99%Batch8 000 bottlesFilling & capping2Load85% of taktEffective C/T 9.6 s (C/T ÷ uptime ÷ yield) against takt 11 sC/T9 sC/O20 minUptime95%FPY98.5%Batch8 000 bottlesPACEMAKERLabelling + Case pack…3CellLoad100% of taktEffective C/T 11 s (C/T ÷ uptime ÷ yield) against takt 11 sC/T10 sC/O15 minUptime90.3%FPY98.8%Work28 s1.5 days5 s1.5 days9 s1.5 days18 s1.5 daysWAITING (STOCK)PROCESSING (VALUE-ADDED)Lead time6 daysProcessing32 sFlow eff.0.01%SMED 40→20 minTPM 78→95%Flow cellTPM 88→95%Level the mixDaily deliveries
Future-state map drawn by the builder's guide: supermarkets and kanban loops, FIFO lanes, one pacemaker fed from a load-leveling box, and kaizen bursts where a process has to improve.
Open it and change the numbers →Free, no sign-up. The map is saved in your own browser.

More value stream map examples

New to the symbols? See the VSM symbols cheat sheet.

Get the free Value Stream Walk Kit (Excel)

Free, instant download. We'll only email you the occasional practical quality update — no spam, unsubscribe anytime.

Turning the map into results

Mapping a value stream and not sure what to fix first?

Stuck between a current-state map and a future state that actually happens on the floor — too much stock, a bottleneck nobody owns, a kanban loop that never stuck? Tell us what you're seeing. We'll look at it and suggest a practical next step, or connect you with people we trust who can help.

Email hello@qlause.app

No sales pitch, no obligation — we read every message.