Skip to main content

Why You Should Upgrade From Oracle Primavera Risk Analysis to Safran Risk – Part 2

I’m Ian Nicholson, VP Solutions at Emerald Associates. I have been working with Oracle Primavera Risk Analysis (OPRA) since 2001 when it was Pertmaster, Emerald being the exclusive Canadian distributor for Pertmaster until their acquisition by Primavera in 2006.

In this series of blogs, I will explain why I feel that all OPRA users should upgrade to Safran Risk (SR).


In my last blog post, I discussed the technology used in OPRA vs SR. As I mentioned in that blog, the biggest complaint that we hear about OPRA is that the technology cannot support a large risk model. The second most common complaint that we hear is that the user interface is clunky and moving reports and layouts from one model to another in order to generate consistent outputs is tedious.

When OPRA (at the time called Pertmaster) was re-introduced as a Risk Analysis tool in 2001 (it had previously been a CPM scheduling tool), it had a pretty decent user interface (UI) for the time. It looked like a typical CPM scheduling tool that had an extra “Risk” menu for Risk inputs and extra items added under the “Reports” menu for Risk outputs.

For most risk users of the time, the UI was fine because Schedule Risk Analysis (SRA) was a new and relatively immature concept that was performed infrequently by relatively few people. These users would learn where to find the required items in the Risk and Reports menus. Hey, if you could master P3 or Artemis, Pertmaster should have been a walk in the park! Besides, compared to Primavera’s Monte Carlo add-on, Pertmaster’s UI was a big step forward in usability.


OPRA's Risk Menu


OPRA Reports menu

After nearly 20 years of SRA, things have changed significantly. We now have defined risk maturity models, organizations have made SRA part of their project management methodology, and project teams build their own risk models. More people need to be able to work in the tool and getting them up to speed quickly and easily requires a logical workflow inside the tool.

When Safran developed Safran Risk (SR), they used their experience of the original Pertmaster’s development to modernize their new tool’s User Interface and make it easier for users to understand and learn. The first step that they took was to change from a menu based input model to a workflow based model. This means that SR has replaced the menu based system with a tab based sequential workflow system. The user moves from left to right as they build the risk model.


The other item of note here is that all of the functionality of Safran’s scheduling tool is also here (a big advantage of building the risk engine on top of the scheduling package). Users can create layouts and filters and share them between users and projects, making application of standard processes and reports much easier than in OPRA.

Does an updated UI make the upgrade worthwhile? Not in and of itself, but it does make training new users much easier and makes it much less likely that a user will miss a step in the process. I personally find that Safran’s UI just makes everything easier. I still occasionally talk to P3 users who recall that its UI was the best ever, but I doubt that they would want to go back and work with it today. I’d love to have a classic sports car (say a TR6) in my garage, but I sure wouldn't want to have to drive one to work in the Canadian winter!

In my next blog post, I’ll discuss the benefits of integrated cost and schedule risk analysis.

No video selected.

About the Author

Ian Nicholson, P.Eng. - VP Solutions

As our VP Solutions and a Lead Risk and Implementation Specialist, Ian leads Emerald’s functional consulting group. With over 20 years of international experience in varied fields and roles from manufacturing, heavy civil construction, pharmaceutical plant construction, hospital projects and oil and gas capital and turnaround projects, Ian brings a wealth of project knowledge to all of our clients.

A visionary in the world of CAPEX, maintenance and turnaround planning processes, Ian has lead many of our large clients through their integration projects between ERP/EAM systems and Primavera products. Some of his integration success stories include Suncor Energy SAP to Primavera integration, BP Maximo to P6 integration, implementation of P6 at the Ontario Power Authority as well as the integration of Primavera Contract Manager with Oracle Financials at Capital Health Authority and Vancouver’s Rapid Transit Project 2000. Other major clients include Milwaukee Metropolitan Sewerage District, Shell Canada and Shell Global Solutions.

Ian has conducted Monte-Carlo risk analysis on CAPEX and turnaround projects for Shell Canada, Suncor Energy, Husky Energy and Bruce Power. He believes that successful Monte Carlo application is a process, not just a tool and has spoken at a number of events on the correct application of risk analysis.

When not assisting clients with their projects, Ian unwinds by riding his BMW motorcycle, listening to music or dragging his kids on long hikes.

Leave a comment

Please login to leave a comment.