K
Kurt Petteloot
Hi,
Currently we're working with committed bookings and proposed bookings in
separate project plans.
In our situation we deal with projects hat contain approved (committed) work
and proposed wok at the same time. In case we need the same resource (a named
resource that is, not a generic one) to be assigned accross these 'mixed'
types of bookings we see no other option than to create a second project plan
where that same enterprise resource is entered as a 'proposed' resource (in
this case the resource would already have been added to the original project
plan as a 'committed' resource for all the tasks that got approval from the
customer).
Is there any other way to allow an enterprise resource to be assigned
accross tasks within the same project as 'committed' for one part of those
tasks, while the assigments to the other 'proposed' tasks would show as
'proposed' bookings in the resource graph and availability reports for that
resource (like the MSP cube).
Kind regards,
Kurt Petteloot.
Currently we're working with committed bookings and proposed bookings in
separate project plans.
In our situation we deal with projects hat contain approved (committed) work
and proposed wok at the same time. In case we need the same resource (a named
resource that is, not a generic one) to be assigned accross these 'mixed'
types of bookings we see no other option than to create a second project plan
where that same enterprise resource is entered as a 'proposed' resource (in
this case the resource would already have been added to the original project
plan as a 'committed' resource for all the tasks that got approval from the
customer).
Is there any other way to allow an enterprise resource to be assigned
accross tasks within the same project as 'committed' for one part of those
tasks, while the assigments to the other 'proposed' tasks would show as
'proposed' bookings in the resource graph and availability reports for that
resource (like the MSP cube).
Kind regards,
Kurt Petteloot.