# Looking for Tool to Determine Number of People Needed

Six Sigma – iSixSigma › Forums › General Forums › Tools & Templates › Looking for Tool to Determine Number of People Needed

- This topic has 9 replies, 9 voices, and was last updated 1 month ago by stephanieareid.

- AuthorPosts
- March 29, 2019 at 11:15 am #237749

G Robert GettysParticipant@Kivda**Include @Kivda in your post and this person will**

be notified via email.I’m looking for a tool or approach that works for others that takes into consideration a number of factors including time to complete individual tasks, complexity, and experience to help determine if our teams are right-sized or imbalanced. Any thoughts?

0March 31, 2019 at 9:49 pm #237984

StrayerParticipant@Straydog**Include @Straydog in your post and this person will**

be notified via email.You might find some help at the Project Management Institute’s website. Microsoft Project and other good PM software might help, even if you are dealing with on-going teams rather than projects which begin and end. Bottom line is that there are complex estimating formulas which are still “guesstimates”. You don’t know what you don’t know so you have to make assumptions, and people are not equivalent.

0April 1, 2019 at 11:39 am #238007

Eric DickesParticipant@ericdickes**Include @ericdickes in your post and this person will**

be notified via email.Discrete Event Modeling is a powerful tool to model the workflow and the optimal number of people to run it. It can handle variable distributions (like time to complete tasks) an have resource pools of different kinds of worker (skill level?). A really powerful insight it gives is the impact of delays caused by bottlenecks.

We are currently using Extend software to model the workflow/patient throughput in a hospital setting. It is a fair amount of overhead to get it set up and running, but well worth it – if it is critical to make the right decisions regarding the workflow design/staffing.0April 1, 2019 at 1:16 pm #238008If you’re thinking of the # of Production Operators and you have a recent [weekly] record of the overtime hours, add the OT hours (OTh) and divide by 36. This will get you close to # Operators needed to reduce overtime hours & operator-burnout. Note, I use 36 because 40 hours x 90% = 36, and most humans are about 90% efficient (in the long term) when working on production activities that require manual & hands-on actions. So when a person is present, they’ll be about 90% efficient, which is not same as utilization. And I round up for any fractional results.

Example: If recent totaled OTh = 140 hours, divided by 36 = 3.89, rounded up = 4 operators needed.- This reply was modified 11 months ago by Bubb. Reason: format error

0April 1, 2019 at 5:56 pm #238012

qualitymxParticipant@qualitymx**Include @qualitymx in your post and this person will**

be notified via email.Could someone explain the arguments to state that Crew to talk= process time/ takt time?

To define quantity of people in a process?

Is this assumption reliable?, does it have a math argument?

What could be a real argument to consider it valid and reliable?

Thanks0April 2, 2019 at 12:26 am #238025

Chris SeiderParticipant@cseider**Include @cseider in your post and this person will**

be notified via email.Look for waste ( http://leanmanufacturingtools.org/7-wastes/ ) and this will help you but don’t overanalyze too much–cut the waste and see what happens and see how the process improves.

2April 2, 2019 at 4:37 am #238026

nvkrishnaParticipant@nvkrishna**Include @nvkrishna in your post and this person will**

be notified via email.This is a capacity determination problem. One could start with defining capacity as a function of experience and complexity, and then compare existing team capacity with the required capacity. However, this may be a non trivial exercise for software development, for example, where the standard deviation itself is very large. The capacity approach would be useful in a situation involving repetitive tasks and standard processes.

0April 2, 2019 at 9:24 am #238029Hi, just to 2nd Eric’s comment on Discrete Event Modeling / Process Simulation being very useful for this. Drop me an email and I would be happy to show you some examples using SIMUL8.

0April 2, 2019 at 2:03 pm #238032

qualitymxParticipant@qualitymx**Include @qualitymx in your post and this person will**

be notified via email.Thanks Chris

But I want to understand this in order to convince my boss, since is not clear for me, difficult will be to convince him.

I wonder how dividing process time / takt time the result is quantity of people.

Where is the basis to think like this?

Where is the reasoning of this?Thanks

in my poor thinking, time/ parts per time, results are parts, not quantity of people.

0January 24, 2020 at 3:18 pm #245737

stephanieareidParticipant@stephanieareid**Include @stephanieareid in your post and this person will**

be notified via email.No need for any fancy software, use the level-loading and demand staffing concepts instead. To determine number of people needed in a given day, you must first determine your Takt Time which equals available work hours of operation divided by the number of units that need to be produced or customers to be serviced. Once you have your Takt time in minutes, then you can determine the number of employees you will need to meet that demand by taking your cycle time and dividing it by the Takt time. Now the real work happens when you notice you are not meeting Takt time due to inefficiencies which come from some form of the 8 wastes. That is when you evaluate whether or not your employees are engaging in value-added activities which are the steps in a process that transforms the product/service your customer is paying for or non-value adding activities which slow down your production and cause you not to meet your goals. Try researching operator loading charts as one of your tools for this situation.

1 - AuthorPosts

You must be logged in to reply to this topic.