.png){kind=logo}
Resource Leveling
- 19 Feb 2024
- 4 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Resource Leveling
- Updated on 19 Feb 2024
- 4 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Resource Leveling
Resources are the materials, plants, or people needed to carry out activities. Resource data for a project consists of resource requirements and resource availability. The resource availability states the quantity of various resources available at specified times. The availabilities are entered separately from the project data. Availabilities may only be defined for resources listed in the resource definition set associated with the current project. Resource availability can be determined for each project and also for project groups.
The 'Resource Leveling' is located under the PROJECT ribbon.
Resource Availabilities
Details of availability for all required resources are entered separately from the project data. An availability line consists of a resource code, a quantity, and a timespan. The resource code must correspond to the resources defined in the resource set for the project. Click the Available Resources icon in the PROJECT ribbon to specify resource availability. Resource availability can be entered in terms of QTY-per-day or as manpower. You can toggle between these two modes by clicking the preferred mode button in the dialog window.
| Fields | Description |
|---|---|
| Resource | The resource code (Short Name) for which availability is entered. Select from the drop-down list. |
| Available from | A Date field. Available from. Optional. If missing, Safran Project assumes availability from the Project start date. |
| Available Until | A Date field. Available Until. Optional. If missing, Safran Project assumes availability until the project end date. |
| QTY (per Day) or Manpower | QTY: Decimal field. The maximum quantity available between from-date and until-date. Manpower: Decimal field. Enter availability as Manpower. Safran Project uses the man-hours per day from the specified calendar to compute QTY if manpower is entered and vice versa. |
| Calendar | Uses a Calendar to configure more complex resource availability if resources are unavailable according to a calendar, such as during vacations and holidays. If no value is entered, Safran Project uses a default work pattern with seven working days per week. Work patterns available are those defined for the calendar associated with the current project. |
Complex resource availabilities may be modeled by entering multiple resource availability records for a single resource category.
Adding a New Resource Availability Record
Press the New button in the window to add a new resource availability. Safran Project enters a new line into the availability window.
Deleting a Resource Availability Record
Select the resource availability record to delete and press the Delete button in the window. Safran Project prompts you to confirm the deletion of the resource availability record.
You cannot delete the entire availability table in one operation, as this must be done by deleting row-by-row.
Summary
Using a summary will help you get an overview of resource leveling.
| Fields | Description |
|---|---|
| Activities Selected | Shows the activities included in the resource leveling filter. |
| Activities leveled | Shows the activities that have resources with availability and thus will run when resource leveling is on. |
| Placed (No delay / no overload) | Shows the activities that have been identified so that analysis ES / EC will be calculated without overload. |
| Delayed (No Overload) | Shows the activities that have been placed without overload but have been delayed. |
| Overloaded | Shows the activities that have both been delayed and overloaded. |
Prioritizing resources
This is a practical tool for prioritizing activities in the order in which resource leveling should follow. To do so, drag and drop the fields you need to prioritize.
Filter
This allows you to specify which activities should be considered in resource-leveling.
Resource leveling process
Please note that only the activities that have resources that have been defined and have available units will leveled. During the resource leveling process, two main steps happen:
- The process starts with all the activities in the plan. These activities will be placed in a leveling queue and sorted by sort criteria.
- After leveling each activity, a forward pass will be run to the first successor. The results will be analyzed, sorted, and placed in a leveling queue.
Resource leveling options
By clicking the small arrow on the left corner of resource leveling in the PROJECT ribbon, you will get two options: Time Limit and Resource Limit.
Both options will help you find the location of available resources for all activities that are selected for resource-leveling. The only difference between Time and Resource limit is that Time-Limit will set the Maximum Delay to the activities' Total Float. At the same time, the Resource Limit allows manual input of Maximum delay. Maximum delay is the number of time units permitted for each activity to delay.
The ‘At Overload’ comes with two different options, ‘Place As Early As Possible’ and ‘Place with Minimum Overload,’ available for both Time and Resource Limits.
Place As Early As Possible: Moves to the earliest possible date and does not consider the overload's size.
Place with Minimum overload: Move the activity to the minimum possible overload date.
Maximum Overloaded Activities: The number of overloaded activities can be accepted before resource leveling is canceled.
Was this article helpful?