- 150 calls.
- 2 minutes.
- 50 calls.
- 25 minutes.
- Cycle time dropped from over 11 hours to under 40 minutes.
- Level2 utilization dropped to 51.81%.
- That is bad because they are only busy half of the time they are available to work.
- Perform Research.
- The queue is no longer used
- The average quantity in the queue is 3.71
- The average time in queue is 78.81 minutes
- Level 1 = 53.38%, Level 2 = 89.70%.
- The utilization of both resources is about 70%.
- Low cost, fast turn-around, no disruption to live system, try solutions that would be impractical to test on a live system.
- Level 2 resource utilization of 92.36 and standard deviation of 4.32.
- Cycle time of 316.11 and standard deviation of 244.73.
- The 25% and 75% routings.
- How long does it usually take to perform this operation? What is the longest it has ever taken? What is the shortest amount of time it has ever taken?
- On average less calls arrive per hour in lesson three (12 vs 15). Entities only come in between 8 am and 4 pm, but resources can continue to work after 4 pm to handle any backlog.
- Click Simulation / Options and set the run length to 168 hours or 7 days.
- This is a tricky question. Changing any element in the model will alter the random pattern. You would need to run replications of the original and the changed model to predict the outcome accurately. The model with one large pattern has a greater potential for variation, so more entities could bunch together during arrivals and cause longer waiting times.
- Total cost, cost per call, unused resource cost, the total number of calls returned, and customer satisfaction.
- Despite higher costs, adding a second resource is likely a better choice than staying with 1 resource. Throughput is much better, customers will be happier with shorter wait times, and your employees will probably have higher job satisfaction since stress levels will be significantly lower. The cost of customer dissatisfaction is hard to measure, but generally, you should strive for the best service possible. Employee burnout is likely to be much higher in the case of only one Level 2 resource. That can end up costing a great deal in many different ways.
- Yes, as noted in earlier lessons. It is important to remember that the simulations must be run and the results compared before assuming one solution is better. You might be surprised at the results of some of the experiments.
- If Name = Item Then a_Route = D2(40,2,60,3).
- Create a variable (e.g., v_ReworkCount) with an initial value of 0. On the rework route (returning to Production), add the action logic “Inc v_ReworkCount). In the output report, scroll to the bottom section to view the variable’s stats.
- No, the system falls behind
- Add a second resource in the Level 2 position. Change the lunch breaks for Level 1 and Level 2, so they don’t overlap. Make the Level 2 resource an alternate to Level 1 for answering calls, so when Level 1 is at lunch, Level 2 will answer calls.
- Some returned calls are not resolved satisfactorily. So they have to do more research and return the call later.
- TSR2 is helping TSR1.
- Since the route is not connected to any other activity, they exit the system.
- Run multiple replications, then view the average values in the output report rather than each individual replications’ result.
Self Teaching Guide
- Your First Model
- Replications and Distributions
- Entity Arrivals
- Attributes, Variables and Action Logic
- A More Complex Call Center
- Model Building Techniques
- Froedtert Hospital Improves ICU Care
- Nuclear Site Cleanup
- Restaurant Customer Seating Optimization