Our tip – don’t let job titles drive your Role selection and don’t turn your Roles into Skills! Forecasting and resource management should drive them. This would have made managing resource roles too extensive and the forecast reporting would have been too granular. net Developer to have Roles fit with our employee job titles or make roles equal skills. We could have gone even lower than that and said Senior Operations Consultant, Operations Consultant, Junior Operations Consultant or C# Developer. This is too high level, as we need to forecast by D365 Operations Functional Consultant, D365 Operations Developer, PSA Functional Consultant, Field Service Functional Consultant etc. Using eBECS as an example, in our PSA implementation we could have implemented roles at a high level of Functional Consultant, Developer etc. If too low level, quoting will become too complicated and management of resource roles will become a cumbersome activity and resources will probably get out of date. If too high level, resource management and forecasting will not be effective. When deciding on Roles to add to PSA, think about forecasting and Resource Management.
The User can book a resource to a project and filter by role to see who is available for a specific project as seen below.
a Discovery meeting may be fulfilled by the role ‘Pre-Sales Consultant’. Essentially, these roles will be matched to tasks in a WBS and a resource who can fulfil the role will be allocated i.e.
Resource role is a term used in Professional Services Automation Industry space as a set of skills, competencies and certifications that a person is required to perform a set of tasks on a project.