{"id":34677,"date":"2016-04-26t16:49:26","date_gmt":"2016-04-26t20:49:26","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=34677"},"modified":"2019-10-18t10:54:54","modified_gmt":"2019-10-18t14:54:54","slug":"primavera-p6-16-1-released-complete-details","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/primavera-p6-16-1-released-complete-details\/","title":{"rendered":"primavera p6 16.1 is released! everything you need to know"},"content":{"rendered":"

this month marked oracle’s latest release of primavera p6 16.1, their flagship project management software. there are some new features to discuss and some changes. if you’re on an a single-digit version (version 6, 7 or 8) don’t forget about oracle’s new versioning approach<\/a>\u00a0– version 16.1 isn’t truly 8 releases ahead of v8. you can get the low-down on all versions from our version history page<\/a>.<\/p>\n

since primavera p6 is really 2 applications<\/a>, let me update you on both primavera p6 eppm (web tool) first, then the ever-popular primavera p6 professional (windows tool).<\/p>\n

what’s new in primavera p6 16.1 – p6 eppm first.<\/h2>\n

i know many p6 professional users who have tried to use eppm might be groaning right now, but in truth oracle primavera is\u00a0moving closer to web-based version of p6 we can love (or just use). here’s why:<\/p>\n

java replacement with html5<\/h3>\n

oracle had started in previous versions of primavera p6 eppm to distance itself from java, technology that rendered eppm unusable to many and annoyingly slow for most. with the replacement of java for fleet-footed html5, we’re starting to see improvements in performance that are significant.<\/p>\n

in version 16.1, oracle has replaced the following views with html5 versions:<\/p>\n