Machine resource planning and chart

[GoogleCodeExporter]

Usually, the resources are not only people working, sometimes we do have a 
machine working for a long period of time. 

It would be good to identify two groups of resources (machines and worker). The 
group "worker" should operate as it is on GP; the group "machine" should ignore 
the weekends counting it as a working day (machine wont stop on weekend).

If you have a "worker" and a "machine" as resources for a specific task, the 
task must consider to be done in a working day (example: setup needs a machine 
and a worker in a working day). If just a machine is requested for a task, the 
weekend shall be considered as a working day.

A specific chart with machines would be created showing the machines usage 
inline (machine cannot be overloaded). This design would be similar to 
TaskBlocks (https://code.google.com/p/taskblocks/). Once Machine chart is 
selected, just the machine resources would be shown on the chart.

It is very useful if you have tests running for a long time in a machine 
(example: super computer running a weather estimation, test machine running a 
test for 20 days) 

Original issue reported on code.google.com by [email protected] on 7 Oct 2014 at 9:32

Attachments:

• TB_Capture.PNG

[RB3rg]

I can't understand how people manage projects without monitor equipment (or any other non-human) resource cost. It sounds like all projects only have workers, there is no rental cars, no rental equipment or any other cost involved in the task such as air tickets (one time cost) etc. This is very helpful in long-term projects to determine in which step of the project we are going to spend more money.