Primavera P6 Reflections
In last week’s blog What Is A Reflection?, we discussed some of the key capabilities of Reflections in the Oracle Primavera P6 R8.1 Professional client. Since then we’ve received some great comments and ‘yes and’ ideas from folks who are using this capability out there in the field.
Evidently Reflections offer a much broader range of capabilities than those envisaged by its creators: and indeed those described in our blog. The original article focused on the manufacturer’s context: using Reflections for what-if analysis. Briefly, a Reflection allows you to save a linked copy of a project, update it and then merge those changes back into the original project. But that’s not all you can do with it.
John from Houston made the excellent point that “Reflections are not just for ‘what-ifs’, the uses, as always, are only limited by the user not the tool.” He describes their use as “a neat way of doing updates and keeping an update log for a project.” He points out that using Reflections in this way, means you still have your previous versions for documentation and claims purposes.
Keith from Fort Lauderdale suggests that a “Reflection is a great way to modify a project and then decide whether to keep the changes. Think of it as a way to update a copy of your project and then use the copy in place of the original just like people do in P3.”
Its always gratifying to see how folks make creative use of the tools to address their particular situation, so thanks indeed for all your comments and please keep them coming.
For more Primavera P6 articles click here