What is the use of making a reflection in P6
Featured Partner
Top Posters
Ashkan Mohammadi
0 posts
Jeroen De Bauw
0 posts
Senior Planning Engineer
0 posts
Kristian Mcwilliams
1 posts
dagogo dan - jumbo
2 posts
Alex Lyaschenko
27 posts
James Williams
75 posts
xerxes
0 posts
edwin
0 posts
jhalluk69
0 posts
Our Partners
That was very usefull
Thanks
Check also these websites:
http://tensix.com/2011/11/oracle-primavera-p6-%E2%80%93-what-is-a-refle…
http://tensix.com/2011/11/oracle-primavera-p6-r8-1-reflecting-on-reflec…
Regards,
Ahmed Aziz
I personally havent used reflections that much.
Does anyone know how reliable they are in terms of merging the changes correctly?
Is it more reliable than the update baseline function?
Rodel's description is excellent. If you'd like to learn more about how to use reflections, you can view this tutorial I recently put together. https://www.planacademy.com/use-reflections-primavera-p6-to-merge-scenarios/ Hope it helps shed some light on the topic.
M
Haresh,
A reflection is a copy of an active project that contains a link to the original project. It is almost the same as copy Project but reflection allows you to make changes to the reflection and then merge selected changes back into to the original project, keeping active project data such as timesheet information intact.
This is new function of Primavera allows multiple users to update reflection copy and merge it back to master schedule and allow planners to view the changes and incorporate only the changes that the planners wanted to. This functions is good to multiple user working offline in different station and make their own update.
A reflection is a copy of a project that has the following characteristics:
-> Has the same name as the original source project with reflection appended to it.
-> Internally, contains a link to the source project that allows the application to merge changes to the reflection into the source project.
-> Has a what-if status.
After creating a reflection, you can make changes to it. If desired, you can then merge selected changes back into the source project keeping active data in the source project intact. Creating a reflection facilitates the following work flows and processes:
-> Creating a sandbox area to test different project scenarios.
-> Reviewing changes made by team members to activities they own in a reflection. Using the reflection as an intermediary project lets you review and accept changes before merging the reflection back into the source project.
-> Reviewing changes to a project by exporting a reflection as an .XER file. You can send the .XER file to outside users who can import the file into their database. After making changes to the project, the outside users can export the file and send the resulting .XER file back to you. By importing the .XER file back into your reflection, you can decide which changes to keep when you merge the reflection back into the source project.
Best Regards,
Rodel