Creating Projects


Overview

Two types of projects can be created:

Types of ProjectsSchedule File*
Qualitative Risk Register OnlyNot required
Complete ProjectRequired

*Supported schedule files include P6 XER files (.xer) and NetPoint files (.np4/.npz).

Risk Register Only

  1. In NetRisk, click the Main Menu  icon in the upper left corner.

  2. Choose New Risk Register Project.

A schedule can be subsequently added at any time to the risk register by updating it with a schedule file. For more info, see Updating Projects below.

Complete Project

  1. In NetRisk, click the Main Menu  icon in the upper left corner.

  2. Choose New Project from File.

  3. In the lower right-hand corner, choose either P6 XER File (*.xer) or NetPoint File (*.np4/*.npz).

  4. Navigate to the desired file and click Open.

  5. See Mapping User Defined Fields below.

When importing XER files, please ensure that the project was scheduled and summarized after the latest changes were made in P6 and BEFORE exporting it as an XER file.

The following features of P6 will NOT be maintained after importing into NetRisk: resource calendars, lag calendars set to use the calendar of the successor activity.

Exporting P6 XER Files

  1. Open the desired project(s) in Primavera.

  2. Click Tools > Schedule.

  3. Click the Options button.

  4. Click the Schedule button.

  5. Click Tools > Summarize > Open Projects.

  6. Click OK.

  7. Click File > Export.

  8. Choose Primavera PM/ MM - (XER) and click Next.

  9.  Choose Project and click Next.

  10. Check the box next to the desired project(s) and click Next.

  11. Name the file and click Finish.

Mapping User Defined Fields

User defined fields (UDFs) created in Primavera P6 can be mapped to NetRisk fields. To map a UDF, check the box to the left of the field name and choose an option from the dropdown to the right.

Non-supported fields will not show up in the interface.

P6 UDF TypeImported?Available Field Mapping
CostNoNone
Finish DateYesNone, only available when exporting out of NetRisk. See Exporting Percentile Results to P6.
IndicatorNoNone
IntegerYesCode, Max, Min, Most Likely
NumberYesCode, Max, Min, Most Likely
Start DateYesNone, only available when exporting out of NetRisk. See Exporting Percentile Results to P6.
TextYesCode, Correlation

Correlations must be defined using the activity ID. For multiple correlations, separate them using a comma. By default, the coefficient will be set to 1; however, it can be specified in parenthesis immediately following the ID of the activity. For example: "A1000 (.7), A1010 (.5), etc.".

If after mapping, the fields comprise a valid duration distribution, the Distribution Type will automatically be set and the box checked for including in the simulation, as follows:

Mapped FieldsDistribution Type
Only Max, Min, Most Likely (unique)Triangular
Only Max, Min, Most Likely (equal)Constant
Only Max, MinConstant

When updating a project, the following behavior is observed:


No Fields Checked for Mapping1 or More Fields Checked for Mapping
Existing ActivitiesNo changeUDF data previously imported overwritten
New ActivitiesNo UDF data importedUDF data imported

Saving Projects

  1. Click the Main Menu  icon in the upper left corner.

  2. Choose Save or Save As....

  3. Enter a filename and click Save.

Updating Projects

If a schedule has changed since the original import, the new schedule file can be used to update the existing NetRisk project, all the while maintaining any prior simulation results, inputs, and risk register information.

  1. To update an existing project, click the Main Menu  icon in the upper left corner.

  2. Choose Update Project from **** File.

  3. If the project has never been saved, you will be prompted to save first.

  4. In the lower right-hand corner, choose either P6 XER File (*.xer) or NetPoint File
    (*.np4/*.npz).

  5. Navigate to the desired file and click Open.

  6. See Mapping User Defined Fields above.

  7. In the confirmation window, click Dismiss.

Tip

Updating is done by matching activities to one another through their IDs. This means the user can always update any activity by simply ensuring it has the same ID, regardless of whether or not it actually represents the same activity.

Updating only works for schedules where every activity contains an ID. If one or more activities lack ID's, the updating feature will be disabled.

Jump to:


Still Need Help?

Click the icon above or visit our support desk.