For more slides and tutorials visit www.p6academy.com Source: Collaborate 14

1. 1

2. <Insert Picture Here>
P6 Analytics R3.2 SP1
Shawn LaffertyShawn Lafferty
Oracle Primavera Development
Shawn.Lafferty@oracle.com

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 anycontract. 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 anyThe development, release, and timing of any
features or functionality described for Oracle’s
products remains at the sole discretion of Oracle.
3

4. Agenda
• History
Daily for Activity and Resource Assignment– Daily for Activity and Resource Assignment
– Burn Down
– Useful Calculations (Ago, TimeStampDiff)
• Hierarchies
– Codes
– Accurate LevelsAccurate Levels
• Map
– Map Layers
– Configuration
4

5. P6Analytics History
5

6. History
• Daily and Dimensional
Set History Level to Activity– Set History Level to Activity
• History interval still applies to Primavera Project History
– Run ETL daily…
– Daily also means Dimensional (mappings.tcsv)
• Primavera Activity History
– “Spreads” captured daily, for each activitySpreads captured daily, for each activity
– Percent Completes, Units, Costs, Earned Value (Units and
Costs), Dates and Durations
Primavera Resource Assignment History• Primavera Resource Assignment History
– “Spreads” captured daily, for each Resource Assignment
– Units and Costs
6

7. Formulas for History
7

8. AGGREGATION (SUM, RSUM, COUNT, RCOUNT)
SUM(expr), RSUM(expr), COUNT(expr), RCOUNT(expr)
Aggregation BY
Use the BY Condition within the Aggregation function to aggregate
l b d ifi di i l l (ti d j tvalues based on specific dimensional values (time, codes, projects,
etc…)
BE CAREFUL if the dimensional value is not included in the
l i th lt b t f d b t th ti ianalysis, the results may be out of order…but the aggregation is
working.
For EXAMPLE:
RSUM("Units"."Planned Labor Units" BY "Calendar"."Calendar
Date")
8
Date )

9. CASE STATEMENT
CASE WHEN a=b THEN c ELSE d END
Used to determine when a field meets a criteria (CASE WHEN), do
something (THEN), OR (ELSE) if the criteria is not met, do something
else.e se
For EXAMPLE:
CASE WHEN "Units"."Planned Labor Units" > 0 THEN
"Units"."Planned Labor Units"/8 ELSE 0 END
9

10. AGO
AGO(expr, time_level, offset)
A time series aggregation function that calculates the aggregated
value from the current time back to a specified time period.p p
expr = Any FACT value
time_level = Time unit to use for looking back (Day, Week, Month,
etc)
offset = integer value for the specified number of time level that youoffset = integer value for the specified number of time_level that you
want to pull data forward from
EXAMPLE:
AGO("Dates"."Planned Start", "Calendar"."Date Hierarchy"."Day", 1)
10

11. TIMESTAMPDIFF
TIMESTAMPDIFF(interval, expr, timestamp2)
Returns the total number of specified intervals between two
timestamps.p
interval = the time difference level you want to count, MUST BE in the
following format: SQL_TSI_HOUR, SQL_TSI_DAY, etc…
expr = the first timestamp element that will be compared
timestamp2 = the second timestamp element that will be comparedtimestamp2 = the second timestamp element that will be compared
EXAMPLE:
TIMESTAMPDIFF(SQL_TSI_HOUR, "Dates"."Start", "Dates"."Finish")
11

12. TIMESTAMPDIFF (cont.)
TIMESTAMPDIFF(interval, expr, timestamp2)
Returns the total number of specified intervals between two
timestamps.p
• Negative numbers can result, depends on the order of expr and
timestamp2 values.
• If the value in expr field is later in time than value of timestamp2
• does NOT consider P6 calendars (will use 24x7)• does NOT consider P6 calendars (will use 24x7)
• Can be combined with other functions, like AGO
EXAMPLE:
TIMESTAMPDIFF(SQL_TSI_HOUR, "Dates"."Start",
AGO("Dates" "Start" "Calendar" "Date Hierarchy" "Day" 1))
12
AGO( Dates . Start , Calendar . Date Hierarchy . Day , 1))

13. P6Analytics Hierarchies
13

14. Hierarchies
• All Subject Areas
Previous hierarchies still exist with a few changes– Previous hierarchies still exist with a few changes
• Level names no longer repeat
– Full Code Path
– Configured Codes are automatically part of the Hierarchy
• Resource and Role Hierarchies AddedResource and Role Hierarchies Added
– in the appropriate Subject Areas
• Filtering, Sorting, and Aggregation
– Selection Steps
– Right Click Menu
14

15. P6Analytics Maps
15

16. Maps
• Project, Activity and Resource
– Assigned in P6, loaded into STAR schema
P6 has geo coder to resolve locations (configurable)– P6 has geo-coder to resolve locations (configurable)
– Country, State, City, Street Address, and Longitude/Latitude
• Oracle Mapviewer
– included with Oracle Business Intelligence
– P6 Analytics uses 2 data sources (MVDEMO & NAVTEQ)
– can include Oracle Maps Bing Maps Nokia Maps Googlecan include Oracle Maps, Bing Maps, Nokia Maps, Google
Maps, and TomTom Maps
• Oracle Business Intelligence
t f th b i t ti ith O l M i– out of the box integration with Oracle Mapviewer
– Administration, Manage Map Data
– associate map layers with RPD fields
16

17. Additional Resources
17

18. More Information
• OTN
http://www oracle com/technetwork/apps• http://www.oracle.com/technetwork/apps-
tech/primavera/documentation/index.html
• Blog
• https://blogs.oracle.com/P6Analytics/
• P6 Analytics Product page
htt // l / / d t / li ti / i• http://www.oracle.com/us/products/applications/pri
mavera/p6-analytics/resources/index.html
18

19. Demo
19