Powered by Proteus

User Documentation
Proteus - Reporting for Oracle Primavera P6
Version: 1.12.2

last updated: 15.08.2013

NOTE ON USING THIS DOCUMENT

This document has been prepared by Promineo AS and its partner(s) for the sole purpose of
providing supporting material for Registered Users of S-Curves for Primavera software. The
use of the software and accompanying written materials is governed by the End User
License Agreement for the use of S-Curves for Primavera software (EULA is available at:
www.scurvesforprimavera.com/user-agreement).

DISCLAIMER OF WARRANTIES
As set out in the EULA, The User uses the Software at its sole risk. The Software and
accompanying written materials are provided on an "AS IS" and "AS AVAILABLE" basis
without warranty of any kind, express or implied, and Promineo specifically disclaims the
warranties of fitness for a particular purpose and merchantability. No oral or written advice
given by Promineo, its dealers, distributors, agents or employees shall create a warranty or
in any way increase the scope of this warranty and you may not rely upon such information
or advice.

PATENTS, TRADEMARKS, COPYRIGHTS, INTELLECTUAL

PROPERTY
The user acknowledges that all patents, trademarks, copyrights and intellectual property
rights used or embodied in, or in connection with, the S-Curves for Primavera software and
accompanying materials shall remain the sole property of Promineo AS, or a Third Party
whose components may have been used in the development of the software and the
materials.

All Rights Reserved

version 1.12.2

Page 2 of 40

Table of Contents
About this document .............................................................................................................5
Terms used ........................................................................................................................6
Colour schema for S-Curves in S-Curves for Primavera...................................................7
Oracle Primavera P6 Standard Colors ..........................................................................8
A note on cost types in Oracle Primavera P6 ................................................................8
Roles .................................................................................................................................9
Currency ............................................................................................................................9
Oracle Primavera P6 System Requirements ......................................................................10
S-Curves for Primavera historic database ..........................................................................11
Selecting activity codes ...............................................................................................12
Storing project history ..................................................................................................13
Creating an initial baseline in S-Curves for Primavera.............................................13
On-going projects .....................................................................................................15
Cutoff periods setup samples ......................................................................................16
Weekly .....................................................................................................................16
Monthly (Calendar) ..................................................................................................17
Monthly (Cutoff last Sunday each month) ................................................................18
Creating periodical snapshots .....................................................................................19
Re-baselining ...............................................................................................................20
Available Report Fields .......................................................................................................21
Task level fields ...............................................................................................................21
Expense level fields ........................................................................................................22
Resource Assignment level fields ...................................................................................23
Report Samples ......................................................................................................................26
01 SCurve Total Cost ..........................................................................................................26
02 SCurve Total Cost w_current forecast ...........................................................................27
03 SCurve Total Cost Percent ............................................................................................28
04 SCurve Total Cost Percent w_current forecast ..............................................................29
05 Total Cost Earned forecast ............................................................................................31
06 SCurve Units .................................................................................................................32
07 SCurve Units w_current forecast ...................................................................................33
08 SCurve Units Percent ....................................................................................................34
09 SCurve Units Percent w_current forecast ......................................................................35
10 SCurve Live Cost Percent .............................................................................................36
T1 Period Progress Report Units ........................................................................................36
Filters and Grouping ...............................................................................................................37
All Rights Reserved

version 1.12.2

Page 3 of 40

Resource filtering ................................................................................................................37

WBS filtering / grouping ......................................................................................................38
Activity Code filtering ..........................................................................................................39
EPS Coding ........................................................................................................................39
Contact Details ...................................................................................................................40

All Rights Reserved

version 1.12.2

Page 4 of 40

About this document

Oracle Primavera P6 is a leading scheduling and resource management product, but its
ability to report trends is limited - the software usually plots a single point in time, overriding
previous periods by redistribution.
Oil and Gas industry, among others that use the Primavera P6 software, have a need to have
data for each project cutoff period stored as a frozen dataset to enable viewing progress
based on multiple baselines in cost, units and percent.
S-Curves for Primavera is a tool that is designed to enable the reports that Primavera P6
lacks and to add further reporting flexibility.
The document serves as documentation and showcase for sample report types provided with
the S-Curves for Primavera.
S-Curves for Primavera is based on a software named Proteus. This document is not
intended as a user manual for general Proteus use; please use Proteus User Guide for
general Proteus instructions.

All Rights Reserved

version 1.12.2

Page 5 of 40

Terms used
BCWS/Planned value: This is the Budgeted Cost of Work Scheduled (Budgeted
costs for labor and resources for the project. Based on baseline data)
BCWP/Earned Value: Budget Cost of Work Performed. BCWS * Percent
Complete. For example, take project with a BCWS of $10,000 that is 40% done.
Earned Value = $10,000 x 0.40 = $4,000.
ACWP/Actual: Actual Cost of Work Performed.
SPI/Schedule Performance Index = BCWP / BCWS. SPI greater than 1 is good
(ahead of schedule).
CPI/Cost Performance Index = BCWP/ACWP. CPI greater than 1 is good (under
budget).
Performance Ratio Percent: ACWP / BCWP * 100. Continuing the example, if the
ACWS had been $3,000, then the performance ratio is $3,000 / $4,000 x 100 = 75%.
(Under budget)
P50: Used as a term for average curves (Mean value of early / late curves)

All Rights Reserved

version 1.12.2

Page 6 of 40

Colour schema for S-Curves in S-Curves for Primavera

-

Planned Total Cost/Units Early

Colour: Black

Periodical/Accumulated baseline percent for period.

Planned Total Cost/Units Late

Colour: Dark Grey

Periodical/Accumulated baseline percent for period.

Earned Total Cost/Units

Colour: Orange

Periodical/Accumulated earned value towards baseline.

Actual Total Cost/Units

Colour: Blue

Periodical/accumulated Current plan Actual hours/costs for period / Current plan planned for
period )

Planned Total Cost/Units Forecast Early

Colour: Black

Periodical/Accumulated planned value towards baseline plan. (Planned for period / baseline
planned for period ). Entry point = Baseline Actual.

Planned Total Cost/Units Forecast Late

Colour: Dark Grey

Periodical/Accumulated planned value towards baseline plan. (Planned for period / baseline
planned for period ). Entry point = Baseline Actual.

Current Total Cost/Units Forecast Early

Colour: Light Blue

Periodical/Accumulated planned value towards current plan. (Planned for period / baseline
planned for period ) . Entry point = Current Actual

Current Total Cost/Units Forecast Late

Colour: Light Green

Periodical/Accumulated planned value towards current plan. (Planned for period / baseline
planned for period ) Entry point = Current Actual

All Rights Reserved

version 1.12.2

Page 7 of 40

Oracle Primavera P6 Standard Colors

A note on cost types in Oracle Primavera P6

In Primavera P6, we have four different types of cost involved in earned value calculations:
1. Labour cost ( resource level )
2. Nonlabour cost ( resource level )
3. Material cost ( resource level )
4. Project Expenses ( task level )
To see a total of all cost; one must report on Task level in S-Curves for Primavera.
Total Cost is Oracle Primavera Terminology for the sum of these four types of cost. The
Earned cost value is based on Total Cost on activity level.

All Rights Reserved

version 1.12.2

Page 8 of 40

Roles
If roles are used instead of regular resources; S-Curves for Primavera needs to be told this.
This is done by selecting Use Roles in the Project Open dialogue.

Currency
S-Curves for Primavera has built in support for currency handling; based on the same
currency dictionary as P6. The user must select the wanted currency when opening the
projects.
Select currency:

All Rights Reserved

version 1.12.2

Page 9 of 40

Oracle Primavera P6 System Requirements

-

Oracle Primavera P6 version 8.1, 8.2, 8.3

Publish Project service must be enabled

All projects must have an assigned Project Baseline

Version 1.x: SQL Server 2008

All Rights Reserved

version 1.12.2

Page 10 of 40

S-Curves for Primavera historic database

S-Curves for Primavera stores Primavera baseline and current data for each cutoff in
its own database/tables.
-

Data for each cutoff is stored in separate data tables, these tables are managed by SCurves for Primavera.

Both current data and baseline data is stored for each cutoff; giving us the data
needed to produce reports which illustrate changes in scope and keep true history.

Data must be stored by the users at each cutoff; from project start to finish. This is
done by choosing Save Period Snapshot in S-Curves for Primavera, described in
detail later in this document.

All Rights Reserved

version 1.12.2

Page 11 of 40

Selecting activity codes

We need to select which P6 activity codes than can be used in P6. Choose Action List,
Select ActivityCodes

Choose the codes needed for reporting

All Rights Reserved

version 1.12.2

Page 12 of 40

Storing project history

There are a few steps that are vital to creating and maintaining a complete project history;
among them are creating the initial snapshot, and to store a new baseline in S-Curves for
Primavera after rebaselining.

Creating an initial baseline in S-Curves for Primavera

1. Make sure the P6 project(s) have established a baseline; and that the project(s) have
been scheduled. There is no way to make early/late curves without doing the
schedule calculations. Make sure to hit F10 in P6 after assigning a new baseline or
changed baseline!
In the following example will have the P6 Datadate on 1. Oct 2011, and we have
weekly cutoffs with period finish on Sundays. Project start is 8. Oct.
2. Start S-Curves for Primavera; and choose project(s)
3. Choose Action List, Save Snapshot.

4. Make sure the snapshot date is on the same day as period finish date; usually 1 day
before P6 Datadate. Tick off Initial baseline snapshot

5. You will get a message that the snapshot has been created.
All Rights Reserved

version 1.12.2

Page 13 of 40

6. Start Choose File New Session to load the data set into memory
7. For further snapshots use same method; but without the Initial baseline snapshot

All Rights Reserved

version 1.12.2

Page 14 of 40

On-going projects
In the case where a project is already started and have been run for several cutoffs; all
progress until first normal snapshot is shown within the first normal snapshot.
The sample below:
1. The project started in July 2011, and have assigned a baseline with DD in July
2. The project has been run in P6 for a couple of cutoffs, and progress has been entered
3. After 3 months, S-Curves for Primavera is implemented for the project.

All Rights Reserved

version 1.12.2

Page 15 of 40

Cutoff periods setup samples

Weekly
Sample Project start is 4. February, Datadate in P6 is 4. February

Example 1: We want to use weekly periods; cutoff each Sunday.

P6 Datadate
3.Feb

S-Curves for Primavera snapshot date

2. Feb

Period 1

11. feb

10.Feb

Period 2

18. Feb

17. feb

Initial snapshot

Setup in S-Curves for Primavera histograms

All Rights Reserved

version 1.12.2

Page 16 of 40

Monthly (Calendar)
Sample Project start is 4. February, Datadate in P6 is 1. February

Example 2: We want to use weekly periods; cutoff each last day of Month.
P6 Datadate

S-Curves for Primavera snapshot date

Initial snapshot

1.Feb

31. Jan

Period 1

1.Mar

28. Feb

Period 2

1.Apr

31. Mar

Setup in S-Curves for Primavera histograms

All Rights Reserved

version 1.12.2

Page 17 of 40

Monthly (Cutoff last Sunday each month)

Sample Project start is 4. February, Datadate in P6 is 1. February

Example 3: We want to use weekly periods; cutoff each last Sunday of Month.
P6 Datadate

S-Curves for Primavera snapshot date

Initial snapshot

1.Feb

31. Jan

Period 1

25.Feb

24. Feb

Period 2

1.Apr

31. Mar

Setup in S-Curves for Primavera histograms

All Rights Reserved

version 1.12.2

Page 18 of 40

Creating periodical snapshots

1. After progressing the projects in P6, and the new datadate has been set, start SCurves for Primavera, select the corresponding project and choose Action List,
Save Snapshot.
2. Make sure that the S-Curves for Primavera Snapshot date is set to the day after P6
Datadate; following our current sample; this will be 14.August 2011. (P6 datadate is
set to 15. Aug 2011 for the first weekly period)
3. You will get a message that the snapshot has been created.
4. Start Choose File New Session to load the data set into memory and start reporting.

All Rights Reserved

version 1.12.2

Page 19 of 40

Re-baselining
1. When a scope change occurs in P6; and the baseline has been updated in P6; we
need to let S-Curves for Primavera know this. This is done by creating a special SCurves for Primavera snapshot; a New Baseline Snapshot. Follow this procedure to
make sure the re-baselining is calculated correctly in S-Curves for Primavera.
2. After doing the needed adjustments in P6; make sure the project has been scheduled
before creating the new baseline/updating the existing baseline. Also, make sure to
F10 in P6 if you change the baseline.
3. Start S-Curves for Primavera, load the project(s) and choose Action List, Save
Snapshot.

4. Start Choose File New Session to load the data set into memory and start reporting.

All Rights Reserved

version 1.12.2

Page 20 of 40

Available Report Fields

The fields below are available for reporting.

Task level fields

Task level = sum of Resource Assignment level + expense level data
-

Earned Total Cost

Period value and/or cumulated ( progress % * Baseline Budget)

Earned Total Cost %

Calculated towards baseline budget at cutoff

Planned Total Cost Early / Late

Baseline cost early / late

Planned Total Cost Early / Late %

Current Total Cost Early / Late

Calculated towards baseline budget scope/dates

% = Planned cost within period dates / Planned Total Cost at cutoff
For historic data (left of DD); use Planned Total Cost at cutoff. as scope

Current cost early / late

Current Total Cost Early / Late %

Current Earned Total Cost Forecast Early

Calculated towards current budget scope/dates

% = Current cost within period dates / Current Total Cost at cutoff
For historic data (left of DD); use Current Total Cost at cutoff. as scope

Earned + Remaining Earned( Estimated curves from Current Project datadate to project end
date )

All Rights Reserved

version 1.12.2

Page 21 of 40

Expense level fields

-

Planned Expense Cost Early / Late

Baseline Expense cost early / late

Actual Expense Cost

Actual cost early / late

Earned Expense Cost

Earned expense cost

Current Forecast Expense Cost Early

Actual Expense Cost + Estimate to complete/remaining ( Estimated curves from Current

Project datadate to project end date )

All Rights Reserved

version 1.12.2

Page 22 of 40

Resource Assignment level fields

Periodical / Cumulative cost fields.
-

Planned Total Cost Early / Late

Baseline cost early / late

Planned Total Cost Early / Late %

Live Planned Total Cost Early / Late %

Period value and/or cumulated

Actual Total Cost %

Calculated towards Current budget. ( Current scope )

Actual Total Cost

Period value and/or cumulated ( progress % * Current Budget)

Live Earned Total Cost %

Calculated towards baseline budget at cutoff

Live Earned Total Cost

Period value and/or cumulated ( progress % * Baseline Budget)

Earned Total Cost %

Calculated towards current scope

For historic data (left of DD); use Current Total Cost at cutoff

Earned Total Cost

Calculated towards baseline budget scope/dates

% = Planned cost within period dates / Planned Total Cost
For historic data (left of DD); use Planned Total Cost at cutoff. as scope

Calculated towards baseline budget

Live Actual Total Cost %

Calculated towards current budget

For historic data ( before DD) use the current budget at cutoff

Current Total Cost Forecast Early / Late

Current Total Cost Forecast Early / Late %

Actual + Estimate to complete/remaining / Estimate At Completion
Total scope is Baseline Budget
Live Current Total Cost Forecast Early / Late %
Actual + Estimate to complete/remaining / Estimate At Completion
Total scope is Current Budget

Planned Total Cost Forecast Early / Late

Actual + Estimate to complete/remaining / Estimate At Completion(baseline plan)

Total scope is Baseline project

Live Planned Total Cost Forecast Early / Late %

Actual + Estimate to complete/remaining ( Estimated curves from Baseline Project

datadate to baseline project end date )

Planned Total Cost Forecast Early / Late %

Actual + Estimate to complete/remaining ( Estimated curves from Current Project

datadate to project end date )

Actual + Estimate to complete/remaining / Estimate At Completion(current plan)

Total scope is Current project

Cost Performance Index (CPI)

Earned / Actual
Cost Schedule Performance Index (SPI)
Earned / Planned

Planned Total Cost Forecast P50

Mean value of Planned Total Cost Forecast Early / Late

Current Total Cost Forecast P50

All Rights Reserved

version 1.12.2

Page 23 of 40

Mean value of Current Total Cost Forecast Early / Late

Planned Total Cost Forecast P50 %
Mean value of Planned Total Cost Forecast Early / Late %
Total scope is Baseline project
Current Total Cost Forecast P50 %
Mean value of Current Total Cost Forecast Early / Late %
Total scope is Baseline project

Planned Earned Total Cost Forecast Early/Late %

Planned earned from Baseline DD
Total scope is Baseline project

Current Earned Total Cost Forecast Early/Late %

Planned earned from Curent DD
Total scope is Baseline project

Planned Earned Total Cost Forecast P 50%

Mean value of Planned Total Cost Forecast Early/Late % <Earned>
Total scope is Baseline project
Current Earned Total Cost Forecast P 50%
Mean value of Current Total Cost Forecast Early/Late % <Earned>
Total scope is Baseline project

All Rights Reserved

version 1.12.2

Page 24 of 40

Periodical / Cumulative Unit fields.

-

Earned Units

Earned Units %
Period value and/or cumulated. ( Earned Units / Baseline budget )
Actual Units

Before Project Baseline Datadate: Actual progress towards baseline at that time.

Before Project Baseline Datadate: Actual progress towards baseline at that time.
After Project Baseline Datadate: Planned Units Forecast Early / Late
Baseline Budget is total scope

After Project Baseline Datadate: Planned Units Forecast Early / Late

Planned Units Early / Late %

Planned Units Forecast Early / Late

Actual + Estimate to complete/remaining ( Estimated curves from Current Project

datadate to project end date )

Current Units Forecast Early / Late %

Mean value Planned Total Units Percent Early / Late

Baseline Budget is total scope

Current Units Forecast Early / Late

Mean value Planned Total Units Forecast Early / Late

Planned Units Forecast P50 %

Actual + Estimate to complete/remaining / Estimate At Completion

Baseline Budget is total scope

Planned Units Forecast P50

Actual + Estimate to complete/remaining ( Estimated curves from Baseline Project

datadate to baseline project end date )

Planned Units Forecast Early / Late %

Period value and/or cumulated

Baseline Budget is total scope

Planned Units Early / Late

Period value and/or cumulated

Actual Units %

Period value and/or cumulated ( Progress % * Baseline budget )

Actual + Estimate to complete/remaining / Estimate At Completion

Current Budget is total scope

Current Units Forecast P50

Mean value Planned Total Units Forecast Early / Late
Current Units Forecast P50 %
Mean value Current Total Units Percent Early / Late
Current Budget is total scope
Unit Performance Index (CPI)
Earned / Actual
Unit Schedule Performance Index (SPI)
Earned / Planned

All Rights Reserved

version 1.12.2

Page 25 of 40

Report Samples
01 SCurve Total Cost
Report calculates all progress based on S-Curves for Primavera Extended Storage actuals,
earned early/late. All figures computed towards the baseline active at each cutoff. Each
cutoffs resource assignments saved towards historical database.
Report variables
Resource Cumulated
-

Earned Total Cost

Actual Total Cost

Planned Total Cost Forecast Early

Planned Total Cost Forecast Late

Sample:

All Rights Reserved

version 1.12.2

Page 26 of 40

02 SCurve Total Cost w_current forecast

Report variables
Resource Cumulated
-

Earned Total Cost

Actual Total Cost

Planned Total Cost Forecast Early

Planned Total Cost Forecast Late

Current Total Cost Forecast Early

Current Total Cost Forecast Late

Sample:

All Rights Reserved

version 1.12.2

Page 27 of 40

03 SCurve Total Cost Percent

Report variables
Resource Cumulated
-

Earned Total Cost %

Actual Total Cost %

Planned Total Cost Forecast Early %

Planned Total Cost Forecast Late %

Sample:

All Rights Reserved

version 1.12.2

Page 28 of 40

04 SCurve Total Cost Percent w_current forecast

Report variables
Resource Cumulated
-

Earned Total Cost %

Actual Total Cost %

Planned Total Cost Forecast Late %

Planned Total Cost Forecast Late %

Current Total Cost Forecast Early %

Current Total Cost Forecast Late %

Sample(s):

All Rights Reserved

version 1.12.2

Page 29 of 40

Sample - P50 Actual prognosis

Sample - P50 Earned prognosis

All Rights Reserved

version 1.12.2

Page 30 of 40

05 Total Cost Earned forecast

Report variables
Task Cumulated
-

Earned Total Cost %

Actual Total Cost %

Planned Total Cost Early %

Planned Total Cost Late %

Sample no baseline revision:

All Rights Reserved

version 1.12.2

Page 31 of 40

06 SCurve Units
Report variables
Resource Cumulated
-

Earned Units

Actual Units

Planned Units Early

Planned Units Late

Sample:

All Rights Reserved

version 1.12.2

Page 32 of 40

07 SCurve Units w_current forecast

Report variables
Resource Cumulated
-

Earned Units

Actual Units

Planned Units Early

Planned Units Late

Current Units Forecast Early

Current Units Forecast Late

All Rights Reserved

version 1.12.2

Page 33 of 40

08 SCurve Units Percent

Report calculates all progress towards the baseline active at each cutoff.
Report variables
Resource Cumulated
-

Earned Total Units %

Actual Total Units %

Planned Total Units Early %

Planned Total Units Late %

Sample no baseline revision:

All Rights Reserved

version 1.12.2

Page 34 of 40

09 SCurve Units Percent w_current forecast

Report calculates all progress towards the baseline active at each cutoff. Each cutoffs
resource assignments saved towards historical database.
Report variables
Resource Cumulated
-

Earned Units %

Actual Units %

Planned Units Forecast Late %

Planned Units Forecast Late %

Current Units Forecast Late %

Current Units Forecast Late %

Sample no baseline revision:

All Rights Reserved

version 1.12.2

Page 35 of 40

10 SCurve Live Cost Percent

Report calculates all progress based on current scope. Could be used to report on progress
between rebaselining; where current project contains changes(could be new activities etc.)
which are going to be included in next baseline.
Report variables
Resource Cumulated
-

Live Earned Units %

Live Actual Units %

Live Planned Units Forecast Late %

Live Planned Units Forecast Late %

Live Current Units Forecast Late %

Live Current Units Forecast Late %

T1 Period Progress Report Units

All Rights Reserved

version 1.12.2

Page 36 of 40

Filters and Grouping

Resource filtering
It is possible to filter which resource is used as basis for reporting. For reports including
earned value; it is required with only one resource per activity. ( Earned value is stored at
activity level )

Illustration: User selects resource WF as the filter resource.

All Rights Reserved

version 1.12.2

Page 37 of 40

WBS filtering / grouping

It is possible to filter on selected WBS-levels.

It is possible to get a report to create a s-curve for each entry at a specific WBS level; by
using the Page field

In this sample we have selected WBS_Level 3; and get this report ( 2 pages for this simple
data )

All Rights Reserved

version 1.12.2

Page 38 of 40

Activity Code filtering

It is possible to filter and summarize/group on activity codes

EPS Coding

Illustration: User can select one or more projects for reporting. One can also select an entire
EPS level.

All Rights Reserved

version 1.12.2

Page 39 of 40

Contact Details
Product Web Site:
www.scurvesforprimavera.com
Head Office - Address:
Promineo AS
Eiganesveien 8
NO-4008 Stavanger
Norway
Phone: +47 9804 1000
Fax:

+47 53 22 50 51

Corporate Web Site: www.promineo.no

Product Sales:
Europe - email: europe@promineo.com
North America - email: usa@promineo.com
Middle East - email: middleeast@promineo.com
Asia - email: asia@promineo.com
Other Region - email: otherregion@promineo.com

Product Support:
Global - email: support@promineo.com

All Rights Reserved

version 1.12.2

Page 40 of 40