The first step of a typical Oracle | Primavera Risk (Pertmaster) Monte Carlo analysis is to import the file. This training session will outline how to import a project schedule into Pertmaster from a Primavera P6 backup (.xer) file.
A significant difference between importing from a database connection and a .xer backup file is the available import mappings. All information in a .xer Primavera P6 backup file will be imported. Users cannot exclude activity codes, user-defined fields, and resources as they could in the Primavera P6 direct connection method. Users have two places to import a Primavera P6 backup (.xer) file:
For audit purposes the values may have been loaded in Primavera P6. Schedulers may have also chosen to load each activity with a manual minimum, most likely, and maximum value. Occasionally users may have these situations, however it is most common for no risk information will be loaded in the Priimavera P6 schedule. The templates in Pertmaster provide users with some powerful and time-saving features for risk loading. If the fields are not brought in upon import, then they can be synchronized after the import by following the menu path File | Primavera | Edit Default Import Mappings… After adding the desired fields, the project manager will click the “synchronize Primavera data” button and the fields will be available in Primavera Risk.
Import Options Pop-up:
Import Mappings Tasks Tab:
Import Mappings Probabilistic Tab:
If the project planner would like to push data back to the Primavera P6 database, then they will need to import via a connection to the Primavera P6 database. Users can export a Pertmaster plan as a Primavera backup (.xer) file. The export option is listed under the path File | Primavera. The file will be created directly from Pertmaster. This is usually not a desirable option as it will completely rewrite the file based on Pertmaster’s CPM scheduling engine and options. Although the file will be reasonably clean it is still not advisable in many situations due to small differences in the scheduling engines.
Copyright © 2021 PRC Software. All rights reserved