M
MikeO
Hi,
I'm evaluating MS Project Server 2003 as a potential replacement for our
existing Niku (was ABT) system. For resource management, the required process
is
- Project Manager requests a resource for a project (either generic or named)
- Resource Manager & Project Manager identify/change/agree named resource
- Resource Manager 'allocates' resource to project
- Project Manager can 'assign' tasks in project to their 'allocated' resource
So far so good - but importantly, the resource manager's view of resource
availability is based on 'allocation' rather than 'assignment' - i.e. once
someone is allocated to a project for a period they are gone from the
Resource Manager's view of availability.
As far as I can see MSPS 2003 only has a view of availability based on
'assignment'.
I would welcome comments on our existing process, suggestions as to how/if
the existing process can be implemented using MSPS 2003 and suggestions for
any better process that MSPS 2003 supports.
Thanks,
Mike.
I'm evaluating MS Project Server 2003 as a potential replacement for our
existing Niku (was ABT) system. For resource management, the required process
is
- Project Manager requests a resource for a project (either generic or named)
- Resource Manager & Project Manager identify/change/agree named resource
- Resource Manager 'allocates' resource to project
- Project Manager can 'assign' tasks in project to their 'allocated' resource
So far so good - but importantly, the resource manager's view of resource
availability is based on 'allocation' rather than 'assignment' - i.e. once
someone is allocated to a project for a period they are gone from the
Resource Manager's view of availability.
As far as I can see MSPS 2003 only has a view of availability based on
'assignment'.
I would welcome comments on our existing process, suggestions as to how/if
the existing process can be implemented using MSPS 2003 and suggestions for
any better process that MSPS 2003 supports.
Thanks,
Mike.