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.  Sometimes the schedule import is not flawless.  This article will details some of the key reasons that a schedule import may be flawed.

Video Walkthrough of Common Oracle | Primavera Risk (Pertmaster) Import Issues (Duration: 6 min: 32 sec)

Common Issues Importing a File to Primavera Risk

Listed below are a list of common issues with a Primavera Risk import:

• Out of sequence logic is in the schedule.
• Progress Overrides vs Retained Logic setting came over incorrectly.
• The data dates for sub-projects are not aligned.
• The planning unit setting caused duration rounding.
• There may be issues with Primavera P6 database.  This is often seen after a Primavera P3 file is migrated to Primavera P6. 
• The incorrect planning unit was used for import. 
• Primavera Risk does not read secondary constraints. 
• The lag calendar settings could have been imported incorrectly.  The settings should be checked. 
• The Primavera P6 plan was not scheduled (F9) before exporting. 
• A Microsoft Project plan with sub-projects was not imported from the Microsoft Project toolbar (Review the MSP import module). 
• The project or sub-projects were not statused to time now.  The project contains actual dates in the future or remaining duration in the past.
• The % Complete is driving earned value in Microsoft Project.  The % complete field may be adjusting the remaining duration value.