[Latest - Step by Step Guide - Install, Setup and Configure Oracle Primavera P6 Professional R22.12 on Windows 10/11 - Link]
Content Summary: During a recent program on Oracle Primavera P6, few participants found it difficult to install, setup and configure P6 Professional edition. They faced either some scripting issues or certain permission issues. Later on came to know, many face those issues. In this post, I'll elaborate a complete step by step installation, set up and post set-up configuration for Primavera P6 Professional Release 8.3 in Windows 7.
Primavera P6, the EPPM tool from Oracle, is widely used in certain sectors, such as construction, aerospace, manufacturing - in Project and Portfolio Management. However, people come up with issues during installation. In fact, it is not at all difficult to install and configure, if you understand what are the needed components for the installation. More importantly, if the components are already available (installed), then the installer will skip them. There are 5 major components for installation:
.NET framework (comes bundled with 4.0)
Java Runtime Environment (JRE) 7.0 or later (comes bundled with 7.0)
DHTML component
Oracle Database XE Edition, and of course,
Primavera P6 Professional 8.3.x software (Client side)
If you have Java, .NET, DHTML and Oracle XE installed, you just need to install the 5th component. However, Primavera P6 software media pack comes bundled with all the above components. So irrespective of installation of those components, the installer application will check their availability and based on that, the installer apps will do the necessary operations. However, there few issues found while executing certain scripts post installation. This is during the DB Connection creation for the user, which ultimately boils down to permission issue. The error that you may get is shown below:
To fix the issue, you have to simply set the permission and execute the script. The script in question is: "manual_script_before_install.sql". It is detailed in the below installation document shared via GDrive. The document covers in detail explanation of all the steps involved to set up Primavera P6 Professional R8.3.x (8.3.2 is used here) in Windows 7 along with issues that you might face. The steps will remain same for Windows 8. For complete step-by-step instructions, subscribe to this blog (on top right corner of this blog) and send a mail, from your gmail id to managementyogi@gmail.com.
The document is available for viewing in PDF format - Link.
Note: Post installation, I always suggest participants to perform some basic configuration for the usage of Primavera P6, like:
Setting up your Industry type from Admin Preferences.
Getting the option to choose last project, all projects, global data etc when Primavera P6 starts up, which will be from User Preferences.
Setting the currency option
Setting the Time Units
Setting up Dates
There are also certain other post set-up configuration needed, however, for this post I'll limit to these few.
Note:A course covering Project Management Professional (PMP) certification with Oracle Primavera P6 (and its certification) is available. This has been used by professionals worldwide. For details, check:
[NEW: ACP Exam Prep Book Available - "I Want To Be An ACP" (Link)] In the previous post, we created an Agile BurnUp Report with MS Project 2013 directly without switching to any other apps.
Let us analyze the graph a bit more.
As it is baselined, the “Baseline Cumulative Work” line is shown. However, it is below Cumulative Actual Work. Hence more work has been done than actually baselined.
The “Cumulative Work” is above the “Cumulative Actual Work”, which understandable as we have work to do, i.e., the pending work.
The above interpretation can be seen by adding another filed called "Cumulative Actual Work" to the Task Usage details. It is shown as below. I have switched to Resource Usage view here, as it will be easier to understand.
As you can see, the actual work field has values as we had entered in the previous post. The cumulative work by end of 1st week is 49h, whereas the cumulative actual work is 45.5h. And the baseline cumulative work is, of course, 40h.
Now, let us do a few formatting for the Labels for 3 the series of "Cumulative Work", "Cumulative Actual Work" and "Baseline Cumulative Work" and it will look as:
To perform above the customization for deeper interpretation of data, add the labels for all the lines as shown below. It is for "Cumulative Work" line. You can change the color coding from Blue to any other color as well.
After you add the Data labels, you can format the Data Labels and place them, customize them the way you want. Also from the field list, you can choose to add additional fields.
The best part in all of these - you do not need to go Excel for your reports. Baseline is a good addition as actual work for a task might be more than initially planned (or can be less) during the Sprint and Baseline information shows - how much we have actually varied from the initially planned one.
-- Few Key Notes --
Question - Can I variants of this chart in Bar format? Yes you can. Just change the Chart Type as shown earlier. Like it can be as shown below.
Question – Can I copy the report to another apps, say PowerPoint, directly?
Yes, you can. Use the Copy Report functionality as shown.
Question – Can I create a PDF copy?
Yes, you can. Just use the Export PDF functionality and it will work.
Some say, it is not possible to create PDF for reports. Wrong! It is possible and it works perfectly. Set your print setting properly - orientation, size and margin.
In conclusion, few may agree with you that MS Project will help you can create Agile Reports. I think it is unfair. In fact, a number of interesting fields are added like - Baseline Cumulative Work, Remaining Cumulative Work, Remaining Cumulative Actual Work, and so on - with which you can create a number of Agile specific reports.
[NEW: ACP Exam Prep Book Available - "I Want To Be An ACP" (Link)] With MS Project 2013 one can create a number of Graphical Reports directly – one of the new features introduced. This helps you NOT to move to another apps – say Excel or Visio, but still be able to create most of the reports. In my view, it is a good strategic move by Microsoft. By default, MS Project comes with an inbuilt Burndown Report. But how about Burnup report? Can someone create it? Yes and quite easily. Two points to note here:
I am focusing on Iteration Burnup Chart in this post. In Iterations (or Sprints as it is called in Scrum), for a burnup chart, we will have Days in the X-axis and Hours in the Y-axis.
My belief as a PMI-ACP/Agile Practitioner is that for Sprint planning estimation is done in hours whereas for Release Planning, estimation is with Story Points.
Alright. Let us proceed. I have two tasks– to make it quite simple and easy to understand. Each tasks starts on Monday, here Nov 10 and Nov 17, respectively and finishes by Friday. Both are executed by a work resource,i.e., Resource 1.
Select Report tab – View reports – New Report – Chart. Give a name “Agile Burnup Report”. You will have a new report as shown.
Go to Field List (on the right side), select the Category is a “Time”. If field list is not shown, then simply select the graph and select “Show Field List”.
In the “Edit” check box, as shown in the Field List, have the following respective scale set for Units, Date Format and Count. This is to increase the visibility area of the chart and check a day by day Burnup for the iteration/sprint. It is shown as below.
Now, from the Field List, “Select Fields” un-select all “Actual Work”, “Remaining Work”, and “Work”. It will turn to a Blank Chart now. Again from the Field List, “Select Fields”, select “Cumulative Actual Work” and “Cumulative Work” under Work field. Under Work – Baseline, select “Baseline Cumulative Work”.
Select the Chart. Go to Chart Tools – Design – Type – Change Chart Type and change the type to Line – Line. A line chart will be displayed now. The chart will be as shown below:
Let us interpret the data:
Cumulative Work is finally 80 hours (for two tasks with week long work each) by end of Nov 21, which is correct.
No actual work has been entered. So the Cumulative Actual Work is 0 hr. It is actually on the X-axis, but has been overridden by the Baseline Cumulative Work value.
No baseline has been done yet, so that line is also dormant and actually on the X-axis. Look closely! As noted in the previous point, if you remove "Baseline Cumulative Work" from the graph, the "Cumulative Actual Work" will be shown.
Next, baseline the Project, via Project – Schedule - Set Baseline.
Go to View tab – Task Usage View and select “Actual Work” and “Cumulative Work” from Task Usage tools – Cumulative Work. With the help of “Add Details”, add the field “Baseline Cumulative Work”.
Set the status date. In my example, the status date has been set after 5days of the project. Initially the actual work done by the resource is empty, i.e., for Task 1, which is executed by Resource 1, from Monday to Friday - actual work field is showing empty.
Enter the data for the “Actual Work” performed by the Resource. After I entered actual work done by Resource 1, the task usage details is shown as below.
Now go back to your created Report. You now have a Custom Chart called “Agile Burnup Report". Select it from Report tab - Custom - Agile Burnup Report. It will look as shown below.
Our simple example can be expanded to have multiple tasks. As noted earlier, during Iterations/Sprints, it is about tasks and estimation is in hours. Many ask to estimate in Story Points in the iteration for the tasks, which I really do not agree with. As story point should be actually considered on a longer time horizon.
You can customize the report, export the report, copy the report or create various other Agile reports with the help of MS Project.Will see that in next post.
One of the participants in a class for MS Project 2010/2013 was having trouble in viewing Critical Tasks in his customized view of the Project Management Plan and few weeks after the session, asked me ways to check them. Now, critical tasks are important from scheduling perspective and a seasoned project manager frequently checks on them. MS Project gives a number of options to check on critical tasks. In fact, there are so many options that it wont be possible to outline them all in this post! It is immaterial which view you are in or which table you have applied - you can easily check your critical tasks. The easiest and quickest way is outlined below in # 1. Way # 1: Option Under Format Tab
Let us take a simple example. I have 5 tasks and 2 milestones with duration as shown below. To see the critical tasks, go to Format Tab -- Bar Styles group. Under that, select the checkbox for "Critical Tasks". The critical tasks will be highlighted in red in the Gantt view.
Critical Tasks - Enabling Option from Format Tab
Above - Task 3 and Task 5 are Critical Tasks, whereas Task 1, Task 2 and Task 4 are Non-Critical Tasks.
Still, you might be in different views or different tables, but still you can check on the Critical Tasks.However, as noted earlier, you have enough options to check on critical tasks wherever you are in MS Project. In rest of the ways, we will reuse the above simple example.
Way # 2: Switch to Tracking Gantt View
Another important view which you will use frequently is the Tracking Gantt View. Here, the critical tasks are also shown and are highlighted in red. You need not select any checkbox, rather it will be done by MS Project for you. To switch to Tracking View: use View tab -- Task Views group -- Other View -- More Views and select Tracking Gantt View from the opened up dialog box.
Critical Tasks in Tracking Gantt View
Tip: The checkbox noted earlier in Way # 1 is automatically selected when you switch to the Tracking Gantt View!
Way #3: Use Filter for Critical Tasks
Go to View tab -- Data group. Under that, select Filter: Critical from the drop down menu as shown. Critical Filter is one of the built filters in MS Project. After selection, only the critical tasks will be shown, irrespective of your view. In the below image, critical tasks are filtered and shown for the Gantt Chart View. The non-critical tasks will be filtered out.
Critical Tasks - Applying Critical Filter
As you can see, the Critical Tasks - Task 3 and Task 5 - are only shown in the filtered view.
Tip: To disable Filter, select Filter:[No Filter]
Way # 4: Highlight Critical Tasks
Critical Tasks in the complete plan can be highlighted in a different color. To do that, go to View tab -- Data group -- Highlight: Critical, which is to be selected from the drop down menu.
Highlighting Critical Tasks
As you can see, the critical tasks are highlighted in yellow.
Tip: To disable highlighting, select Highlight:[No Highlight]
Way # 5: Group Critical Tasks
There is not only a built-in filter for Critical Task, but a built Critical Task group. To group the critical tasks, go to View tab -- Data group -- Group by: Critical.
Grouping Critical Tasks
Both the critical and non-critical tasks are grouped and shown to you with Critical:Yes and Critical:No headings.
Tip: To disable grouping, select Group:[No Group]
Way # 6: Switch to Detail Gantt Chart
Detail Gantt View is another view which you will use to check on the delayed introduced due to leveling and used when you perform resource leveling. Here critical tasks are shown by default and are highlighted in red.To switch to Detail Gantt View, use View tab -- Task Views group -- Other View -- More Views and select Detail Gantt View from the opened up dialog box.
Critical Tasks in Detail Gantt View
Way # 7: Switch to Network Diagram View
Network Diagram View is another important view used by professional users of MS Project. This gives a clean and easy way to check on the activities/tasks in a Nework Diagram. Here critical tasks are shown by default and are highlighted in red.To switch to Network Diagram View, use View tab -- Task Views group -- Network Diagram View.
Critical Tasks in Network Diagram View
Nework Diagram view used the Precedence Diagramming Method (PDM) as noted in PMBOK and shows task details along with dependencies.
Way # 8: Add Critical Field to the Table
Critical Tasks can be seen in various task tables - it does not matter which table you are in - by adding a new column/field called "Critical", which is built into MS Project.
To do that, simply right click on the table side of the view and select "Insert Column" and then type in "Critical" to be have the field added as one of the columns in your table. The critical and non-critical tasks will be populated with "Yes" and "No" values, respectively.
Column "Critical" in the Entry Table showing Critical Tasks
Way # 9: Use Critical Task Report
MS Project 2013 has a new Tab introduced - Report tab. Here, you can generate a report for Critical Tasks. Go to Report tab -- View Reports group -- In Progress and select "Critical Tasks" Report from the drop down menu.
In Built Critical Task Report
Here, the status of the Critical Task - Complete, In Progress, Future etc. - all will be shown. As our simple project has a planned start date on Nov 17, 2014, all critical tasks are shown as Future Tasks. If you are in MS Project 2010, go to Project tab -- Reports group -- Overview -- Critical Tasks.
Still, there are few more ways to check on critical tasks. Like you can create your own custom filter or custom group and apply different color code or switch to yet another view called "Descriptive Network Diagram View" to check on critical tasks. However, I hope the above 9 ways would suffice to check on critical tasks in your project and will meet your need. Update (February 2, 2018): To know the various ways to check Critical Tasks, a video has been made available for you! This is from MS Project 2016 Live Lessons - Guaranteed Learning or Your Money Back. The video is from Lesson 9: Analyzing Project.
