WIXLIB

Data exchange betweenCandy Planningand Primavera

Export Candy Planningto Primavera

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

SitePlan program viewExport the programIn the program manager highlight the program to be exported.Select Tools Export Export a Primavera 6. .XML

Which versions of Primavera’sXML can be exported ?P6 Version Release Date19.12Dec 1918.8Aug 1817.12Dec 1717.7Jul 1716.2Oct 1616.1Apr 96.720096.220086.1200752005Import a Candy XML file?Not yetNot yetNot yetNot yetNot yetYesYesYesYesYesYesNo longer supportedNo longer supportedNo longer supported

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

SitePlan program viewSave XML fileSave 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 structureActivities Activity number & descriptionsActivity durations -- Start and End datesPrecedence LogicTime now and actual dates (progress)BOQ * Net amount as a number per activity in a user defined columnSelling amount as a number per activity in a user defined columnNet amount per activity as a P6 resourceSelling 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 sheetsBase program and snapshotsSpecial types i.e. T-types (SitePlan hammocks)Codes i.e. zone, area, etc.Time location dataInformation and Long lead schedules dataResources No planning resources are exported No estimating resources are exportedGeneral Only planning data mentioned in previous slides are exported.No other planning data are exportedOnly BOQ data mentioned in previous slides are exported.No other estimating data are exported

What does not get exported ?Activities Remarks, notes and calculation sheetsBase program and snapshotsSpecial types i.e. T-types (SitePlan hammocks)Codes i.e. zone, area, etc.Time location dataInformation and Long lead schedules dataResources No planning resources are exported No estimating resources are exportedGeneral Only planning data mentioned in previous slides are exported.No other planning data are exportedOnly BOQ data mentioned in previous slides are exported.No other estimating data are exported

Import Candy Planninginto Primavera

Import the XML into P6In the home screen of P6 select File ImportChoose the option “Primavera PM – (XML)

Select the folder to import fromUse the dropdown menu to browse and select the XML file created byCandy

Choose the EPS to import toWith the file selected choose the import action “ Create New Project” andselect where to import to

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

Recommended import configurationThe above is the recommended configurationEnsure that you have the applicable user rights to allow changes

Import completeOnce complete you can choose to view the log file with information aboutthe import

End resultOpen the project and check dates, calendars and calendar allocation aswell as holiday exceptions

Logic differences between SitePlan and P6A Start Lead in P6 is the number of days from the start of apredecessor to the start of the successor.A Start Lead in SitePlan is the number of days of workdone in the predecessor before the successor can start.This will cause differences in results when there isprogress out of sequence.The same applies to End Lags.Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.

Recommended checksContract starts and ends; Target starts and ends areexported as constraints. Ensure that these constraints areset correctly in P6.All calendars are exported, but check that the holidays andnon-work days are set correctly in each calendar.A (T)ied activity is linked differently than a Hammock inP6. One of the Tied activity’s links is discarded during theconversion process. These activities must be re-linked inP6 according to P6’s conventions.Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.

Due to differences in calculation andthe activity types between productsthe responsibility for validating theresults must lie with those providingthe export file and those doing theimport.Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.

Export a Primavera XML filefor Candy Planning

Which versions of P6’s XML canbe imported into Candy ?P6 Version Release Date18.8Aug 1817.12Dec 1717.7Jul 1716.2Oct 1616.1Apr 96.720096.220086.1200752005Import into Candy?YesYesYesYesYesYesYesYesYesYesNo longer supportedNo longer supportedNo longer supported

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

Export the prgramExport the programIn P6 open the program to exportSelect File Export

SitePlan program viewExport the programSelect “Primavera PM – (XML)”.

SitePlan program viewExport the programEnsure the correct program is exported.

Export the programBrowse and choose where you want to save the XML file.Select the box “Export all project level layouts” to produce a smaller zipfile.

Import Primavera XML fileinto Candy Planning

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

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

SitePlan program viewAnalysis displayAt the end of import process an analysis report will be displayed.If any conversion problems were encountered it will also be included inthe report.

SitePlan program viewImported program in Program managerThe imported program will be added to the program manager.Select the program.

SitePlan program viewCustomise a view to include Import referenceAdd the import reference column to your document view to see the P6activity Id for comparison.

SitePlan program viewCalculate the programPress the Calculate button to calculate the imported program.

SitePlan program viewImport completeOnce complete check & compare the calendar, holidays and activitydates.

What gets imported into Candyfrom 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 Candyfrom 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 – notadvisable as Primavera allows “funny” progress like actual datesafter TimeNow / Data date or Actual finish dates with a remainingduration. Candy “ignores” this (with a message displayed afterimport)

What does not get imported?Activities Specialised activity types (other than task dependent) areimported as normal activities (example “Level of effort, milestones, etc.) No base program information.Layouts Only the WBS layout is imported – Imported as heading levelsin Candy. Note only 9 tree levels of WBS layout are imported – NOactivity 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 calendarsetc. are imported into CandyGeneral Only planning data mentioned in previous slides are imported. No other planning data are imported.

Logic differences between SitePlan and P6A Start Lead in P6 is the number of days from the start of apredecessor to the start of the successor.A Start Lead in SitePlan is the number of days of work done in thepredecessor before the successor can start.This will cause differences in results when there is progress outof sequence.The same applies to End Lags.Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.

Recommended checksContract starts and ends; Target starts and ends are exported asconstraints. 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. Oneof the Tied activity’s links is discarded during the conversionprocess. These activities must be re-linked in P6 according toP6’s conventions.Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.

Due to differences in calculation andthe activity types between productsthe responsibility for validating theresults must lie with those providingthe export file and those doing theimport.Primavera Project Planner and P6 are registered trademarks of Oracle Primavera Systems, Inc.

Select Help About Primavera P6 to get the release information. Export the prgram Export the program In P6 open the program to export Select File Export . SitePlan program view Export the program Select "Primavera PM -(XML)". 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 .