Products > PSOP > Documentation How can I get the most out of PSOP? PSOP can improve most schedules without any intervention on your part. However, there are several things you can do to help PSOP produce better schedules: Allow the schedule to be longer: Specifying a finish date in the leveling options limits what PSOP can do to reduce overload. Choosing no limit gives PSOP the most flexibility. If some limit is required, choose this date and specify a date that is as late as acceptable to help minimize over-allocation. Assign resources: If an activity uses resources and there are limits on that resource this information should be entered into Primavera as accurately as possible. If PSOP doesn't know about resource utilization and limits, it can't reduce resource conflicts. Use roles instead of resources: If an activity could be performed by multiple resources, specifying a single resource unnecessarily limits what the leveler can do. For example, if Joe and Judy are both welders and it doesn't matter which of them performs a certain activity, assigning the resource Judy to the activity may limit where the activity can be placed as PSOP will try to avoid resource conflicts with other activities that have been assigned to Judy. If the welder role is used for this activity instead of a specific resource PSOP will have more options and may be able to find a better schedule. Note that PSOP also has the ability to infer the correct role for a resource and level using roles without requiring the user to substitute roles for all resource assignments in P3e (more information...). Provide appropriate resource availabilities: PSOP aims for a schedule where all activities can be completed without exceeding resource availabilities. It is therefore important to provide accurate resource availabilities. Don't use Primavera activity leveling priorities: Primavera allows the user to specify a leveling priority for each activity. In P3e, this can help produce a more level schedule as explained in the overview. Since PSOP tries many leveling priorities and actively searches for those that are successful, it generally produces better schedules if it is not forced to honor user-specified leveling priorities. For this reason PSOP, by default, ignores the Primavera activity leveling priority. On the Primavera Compatability tab you can specify that PSOP should honor P3e activity leveling priorities, but this is usually not appropriate. Don't use constraints to force activity placement: As the Primavera leveler is often unable to provide a good level schedule (see the overview for details), it is common practice for users to manually place activities and then use activity constraints to keep Primavera from moving the activity when the Primavera leveler or scheduler is run. Because PSOP honors these constraints, this limits PSOP's ability to find good quality schedules. PSOP will generally find better results if unnecessary constraints and relationships are removed from the project. Back to FAQ