B
Bazzaboo
Problem
I have 4 machines (resources) all with skill A. One of these 4 resources ALSO posesses skill B
I would like to generically call an activity that uses skill A (levelling chooses one of 4 options)
Obviously would like to call skill B - with only one option
Problem
Assuming problem 1 can be resolved, if an activity has chosen one of the above 4 resources, how do you ensure it maintains this choice for an immediately following task (i.e. when a machine has been 'set' for a 'job' and now you want to run production)
Background
Our requirement is to choose from a pool of machines (2 types - one is a superset of the general case) a standard or enhanced machine. This machine is 'set' to perform a function by a 'setter' - a setter is a superset of the class operator. After this activity, production runs - but it must be on this machine - with any member of the operator class
Activity 1 Resource 1 Resource
Set machine any machine from pool setter (superset member of operator class
Run machine same machine as above any operato
Activity 2 Resource 1 Resource
Set machine superset machine from pool setter (superset member of operator class
Run machine same machine as above any operato
Lastly the operators / machines are individuals - although they may be called arbitrarly in some cases. They must still be subject to individual unique constraints such as absense and downtime
I have 4 machines (resources) all with skill A. One of these 4 resources ALSO posesses skill B
I would like to generically call an activity that uses skill A (levelling chooses one of 4 options)
Obviously would like to call skill B - with only one option
Problem
Assuming problem 1 can be resolved, if an activity has chosen one of the above 4 resources, how do you ensure it maintains this choice for an immediately following task (i.e. when a machine has been 'set' for a 'job' and now you want to run production)
Background
Our requirement is to choose from a pool of machines (2 types - one is a superset of the general case) a standard or enhanced machine. This machine is 'set' to perform a function by a 'setter' - a setter is a superset of the class operator. After this activity, production runs - but it must be on this machine - with any member of the operator class
Activity 1 Resource 1 Resource
Set machine any machine from pool setter (superset member of operator class
Run machine same machine as above any operato
Activity 2 Resource 1 Resource
Set machine superset machine from pool setter (superset member of operator class
Run machine same machine as above any operato
Lastly the operators / machines are individuals - although they may be called arbitrarly in some cases. They must still be subject to individual unique constraints such as absense and downtime