Data exchange between Candy Planning and Primavera

Export Candy Planning to Primavera

SitePlan program Before a program is exported ensure that all the logic links, BOQ links, etc. are correct

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

Which versions of Primavera s XML can be exported? P6 Version Release Date Import a Candy XML file? 17.7 Jul-2017 Not yet 16.2 Oct-2016 16.1 Apr-2016 Not yet 15.2 2015 15.1 2015 Not yet 8.4 2014 Yes 8.3 2013 Yes 8.2 2012 Yes 8.1 2011 Yes 7 2009 Yes 6.7 2009 Yes 6.2 2008 No longer supported 6.1 2007 No longer supported 5 2005 No longer supported

SitePlan program view Linked program If the program is linked to the BOQ, choose to export amounts or not.* * Only available for Primavera 6 release 7 export.

SitePlan program view Save XML file Save the XML file in your destination of choice

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 * Only available for Primavera 6 release 7

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

Import Candy Planning into Primavera

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

Select the folder to import from Use the dropdown menu to browse and select the XML file created by Candy

Choose the EPS to import to With the file selected choose the import action Create New Project and select where to import to

Modify import configuration You can select to modify the import configuration as required

Recommended import configuration The above is the recommended configuration Ensure that you have the applicable user rights to allow changes

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

End result Open the project and check dates, calendars and calendar allocation as well as holiday exceptions

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. Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.

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 activity s links is discarded during the conversion process. These activities must be re-linked in P6 according to P6 s conventions. Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.

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.

Export a Primavera XML file for Candy Planning

Which versions of P6 s XML can be imported into Candy? P6 - Version Release Date Import into Candy 17.7 Jul-2017 Yes 16.2 Oct-2016 Yes 16.1 Apr-2016 Yes 15.2 2015 Yes 15.1 2015 Yes 8.4 2014 Yes 8.3 2013 Yes 8.2 2012 Yes 8.1 2011 Yes 7 2009 Yes 6.7 2009 Yes 6.2 2008 Yes 6.1 2007 Yes 5 2005 Yes

Only P6.7 and later exports XML files Primavera P6 program The XML export described here will only work with Primavera P6 release 7 or later. Select Help > About Primavera P6 to get the release information.

Export the program In P6 open the program to export Select File > Export Export the prgram

Export the program Select > Primavera PM (XML). SitePlan program view

SitePlan program view Export the program Ensure the correct program is exported.

Export the program Browse and choose where you want to save the XML file. Select the box Export all project level layouts to produce a smaller zip file.

Import Primavera XML file into Candy Planning

SitePlan program view Import the XML into Candy In the Program Manager select Tools > Import > General importer. NOTE: First Unzip the P6 file, if received as a zip file.

SitePlan program view Select the XML to import Browse for the unzipped XML and Open to start the import. (Remember to unzip the file first if received as a zip file.)

SitePlan program view Analysis display At the end of import process an analysis report will be displayed. If any conversion problems were encountered it will also be included in the report.

SitePlan program view Imported program in Program manager The imported program will be added to the program manager. Select the program.

SitePlan program view Customise a view to include Import reference Add the import reference column to your document view to see the P6 activity Id for comparison.

SitePlan program view Calculate the program Press the Calculate button to calculate the imported program.

SitePlan program view Import complete Once complete check & compare the calendar, holidays and activity dates.

What gets imported into Candy from P6? Program Start date and TimeNow / Data date Only activity calendars used and allocated to activities are imported (including the holiday exceptions) WBS layout is imported as level headings.

What gets imported into Candy from P6? Activities Activity Id = Import into the Import reference column in Candy Activity descriptions Activity durations -- Start and End dates Precedence Logic (predecessors and successors) Actual start, Actual finish and Remaining durations not advisable as Primavera allows funny progress like actual dates after TimeNow / Data date or Actual finish dates with a remaining duration. Candy ignores this (with a message displayed after import)

What does not get imported? Activities Specialised activity types (other than task dependent) are imported as normal activities (example Level of effort, mile stones, etc.) No base program information. Layouts Only the WBS layout is imported Imported as heading levels in Candy. Note only 9 tree levels of WBS layout are imported NO activity code layout or filtered layouts are imported. No activity codes are imported. No user defined columns are imported.

What does not get imported? Resources No Primavera resources or resource data like resource calendars etc. are imported into Candy General Only planning data mentioned in previous slides are imported. No other planning data are imported.

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 nonwork days are set correctly in each calendar. A (T)ied activity is linked differently than a Hammock in P6. One of the Tied activity s links is discarded during the conversion process. These activities must be re-linked in P6 according to P6 s conventions. Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.