For more free articles and slides visit www.p6academy.com

1. 1

2. <Insert Picture Here>
P6 Analytics R3.1
Shawn Lafferty
Functional Designer

3. 3
The following is intended to outline our general
product direction. It is intended for information
purposes only, and may not be incorporated into any
contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decisions.
The development, release, and timing of any
features or functionality described for Oracle’s
products remains at the sole discretion of Oracle.

4. 4
Agenda
• New Features in P6 Analytics r3.1
• New Subject Areas and Fields
• Demo
– Dashboards, Analyses, and Catalog

5. 5
P6 Analytics 3.1 available on e-delivery

6. 6
New Features

7. 7
New Features in P6a r3.1
• History
– Daily (Activity and Resource Assignment)
– Dimensional (Slowly Changing Dimensions (SCD))
• (e.g. activity name change can be saved)
• Code Hierarchies
– Project, Activity, and Resource level
– Available in all subject areas
• Burn Down
– Ability to track project progress vs. point in time
– Industry specific (non-agile)

8. 8
New Features in P6a r3.1 (con’t)
• User Defined Fields
– Date and Text
– Project, WBS, Activity and Resource
– Cost/Numbers for Resource and Resource Assignment
• Work Planning
– Ability to track project planning vs. multiple points in time
– Industry specific (AP928, INPO)

9. 9
History
• Activity and Resource Assignment Level
– New Subject Areas for each
– P6 Project Preferences, Analytics, History Level = Activity
• Daily
– Opting in to Activity History = Daily History
• Dimensional
– Customizable with mappings.tcsv

10. 10
Code Hierarchies
• Project, Activity, and Resource codes
– Across Subject Areas
– Full Code Path
– Configured Codes are automatically part of the Hierarchy
– Hierarchy as well as full level support

11. 11
Burn Down
• Track project against single point in time
– sys_workdown_date project UDF in P6
– “baseline” of how project should go
• “Burn Down” values based on whole project
– Historical capture and future projections
• Daily
– Daily view to get project back on schedule (if needed)

12. 12
Work Planning
• Track project against multiple points in time
– sys_scope_freeze, sys_schedule_freeze project UDF in P6
– How project doing according to scope and schedule freeze
– Weekly and Daily capture
– Historical comparisons (scope & schedule freeze)
– Last week

13. 13
Subject Area Growth By Release
1.0 2.0 3.1
4 - Subject Areas
Activity
Project History
Resource Assignment
Resource Utilization
7 - Subject Areas
Activity
Activity UDF
Project History
Project UDF
Resource Assignment
Resource Utilization
WBS UDF
13 - Subject Areas
Activity
Activity History
Burn Down
Activity UDF
Project History
Project UDF
Resource Assignment
Resource Assignment
History
Resource UDF
Resource Assignment
UDF
Resource Utilization
WBS UDF
Work Planning
New Subject Areas

14. 14
Subject Area Categories
• 13 Subject Areas
3 Current
3 History
5 UDF
2 Industry

15. 15
Demo

16. 16
Additional Resources

17. 17
More Information
• OTN
• http://www.oracle.com/technetwork/apps-
tech/primavera/documentation/index.html
• Blog
• https://blogs.oracle.com/P6Analytics/
• P6 Analytics Product page
• http://www.oracle.com/us/products/applications/pri
mavera/p6-analytics/resources/index.html