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 schedule planning options should be automatically set based on the options set into your scheduling tool (Microsoft Project, Primavera P6, etc), however it is a best practice to review the settings and ensure they were imported correctly.
The scheduling options tab is one of the most important settings sections in the Primavera Risk product. Users are able to define how the CPM scheduling network is calculated by the scheduling engine. The scheduling options will be inherited from the original scheduling tool. For example, if a planner has turned on progress overrides in Primavera P6, then Pertmaster will see this option upon import. If users changed a setting without rescheduling the project, then a mismatch is possible.
The calendar used on the lag will be set based on the setting of the original scheduling tool as well. Many scheduling tools put the calendar for a lag on the same calendar as the predecessor, however this is not standard for all scheduling tools. This is important because putting a 7 day lag when the lag calendar is 5 days could create up to 11 calendar days of lag time, instead of the intended 7 calendar day lag.
All options should import from the original scheduling tool, however it is a best practice to always check the options before starting a Monte Carlo analysis. The options in this section include:
Copyright © 2021 PRC Software. All rights reserved