If you’re part of the Primavera Community you know what the bane of most user’s existence is. It’s, of course, Java. Java, that once heralded Sun developed software that enabled developers to deploy code on almost any platform, has had it’s issues lately to say the least. In Primavera software, Java is most common in the applets that run within P6 and is the cause for most of the support calls relating to stability and performance. Users have been waiting patiently for Oracle to clear the decks of Java applets within P6. As of version 17.7, which will be released the week of July 17, 2o17 they will have made significant inroads into delivering on that promise.
In this new release most Java applets will be replaced with HTML5 views and those few that remain can be disabled. The new HTML5 views in 17.7 are:
|• Capacity Planning
• Global Search and Replace
• Activity Network
• Resource Overallocation
• User Interface Views
• Schedules Services
|• Trace Logic
• My Calendar
• Status Updates
• My Preferences
• Calendar View
• My Issues Portlet
The Java Applets that remain and can be “switched off” include:
|• Risk Management (Project Tab and Dashboard Portlet)
• Resource Planning (Resources Tab)
• Workspaces (Projects Tab)
There are many other refinements and new features in Primavera P6 included in the release that we’ll discuss at a later date. But for most users the ability to cut down on your Java intake is a great reason to look at upgrading to the new release. We’d be glad to help you evaluate your current P6 environment with our P6 Health Check and recommend how you can chart your best path forward.read more
As many times as I have conducted Primavera P6 training, I am always surprised by the under use of one of the basic P6 tools.
A Scheduler painstakingly builds a schedule to reflect reality and then after the project starts, neglects to take advantage of the opportunity to be proactive in managing negative float and variance trends. The tool is the P6 Baseline. Sure, most Schedulers create a baseline at the onset of a project and, if following best practices, assign it to the Project Baseline to make it globally available for all users to view. Assigning to the Project Baseline ensures that any P6 User comparing the “BL Columns and Gantt Bars” is viewing data from the original Baseline.
But how about Updated Baselines for trend analysis?
With all the focus on managing negative float within a schedule, the Finish Date variance trends sometimes get lost in the shuffle. It is extremely important to understand that, even when an activity has positive float, if the Finish Date Variance is trending in a negative path, the activity may soon have negative float. The ability to see the negative trend and adjustment the schedule accordingly can prevent the activity from ever having negative float.
Consider the following:
Utilizing data in the table below, at what point would you recognize that the Foundation activity had a negative float issue? CYCLE 5??
|Update #||Update Date||Activity||Float||BL1 Finish Date Variance|
If you were capturing updated baselines each cycle and monitoring the negative Finish Date Variance trends, it is likely that you noticed a potential problem on Cycle 3. Being the proactive person you are, you take action to mitigate the negative trend activity from ever getting into negative float territory.ly
So what is the suggested best practice?
- Capture a baseline each time you update the schedule and assign it to the Primary Baseline
- Use variance analysis layouts to monitor trends using Activity Table columns such as BL1 Finish Date and BL1 Project Finish Date Variance.
- Consider capturing past period Finish Date Variances in User Defined Fields to watch for trends occurring over multiple Update cycles.
- Design P6 Report Writer reports to use color coded conditionally formatted cells to highlight negative float/negative finish date trends as red and positive float/negative finish date trends as yellow.
- Take action on the scenario where positive float activities have multiple Update Cycles with negative Finish Date Variances.
Let’s assume you have made an enterprise decision to manage all of your projects using Oracle’s Primavera software. Smart move! Let’s also assume that you have spent considerable amounts of dollars purchasing the product along with Oracle Maintenance. You have decided to have CBA, Inc. install your product and are ready to send your users to our terrific training classes.
Everything is installed, users are trained and it’s time to get to work – but wait…the system isn’t configured yet…the users cannot manage their projects yet…what to do?
Consider software configuration a time saver that each new customer to the Primavera software product line should seek out. Having a professional qualified provider, like CBA, work with you and your users to identify, develop and implement best practices for your unique business and configure the system according to your specific requirements will allow your team to not miss a beat when they return from training. Being proactive and pre-determining configuration services will allow your newly trained staff to know exactly were to find those very powerful tools they just learned about and know exactly were to begin.
As a part of your overall project plan, CBA’s Primavera Implementation services are extremely beneficial, cost-effective and an efficient solution to the learning curve blues.
Sure, you could try to configure the system yourself; but you’ll most likely end up wasting valuable time and spending more money trying to figure everything out by a process of trial and error than if you just paid to have the system configured ahead of time.
CBA, Inc., will make certain that your investment works from day one!
Call me: Donna McLean, Account Executive CBA, Inc. 567-202-9289read more