oracle announced new updates to the primavera p6 suite at march’s oracle industry connect event. i wasn’t there, but i did recently attend a webinar about the recent release and i’ve been playing with the new versions of primavera p6 professional and primavera p6 eppm. i’ve put together an overview of what new with primavera p6 15.1 to share with you all.
this release has updates for both primavera p6 professional and primavera p6 eppm (enterprise project portfolio management) so if you’re using either of these tools, read on to find out what’s up. but don’t be surprised that there’s been many more enhancements to primavera p6 eppm than to primavera p6 professional.
1) new version numbers for primavera applications
if you haven’t read our last post, “all primavera products jump to version 15.1 – here’s why” which explains oracle primavera’s new version numbering, then you probably should have a read. the short of it is that all products, including primavera p6 professional and primavera p6 eppm are moving from version 8.4 to this release, version 15.1. the new numbering will help you understand which products in the primavera suite integrate successfully with other products.
2) primavera application integrations
as we mentioned in 1), oracle is continuing to improve on the cross-application integration of their primavera suite. one integration that’s been getting a lot of attention is primavera p6 to unifier. since the world is on mission to get cost and schedule data in a single system (or close, but it’s never really nice for users), oracle has been focusing a lot on how p6 schedule data and unifier cost and business data can be passed back and forth. many companies are passing data from unifier to p6 (and back) using primavera gateway as a go-between.
unifier allows for business processes to be managed and tracked as they move along various stages. in primavera p6 15.1, users can now associate a business process with a primavera p6 task. the result is that business process progress can now flow to primavera p6 and status an activity. you can pass % complete, actual dates and other progress data. the example karen pilla has given is for an rfi. you would associate an rfi in unifier with p6 activities which are updated as the rfi progresses in unifier.
3) resource bucket planning in primavera p6 eppm
although primavera p6 professional and primavera p6 eppm were often said to have the same functionality in terms of planning & scheduling, there were clearly some major gaps from the start. however, those gaps are continuing to be filled and the addition of resource bucket planning to primavera p6 eppm is a welcome one.
in case you don’t know what resource bucket planning is, here’s a review. in resource management with bucket planning, you can edit how a resource’s hours are spread out by editing the hours allocated in each “bucket” or time period on the resource assignments screen. by default, p6 will spread hours out evenly.
in primavera p6 eppm v15.1, you can now have the same control over your resource hour allocations on the resource assignments screen. this is a nice addition to primavera p6 eppm that many will take advantage of.
4) support for integrated master schedule format
companies that work with the us government and others governments/companies that have adopted the un/cefact standards will find that primavera p6 has support for the ims (integrated master schedule) format in version 15.1. in p6 15.1, you can now export your project in a fully compliant un/cefact ims format. apparently previous versions of primavera p6 had this features, but some of the data elements were missing in the export. the export is now fully-compliant to the standards.
as part of this enhancement, you can now map p6 activity codes and user defined fields to un/cefact fields, dates and durations. and you get this power in both primavera p6 professional and primavera p6 eppm.
5) import / export of baselines in the xml format
although adoption of the xml is slow and the xer format is still widely used (unless you’re only using p6 professional), i’m happy to see that in 15.1 you can now export both a project along with it’s baseline(s) in the same file – (man we need this in the xer format too!).
previously, there was a painstaking process to go through of detaching a baseline from it’s project, making a copy, reattaching the copy, then exporting the project and it’s baseline. ….well, i guess we still have to do this on the p6 professional side. but not in eppm anymore. this will make some lives much easier.
6) better support for database auditing
primavera p6 eppm has had auditing support from previous versions, but oracle has made things a bit easier. the auditing controls have been moved into the application settings area within eppm, making it easier to manage. the auditing reporting are available in bi publisher.
as you can see here, inside eppm, you can set which tables you want to audit. i’ve set the first table “chgtask” to audit insert, update, and delete. what this should essentially do is track which users have made changes to the activity table in p6 (or basically to any project activities). unfortunately, you’ll need to both understand p6’s db table structures and unravel how to use bi publisher reports to view the auditing reports.
7) improved integration configuration for gateway
there are few improvements to primavera gateway configuration. previously p6 had 3 hard-coded integrations – unifier, an erp system and primavera prime. in version 15.1, you can now setup as many integrations as you choose. and you can include multiple integrations of the same type. this is handy if you want to integrate with 2 unifier installs, for example – a staging install and the real production install. this flexibility will make life a lot easier for the enterprise with more than a few test / staging environments.
8) move project-level p6 data between databases with gateway
i like this feature, and apparently it was around in 8.4, but i didn’t realize it. like 7) this feature is meant for those enterprises who have test / staging databases. you can set up your p6 enterprise data (global data like 世界杯时间比赛时间 , obs, eps, activity codes), in a staging db. prior to go-live, you can use gateway to transfer that global staging data to your production database. nice!
in primavera p6 eppm 8.4, you could transfer these fields between databases:
- 世界杯时间比赛时间
- roles
- cost accounts
- calendars
- project codes
- baseline types
- currency
- financial periods
- notebook topics
- expense categories
- rate types
- location
added to this list in primavera p6 15.1 are:
- eps
- wbs
- project codes
- high-level resource planning
- activities
- resource assignments
- expenses
- risks
i don’t see “projects” itself, but i’m assuming it’s in there.
oracle is calling this feature configuration management and i can tell it’s well thought-out. i know i’ve implemented primavera p6 for a few large clients with many dbs where this feature would have really helped to keep data in sync between the staging and production databases.
9) additional enhancements in primavera p6 eppm
- cut / copy / paste multiple projects at once
- all fields on relationship tabs, including date fields
- these fields are invaluable for analyzing a schedule and it’s relationships.
- column selection dialogs for details windows.
- now, instead of just checking off columns to show on the dropdown list, you actually get the column chooser pop-up window for many of the details tabs. see the “customize colums” menu entry in the image above.
- grant access to visualizer only
- granting access to visualizer is no longer tied to granting access to primavera p6 professional. there is now a separate option for visualizer access to be assigned to a user. so users can now be granted access to visualizer only.
10) primavera team member 15.1 enhancements
primavera team member continues to be a vehicle for gathering updates from the field that are rolled into a schedule’s progress update. in case you don’t know, there are 2 versions:
- “primavera team member mobile” is a smart-phone app for android and iphone that sends updates to your p6 install.
- “primavera team member web” is a web-based app that users can login to provide updates.
the slide below summarizes the new features you see in both team member mobile and team member web.
i won’t go into detail here (you can watch the broadcast for more information), although it’s worth mentioning now that team member web now allows users to configure their units and durations to show in days or hours now in 15.1.
11) visualizer goes 64-bit – to handle those big big projects
primavera visualizer has been relaunched as a 64-bit tool in v15.1. that means it can take advantage of additional memory to display large data sets. previously, visualizer had trouble displaying large projects, but now it apparently hums.
12) import / export visualizer layouts
new as well is the ability to import and export or basically share visualizer layouts. very handy if you’re migrating between to a new pc or picking up views that a colleague created on another installation.
13) admin functionality is back in primavera p6 professional 15.1
it was here, then it was gone, then, depending on what version you had – it was gone again. and now it’s back! (for good?). now in primavera p6 professional 15.1 you have *some* of your invaluable administrative features back.
here’s what you can administer:
- eps
- obs
- project codes
- activity step templates
- cost accounts
- funding sources
now, just to be clear, these changes only affect users who are using p6 professional to connect to a primavera p6 eppm database. those who are using primavera p6 professional in a stand-alone environment never lost their admin features. only those who were using what was once termed the “optional client” – the version of primavera p6 professional that connects to an eppm database.
summary
as we’ve seen before, there are many new changes in primavera p6 15.1 for users of primavera p6 eppm, but not much for users of primavera p6 professional. however, i am impressed with the enhancements to eppm. i think we all know that the future is online and that a web-based tool with the core cpm scheduling engine of primavera p6 professional is a tool we might all be using soon. for a while, there have been huge gaps in functionality between p6 professional and eppm, but those gaps are closing fast. if perhaps we saw a significant performance improvement of eppm (perhaps fueled by a migration away from java), then i’d wager that eppm would be popping up on desktops worldwide quickly.
what do you think about primavera p6 v15.1 and oracle’s direction with software updates? we’d love to hear your thoughts. leave us a comment.
