How to Prioritize Primavera P6 project using Project code weights and Project code

Oracle Primavera P6 provides a feature to prioritize or rank a project so that project manager will concentrate on the higher ranked project. Prioritizing a project involves many metrics, and it depends on the Organization. For example, A car company prioritizes their project based on the number of sales, number of defects and number of new models they released per month. In this case, a project with more defects, more model and less in sales gives more attention to the management. Also, a company may consider ‘Number of Sales’ has more weight than the ‘number of defects’ than the ‘new models’, so long thing short a project with lower rank requires manager attention.

So, two questions arrive here

1. Where I will add these measurements in Primavera P6

2. How I will add weight to the measurement, that is one metric has more weight than other

Primavera P6 Project code weights provide this functionally; let’s create an example scenario before going there so that we can understand this easily.

1. In my Primavera P6, I have 3 Car projects running, and they are below

2. I want to rank these project under three measurements, ‘Sales Per Month’, ‘Defect Per Month’ and ‘Model Per Month’. 

Note: The values I’ve mentioned here my own for demonstration purpose and they do not reflect actual values   

3. These three measurements are project codes in Primavera P6. As you notice below, I input Weight between 1 to 10 in the Project code; Here, P6 consider Sales has the higher weight than Defect than Model to rank a project; The Weight Percent calculates automatically based on the Weight, the overall Project Code weight percent should be 100. You can input any weight that depends on your project code

4. Below are the project code values and its corresponding weights on each project code. I input a number between 1 to 10 on each project code value; Just consider, less number means a high priority. The Maximum Code Value Weight calculates automatically; you can also input a Maximum code value weight;

5. That’s it. Add the column Project Score in the EPS tab. Again, less number means higher priority; On P6 16.2.6 onwards, P6 provides a visual indicator in the Project Score field like in Project Statistics (next screen)

Here,

Project Civic has performed well, so it requires less attention by the management 

Project CRV has poor performance and needs attention by the management

6. The same projects in Project Statistics portlet. J