Oracle | Primavera Risk: Pertmaster Running a Schedule Check

The third step of a typical Oracle | Primavera Risk (Pertmaster) Monte Carlo analysis is to validate the integrity of the schedule logic.  The Primavera Risk schedule check flags areas of concern or note in the schedule.  This training article will give the steps and some hints for running the schedule check report.

Video Walkthrough of the Oracle | Primavera Risk (Pertmaster) Schedule Check Report(Duration: 4 min: 9 sec)

Running the Schedule Check Report

Running the schedule check is a simple process.

  • Set the schedule check options via the menu path Reports | Schedule Check Options…
  • Click the “Run Check” button in the options or follow the menu path Reports | Run Schedule Check

Bookmarking Activities

Primavera Risk will bookmark all flagged activities unless the option is turned off in the schedule check options.  The bookmarked activities will allow the planner to create filters or jump to the problem areas of the project schedule very quickly.  This is a great interactive planning tool.  The manual bookmark options are located under the edit menu and on the Gantt toolbar.

Saving and Sending the Schedule Check Report

An .html or web-based report is generated each time the schedule check report is run.  If the report options are changed and the report is rerun, then the previous report will be overwritten.  The schedule check report will be saved in the same folder that the Pertmaster plan (.plan) file is located.  Users can choose to save a copy of the schedule check from within the internal Pertmaster report viewer.  With the schedule report open in Pertmaster, the project manager can open the file menu for options to export the file to a web-based, Microsoft Word, or text file format.

Pushing Schedule Check Data to Primavera P6 or Microsoft Project

Other sections outline the process of pushing data back to Microsoft Project and Primavera P6.  The schedule check data is one area that users often push data back to the original scheduling tool.  The original schedule file should be cleaned in the base tool and the file should be re-imported.  When the schedule check is run, the data is saved to user-defined fields for each check.  Certain checks such as the open-ended activities, which are seen differently in Primavera Risk, can be pushed back to user-defined fields so that users can create filters in the main schedule.  This can be a huge time saver for schedule cleanup instead of the scheduler going through a printed report manually.  It is also advisable that any flag that is not cleaned is documented for audit purposes.  If a scheduler leaves in a hard constraint, then they should justify why it is acceptable or most auditors will consider it wrong without even analyzing the situation.