PSOP Equivalent of Primavera Options

• Automatically level resources when scheduling: Because PSOP always levels resources, there is no equivalent setting in PSOP.
• Consider assignments in other projects with priority equal/higher than: PSOP allows you to select multiple projects for leveling (more information...). All resource assignments in the selected projects will be considered regardless of their leveling priority. Resource assignments in projects that were not selected will be ignored. Specifying leveling priorities in PSOP is generally unnecessary and is not recommended (more information...).
• Preserve scheduled early and late dates: If this option is selected P3e will perform two leveling passes, a "forward" and a "backward" pass. The late dates will be set to the dates calculated by the backwards pass and the early dates will be set to the dates calculated by the forward pass. PSOP provides no equivalent option.
• Recalculate assignment costs after leveling: If you export the PSOP schedule to the Primavera database, resource assignment costs are not recalculated by P3e. You must click Recalculate assignment costs on the tools menu in P3e to have the costs updated for the new schedule.
• Level all resources: This is the same as choosing all resources under "What to level" on PSOP's Main Settings tab. Both P3e and PSOP allow you to select a subset of resources to be considered during leveling (more information...).
• Level resources only within activity total float: In P3e, this option can result in 3 different behaviors:
  1. If a deadline has been set for the project and this option is selected, P3e will honor the project deadline.
  2. If no deadline has been set and this option is selected, P3e will make the schedule as short as possible.
  3. If this option is not selected, the P3e leveler will allow the project to lengthen during leveling and will also ignore some relationships and constraints (more information...).
  The PSOP leveling options provide equivalent settings:
  1. Selecting the current project deadline has the same effect as selecting level resources only within activity total float with a project that has a deadline.
  2. Selecting as early as relationships and constrains allow has the same effect as selecting level resources only within activity total float with a project that does not have a deadline.
  3. Selecting No limit has the same effect as not selecting level resources only within activity total float except that PSOP will honor all activity constraints if Enforce constraints ignored by Primavera is checked on the Primavera Compatability tab.
• Preserve minimum float when leveling: PSOP allows you to specify how much total float should be preserved for each activity. This option appears on the Primavera Compatability tab (more information...).
• Max percent to over-allocate resources: In P3e, you can use this setting to get around the fact that the P3e leveler will not minimize over-allocation for tasks that cannot obtain zero over-allocation (more information...). Since PSOP does not suffer from this problem, there is no need for an equivalent option in PSOP.
• Leveling priorities: as explained in the overview, P3e does not attempt to search for an optimal priority order when leveling. It is up to the user to specify a leveling priority order which will produce a good schedule. As PSOP intelligently searches many priority orders it is not necessary to provide a priority order to PSOP. However, if there are activities that you would like placed earlier in the schedule, you can give those activities a higher priority (lower number) and select the Use Primavera activity leveling priority option on the Primavera Compatability tab.
• Log to file: PSOP does not currently provide a leveling log. However PSOP does provide many ways to explore the schedule changes made by the leveler, and this information can be saved and printed (more information...).