Bottom up planning in PSA lets you start from a set of project tasksA unit of work or collection of work associated with a project. and define detailed project requirements, including potential resource spend and allocation, and potentially staff your project based on information in your project plan.
As a Resource Manager, creating resource requests for project tasks manually can be time consuming. It's quicker to generate them automatically, based on project tasks created in Project Task Gantt or through standard Salesforce pages, to make informed estimates of the roles, resources and project milestones you'll need to cover. This can be achieved by generating task-driven resource requestDescribes a resource request that has been generated based on information on project tasks and their associated project task assignments. If you use a bottom-up approach to manage your projects, you can generate task-driven resource requests on the Generate Resource Requests From Project Task Assignments page (accessed from Project Task Gantt or the Project detail record).s.
PSA can generate resource requests based on information on project tasks and their associated project task assignmentAssociates a resource with a project task. This has no relationship with an Assignment.s. Depending on how much information exists on your project tasks at an early stage, you can choose to generate resource requests based on role, resource, external resource or milestone. For example, you may have project tasks that cover the Content Optimization milestone of a project with project task assignments for the SEO Specialist role. In this case, you can choose to generate resource requests based on available information on milestone and resource role.
Your administrator can configure PSA to update the source project task assignments with the resource that you eventually assign to a task-driven resource requestDescribes a resource request that has been generated based on information on project tasks and their associated project task assignments. If you use a bottom-up approach to manage your projects, you can generate task-driven resource requests on the Generate Resource Requests From Project Task Assignments page (accessed from Project Task Gantt or the Project detail record). through a regular PSA assignment. This ensures consistency between resources assigned to project tasks and resources assigned to downstream assignments. If you have assigned external resourceA person or entity that is external to your Salesforce organization. You can use external resources when assigning external staff, such as contractors, to project tasks.s to project tasks, using either Project Task Gantt or the standard Salesforce interface, they are automatically removed when you come to assign a resource to a task-driven resource request. For more information, see "auto-update-pta-with-assigned-resource".
You can view the financial impact of task-driven resource requests, alongside other resource requests and assignments, on the Unfilled Resource Requests page.
The following table summarizes the mappings that PSA applies when generating resource requests from project tasks:
Key: * – Mandatory field
| Field on Generated Resource Request | Key | Maps to Field(s) on Project Task: | Maps to Field(s) on Project Task Assignment |
|---|---|---|---|
| Start Date | Start Date on earliest project task. | - | |
| End Date | End Date on latest project task. | - | |
| Notes | External Resource. | ||
| Requested Hours | Sum of Duration (Hours) field on all project tasks. | - | |
| Role | * | - | Maps to either Resource Role on the project task assignment (preferred), or Resource Role on the assigned resource. |
|
|
* | - | Resource. |
The following tables illustrate two scenarios where a set of project tasks is used to generate resource requests: firstly by role and secondly by both Milestone and Role.
| Project Task | Project Milestone | Internal Resource | External Resource | Resource Role |
|---|---|---|---|---|
| Task 1 | Milestone A | Developer | ||
| Task 1 | Milestone A | Java Developer | ||
| Task 2 | Milestone A | Consultant | ||
| Task 3 | Milestone B | Robert | ||
| Task 4 | Milestone D | Daniel | Developer | |
| Task 5 | Milestone B | Daniel |
| Target Resource Request | Resource Role | Project Milestone | Project Tasks |
|---|---|---|---|
| RR1 | Developer | Milestone A, Milestone D | Task 1, Task 4 |
| RR2 | Java Developer | Milestone A | Task 1 |
| RR3 | Consultant | Milestone A | Task 2 |
| RR4 | Robert's role on Contact record | Milestone B | Task 3 |
| RR5 | Daniel's role on Contact record | Milestone B | Task 5 |
| Target Resource Request | Resource Role | Project Milestone | Project Tasks |
|---|---|---|---|
| RR1 | Developer | Milestone A | Task 1 |
| RR2 | Developer | Milestone D | Task 4 |
| RR3 | Java Developer | Milestone A | Task 1 |
| RR4 | Consultant | Milestone A | Task 2 |
| RR5 | Robert's role on Contact record | Milestone B | Task 3 |
| RR6 | Daniel's role on Contact record | Milestone B | Task 5 |
Related Tasks
Generating Resource Requests from Project Tasks
Generating Resource Requests from Project Task Gantt
Viewing Unfilled Resource Requests
Reference Materials
Generate Resource Requests from Project Tasks Fields
© 2009-2015FinancialForce.com, inc All rights reserved. FinancialForce and FinancialForce.com are registered trademarks, and the FinancialForce.com logo is a trademark. Other product names appearing herein may be trademarks.
This document contains proprietary information of FinancialForce.com, inc and its licensors, and is subject to change without notice.