Resource Loading in Core

How P6 Resource loading is applied in Core and unique ALICE benefits 

Importing your budgeted labor units from P6  

ALICE core imports your budgeted labor units, actual labor units, and remaining labor units from your original P6 file.

Additionally, ALICE estimates your planned labor units using duration*default units/time (workforce required for tasks) this is an additional column labeled Planned Labor Units  

 

ALICE Core utilizes the concept of budgeted labor units to optimize resource loading. ALICE calculates the minimum resources required per task and the peak number of resources required for the project based on your histogram peak from P6. 

 

Functionality of the Resources tab

Click the resources tab to view, create, and modify your labor, equipment, materials, rates, and calendars from your imported schedule 

Note: You can also import resource metadata from a historical project and easily assign the resources to your new schedule 

If your schedule is already resource-loaded below is an explanation of how your P6 resource loading is handled in Core  

  • Crew Name
    • Assign crews based on discipline, scope, and schedule detail
    • crews can be grouped under a subcontractor or managed independently 
    • Note: We recommend you start by resource-loading critical path activities to quickly identify risks and opportunities on the critical path that can make the biggest impact to project duration  
  • Imported Resource Peak 
    • Calculated Peak of resource histogram from the imported schedule 
    • This number can not be modified and is a helpful benchmark of your P6 assumptions before optioneering in Alice
      • To modify the workforce peak in Alice-generated solutions use the max units/time variable explained below  
  • Max Units/Time 
    • The initial value is imported from your P6 schedule
    • Max available workforce for crew type
    • Optimize resources by removing max units of time constraint or modifying this value in the explore page and simulate the impacts on your schedule duration
    • A change here applies to the project resource pool
  • Default Units/Time (applies to tasks) 
    • The initial value is imported from your P6 schedule
    • This is used to estimate Planned Labor Units = Crews required for task * # of work hours in original duration and relevant task calendar
    • A change here applies to the task and planned labor units 
  •  #pers/crew (applies to the project) 
    • Set this value to control the number of people per crew at the project level 
    • As of Feb 15 recommend keeping your # of pers/crew to 1 (This feature will work best with planned upgrades coming soon) 
    • Please note that number of people per crew is tied to the daily workforce limit feature calc
  • Cost (crew/hour applies to the project) 
    • Cost is used to calculate the direct cost of crew labor hours and the idle cost (downtime) for the crew when it demobilizes and remobilizes until it fully demobs from the job. 
  • Calendar for Crews  
    • In Core, calendars are defaulted to the task calendar. However, users have the flexibility to assign a default crew calendar and Optioneer with crew calendars and task calendars 
    • Your default crew calendar default in P6 is imported as your crew calendar in Alice 
    • Please note that in Core activity calendars are task-based by default (like P6)
  • Idle Cost (Toggle on or off) 
    • Turn on idle cost if you want to see a scale of efficiency in your optioneering, faster solutions can result in lower idle cost due to reduced downtime for crews 
    • Turn off idle cost if you want to easily see only direct labor cost changes, like the additional cost impact of overtime work or productivity changes.  

Resource Loading a new P6 schedule with Core  

This section explains how users can resource-load a new P6 schedule in ALICE 

Why is resource loading important when scheduling with ALICE? 

Resource loading is required to realistically assess the feasibility of your baseline schedule Based on the required resources in the schedule and your estimation of available resources 

Alice will dynamically shuffle resources to help you find the fastest feasible schedule duration while abiding by your scheduling, logic, and resource constraints. 

 

Resource Loading Best Practices in Core 

  1. Analyze the critical path in your baseline solution
  2. Start by creating a labor resource pool for crews that are on the critical path  
  3. Use the filter builder to filter the activities that require the same resource type
  4. Bulk assign the resource type and quantity required per task (default units/time) 
  5. Repeat this process for all critical tasks to de-risk and optimize the critical path   
  6. Repeat this process for all activities to resource load your entire schedule and develop an antifragile schedule 

 

Step 1: Create labor resource types

 

Step 2: Filter and select activities that require the same crew types

Note: in this example, the user has created a mobilization crew and is bulk-assigning the crew to all mobilization & demobilization activities. 

 

Step 3: Bulk assign required resources and type in the required count of labor for the tasks 

Note: deselect a crew type to bulk remove the crew 

Was this article helpful?
0 out of 0 found this helpful