I go to the “Details” tab and verify the Default Units / Time” to 8h/d.(you can create one “Labor” resource and copy/paste and rename once you have set up all the settings on one resource…). I then set each resource type to “Labor”.I then add the appropriate labor resource per trade/subcontractor under this parent resource.Going to the Resources window and creating a parent resource for the project.įigure 2 – The Parent Resource (note indentation).I then set the unit and cost up to allow lump sum cost loading by unit. When developing a project schedule which requires “Cost Loading”, I prefer to develop a group of project labor resources with one resource per trade or subcontract. Project level Calculation “Resource Assignments” set to “Subtract Actual from At Completion”.
“Percent Complete” type set to “Physical”.“Duration Type” set to “Fixed Duration and Units”.I will also assume a fully developed schedule, (complete scope of work, activities, logic, calendars, and all settings correct…). Keep in mind that LS cost loading is not nearly as accurate as using estimated manhours and unit cost for developing the cost values for each activity. Personally, I see this required / used more than any other unit of measure. We can track the progress of any or all of these to provide the data necessary to create planned curves and histograms, performance metrics for Schedule Variance SV, Schedule Performance Index SPI, At Completion Values, and other helpful performance metrics.įor this article, I will focus on simple Lump Sum (LS) cost loading. Without some method of measuring actual progress against planned progress, the schedule doesn’t add the potential value it could if manhours, units, or cost are assigned to activities. Simple Lump Sum Cost Loading in Primavera P6ĭeveloping the basic Primavera P6 schedule with activities and logic is only the first step in creating a useful project schedule.