reflection projects are a little-known but very handy feature in primavera p6 professional. a primavera p6 reflection project is essentially a copy of a project but with one snazzy built-in trick – the ability to merge the copied project back into the original at any time. if the genius of this trick hasn’t struck you yet, it will.
this merging ability was designed to help planners work with scenario projects.
let’s say you’re the planner for a large capital project that is a falling behind schedule. the boss wants you to assess the impact of adding an extra shift to the work schedule. how much time can be caught up with this approach (ie: scenario)?
the thing to do here is to create a reflection of the project in primavera p6, add an extra shift and verify the finish date. if the boss approves the extra shift, then you can merge this scenario project into the original project along to keep the changes you made.
primavera p6 reflections save you the time of renaming projects, resetting permissions and copying and pasting changes from one project to another. there are also some nice options to help you create a backup of the original project in case you need to reference it again in the future.
step 1 – creating a reflection project in primavera p6
from the projects window, right-click on the original project and select create reflection from the menu.
if the original project has any baselines you will see pop-up window where you can select whether or not to copy these baselines into the reflected project. simply mark the checkbox in the copy column if you want to preserve any baselines in the reflected project.
you should now see a copy of your project in the projects window. the copy will have the same project id with “-1” appended. this reflection project will also be marked with a status of “what-if” which is primavera’s way of indicating the project is a “scenario” project and not a real project plan.
step 2 – open the reflection project and activity layout
you primavera p6 reflection project is now created and ready for editing.
now it’s time to run your scenario – ie: you can now make changes to the reflection project to run your scenario, test out a hypothesis, etc.
in this tutorial, we’ll make a small change to the reflection project’s 世界杯时间比赛时间 .
open the project and then open the activity layout provided the tutorial downloads section.
before we make any changes, you’ll need to make sure a key setting for working with 世界杯时间比赛时间 is set correctly in user preferences. go to edit -> user preferences, and click on the calculations tab.
set the “recalculate the units, duration, and units/time for existing assignments based on the activity duration type” option. this will make sure that primavera will perform the necessary recalculations when 世界杯时间比赛时间 are added or removed from an activity. close the user preferences window.
note: this step isn’t necessary when working with primavera p6 reflections, but i like to set this option when i’m doing resource-based scenarios.
step 3 – making changes to your primavera p6 reflection project
find activity a1020 – convert legacy data. you’ll be adding another resource to activity a1020 to see how this will affect the project’s overall finish date.
since the activity’s duration type is set to “fixed units”, adding an additional resource will have the effect of reducing the activity’s duration and spreading the units equally over the 3 世界杯时间比赛时间 assigned. let’s give it a try.
i’ll now add resource tom bell as a new resource assignment to a1020 and reschedule the project using the current data date and check the project’s finish date.
the project should now finish on dec 20, 2010 whereas before it was scheduled to finish on march 1, 2011.
step 3 – reviewing the reflection differences report
one of the best features of working with primavera p6 reflections reveals itself when you initiate a merge – the differences report.
the differences report will show you specifically what has changed in your primavera p6 reflection project.
go back to the projects window and right-click on the reflection project – “billing-1”.
choose “merge reflection into source project” from the menu. you should now see the differences report window.
this screen is really nice. it provides you with a report on the differences between the original project and the reflection at the activity level. you’ll see the value for say remaining duration from the source project, and the updated value from the reflection project.
from here you can choose which changes you want to merge into the original, or leave out by checking the box in the “merge” column next to the item. don’t like the updates on a particular activity? just leave them out.
primavera p6 also gives you some options to archive the original project, either as a baseline or as an .xer export file. this is *essential* as you’ll likely need to keep the original project around. and you can also choose how to handle the reflection – keep it, delete it or replace it (update it) with the new merged project.
step 4 – merging the reflection into the original project plan
if you agree to merging the projects, you can go ahead and set the options as above, and click “merge changes” to finalize the merge. you may want to print this differences report first, or you might even copy and paste it into a text document before you merge. you can do either of these by clicking the display bar.
with your scenario complete, don’t forget to communicate the results.
merging primavera p6 reflections – limitations
the merging process between a source project and a reflection project has some limitations that i’ll do my best to outline here.
permissions to create reflections and merge
the following permissions apply if you are running a version of primavera p6 professional that connects to an enterprise database – not a standalone version.
in order to be able to create a primavera p6 reflection project, you will need to have the permission to “add projects” in whatever project security profile you are assigned. most folks will already have this permission.
the ability to merge reflections requires further permissions. in order to be able to merge a reflection, you will require big access – yes – super admin. you will need to have the “<admin superuser>” global security profile in order to merge reflections.
deleted data in your reflection project
if you have deleted data in the reflection project, primavera p6 will have a very difficult time resolving the differences when you merge the project back together. according to oracle, the merge cannot distinguish whether or not an item was deleted from the reflection or if the item was added to the source after the reflection was created. (here’s another way to compare 2 project files.)
thus any deletions in your reflection will not be deleted in the source project during merge.
more specifically, the following items will not be removed from the source project if they were deleted from the reflection:
- activities
- relationships
- resource assignments
- wbs elements
- work products and documents
- project expenses
- project issues
- project risks
“merging will not necessarily remove items from the source project that have been deleted from the reflection. if major elements of a project have been deleted from the reflection, you will have to manually delete them from the source project if you do not want to keep the elements in the source project. elements that are not deleted during a merge include activities, resource assignments, wbs elements, work products and documents, project expenses, project issues, and project risks.” (primavera p6 reflections help file)
right away, this puts some limits on what you can do with reflections. but it’s clear that they were not meant to support major changes between source & reflection, only smaller, incremental changes.
dealing duplicate entries after merging
another set of limits is when you change the following items in the reflection:
- project id
- activity id
- resource id
- role id
- cost account
- price/unit
any changes to these items will result in new items being added to the source project.
for example, let’s say you change renumber activity id eng-2050 to a new id of eng-3050. that change will not be merged into the source project.
instead, a duplicate activity, eng-3050 will be added to the source project, resulting in 2 identical activities with different ids.
the same behaviour applies to the other items in the list above.
so you’ll definitely have to review your schedule after a merge to ensure there’s no duplication.
what else you should know about reflections:
- primavera p6 reflections are only available in primavera p6 professional (windows) and not in primavera p6 eppm (web) (check out this article for all of the differences)
- check primavera p6 help file for more information, like this handy faq about reflections
wrap up
primavera p6 reflections and merging features in primavera p6 are great features for the planner or scheduler who needs to run project scenarios or hypothetical analysis.
many planners also use reflections to help with progressing their project, especially when subcontractors are involved.
things for you to try:
- try making more than 1 reflection of the same project to compare multiple scenarios
download tutorial files
- want to follow along with this tutorial? grab the files below.
- project .xer and layout [reflections-tutorial.zip] – don’t know how to import our layouts? read how here.
this article was originally published in august 2011. it has been updated for accuracy.
