Multiple Deliverables/day 1

[Mako2U]

I work for a small manufacturing company and one of our products is an electronic control panel.

I have outlined all of the tasks required to complete one panel based on our current production rate. However, we produce 10 of these panels per day. How do show model this in project? Do I manually multiply the duration of each task by 10, in this example, and place this value in the duration field or can Project do this for me? Looking for any suggestions.

Thanks,

LK Williams

 

[johnherman]

I think I would control this via Resources. That is, I would create a resource called Mfg Rate as of Jun2007 and assign it to the task. Make its max units as 1000% (ten per 100% day). This way, if/when your rate changes, you only need to reassign the Resource. But don't do this yet. PDQBach is the expert and may have better ideas.

-------------------------
The trouble with doing something right the first time is that nobody appreciates how difficult it was - Steven Wright

 

[bestchild]

Hi,

Let me share my point of view.
In such case, I seldom manage the quantity in this way. Only the task activity is the most important to manage. Especially in this case, just number of tasks x quantity, I will just at the quantity on the task name " x 10" to handle it. Then I can check the completion until "10" is completed. otherwise, I can reflected in the work complete %, for example 80% completed means 8 is completed, 2 is yet to come.

 

[bestchild]

If quantity is really important. I would rather separate one task into ten :
Task A 01
Task A 02
.
.
Task A 10


This is just my preference, let see PDQBach have any suggestion ?

 

[Mako2U]

Both are good suggetions, will wait to see if PDQBach has something else I can try.

 

[PDQBach]

Well, technically, this isn't a project ("a temporary endeavour to create a unique product, service or result") -- but we can probably ignore that pesky intrusion.

At the end of the day, you have to decide what it is you're trying to control and measure.

If it's "10 gizmos" then I'd have

Task1 "10 gizmo lids"; duration is time for 10 lids
Task2 "10 gizmo bottles"; duration is time for 10 bottles
Task3 "10 gizmo labels"; duration is time for 10 labels

My link from Task1 to Task2 would be SS with a lag equal to the amount of time to produce a lid. My link from Task2 to Task3 would also be SS with a lag equal to the amount of time to produce a bottle.

If, however, you want to control and measure each then I would create a skeleton plan to make one and save it; then I would create a Master project and insert the skeleton plan as often as necessary to track the output and I would link the lid tasks in a cascading FS relationship.

I get the feeling that there is some background to this requirement that put you in the position of having to do the tracking. If this is true and the impact of a failed or delayed product (during the manufacturing process) is critical then other QA/QC products (but don't ask me!) might possibly be more appropriate to your environment.

 

[Mako2U]

Sorry for the delayed response. Thanks to all of you for your suggestions. I had already created a skeleton as suggested by PDQ but I was hoping for a easier way to accomplish this.

LOL, I was pushed into doing this and I did not feel Project was the best way to go, however sometimes you must go with the flow even if it doesn't make sense.

Mako