Resource Loading in Primavera utilizes both Cost and Units Columns. Knowing which fields are important is half the battle. This page discusses some of the key fields / considerations to make when resource loading a schedule. This document also discusses why some fields may be ignored when resource loading.
Having the right table columns is a necessity when resource loading in Primavera. Generally, if you are cost loaded, you will want to show the roll-ups of cost. As an example, Remaining Total Cost is the sum of Expense, Labor, Material and Non-Labor Costs. It would be counterproductive to add all of these fields so Remaining Total Cost is used.
Users should show the columns that are complimentary to what is being shown at the table level, whether that be cost, units or both. In addition, specific fields change the behavior of resources. As an example, Calculate Costs from Units breaks the tie between effort and rates.
A Resource / Role pool is created so that a company can use that pool to establish both, demand on a company, and supply for that demand. The demand is typically represented as roles whereas the the supply is where the resources are used. Note there is no requirement that a role must be used in a schedule and resources may be loaded regardless of role.
Roles are always labor while a resource can be labor, nonlabor or material.
Within the settings of a role / resource, a rate is added. This ‘burdened’ rate, multiplied by the hours of a resource, establishes the budget of a resource. Multiple resources loaded onto a single task roll up to the budget at the activity level and ultimately the Work Breakdown Structure (WBS) / Project Level.
Once all columns at the Table Level and the columns at the Activity Detail level have been set, you can then save a layout so these do not have to be recreated.
While Cost, Units and Demand are all needed when Resource loading, there are a few fields that can be confusing but may ultimately go unused: