Review by Tim Breeding

I’ve been working with Primavera P6 in the Oil Refining industry now for 10 years.

The only certain thing is that profits are getting thinner.

I’m certain this story resonates with every industry. This means that project execution and the administrative costs of running the business must become more and more eficient.

Let’s face it, enterprise software is expensive and Oracle’s Primavera P6 is no exception.

PrimaveraReader get the easy your organization the ability to avoid the steep cost of providing P6 access across your entire organization, but is your organization in the position to benefit from it?

 

Hard Numbers

 

 

Let’s get the easy stuff out of the way. I own a copy of Primavera P6 Professional myself and it’s expensive.

 

The lowest possible price you can get away with is about $1100 upfront for only one year of the license and support.

The Perpetual license is $2500 and you pay an annual recurring support cost of $550, so your 5-year cost is around $5,250.

I don't know the specific costs for the Enterprise version of P6, but we know that it’s expensive and requires a lot of overhead to manage.

PrimaveraReader costs $249 per user and the price goes down from there depending on how many licenses you purchase. Keeping the software completely up to date costs roughly 20% of the license fee, so your 5-year cost is under $500. That is less than 90% than the price of a full P6 license.

I was a site superuser for a plant that had around 200 users. Managing licenses, rights profiles, the OBS, etc is expensive. Limiting the number of licenses, and thus the complexity of your Primavera configuration can save you a lot of time, money, and headaches. There are many other subtle factors that can affect the cost of running Primavera, but for a small company it’s fairly straight-forward. If you’ve got one scheduler or PM, you only need one Primavera license.

 

The OODA Loop

 

 

The OODA Loop is an acronym with military roots (surprising, right?). It stands for Observe, Orient, Decide, Act.

 

ooda loop

It illustrates the iterative nature of the activities we engage in. In all of the daily hustle of our work lives, we often forget that the only reason we produce information is to make a decision, act upon that decision, and then see where that decision took us.

Too often, we just start producing information for the sake of keeping busy or feeling productive, but we should focus more on making our efforts more focused and useful. Scheduling is a purely iterative process.

Scheduling information is typically issued to the field via PDF. The PDF is static and uncompromising. It’s often very busy, thus difficult tease out the insight you need to make effective decisions. An experienced scheduler can flip through multiple views per minute to review the status of the project. The PDF does not allow this.

Some organizations call for schedulers to issue several different PDFs to accommodate different players within the organization. One for the PM, one for this supervisor, that supervisor, etc. This can take quite a lot of time. At one point I was on a team of four schedulers that were issuing five different PDF files per day. I calculated that the PDF generation alone was costing the organization $100,000 a year. Custom PDF layouts can limit visibility also by hiding the interdependence between different resources when certain teams only want to see their own work.

You must be able to look at the information in various ways, quickly, to gain enough insight to make decisions to move forward. How can you do this?

 

PrimaveraReader, the tool you need

 

 

What is needed is a simple, cost effective way for project team members to have the freedom to look at project data in manyways, quickly that doesn’t burden the scheduler or PM with creating a bunch of static PDF files. PrimaveraReader is the tool you need, for some people.

 

PrimaveraReader in actionSource: PrimaveraReader

I have used some other tools excel-based XER viewing tools in the past. I actually built one myself from scratch a decade ago. PrimaveraReader is the cleanest and most intuitive interface I have seen thus far. It looks like it’s built using the MS Office suite so it will familiar to almost anyone, but they have also mimicked the P6 look and feel enough so that P6 users will feel at home as well. The videos available on their site make it easy to learn, so adoption shouldn’t be a challenge.

PrimaveraReader allows you to look at the schedule in many different ways very quickly. Changing columns and filtering is easy, but the feature I really like is the ability to use layout files from P6. Simply put, you can’t ask for a much easier interface when it comes to manipulating a P6 schedule.

 

Updates and Analysis

 

 

There are several key features that PrimaveraReader contains that make it more than just a simple XER viewer. One of these features is the ability to compare up to four different XER files at a time. This is the Baselines feature. This is a very nice tool for analyzing how the project is unfolding. Again, it is very easy to use.

 

They have also implemented the Trace Logic view from P6, but actually made it better looking. This is useful for gathering a visual representation of how the activities relate to each other. Again, it has a very clean appearance and works very similar to P6.

Another feature is the Progress Update. It allows you to update progress very easily within PrimaveraReader and then export the updated schedule to an XLS and then import it back into P6. It’s quick and easy to update.

PrimaveraReader also allows you to review global data such as calendars which is great for administrators to ensure they’re not importing anything they don’t want.

 

What I like?

 

 

As a person who is extremely comfortable in software I love the idea of PrimaveraReader.

 

It gives you the ability to look at a schedule in many different ways, very quickly. It feels very familiar to P6 and MS OÕce so it’s easy to feel at home in the application. And the software runs very smoothly, it's actually faster than P6.

Cost.

Relative to a full P6 license, it’s cheap. For most companies, it’s cheap enough to buy just to see if it’s right for your organization. It’s a very low-stakes investment.

Mobile.

PrimaveraReader offers an iOS version which looks good and runs smoothly. Nothing or Android yet, but I’d bet they’re working on it.

 

What’s missing?

 

 

I wish the Printing were a bit better organized. The page-setup dialog box doesn’t have an ‘Apply’ button to you have to close the window for every change making it hard to dial in your print-preview quickly. I would add most of the features from the 'Options' tab of the page-setup straight to the Print view; there is plenty of real-estate for it.

 

It would be nice if the Filtering mimicked P6 more. Nested filtering is a key piece of building views and layouts.

I would also like to see a Group and Sort feature similar to P6. Also, to one-up P6, it would be nice if you could to a layered sort just by hold the shift or control key and clicking on columns in order.

Overall I would like PrimaveraReader to have more analysis tools; like S-Curves and Histograms for looking at performance and resource needs in a more visual manner. Also, I would like to see more schedule integrity analysis tools as well; similar to the 14-Point DCMA assessment.

 

Is this right for your organization?

 

 

I’ve worked in Oil & Gas for a decade now and most of the work processes I’ve seen have always centered around a dedicated Scheduler doing all of the work inside P6 while receiving written or verbal progress updates from the field. I have rarely encountered field supervisors, superintendents, or even managers that are comfortable enough inside P6, or a computer in general, to take advantage of having P6 installed on their own computer. If this is the case in your organization, I don’t know if PrimaveraReader will be a good fit. Be cautious about using the progress update feature, only for that fact that people tend to mismanage files and folders and you’re likely to get an old Excel file from someone. This can cause serious frustrations and miscommunication. Or even worse, you could update your actual P6 schedule with bad information.

 

That being said I would like to see PrimaveraReader implement some more enterprise features that would push the baselines, layouts, and latest version of the schedule to the appropriate people involved in the project. This would save you from having to individually import the Layout Files, and reload baselines, etc. This would go even farther to fiatten the learning curve.

However, I am starting to see a newer generation of managers and superintendents that are interested in using software tools rather than just looking at printed schedules and reports. PrimaveraReader is perfect for these people and organizations.

In conclusion, I would definitely use PrimaveraReader in my company. I would focus on building the work processes and the rhythm of the project around Primavera to ensure people are looking at the right schedule at the right time, particularly in the mobile app. It’s inexpensive, fast, and as intuitive as something this complex can be.

 


If you want to try this solution, here it the link.