Changeovers

One of the many powerful things you can do with your Systems2win Value Stream Mapping template is to

 

Automatically calculate your optimum Smallest Change Over Batch Sizes

 

How to Calculate your Optimum Default Change Over Batch Size

When you're ready to use your Power Tool to help calculate your optimum Default Change Over Batch Size:

1. Use the Hide/Show Rows button to unhide rows

   (because all rows for Change Overs are hidden by default)

2. For your pacemaker process only...

   enter data for 'Time Per Change Over'

   Of course, you can always just enter a close guess.

   To enter the more accurate and precise number, use your Standard Work template to carefully observe your pacemaker process, and (if needed) to perform SMED Setup Reduction to minimize Time Per Change Over.

3. Your Systems2win Value Stream Mapping template will auto-calculate your Smallest Batch Size

   Smallest Batch Size = The smallest possible batch size to keep Effective Cycle Time just below Takt Time

4. If there is another process that requires a batch size larger than your Pacemaker, then perform the same analysis for that process
5. Enter your chosen 'Default Change Over Batch Size'

   Enter your chosen 'Default Change Over Batch Size' in the pink double border cell found in the Values column in the row headers for the Critical Path Processes.

   You will usually round to a convenient container size.

   Your chosen default will be determined by either: the Pacemaker, or some other process that requires a larger batch size.

   

   As explained below, you have the ability to override a unique batch size for a unique process, so you want to choose the 'Default Change Over Batch Size' that will work best for MOST processes in your value stream.

Change Over Batch Size for most typical processes

Change Over Batch Size can be overridden for any process

For each process... in the cell just to the right of the 'Change Over Batch Size' data cell,

you can optionally override the default Change Over Batch Size for just that process.

And you can follow the above steps to easily calculate the Smallest Change Over Batch Size for as many processes as you want.

Example: If there is one bottleneck process that requires a large batch size, you might strategically place an inventory buffer before and/or after that process, so that it can run batches that are larger than the rest of the value stream.

Opposite example: Perhaps most of your value stream might use a larger batch size required for a non-pacemaker operation, but you don't want to slow down your Pacemaker, which can run faster with a smaller batch size, so you override the Change Over Batch Size for your Pacemaker (and perhaps a few surrounding nearby processes) with a batch size that is smaller than your default.

---

---

If you don't already own your value stream mapping template

you can own it now

 

 

priced low enough to empower every team member