Professional Documents
Culture Documents
Acumen Fuse User Guide
Acumen Fuse User Guide
Acumen Fuse User Guide
Guide
V3.0
Acumen
Fuse
Software
www.projectacumen.com
October
2011
1 INTRODUCING ACUMEN FUSE ...................................................................................... 9 1.1 Overview ................................................................................................................................... 9 1.1.1 Project Analysis and Visualization ........................................................................................... 9 1.1.2 Acumen Fuse Ribbons .................................................................................................................... 9 Figure 1-1 Sample Project Shown as a Gantt Chart in MS Project ....................................... 10 Figure 1-2 Sample Project Shown as a Project Ribbon in Acumen Fuse .......................... 10 Figure 1-3 Sample Project Showing Critical Path Ribbons in Acumen Fuse ................... 10 Figure 1-4 Sample Project Showing Path Ribbons in Acumen Fuse ................................... 11 1.1.3 Acumen Fuse Metrics .................................................................................................................. 11 1.1.4 Acumen Fuse Analysis ................................................................................................................ 12 Figure 1-5 Ribbon, Phase & Intersection Analyzers .................................................................. 12 Figure 1-6 Metric Tripwire Thresholds .......................................................................................... 12 Figure 1-7 Activity Browser ................................................................................................................. 13 1.2 Navigation .............................................................................................................................. 14 Figure 1-8 Navigation through the Ribbon Menu Bar .............................................................. 14 Figure 1-9 File Management Menu ................................................................................................... 14 1.2.1 The Projects View ......................................................................................................................... 14 Figure 1-10 The Projects View ............................................................................................... 15 1.2.2 The Dashboard View ................................................................................................................... 16 Figure 1-11 The Dashboard View .......................................................................................... 16 1.2.3 The Analysis View ......................................................................................................................... 16 Figure 1-12 The Analysis View ............................................................................................... 17 1.2.4 The Logic View ............................................................................................................................... 18 Figure 1-13 The Logic Analysis View .................................................................................... 19 1.2.5 The Forensics View ...................................................................................................................... 19 Figure 1-14 The Forensics View ............................................................................................. 20 1.2.6 The Metrics View ........................................................................................................................... 20 Figure 1-15 The Metrics View ................................................................................................. 21 1.2.7 The Fields View .............................................................................................................................. 22 Figure 1-16 The Fields View .................................................................................................... 22 1.3 Integrating With Project Management Platforms .................................................... 23 Figure 1-17 - Supported Platforms .......................................................................................... 23 2 WORKING WITH ACUMEN FUSE WORKBOOKS ..................................................... 24 2.1 Introducing Acumen Fuse Workbooks ........................................................................ 24 2.1.1 Standard File Format ................................................................................................................... 24 2.1.2 XML File Format ............................................................................................................................ 24 2.2 Creating a New Workbook ............................................................................................... 24 Figure 2-1 Creating a New Acumen Fuse Workbook ....................................................... 24 2.2.1 Metrics within a Workbook ...................................................................................................... 25 2.3 Linking and Importing Projects ..................................................................................... 25 2.3.1 MS Project 2003/2007/2010 .................................................................................................. 25 2.3.2 Oracle Primavera P6 (V5/6/7/R8) ....................................................................................... 25 2.3.3 Linking to a single Project within an XER File .................................................................. 26 Figure 2-2 Importing a single Primavera P6 Project from an XER File ....................... 26 2.3.4 Linking to All Projects Within an XER File ......................................................................... 26 2.3.5 Primavera P3 .................................................................................................................................. 26 2.3.6 Oracle Primavera Risk Analysis (formerly known as Pertmaster) ......................... 26 2.3.7 Deltek Open Plan ....................................................................................................................... 26
2 | P a g e
3 CUSTOM FIELD MAPPINGS .......................................................................................... 38 3.1 Introducing Field Mapping ............................................................................................... 38 Figure 3-1 The Fields View ......................................................................................................... 38 3.2 Editing Field Mappings ...................................................................................................... 39 Figure 3-2 Creating Custom Field Mappings ...................................................................... 40 3.3 Editing Field Names ............................................................................................................ 40 3.4 Deleting Fields ...................................................................................................................... 40 3.5 Deleting Field Mappings ................................................................................................... 40 Figure 3-3 Deleting Custom Field Mappings ...................................................................... 40 3.6 Minimum Fields Required ................................................................................................ 40 3.7 Working with Field Types ................................................................................................ 41 3.8 Mapping a Field to Multiple Data Sources .................................................................. 41 Figure 3-4 Map to All Projects ................................................................................................ 41 3.9 Map all Code Fields for this Project ............................................................................... 41 3.10 Map all Code Fields for all Projects ............................................................................. 41 3.11 Map all User fields for All Projects .............................................................................. 41
2.3.8 Asta PowerProject ........................................................................................................................ 27 2.3.9 UN/CEFACT XML Schedule Files ............................................................................................ 27 2.3.10 Deltek Cobra CAP Earned Value Data ............................................................................ 27 2.3.11 MS Excel .......................................................................................................................................... 28 Figure 2-3 Linking to a Worksheet within an Excel File ................................................... 28 2.3.12 ARES PRISM G2 ........................................................................................................................... 28 2.4 Link Types ............................................................................................................................. 28 2.4.1 Project Links ................................................................................................................................... 29 2.4.2 Snapshot Links ............................................................................................................................... 29 Figure 2-4 Workbook, Project & Snapshot Hierarchy ....................................................... 29 2.4.3 Adding a Snapshot to a Project ............................................................................................... 29 2.4.4 Converting a Snapshot to a Project ....................................................................................... 30 Figure 2-5 Converting a Snapshot to a Project ..................................................................... 30 2.4.5 Adding a Baseline to Primavera P6 Workbooks .............................................................. 30 Figure 2-6 Adding a Baseline to a Primavera Project ........................................................ 31 Figure 2-7 Assigned Baseline against a Primavera P6 Project ....................................... 31 2.4.6 Merging Multiple Data Sources into a Single Dataset (e.g. cost and schedule) .. 31 Figure 2.8 Assigning a Mapped File ...................................................................................... 32 Figure 2.9 Mapping Merge File Fields .................................................................................. 33 Figure 2.9b Analysis View showing Merged Data ............................................................ 33 2.5 Importing Project Data ...................................................................................................... 33 Figure 2-10 Importing Project(s) Data ................................................................................... 34 2.5.1 Filtering Project Data During an Import ............................................................................. 34 Figure 2-11 Importing Project Data ........................................................................................ 35 2.6 Alternate Scenario Analysis by Including/Excluding Projects ............................ 35 Figure 2-12 Including/Excluding Projects from a Fuse analysis ................................... 35 2.7 Setting Display Units .......................................................................................................... 35 Figure 2-13 Display Time Units ................................................................................................. 35 2.8 Displaying projects, Snapshots & Scenarios in Timeline Mode ........................... 36 2.8.1 Adding Activities to the Timeline View ............................................................................... 36 Figure 2-14 Adding Activities to the Timeline View ........................................................... 36 2.8.2 Displaying the Timeline View .................................................................................................. 37 Figure 2-15 the Timeline View .................................................................................................. 37
3 | P a g e
4
MANAGING
METRICS
.....................................................................................................
43
4.1
Introducing
Acumen
Fuse
Metrics
.................................................................................
43
4.1.1
Primary
Formula
...........................................................................................................................
43
4.1.2
Secondary
Formula
......................................................................................................................
43
4.1.3
Tripwire
Formula
.........................................................................................................................
43
4.1.4
Tripwire
Threshold
......................................................................................................................
43
Figure
4-1
The
Metric
Editor
......................................................................................................
44
4.2
Metric
Definition
.................................................................................................................
44
Figure
4-2
Hierarchical
Development
of
Metrics
................................................................
45
4.3
Writing
Metric
Formulas
..................................................................................................
45
4.3.1
Array
Formula
Types
..................................................................................................................
45
Figure
4-2
Calculation
of
Array
Formulas
.............................................................................
46
4.3.2
Developing
Primary
Formulas
................................................................................................
46
Figure
4-3
Basic
and
Advanced
Primary
Formula
Definition
.........................................
47
4.3.3
Developing
Secondary
Formulas
...........................................................................................
47
Figure
4-4
Simple
Percentage
of
Primary
Formula
and
Advanced
Secondary
Formula
Definition
........................................................................................................................
48
4.4
Tripwires
...............................................................................................................................
48
4.4.1
Tripwire
Formulas
.......................................................................................................................
48
Figure
4-5
Auto
Calculated
and
Advanced
Tripwire
Formula
Definition
...................
49
4.4.2
Tripwire
Thresholds
....................................................................................................................
49
4.4.3
Defining
Tripwire
Threshold
Scales
.....................................................................................
49
Figure
4-6
Tripwire
Threshold
Scales
....................................................................................
49
4.4.4
Normal
and
Gradient
Scales
.....................................................................................................
50
4.4.5
Including/Excluding
Metrics
from
Analysis
......................................................................
50
Figure
4-7
Inclusion/Exclusion
of
Metrics
to
Analyzers
...................................................
50
4.5
Testing
Metric
Formulas
...................................................................................................
50
4.6
Commonly
Used
Functions
...............................................................................................
51
Figure
4-8
Commonly
Used
Function
Types
.........................................................................
51
4.6.1
IF(logical_test,
value_if_true,
[value_if_false])
..................................................................
51
4.6.2
SUM(number1,
[number2],
[number3],
[number4],
...)
...............................................
51
4.6.3
AND(logical1,
[logical2],
...)
......................................................................................................
52
4.6.4
MAX(number1,number2,...)
......................................................................................................
52
4.6.5
AVERAGE(number1,
[number2],...)
......................................................................................
52
4.6.6
COUNTIF(range,
criteria)
..........................................................................................................
52
4.7
Types
of
Acumen
Fuse
Field
............................................................................................
52
4.7.1
Activity
Fields
.................................................................................................................................
52
4.7.2
Project
Fields
..................................................................................................................................
53
4.7.3
Workbook
Fields
...........................................................................................................................
53
4.7.4
Dynamic
Fields
...............................................................................................................................
53
4.8
Templated
Metric
Libraries
.............................................................................................
53
4.8.1
Saving
a
Metric
Library
as
a
Template
................................................................................
54
Figure
4.9
Saving
a
Metric
Library
as
a
Template
............................................................
54
4.8.2
Re-using
a
Metric
Library
Template
.....................................................................................
54
4.8.3
Setting
a
Custom
Metric
Library
as
the
Default
Library
..............................................
54
Figure
4.10
Setting
Default
Metric
Library
.........................................................................
55
3.12 Load Default Mapping ..................................................................................................... 42 3.13 Field Mapping Context .................................................................................................... 42 3.14 Mapped Fields and Metrics ............................................................................................ 42
4 | P a g e
5 THE ACUMEN FUSE ENGINE ......................................................................................... 58 5.1 Ribbon Analysis ................................................................................................................... 58 Figure 5-1 Ribbon Analysis ...................................................................................................................... 58 5.2 Phase Analysis ...................................................................................................................... 58 Figure 5-2 Simple MS Project Schedule Spanning Four Phases ............................................... 58 Figure 5-3 Phase Analysis ......................................................................................................................... 59 5.3 Intersection Analysis ......................................................................................................... 59 Figure 5-4 Two Activities within MS Project .................................................................................... 59 Figure 5-5 Two Activities within Acumen Fuse .............................................................................. 59 Table 5-6 Three-Dimensional Fuse Analysis Modes ........................................................ 60 6 THE ANALYSIS VIEW ...................................................................................................... 61 6.1 Analysis View Navigation ................................................................................................. 61 Figure 6-1 The Analysis View .................................................................................................. 61 6.1.1 Ribbon Browser ............................................................................................................................. 62 6.1.2 Phase Analyzer ............................................................................................................................... 62 6.1.3 Ribbon Analyzer ............................................................................................................................ 62 6.1.4 Intersection Analyzer .................................................................................................................. 62 6.1.5 Activity Browser ............................................................................................................................ 62 6.2 Running Your First Acumen Fuse Analysis ................................................................. 62 6.2.1 Populate your workbook with project data ...................................................................... 63 6.2.2 Run Acumen Fuse Analysis ....................................................................................................... 63 Figure 6-2 Sample Analysis Results ...................................................................................... 63 6.3 The Ribbon Menu ................................................................................................................ 63 Figure 6-3 The Ribbon Menu ................................................................................................... 64 6.4 Creating Ribbons ................................................................................................................. 64 6.4.1 Project/Snapshot Ribbons ........................................................................................................ 64 Figure 6-4 Project-Based Ribbons ......................................................................................... 64 6.4.2 Field-Based Ribbons .................................................................................................................... 64 Figure 6-5 Creating Field-Based Ribbons ........................................................................... 65 Field Ribbons using Interval Size .......................................................................................................... 65 Field Ribbons using # of Intervals ........................................................................................................ 65 Field Ribbons using Delimiters .............................................................................................................. 65 Figure 6-6 Field-Based Ribbons ............................................................................................. 65 6.4.3 Resource Ribbons ......................................................................................................................... 66 Figure 6-6b Resource-based Ribbons .................................................................................. 66 6.4.4 WBS Based Ribbons ..................................................................................................................... 67 Figure 6-6c WBS-based Ribbons ............................................................................................ 67 6.4.5 Sorting Ribbons ............................................................................................................................. 67 6.4.6 Filtering and Drilling Down through Ribbons .................................................................. 67 Figure 7 Filtered Analysis using Hierarchical Ribbons .................................................. 68 6.5 Defining Date Ranges & Phases ...................................................................................... 68 Figure 6-8 Ribbon Phase Options .......................................................................................... 68 Splitting Q3 and Q4 Phases ...................................................................................................................... 69 Merged Q3 and Q4 2009 Phases ............................................................................................................ 69 Figure 6-9 Merging Ribbon Phases ....................................................................................... 69
4.9 Managing Metrics and Metric Libraries ....................................................................... 56 Figure 4.11 Managing the Metric Library ........................................................................... 56 4.10 Metric Weightings for Scorecards ............................................................................... 56 Figure 4.12 Metric Weightings for Scorecard Analysis .................................................. 57
5 | P a g e
6.6 Applying Metrics .................................................................................................................. 69 Figure 6-10 Ribbon Tabs .......................................................................................................... 69 6.6.1 Adding a Metric to a Analysis View ....................................................................................... 69 Adding Days Remaining metric to the analysis view ................................................................ 71 Days Remaining Metric Added to all Three Analyzers ................................................................. 71 Figure 6-11 Adding Metrics ..................................................................................................... 71 6.6.2 Removing Metrics from a Analysis View ............................................................................ 71 6.6.3 Adding an Entire Metric Library to an Analyzer ............................................................. 71 Figure 6-12 Adding Metrics ..................................................................................................... 72 6.6.4 Adding New Tabs to the Analysis View ............................................................................... 72 6.7 Running an Acumen Fuse Analysis ................................................................................ 72 6.8 Viewing & Interpreting Results through Analyzer Windows ............................... 72 6.8.1 Ribbon Analyzer ............................................................................................................................ 72 Ribbon Analyzer Tabular View ............................................................................................................... 72 Ribbon Analyzer Chart View ................................................................................................................ 72 Figure 6-13 Ribbon Analyzer .................................................................................................. 72 6.8.2 Phase Analyzer ............................................................................................................................... 73 Phase Analyzer Tabular View ................................................................................................................. 73 Phase Analyzer Chart View ................................................................................................................... 73 Figure 6-14 Phase Analyzer ..................................................................................................... 73 6.8.3 Intersection Analyzer .................................................................................................................. 73 Intersection Analyzer Tabular View .................................................................................................... 73 Intersection Analyzer Chart View ...................................................................................................... 73 Figure 6-15 Intersection Analyzer ........................................................................................ 73 6.8.4 Analyzer Chart Options .............................................................................................................. 73 6.9 Using the Activity Browser ............................................................................................... 74 Figure 6-16 Activity Browser Results .................................................................................. 75 Activity Browser Tabular mode ......................................................................................................... 76 Activity Browser Gantt mode .............................................................................................................. 76 Activity Browser Heat Map ................................................................................................................... 76 Activity Browser Detailed mode ........................................................................................................ 76 Activity Browser Scorecard .................................................................................................................. 76 Figure 6-17 Activity Browser Modes .................................................................................... 76 6.9.1 Scorecard View within the Activity Browser .................................................................... 76 Figure 6-17b Activity Browser showing Scorecard Results ......................................... 77 6.9.2 Heat Map View ............................................................................................................................... 77 Figure 6-17c Heat Map Options .............................................................................................. 78 Figure 6-17d Heat Map Example ............................................................................................ 78 6.10 Smart-Filtering of Ribbons ............................................................................................ 78 Figure 6-18 Smart-Filtering of Activities based on Analysis Results ........................ 79 6.11 Zooming in/out of Phases .............................................................................................. 79 Analysis View showing Years .................................................................................................................. 79 Analysis View Zoomed into a specific Year ....................................................................................... 79 Figure 6-19 Zooming within Phases ..................................................................................... 79 6.12 (Driving) Logic Analysis ................................................................................................. 80 Figure 6-20 Logic Trace Menu ................................................................................................ 81 Figure 6-21 Triggering a Logic Trace from the Activity Browser ............................... 81 Figure 6-22 Results from a Logic Trace ............................................................................... 82
6 | P a g e
8 BENCHMARK ANALYSIS ................................................................................................ 85 Figure 9.1 Benchmark Analysis .............................................................................................................. 85 10 LOGIC ANALYSIS ........................................................................................................... 86 10.1 Overview .............................................................................................................................. 86 Figure 10-1 Various Logic Analysis Options ..................................................................................... 86 10.2 Positive and Negative Leads and Lags ....................................................................... 86 10.3 Redundant Logic ............................................................................................................... 86 Figure 10.2 Redundant Logic in a MS Project Schedule .............................................................. 87 Figure 10-3 Logic Analysis in Acumen Fuse ..................................................................................... 87 10.4 Circular Logic ..................................................................................................................... 87 10.5 Open Ends ............................................................................................................................ 87 10.6 Relationships on Summaries ........................................................................................ 88 10.7 Out of Sequence Updates ................................................................................................ 88 10.8 Reverse Logic ..................................................................................................................... 88 10.9 Dangling Activities (Open Start and Open Finish) ................................................. 88 10.10 Sorting and Grouping Logic Analysis Results ....................................................... 88 10.11 Publishing Logic Analysis Results ............................................................................ 88 11 FORENSIC ANALYSIS .................................................................................................... 89 11.1 Overview .............................................................................................................................. 89 11.2 Setting up a Forensic Analysis ...................................................................................... 89 Figure 11.1 Setting up a Forensic Analysis Workbook ................................................................ 90 11.3 Running a Forensic Analysis ......................................................................................... 90 Figure 11.2 Running a Forensic Analysis ........................................................................................... 90 Figure 11.3 Sorting and Grouping a Forensic Analysis Report ................................................ 91 Figure 11.4 Exported Forensic Analysis Results in MS Excel .................................................... 92 11.4 Modifying Reporting Criteria ........................................................................................ 92 Figure 11.5 Selecting the Modify Fields option in the Forensic Report ................................ 92 Figure 11.6 Customizing Forensic Columns ..................................................................................... 93 Figure 11.7 Customizing Columns and Criteria for the Forensic Analyzer ......................... 93 12 FUSE DASHBOARD ....................................................................................................... 95 Figure 12.1 Fuse Dashboard .................................................................................................................... 95 12.1 Fuse Widgets ...................................................................................................................... 96 Figure 12.1 Fuse Analysis Widgets ....................................................................................................... 96 13 REPORTING .................................................................................................................... 97 13.1 Activity Browser Printing .............................................................................................. 97 Figure 13-1 Printing the Activity Browser Results ........................................................................ 97 13.2 Comparison Analyzer Printing ..................................................................................... 97 Figure 13-2 Printing the Comparison Analyzer Results .............................................................. 98 13.3 Analysis View Report Generation ............................................................................... 98 Figure 13-3 Publish to MS Excel ............................................................................................................ 99 13.4 Executive Briefing ............................................................................................................ 99 Figure 13-4 Example Pages within the Executive Briefing Report ...................................... 100 13.5 Analyst Report ................................................................................................................. 100 Figure 13-5 Example of Analyst Report .......................................................................................... 101 13.6 Logic Analysis Report .................................................................................................... 101
7.1 Running a Comparison Analysis .................................................................................... 83 Figure 7-1 Compare Analysis Results .................................................................................................. 84
7 | P a g e
14 SCHEDULE CLEANSER ........................................................................................... 104 14.1 Running a Schedule Cleanse ....................................................................................... 104 Figure 14-1 Schedule Cleanser ......................................................................................................... 104 14.2 Scenarios ........................................................................................................................... 104 14.3 Publishing a Scenario to MS Project and Primavera ........................................... 104
Figure 13-6 Logic Analysis Report ..................................................................................................... 102 13.7 Forensics Analysis Report ........................................................................................... 102 Figure 13-7 Example of Analyst Report .......................................................................................... 103
15 TYPES OF ACUMEN FUSE ANALYSIS .................................................................... 106 15.1 Single Project Analysis .................................................................................................. 106 Single Project Shown as a Project Ribbon ...................................................................................... 106 Single Project Shown Ribbonized by WBS ..................................................................................... 106 Figure 15-1 Single Project Analysis Mode ...................................................................................... 106 15.2 Snapshot Comparison-Trending of a Project over Time ................................... 106 Figure 15-2 Snapshot Comparison Analysis Mode ........................................................... 107 15.3 Multi-Project/Portfolio Analysis ............................................................................... 107 Figure 15-3 Portfolio Analysis Mode ..................................................................................... 108 16 The Fuse Application Programming Interface (API) .................................... 109 Figure 16.1 Example Custom API integration .................................................................... 109 17 FUSE 360 GOAL-BASED OPTIMIZATION ......................................................... 110 17.1 How does a Fuse 360 Analysis Work? ...................................................................... 110 17.2 Defining a Goal ................................................................................................................. 110 17.2.1 Project Goal ................................................................................................................................ 110 Figure 17.1 Defining a Project Goal in Fuse 360 ................................................................ 111 17.2.2 Activity Goal ............................................................................................................................... 111 Figure 17.2 Defining an Activity Goal in Fuse 360 ............................................................ 112 17.3 Advanced Settings .......................................................................................................... 112 Figure 17.3 Advanced Acceleration Settings ...................................................................... 113 17.4 Defining Criteria Sets (Scripts) .................................................................................. 113 Figure 17.4 Script Editor ........................................................................................................... 113 17.4.1 Defining Steps ........................................................................................................................... 114 17.4.2 Defining Filters within Steps .............................................................................................. 114 Figure 17.5 Filter Definition within a Step .......................................................................... 115 17.5 Working with Script Templates ................................................................................. 115 Figure 17.6 Working with Criteria Set Scripts ................................................................... 116 17.6 Running a 360 Analysis ................................................................................................ 116 Figure 17.7 Results from a Fuse 360 Acceleration ........................................................... 117 17.7 Analyzing the Results .................................................................................................... 117 Figure 17.8 Results from a Fuse 360 Acceleration ........................................................... 117 17.8 Publishing Scenarios ..................................................................................................... 117 18 STANDARD FIELD MAPPINGS ............................................................................... 118 19 SYSTEM REQUIREMENTS ........................................................................................ 122
1.1 Overview
1.1.1 Project
Analysis
and
Visualization
Acumen
Fuse
is
a
project
analysis
and
visualization
software
tool
that
provides
a
unique
insight
into
project
planning
quality,
project
performance
and
project
execution.
This
is
achieved
by
simplifying
project
data
through
the
generation
of
Acumen
Fuse
Ribbons
against
which
libraries
of
project
metrics
are
applied.
Acumen
Fuse
analysis
can
be
conducted
for:
Analysis
of
a
single
project
Comparison
of
multiple
projects
within
a
program/portfolio
Trending
analysis
of
a
single
project
over
time
Forensic
analysis
of
projects
1.1.2 Acumen
Fuse
Ribbons
Acumen
Fuse
Ribbons
are
the
basis
against
which
an
analysis
is
conducted.
Ribbons
are
a
means
of
flattening
and
simplifying
large
amounts
of
project
data.
A
ribbon
can
be
defined
by
something
as
simple
as
an
activity
attribute
(e.g.
type
of
activity),
a
resource
or
can
be
defined
to
represent
a
path
through
a
network
between
two
activities
within
a
project.
Irrespective
of
how
a
ribbon
is
created,
its
purpose
is
to
group
activities
based
on
a
given
criteria.
Acumen
Fuse
analysis
is
conducted
against
ribbons.
The
benefits
of
grouping
project
data
into
ribbons
are
numerous:
Simplification
of
large,
complex
projects
reduction
of
large
numbers
of
activities
down
to
a
more
manageable
number
of
ribbons.
Visualization
of
activities
based
on
common
criteria
(e.g.
activity
attribute
or
network
path).
Easy
reporting
giving
fast
means
of
slicing
and
dicing
project
data.
Figure 1-1 shows a sample project created in MS Project that contains four activities and two parallel paths. Activities A, C and D all lie on the critical path. Activity B contains float and is not on the critical path.
9 | P a g e
In Acumen Fuse, at the summary level, you can create a single ribbon that contains all activities within the project. Figure 1-2 shows a ribbon view of the same sample project ribbonized by project.
Now consider a scenario whereby you want to ribbonize based on whether an activity falls on the critical path or not. Figure 1-3 shows the same sample project this time ribbonized by Critical Path. By separating critical and non critical activities, you are able to get a clearer insight into your project.
Figure 1-3 Sample Project Showing Critical Path Ribbons in Acumen Fuse
Taking this a step further, now consider creating ribbons not by an activity attribute but instead by paths through the network. Ribbons can be created by choosing any two points within your project (start point and end point) with the resulting network paths becoming the analysis ribbons. Figure 1-4 shows the example project ribbonized based on the paths between project start and project completion.
10 | P a g e
By
ribbonizing
by
various
activity
attributes
and
network
paths,
you
can
run
Acumen
Fuse
analytics
in
multiple
dimensions
providing
insight
that
is
not
easily
available
in
traditional
Gantt
chart
type
reports.
1.1.3 Acumen
Fuse
Metrics
Acumen
Fuse
uses
libraries
of
metrics
to
analyze
projects.
Standard
metric
libraries
pertaining
to
schedule
quality,
cost,
project
performance,
risk
exposure,
Earned
Value
and
more
are
included
within
the
tool.
Additional
libraries
and
associated
metrics
can
be
created.
Metrics
contain
formulas
and
tripwire
thresholds.
Formulas
are
used
to
calculate
results
as
part
of
an
analysis.
Tripwire
thresholds
are
used
to
flag
and
filter
activities
that
exceed
given
thresholds.
Metric
results
can
be
numeric
(e.g.
cost
or
duration)
or
percentages
(e.g.
percentage
of
total
project
duration).
Percentages
are
useful
for
portraying
results
within
a
given
context.
Metric
formulas
are
defined
using
standard
MS
Excel-based
formula
syntax.
Chapter
4
details
this
process.
Acumen
Fuse
includes
various
metrics
libraries
including
but
not
limited
to:
DCMA
14
Point
Schedule
Assessment
schedule
critique
Schedule
schedule
characteristics
Cost
cost
characteristics
Performance
execution
performance
relative
to
a
given
baseline
Plan
characteristics
nature
and
complexity
of
a
project
plan
Risk
Exposure
cost
and
schedule
risk
exposure
Earned
Value
EV-based
performance
analysis
Earned
Schedule
schedule-based
performance
analysis
Forensics
Comparison-based
metrics
for
determining
root
cause
of
delay
11 | P a g e
1.1.4 Acumen
Fuse
Analysis
Acumen
Fuse
is
based
on
an
advanced
metric
analytics
engine.
The
analytics
engine
applies
metrics
to
ribbonized
groupings
of
project
data.
Acumen
Fuse
analysis
is
conducted
in
three
modes
as
shown
in
figure
1-5.
Ribbon
analysis
metrics
are
applied
to
a
ribbon
as
a
whole.
Phase
analysis
metrics
applied
across
ribbons
within
a
specific
phase
or
time
period.
Intersection
analysis
metrics
are
applied
to
a
specific
ribbon
within
a
specific
phase.
Intersection
Analyzer
Ribbon
Analyzer
Phase nalyzer A
As well as calculating metrics, Acumen Fuse analysis also determines whether or not defined tripwire thresholds have been triggered. Figure 1-6 shows an example of two metrics being applied to our sample project with the lags metric causing a tripwire to be triggered. Note: the ribbon analyzer tells you which path is carrying the lag; the phase analyzer tells you which time period contains the lag and the intersection analyzer pinpoints the path and phase.
To pinpoint which activity(s) are causing the metric tripwire to trigger, use the Activity Browser. The Activity Browser shows activities based on which ribbon, phase or intersection you click on. This is described in detail in chapter 6.
12 | P a g e
One of the unique capabilities of Acumen Fuse is the way the analysis engine is able to analyze across multiple phases as well as segment data by ribbon. The analysis engine automatically calculates duration, cost and work across phase boundaries and spreads values accordingly. For example, a 60-day activity starting on January 1st will be automatically segmented into 31 days for January and 28 days for February (assuming a non leap year) and 1 day in March. The costs and work for this activity also get spread accordingly so that when the metric engine is run, results are not only analyzed for the ribbon as a whole but also within each individual phase. Similarly, the engine determines, for example, which phase an activity starts within. This in turn enables metrics such as the number of activities starting within a particular fiscal reporting period to be created. In addition to carrying out metric analysis, you can also use Acumen Fuse to conduct a comparison analysis. A comparison analysis is a means of comparing similarities and differences between two sets of results. For example, you can use a comparison analysis to compare the differences between two identified paths within a network or the cost differences between two disciplines.
13 | P a g e
1.2 Navigation
There
are
seven
main
navigation
tabs
within
Acumen
Fuse.
The
tabs
are
as
follows:
Projects:
used
to
create
and
maintain
project
workbooks.
Use
this
tab
to
import
project
data.
Dashboard:
executive
summary
of
status,
schedule
quality
and
forensics
analysis
Analysis:
the
main
reporting
and
analysis
view.
Use
this
tab
to
generate
Acumen
Fuse
analysis
sessions.
Logic:
advanced
logic
checks
Forensics:
compare
multiple
snapshots
or
historical
instances
of
a
project(s)
Metrics:
the
metric
editor
for
maintaining
custom
metrics.
Fields:
view
for
defining
custom
field
mappings
when
importing
project
data.
Navigation between these tabs is carried out through the Ribbon Navigation Menu Bar (figure 1-8).
File management (File New, Open, Close, Save, Save as, Print and Options) is navigated to by clicking on the Acumen Fuse icon in the top left hand corner of the ribbon menu bar (figure 1-9).
1.2.1 The Projects View The projects view is used to manage the contents of Acumen Fuse workbooks. Workbooks are containers for storing project data. Project data can come from multiple 14 | P a g e Figure 1-9 File Management Menu
sources/platforms and can be a combination of cost, schedule, risk or any other type of project management data that is to be analyzed.
A workbook can contain one or more projects. A project can optionally contain one or more snapshots. Snapshots are previous versions of a project file. This enables comparisons between versions of a single project file to be carried out without accidental double-dipping of data during analysis. More detail on project snapshots can be found in chapter 2.
15 | P a g e
1.2.2 The Dashboard View The dashboard view is used to provide a summary overview as to the status, quality, health as well as changes made to a project or projects. A dashboard can be used at the workbook level or specifically within the context of a single project.
16 | P a g e
Phases
Intersection Analysis
Ribbon Analyzer
Phase Analyzer
Activity Browser
A single workbook can contain multiple analysis views. For example, you may have a analysis view designed for cost analysis and a second analysis view for the same workbook setup for risk exposure analysis.
17 | P a g e
1.2.3.1 Ribbon Browser The ribbon browser is the core of the analysis view. Within the ribbon browser, you create ribbons, segment by phases and apply metrics. The ribbon browser is highly customizable. 1.2.3.1.1 Ribbons Ribbons are groupings of activities based on a given criteria. By default, ribbons are grouped by project but can be grouped in multiple ways including activity attribute, resource and path. If a workbook contains multiple projects, then a separate ribbon for each of these projects will be shown. Ribbons also contain activities. These activities can be hidden from within a ribbon if desired. Ribbons are segmented by phases. 1.2.3.1.2 Phases Phases are user definable segments of time against which the Acumen Fuse analysis is run. Phases can be weeks, days, months, quarters, years, custom periods or the entire project duration. 1.2.3.2 Phase Analyzer The phase analyzer shows the results from an Acumen Fuse analysis for each phase. Multiple metrics can be added to the phase analyzer. The phase analyzer can be displayed as either a table or a chart. 1.2.3.3 Ribbon Analyzer The ribbon analyzer shows the results from an Acumen Fuse analysis for each ribbon. Multiple metrics can be added to the ribbon analyzer. The ribbon analyzer can be displayed as either a table or a chart. 1.2.3.4 Intersection Analyzer In addition to running an analysis against a ribbon or phase, Acumen Fuse also enables metric reporting against a single segment within the ribbon browser (i.e. for a specific ribbon within a specific phase). 1.2.3.5 Activity Browser The Activity Browser shows individual activities. The activities shown depend on which segment of the ribbon or analyzer windows are clicked. There are six modes in which the Activity Browser can be used for reporting. These are described in detail in chapter 6. 1.2.4 The Logic View The logic analysis view is used to run various logic integrity checks against the schedule(s). Numerous analysis checks can be carried out including relationship types, leads and lags, redundant logic, open ends, circular logic, out of sequence updates and reverse logic.
18 | P a g e
1.2.5 The Forensics View The forensics view enables you to compare multiple iterations, versions or snapshots of a schedule and track and trend changes and variances over time. There is no limit to the number of comparisons that can be made and every single field (including codes and user defined fields) can be analyzed for variance.
19 | P a g e
1.2.6 The Metrics View The metrics view is used to manage metrics, including the editing of existing and creation of new metrics.
20 | P a g e
Advanced Formula
Metrics
The three formula properties use a combination of user-friendly filters and optional advanced MS Excel type formulas where needed. 1.2.6.1 Primary formula The primary formula is the formula used to calculate the primary result calculated in an Acumen Fuse analysis. 1.2.6.2 Secondary formula The secondary formula is the corresponding formula associated with the primary formula often used to represent the primary formula as a percentage. 1.2.6.3 Tripwire formula The tripwire formula is used to determine the individual exceptions that are listed in the Activity Browser.
21 | P a g e
1.2.6.4 Tripwire Threshold The threshold editor enables customizable thresholds to be defined and associated colors set. 1.2.7 The Fields View The fields view is used to map fields from the various source projects to corresponding fields in the Acumen Fuse workbook. Field mapping is flexible in that an individual Acumen Fuse field can obtain its data from any field from the source project. Further, the mappings between source projects may be different e.g. Baseline Start may come from Start1 in Project A and BaselineStartDate in project B (all within the same workbook). Standard, User Defined and Code fields can be mapped. Default mappings for all of the supported platforms are included.
Selected Source
Source Fields
Fuse Fields
22 | P a g e
In
addition,
Acumen
Fuse
provides
flexible
customizable
integration
with
MS
Excel.
The
Excel
integration
enables
you
to
import
data
in
almost
any
format
from
an
Excel
spreadsheet.
Data from any discipline (cost, schedule, risk, earned value, performance etc.) can be analyzed within Acumen Fuse. Refer to chapter 3 for more information on custom mapping and importing.
23 | P a g e
Only one workbook can be open at a time within Acumen Fuse. Workbooks are stored as single files either on a local or network drive. Workbooks can be saved in two formats: 2.1.1 Standard File Format This is the default file format for saving Acumen Fuse workbooks. A proprietary high performance file format is used. Standard files have a file suffix of .afw. These files can be shared between users via file sharing and email etc but the content of the file cannot be edited outside of Acumen Fuse. For the analysis of large project files, it is recommended that the standard file format is used. 2.1.2 XML File Format Acumen Fuse workbooks can optionally be saved as XML. XML files provide a more open means of storing data as well as a means of viewing/sharing the content of the file outside of Acumen Fuse. This file format generates larger file sizes and as such is not as efficient as the native .afw format. Creation of an Acumen Fuse workbook is very straightforward. From within the Projects tab (the first navigation tab), simply click on the Acumen Fuse icon to reveal the file menu and select New.
If you currently have a workbook open, you will be prompted to save any changes before your new workbook is created. Once a new workbook has been created, you can then start linking and importing projects. 2.2.1 Metrics within a Workbook It should be noted that each workbook contains its own metric library. Any changes made to metrics or the metric library are made only to the currently opened workbook. To re-use an updated metric library, you will need to open the updated workbook and do a Save As before proceeding with adding projects for analysis.
Once you have created a new workbook you can begin to link to external data sources. The objective here is to create links and mappings between your workbook and one or more data sources so as to determine where to import project data from. Linking is the pre-cursor step to actually importing the data. A workbook can have an unlimited number of links to external sources. Acumen Fuse supports seven different types of data source. Once an external source is linked, default field mappings are applied between the source data and the Acumen Fuse workbook. These mappings are fully configurable as described in chapter 3. 2.3.1 MS Project 2003/2007/2010 Acumen Fuse links to MS Project files either through your installed copy of MS Project (2003, 2007, 2010) or by directly reading a MS Project file (without needing MS Project installed on your PC). The means by which MS Project is imported into Fuse can be set in the Fuse Options menu. MS Project linking supports cost, schedule, risk and Earned Value integration by default. MS Project linking supports custom field mapping (normal, code and user defined fields see Chapter 3). 2.3.2 Oracle Primavera P6 (V5/6/7/R8) Acumen Fuse links to Oracle Primavera P6 XER files. XER files are the standard means of exporting data outside of a P6 database. You do not need P6 installed on your PC to link and import XER files into Acumen Fuse. MS Project linking supports cost, schedule, risk and Earned Value integration by default. Primavera P6 linking supports custom field mapping (normal, code and user defined fields see Chapter 3). 25 | P a g e
2.3.3 Linking to a single Project within an XER File You can import a single project from an XER or all projects within the XER file. To do this, click on the From Oracle Primavera > Single Project from XER file. When prompted with a list of projects within the XER file, select the desired project and click OK.
2.3.4 Linking to All Projects Within an XER File If the XER file you are linking to contains more than one project, you can import all of the projects in a single step. To do this, click on the From Oracle Primavera > Multiple Projects from XER file. 2.3.5 Primavera P3 You can import a project(s) from a Primavera P3 file. To do this, click on the From Oracle Primavera > Single Project from a P3 file. When prompted select the desired project file (with a dir.p3 suffix) and click OK. 2.3.6 Oracle Primavera Risk Analysis (formerly known as Pertmaster) Acumen Fuse links to Primavera Risk Analysis files directly through your installed copy of Risk Analysis (V8.x and higher) or in absence of having Risk Analysis installed, you can natively read .plnx files into Fuse. You must have Risk Analysis installed on your PC in order to link and to and import .plan files from a Risk Analysis file. Such installation is not required for importing .plnx files generated in Risk Analysis. In addition to importing cost and schedule data, Acumen Fuse imports both risk inputs and risk output data from your Risk Analysis file. This enables you to conduct advanced risk-based analytics. Risk Analysis linking supports custom field mapping (normal, code and user defined fields see Chapter 3). 2.3.7 Deltek Open Plan Acumen Fuse links to Deltek Open Plan 3.x files directly through your installed copy of Open Plan. You must have Open Plan installed on your PC in order to link and to and import from an Open Plan file. In addition, you must have a valid Open Plan login in
26 | P a g e
order to select a project for linking to. The Open Plan login credentials can be stored in the Acumen Fuse Options > Platforms window. Open Plan linking supports custom field mapping (normal, code and user defined fields see Chapter 3). 2.3.8 Asta PowerProject Acumen Fuse links to Asta PowerProject schedules that have been saved in the Asta PowerProject database format (MS Access files with .mdb suffixes). These files do not contain Float values for activities and so if float-based analysis is required for an Asta PowerProject in Fuse, the following steps in PowerProject must first be carried out before importing the mdb file: 1) Load the project file in PowerProject 2) Under Tools > User Field Manager, select Object Type > Bar > Add > Integer and name the newly created field e.g. TotalFloatUserField" 3) Add a column in the main view for Total Float: right click on column header > add column > Float > Total Float (you are about to copy this column to your newly created user field) 4) Add your user column in the main view by right clicking on a column header > Add column > User > " TotalFloatUserField " 5) Copy Total Float field data to user field (TotalFloatUserField) by selecting the Total Float column header and trigger a copy (CTRL C or edit > copy). Move to the user field and paste the data by edit > paste (or CTRL V) 6) Save file as an Asta PowerProject database MDB file You can now read the MDB file directly into Fuse. Once imported, to reference the Total Float field, simply map the User Field representing Total Float to the Fuse Total Float field in the field mapping view. 2.3.9 UN/CEFACT XML Schedule Files Acumen Fuse links to schedule files that use the UN/CEFACT XML schema (version D080B). This schema is an emerging standard being driven by the likes of the DCMA. You can link to and import from a UN/CEFACT XML file without having a scheduling tool installed on your PC. UN/CEFACT linking does not support custom field mapping. 2.3.10 Deltek Cobra CAP Earned Value Data Detailed phase-based Earned Value (EV) data can be linked to from Deltek Cobras Excel based CAP report. Importing a CAP report into Acumen Fuse enables Earned Value metrics to be run during a Fuse analysis. It should be noted that the outputs from an EV analysis (e.g. CPI, SPI, SV, CV etc) are not imported from the CAP report. Instead, these
27 | P a g e
calculations are carried out directly within Acumen Fuse and are included in the Earned Value metrics. Deltek Cobra linking in Acumen Fuse does not support custom field mapping. Earned Value metric analysis is not limited to Deltek Cobra data. EV data can originate from any of the supported platforms and be imported into an Acumen Fuse workbook through custom field mapping (see chapter 3). 2.3.11 MS Excel Acumen Fuses interface with MS Excel provides an extremely open and flexible means of linking to external data. Any data that can be stored as an XLS or XLSX file can be imported into Acumen Fuse for analysis. When linking to an Excel file you are firstly prompted to select which worksheet within your Excel file you want to import (figure 2- 3).
Once you have linked to a desired worksheet, you need to create mappings between the columns in the XLS spreadsheet and the fields within your Acumen Fuse workbook (see chapter 3). Excel fields will be auto mapped to Fuse fields if the field names are consistent between the two applications. 2.3.12 ARES PRISM G2 Detailed phase-based Earned Value (EV) data can be linked to from ARES PRISM G2. This is a very flexible means of analyzing time-phased cost data. PRISM G2 linking in Acumen Fuse does not support custom field mapping.
Links to data sources can be either projects or snapshots within a workbook. During an analysis, it is often useful to reference summated values within a workbook, for example, total workbook cost or duration. If the workbook contains different projects, then such a summation is straightforward. However, if the workbook contains say two
28 | P a g e
versions of the same project, then it is not valid to assume that the total workbook cost is the sum of both projects. By flagging a project as being a project or a snapshot of a parent project, the analysis engine is able to correctly calculate workbook level totals. 2.4.1 Project Links A project link is the most common type of link within a workbook. A project link treats the linked data as a normal project including all data in workbook summary calculations. 2.4.2 Snapshot Links Snapshot links belong to project links. A snapshot link cannot exist outside of a project link. A snapshot link is used to flag the project data as being a different version of the parent project. Not all the data from a snapshot linked project gets rolled up to the workbook level when the analysis engine calculates workbook level metrics. A snapshot of a project does not have to originate from the same source type as that of its parent project. For example, your current schedule may be stored in Primavera P6 whereas a previous version of the project may have been created (and linked to in Acumen Fuse) in MS Project.
By selecting a project in the list of projects prior to linking to a new source, you are automatically designating the newly linked project to be a (child) snapshot of the selected project.
29 | P a g e
2.4.4 Converting
a
Snapshot
to
a
Project
If
you
need
to
escalate
a
snapshot
to
become
its
own
project:
Select
the
snapshot
in
question
Click
on
the
Convert
Snapshot
to
Project
2.4.5 Adding a Baseline to Primavera P6 Workbooks XER files exported from Primavera P6 do not contain associated baseline project data. This causes a challenge when running metrics within Fuse that compare baseline data with the current schedule. To overcome this, Fuse provides the ability to assign a given P6 baseline schedule to a P6 schedule that has been brought into a Fuse workbook. In essence, this process merges a baseline dataset with the current project dataset overcoming the issue of baselines not natively being saved as part of an XER export from P6.
30 | P a g e
Baselines can be re-assigned/added/deleted by right-clicking on the Primavera project. A Primavera file can be assigned as both a snapshot and a baseline in a single step. Right click on the parent project and select Set Baseline and Add Snapshot. 2.4.6 Merging Multiple Data Sources into a Single Dataset (e.g. cost and schedule) Fuse includes a powerful utility for merging datasets from disparate sources into a single set of data that can be subsequently analyzed as a single dataset. Example use cases include merging a cost estimate from Excel with a schedule created in MS Project or Primavera. Such integration is a powerful means of combining cost and schedule information.
31 | P a g e
To create a merge file, firstly select the project file that youd like to merge data into. Right click on the project and select Merge with Excel File. Select the desired Excel file and then hit the Import Project button to actually complete the merge. The actual data merge occurs when the parent project data is imported into Fuse. Once merged, the combined dataset can be exported from Fuse using the Export to Excel button in the project workbook view. Merging is not limited to cost/schedule. Any dataset that has a ID structure that corresponds with the activity IDs in the main dataset can be merged. If the field headings in the XLS merge file correspond to field names in the Fuse file, they will be auto mapped (merged). Non-standard fields can also be imported/merged simply by drag-dropping the merge fields into the Fuse field list in the field mapping view (figure 2.9). Available mapped fields are displayed in the source field list highlighted in green. The merge file must have a column called ID in order to bind the merge data with activities in the Fuse workbook.
32 | P a g e
Source XLS Cost d containing ata Actual Cost and CAM Owner
Schedule ribbons grouped by CAM & showing actual cost (both from merged XLS file)
Once
you
have
defined
your
workbook
by
adding
projects
and
snapshots,
you
are
ready
to
import
the
data.
Importing
can
be
done
on
a
per
project/snapshot
basis
or
for
the
workbook
as
a
whole.
To
import
a
single
project/snapshot:
Select
the
desired
project/snapshot
Click
on
Import
Project
under
the
Import
menu.
33 | P a g e
Importing
project
data
will
override
any
existing
versions
of
previously
imported
data
for
the
project(s)
in
question.
Once
imported,
the
project
data
is
stored
within
the
Acumen
Fuse
workbook.
Subsequent
importing
is
not
necessary
to
conduct
repeated
analysis.
Re-importing
is
only
required
if
you
want
to
analyze
newly
updated
data
that
has
changed
in
the
source
application.
2.5.1 Filtering
Project
Data
During
an
Import
When
importing
project
data,
you
can
optionally
filter
the
type
of
information
that
is
imported
into
your
Acumen
Fuse
workbook.
Filters
can
be
applied
based
on:
Activity
type:
filter
on
normal,
milestone,
summary,
Level
of
Effort
(LOE)
Status:
Complete,
in
progress,
planned
Resource
assignments
34 | P a g e
Different filters can be applied to each project/snapshot within a workbook. Additionally, the default hours per day can be set. This is used when converting the default duration units for displaying durations in Acumen Fuse.
While a Fuse workbook can contain an unlimited number of projects and snapshots, you can control which of these projects/snapshots get included in a Fuse analysis. To include/exclude projects from a Fuse analysis, use the checkboxes to the right of the project icons in the projects list.
Once imported, workbook duration and work data can be displayed in either days or hours. Irrespective of the display units selected, the analysis engine will always calculate results to the nearest minute.
Once the activities have been selected, click on the Timeline view to display the activities. Each project/snapshot/scenario is shown in its own timeline. The timeline can be scaled and zoomed using the zoom feature at the bottom of the view.
37 | P a g e
With the ability to import from multiple platforms comes the ability to also customize which fields are imported into a workbook. Each supported platform (e.g. MS Project and Primavera) has default field mapping templates. These defaults mean that unless you need to change the default behavior of an import, you can import project data without manually having to create or maintain field mappings. However, if you want to change the way fields are imported and/or want to import additional fields that are not part of the standard field mapping templates, then you can use the field mapping feature to achieve your custom imports.
Fuse Fields
Figure 3-1 shows an example of the field mapping view. The example shows two projects within a workbook (Project A and Project B). Project A is a Primavera P6 project
38 | P a g e
and Project B is a MS Project project. The Fields view is best explained by examining the columns from right to left: The right hand side column contains a list of Acumen Fuse fields. These fields are available during an analysis and can be referenced by metric formulas. The names of the fields can be edited by clicking on the field name and editing the content. The bold field names cannot be edited (but can have customized mappings assigned to them). The center columns (highlighted in figure 3-1 by the blue rectangles are the currently mapped fields. There is a separate column shown for each of the projects/snapshots within a workbook. When linking to a data source, default mappings are assigned based on the platform type. If we examine the Acumen Fuse field called Baseline Work in figure 3-1, we can see that the corresponding default field for Project A (Primavera file) is known as Budgeted Labor Units whereas in Project B, the same field is known as BaselineWork. Based on the default mappings, Acumen Fuse normalizes these fields even though the field names are actually different. Within your workbook, this field is then referred to as Baseline Work. Acumen Fuse field mapping provides the flexibility to have different custom mappings from each of your data sources to a common field in effect, standardizing data from multiple platforms that may have very different data schemas.
39 | P a g e
Any of the non-bold type faced Fuse fields can be deleted by clicking on the Activity Fields > Delete.
Field
mappings
can
be
deleted
without
deleting
the
field
itself.
This
is
useful
when
you
no
longer
want
to
import
a
specific
field
that
has
previously
been
mapped.
To
delete
a
field
mapping:
Click
on
desired
the
mapped
source
field
Click
the
Mapped
Field
>
Delete
button
40 | P a g e
results from the analysis, at a minimum, the standard default mapped fields should be populated.
The custom field mapping enables fields of different types to be matched with each other. During analysis Acumen Fuse determines how to treat a field (type) based on the data and context within which it is being used. Such flexibility allows, for example, a user defined number field to be mapped as a text field in Acumen Fuse.
If
your
workbook
contains
multiple
projects/snapshots,
you
can
map
a
single
field
(standard,
user,
code)
to
all
projects/snapshots
in
a
single
click
(rather
than
having
to
repeat
the
field
mapping
process
manually
to
each
project).
To
do
this:
Select
the
required
field
Click
on
Map
to
All
Projects
If you need to map all code fields from a source project/snapshot, you can use the Source Fields > Map All Code Fields to assign all code fields to the workbook in a single click. By default, all code fields are auto mapped during an import. This feature can be disabled in the Options menu of Fuse.
If you need to map all code fields from a source project/snapshot to multiple projects, you can use the Source Fields > Map All Code Fields for all Projects to assign all code fields all the projects in the workbook in a single click. Fuse will map all common codes within each source file to all projects within the workbook. By default, all code fields are auto mapped during an import. This feature can be disabled in the Options menu of Fuse.
If you need to map all User fields from a source project/snapshot to multiple projects, you can use the Source Fields > Map All User Fields for all Projects to assign all user 41 | P a g e
fields to the workbook in a single click. By default, all user fields are not mapped during an import. This feature can be enabled in the Options menu of Fuse.
To reset field mappings within a workbook, click on the Load Default Mapping
Each workbook contains its own field mapping template. Each project/snapshot within a workbook also has its own mapping values back to the fields within the workbook template.
In order for metrics to produce valid calculations, the fields referenced in the metric definition need to be present in the workbook. The default field mapping templates include the required fields for the standard metric libraries to be run.
42 | P a g e
4 MANAGING
METRICS
4.1 Introducing
Acumen
Fuse
Metrics
The
Acumen
Fuse
analysis
engine
uses
libraries
of
metrics
to
run
project
analytics.
These
metrics
are
defined
using
either
basic
filters
or
more
advanced
formulas
that
are
of
the
same
syntax
as
those
found
in
MS
Excel.
Acumen
Fuse
includes
various
libraries
of
metrics.
Metrics
can
be
edited
using
the
metric
editor.
Each
metric
contains
three
formulas:
4.1.1 Primary
Formula
The
primary
formula
is
the
formula
used
to
calculate
the
primary
result
calculated
in
the
analysis
(e.g.
total
cost).
4.1.2 Secondary
Formula
The
secondary
formula
is
the
second
of
two
results
that
can
be
displayed
for
a
metric
after
running
an
analysis.
Typically
(although
not
limited
to),
the
secondary
metric
is
used
to
show
the
primary
formula
as
a
percentage
(e.g.
cost
as
a
percentage
of
total
project
cost).
The
secondary
formula
is
an
optional
attribute
of
a
metric.
If
it
is
not
defined,
it
will
not
display
in
the
analyzer
windows.
4.1.3 Tripwire
Formula
The
tripwire
formula
is
(optionally)
used
to
determine
the
individual
exceptions
that
are
listed
in
the
Activity
Browser.
Metrics
that
dont
contain
a
Threshold
formula
cannot
be
used
to
display
activities
in
the
Activity
Browser
and
also
cannot
be
used
in
the
Comparison
Analyzer.
4.1.4 Tripwire
Threshold
A
tripwire
threshold
is
a
defined
value
that
if
exceeded,
causes
a
metric
to
be
classified
as
triggered.
A
metric
can
have
multiple
trigger
points
with
corresponding
color
coding
for
each
interval.
The
threshold
editor
enables
customizable
bandwidths
or
thresholds
to
be
defined,
color
coded
and
described.
43 | P a g e
Each metric contains three formulas (primary, secondary and tripwire). Each of these three formulas are built using a three level hierarchy: Inclusions: a top level set of filters to exclude specific activities based on type, status and time period Filters: standard filters that further pinpoint specific activities Formula: advanced custom formulas to further specify advanced criteria sets. Inclusions, filters and formula are hierarchical.
44 | P a g e
Activity Status e.g. planned, in-progress, complete Activity type e.g. normal, milestones, summary Inclusions Time period e.g. starts or inishes in current time period Filters
Simple
ilters
based
on
ields
e.g.
Actual
Start
Date
>
Baseline
Start
Date
Multiple
ilters
can
be
added
-
treated
as
AND
compounds
User-deined
formulas.
Useful
when
needing
OR
statements
,
divisions
or
other
advanced
functions.
Figure
4-2
Hierarchical
Development
of
Metrics
Formulas
Acumen Fuse metrics can be developed using either a basic or advanced approach (or a combination of the two): Basic: essentially a filter-based set of metrics that dont require detailed formula definition Advanced: detailed formulas used to define a metric beyond a simple filter Acumen Fuse metric formulas use what is known as array-based formulas in their calculations. These are explained in detail below but enable us to group and aggregate multiple activities together so that results for a ribbon or phase or intersection can be calculated. 4.3.1 Array Formula Types Acumen Fuse metric formulas are based on Single Value Result Array formulas. Single Value Result Array formulas work with a series of data (activities), aggregate it (typically using the likes of SUM, AVERAGE or COUNT) and return a single value to the (ribbon, phase or intersection) analyzer. Array formulas typically return a series of values. For example, in Excel, the formula =Row(A1:A5) returns only a single value (the first value in the list). Instead, an array formula will return all values for A1 to A5. Against the results of an array formula, you 45 | P a g e
typically
apply
a
container
function
such
as
SUM
or
AVERAGE
or
COUNT.
These
functions
enable
you
to
apply
the
function
to
the
list
of
values
and
return
a
single
value
result.
Relating
this
back
to
Acumen
Fuse,
a
ribbon,
phase
and
intersection
all
contain
one
or
more
activities.
In
the
case
of
phases
and
intersections,
the
activities
may
span
across
more
than
one
phase
or
intersection
and
so
certain
data
(duration,
work
and
cost
field
types)
gets
pro-rated
(see
chapter
5
for
more
detail).
When
metric
functions
are
applied
during
an
Acumen
Fuse
analysis,
they
are
applied
to
the
ribbon,
phase
or
intersection
indirectly
being
applied
to
all
activities
within
that
segment
through
the
use
of
an
array
formula.
Array
formula
Original
Duration
=
5
+
5
=
10
46 | P a g e
For both basic and advanced Primary formula definition, formatting of primary formula results is achieved using the Formula Format drop down list. 4.3.3 Developing Secondary Formulas A Secondary formula is additional information shown in a ribbon/phase or intersection analysis window. Secondary formulas are defined in a similar way to how a primary formula is defined. If a secondary formula is to be used to show a percentage, set the Format option to Percentage. There are two ways to create a secondary formula: Simple percentage relative to the primary formula: if the secondary formula is representing a percentage of the primary formula, then there is no need to create complex formulas to create this result. Instead, simply select the relevant inclusions and filters (in order to define the population against which you are going to divide the primary formula in order to calculate the percentage) and then set the mode to Percentage of Primary Formula. A simple percentage secondary formula can be auto- calculated in this mode irrespective of whether the primary formula has been defined in basic or advanced mode. Advanced Secondary Formula: if the required secondary formula is not a simple percentage of the primary formula, then set the mode to Advanced and define the inclusions, filters and advanced formula manually.
47 | P a g e
Figure 4-4 Simple Percentage of Primary Formula and Advanced Secondary Formula Definition
4.4 Tripwires
Tripwires are a very useful means of graphically depicting when a particular metric threshold is reached. Acumen Fuse tripwires are flexible with regards to the number of thresholds per metric that can be defined, the type of thresholds (absolute and gradient) and the formulas against which they can be based (primary and secondary). 4.4.1 Tripwire Formulas The tripwire formula is used to determine the individual exceptions that are listed in the Activity Browser. Tripwire formulas must ultimately return a Boolean in the form of either a True or False value. The most commonly used function to return this Boolean is an AND statement. AND functions can contain an unlimited number of conditions. AND(ActivityType=Normal, ActivityStatus=Planned) Tripwire formulas get applied to each activity separately whereas primary and secondary formulas get applied to groupings of activities (depending on the ribbon, phase or intersection context). Tripwire formulas can be created in one of two ways: Auto Calculated by Primary Formula: if the Primary formula was created using the basic mode, you can opt to automatically create the tripwire formula without defining any inclusions, filters or formulas for the tripwire definition. Instead, Fuse will automatically create a Tripwire formula based on the inclusions and filters defined in the primary formula. This mode cannot be used if the primary formula was created in advanced mode. In Auto Calculated by Primary Formula mode, the tripwire inclusions and filters options are disabled as they are not needed in light of the fact these settings are automatically inherited from the primary inclusions and filters. 48 | P a g e
Advanced: This mode enables you to manually create inclusions, filters and advanced functions that together return the required set of activities.
Advanced Mode
For each of the three scale types, varying numbers of interval can be created. In addition to using the standard scale types, additional intervals can be added through the Color Scales menu. 4.4.4 Normal and Gradient Scales Threshold intervals can be defined as either normal or gradient. By default, scales are defined as normal. All threshold intervals within a single metric are either normal or gradient-based (they cannot be mixed within a metric). Normal scales behave in an absolute or binary manner that is, a metric result either triggers a threshold or it doesnt. A Gradient Scale behaves differently, in that a metric result, while falling within a given interval, can be represented as being close to an interval boundary. This type of scale is useful when determining how close to a tripwire boundary does a metric result get. When using gradient scales, instead of discrete colors for the intervals being used, gradient scales of color are used (based on where the metric falls in the scale). 4.4.5 Including/Excluding Metrics from Analysis By default, each metric is available in all three analyzers (ribbon, phase, intersection). Optionally, metrics can be excluded from a particular analysis (e.g. phase) if, for example, the context is not valid. Including/excluding metrics from each of the three analyzers is done through the three check boxes in the Applies To menu. Additionally, the Include in New Workbook checkbox enables you to define whether a metric gets automatically added to a view upon creation of a new workbook.
When creating or editing a metric formula, you can use the Check Formula button to validate the syntax of the formula. Note that when using the check formula button the test calculation is applied to all activities within the workbook. 50 | P a g e
The Acumen Fuse metric editor supports all MS Excel functions. The most commonly used formulas are grouped in the Commonly Used Menu.
4.6.1 IF(logical_test,
value_if_true,
[value_if_false])
The
IF
function
returns
one
value
if
the
specified
condition
is
TRUE
and
returns
another
value
if
the
specified
condition
is
FALSE.
Logical_test
Required
-
Any
value
or
expression
that
can
be
evaluated
to
TRUE
or
FALSE
Value_if_true
-
Required
-The
value
to
be
returned
if
the
logical_test
argument
evaluates
to
TRUE
Value_if_false
Optional
-
The
value
to
be
returned
if
if
the
logical_test
argument
evaluates
to
FALSE.
If
omitted
then
zero
is
returned
Example: IF(TaskStatus="Inprogress",1,0) returns 1 if the activity status is equal to InProgress otherwise 0 is returned. IF statements can be written in shorthand within Acumen Fuse. If the IF function name and Value_if_true and Value_if_false parameters are omitted, the Acumen Fuse engine will assume that the function is an IF statement returning either a 1 or a 0. e.g. IF(TaskStatus="Inprogress",1,0) can be written in shorthand as (TaskStatus="Inprogress")
4.6.2 SUM(number1,
[number2],
[number3],
[number4],
...)
The
SUM
function
adds
all
the
numbers
specified
as
arguments.
number1
Required
-
The
first
item
that
you
want
to
add
number2,
number3,
number4,
...
Optional
-
The
remaining
items
that
you
want
to
add
51 | P a g e
4.6.3 AND(logical1,
[logical2],
...)
Returns
TRUE
if
all
its
arguments
evaluate
to
TRUE;
returns
FALSE
if
one
or
more
arguments
evaluate
to
FALSE.
Most
commonly
used
in
the
Tripwire
formula.
logical1
Required
-
The
first
condition
that
you
want
to
test
that
can
evaluate
to
either
TRUE
or
FALSE.
logical2,
...
-
Optional
-
Additional
conditions
that
you
want
to
test
that
can
evaluate
to
either
TRUE
or
FALSE
Example:
AND(
ActivityType="Normal",
ActivityStatus<>"Complete")
returns
TRUE
if
the
activity
type
is
NORMAL
and
activity
status
is
not
equal
to
COMPLETE.
4.6.4 MAX(number1,number2,...)
Returns
the
largest
value
in
a
set
of
values.
Number1,
number2,
...
-
are
1
to
255
numbers
for
which
you
want
to
find
the
maximum
value.
Example: MAX(TotalFloat) returns the maximum Total Float. 4.6.5 AVERAGE(number1, [number2],...) Returns the average (arithmetic mean) of the arguments.
number1 Required - The first number for which you want the average. number2, ... - Optional - Additional numbers for which you want the average, up to a maximum of 255
4.6.6 COUNTIF(range,
criteria)
Counts
the
number
of
occurrences
that
meet
a
given
criteria.
Range
-
Required
-
One
or
more
fields
that
contain
numbers.
Criteria
-
Required
-
A
number,
expression,
or
text
string
that
defines
which
records
to
be
counted.
For
example,
criteria
can
be
expressed
as
3,
">3","Normal",
or
"3".
Example: COUNTIF(TotalFloat,">5") counts the number of activities who have a Total Float value greater than 5.
When creating metric formulas, there are four types of field that can be referenced. These are described below. Formulas are generally written within the context of an activity. By further exposing fields outside of the activity context (e.g. project and workbook), you are able to model how activities relate to and potentially impact other contexts such as project and workbook. 4.7.1 Activity Fields Activity fields are the most commonly used type of field in an Acumen Fuse metric formula. All fields that are defined in the field mapping during a project import are exposed as activity fields in the metric editor.
52 | P a g e
4.7.2 Project
Fields
Some
project
level
fields
get
automatically
imported
during
a
project
import.
These
fields
are
also
exposed
for
use
within
metric
formulas.
When
a
metric
is
calculated
that
contains
a
project
field
reference,
the
specific
project
field
value
for
the
activity
in
question
is
used.
A
single
metric
calculation
may
contain
activities
from
multiple
projects.
In
this
instance,
the
appropriate
project
level
field
value
will
be
used
for
each
activity
(e.g.
time
now
may
be
different
for
each
of
the
projects).
Project
fields
include:
Project
Start
[ProjectStart]
Project
Finish[ProjectFinish]
Project
Time
Now
[ProjectTimeNow]
4.7.3 Workbook
Fields
Workbook
fields
are
summated
values
that
are
calculated
at
the
workbook
level
(that
take
into
account
all
activities
within
the
workbook).
Workbook
fields
include:
Workbook
Cost
(total)
[WorkbookCost]
Workbook
Actual
Cost
[WorkbookActualCost]
Workbook
Remaining
Cost
[WorkbookRemainingCost]
Workbook
Budget
Cost
[WorkbookBudgetCost]
Workbook
Budget
Duration
[WorkbookBudgetDuration]
Workbook
Actual
Duration
[WorkbookActualDuration]
Workbook
Remaining
Duration
[WorkbookRemainingDuration]
Workbook
Duration
(total)
[WorkbookDuration]
Workbook
#
of
Activities
[WorkbookNumberofactivities]
4.7.4 Dynamic Fields Dynamic fields have different values depending on the context within which they are being used within an analysis. Period Start and Period End are both dynamic fields. When Period Start and Period Finish are being applied to a phase analysis, Period Start and Period Finish relate to the start and finish of the phase in question. When being used within the context of a ribbon, Period Start and Period End relate to the start and end date of the ribbon. Period Start: [_PeriodStart] Period Finish: [_PeriodFinish]
In addition to editing a metric library within a given workbook, metric libraries can be saved as templates and re-used within other Fuse workbooks.
53 | P a g e
4.8.1 Saving a Metric Library as a Template Once a metric library has been customized, you can save it (for re-use) by clicking on the Fuse icon > Save as > Fuse Metric Library Template. This saves the metric library as an XML file that can subsequently used when creating new Fuse workbooks. Metric library files can be stored on file servers and shared between multiple users if required.
4.8.2 Re-using a Metric Library Template To re-use a Fuse metric library template: Fuse Icon > File > Open > [select the Fuse metric template file]. This will create a new Fuse workbook and automatically inherit the selected metric template library. 4.8.3 Setting a Custom Metric Library as the Default Library In addition to manually applying custom metric libraries through the steps described above, you can also set a custom metric library to be the standard default library for each newly created workbook. From the Fuse icon > Options menu, deselect the Use built-in Metric Library option and then select the desired custom metric library file. This will subsequently be applied to all newly created Fuse workbooks.
54 | P a g e
55 | P a g e
Scorecard totals are calculated using two approaches: Overall scores: (e.g. project scores): based on the number of activities within the dataset that fail one or more of the metric tests (irrespective of weighting) o This method can be modified through the Options window to use weighted scores based not just on the number of activities that fail a test but the total number of metrics that fail a test Individual Activity scores: based on the weighted results of all metrics being applied to the activity In order to calculate these activity scores, the relative weighting for each metric is required. Weightings can be viewed and edited by clicking on the respective metric library folder in the metric editor view. Weightings are based on a +/- 10 point sliding scale. The higher the weighting, the more impact the metric in question has on the scorecard score. By default, metric weightings have been set to the mid point in the weighting scale (i.e. +/- 5 depending on whether a high score is a positive or negative result). Newly created metrics inherit a neutral score until edited by the user. Weightings only apply to activity scores and not project/dataset scores.
56 | P a g e
57 | P a g e
As discussed in previous chapters, Acumen Fuse uses a combination of ribbons and metrics to run a project analysis. The Acumen Fuse engine is a powerful and flexible analytics engine that analyses projects in three dimensions:
Ribbon analysis is conducted against all activities within a given ribbon. It is typically the starting point for reporting in that it gives a high level overview of exceptions.
For a phase analysis, the Acumen Fuse engine calculates results across ribbons within a specific time slice or phase. This tends to be more complex than a ribbon analysis in light of the fact that activities may span across multiple phases. Figure 5-2 shows a simple sample project with three activities spanning over a four week period. When we analyze the data in Acumen Fuse (figure 5-3) and calculate two basic metrics, cost and schedule, we can see that the Acumen Fuse engine pro-rates both duration and cost based on how the activities span across the four periods. This makes phase-based analysis very powerful in that you can analyze both within and across defined phases accounting for the amount of cost, duration and work that falls into each phase.
58 | P a g e
Figure
5-3
Phase
Analysis
Intersection analysis only includes activities within a specific ribbon within a specific phase. Figure 5-4 shows an example of two activities in MS Project that overlap with respect to time.
Figure
5-4
Two
Activities
within
MS
Project
Figure 5-5 shows the same two activities within Acumen Fuse being analyzed using two metrics original duration and Total Cost. It can be seen that for each intersection, the assigned metric (Total Cost) is being calculated separately.
59 | P a g e
Details Metric analysis by ribbon enabling cross-ribbon comparisons to be drawn. Metric analysis by phase enabling cross-phase comparisons to be drawn. Trending can also be carried out. Metric analysis for a specific ribbon/phase intersection enabling pinpointing of project hot spots and problem areas.
60 | P a g e
This chapter focuses on the main view within Acumen Fuse - the Analysis View. The Analysis View is used to conduct an Acumen Fuse analysis. This view is extremely flexible and provides various modes of analysis that are discussed in this chapter.
Phases
Intersection Analysis
Ribbon Analyzer
Phase Analyzer
Activity Browser
A single workbook can contain multiple analysis views. For example, you may have a analysis view designed for cost analysis and a second analysis view for the same workbook setup for risk exposure analysis.
61 | P a g e
6.1.1 Ribbon Browser The ribbon browser is the core of the analysis view. Within the ribbon browser, you create ribbons, segment by phases and apply metrics. The ribbon browser is highly customizable. 6.1.1.1 Ribbons Ribbons are groupings of activities based on a given criteria. By default, ribbons are grouped by project but can be grouped in multiple ways including activity attribute, resource and path. If a workbook contains multiple projects, then a separate ribbon for each of these projects will be shown. Ribbons also contain activities. These activities can be hidden from within a ribbon if desired. Critical activities are shaded in red; non- critical in blue. Normal activities sit beneath summaries and milestones within a ribbon. Ribbons are segmented by phases. Ribbons can be sorted by metric results (by right clicking on the metric header and selecting the sort option). 6.1.1.2 Phases Phases are user definable segments of time against which the Acumen Fuse analysis is run. Phases can be weeks, days, months, quarters, years, custom periods or the entire project duration. 6.1.2 Phase Analyzer The phase analyzer shows the results from an Acumen Fuse analysis for each phase. Multiple metrics can be added to the phase analyzer. The phase analyzer can be displayed as either a table or a chart. 6.1.3 Ribbon Analyzer The ribbon analyzer shows the results from an Acumen Fuse analysis for each ribbon. Multiple metrics can be added to the ribbon analyzer. The ribbon analyzer can be displayed as either a table or a chart. 6.1.4 Intersection Analyzer In addition to running an analysis against a ribbon or phase, Acumen Fuse also enables metric reporting against a single segment within the ribbon browser (i.e. for a specific ribbon within a specific phase). 6.1.5 Activity Browser The Activity Browser shows individual activities. The activities shown depend on which segment of the ribbon or analyzer windows are clicked. There are six modes in which the Activity Browser can be used for reporting. These are described in detail later in this chapter.
Running an Acumen Fuse analysis is very straightforward. There are only two steps required: 62 | P a g e
63 | P a g e
Ribbons can be created using one of four techniques. In all four instances, the purpose of creating ribbons is to group project data in order to run a meaningful analysis. 6.4.1 Project/Snapshot Ribbons Project ribbons are the most simple types of Acumen Fuse ribbon. When the ribbon mode is set to Project/Snapshot, a separate ribbon is created for each project and/or snapshot within the workbook. In the case of a workbook containing a single project, a single ribbon is created. This is the default option when opening a analysis view. Project-based ribbons provide a means of running a high level Acumen Fuse analysis against a project or portfolio without drilling down into specific activities or sections of the project(s). Figure 6-4 shows an example workbook containing multiple projects each displayed as a separate Ribbon.
6.4.2 Field-Based
Ribbons
Field-based
ribbons
are
very
flexible
in
that
ribbons
can
be
defined
through
any
of
the
imported
activity
fields.
Common
examples
of
field-based
ribbons
include:
Critical
path-compare
analysis
results
between
critical
and
non
critical
activities.
Activity
type
differentiate
between
normal,
summary
and
milestone
activities
64 | P a g e
In
addition
to
basing
ribbons
by
field,
a
field-based
ribbon
can
be
further
defined
using
one
of
three
modes:
Discrete
a
separate
ribbon
is
created
for
each
field
value.
Interval
size
a
variable
number
of
ribbons
each
defined
by
a
user
selected
size
e.g.
cost
broken
out
into
multiple
ribbons
in
$50,000
intervals.
#
of
Intervals
a
fixed
number
of
ribbons
are
created
based
on
the
selected
number
of
intervals.
This
is
useful
if
creating
ribbons
by
a
field
that
returns,
for
example,
a
percentage.
Creating
ten
intervals
would
result
in
ten
ribbons
representing
0
10%,
10
20%,
20-30%
etc
all
the
way
to
90-100%.
Delimiter
-
Ribbons
are
created
based
on
period
delimiters.
This
is
useful
when
needing
to
create
ribbons
from
the
likes
of
a
WBS
or
a
hierarchical
code
field
that
uses
delimiters
to
designate
separation
of
sections
(and
level)
within
a
hierarchy.
6.4.3 Resource Ribbons Resource ribbons provide a rotated view of a project from the perspective resources. By creating a separate ribbon per resource, you are able to quickly see who is working on which activities and more importantly, when. Resource-ribbons are an excellent insight into cost/schedule performance.
66 | P a g e
6.4.4 WBS Based Ribbons WBS Ribbons provide a means of grouping activities by any given level of a project WBS. This is very useful for comparing the quality and performance across WBS elements of a project as well as being able to conduct a project rollup at any level.
6.4.5 Sorting Ribbons Ribbons can be sorted by metric results by right clicking on the metric header and selecting the sort option. This is an extremely useful technique for prioritizing results once a Fuse analysis has been conducted. 6.4.6 Filtering and Drilling Down through Ribbons Ribbons can also be used as a powerful means of filtering and drilling down into specific sections of an analysis. Any ribbon can be selected as a filter simply by double clicking on the ribbon heading. Executing this action causes Fuse to filter activities for that specific ribbon. Analysis and results only then pertain to the filtered data set. Further, hierarchies of filters can be created. Figure 6.7 shows an example whereby we have firstly ribbonized by location; filtered by a location called Domestic; further ribbonized by contractor; filtered by contractor ACom and then finally ribbonized by activity status.
67 | P a g e
Navigation back up through the created hierarchy is straightforward using the vertical navigation strip on the left hand side of the screen. Clicking on the home button takes you back to the unfiltered set of data.
Ribbons are segmented by phases. Each phase is analyzed separately in the phase analyzer. By default, Acumen Fuse will create a analysis view that encapsulates the entire project. Phase definition is fully customizable. The start and end of the analysis view can be defined either by a specific date or event (e.g. start of project or Time Now). Phase intervals can be set to days, weeks, months, quarters, years or single (representing the entire date range as a single phase). In addition, custom phases can be created through the use of the Add Phase menu item.
Phases can also be merged. For example, two adjacent quarters can be merged into a single half year segment. This is achieved by deleting a phase boundary. To do so, hover over the phase header until the delete icon appears. Click on this to remove the boundary and merge the two phases.
68 | P a g e
The entire analysis view can be reset to include all activities by clicking on the Reset Dates menu item.
By default, the Analysis View is automatically populated with multiple tabs containing separate views for each of the metric libraries. Each of these views can be edited with regards to adding/removing metrics to each of the three analyzers (ribbon, phase, intersection).
New tab
6.6.1 Adding a Metric to a Analysis View Metrics can be added to any of the three analyzer windows (ribbon, phase, intersection). To add a metric, click on the Metrics tab on the left hand side of the
69 | P a g e
analysis
view
to
reveal
the
list
of
metric
libraries
and
corresponding
metrics
within
each
library.
Right
click
on
the
required
metric
and
select
from
the
following
four
options:
Add
to
Ribbon
Analyzer
Add
to
Phase
Analyzer
Add
to
Intersection
Analyzer
Add
to
All
Analyzers
70 | P a g e
Adding Days Remaining metric to the analysis view Days Remaining Metric Added to all Three Analyzers
An
unlimited
number
of
metrics
can
be
added
to
the
ribbon
and
phase
analyzers.
Only
a
single
metric
at
a
time
can
be
viewed
in
the
intersection
analyzer.
6.6.2 Removing
Metrics
from
a
Analysis
View
Metrics
are
removed
from
the
ribbon
and
phase
analyzer
by
right
clicking
the
metric
title
and
clicking
on
the
delete
icon.
To
delete
the
currently
applied
intersection
metric,
hover
over
the
intersection
metric
title
in
the
top
left
hand
corner
of
the
view
and
click
on
the
delete
icon.
6.6.3 Adding
an
Entire
Metric
Library
to
an
Analyzer
As
well
as
adding
individual
metrics
to
a
analysis
view,
entire
metric
libraries
can
be
added
to
a
view
in
a
single
action.
The
process
is
similar
to
that
of
adding
individual
metrics:
right
click
on
the
desired
metric
library
and
choose
from
the
following
three
options:
Add
to
Ribbon
Analyzer
Add
to
Phase
Analyzer
Add
to
Ribbon
and
Phase
Analyzer
Because only one metric at a time can be viewed in the intersection analyzer, it is not possible to add a metric library to the intersection analyzer. Instead assign individual metrics as described above.
71 | P a g e
Once ribbons have been created, an Acumen Fuse analysis can be run. Each time a ribbon definition is changed or a metric added/removed, a new analysis needs to be run. Running an analysis is as easy as clicking the Fuse! menu button (or hitting F9 on the keyboard).
Once an analysis has been run, results can be viewed through the three main analyzer windows. These are used to report totals and numbers of exceptions to tripwire thresholds. To drill down further to determine individual activities causing the tripwires to trigger, use the Activity Browser. 6.8.1 Ribbon Analyzer The ribbon analyzer shows metric results for each individual ribbon. By default, the results are shown in a tabular format but can also be viewed as a chart.
6.8.2 Phase Analyzer The phase analyzer shows metric results for each individual phase. By default, the results are shown in a tabular format. The phase analyzer is useful for viewing trending information over time.
6.8.3 Intersection Analyzer The intersection analyzer is slightly different to that of the ribbon and phase analyzer in that only one metric at a time can be reported. However, in the same way as for ribbons and phases, results can be shown in both a tabular and graphical format. The intersection analysis is the most detailed of the three analyzers as it pinpoints exceptions within ribbons and phases combined.
6.8.4 Analyzer Chart Options When viewing any of the three analyzers in chart mode, the chart type can be modified by using the drop down menu on the chart button. In addition, charts can be set to cumulative and non-cumulative in the same drop down menu. When viewing analyzer results through the use of charts, the colors of the bars and lines relate to the tripwire threshold colors as defined for the metric in question. 73 | P a g e
The
Activity
Browser
is
used
to
report
specific
activities
based
on
a
given
criteria.
Activities
shown
in
the
Activity
Browser
can
originate
from
the
following:
Activities
irrespective
of
Tripwire
threshold
1. A
ribbon
(cutting
across
multiple
phases)
all
activities
for
a
given
ribbon.
2. A
phase
(cutting
across
multiple
ribbons)
all
activities
for
a
given
phase.
3. An
intersection
all
activities
for
a
given
ribbon
within
a
specific
phase.
Activities
that
trigger
a
given
tripwire
threshold
1. Ribbon
metric
results
activities
for
a
given
metric
segment
within
the
ribbon
analyzer.
2. Phase
metric
results
activities
for
a
given
metric
segment
within
the
phase
analyzer.
3. Intersection
metric
results
activities
for
a
given
metric
segment
within
the
intersection
analyzer.
In order to report activities irrespective of tripwire threshold, simply click on the ribbon or phase or intersection header. To report activities that make up the score in the analyzer cells, click on the cell in question. If a metric does not have a tripwire formula defined, the Activity Browser cannot be used to view activities.
74 | P a g e
Action
Analysis View
Shows those activities for the selected intersection that triggered the tripwire. Shows those activities for the selected ribbon that triggered the tripwire. Shows those activities for the selected phase across all ribbons that triggered the tripwire.
The Activity Browser can show activities in either a tabular format, a Gantt chart, scorecard or detailed view. Click on the Activity Browser View icons to toggle the view mode. A snapshot of the Activity Browser can also be displayed as a popup window. This is useful when reporting large quantities of data. Click on the popup icon to show the results in a separate window. Results from the Activity Browser can be printed in a tabular or scorecard report by clicking on the print icon. 75 | P a g e
Activities within the activity browser can be shown in five formats: Tabular Gantt Heat map Detailed Scorecard
6.9.1 Scorecard View within the Activity Browser In addition to viewing results in the Activity browser as either a Gantt or tabular view, you can also view them using a scorecard view. This gives the advantage of totaling metric scores directly within the analysis view.
76 | P a g e
6.9.2 Heat Map View Showing activities in the activity browser as a heat map is an extremely powerful visual aid with regards to reporting results. A heat map report uses relative box size and color to distinguish various attributes of activities. Any activity attribute can be used to define box size, color and grouping of heat maps charts. In addition, the number of activities shown in a heat map chart can be defined.
77 | P a g e
Figure 17d shows an example heat map with size of box showing duration, color showing Total Cost, grouped by Critical/Non Critical.
78 | P a g e
The analysis view provides a quick means of zooming in and out of phases. To zoom into a phase, hover over the phase header and click on the magnifying glass icon.
To zoom out of a phase, hover over the Timeline header and click on the magnifying glass icon to zoom out.
The Fuse analysis view can also be used to run a logic analysis. A logic analysis traces the path(s) of activities to and from a given activity. For example, all activity paths leading into a given milestone or instead all activities on the path from a project sanction milestone to the end of the project. Different variations of logic analysis can be conducted in Fuse: paths leading to an activity (trace backwards) paths leading from an activity (trace forwards) paths leading to and from an activity (trace backwards/forwards) paths between any two given activities. In addition to these four types of logic analysis, a further override known as Driving Logic can also be applied. When driving logic analysis is conducted, only those path(s) that are driving the schedule through to completion are shown. This is a very powerful means of pinpointing the key activities in a schedule. When a logic analysis is conducted, the Fuse analysis engine and resultant metric results only reflect those activities that are returned in the path analysis. Logic analysis is trigger either through the Logic menu or by using the three logic trace icons in the Activity Browser. Note: by default, the logic trace runs in driving logic Only mode. This can be changed to show all logic through the logic menu.
80 | P a g e
Figure 6-21 shows the three logic trace buttons in the activity browser that can be used as a fastrack means of running a logic trace. Simply select the activity in question and click on one of the three icons to trace forwards, backwards or in both directions.
Figure 6-22 shows an example of a Driving Logic analysis looking at all driving activities leading into and stemming from an activity called EPC Design. The activities in this path analysis are also shown in the ribbon browser and the results in the ribbon/phase analyzer are reflective of this driving path.
81 | P a g e
82 | P a g e
7 COMPARISON
ANALYZER
The
Comparison
Analyzer
is
a
powerful
analytical
feature
within
Acumen
Fuse.
The
Comparison
Analyzer
enables
you
to
compare
similarities
and
differences
between
two
scenarios.
The
power
of
this
capability
lies
in
the
fact
that
the
scenarios
that
get
compared
can
originate
from
multiple
origins
as
well
as
report
in
different
contexts:
Compare
the
same
metric
across
two
different
ribbons.
Compare
the
same
metric
across
two
different
time
periods
within
either
the
same
ribbon
or
even
between
different
ribbons.
Compare
two
different
metrics
within
the
same
ribbon
or
phase.
Compare
similarities-report
activities
that
havent
changed
between
two
scenarios.
Compare
differences-report
activities
that
have
changed
between
the
two
scenarios.
Upon
selecting
Scenario
B,
the
compare
analysis
will
automatically
run.
The
results
are
shown
in
a
popup
window
(see
figure
7-1).
*Note:
selecting
a
scenario
from
either
a
phase
or
ribbon
header
allows
you
to
select
activities
for
a
scenario
irrespective
of
whether
the
activities
trigger
a
metric
tripwire.
83 | P a g e
Within
the
Comparison
Analyzer
results
window,
there
are
three
filters
that
can
be
applied.
This
enables
you
to
do
further
analysis
comparing
similarities
and
differences
within
the
two
scenarios.
By
default,
all
three
filters
are
enabled
resulting
in
three
sets
of
data
to
be
shown:
Present
in
both:
shows
those
activities
that
are
present
in
both
scenarios.
In
the
case
of
comparing
two
scenarios
against
the
same
metric,
this
indicates
those
activities
that
trigger
a
metric
tripwire
in
both
instances-
i.e.
havent
changed
between
the
two
scenarios.
Only
present
in
scenario
A:
shows
those
activities
that
are
present
in
the
first
scenario
but
not
in
the
second.
In
the
case
of
comparing
two
scenarios
against
the
same
metric,
this
reports
those
activities
that
triggered
the
metric
tripwire
in
the
first
scenario
but
not
in
the
second.
Typically,
this
is
used
to
show
those
activities
that
were
an
issue
in
scenario
A
that
then
got
addressed
and
fixed
in
scenario
B.
Only
present
in
scenario
B:
shows
those
activities
that
are
present
in
the
second
scenario
but
not
in
the
first.
In
the
case
of
comparing
two
scenarios
against
the
same
metric,
this
reports
those
activities
that
triggered
the
metric
tripwire
in
the
second
scenario
but
not
in
the
first.
Typically,
this
is
used
to
show
those
activities
that
werent
an
issue
in
scenario
A
that
then
became
an
issue
in
scenario
B.
The
filters
are
cumulative
and
not
exclusive.
The
results
from
the
Comparison
Analyzer
can
be
printed
using
the
Print
menu
button
within
the
popup
window.
84 | P a g e
8 BENCHMARK
ANALYSIS
In
addition
to
calculating
metric
results
in
the
three
analyzer
windows,
Fuse
also
has
the
capability
to
benchmark
metric
scores
against
other
scores.
Benchmark
comparison
can
be
conducted
in
three
dimensions:
Compare
results
between
ribbons
Compare
results
between
phases
Compare
results
between
intersections
To
enable
benchmark
comparison,
enable
the
Show
Benchmark
Comparison
button
in
the
ribbon
View
menu.
Once
enabled,
click
on
any
of
the
analyzer
cells
to
run
a
comparison
with
the
selected
ribbon/phase/intersection
and
the
other
ribbons/phases/intersections.
Benchmark
comparison
results
are
shown
through
the
use
of
up/down
triangular
icons.
Red
shading
indicates
a
negative
comparison,
green
shading
indicates
a
positive
comparison
(for
the
respective
cell
in
question).
Figure
9.1
shows
an
example
of
benchmark
comparison
with
the
Houston
ribbon
being
the
selected
base
scenario
against
the
comparison
analysis
is
being
carried
out.
85 | P a g e
10 LOGIC
ANALYSIS
10.1 Overview
Fuse
logic
analysis
provides
multiple
advanced
logic
checks
on
a
project(s)
including:
Analysis
of
logic
types
Positive
and
negative
lags
(leads)
Redundant
logic
Circular
logic
Open
ends
Relationships
on
summaries
Out
of
sequence
status
updates
Reverse
Logic
Dangling
Activities
(Open
Start
and
Open
Finish)
This analysis pinpoints all relationship links that are carrying a lag. Negative lags (or leads) are especially of concern within a schedule as they can lead to reverse logic (see later). Likewise, positive lags often result in detail being lost within a schedule during statusing/execution.
The redundant logic analysis pinpoints redundant logic links within a schedule. This is a very valuable feature enabling you to generate and maintain clean schedules that dont contain redundant or overlapping logic. Consider the simple example of three activities, A, B and C, in sequence with FS logic links. In addition, if the schedule in question has a logic link between Activity A and C, then this link is essentially redundant as Activities A and C are already logically tied through Activity B. 86 | P a g e
To run a Fuse logic analysis, select the workbook, project or snapshot you want to run the analysis against (in the projects view) and then click on Logic Analyzer to run the logic analysis. Figure
Duplicated logic between Activity A and C (through B) Figure 10-3 Logic Analysis in Acumen Fuse
Circular logic analysis checks for paths of activities that loop back on themselves. This is especially of concern in multi-project environments (e.g. multiple Primavera files that reference each other) where circular logic checks can otherwise go undetected.
Open ends analysis checks for any activities that are missing either predecessors or successors causing the activity to be open ended.
87 | P a g e
While some scheduling tools allow logic links to be added to summary or WBS elements, it is generally accepted best practice to only logic tie normal activities together so as to retain the ability to re-sort/group activities without having to break the summary logic links. Out of sequence errors occur between activities when the successor activity status contradicts the logic with its predecessor. A simple example being a successor activity starting before its FS predecessor has started.
Reverse logic errors occur when the start of a successor activity starts before the start of the predecessor. Typically caused by negative lags (leads), these reverse logic errors should be avoided at all costs. Dangling activities occur when there are not actually any missing predecessors or successors but as a result of a FF or SF predecessor link (open start) or SS or SF successor link (open finish), the successor ends up with an open start and the predecessor ends up with an open finish.
A useful feature in the logic analysis module is the ability to sort and group results. Group results by dragging the column header above the table to create a grouped list of results. Click on a column header to sort.
All logic analysis results can be exported to Excel through the Publish to Excel icon.
88 | P a g e
11 FORENSIC
ANALYSIS
11.1 Overview
The
Acumen
Fuse
Forensic
Analyzer
provides
a
flexible
means
of
comparing
differences
and
pinpointing
changes
made
to
two
or
more
schedules,
cost
estimates
or
risk
models.
The
analysis
can
be
used
to
compare
updated
revisions
of
schedules
(e.g.
monthly
updates)
or
can
be
used
to
compare
differences
between,
for
example,
contractual
baseline
schedules
and
as-builts
during
dispute
resolution
or
lessons
learned
exercises.
You
can
even
compare
differences
(and
integrity)
between
the
same
schedule
developed
in
different
platforms
(e.g.
MS
Project
and
Primavera).
Example
analytics
include:
Added/removed
activities
Changed
activity
status
Modified
logic
links
Added/changed
constraints
Updated/changed
resources
and
resource
assignments
Updated
activity
costs
Updated
progress
and
Earned
Value
Changed
critical/longest
path
activities
An
unlimited
number
of
forensic
checks
can
be
run
in
the
analysis
including
changes
to
code
and
user
defined
fields.
You
can
add,
sort
and
group
results
and
then
seamlessly
publish
to
the
likes
of
pdf
and
MS
Excel.
Fuse
Forensic
analysis
can
be
used
for:
Ongoing
project
surveillance
Schedule
import/export
integrity
support
Contractor
performance
tracking
Claims
Avoidance/Evaluation
Expert
Witness
Testimony
A forensic analysis requires, at a minimum, two or more projects within a Fuse workbook. Additionally, one of the two projects must be designated as a snapshot against the primary project. Creating such a hierarchy is very simple: 1. Create a new Fuse workbook (File > New) 2. Add a primary project to the workbook (click one of the Get External Data icons) 89 | P a g e
3. Add a snapshot(s) to the primary project (select the primary project and then click one of the Get External Data icons to add a snapshot(s) to the parent primary project) 4. Import all data (click on the Import All button to complete the import) Figure 11.1 shows an example workbook containing a single primary project with two snapshot projects (last month and last year snapshots) assigned. This hierarchy will then provide the basis for running a forensic analysis. There is no limit to the number of snapshots than can be assigned to a parent project and subsequently analyzed using the forensic analyzer.
Once a forensic analysis workbook has been setup, you can run the analysis by selecting the Forensic tab in the main Fuse navigation ribbon.
The forensic analysis provides multiple criteria against which to analyze changes. The following insights are available: Project level changes e.g. changes to status, data dates, cost, duration Added/removed activities Added/removed/modified relationships Added/removed/modified resources Added/removed/modified resource assignments Unlimited number of added/removed/modified activity attributes (e.g. activity type, status, % complete, actual duration, remaining cost, risk etc) The results are shown in a tabular format, which can be modified (sorts, groupings and custom columns). Data can be sorted by clicking on the required field header Data can be grouped by drag-dropping the required grouping field from the table header to the top of the table to create a grouping Absolute and percentage variances are shown for each of the comparison snapshots (compared to the base schedule being compared against). Refer to section 11.4 for details regarding creating new forensic reports/criteria.
Acumen Fuse Forensic Analysis reports can be published to MS Excel by clicking on the Publish to Excel button in the projects tab.
Additional criteria (and columns) can be added to the Forensic analysis. This is achieved through the Fields tab in Fuse. To modify criteria and/or columns, either: Click on the Fields tab Click on the More button under the Activity Variances menu in the forensics tab
Figure 11.5 Selecting the Modify Fields option in the Forensic Report
Once in the fields view, use the two columns on the right hand side to customize the Forensic report (see figure 11.6): Compare in Forensic Report: creates a new Forensic view that compares differences between the snapshots for the given field 92 | P a g e
Show in Forensic Report: adds the selected column to all activity-based forensic reports (which can then be used for sorting and grouping)
Figure 11.7 Customizing Columns and Criteria for the Forensic Analyzer 93 | P a g e
Figure 11.7 shows an example of a newly added Forensic comparison (Percent Complete) with an additional column added (remaining cost). There is no limit to the number of additional comparisons and/or fields that can be added. Even custom fields and Code fields can be included in the Forensic analysis.
94 | P a g e
12 FUSE DASHBOARD
The Fuse dashboard provides an interactive overview of project(s) status; schedule quality, metrics, forensics and changes made over time. The dashboard can be run in the context of an entire workbook or a selected project (select a specific project from the project view). The dashboard comprises two types of customizable Widgets General Widgets o Project Status o Activity Status o Forensics o Logic Quality o Status Overview Fuse Analysis Widgets o Customizable widgets driven by the Fuse analysis metrics/views
All widgets within the dashboard can be directly copied to the clipboard using the copy icon in the top right corner of the view.
95 | P a g e
Results from a Fuse analysis created in the main analysis view can be incorporated into the dashboard through Fuse Widgets. Multiple Fuse Widgets can be added to a single dashboard. Fuse Widgets can be customized using the Configuration menu items in the dashboard menu, once a widget has been selected. Options include: View mode: group by ribbons or metrics and display in horizontal or vertical mode Auto Fit automatically fits the data within the Widget to fit the window, eliminating scrolling Copy copies the current Widget to the clipboard Font control of the font side within the Widget
96 | P a g e
13 REPORTING
Acumen Fuse can generate printable reports from within multiple areas: Activity Browser (MS Excel) Comparison Analyzer (MS Excel) Analysis View (MS Excel) Executive Briefing (MS Word and Adobe PDF) Analyst Report (native Fuse report, PDF) Logic analysis (MS Excel) Forensics Analysis (MS Excel) Dashboard (see previous chapter)
To print from the Activity Browser window: Select the required activities to display (See Activity Browser section in Chapter 6) Select tabular view (default mode) Optionally arrange, sort and group the columns Click the Print icon in the Activity Browser to print the report
Results from the comparison analyzer can be printed by clicking on the Print icon within the Comparison Analyzer window. 97 | P a g e
The main reporting capabilities lie within the Analysis View. All components of the analysis view listed below can be included in a MS Excel-based report: Ribbons Ribbon Analyzer Ribbon Analyzer Detail Phase Analyzer Phase Analyzer Detail Intersection Analyzer Detail All ribbon data can be published to MS Excel through the publish menu. This provides a means of publishing editable reports and data that can subsequently be used within other applications such as MS PowerPoint.
98 | P a g e
The executive briefing is one of the most powerful reports within Acumen Fuse. The executive briefing consolidates information and results generated from a Fuse analysis and presents them in a descriptive briefing without the need for manual interpretation of the data. The executive briefing consists three sections: Workbook: summary of the overall analysis including cost and schedule characteristics Project: project level summary including characteristics, status, areas of concern Ribbon: detailed analysis of each ribbon including trending An executive report can be created as either an editable MS Word document or a ready to publish Adobe PDF file. The executive briefing is generated from the publish menu icon in the ribbon view.
99 | P a g e
The analyst report is designed to be used as a checklist listing each of the individual activities that fail the various metric tests that have been applied to the view.
100 | P a g e
The Logic Analysis report includes a separate tab for each of the various Fuse logic analysis checks. Each exception (activity or logic link) is listed in the report.
101 | P a g e
The forensics analyst report published from Fuse gets generated as a MS Excel file. A separate tab for each forensic check is automatically created in the Excel workbook.
102 | P a g e
103 | P a g e
14 SCHEDULE CLEANSER
Acumen Fuse can not only analyze a schedule but can also be used to resolve and cleanse a schedule.
A schedule cleanse can be conducted on MS Project and Primavera P6 schedules within Fuse. To run a schedule cleanse, select the project to be cleansed and then click on the Cleanse Schedule button. Select the desired cleanse options and then click OK to create the newly cleansed scenario.
14.2 Scenarios
Rather than updating the source schedule file upon running a schedule cleanse, a scenario is created. A scenario is very similar to the previously described snapshot in Fuse. A scenario is a schedule created directly within Fuse. Scenarios can be compared to their respective parent projects using the forensic analyzer and Fuse analysis views.
Once a cleansed scenario has been created, it can be published back to the (MS Project or Primavera) format from which the original project originated. To publish, select the scenario in question and click on the Publish button to create a file that
104 | P a g e
can be imported back into the native scheduling tool. These files are scheduled/CPM time analyzed in Fuse before being published and so have updated early/late dates, float etc.
105 | P a g e
Acumen Fuse can analyze one or more projects within a single workbook. Through the use of Acumen Fuse Ribbons, you are able to carry out three main types of analysis as described below:
When a workbook contains a single project, Ribbons can be generated as a single project ribbon or grouped by field or by network path (see chapter 6). This mode of analysis provides a huge amount of slice and dice flexibility within a single project.
Single Project Shown as a Project Ribbon Single Project Shown Ribbonized by WBS
As described in Chapter 3, multiple snapshots of the same project can be included within a workbook so as to run comparisons against a given version of the same project. To run such an analysis, simply include the multiple snapshots of the project in a single workbook and then ribbonize by project. This will result in a separate ribbon being created for each of the snapshots. Metric analysis using all three analyzers can then be used in the normal way. Use the Ribbon and Intersection Analyzers to analyze the characteristics of the portfolio.
106 | P a g e
When comparing snapshots of the same project, the Comparison Analyzer is a useful tool for comparing metrics or phases between each of the snaphots e.g. compare September snapshot with October snapshot to determine if issues are being resolved.
In a similar manner in which multiple snapshots of the same project can be analyzed, multiple projects within a given program or portfolio can also be ribbonized. Import multiple projects (even from multiple platforms) into a single workbook and ribbonize by project. Use the Ribbon, Phase and Intersection Analyzers to analyze the characteristics of the portfolio. In addition, use the Comparison Analyzer to compare metric results across projects.
107 | P a g e
108 | P a g e
109 | P a g e
Fuse 360 is a goal-based optimization add-on module within the Fuse platform. It is used to accelerate or compress project schedules using an advanced optimization technique. It is a powerful decision support tool that automates an otherwise very lengthy manual schedule review process.
Fuse 360 runs a CPM simulation running hundreds of iterations progressively accelerating the project towards a defined goal using sets of user-definable criteria. Steps for Running a 360 Analysis Define your goal e.g. accelerate by 3 weeks Define your criteria for acceleration e.g. focus on engineering tasks Run the analysis Compare the results use forensics, timeline, analysis views
Defining a goal in Fuse 360 can be done in several ways: Define the number of days acceleration Define a target goal date Define a percentage acceleration Let Fuse 360 determine the best possible date possible 17.2.1 Project Goal To define a goal relative to the end of the project, use the Accelerate Schedule tab in the Fuse 360 window shown in figure 17.1. Use the goal options (date field or sliding scale) to set the target goal for the acceleration.
110 | P a g e
17.2.2 Activity Goal To define an acceleration goal for a specific activity, use the Accelerate Activity tab in the Fuse 360 window shown in figure 17.1. Select the activity against which the acceleration needs to be conducted (e.g. accelerate completion of construction) by using the activity selector. Use the goal options (date field or sliding scale) to set the target goal for the activity acceleration.
111 | P a g e
Fuse 360 automatically determines the appropriate level of granularity to apply during an analysis. This is calculated based on the complexity of logic, number of activities, remaining duration and aggressiveness of the acceleration. This can be manually overridden so that an even more accurate or alternately, a faster but less accurate model can be run. 112 | P a g e
Scripts can be exported from a Fuse workbook and re-used within other workbooks. Additionally, the default script can be set in the Fuse options window. Scripts can also be merged with other script libraries using the merge feature. 113 | P a g e
17.4.1 Defining Steps Define steps through the Steps Editor. Steps define how a schedule optimization is conducted. A step can define the following: Reduce duration Reduce predecessor lag Reduce successor lag Change calendar Remove constraints A step also defines the priority for applying the acceleration action. This can be defined as: Earliest earliest activities in the selection Latest latest activities in the selection Longest longest duration activities Easiest Fuse can use an advanced technique for determining the activities with the least amount of resistance during the acceleration simulation. 17.4.2 Defining Filters within Steps Filters are used to control which activities the steps get applied to. A single step can contain one or more filter sets. A single filter set can be a compound filter (AND statements). Multiple filters within a step enable an OR set of filters to be created. This provides a means of generating hybrid and hierarchical AND/OR filter sets. Define filters by clicking on the Create Filter Set icon and then define the field and associated value within the filter. The most common filter use is to create a filter by WBS. If selecting a WBS, then all activities within the selected WBS are included (i.e. the selected WBS is assumed to be the parent). Figure 17.5 shows an example of a filter that defines all activities within the WBS grouping called Commissioning where the contractor is ACom.
114 | P a g e
Steps are applied to a script by drag-dropping the steps from the step library into the script timeline. Steps within a script can be re-ordered by re-arranging the steps in the timeline. The timeline defines the order in which the steps are applied during the simulation.
115 | P a g e
Once an analysis has been run, opt to add the scenario; add the scenario and try another script; add the scenario and view the changes in forensics or add the scenario and compare in the Fuse analysis view.
Fuse 360 accelerated scenarios can be published to MS Project And Primavera using the publish button in the projects view.
117 | P a g e
Acumen
Fuse
includes
standard
field
mappings
for
each
of
the
supported
platforms.
These
are
listed
below.
Additional
custom
field
mappings
can
be
created
using
the
Fields
view.
Acumen
Field
ID
Description
Activity
Type
Critical
MS
Project
ID
Name
Calculated
Critical
Primavera
P6
Activity
ID
Activity
Name
Activity
Type
Critical
Primavera
Risk
Analysis
ID
Description
Task
Type
Critical
Deltek
Cobra
ID
Description
Calculated
NA
Open
Plan
Activity
ID
Activity
Desc.
Activity
Type
Critical_Activity
UN/CEFACT
ProjectScheduleTas k.Name
ProjectScheduleTas k.Description
ProjectScheduleTas k.TypeCode
ProjectScheduleTas k.CriticalPathIndicat or
TotalDurationMeas ure
ProjectScheduleTas k.RemainingDuratio nMeasure
ProjectScheduleTas k.CalculatedComple tionPercent
CurrentScheduledB asePeriod.Start
CurrentScheduledB asePeriod.Finish
ActualScheduledBas ePeriod.Start
ActualScheduledBas ePeriod.Finish
TargetScheduledBa sePeriod.Start
TargetScheduledBa sePeriod.Finish
EarliestScheduledB asePeriod.Start
NA NA
Percent Complete
% Complete
NA
Start Finish Actual Start Actual Finish Baseline Start Baseline Finish Early Start Early Finish
Start Finish Actual Start Actual Finish Baseline Start Baseline Finish Early Start
Start Finish Actual Start Actual Finish Planned Start Planned Finish Early Start
Start Finish Actual Start Actual Finish Baseline Start Baseline Finish Early Start
Start Calculated NA NA NA NA NA
Early Start Early Finish Actual Start Actual Finish Baseline Start Baseline Finish Early Start
Early Finish
Early Finish
Early Finish
NA
Early Finish
Total Float
Total Slack
Total Float
TotalFinshFloat
NA
Baseline Work Actual Cost Budget Cost Remaining Cost Total Cost Number of Predecessors Number of Successors
Baseline Work Actual Cost Baseline Cost Remaining Cost Cost Calculated Calculated
NA NA NA NA NA NA NA
118 | P a g e
Calculated
Number of FF Predecessors Number of SF Predecessors Number of SS Predecessors Number of Lags Number of Leads Project Start Project Finish Project Time Now Activity Status Activity Constraint WBS Code WBS Name
Calculated Calculated
Calculated Calculated
Calculated Calculated
NA NA
Calculated Calculated
Calculated Calculated
Calculated Calculated
Calculated Calculated
Calculated Calculated
NA NA
Calculated Calculated
Calculated Start Date Finish Date Status Date Status Constraint Type Outline Number
Calculated Start Finish Data Date Activity Status Primary Constraint WBS
Calculated Start Data Date Finish Calculated Constraint Type Work Breakdown Structure
NA NA NA NA NA NA WBS Code
Calculated Project Start Scheduled Finish Time Now Progress Type Calculated NA
Outline Number
ACWP (AC) BCWP (EV) BCWS (PV) EAC LIKELY CAM-EAC PLAN_ACC ETC MOD OTB REPLAN WORST Risk Input - Duration Description Risk Input - Duration LowerPcent Risk Input - Duration Max Risk Input - Duration Mean Risk Input - Duration Min Risk Input - Duration MostLikely Risk Input - Duration MostLikelyPcent Risk Input - Duration Notes Risk Input - Duration Risk Distribution Risk Input - Duration
Work Breakdown Structure Calculated NA NA NA NA NA NA NA NA NA NA Calculated Calculated Risk input- Duration Maximum Risk input- Duration Mean Risk input- Duration Minimum Risk Input - Duration MostLikely Calculated Risk Input - Duration Notes Calculated Calculated
WBS Name
NA
NA
ACWP (AC) BCWP (EV) BCWS (PV) EAC LIKELY CAM-EAC PLAN_ACC ETC MOD OTB REPLAN WORST NA NA NA NA
NA Calculated NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA
NA
NA
NA
NA
NA
NA NA
NA NA
NA NA
NA NA
NA NA
NA NA
NA NA
NA NA
NA
NA NA
119 | P a g e
NA
RiskFunction Risk Input - Duration RiskId Risk Input - Duration RiskOn Risk Input - Duration Shape Risk Input - Duration StdDeviation Risk Input - Duration UpperPcent Risk Input - Probabilistic Description Risk Input - Probabilistic Notes Risk Input - Probabilistic RiskFunction Risk Input - Probabilistic RiskId Risk Input - Probabilistic RiskOn Risk Input - Probabilistic Links Description Risk Input - Probabilistic Links Notes Risk Input - Probabilistic Links RiskFunction Risk Input - Probabilistic Links RiskId Risk Input - Probabilistic Links RiskOn Risk Input - Task Existence Description Risk Input - Task Existence Notes Risk Input - Task Existence RiskFunction Risk Input - Task Existence RiskId Risk Input - Task Existence RiskOn Risk Input - Task Existence Probability P50 Start P80 Finish P50 Finish P50 Cost P80 Cost Risk Output - CostSensitivity Risk Output - CostStdDeviation
NA NA NA NA NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA NA NA NA NA
Calculated Calculated Calculated Calculated Calculated Calculated Calculated Calculated Calculated Calculated Calculated Risk Input - Probabilistic Links Notes Calculated
NA NA NA NA NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA NA NA NA NA
NA
NA
NA
NA
NA
NA
NA
Calculated
NA
NA
NA
NA NA NA NA NA NA
NA NA NA NA NA NA
Calculated Calculated Risk Input - Task Existence Notes Risk Input - Task Existence Function Calculated Calculated
NA NA NA NA NA NA
NA NA NA NA NA NA
NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
Risk Input - Task Existence P50 Start P80 Finish P50 Finish P50 Cost P80 Cost Risk Output - CostSensitivity Risk Output - CostStdDeviation
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
120 | P a g e
NA
NA
NA
NA
NA
Risk Output - Duration Cruciality Risk Output - DurationStdDeviation Risk Output DurationSensitivity Risk Output MeanCost Risk Output MeanDuration Risk Output - MeanFinish Risk Output MeanStart Risk Output - PercentageTaskExisted Risk Output - ScheduleSensitivityIndex
NA
NA
NA
NA
NA NA NA NA NA
NA NA NA NA NA
NA NA
NA NA
Risk Output - Duration Cruciality Risk Output - DurationStdDeviati on Risk Output DurationSensitivity Risk Output MeanCost Risk Output MeanDuration Risk Output - MeanFinish Risk Output MeanStart Risk Output - % Iterations Existed Risk Output - ScheduleSensitivityI ndex
NA
NA
NA
NA
NA
NA
NA NA NA NA NA
NA NA NA NA NA
NA NA NA NA NA
NA NA
NA NA
NA NA
121 | P a g e
19 SYSTEM
REQUIREMENTS
Acumen
Fuse
is
a
Windows
application.
It
requires
no
backend
database
installation.
System
requirements
as
follows:-
Windows
XP
SP2,
Windows
Vista,
Windows
7
(32
and
64
bit
versions
supported)
MS
.net
runtime
version
4.0
(included
as
part
of
Acumen
Fuse
installer)
Minimum
1GB
RAM,
recommended
2GB
RAM
Hard
drive
space
required:
80MB
122 | P a g e
20 INSTALLATION
Acumen Fuse is installed from an on-line virtual DVD. The Acumen Fuse installer uses Microsoft ClickOnce technology which provides a seamless means of installing and maintaining updates to Acumen Fuse without the need for complex and often prohibitive administrative rights to your computer. To install Acumen Fuse, simply point your web browser to http://projectacumen.com and navigate to the install page. Upon installation, you will be asked to review the license agreement. Upon acceptance, you will be prompted for a valid Acumen Fuse license key. Upon successful validation, you will be ready to run Acumen Fuse. Acumen Fuse includes sample files and documentation. These can be found in the Acumen Fuse folder within your Documents folder on your PC.
123 | P a g e
21 AUTOMATIC
UPDATES
Fuse
checks
for
both
required
and
recommended
updates
each
time
the
application
runs.
Using
ClickOnce,
this
is
a
quick
and
easy
means
of
ensuring
you
have
the
latest
compatible
version
of
Fuse
installed.
An
internet
connection
is
required
in
order
to
receive
these
updates.
Automatic
updates
can
be
disabled
in
the
Options
menu
of
Fuse.
124 | P a g e