Forum Discussion
Creating production schedule in Project
Thank you for the long description of your question. As I read through it a couple of times I wonder if Project is really the best app for you. I can only help you with what Project can and cannot do, you will have to do your own research with regard to what other apps are available that might better meet your needs.
With that, let me address your questions.
1. You can have as many machine resources as you need. They would be defined as Work type resources on the Resource Sheet. They may have a cost factor just like a labor type resource (i.e. $/hr) or they may have a cost per use, or no cost at all if fully amortized and cost of the machine is not of interest. Each machine resource would be assigned to tasks (process steps) as necessary. For example, let's say you have 4 fine wire drawing machines that can run 24/7. On the Resource Sheet they would be shown with a Max Unit level of 400% and a 24 hour Base Calendar. There may or may not be any cost associated with operating each machine but there may be maintenance downtime or die changeover time for each use. Those would be handled as separate process step tasks on the schedule.
2. In Project material resources as consumables. Project does NOT track inventory of material resources but it does track cost of materials (e.g. $/kg bar stock, $/ft thermoplastic insulation, etc.).
3. Unless there are unique characteristics to certain types of wire orders and processing (e.g. scheduling calendars), I would assume the production plan would be a single Project file that changes dynamically as new orders are added and completed orders finish. To keep the ever growing plan at a manageable level, the plan could be saved monthly/quarterly, etc. and deleting orders that are complete. The saved plans create a historical reference.
4. Leveling in Project has one purpose and that is to help alleviate overallocation of work type resources. Leveling does NOT impact material resources and does NOT optimize the plan. Leveling may or may not impact on-going tasks depending on leveling options (e.g. allow on-going tasks to split).
5. As I noted before I have no working knowledge of Project Online plan 3 which includes Project for the Web (very limited functionality), PWA, and Project desktop client. What I explained above is all in the framework of Project desktop. Whether the addition of PWA in Project Online plan 3 will provide added benefit for the shop floor, I do not know. Hopefully some of my colleagues will jump in with their thoughts.
With regard to the sample data you provided, most of the plan appears to be custom fields (e.g order number, target quantity, finish good name, etc.) not related to any type of scheduling. Although Project has the capability to show custom field data the only fields relating to scheduling are the process steps ("Stage Desc"), sequence ("StageLevel"), and Delivery date. That information is readily adaptable to an Excel spreadsheet however if laid out in Project it might look something like this:
John
Thanks, appreciate.
I tested that small sample myself also:
For me, kind of challenge I foresee, is to understand practically adding new orders in Project, and if so, the list of tasks will go on. Would there be any limitation, how to handle this part. Another challenge is how to avoid repetitive task, many sales orders items are repetitive, with multiple stages, can we make a task master for products, so if I add a product, its multiple stage products as sub task are added automatically?
As far as Project 3 is concerned, what I understood so far, is that One can create a project in the client and publish online and then shop floor team can update the actuals in online version, the planner will update back those updates to his client file and then only add new schedules and republish. This way sync on planning and production is maintained. Not very sure of this understanding as did not test yet, but if so, then its likely a useful feature for ongoing changes on shop floor.
- mkjain,
You're welcome and thanks for the feedback.
John Great! You drew my attention to test different file structure/s. I will definitely give a try and see what happens.
We tried Project today in more detail, and so that different views like team planner etc make it very clear where are resources are overallocated and so handy to resolve in the same view with the help of details page.
Thanks for all your support so far.
Project's specification allows for more tasks and resources than are practical to manage, (e.g. 400K tasks, 700K resources), so no, there is no limitation on adding new orders. As I suggested, you should consider periodically dropping completed orders from the plan to maintain a workable file.
Avoiding repetitive tasks is a matter of careful file structure. For example, instead of laying out each order under it's own heading, it makes more sense to lay out the plan under the headings (summary lines) of process functions, as shown here:
Assignments of machine resources will perhaps more clearly shown when overallocated so appropriate action can be taken (i.e. manual shuffling of machine allocation or leveling based on Order priority).
Again, unfortunately I can't help you with pluses or minus of going with Project Online versus standalone Project.
John
