Products > PSOP > Documentation
PSOP says my original schedule is in an inconsistent state. What does that mean?

In the PSOP results screen, the PSOP schedule is compared to an original schedule. This original schedule is the one that was in P3e when you started PSOP (more information...); it could easily be inconsistent.

For example, consider a project with two activities: Write FAQ and Publish FAQ, with a finish to start relationship between the two. If you move the Publish FAQ activity ahead of the Write FAQ activity (it is possible to do this manually, without P3e complaining, for example) and then start PSOP, this 'original' schedule is illegal.

PSOP will always produce a schedule that is consistent with the relationships in the project, if possible. Additionally, it will honor constraints that P3e ignores, and won't split tasks if these options are selected on the Primavera Compatability tab. If PSOP produces a warning that the original schedule was in an inconsistent state, that simply means the schedule against which PSOP is being compared was not legal and thus PSOP can not be expected to produce a schedule that is shorter or contains less overload. Nevertheless, PSOP is often able to produce shorter schedules with less overload even when it honors constraints that were ignored in the original schedule.

PSOP will consider the original schedule inconsistent if:
  • The original schedule violates relationships or constraints.
  • PSOP is required to honor constraints that were ignored by the original schedule. If specified on the Primavera Compatability tab, PSOP will enforce constraints that Primavera might ignore (more information...) and PSOP will not split activities that are partially completed where Primavera might (more information...). If the original schedule has violated constraints or split activities when PSOP won't, the original schedule is considered inconsistent.
  • The original schedule finishes after the deadline specified in the leveling options.
  • The original schedule contains work prior to the data date that has not been completed. Note that invoking the P3e scheduler or leveler will move all uncompleted work to after the data date. PSOP will also move work that has not been completed to a date after the data date.
Back to FAQ