ProcessModel 7 Self Teach GuideChapter 11

Chapter 11. Find Where Your Customers Really Wait

By the end of this chapter you can

Find where customers really wait, and why, in the Output Report.

Watch the video (4 minutes), then work through the lesson below it in ProcessModel, step by step.

Title card: Self Teach Guide, Chapter 11. Find where your customers really wait.

Chapter 11 watched

Now work through the lesson

The video could not be played here.

Watch on YouTube
Length 3 minutes 40 seconds

Before you start

In Chapter 10 the shop ran ten Mondays and the report said the run could be trusted. Now read what those ten Mondays say. This chapter changes nothing in the shop. It is about reading: the skill that turns a model into an answer.

A good report reading follows a fixed order, and the Output Report is built around it. Across its top are five questions, the five any manager asks about a process:

  1. Can I trust it? Before you believe a number, check the run behind it.
  2. How is it doing? The headline figures.
  3. Where’s the constraint? The one place that holds everything else back.
  4. Why? The cause, not just the symptom.
  5. What if I change it? The fix, tried before you make it.

This chapter answers the first four. Chapter 12 answers the fifth. Keep one question in mind throughout: where do customers really wait, and why? In Chapter 9 you might have guessed the answer is Repair, or the parts. The report will tell you otherwise.

You need your Phone Repair Shop from Chapter 10, with ten replications set (or the practice model below), and about twenty minutes. Every tab is described in full in the Output Report help.

Step 1. Run ten Mondays and open the report

  1. On the Welcome screen, under Recent Models, click Phone Repair Shop.
  2. Click Run Simulation. The ten replications run in a few seconds.
  3. When Simulation Complete asks, click Yes. The Output Report opens on its Overview.

Step 2. Can I trust it, and how is it doing?

The Output Report's Overview. A green banner reads Run is trustworthy. Five figures: Throughput 60, Throughput Time 70 min, WIP In System 0.0, Cost per Entity $0 and Process Efficiency 22.1%. Below, Your constraint: Check In, with a sentence on its wait, and a Next hot-spots table listing Quick Fix, Repair Queue and Repair.
Figure 1. The Overview answers the first three questions on one page.

Can I trust it? The green banner says yes: there are enough replications, and they agree. Always look here first. A red or amber banner means the figures below it are not yet safe to act on.

How is it doing? Each figure is the average of ten Mondays. Throughput 60: every customer is served. Throughput Time 70 minutes. And Process Efficiency 22.1%: only about a fifth of a customer’s time in the shop is spent being worked on. The other four fifths is waiting. That is the size of the prize.

Step 3. Where’s the constraint?

Read the box under the figures: Your constraint: Check In. Customers wait there about 40 minutes on average, and its line reaches 16 at its longest.

Stop and notice how surprising that is. Check In is the quickest step in the shop, two to five minutes, with no staff. Nobody would guess it is the problem by looking at its settings. The model found it by watching where the time goes.

Under it, Next hot-spots lists where the most time is lost after Check In: Quick Fix, with 174 minutes lost, then the Repair Queue, then Repair, with none lost: Repair is in the list for its work, not for waiting.

  1. Click Open Impact Analysis.
Impact Analysis: a stacked bar for each step, red for non-value-added time and green for value-added time. Check In's bar is by far the tallest and nearly all red; its tooltip reads NVA 59.6%, RNVA 0.0%, VA 8.8%.
Figure 2. Impact Analysis: each bar splits a step's time into work (green) and waiting (red). Check In's is nearly all waiting.

Each bar splits a step’s time into value-added work (green) and non-value-added waiting (red). Check In’s bar is nearly all red. This is the picture to show a manager: it makes the waste visible at a glance.

Step 4. Make the report your own: My KPIs

  1. Click My KPIs.
The My KPIs tab, empty, with buttons to add a Stat, a Variable graph and a Text header.
Figure 3. My KPIs: your own page of stats, graphs and headers, saved with the model.

This page starts empty. It is yours: add stats, graphs of variables and headers, and they are saved with the model, so the same page is waiting every time you run it. In a real project, this is where you put the three or four numbers your manager cares about.

Step 5. When does the line build? Bottlenecks

  1. Click Bottlenecks.
The Bottlenecks tab. A table lists Check In first, with 68.4% of the total, then Quick Fix, Repair Queue, Repair and Pick Up. Beside it, Check In's detail: input queue 1.7 average and 16 maximum, average wait 39.8 minutes, temporal signature Daily surge, and a chart of queue depth by hour and day, lit on Monday from about 10 to 2.
Figure 4. Bottlenecks: Check In first, and a chart of when its line builds.

Check In comes first. Its chart shows the line by hour: empty all morning, building from 10, when the office group of twelve arrives, and gone by about half past 2.

Now the cause begins to show. The line is not there all day. It is a surge, and it starts at the moment twelve customers arrive at once.

Step 6. Who waits longest? Flow

  1. Click Flow.
The Flow tab. Totals: 60 created, 60 exited, average throughput time 70.45 min, 0 in system. One row for each kind of customer: Customer, 48 completed, average throughput time 59.76 min; Office Customer, 12 completed, 113.24 min. A note reads Office Customer carries the problem: 20% of volume at 17.5% efficiency, and 83% of its time is waiting.
Figure 5. Flow: one row for each kind of customer. The office customers wait far longest.

One row for each kind of customer. A walk-in spends about an hour in the shop. An office customer spends nearly two, and most of it waiting. The office group is a fifth of the customers but carries most of the problem.

Step 7. Why? Activities

  1. Click Activities.
The Activities tab. Check In is listed with utilization 13.8%, in-queue average 1.66, in-queue maximum 16, average wait 39.8 min, and 10.6% blocked.
Figure 6. Activities: Check In is busy only 13.8% of the time, but blocked 10.6% of it.

Here is the why. Check In is busy only 13.8% of the time: it is not overworked. But it is blocked 10.6% of the time: it holds a customer it cannot pass on. You met blocking in Chapter 6: when the Repair Queue is full, the customer at Check In has nowhere to go, so Check In stops. And in Chapter 9 you saw what fills the Repair Queue: customers waiting for parts.

Put the clues together, the way the report laid them out:

  • The line is at Check In, but Check In is not slow.
  • It builds when the office group arrives, and office customers go straight to the Repair Queue.
  • Check In is blocked: the Repair Queue behind it is full.
  • The Repair Queue fills when the parts run out.

The wait shows up at the front door, but its cause is at the back: the parts supply. That is why reading the report in order matters. Each tab moves you one step from the symptom to the cause.

Step 8. The Technicians: Resources

  1. Click Resources.
The Resources tab. Resource Groups: Early Technician, 2 members, utilization 57.4%. Below, Late Technician and Early Technician, each with the signal Headroom.
Figure 7. Resources: both Technicians show Headroom. They have time to spare.

The two Technicians work as one group, and both show Headroom: they have time to spare. So hiring a third Technician is not the obvious fix it might seem. Keep that in mind for Chapter 12.

  1. Close the report. The last question, What if I change it?, is Chapter 12.

Nothing in the model changed, so there is nothing to save.

Your practice model

  1. Start fromChapter 10. Run the Day Ten Times, Not OnceThe shop as Chapter 10 left it. Use your own saved Phone Repair Shop instead if you built it.
  2. Compare withChapter 11. Find Where Your Customers Really WaitThe shop as this chapter leaves it. Open it when you are done, and check your settings against it.

Both are in File ▸ Demo Models, in the Self Teach Guide group. A demo model opens as a new model, so the original never changes.

Check yourself

  1. Question 1Check In is busy only 13.8% of the time, yet it is the constraint. How can that be?
  2. Question 2Why read the banner on the Overview before any figure?
  3. Question 3Both Technicians show Headroom. What does that suggest about adding a third?

Try it yourself

Find the cause from the other end: start at the parts.

  1. Run the ten Mondays again and open the report.
  2. Click Activities and find the Repair Queue row. Read its average wait and its maximum line.
  3. Compare them with what this chapter found at Check In.

Mark it done

When you can trace the wait at Check In back to its cause, turn on Done.

You watched this chapter's video.Not watched yet: the video is marked when it plays to the end.

Kept in this browser only, and shown on the course page.

All 15 chapters of the Self Teach Guide