Export SitePlan to P6.

7
 SitePlan program view

SitePlan program
Before a program is exported ensure that all the logic
links, BOQ links, etc. are correct
 What gets exported?
Program
Start date and TimeNow date
Multiple calendars with holiday/workday exceptions
Summary headers as a work breakdown structure

Activities
Activity number & descriptions
Activity durations -- Start and End dates
Precedence Logic
Time now and actual dates (progress)

BOQ
Net amount as a number per activity in a user defined column
Selling amount as a number per activity in a user defined column
Net amount per activity as a P6 resource
Selling amount per activity as a P6 resource
 What gets exported?
Activity types
Special activity types are exported as follow:
Contract start = Mandatory start
Contract end = Mandatory end
Target start = Start on or before
Target end = Finish on or before
B type = Start on
H type = Normal activity with universal calendar (7days) allocation
Tied (hammock) = normal activity (P6 hammock / level of effort links are different)
F type = As late as possible
V type = normal activity (P6 does not have such a type)
M type = normal activity (P6 does not have such a type)
K type = normal activity (P6 does not have such a type)
What does not get exported?
Activities
Remarks, notes and calculation sheets
Base program and snapshots
Special types i.e. T-types (SitePlan hammocks)
Codes i.e. zone, area, etc.
Time location data
Information and Long lead schedules data

Resources
No planning resources are exported
No estimating resources are exported

General
Only planning data mentioned in previous slides are exported.
No other planning data are exported
Only BOQ data mentioned in previous slides are exported.
No other estimating data are exported
 SitePlan program view

Export the program

In the program manager highlight the program to be
exported.
Select Tools > Export > Export a Primavera 6.7 XML
 SitePlan program view

Linked program
If the program is linked to the BOQ , choose to export
the amounts or not.
 SitePlan program view

Save XML file

Save the XML file in your destination of choice
Import SitePlan into P6.7
 SitePlan program view

Import the XML into P6

In the home screen of P6 select File > Import
Choose the option Primavera PM (XML)
 SitePlan program view

Select the folder to import from

Use the dropdown menu to browse and select the XML
file created by Candy
 SitePlan program view

Choose the EPS to import to

With the file selected choose the import action Create
New Project and select where to import to
 SitePlan program view

Modify import configuration

You can select to modify the import configuration as
required
 SitePlan program view

Recommended import configuration

The above is the recommended configuration
Ensure that you have the applicable user rights to allow
changes
 SitePlan program view

Import complete
Once complete you can choose to view the log file with
information about the import
 SitePlan program view

End result Cost loaded program

Open the project and check dates , calendars and
calendar allocation as well as holiday exceptions
 SitePlan program view

Budget Forecast WBS level

Above is a sample of a report with budget forecast at
WBS level
 SitePlan program view

Budget Forecast Activity level

Above is a sample of a report with budget forecast on
selling amount per activity.
 Logic differences between SitePlan and P6
A Start Lead in P6 is the number of days from the start of a predecessor to the start of the successor.

A Start Lead in SitePlan is the number of days of work done in the predecessor before the successor can start.

This will cause differences in results when there is progress out of sequence.
The same applies to End Lags.

Recommended checks
Contract starts and ends; Target starts and ends are exported as constraints. Ensure that these constraints are set
correctly in P6.

All calendars are exported, but check that the holidays and non-work days are set correctly in each calendar.

A (T)ied activity is linked differently than a Hammock in P6. One of the Tied activitys links is discarded during the
conversion process. These activities must be re-linked in P6 according to P6s conventions.

Disclaimer
Due to differences in calculation and the activity types between products the responsibility
for validating the results must lie with those providing the export file and those doing the
import..

Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.