Exactly they are "used" or "not used" like in my example
I can't build bridge 3 until I have enough earthmovers.
Why? because all the ones I have are busy. If I level the resources
when they are busy Project re schedules the task. The circle completes.
I need to report on the task in a distributed way so the resources will
be marked not busy when appropriate.
Stop worrying about equipment as
resources
This I don't understand that it has everything to do with why I'm using
project,
all the rest is fluff. We can always hire more people, we can't buy, install
or subcontract,
more equipment at the drop of a hat. It costs millions of dollars. Deadlines
on the
product these machines produce are in a constant state of change, it is a
concurrent
engineering/build to order situation. If our customer has an engineering
change that gives
us more time to complete a project but it also means more tasks and a
reordering of tasks
within that project.
A customer may also purchase premium time which means half way through a
production plan
ever more resources are channelled earlier to that project.
Like I said if you could describe to me how you would handle the example I
gave about the bridges
maybe I could see what you are talking about. You tell me to focus elsewhere
and I'm trying
but it is always a circular arguement that comes back to my need to have
concurrent
status updates as to physical machine availailabilty and therefore
enterprise capacity.
In otherwords I don't understand how to look elsewhere, if the example was
shown to me
I hope the ideas you speak of would make sense.
(experiment)
from tracking gantt -> insert column -> resource names
Are the entries in that column always people when using
Project Server. If so? Where is the similarity between that
and regular Project?