PSOP Leveling Options

• No limit: The project deadline will be ignored and PSOP will use as much time as necessary to level the resources. This is similar to leveling in Primavera without the level resources within activity total float option selected. However, unlike the P3e leveler, PSOP will honor all constraints and relationships if the enforce constraints ignored by Primavera leveling option is checked on the Primavera Compatability tab.
• The current project deadline: PSOP will generate a schedule that finishes before the project deadline specified in the Primavera project. If no deadline was specified for the project, this option is not available.
• This date: the PSOP generated schedule will not finish later than the date specified.
• No later than the original schedule: PSOP will generate a schedule whose length does not exceed the length of the Primavera schedule that was current when PSOP was invoked. Note that by rearranging activities PSOP may be able to reduce the over-allocation in a schedule without making the schedule any longer. PSOP may also be able to generate a shorter schedule that has the same or less over-allocation than the original.
• As early as relationships and constraints allow: PSOP will generate a schedule whose length is as short as is possible without violating activity relationships or constraints. While it is impossible to generate a legal schedule with shorter length, PSOP will attempt to arrange the activities which have float to minimize over-allocation.

• Resources: PSOP will try to minimize resource over-allocation. It will ignore roles and consider only resources. By default all resources will be leveled. If you would like to level only a subset of the resources, click Selected under resources and then click the Select button. (More information...)
• Roles: PSOP will ignore resources and try to minimize over-allocation of roles. In order to determine the availability of a role, the availabilities of all resources that have the role as a primary role are accumulated. For example, if welder is a role, and Joe and Judy are the only welders, then the availability of the welder role at any point in time is the sum of Joe and Judy's availability at that time. (More information...)
• Resources and roles: This is similar to leveling by role except resources are not ignored. If a resource is assigned to an activity and that resource has a primary role, the resource assignment is treated as a role assignment. If the resource does not have any role it is leveled in the usual way. For example, consider an activity with the following resource assignments:
• 1 welder role
• 1 painter role
• 1 resource name Joe. Joe's primary role is welder.
• 1 resource named Judy. Judy has no primary role.
This would be treated as 2 welders (the 1 welder assignment plus Joe who is a welder), 1 painter, and 1 Judy. The availability of the roles is determined by aggregating the availabilities of all resources with the role as a primary role. Note that when PSOP substitutes roles for resources it does not change the resource assignments in the P3e database. This option changes the way PSOP calculates resource availability and usage, but does not change the P3e project. (More information...)