Oracle | Primavera Risk: Pertmaster Import Check Tab

The second step of a typical Oracle | Primavera Risk (Pertmaster) Monte Carlo analysis is to validate the import for differences between the original schedule file and the Pertmaster CPM schedule calculations.  The Import check worksheet tab shows the project manager any the difference between the start and finish dates in the original scheduling tool (Microsoft Project, Primavera, etc) versus the Primavera Risk CPM calculation.

Video Walkthrough of the Oracle | Primavera Risk (Pertmaster) Import Check Worksheet (Duration: 4 min: 49 sec)

Import Check Worksheet Tab

After reviewing the import log and schedule settings, verifying the schedule import check is vital.  A worksheet tab labeled “import check” will contain a Gantt chart view showing all Pertmaster activity bars based on the CPM calculation and an overlay of the bars from the original scheduling tool.

The start and finish check column will list the amount of days the schedule is out of line with the original schedule.  The import check will look the same whether the original scheduling tool is Microsoft Project, Primavera P3, or Primavera P6.  A negative number will show that the Pertmaster schedule started or finished early.  A positive number will show that the schedule started or finished late.  The silver bars on the Gantt chart represent the bars in the original scheduling tool.  Regardless of the import check, it is important to follow the import check by running the schedule check report.  The import log and schedule check reports will often guide users to find issues in the original schedule.  Changes may need to be made in the base schedule and the file re-imported before proceeding.

Often the difference in scheduling engines can cause slight variations here.  Errors such as improper logic, planning unit, progress overrides, and rounding can cause issues.  Problems with the Primavera database can also cause issues.   A few tips for working through the import check tab on small and large schedules is listed below:

  • Filter for normal activities that are less than 100% complete.  Completed tasks, milestones, and summary tasks are usually in-line if the normal tasks are perfect.  Try to filter the data to avoid information overload.
  • Look for the root cause of the issue.  One activity can cause a ripple through the entire project.
  • If the Primavera P6 file was migrated from Primavera P3, then duration issues may exist.  Pertmaster often interprets the Primavera P3 data better than Primavera P6 did.
  • Fix items in the original scheduling tool and re-import the new file. 
  • Do not pay too much attention to one or two day variances.  Focus on the reporting milestone variances and work backward.
  • Review the schedule check, import log, and scheduling options for clues.
  • Look for items that have the same start and finish check values.  These items came in with the correct duration regardless of the values.  If the start and finish check values are different, then the duration came in wrong.  This allows a user to trace the cause.

Fixing a schedule that had huge date variations from an import can be one of the most difficult parts of the Pertmaster Monte Carlo analysis process.  Hopefully this will not be an issue, however the root cause is usually the schedule being imported and not the Primavera Risk product.