just before the christmas break, oracle quietly released primavera p6 professional version 20.12. i’ve had a few days to explore this latest version of p6. here’s what’s new in primavera p6 professional version 20.12.
in case you forgot, oracle publishes updates to the on-premise version of primavera p6 annually in december. so we’ve all had a full year to adjust to primavera p6 version 19.12 – and there were a few nice improvements in that version.
but considering all of the new fixes & enhancements in version 20.12 – all i can say is….wow! nice work oracle! (i don’t think i’ve ever said that).
let’s dive into the details of what’s new in this latest version of primavera p6 professional.
in case you prefer it over the mighty written word, watch my video detailing what’s new in primavera p6 version 20.12
(check out the 世界杯2022亚洲比赛时间 video channel for all of our tutorials, webinars & sample course lessons)
what’s new in primavera p6 version 20.12
let’s start.
database configuration gets trickier for sql dbs
oracle has revamped the login screen in version 20.12. while that isn’t really news-worthy, what i did notice is a major update to the database configuration wizard.
up until version 19, we’ve seen this same old legacy wizard that walks us through configuring primavera p6 professional to connect to a database. this wizard was very handy in walking you through the steps to configure the connection to a database; especially handy for sql connections.
in version 20.12, that wizard has been removed and now we have a single screen to input our connection data.
the real difference for us here is the move to inputting a connection string in the form of <server>/<instance>\<database_name> to connect to sql databases. this is new for us and will no doubt trip some folks up.
(i’ve already had 2 clients ask for help on it.)
new! add comments directly on relationships
that’s right!
we’ve been asking for it for 100 years, and we’ve finally got it – a comment field tied directly to a relationship!
now we can better document relationships, why we added this specific one, what the lag is for – directly on the relationships tab, with great visibility!
the implementation of the is pretty simple. it’s a new text field called “comments” that was added so you can leave documentation on specific relationships. currently you’ve got 250 characters to work with.
i also did some testing and saw that within the reports area (only), you can build a report that can group or filter on this comments field.
this is a nice additional feature in primavera p6 version 20.12 and will help contractors and owners reach a new level of transparency around relationships.
more options when scheduling multiple projects
if you ever manage multiple smaller projects together as a megaproject, you’ll be able to take advantage of this new p6 v20.12 feature.
when you open 2 or more projects together, you’ll see some changes to the scheduling options screen. (actually you’ll see these changes even with 1 project open now, but with 2 or more project open, these options come alive).
at the top of p6’s scheduling options screen, you’ll now see the option to choose which project’s scheduling options to use when scheduling your projects.
as i was investigating this new feature, i got curious –
does p6 save the scheduling options as they are set with a project in the project itself??
yes it does now.
when you open a project, and make a change to the schedule options, you’ll be asked if you want to save the options. that’s new!
now, in primavera p6 version 20.12, when you’ve got more than 1 project open, you can then pick which project’s saved scheduling options to use when scheduling projects together.
this feature will help schedulers keep their p6 settings consistent in a multi-project situation.
there’s a bit more related to this feature. read on.
new setting: all projects use their own data date
oracle has migrated an option that used to only be in p6 eppm over to primavera p6 professional in version 20.12.
the option is called “all projects use their own data date” and you’ll see it on the scheduling screen. again this is applicable when scheduling multiple projects at the same time. you can now choose to set a single data date when scheduling a group of projects, or to let projects keep using their own data date.
one of the trickiest parts of working with sub-projects that combine into a megaproject is around data date. typically every project would have a different data date. now with this new feature schedulers will have a lot more control over which data date gets used in a multi-project scheduling scenario.
new codes: resource assignment & role codes
well, this one i never saw coming.
in fact, there’s so much in this update, i’m a bit stymied.
we’ve got project codes, activity codes, resource codes, and now assignment codes & role codes!
yep. in this release of p6, you’ll find 2 brand new type of codes – the assignment code & the role code.
i’m not to excited about role codes, as i don’t ever use roles, so let’s move past them.
you can now use assignment codes to categorize, group and analyze your resource assignments in p6 v20.12.
assignment codes are (wait for it) global-data, which means they are setup as the enterprise level, not at the project level.
so while this is gives us more reasons to use the resource assignments screen, i’m a bit concerned about more data that admins will have to administer and clean-up when importing & exporting projects from their database.
above is an example of implementing an assignment code called “shift type” and assigning values to the resource assignments.
another concern for me, is that things are getting confusing. have a look at the resource assignments screen column chooser.
what do i want here? there’s a ridiculous amount of “codes” and “user defined” fields to pick from. how do i know if i want an assignment code or a resource code?
there’s some great potential for schedulers to get lost in fields and also to misunderstand how they should be used.
imho assignment codes were added as tool to improve categorizations in p6 eppm (just a hunch). but perhaps there will be good use-cases for this type of coding to come. right now, it’s not obvious to me how i would use this, or why.
new: financial period calendars
another surprising new feature!
financial period calendars allow you to use different financial periods for different projects.
oracle has finally fixed what was a long-time limitation to using financial periods. in case you didn’t know, financial periods let you store partial updates for activities that span more than an update period.
the limitation was always that the periods, the spans of time between updates that would create a bucket, were set for once for the database. so if one project did monthly updates, and another project did weekly updates, only one of these could use financial periods because they were set globally. there was no way to set periods for each project.
now there is a way with financial period calendars.
a financial period calendar is a construct that allows you to build an periods you like.
now we can pick which ones to use on our projects with a new setting at the project level.
as more and more projects use resource and cost-loading, financial periods become a real asset in storing partial period performance.
the skinny is that this is a great enhancement in primavera p6 v20.12 that will enable many companies to start using financial periods to their advantage.
new: better fill-down & across in resource assignments spreadsheet
you can now fill down and fill across quickly in the resource assignments spreadsheet. you can fill data on the resource assignment spreadsheet window from the right-click menu. you can fill data from several cells simultaneously.
this is another nice feature for those who like to do bucket planning from the resource assignments spreadsheet.
new: display exact values for histogram bars
another nicety rolled into p6 version 20.12 is a small feature that will make graphs much easier to use.
there’s now a checkbox called “show value” that can be found in the graph settings that enables specific bar values to be printed on-screen, similar to excel.
the result, i’d say, is graphs that are much easier to read and analyse.
conclusion
there are quite a few updates in the new primavera p6 professional version 20.12 that will take me some time to filter through and get used to.
overall, i’m very happy with this update as there’s a lot of meat on the bone; as paying users i think we’re entitled to get a good update like primavera p6 version 20.12 delivers more often than not.
as i promised in my video above, i intend to get dig deeper into some of these new features in future posts.
what do you think about this new version of primavera p6? leave me comment and let me know.
