K
Kevin
This question or forms of this question have been asked from time to time on
this board, but I am still confused with the answers. Here is my scenario.
We are a project oriented service (Engineer to Order) business, not a
standard manufacturing business. Within our facility we have a combined CNC
and traditional machine shop. However, not all of the machinists can operate
all of the machines. So I am at the mercy of the qualification levels of the
machinists when I try to schedule work through the machine shop. I have a
total of twelve machinists, one of which can run every machine. I also have a
machine that only two people are qualified to run, and every scenario in
between.
There are other similar scenarios in other areas of the facility, but not as
severe as those in the machine shop.
Machines are constrained by the availability of machinists so I need to be
able to assign both the Machine and the Proper Machinist concurrently. I also
need to show that that Machinist is not available during that time frame for
any other machine. Typically the scenario is one machinist to a machine, but
we do have one machine that requires two machinists (simultaneously) to
operate. I know I will have to list each machinist as a separate resource,
but how to group them according to skill level is the real problem.
I have read that Project Server has a Resource Substitution Wizard that can
assign resources based on skill level. Will that give me the functionality
that I need to effectively manage the workload in the machine shop? Will
Project server let me list multiple skill levels for each individual
machinist (i.e. Joe Blow: Machine 1, Machine 2, Machine 7, etc...)? We have
just begun an implementation of Project Server, so I am anxious to get my
feet wet so to speak.
We played with another application for a while that did have this
functionality. It let you put individual resources in order of preference
into specific groups and assign those groups concurrent with the machine. The
same individual could be in more than one group, but could not be assigned
anywhere else if he was already utilized. That application fell short in a
lot of other important areas however and was not deemed suitable for our
operation..
Best Regards,
Kevin
this board, but I am still confused with the answers. Here is my scenario.
We are a project oriented service (Engineer to Order) business, not a
standard manufacturing business. Within our facility we have a combined CNC
and traditional machine shop. However, not all of the machinists can operate
all of the machines. So I am at the mercy of the qualification levels of the
machinists when I try to schedule work through the machine shop. I have a
total of twelve machinists, one of which can run every machine. I also have a
machine that only two people are qualified to run, and every scenario in
between.
There are other similar scenarios in other areas of the facility, but not as
severe as those in the machine shop.
Machines are constrained by the availability of machinists so I need to be
able to assign both the Machine and the Proper Machinist concurrently. I also
need to show that that Machinist is not available during that time frame for
any other machine. Typically the scenario is one machinist to a machine, but
we do have one machine that requires two machinists (simultaneously) to
operate. I know I will have to list each machinist as a separate resource,
but how to group them according to skill level is the real problem.
I have read that Project Server has a Resource Substitution Wizard that can
assign resources based on skill level. Will that give me the functionality
that I need to effectively manage the workload in the machine shop? Will
Project server let me list multiple skill levels for each individual
machinist (i.e. Joe Blow: Machine 1, Machine 2, Machine 7, etc...)? We have
just begun an implementation of Project Server, so I am anxious to get my
feet wet so to speak.
We played with another application for a while that did have this
functionality. It let you put individual resources in order of preference
into specific groups and assign those groups concurrent with the machine. The
same individual could be in more than one group, but could not be assigned
anywhere else if he was already utilized. That application fell short in a
lot of other important areas however and was not deemed suitable for our
operation..
Best Regards,
Kevin