Professional Documents
Culture Documents
INTRODUCTION
AACE International recommends that cost engineers and schedulers alike
develop S-curves to graphically display cumulative progress information over
time. These curves can be used to gain insight into almost any type of project. The curves are designed as an intuitive method of
conveying project progress status to the project team and stakeholders.
S-curves are a plot of cumulative costs, hours, quantities or other progress measurements (vertical axis) against time (horizontal
axis). They are designed to visually compare planned progress against current and forecasted progress. To be most meaningful,
the earned value must be plotted with the planned and actual values. The primary point of Recommended Practice 55R-09, is that
graphic presentation promotes understanding of progress.
RECOMMENDED PRACTICE
In the AACE Recommended Practice (RP), there are three primary types of S-curves: baseline, actual and earned value. These
plots typically have a time-period that reflects the reporting period for the project (often monthly), but a more detailed weekly or
even daily timescale may be useful for specific projects. Two other types of curves are described by this RP including quantity
produced and cash flow curves. In this paper, you will learn how PRISM G2 meets the requirement for all of these curves and
more.
Developing Curves
Developing an S-curve first requires the preparation of a project schedule. The schedule is used to determine when resources will
be expended to accomplish the work of the project. The values (costs, hours, quantities or other measures) are associated with
the scheduled activities. From that, the S-curve is determined. Note that is important for the schedule to be of sufficient quality.
To ensure that, it should include:
• Resource leveling
PRISM G2 enables the project team to conform to all the recommendations in the AACE International Recommended Practice
55R-09. This tool is designed to develop an original baseline, generate an early and late approved budget and to compare them to
the actual values and the earned values as suggested by the RP. The PRISM G2 graphic representation of this information is very
useful to aid managers in quickly grasping the progress and status of a project. Let’s take a deeper look at how PRISM G2 helps
organizations to conform to the RP.
Figure 1
• The baseline budget, the approved budget, the earned value and the current actual/ETC curve are the four most
commonly used. These four curves in PRISM G2 represent the three curves called baseline, actual and earned
value in the RP.
• These four curves can readily be displayed using costs, hours or quantities provided the user can gather this
detail and finds it useful. In the PRISM G2 reports, these curves show cumulative values as recommended in
the RP.
• There are two alternate budget curves available in PRISM G2, called control budget and financial budget. The
user will need to determine if they are useful for their organization and what they will specifically represent.
Financial cash flow curves, funding curves, and commitment curves are also available.
• There are eight additional user-defined numeric fields that can be used to define and generate additional time-
phased data to produce other curves.
So, PRISM G2 provides all the time-phased data requirements of the recommended practice. Now, let’s take a closer look at the
different types of curves and how they are typically used in PRISM G2.
Baseline Budget
The baseline budget field in PRISM G2 is designed to reflect the original planned execution of the project. It is often established at
the time of an original investment decision or at least early in the lifecycle of the project. It is formed from the original estimate,
and the original schedule is used to time-phase the data and produce the baseline curves.
Approved Budget
The approved budget curve in PRISM G2 usually reflects the original planned execution, plus approved scope changes to the
project. The budget scope changes are applied in the period in which they occur using date information provided by the schedule.
This may be in advance of a detailed design phase or in advance of the construction phase. Either or both can be maintained
because PRISM G2 uses detailed change management records to justify and explain the differences between the baseline and
the approved budget curves.
Also, PRISM G2 conforms to the RP requirements regarding the generation of an early approved budget curve (see approved
budget in Figure 1) and a late approved budget curve. The difference between these two curves is the float determined in the
schedule which is created using critical path methodology. Thus, the approved budget S-curve can be displayed with both early
and late limits and delineate a “banana” shaped area on the graph. If the project is performing within this graphical area then the
project is being delivered close to plan.
In Figure 1, there is an alternate data column called incurred/ETC. This is often used to reflect only the “booked” costs recorded
in the accounting system – whereas the actual costs represent the actual cost of work performed (ACWP), which includes
accruals. Actual and ACWP are ANSI standard names. PRISM G2 does not dictate whether you use actuals/ETC or incurred/ETC
to represent the actual cost of work performed. You may find US companies using actual/ETC (following the ANSI standard name)
and other companies using incurred/ETC to represent ACWP.
Earned Value
The earned value time-phased data reflects the budgeted value
of the work performed. Like the actual cost data, a portion of
the curve represents the current earned value (calculated each
period from the project start to the current reporting period
end) and the balance of the curve represents a forecast of
future earned value. This is shown in Figure 2 with the previous
period’s background colored displaying historical data.
Commitments
The timing of when commitments are released or planned to be released
can also be managed in PRISM G2 for comparison to other S-curves. The
commitment date is recorded automatically when a commitment is entered in
Figure 3 PRISM G2. Future commitments and dates are manually entered by the user.
The quantity produced or quantity installed curves are two of the possible quantity based curves.
Figure 5
Figure 6
Figure 7
Figure 8
Advantages
One of the advantages of using this method with separate estimating and scheduling tools, is that it is not necessary to force the
estimating process onto the planning process. To elaborate, this means it is not necessary to manage every schedule activity with
the application of resources. It is not necessary to adjust every estimate item with schedule information. This does not, however,
relieve the planner of using appropriate resource leveling in the schedule; nor does it relieve the estimator of using appropriate
schedule information.
In PRISM G2, the schedule and the estimate are combined by applying an appropriate breakdown structure code to both. The
breakdown structure code is used to create control accounts. The control account is the level at which PRISM G2 uses the
schedule to create time-phased data (TPD). The TPD are the costs, hours or quantities distributed into the reporting periods for
the project. This process simulates the reality of most projects, where it is usual to generate the estimate and the schedule using
different tools. Thus, in many cases, the use of PRISM G2 has advantages over using only a scheduling tool. Another advantage
is that the details of the estimate (each estimate line item) and the schedule (each activity) can be made visible within the PRISM
control account.
• The approved schedule and approved budget will generate two sets of time-phased data – early approved
budget (called approved budget in the TPD table) and late approved budget.
• The baseline budget, actual/ETC and earned curves are all single sets of data. However, the user can determine
how much float is used in the spreading of this data. For example, if experience suggests that typically half of
the float is used on the project then the user chooses a 50% application of float in the TPD calculation for the
baseline, actual/ETC and earned value forecast.
No Schedule Tool
PRISM G2 allows users to either import the schedule activities or to manually enter schedule dates. The ability to manually enter
dates makes it possible to generate a schedule in PRISM G2. However, note that PRISM G2 is not a planning tool. It does not
enable you to use logic relationships between activities and resources to calculate dates as a scheduling tool does. It is common
in the early stages of a project to have some manual schedule input, but in later stages, when more details will be available, it is
better to develop a CPM schedule.
Change Management
The baseline budget in PRISM G2 is usually generated from a baseline estimate. The approved budgets in PRISM G2 are created
from the original budget plus any approved budget changes. Approved budget changes are usually limited to project scope
changes or budget shifts. PRISM G2 provides a detailed change management system that can record scope change. A sample
change entry is shown in Figure 9.
Figure 9
PRISM G2 records both a baseline schedule and an approved schedule to match with the baseline budget estimate and the
approved budget for S-curve generation. See Figure 10.
Group Codes
PRISM G2 uses what are termed “group codes” to manage sorting and filtering of data and reports. Reports and on-screen forms
can be filtered, subtotaled or detailed at all levels of the group codes. The work breakdown structure (WBS) is one of the most
useful types of group codes. Other group codes may be related to the organizational breakdown (OBS), cost breakdown (CBS),
categories of materials and services provided, location, phases or stage, and other codes. Codes can be defined at the enterprise
level (applicable to all projects) or at the project level (unique to each project).
For example, the phase or stage may be used to designate engineering design, fabrication, construction, or other portions of the
project. With the appropriate breakdown of the control accounts and application of group codes, PRISM G2 will isolate fabrication
or installation to display produced quantities or installed quantities curves as discussed in the RP.
These curves are used by PRISM G2 when the user triggers the time-phased data calculation for the control account. The user
has control over whether the baseline, approved or current actual/ETC TPD is being calculated.
Calculation Curves
The time-phased data calculation curve in PRISM G2 represents the profile of the work for an account. The PRISM G2 TPD
calculation uses the curve to weight each calendar day within the start and finish date of the account. Each control account records
four curves – one each for the baseline budget, approved budget, control budget, and the current EAC. Often these four curves
are all the same at the beginning of a project.
Many curves are available for selection and custom curves can be created by the user. Examples are described as follows:
Cost engineers will obtain information from the project team to enable recording the actual cost, hours or quantities of the work
performed to date. The cost engineer will enter an accrual into PRISM G2 (it is labeled “ACC”) or calculate the accruals using a
pre-made utility, to represent the work accomplished but not recorded in the ERP. PRISM G2 will automatically reverse the accrual
in the subsequent period, during the period closing process.
Note that the PRISM’s TPD form has an incurred/ETC column. If desired, the user may also import booked accounting records into
this column to show the accounting information without any accruals. This may aid with the reconciling process. The roles of the
actual/ETC column and the incurred/ETC column can be reversed if desired by the users.
• Schedule activities progress: If the schedule is progressed each period, then this progress can be used to
calculate progress in the PRISM G2 control accounts.
• Control account tasks: For example, an account related to concrete may have tasks such as square meters
of forming, tons of rebar placed, cubic meters of concrete placed, and strip & finish. Each task has a relative
weighting applied (often relative costs), an EAC quantity. At each period end, the current quantity completed is
recorded to calculate the account progress.
• Engineering deliverables: The progress of engineering deliverables is recorded in the PRISM G2 Engineering
module and transferred to the control accounts.
• Field Progress Tasks: The PRISM Field Progress module is used to record detailed tasks and progress, which
is transferred to the control accounts.
• Calculated from actual and EAC entries of quantities, hours or costs: To use quantities or hours requires the
accounting entries and the accruals to include hours and/or quantities.
• The planned progress: This is useful when resource usage is not a factor, for example fixed costs like monthly
insurance, overhead, and others.
• Level of effort methods etc.
Figure 13
Flexibility
The standard S-curve report is flexible in the following ways. You can select:
- Actual/ETC
- Earned Value
- Cash Flow
- Funding
- Commitments
• Grouping sets the level of detail on the report based on group code. Use grouping to get multiple separate
graphs. For example, if you group by phase/stage you may get separate preliminary, engineering, procurement,
construction and commissioning graphics.
• Filters allow you to isolate data. The filter can be complex or simple. Filter the data based on group codes,
elements, descriptions or other categories.
Repeatability
You can easily reproduce the reports in PRISM.
• Specification ID - PRISM G2 encourages the user to save the selections noted above in a report specification
ID. If the user enters a specification ID and describes the specification purpose, the selections are saved for the
next time the report is desired. The same report is easily regenerated later.
• Batch ID– Assign the reports to “batch identifiers” to enable the user to run multiple reports at the same time.
Figure 14
• At the end of April, engineering has actual costs (red line) that are less than the earned value (green line). This
suggests that engineering is currently performing well. However, in this report, the total estimate at completion
(EAC) has increased from the budget. The cost engineer should:
1. Discover the root cause of this performance issue.
• Note that the earned value lags the (early) approved budget by about one week at present.
• Also note that the late approved budget is very different from the approved budget. This suggests that the
schedule has a lot float. Determine if this is likely. Determine if a more detailed schedule changes this float.
• The current schedule completion is delayed compared to the budget plan.
Figure 16
Figure 17
Figure 18
Figure 19
Figure 20
Performance Report
Next, let’s look at a project performance report instead of time-phased data. Figure 21 shows the data organized by control
package. It displays schedule variance (SV), cost variance (CV) and variance at completion.
Figure 21
• Control Accounts
• Commitments and Actuals
• Change Management
• Progress and Performance
- Progress Update
- Physical Progress
- Progress
- Productivity
- Performance
- Performance Index
- Performance Data
• Time-Phased Data
- Time-Phased Data
- Time-Phased Budget
- Time-Phased Performance
- Time-Phased Funding
- Time-Phased Plan
Figure 22
• In Figure 23, the contingency account does not have actual costs nor progress. This is usual! In this example,
as the project progresses the approved budget for contingency is unchanged. The unearned value remains the
same as the original budget but is forecast to be earned in less and less time.
• The forecasted actual costs have been managed by reducing the forecast in the example. However, with only
five months left in the project below, will those contingency costs rise to a peak in October, supposedly at the
end of the project?
• Think about your approach to managing contingency. Watch it closely. Maybe you should remove contingency
from your S-curve reports.
• Note that PRISM G2 also provides a contingency drawdown report.
Figure 23
Figure 24
Figure 25
This crossing of the curves is not usually visible in the overall project, so PRISM G2 supplies the user with utilities and reports to
find problems like this. Note the late finish date in January before the late start date in August in Figure 26.
Figure 26
Figure 27
www.aresprism.com