a new version of primavera p6 professional has recently dropped: primavera p6 v21, and i’m here to tell about what’s new, what’s great and what’s not.
i feel it’s my heartfelt duty to schedulers everywhere to unpack these yearly updates and highlight all of the features that are changing or improving, or are still broken. i love to do it, and i’ve been doing it for years.
here is the yearly schedule of releases for on-premise users of primavera p6 professional; sometime in q1 of the year, oracle releases a new version of p6 that’s a xx.12 version, where the xx is now the calendar year, and .12 represents december. now, anyone using primavera p6 “in-the-cloud”, or oracle’s cloud-hosted implementation of primavera p6, will be getting these updates monthly as oracle updates cloud-hosted installs regularly every month. but many of us are still using standalone or on-premise installations are not privvy to monthly updates, but rather yearly updates (xx.12).
in case you want to find out what has changed in primavera p6 from your current version, to the latest version, you can use oracle’s cludgy and oddly-name cummulative feature overview tool (why can’t they just do release notes like everyone else?). here’s a link to the latest interation of the primavera cummulative feature overview (cfo) tool. and yes, it covers both p6 professional and p6 eppm.
now let’s see what’s new in primavera p6 v21.12.
what’s new in primavera p6 v21
start and finish times are never greyed out anymore
if you’re a seasoned scheduler, you probably work like this, the way i do:
i always set my user preferences to show the 12 hr clock next to dates in p6.
why?
because primavera p6 can schedule activities down to the hour, and if you aren’t monitoring the time of day that is being schedules, things get messy in a hurry.
partial durations, partial total float values and incorrect start and finish times can cause inaccuracies that will multiply in your schedule. so, we generally always turn on the clock to scrutinize start and finish times.
but in the past, if you did not turn on the 12 hr clock in user preferences, the ability to edit time of day for fields like the data date or a constrait date would be greyed out.
but in primavera p6 v21.12, even if you do not turn on the 12 hr clock in user preferences, you can still edit the time of day fields next to any date.
such a simple fix will make sure we can have a bit more visibility on the time of day for dates in p6.
multiple improvements to xml files in primavera p6 v21
xml import and export support has been consistently improved by oracle over the past few years.
this p6 version, as well, comes with improvements to xml support. here is what’s changing:
- maintain relationships with external projects when importing from primavera xml files
when you import projects from a primavera xml file, you can choose whether to retain relationships between activities in the project and those in external projects. - resource calendars
when p6 professional is connected to a p6 eppm database, you can differentiate between the types of resource calendars you are importing from the p6 xml template. the type column in the advanced section of the import options dialog box labels the calendars as personal or shared. - select the financial period calendar to assign when importing a new project
when you import projects from a primavera xml file, you can select the financial period calendar to assign to any projects you choose to import with the create new import action. - assignment cost exports
when you export to primavera xml, price per unit data for assignments is included in the export file.
problems with p6 costs and xml files?
with regard to the item assignment cost export above; xml files will now contain price per unit data from the p6 resource screen, units & prices tab.
while i’m a bit surprised it wasn’t always supported, there might be some concerns with supporting this data in xml files going forward, but not having backward support for the same feature. it’s a bit complex to understand. but take for example, 2 companies on different versions of p6, passing data back and forth via xml file. there’s a good chance that project costs could become inconsistent between the 2 databases because of support for this new data for one company, but not for the other. i’ll leave it to my colleague paul harris to explain further here – just grab his pdf file for an explainer.
financial period calendars: support for importing & exporting
a new feature in v20.12 was a new type of calendar; the financial period calendar. you can read more about how financial period calendars make using financial periods a cinch now. but since last version, there’s been limited support for fp calendars, such as during import or export.
now in v21.12, you’ll see a new option on the import screen that let’s you choose which financial period calendar to assign to a project on import. that way you can ensure you assign the correct fp calendar to new projects imported into your database.
resource cost spreads now reflect rate changes
another surprise! p6 professional will now accurate reflect any changes to a resource’s hourly rate in spreads.
when it comes to changes in a resource’s hourly rate (see image of units & prices tab above), p6 has always done the math correctly; that means the total cost field has always taken into account an increase or decrease in hourly rate. however, those changes have never been displayed in places where we see “spread data”, like the resource assignments screen, or the activity usage spreadsheet and profile views.
and now there’s a new admin setting that will toggle if you want to see changes in hourly rate reflected in spreads, or not (the old way).
let’s dig in a bit here.
i create a simple labor resource called “trades person” that has an hourly rate increase of $50/hr from 19-jan-2026. this date happens to be smack in the middle of an activity i assigned her to on my project.
if we check out the resource assignment “spread”, you can see that the budgeted cost field on the left correctly tallies to $20,000. the * on the price/unit field indicates that there is a rate change. this result is nothing new at all. it’s how p6 has always worked – the totals are correctly calculated, but the spread is an averaged cost.
here’s a glimpse of the new admin setting in primavera p6 v21 that controls how spreads display changing hourly rates.
here’s what we get if we set “cost spread” to “unit spread” in p6.
as you can clearly see, with the new “unit spread” setting, we can now accurate see resource cost spreads that take into account hourly rate changes.
as this is an improvement in accuracy, i’m still wondering if it will really make a deep impact an anyone. personally, i don’t use hourly rates for cost-loading schedules. i teach how to cost-load without hourly rates for fixed-bid type projects.
a quick note that this setting also applies to role cost data and role spreads as well.
resource driven critical path visibility
this is the last feature i’ll mention. here’s the description on this new feature in the release notes.
“to aid in the resolution of delayed critical paths before they become project over-runs, p6 professional can show:
- activities on up to 30 activity-driven critical paths, calculated on the forward pass, backward pass, or forward and backward passes (with or without resource leveling).
- the activities on up to 30 resource driven critical paths, calculated on the backward pass with resource leveling.”
while i’m very intrigued, i cannot figure it out yet.
there is a new toolbar you can add to your screen called “activity critical path”. the buttons do something, but i’m not sure what exactly. more to come on this feature soon.
how would i rate this primavera p6 v21 release?
as always, i’m thrilled to see new features and to recognize oracle for fixing things that are long overdue to be fixed.
this release has a big focus on the cost-side of things, especially related to hourly rate changes; the new support for that in xml files, and in resource spreads. hopefully some people welcome these enhancements.
i personally don’t think there’s too much to rave about with regards to resource hourly rate enhancemet. like i said earlier, i don’t use them and i don’t know many users who do.
but it’s becoming clearer that we will have to soon abandon the xer file and replace it with the xml file. as i see more and more supported features in the xml file, it won’t be long before we have to switch.
what do you think about the new version of primavera p6 v21? leave us a comment.
