NetPoint will import and export to Primavera P6 versions 6.0, 6.1, 6.2, and 7.0. Version 8 is not supported. The user must have administrative privileges, and the Primavera Integration API must be installed in the following directory:
Otherwise, the menu options will be disabled. If you’re unsure whether or not these criteria have been met, please contact your IT department.
Preparing to Import
Before importing a schedule from P6 to NetPoint, the project must be scheduled in P6 (by pressing the F9 key or selectingfrom the menu bar). Otherwise, the import process may terminate abnormally, or imported dates may become corrupted.
NetPoint only calculates lag based on predecessor calendar. Primavera or Microsoft Project may already have this as the default setting depending on version, but it is necessary to confirm/adjust to this recommended setting. For P6, this is found in the main menu at Options button and go to Calendar for Scheduling Relationship Lag and choose Predecessor Activity Calendar. In addition, when a NetPoint schedule is exported to Primavera, this is automatically set for the schedule as a function of the transfer.click the
Finally, the project start and end dates reported by the P6 API may not be correct unless the schedule is “summarized” in P6 before the import. The schedule should be summarized (via the “Tools->Summarize” menu option) immediately before the import. Failing to do this can result in incorrect calendar start and end dates being imported into NetPoint.
To import from Primavera, clickfrom the menu bar.
The P6 Import Authorization window will open.
Enter a username and password with administrative privileges and click OK.
The P6 Import Selection window will open displaying a list of projects to choose from.
Select a file and click Import.
Once a schedule has been selected, a pre-import report is generated in Excel and a confirmation window opens. This report identifies any items unsupported by NetPoint and explains how they will be handled. The user should review and understand the report.
NetPoint imports resources on a full-time basis only. If any activities in P6 have fractional durations (e.g. 5.5 days) and are imported into a day-based NetPoint schedule, NetPoint will round their durations down (if finishing before noon) or up (if finishing after noon). Resources would then be distributed based on the assignment selected for the activity (per day or per duration). If per duration is chosen, the rate will remain constant. Check the pre-import report for any discrepancies in activity durations or resource assignements.
Calendars & Holidays
Calendars will be imported from P6 into NetPoint, but holidays will only be included if they fall between the start and end dates of the project. If a holiday coincides with a non-working day, it will not be transferred into NetPoint.
Activity Codes & Actual Dates
NetPoint will import activity codes as well as maintain actual dates when importing for any activity for which actual dates have been entered.
To finalize the import process, click OK.
After importing, NetPoint will place multiple activities per row, but will attempt to minimize clashing and conflicts. As a result, some manual repositioning may be required. To customize the position of the different data elements, see Minimizing Clashing and Global Edit Mode.
NetPoint only calculates lag based on predecessor calendar, Primavera or Microsoft Project may already have this as the default setting depending on version, but it is necessary to confirm/adjust to this recommended setting. For P6, this is found in the main menu at Tools > Schedule > click the Options button and go to Calendar for Scheduling Relationship Lag and choose Predecessor Activity Calendar. In addition, when a NetPoint schedule is exported to Primavera, this is automatically set for the schedule as a function of the transfer.
To export to Primavera, click P6 Export Options window will open.from the menu bar. The
Enter a Username, Password, and P6 Project ID.
Choose whether or not to export Project Codes as Primavera’s activity codes.
In NetPoint, multiple values per code may be assigned to the same activity. In P6, however, only one value per code may be assigned to the same activity. Project codes are not exported if they are allowed to have multiple values in NetPoint (even if only one value is actually defined for the code or assigned to an activity).
Choose whether to export resources.
In NetPoint, an activity may have some resources assigned to it “per day” and other resources assigned to it “per duration”. This is called a mixed assignment. In P6, all resource assignments for a given activity must be of the same type. For more on distribution types, see Assignment Options.
Convert Mixed Assignment to will convert ONLY those activities with mixed assignments while leaving activities with uniform assignments as is.
Convert All Assignments to will convert ALL activities, whether their assignments are mixed or uniform, to the selected distribution.
NOTE: When using PolyTime, resource assignments may be inaccurate when exporting a plan that is in any time unit other than days. The following approaches may be taken to correct the outcome: 1) wait to resource load the schedule until the file is exported; 2) reassign every resource to every activity after exporting to correct the values; or 3) delete the resource assignments prior to exporting and start with a clean resource-assignment slate, but with resources defined.
Info objects that have been attached to activities, milestones or benchmarks will export as P6 documents and be assigned to the appropriate object. Info objects drawn on the canvas will also be exported and associated with the exported project.
When finished, click Export. A new EPS node called NPXfer will be created within P6 and the schedule is exported to that node. P6 can be opened or closed during the export process; however, the user may have to refresh the data to see the changes.
NOTE: After exporting, make sure to schedule the project in P6. Until this is done, milestone and benchmark dates may show up as 1 day later.
NOTE: When exporting a schedule where hammocks are present, the hammock must include at least one activity, otherwise the schedule may not export and/or logic may not transfer. Milestone and benchmarks (event objects) may be included in a hammock where a start event object is connected to a successor activity and a finish event object is attached to a predecessor activity. Further, recommended hammock definition in NetPoint is where the hammock contains a continuous network of member objects.
NOTE: Recurring holidays are not supported in P6. As a result, a NetPoint fixed-date holiday with a repeat factor of 1 year may cause the export to fail. To avoid this, delete the fixed-date holiday and replace it with a new annual holiday.