To import a schedule from P6 into NetPoint, you must first go to P6 and export it as an XER file. While in P6, a couple of important steps should be taken to prevent any potential conflicts. For example, in NetPoint, the relationship calendar is based on the predecessor activity. This should have been set in P6 from the onset, but if not, it should be reviewed and updated beforehand (see “in P6” steps below). In addition, the project should be “scheduled” to avoid any potential terminations and “summarized” to ensure that the project start and end dates are correct. And finally, all activities should be of the “task-dependent” type.
Upon importing, a new NetPoint file will be created and the data from the XER file brought in. At this time, you cannot update or import into an existing NetPoint schedule. If the schedule was created in P6, or if it was created in NetPoint using a version prior to 4.1, release 25 Feb 2013, the user should run the automated layout engine to optimize the network. For more information, see [bookmark postid=”12646″ anchor=”run”]Running the Engine[/bookmark]. Instructions for importing are provided below.
If you’re importing/exporting “round-trip”, pay special attention to the notes in bold. A “round-trip” has occurred if the same schedule ends up back in the application it originated in, e.g. NetPoint -> P6 -> NetPoint or P6 -> NetPoint -> P6.
NOTE: Any start dates later than noon will be adjusted to the beginning of the next day; any finish dates earlier than noon will be adjusted to the end of the previous day. This will result in dates that are different from those in P6. This can be avoided by making sure all activities start before noon and end after noon.
*NOTE: Changing the calendar for the relationship lag can potentially affect activity dates. If the calendar is changed, please review the schedule afterward.
Columns can be sorted, added, or removed by left-clicking or right-clicking accordingly. At this time, only one project can be imported at a time.
|Import||Controls whether or not the item will be imported.|
|Activity ID||The identifier used in P6.|
|Activity Type||The type of activity as set in P6.|
|Activity Name||The description of the activity in P6.|
|Start||The date and/or time the activity begins in P6.|
|Finish||The date and/or time the activity finishes in P6.|
|Original Duration||The amount of time it takes the activity to complete in P6.|
Summarizes any discrepancies found during import. The report can be grouped by any field at the top. Columns can be sorted, added, or removed by left-clicking or right-clicking accordingly.
|Type||Type of notification. Info notifications include confirmations and minor incompatibilities, such as when items are converted to be compatible with NetPoint. Warning notifications include major incompatibilities, such as items that are changed, which affect logic, or items not being imported altogether.|
|Issue||A general category for the notification, such as calendars, resources, data dates, etc.|
|Item Id (NetPoint)||The identifier as found in NetPoint.|
|Item ID (Source)||The identifier as found in P6.|
|Item Description||The name or description of the item in question.|
|Message||The notification itself.|
|Resolution||How (if possible) the issue has been resolved.|
The following P6 objects and fields are brought into NetPoint. If a field is not listed, then it does NOT transfer. Some examples of fields that do not transfer are identified where relevant.
|This field in P6||Becomes this field in NetPoint||Notes|
|Start/Finish Milestone||Start/Finish Milestone|
|Level of Effort||Hammock||Only LOE’s which are connected to their fragnet by start-to-start AND finish-to-finish relationships will be imported as hammocks. If an object is found under multiple LOE’s, it will only be brought in beneath the first one. Any LOE’s left without any fragnets will not be brought into NetPoint.|
|Lag||Embedded node or link lag||If positive, the lag will be captured in the embed unless it is larger than the duration of the activity, in which case it will be captured in the link lag. If negative, it will be captured in the link lag for FS relationships or otherwise ignored.|
|Documents||Info Objects||Documents associated with activities, milestones, or benchmarks will be assigned to the appropriate object. Project documents will become info objects on the canvas.|
|Start||Start Date||Start dates later than noon are adjusted to the beginning of the next day.|
|Finish||Finish Date||Finish dates earlier than noon are adjusted to the end of the previous day.|
|Actual Start||Start Date|
|Actual Finish||Finish Date|
|Remaining Duration||Remaining Duration|
|Total Float||Total Float|
|Finish On/Mandatory Finish (milestones)||Finish benchmark||On activities, ignored.|
|Finish On Or After (finish milestones)||Finish-no-earlier than (FNE)||On activities, ignored.|
|Finish On Or Before||Finish-no-later than (FNL)|
|Start On/Mandatory Start (milestones)||Start benchmark||On activities, ignored.|
|Start On Or After||Start-no-earlier than (SNE)|
|Start On Or Before (start milestones)||Start-no-later than (SNL)||On activities, ignored.|
|Relationships||Relationships/Links||P6 allows FS relationships for start and finish milestones; however, in NetPoint a link with a start milestone as predecessor can only be SS or SF; a link with a finish milestone as successor can only be FF or SF. After a round trip, such links on milestones using FS links will be changed to match NetPoint requirements|
|Calendars||Calendars||Any calendars at the project level will transfer, regardless of whether or not they’ve been assigned; any calendars at the global level will transfer, as long as they have been assigned to at least one activity; and any global calendars from which a project calendar was created will transfer. Any calendar exceptions are NOT imported; therefore, any activities assigned a calendar with an exception should be reviewed after importing. NOTE: If you plan on going from P6 -> NetPoint -> P6 and updating an existing project, use the same number of working hours/day for all calendars in the schedule. When exporting out of NetPoint, this can only be set for all calendars globally. In addition, each time a schedule is imported into NetPoint, two calendars will be added for “United States” and “Calendar Days”. Review the calendars and delete any duplicates.|
|Codes||Codes||This includes all codes from the project level plus any codes from the global level that have had at least one of their values assigned. Unassigned values of global codes will not be brought into NetPoint. NOTE: If you plan on going from P6 -> NetPoint -> P6 and updating an existing project, don’t use global codes if you plan on making changes to them in NetPoint, since NetPoint cannot export them as global. If exported out of NetPoint, you will have duplicate assignments: one from the global level version of the code and one from the project level version of the code.|
|Activity Code Name||Name|
|Code Value||NA||Transferred into NetPoint but cannot be edited.|
|Resources||Resources||Any resource that has been assigned, regardless of which project it is under, will be brought into NetPoint; however, any resources that haven’t been assigned, even if within the same project, will not transfer. In addition, NetPoint only supports resources on activities. This means any activities with 0 duration (delays), milestones, or levels of effort (hammocks) will not have their resources transfer. NOTE: If you plan on going from P6 -> NetPoint -> P6 and updating an existing project, make sure all your resources are from the same project. Once imported into NetPoint, resources are given a unique ID. When updating back into P6, you will then have duplicate resources and assignments.|
|Resource Name||Name||The “Resource ID” field from P6 does not transfer.|
|Price/Unit||Cost/Unit||P6 stores the price/unit using hours (e.g. $0.125/hour). When the XER file is exported from P6, this value is rounded to 2 decimal places (e.g. $0.13), which is then converted to cost/unit, resulting in a different overall value. After importing from P6, it is recommended to review the cost/unit of each resource to correct for any significant differences due to rounding.|
|Budgeted Units||Rate/Dur or Rate/Day||An activity with duration type of “fixed units” will have its resources end up as rate/duration. An activity with duration type “fixed units/time” will have its resources end up as rate/day. When the XER file is exported from P6, this value is rounded to 1 decimal place (e.g. 0.15/day would become 0.2/day), resulting in a different overall value. After importing from P6, it is recommended to review the assignments of each resource to correct for any significant differences due to rounding.|
If the schedule was exported from NetPoint already, everything will be brought in EXCEPT for the following:
|Link Geometries||Become default|
|Embed Behaviors||Become constant|
|Custom Positioning||Becomes default|
|Resource Formatting||Become default (color, histogram patterns, color intensities)|
|Page Size||Becomes letter|
|Page Tiling||Becomes 1×1|
|Grid Spacing||Becomes default|
|Canvas Color||Becomes default|
|Calendar Strips||Become default|
|Calendar Sightlines||Become default|
|Text Size||Becomes default|