Deltek Acumen

Deltek l Acumen
Software
User Manual V5.0
10/1/13
Table of Contents
1 Overview of the Deltek Acumen Software Suite .............................................................................................. 10
1.1 Whats Included.............................................................................................................................................. 10
1.2 Navigating through the Deltek Acumen Software Suite ................................................................................. 10
1.2.1 The S1 // Projects Tab ............................................................................................................................. 11
1.2.2 The S2 // Diagnostics Tab ....................................................................................................................... 12
1.2.3 The S2 // Logic Tab ................................................................................................................................. 14
1.2.4 The S2 // Benchmarking Tab................................................................................................................... 14
1.2.5 The S3 // Risk Tab ................................................................................................................................... 15
1.2.6 The S4 // Acceleration Tab ...................................................................................................................... 15
1.2.7 The S5 // Dashboard Tab ........................................................................................................................ 16
1.2.8 The Forensics Tab .................................................................................................................................. 17
1.2.9 The Metrics Tab ...................................................................................................................................... 17
1.2.10 The Fields Tab ...................................................................................................................................... 18
1.3 Integrating With Project Management Platforms ........................................................................................... 19
2 Working With Deltek Acumen Workbooks ....................................................................................................... 20
2.1 Workbook File Formats .................................................................................................................................. 20
2.1.1 Standard File Format............................................................................................................................... 20
2.1.2 XML File Format ...................................................................................................................................... 20
2.2 Creating a New Workbook ............................................................................................................................. 20
2.2.1 Metrics within a Workbook ...................................................................................................................... 20
2.3 Linking and Importing Projects....................................................................................................................... 21
2.3.1 MS Project 2003/2007/2010 .................................................................................................................... 21
2.3.2 Oracle Primavera P6 (V5/6/7/R8) ........................................................................................................... 21
2.3.3 Primavera P3 ........................................................................................................................................... 22
2.3.4 Oracle Primavera Risk Analysis (formerly known as Pertmaster) .......................................................... 22
2.3.5 Deltek Open Plan .................................................................................................................................. 22

2.3.6 Asta PowerProject ................................................................................................................................... 23
2.3.7 UN/CEFACT XML Schedule Files ........................................................................................................... 23
2.3.8 Deltek Cobra CAP Earned Value Data .................................................................................................. 23

2.3.9 MS Excel ................................................................................................................................................. 23
2.3.10 ARES PRISM G2 .................................................................................................................................. 24
2.3.11 Phoenix Project Manager ...................................................................................................................... 24
2.4 Link Types ...................................................................................................................................................... 24
2.4.1 Project Links ............................................................................................................................................ 24
2.4.2 Snapshot Links ........................................................................................................................................ 24
2.4.3 Adding a Baseline to Primavera P6 Workbooks ..................................................................................... 25
Deltek Acumen Software User Guide V5.0 | Deltek 2013, All Rights Reserved 2
2.4.4 Merging Multiple Data Sources into a Single Dataset (e.g., cost and schedule) .................................... 26
2.5 Importing Project Data ................................................................................................................................... 28
2.5.1 Filtering Project Data During an Import ................................................................................................... 29
2.6 Including/Excluding Projects from Analysis ................................................................................................... 29
2.7 Setting Display Units ...................................................................................................................................... 30
3 S1 // PROJECTS: Viewing and Editing the Schedule ...................................................................................... 31
3.1 Activity View ................................................................................................................................................... 31
3.1.1 Activity Grouping ..................................................................................................................................... 31
3.1.2 Add/Remove Columns ............................................................................................................................ 32
3.2 Smart Gantt ................................................................................................................................................ 33
3.2.1 Top Bar vs. Bottom Bar ........................................................................................................................... 34
3.2.2 Smart Gantt Dates ................................................................................................................................... 34
3.2.3 Smart Gantt Colors .................................................................................................................................. 35
3.2.4 Additional Smart Gantt Options ............................................................................................................... 36
3.3 Filtering Activities ........................................................................................................................................... 37
3.3.1 Create a Filter Using Metrics ................................................................................................................... 37
3.3.2 Create a Filter Using Forensics ............................................................................................................... 37
3.4 The Timeline View.......................................................................................................................................... 38
3.5 Editing the Schedule ...................................................................................................................................... 39
3.5.1 Modifying the Schedule ........................................................................................................................... 39
3.6 Create a new Cost Estimate .......................................................................................................................... 40
3.6.1 Add New Activities ................................................................................................................................... 41
3.6.2 Organizing Activities into a Hierarchy or Cost Breakdown Structure ...................................................... 41
4 Introducing Deltek Acumen Fuse .................................................................................................................... 43

4.1 Types of Analysis ........................................................................................................................................... 43
4.1.1 Single Project Analysis ............................................................................................................................ 43
4.1.2 Snapshot Comparison-Trending of a Project over Time ......................................................................... 43
4.1.3 Multi-Project/Portfolio Analysis ................................................................................................................ 43
4.2 Introducing Ribbons ....................................................................................................................................... 44
4.3 Introducing Metrics ......................................................................................................................................... 45
4.4 Deltek Acumen Fuse Analysis ....................................................................................................................... 46
4.5 The Deltek Acumen Fuse Engine .................................................................................................................. 47
4.5.1 Ribbon Analysis ....................................................................................................................................... 47
4.5.2 Phase Analysis ........................................................................................................................................ 47
4.5.3 Intersection Analysis ............................................................................................................................... 48
4.5.4 Trend Analysis ......................................................................................................................................... 49
5 S2 // DIAGNOSTICS: Schedule Analysis .......................................................................................................... 51
5.1 Navigation ...................................................................................................................................................... 51

5.2 Running a Deltek Acumen Fuse Analysis ...................................................................................................... 52
5.2.1 Populate your workbook with project data .............................................................................................. 52
5.2.2 Run Acumen Fuse Analysis .................................................................................................................... 52
5.3 Grouping Activities: Ribbons .......................................................................................................................... 53
5.3.1 Project/Snapshot Ribbons ....................................................................................................................... 53
5.3.2 Field-Based Ribbons ............................................................................................................................... 54
5.3.3 Resource Ribbons ................................................................................................................................... 55
5.3.4 WBS Based Ribbons ............................................................................................................................... 55
5.3.5 Sorting Ribbons ....................................................................................................................................... 56
5.3.6 Filtering and Drilling Down through Ribbons ........................................................................................... 56
5.4 Defining Date Ranges & Phases ................................................................................................................... 56
5.5 Applying Metrics ............................................................................................................................................. 57
5.5.1 Adding a Metric to an Analysis View ....................................................................................................... 58
5.5.2 Removing Metrics from an Analysis View ............................................................................................... 59
5.5.3 Adding an Entire Metric Library to an Analyzer ....................................................................................... 60
5.5.4 Adding New Metric Views........................................................................................................................ 60
5.6 Viewing & Interpreting Results through Analyzer Windows ........................................................................... 61
5.6.1 Ribbon Analyzer ...................................................................................................................................... 61
5.6.2 Phase Analyzer ....................................................................................................................................... 61
5.6.3 Intersection Analyzer ............................................................................................................................... 61
5.6.4 Analyzer Chart Options ........................................................................................................................... 62
5.7 Using the Activity Browser ............................................................................................................................. 62
5.7.1 Activity Browser View Options................................................................................................................. 63
5.7.2 Scorecard View within the Activity Browser ............................................................................................ 64
5.7.3 Heat Map View ........................................................................................................................................ 65
5.7.4 Activity Browser Printing .......................................................................................................................... 66
5.8 Smart-Filtering of Ribbons ............................................................................................................................. 67
5.9 Zooming in/out of Phases .............................................................................................................................. 67
5.10 Analysis Justification & Exclusions .............................................................................................................. 68
5.10.1 Exclude Activities From the Analysis .................................................................................................... 68
5.11 Adding Annotations to activities ................................................................................................................... 68
6 Deltek Acumen Fuse Driving Logic Analysis .................................................................................................. 70
7 Deltek Acumen Fuse Comparison Analysis .................................................................................................... 72
7.1 Running a Comparison Analysis .................................................................................................................... 72
7.2 Comparison Analyzer Printing ....................................................................................................................... 73
8 Deltek Acumen Fuse Metric Benchmarking .................................................................................................... 74
9 Managing Metrics ............................................................................................................................................... 75

9.1 The Building Blocks of Acumen Fuse Metrics ............................................................................................... 75
9.1.1 Primary Formula ...................................................................................................................................... 75
9.1.2 Secondary Formula ................................................................................................................................. 75
9.1.3 Tripwire Formula ..................................................................................................................................... 75
9.1.4 Tripwire Threshold ................................................................................................................................... 75
9.2 Metric Definition ............................................................................................................................................. 75
9.3 Writing Metric Formulas ................................................................................................................................. 76
9.3.1 Array Formula Types ............................................................................................................................... 76
9.3.2 Developing Primary Formulas ................................................................................................................. 77
9.3.3 Developing Secondary Formulas ............................................................................................................ 78
9.4 Tripwires ......................................................................................................................................................... 78
9.4.1 Tripwire Formulas .................................................................................................................................... 78
9.4.2 Tripwire Thresholds ................................................................................................................................. 79
9.4.3 Defining Tripwire Threshold Scales ........................................................................................................ 79
9.4.4 Normal and Gradient Scales ................................................................................................................... 80
9.4.5 Including/Excluding Metrics from Analysis .............................................................................................. 80
9.5 Testing Metric Formulas ................................................................................................................................ 80
9.6 Commonly Used Functions ............................................................................................................................ 80
9.6.1 IF Function............................................................................................................................................... 81
9.6.2 SUM Function .......................................................................................................................................... 81
9.6.3 AND Function .......................................................................................................................................... 81
9.6.4 MAX Function .......................................................................................................................................... 82
9.6.5 AVERAGE Function ................................................................................................................................ 82
9.6.6 COUNTIF Function .................................................................................................................................. 82
9.7 Types of Acumen Fuse Fields ....................................................................................................................... 82
9.7.1 Activity Fields .......................................................................................................................................... 82
9.7.2 Project Fields ........................................................................................................................................... 82
9.7.3 Workbook Fields ...................................................................................................................................... 83
9.7.4 Dynamic Fields ........................................................................................................................................ 83
9.8 Templated Metric Libraries ............................................................................................................................ 83
9.8.1 Saving a Metric Library as a Template .................................................................................................... 83
9.8.2 Reusing a Metric Library Template ......................................................................................................... 84
9.8.3 Setting a Custom Metric Library as the Default Library .......................................................................... 84
9.9 Managing Metrics and Metric Libraries .......................................................................................................... 85
9.10 Metric Weightings for Scorecards ................................................................................................................ 85
9.11 Metrics Using Variables ............................................................................................................................... 86
9.11.1 Defining Variables ................................................................................................................................. 86

9.11.2 Referencing Variables when Defining Metrics ...................................................................................... 87
9.11.3 Running a Fuse Analysis using Variables ............................................................................................. 87
9.11.4 Defining Variable Fields ........................................................................................................................ 89
9.11.5 Referencing Variable Fields when Defining Metrics ............................................................................. 89
9.11.6 Working with Both Variable Fields and Variable Values ....................................................................... 91
10 Reporting Diagnostics Results ....................................................................................................................... 95
10.1 Executive Briefing ........................................................................................................................................ 95
10.2 Analyst Report.............................................................................................................................................. 96
11 S2 // LOGIC: Logic Analysis ............................................................................................................................ 97
11.1 Overview ...................................................................................................................................................... 97
11.2 Positive and Negative Leads and Lags ....................................................................................................... 97
11.3 Redundant Logic .......................................................................................................................................... 97
11.4 Logic Sensitivity ........................................................................................................................................... 98
11.5 Additional Logic Checks ............................................................................................................................... 99
11.5.1 Circular Logic ........................................................................................................................................ 99
11.5.2 Open Ends ............................................................................................................................................ 99
11.5.3 Relationships on Summaries................................................................................................................. 99
11.5.4 Out of Sequence Updates ..................................................................................................................... 99
11.5.5 Reverse Logic ....................................................................................................................................... 99
11.5.6 Dangling Activities (Open Start and Open Finish) ................................................................................ 99
11.6 Sorting and Grouping Logic Analysis Results .............................................................................................. 99
11.7 Logic Analysis Report ................................................................................................................................ 100
12 FORENSICS: Identifying Additions, Deletions and Modifications ............................................................ 101
12.1 Overview .................................................................................................................................................... 101
12.2 Setting up a Forensic Analysis................................................................................................................... 101
12.3 Running a Forensic Analysis ..................................................................................................................... 102
12.3.1 Calendar Definition Forensics ............................................................................................................. 104
12.4 Modifying Reporting Criteria ...................................................................................................................... 104
12.5 Forensics Analysis Report ......................................................................................................................... 106
13 S5 // DASHBOARD: Reporting Results ........................................................................................................ 108
13.1 Diagnostics Widgets .................................................................................................................................. 108
14 Schedule Cleanser ...................................................................................................................................... 110
14.1 Running a Schedule Cleanse .................................................................................................................... 110
14.2 Scenarios ................................................................................................................................................... 110
14.3 Publishing a Scenario to MS Project and Primavera ................................................................................. 110
15 The Acumen Application Programming Interface (API) ............................................................................. 111
16 S3 // RISK: Project Risk Analysis .................................................................................................................. 112

16.1 Introducing Deltek Acumen Risk ............................................................................................................ 112
16.2 Starting with Acumen Risk ......................................................................................................................... 112
16.2.1 Importing Cost/Schedule Data into Acumen Risk ............................................................................... 112
16.2.2 Updating an Existing Risk Model with a Modified Schedule ............................................................... 112
16.2.3 Navigating the Risk View..................................................................................................................... 112
17 Risk Inputs ...................................................................................................................................................... 113
17.1 Uncertainty ................................................................................................................................................. 113
17.1.1 Uncertainty Factor Template ........................................................................................................... 113
17.1.2 Setting the Uncertainty Loading Level ................................................................................................ 114
17.1.3 Assigning Uncertainty .......................................................................................................................... 114
17.2 Distribution Types ...................................................................................................................................... 115
17.3 The Risk Adviser .................................................................................................................................... 116
17.4 Modeling Task Existence ........................................................................................................................... 117
17.5 Activity Correlation ..................................................................................................................................... 117
17.6 Viewing Uncertainty Distributions .............................................................................................................. 118
18 Risk Register ................................................................................................................................................... 120
18.1 Defining the Risk Matrix ............................................................................................................................. 120
18.2 Creating Risk Events ................................................................................................................................. 121
18.2.1 Risk Event Types ................................................................................................................................ 121
18.3 Mitigation .................................................................................................................................................... 122
18.4 Mapping Risk Events to Activities .............................................................................................................. 122
18.4.1 Manually mapping a risk to multiple activities ..................................................................................... 122
18.4.2 Manually mapping an activity to multiple risks .................................................................................... 123
18.5 Importing Risk Registers ............................................................................................................................ 124
19 Running A Risk Analysis ............................................................................................................................... 125
19.1 Simulation Options ..................................................................................................................................... 125
19.2 Simulation Scenarios ................................................................................................................................. 125
19.3 Interaction .................................................................................................................................................. 126
19.4 Repeatability .............................................................................................................................................. 126
19.4.1 Cost/Schedule Integration ................................................................................................................... 126
20 Risk Reporting ................................................................................................................................................ 127
20.1 Reporting Risk Exposure (Risk Histogram) ............................................................................................... 127
20.1.1 Reporting Cost, Duration, Float, Start, Finish Date Risk Exposure .................................................... 127
20.2 Reporting Risk Drivers (Risk Tornado) ...................................................................................................... 128
20.2.1 Reporting Criticality ............................................................................................................................. 128
20.2.2 Reporting Schedule & Cost Contribution ......................................................................................... 128
20.2.3 Risk Drivers Report Configuration ....................................................................................................... 129

20.2.4 Setting the Display Level ..................................................................................................................... 130
20.2.5 Reporting Risk Event Drivers .............................................................................................................. 131
20.2.6 Publishing/Printing Results.................................................................................................................. 131
20.3 Risk Sensitivity ....................................................................................................................................... 131
20.3.1 Configuration ....................................................................................................................................... 131
20.3.2 Deterministic Value ............................................................................................................................. 131
20.3.3 Quadrants ............................................................................................................................................ 131
20.3.4 Joint Confidence Level (JCL) .............................................................................................................. 132
20.4 Risk Comparison (Comparing Results) ..................................................................................................... 133
20.4.1 Adding Scenarios ................................................................................................................................ 133
20.4.2 Risk Comparison Reporting ................................................................................................................ 133
20.4.3 Publishing/Printing Results.................................................................................................................. 134
21 Cost Risk Analysis ......................................................................................................................................... 135
21.1 Create a new Cost Estimate ...................................................................................................................... 135
21.1.1 Add New Activities ............................................................................................................................... 135
21.1.2 Organizing Activities into a Hierarchy or Cost Breakdown Structure .................................................. 135
21.2 Importing an Existing Cost Estimate .......................................................................................................... 136
21.3 Linking Cost & Schedule Risk Models ....................................................................................................... 137
22 Building A Risk Adjusted Schedule.............................................................................................................. 139
22.1.1 Scenario based on Risk Inputs ........................................................................................................... 139
22.1.2 Scenario based on Risk Outputs ......................................................................................................... 139
23 Analyzing Risk Results .................................................................................................................................. 140
23.1 Forensics .................................................................................................................................................... 140
23.2 Diagnostics & Risk Metrics in Deltek Acumen Fuse .................................................................................. 140
24 S4 // ACCELERATION: Deltek Acumen 360 .............................................................................................. 142
24.1 How does Deltek Acumen 360 Work? ....................................................................................................... 142
24.2 Automatic Goal Based Acceleration .......................................................................................................... 142
24.2.1 Defining a Goal .................................................................................................................................... 142
24.2.2 Advanced Acceleration Settings ......................................................................................................... 144
24.3 Targeted Acceleration ................................................................................................................................ 145
24.3.1 Defining Criteria Sets (Scripts) ............................................................................................................ 145
24.3.2 Defining Steps ..................................................................................................................................... 146
24.3.3 Defining Filters within Steps ................................................................................................................ 146
24.3.4 Working with Script Templates ............................................................................................................ 146
24.4 Interactive Acceleration .............................................................................................................................. 148
24.4.1 Calibration Overview ........................................................................................................................... 148
24.4.2 Manipulating the Schedule with Calibration ........................................................................................ 148

24.5 The Schedule Realism Adviser .............................................................................................................. 149
24.6 Analyzing the Results ................................................................................................................................ 150
24.7 Publishing Scenarios ................................................................................................................................. 150
25 S2 // BENCHMARKING: Project Scoring and Ranking................................................................................ 151
25.1 Deltek Acumen Cloud Overview............................................................................................................. 151
25.2 Project Benchmarking ................................................................................................................................ 151
25.3 Scoring, Benchmarking & Forecasting ...................................................................................................... 152
25.4 Fuse Schedule Index .............................................................................................................................. 153
25.5 Fuse Logic Index .................................................................................................................................... 154
25.6 Metric Percentile Analysis .......................................................................................................................... 155
25.7 Points of Note............................................................................................................................................. 156
26 Custom Field Mappings ................................................................................................................................. 157
26.1 Introducing Field Mapping .......................................................................................................................... 157
26.2 Editing Field Mappings ............................................................................................................................... 158
26.3 Editing Field Names ................................................................................................................................... 158
26.4 Deleting Fields ........................................................................................................................................... 158
26.5 Deleting Field Mappings ............................................................................................................................ 158
26.6 Minimum Fields Required .......................................................................................................................... 159
26.7 Working with Field Types ........................................................................................................................... 159
26.8 Field Mapping............................................................................................................................................. 159
26.8.1 Mapping a Field to Multiple Data Sources .......................................................................................... 159
26.8.2 Map all Code Fields for this Project .................................................................................................... 159
26.8.3 Map all Code Fields for all Projects ..................................................................................................... 159
26.8.4 Map all User fields for All Projects ...................................................................................................... 160
26.8.5 Load Default Mapping ......................................................................................................................... 160
26.8.6 Field Mapping Context ........................................................................................................................ 160
26.8.7 Mapped Fields and Metrics ................................................................................................................. 160
26.9 Standard Field Mappings ........................................................................................................................... 160
27 System Requirements .................................................................................................................................... 165
28 Installation ....................................................................................................................................................... 166
29 Automatic Updates ......................................................................................................................................... 167
1 Overview of the Deltek Acumen Software Suite

The Deltek Acumen software suite consists of three products, Deltek Acumen Fuse, Deltek Acumen Risk, and
Deltek Acumen 360 which seamlessly work together to provide the analytics and insight necessary for sound
scheduling and successful project execution.
1.1 Whats Included

Each product contains unique features and benefits.
Deltek
Acumen
Fuse
Deltek
Acumen
Risk
Deltek
Acumen
360
Full
Software
Suite
Integration with all major planning tools
Schedule diagnostics
DCMA 14 Point Assessment
Schedule Quality Analysis
Logic Analysis
Project Benchmarking
Schedule Cleansing
Schedule Risk Analysis
Cost Risk Analysis
Forensic Analysis/Schedule Comparison
Dashboard Reporting
Schedule Acceleration
Schedule Deceleration
Customizable Metrics
Customizable Reports
1.2 Navigating through the Deltek Acumen Software Suite

Navigate throughout the product suite using the S1 to S5 tabs at the top of the software. Each tab relates to a
1
particular level of the Deltek Acumen schedule maturity framework . The tabs are as follows:
S1 // Projects: Used to create and maintain project workbooks. Use this tab to import, view and edit
project data. Available in all three Deltek Acumen products.
S2 // Diagnostics: Schedule analysis using metrics. Only available in Deltek Acumen Fuse.
The Deltek Acumen schedule maturity framework is a series of 5 stages that result in a validated, risk-adjusted,
and team-approved schedule. Learn more at: http://www.projectacumen.com/resource/improving-project-plansusing-a-schedule-maturity-framework/
S2 // Logic: Advanced logic checks. Available in Deltek Acumen Fuse
S2 // Benchmarking: Comparison of project data to cloud-based database of similar projects. Available

in Deltek Acumen Fuse.
S3 // Risk: Monte-Carlo risk analysis, risk register and reporting. Only available in Deltek Acumen Risk.
S4// Acceleration: Define acceleration goals and criteria. Available in Deltek Acumen 360.
S5 // Dashboard: Reporting dashboard. Available in all three Deltek Acumen products.
Forensics: Compare multiple snapshots or historical instances of a project(s). Available in all three
Deltek Acumen products.
Metrics: The metric editor for maintaining custom metrics. Available in Deltek Acumen Fuse.
Fields: View for defining custom field mappings when importing project data. Available in all three Deltek
Acumen products.
Navigation between these tabs is carried out through the Ribbon Navigation Menu Bar (Figure 1-1).
Figure 1-1 Navigation through the menu bar
File management (File New, Open, Close, Save, Save as, Print and Options) is navigated to by clicking on the
icon in the top left hand corner of the ribbon menu bar (Figure 1-2).
Figure 1-2 File Management Menu
1.2.1 The S1 // Projects Tab

The projects view is used to manage the contents of Acumen workbooks. Workbooks are containers for storing
project data. Project data can come from multiple sources and platforms and can be a combination of cost,
schedule, risk or any other type of project management data that is to be analyzed.
Workbook
Project
Snapshots
Imported
project data
Figure 1-3 The Projects View
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.
1.2.2 The S2 // Diagnostics Tab

The Diagnostics tab is used to identify schedule shortcomings and gain insight into project quality through
metrics.
The main view consists of four panels:
Ribbon Browser: flattened project data showing ribbons, activities and phases
Ribbon analyzer: graphical/tabular view of analysis results for each ribbon
Phase analyzer: graphical/tabular view of analysis results for each phase
Activity Browser: tabular/Gantt/scorecard/heat map chart view of activities/results
Intersection
Analysis
Phases
Ribbons
Ribbon
Analyzer
Ribbon
Browser
Metrics
Figure 1-4 The S2 // Diagnostics Tab
Activity
Browser
Phase
Analyzer
A single workbook can contain multiple analysis views. For example, you may have an analysis view designed for
cost analysis and a second analysis view for risk exposure analysis in the same workbook.
Ribbon Browser
The ribbon browser is the core of the diagnostics tab. Within the ribbon browser, you create ribbons, segment by
phases and apply metrics. The ribbon browser is highly customizable.
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.
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.
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.
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.
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).
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 5.
1.2.3 The S2 // Logic Tab

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.
Figure 1-5 The Logic Analysis View
1.2.4 The S2 // Benchmarking Tab

The benchmarking view provides a means of comparing project analytics against a global database of similar
projects. This view reports the Fuse Schedule Index of a given project, how this score compares to other
projects, and what the likelihood of an on time, on-budget project completion is.
Figure 1-6 S2 // Benchmarking Tab
1.2.5 The S3 // Risk Tab

This view is where Monte Carlo risk analysis is performed on an imported schedule or cost estimate. Report risk
exposure, risk drivers and track risk events all on this view.
Figure 1-7 S3 // Risk Tab
1.2.6 The S4 // Acceleration Tab

The acceleration tab provides options for creating acceleration scripts.
Figure 1-8 S4 // Acceleration Tab
1.2.7 The S5 // Dashboard Tab

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.
Figure 1-9 The Dashboard View
1.2.8 The Forensics Tab

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.
Figure 1-10 The Forensics View
1.2.9 The Metrics Tab

The metrics view is used to manage metrics, including the editing of existing and creation of new metrics.
Metric
Libraries
Metrics
Filters
Advanced
Formula
Figure 1-11 The Metrics View
Metrics contain four properties:

Primary formula
Secondary Formula
Tripwire Formula
Tripwire Threshold
The three formula properties use a combination of user-friendly filters and optional advanced MS Excel-type
formulas where needed.
Primary formula
The primary formula is the formula used to calculate the primary result calculated in an Acumen Fuse analysis.
Secondary formula
The secondary formula is the corresponding formula associated with the primary formula often used to represent
the primary formula as a percentage.
Tripwire formula
The tripwire formula is used to determine the individual exceptions that are listed in the Activity Browser.
Tripwire Threshold
The threshold editor enables customizable thresholds to be defined and associated colors set.
1.2.10 The Fields Tab

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 the supported platforms are
included.
Selected
Source
Mapped
Source
Fields
Source
Fields
Fuse Fields
Figure 1-12 The Fields View
1.3 Integrating With Project Management Platforms

Acumen integrates with multiple project management platforms. Each Acumen workbook can contain projects
from any of the following platforms:
MS Project 2003/2007/2010, MS Project Server 2007 and above
Primavera P6 (versions 5.x, 6.x, 7.x and R8)
Primavera P3
Oracle Pertmaster/Risk Analysis V8.x
Asta PowerProject
UN/CEFACT XML
Deltek Open Plan V3.x
Deltek Cobra (Earned Value)
Deltek Risk+
ARES PRISM G2
Phoenix Project Manager
In addition, Acumen provides flexible customizable integration with MS Excel. The Excel integration enables you
to import data in almost any format from an Excel spreadsheet.
Figure 1-13 Supported Platforms
Data from any discipline (cost, schedule, risk, earned value, performance, etc.) can be analyzed within Acumen.
2 Working With Deltek Acumen Workbooks

Workbooks are the core files within Acumen. Workbooks contain all information pertaining to an Acumen analysis
including:
Imported project data
Metric libraries and metrics
Analysis Views
Custom field mappings
Only one workbook can be open at a time within Acumen. Workbooks are stored as single files either on a local or
network drive.
2.1 Workbook File Formats

Workbooks can be saved in two formats:
2.1.1 Standard File Format

This is the default file format for saving Acumen 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, e-mail, etc. but
the content of the file cannot be edited outside of Acumen. For the analysis of large project files, it is
recommended to use the standard file format.
2.1.2 XML File Format

Acumen 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. This file format generates larger file
sizes and as such is not as efficient as the native .afw format.
2.2 Creating a New Workbook

Creation of an Acumen workbook is very straightforward. From within the Projects tab (the first navigation tab),
simply click on the icon in the top left corner of the software to reveal the file menu and select New.
Figure 2-1 Creating a New Acumen Workbook
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 is made only to the currently opened workbook. To reuse an updated metric library, you will need to open
the updated workbook and do a Save As before proceeding with adding projects for analysis.
2.3 Linking and Importing Projects

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. Linking is the precursor step to actually importing the data.
A workbook can have an unlimited number of links to external sources. Acumen 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 workbook. These mappings are fully configurable as described in chapter 26.
2.3.1 MS Project 2003/2007/2010

Acumen 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 manner in 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 26).
2.3.2 Oracle Primavera P6 (V5/6/7/R8)

Acumen includes direct integration to Primavera P6 through web-services. This means that all P6 V8 and above
users can link directly to Primavera to analyze their projects.
Acumen additionally analyzes Oracle Primavera P6 XER and XML 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 or XML
files into Acumen.
Primavera P6 linking supports custom field mapping (normal, code and user defined fields see Chapter 26).
Linking to a Primavera P6 File through Web Services
Figure 2-2 Setting up connection to Primavera P6 Web Services
You can import a single project or multiple projects from Primavera P6 web services. To do this you will first need
to set up a connection to your P6 server. On the Acumen Options menu, click on the tab titled Platforms. Add
your host name (server), the Port, your user name and password. If you do not have this information contact your
P6 administrator or IT representative.
Test your connection and once it goes through you are ready to analyze P6 schedules. To link to the project, click
on the From Oracle Primavera button and then click Single or Multiple Projects from P6 Web Services.
You will see the EPS (Enterprise Project Structure) appear. Use the check boxes to select a single project or
multiple projects within the EPS. Hit ok.
Linking to a single project within an XER File

You can import a single project from an XER (or multiple XER files) or all projects within a single XER file. To do
this, click on the From Oracle Primavera button, and then Single Project from XER file. When prompted with a
list of projects within the XER file, select the desired project and click OK.
Figure 2-3 Importing a Single Primavera P6 Project from an XER File
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 button, and then Multiple Projects from XER file.
Primavera XML
Use the Project from a P6 XML file menu option to import a Primavera project that has been stored in the
Primavera XML format.
2.3.3 Primavera P3
You can import a project(s) from a Primavera P3 file. To do this, click on the From Oracle Primavera button, and
then Single Project from a P3 file. When prompted, select the desired project file (with a dir.p3 suffix) and click
OK.
2.3.4 Oracle Primavera Risk Analysis (formerly known as Pertmaster)

Acumen 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.
Installation is not required for importing .plnx files generated in Risk Analysis. In addition to importing cost and
schedule data, Acumen 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.
2.3.5 Deltek Open Plan

Acumen 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 order to select a project for linking. The Open Plan login credentials can be stored
in the Acumen Options > Platforms window.
Open Plan linking supports custom field mapping (normal, code and user defined fields see Chapter 26).
2.3.6 Asta PowerProject

Acumen 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:
Load the project file in PowerProject
Under Tools > User Field Manager, select Object Type > Bar > Add > Integer and name the newly
created field e.g. TotalFloatUserField"
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)
Add your user column in the main view by right clicking on a column header > Add column > User > "
TotalFloatUserField "
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)
Save file as an Asta PowerProject database MDB file
You can now read the MDB file directly in 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.7 UN/CEFACT XML Schedule Files

Acumen links to schedule files that use the UN/CEFACT XML schema (version D080B). This schema is an
emerging standard being driven by organizations like DCMA. You can link to and import from an UN/CEFACT
XML file without having a scheduling tool installed on your PC.
UN/CEFACT linking does not support custom field mapping.
2.3.8 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 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 calculations are carried out directly within Acumen and are included in the Earned Value metrics.
Deltek Cobra linking in Acumen 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 workbook through custom field mapping (see chapter 26).
2.3.9 MS Excel
Acumens 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 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-4).
Figure 2-4 Linking to a Worksheet within an Excel File
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 workbook (see chapter 26). Excel fields will be auto mapped to
Acumen fields if the field names are consistent between the two applications.
2.3.10 ARES PRISM G2

G2
Detailed phase-based Earned Value (EV) data can be linked to from ARES PRISM . This is a very flexible
means of analyzing time-phased cost data.
PRISM
G2
linking in Acumen does not support custom field mapping.
2.3.11 Phoenix Project Manager

Import CPM schedules directly from Phoenix Project Manager for use in project analysis, acceleration and risk
analysis in the full Acumen software suite.
2.4 Link Types

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 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 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) in MS Project.
Workbook
Project
Snapshots
Figure 2-5 Workbook, Project, and Snapshot Hierarchy
Adding a Snapshot to a Project

To add a snapshot to an existing project:
1. Select the project that you want to add a snapshot to
2. From the Get External Data menu, add a new 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.
Converting a Snapshot to a Project

If you need to escalate a snapshot to become its own project:
Select the snapshot in question
Click the Convert Snapshot to Project button
2.4.3 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 Acumen that compare baseline data with the current schedule. To overcome this,
Acumen provides the ability to assign a given P6 baseline schedule to a P6 schedule that has been brought into
an Acumen 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.
Figure 2-6 Adding a Baseline to a Primavera Project
Select the desired Primavera P6 project within your Fuse workbook
Either right click on the P6 project or click on the Primavera menu within Fuse and select Set/Change
Baseline
Select the desired P6 XER that youd like to set as the baseline project
Once assigned, the Primavera P6 file within the Fuse workbook will have a B icon associated with it
(Figure 2-7).
Import the project data to import both the project and baseline files together.
Figure 2-7 Assigned Baselined against a Primavera P6 Project
Baselines can be reassigned/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.4 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. 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.
Figure 2-8 Assigning a Mapped File
To create a merge file, firstly select the project file that you would 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 Acumen using the Export to Excel button in the project workbook view.
Merging is not limited to cost/schedule. Any dataset that has an 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 dragdropping 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.
Figure 2-9 Mapping Merge File Fields
Source XLS Cost

data containing
Actual Cost and
CAM Owner
Schedule ribbons grouped by

CAM & showing actual cost
(both from merged XLS file)
Figure 2-10 Analysis View Showing Merged Data
2.5 Importing Project Data

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:
1. Select the desired project/snapshot
2. Click on Import Project under the Import menu.
To import all projects within the workbook
Click on Import all Projects under the import menu
Figure 2-11 Importing Project Data
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 workbook. Subsequent importing is not necessary to
conduct repeated analysis. Reimporting 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
workbook. Filters can be applied based on:
Activity type: normal, milestone, summary, Level of Effort (LOE)
Status: complete, in progress, planned
Resource assignments
Figure 2-12 Importing Project Data
Different filters can be applied to each project or 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.
2.6 Including/Excluding Projects from Analysis

While an Acumen workbook can contain an unlimited number of projects and snapshots, you can control which of
these projects/snapshots get included in analysis. To include/exclude projects from analysis, use the checkboxes
to the right of the project icons in the projects list.
Include/exclude from
analysis
Figure 2-13 Including/excluding Projects from Analysis
2.7 Setting Display Units

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. To set the display
units use the Display Settings options found under the Activity View menu item.
Figure 2-14 Display Time Units
3 S1 // PROJECTS: Viewing and Editing the Schedule

The projects tab is where Acumen workbooks are set up, schedules are manipulated, and scenarios are created.
3.1 Activity View

The activity view in Acumen is the standard view after importing a project. This view displays all activities,
grouped hierarchically by WBS (Work Breakdown Structure), along with each activity attribute including start/finish
dates, remaining duration, calendar, activity status and more. Use the scroll bar at the bottom of the screen to
view all of the details for each activity or group of activities.
3.1.1 Activity Grouping

Group activities hierarchically either by WBS (Work Breakdown Structure) or by a set of fields. To set up this view
click on the Activity View menu item.
Group by WBS
This option displays the activities by the project WBS hierarchy.
Figure 3-1 Group Activities by WBS
Group by Fields
Grouping by fields allows you to create a structure based on existing fields within your project file. For example,
you could view all critical activities within a certain contractor by first grouping by Critical/Non-Critical and then by
Contractor. Figure 3-2 shows the view grouped by critical/non-critical and then by WBS.
Figure 3-2 Create Hierarchies by Project Fields
Expand/Collapse Activity Groupings

Expand or collapse the groupings by using the + or signs at the left of each row. To expand or collapse the
entire project at once, use the Display Level slider found on the Activity View Grouping menu.
Figure 3-3 Set the Level of Detail Shown in the View
3.1.2 Add/Remove Columns

To further customize the project view, you can add or remove columns by simply right clicking on any column
header. From there select Show Column Chooser. This will allow the column chooser to pop up. Select the
column you would like to add and drag and drop it onto the view.
Figure 3-4 Right Click on Column Headings and Select Show Column Chooser
Figure 3-5 Drag and Drop Columns to the View
3.2 Smart Gantt

On the right hand side of the projects screen you will see the project displayed as a Gantt chart. You can resize
the Gantt chart by clicking on the left hand border of the Gantt column header and dragging to the left.
The Gantt chart view, called the Smart Gantt, allows you to view metric results, activity progress, uncertainty
settings or even modification such as activity acceleration, directly on the schedule.
Figure 3-6 Smart Gantt
3.2.1 Top Bar vs. Bottom Bar

The Smart Gantt can display a single bar for each activity or two bars for insight into multiple attributes of a
single activity. The various Smart Gantt display options including dates, color settings, and whether or not to
show activity progress and/or float can be set for each bar.
View the current selections directly in the menu item. Figure 3-7 shows that the Top Bar has been selected to
show scheduled dates with each activity color based on schedule quality. The bottom Bar is set to show
Baselined dates with each activity color based on historical performance.
Figure 3-7 Top and Bottom Bar Settings
3.2.2 Smart Gantt Dates

Select which dates to display on the Smart Gantt.
Scheduled: The current dates for the activities as defined in the schedule.
Early: The earliest possible date that the activity can start.
Late: The latest possible date that the activity can start.
Baseline: The dates defined by the project baseline.
Original: The dates as defined in the schedule prior to any modifications such as acceleration.
Px Date: Probabilistic or risk adjusted dates identified during a project risk analysis.
3.2.3 Smart Gantt Colors

Select color settings for the activities displayed in Smart Gantt.
Critical/Non Critical
Show critical activities in red and non-critical activities in blue.
Schedule Quality
Show color based on the Fuse Schedule Index. Activities in red are poorly planned (include errors such as
missing logic, negative float or insufficient detail) while activities in green are well planned. Yellow or orange
activities follow somewhere in between.
Historical Performance
Show color based on the historical performance of each activity. Activities that have been performing poorly are
shown in red. Activities that are on time and on budget are shown in green. Yellow or orange activities fall
somewhere in between.
Metrics
Show color based on a certain metric from a Fuse analysis. Each activity will be colored based on the thresholds
defined by the metric.
Field
Select a field such as Activity Status or any user-defined field to use as the basis for coloring each activity. Once
a field is selected define the color mapping.
Figure 3-8 Base Activity Colors on a Field
Adviser
Color each activity based on suggestions from the Schedule Realism Adviser. See Chapter 24 for more
information on the Adviser.
Risk Inputs
Color activities based on the uncertainty inputs defined during a risk analysis. This option is only available with
Deltek Acumen Risk.
Duration Uncertainty: Color each activity based on the Duration Uncertainty assigned in Acumen Risk.
The colors are defined in the Uncertainty Template found on the S3// Risk tab. See chapter 17 for more
information on uncertainty assignments in Acumen Risk.
Cost Uncertainty: Color each activity based on the Cost Uncertainty assigned in Acumen Risk. The
colors are defined in the Uncertainty Template found on the S3// Risk tab. See chapter 17 for more
information on uncertainty assignments in Acumen Risk.
Risk Outputs
The Risk Output options for coloring activities in the Smart Gantt are only available with Deltek Acumen Risk. A
risk analysis must be performed first in order to use these options.
Criticality: Color based on how many times the activity fell on the critical path during risk analysis. Red
activities have a higher criticality while green activities have a lower criticality. Yellow or orange activities
fall somewhere in the middle.
Schedule Contribution: Color the activities based on how much or how little they impact the riskadjusted project finish date. Red activities have a higher impact on project finish while green activities
have a lower impact. Yellow or orange activities fall somewhere in the middle.
Risk Range Factor: Color the activities based on Deltek Acumen Risks simulation of the impact of risk
events on the schedule.
Acceleration
Color activities based on the acceleration calibration settings. This option is only available with Deltek Acumen
360. The color settings for this option are defined in the calibration template. For more information on Calibration
refer to chapter 24.
3.2.4 Additional Smart Gantt Options

Display Progress
Select this option to show progress of each activity. A dark line will be added to the activity bar to display activity
progress. Figure 3-9 shows an activity with 50% completion.
Figure 3-9 Activity Displaying 50% Completion on Smart Gantt
Display Float
Select this option to display the amount of float on each activity. A dark line is added below the activity to indicate
positive float. A red line below the activity shows negative float.
Figure 3-10 Smart Gantt Displaying Positive and Negative Float
3.3 Filtering Activities

Create filters for the Activities View and Smart Gantt using Acumen Fuse metrics or during Forensic Analysis.
3.3.1 Create a Filter Using Metrics

Any metric within Deltek Acumen Fuse can be used to create a filter for the activities view and Smart Gantt. On
the S2 // Diagnostics tab select any metric result (For additional information on using Acumen Fuse diagnostics
refer to chapter 5). Select the Smart Gantt filter icon in the top right corner of the activity browser.
Browse back to the S1 // Projects tab and select the Filtering option under Activities View. The newly created
filter will be listed. Once selected, the filter will remove the activities from the list as well as the Smart Gantt.
Create metricbased Smart

Gantt filter.
Figure 3-11 Create a Filter based on Acumen Fuse Analysis
3.3.2 Create a Filter Using Forensics
Create a filter for the Activities View and Smart Gantt using activities identify during a Forensic Analysis. On
the Forensics tab use the Create Smart Gantt Filter icon to create a filter for the listed activities. For additional
information on Forensic Analysis refer to chapter 12.
Browse back to the S1 // Projects tab and select the Filtering option under Activities View. The newly created
filter will be listed. Once selected, the filter will remove the activities from the list as well as the Smart Gantt.
3.4 The Timeline View

Select activities can be added to a graphical timeline view in the projects tab. This is useful for looking at the big
picture within a project as well as comparing a project to its respective snapshots or scenarios.
To add activities to the timeline view, use the checkboxes in the activity list to assign activities to the timeline. To
select groups of activities first create groups in the table view. To select all activities within a group, simply select
that group heading or parent.
Use the checkboxes to select
activities to show in the
timeline view.
Select the parent activity to

add that entire group of
activities to the timeline view.
Figure 3-12 Select Activities to Show in Timeline View
Displaying the Timeline View

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.
Figure 3-13 The Timeline View
3.5 Editing the Schedule

Many features of the schedule can be modified directly within the Deltek Acumen software suite. It is
recommended to create a scenario (see chapter 24 for information on scenarios) prior to making any edits to the
schedule. Modify any activity using the options found on the activity details pane at the bottom of the projects tab.
Figure 3-14 Modify Activity Details
3.5.1 Modifying the Schedule

Browse through the tabs found in the Activity Details Pane to modify activity attributes. Simply select the desired
activity and then choose which field you would like to edit (e.g. ID, Description, Calendar) by placing your cursor
in the field. Any edits made will automatically be updated in the Activities view.
Update Activity Status
Update activity status by inputting the activity Actual Start and/or Actual Finish. The status of the activity, and
remaining duration will be updated. You can additionally choose to suspend the activity or resume an already
suspended activity.
Add/Remove Constraints
Add or remove Primary and Secondary constraints on the Status tab of the Activity details pane. Choose from the
provided list of constraints and input any required dates.
Modify Relationships
Change the relationship type of any activity or add/remove a relationship on the Relationships tab of the Activity
Details Pane. Select any activity from the activities view. In the Activity Details Pane you will see predecessor
activities on the left and any successor activities on the right.
Figure 3-15 Modify Relationships
Change Activity Work Breakdown Structure

In order to change the Work Breakdown Structure of any activity you must first group activities by WBS. Then
simply drag and drop the activity into the appropriate WBS grouping.
3.6 Create a new Cost Estimate

A new cost estimate can be created directly within Deltek Acumen. Click the Create Cost Estimate icon found
under the Excel menu item.
Figure 3-16 Create a New Cost Estimate
This opens a new cost estimate which will automatically be populated with a single activity called New Activity.
Edit the activity name and details directly in this view or by using the fields in the Activity Details Pane.
Edit an activity in the Activity Details Pane
Figure 3-17 Create a new cost estimate
3.6.1 Add New Activities

To add a new activity to the cost estimate use the Add Activity icon found in the Editing menu or right click on
any row of the Activities view.
3.6.2 Organizing Activities into a Hierarchy or Cost Breakdown Structure

Activities can be dragged and dropped to create a Cost Breakdown Structure or other hierarchy within the cost
estimate. Select any activity or row within the activities view and simply drag and drop it into the desired grouping.
In Figure 3-18, New Activity 5 was dragged on to the row titled Parent 2. This made New Activity 5 a child of
Parent 2.
Figure 3-18 Create a Hierarchy
Any number of hierarchical levels or groups can be created in the cost estimate. In Figure 3-19 New Activity 5
has been turned into a parent activity by adding a new activity (New Activity 6) and dragging it onto the New
Activity 5 row.
Figure 3-19 Create a New Parent Activity
Any time an activity, or group of activities, is dragged onto another row it becomes a child of that row.
4 Introducing Deltek Acumen Fuse

Deltek Acumen Fuse is a project diagnostic tool that pinpoints and resolves schedule shortcomings, helping to
ensure a sound basis of schedule and a successful execution.
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
4.1 Types of Analysis

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:
4.1.1 Single Project Analysis

When a workbook contains a single project, Ribbons can be generated as a single project ribbon or grouped by
field, WBS, or Resource. This mode of analysis provides a huge amount of slice and dice flexibility within a single
project.
Single Project as a Project Ribbon
Single Project Ribbonized by WBS
Figure 4-1 Single Project Analysis Mode
4.1.2 Snapshot Comparison-Trending of a Project over Time

As described in Chapter 2, 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.
4.1.3 Multi-Project/Portfolio Analysis

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.
Figure 4-2 Portfolio Analysis Mode
4.2 Introducing Ribbons

Ribbons are a means of slicing and dicing the project into meaningful groups of activities for analysis. They are a
means of flattening and simplifying large amounts of project data. A ribbon can be created by something as
simple as an activity attribute (e.g., type of activity, contractor, or critical/non-critical), a WBS, 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 projectsreduction of large numbers of activities to a more manageable

number of ribbons
Visualization of activities based on common criteria (e.g., activity attribute or network path)
Easy reporting giving a fast means of slicing and dicing project data
Figure 4-3 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.
Figure 4-3 Sample Project Shown as a Gantt Chart in MS Project
In Acumen Fuse, at the summary level, you can create a single ribbon that contains all activities within the project.
Figure 4-4 shows a ribbon view of the same sample project where a single ribbon is created for the entire sample
project.
Figure 4-4 Sample Project Shown as a Project Ribbon in Acumen Fuse
Now consider a scenario where you want to ribbonize based on whether an activity falls on the critical path or not.
Figure 4-5 shows the same sample project this time ribbonized by Critical Path. By separating critical and noncritical activities, you are able to get a clearer insight into your project.
Figure 4-5 Sample Project Showing Critical Path Ribbons in Acumen Fuse
Taking this a step further, now consider creating by work breakdown structures (WBS).
Figure 4-6 Sample Project Showing WBS Ribbons in Acumen Fuse
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.
4.3 Introducing 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 9 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
4.4 Deltek 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 4-7.
Ribbon analysis: metrics are applied to a ribbon as a whole.

Phase analysis: metrics are applied across ribbons within a specific phase or time period.
Intersection analysis: metrics are applied to a specific ribbon within a specific phase.
Ribbon Analyzer
Phase Analyzer
Figure 4-7 Ribbon, Phase and Intersection Analysis
As well as calculating metrics, Acumen Fuse analysis also determines whether or not defined tripwire thresholds
have been triggered. Figure 4-7 shows an example of the metric Missing Logic metrics being applied to a
project. Note: the ribbon analyzer tells you which group of activities (Critical or Non- Critical) has missing logic; the
phase analyzer tells you which time period contains the activities with missing logic, 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.
Figure 4-8 Activity Browser
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 1 will be automatically segmented into 31 days in January, 28
days in 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.
4.5 The Deltek Acumen Fuse Engine

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:
4.5.1 Ribbon Analysis

Ribbon analysis is conducted against all activities within a given against an activity grouping known as a Ribbon.
It is typically the starting point for reporting in that it gives a high level overview of exceptions.
Figure 4-9 Ribbon Analysis
4.5.2 Phase Analysis

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 4-11 shows a simple sample project with three activities spanning over a four-week period. When we
analyze the data in Acumen Fuse (Figure 4-12) and calculate two basic metrics, cost and schedule, we can see
that the Acumen Fuse engine prorates both duration and cost based on how the activities span across the four
periods. This makes phase-based analysis very powerful because you can analyze both within and across
defined phases, accounting for the amount of cost, duration and work that falls into each phase.
Figure 4-10 Simple MS Project Schedule Spanning Four Phases
Figure 4-11 Phase Analysis
4.5.3 Intersection Analysis

Intersection analysis only includes activities within a specific ribbon within a specific phase. Figure 4-13 shows an
example of two activities in MS Project that overlap with respect to time.
Figure 4-12 Two Activities within MS Project
Figure 4-14 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.
Figure 4-13 Two Activities within Acumen Fuse
4.5.4 Trend Analysis

The Acumen Fuse trend analysis feature allows you to replace the traditional time-based phases in the
diagnostics view with project snapshots. To use this feature you will need to have a project loaded with at least
one snapshot.
Similar to a phase analysis, the Acumen Fuse engine calculates results across ribbons within each snapshot.
Figure 4-15 shows a trend analysis across 3 project snapshots: the initial plan, a 1 month update, a 6 month
update and the current schedule.
The Total Activities metric has been added to the intersection analyzer and the activities have been grouped by
status. In this view you can see the number of activities that are planned, in-progress, or complete for each
project snapshot.
The Phase analyzer shows the total metric result for each snapshot.
Figure 4-14 Trend Analysis in Acumen Fuse
Analysis Type
Ribbon Analysis
Summary
Cross ribbon comparison
Phase Analysis
Cross phase comparison
Intersection Analysis
Specific ribbon/phase analysis
Trend Analysis
Specific project snapshots
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.
Metric analysis for multiple
project snapshots across ribbons.
Figure 4-16 Three-Dimensional Fuse Analysis Modes
5 S2 // DIAGNOSTICS: Schedule Analysis

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.
5.1 Navigation
The analysis view consists of four panels:
Ribbon Browser: flattened project data showing ribbons, activities and phases
Ribbon analyzer: graphical/tabular view of analysis results for each ribbon
Phase analyzer: graphical/tabular view of analysis results for each phase
Activity Browser: tabular/Gantt/scorecard/heat map view of activities
Intersection
Analysis
Phases
Ribbons
Ribbon
Analyzer
Ribbon
Browser
Metrics
Figure 5-1 S2 // Diagnostics Tab
Activity
Browser
Phase
Analyzer
A single workbook can contain multiple analysis views. For example, you may have an analysis view designed for
cost analysis and a second analysis view for the same workbook setup for risk exposure analysis.
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.
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).
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.
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 chart.
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 chart.
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).
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.
5.2 Running a Deltek Acumen Fuse Analysis

Running an Acumen Fuse analysis is very straightforward. There are only two steps required:
5.2.1 Populate your workbook with project data

(Refer to chapter 2)
5.2.2 Run Acumen Fuse Analysis
Navigate to the Ribbons view
Select desired pre-defined analysis view through tabs at the bottom of the screen
Click on the Fuse button to run the analysis
Click on any metric result, ribbon, or phase to view the included activities in the Activity Browser
Figure 5-2 Sample Analysis Results
5.3 Grouping Activities: Ribbons

Activities can be grouped based on any attribute (e.g. activity status, critical/non-critical, contractor). These
groups are called Ribbons. Ribbons can be created using one of four techniques. In all four instances, the
purpose of creating ribbons is to slice and dice the project data in order to run a meaningful analysis.
5.3.1 Project/Snapshot Ribbons

Project ribbons are the simplest 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 an 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 5-3 shows an example
workbook containing multiple projects, each displayed as a separate Ribbon.
Figure 5-3 Project Based Ribbons
5.3.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
Figure 5-4 Creating Field-Based Ribbons
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).
Number 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.
Field Ribbons using Interval Size
Field Ribbons using # of Intervals
Field Ribbons using Delimiters
Figure 5-5 Field-Based Ribbons
5.3.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.
Figure 5-6 Resource-based Ribbons
5.3.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.
Figure 5-7 WBS-based Ribbons
5.3.5 Sorting Ribbons

Ribbons can be sorted by metric results by right clicking on the metric header and selecting the sort option. This is
a good technique for prioritizing results once a Fuse analysis has been conducted.
5.3.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 5-8 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.
Figure 5-8 Filtered Analysis Using Hierarchical Ribbons
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.
5.4 Defining Date Ranges & Phases

Ribbons are segmented by phases. Each phase is analyzed separately in the phase analyzer.
By default, Acumen Fuse will create an 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.
Figure 5-9 Ribbon Phase Options
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.
Splitting 2010 and 2011 Phases
Merged 2010 and 2011 Phases
Figure 5-10 Merging Ribbon Phases
The entire analysis view can be reset to include all activities by clicking on the Reset Dates menu item.
5.5 Applying Metrics

By default, the Diagnostics 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).
Figure 5-11 Ribbon Tabs
5.5.1 Adding a Metric to an 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 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
Figure 5-12 Adding Metrics
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.
5.5.2 Removing Metrics from an 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.
Figure 5-13 Remove metric applied to Intersection Analyzer
5.5.3 Adding an Entire Metric Library to an Analyzer

As well as adding individual metrics to an 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.
Figure 5-14 Adding Metrics
5.5.4 Adding New Metric Views

New tabs can be added with metrics added to each in the same way as described above. New tabs are created
by clicking on the new icon on the furthest tab on the right hand side. Rename tabs by right clicking on the tab
and selecting Rename.
Figure 5-15 Add New Tab or Ribbon View
5.6 Viewing & Interpreting Results through Analyzer Windows

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.
5.6.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.
Ribbon Analyzer -Tabular View
Ribbon Analyzer Chart View
Figure 5-16 Ribbon Analyzer
5.6.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.
Phase Analyzer Tabular View
Phase Analyzer Chart View
Figure 5-17 Phase Analyzer
5.6.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 manner as 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.
Intersection Analyzer Tabular View
Intersection Analyzer Chart View
Figure 5-18 Intersection Analyzer
5.6.4 Analyzer Chart Options

When viewing any of the three analyzers in chart mode, modify the chart type 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.
5.7 Using the Activity Browser

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
A ribbon (cutting across multiple phases): all activities for a given ribbon.
A phase (cutting across multiple ribbons): all activities for a given phase.
An intersection: all activities for a given ribbon within a specific phase.
Activities that trigger a given tripwire threshold
Ribbon metric results: activities for a given metric segment within the ribbon analyzer.
Phase metric results: activities for a given metric segment within the phase analyzer.
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.
Action
Analysis View
Activity Browser Results
Click on a
ribbon
description
Shows all activities for the

selected ribbon.
Click on a
Phase
Header

selected phase.
Click on a
ribbon/phase
intersection

selected intersection.
Click on a
intersection
metric
Shows those activities for the

selected intersection that
triggered the tripwire.
Click on a
ribbon
analyzer cell

selected ribbon that triggered
the tripwire.
Click on a
phase
analyzer cell

selected phase across all
ribbons that triggered the
tripwire.
Figure 5-19 Activity Browser Results
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 Undock 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 Publish icon.
5.7.1 Activity Browser View Options

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.
Figure 5-20 Activity Browser View Options
Activities within the activity browser can be shown in five formats:
Tabular
Gantt
Heat map
Detailed
Scorecard
Activity Browser Tabular mode
Activity Browser Gantt mode
Activity Browser Heat Map
Activity Browser Detailed mode
Activity Browser Scorecard

Figure 5-21 Activity Browser Modes
5.7.2 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.
Figure 5-22 Activity Browser Showing Scorecard Results
5.7.3 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.
Figure 5-23 Heat Map Options
Figure 5-24 shows an example heat map with size of box showing duration, color showing Total Cost, grouped by
Critical/Non Critical.
Figure 5-24 Heat Map Example
5.7.4 Activity Browser Printing

To print from the Activity Browser window:
Select the required activities to display
Select tabular view (default mode)
Optionally arrange, sort and group the columns
Click the Print icon in the Activity Browser to print the report
Figure 5-25 Printing the Activity Browser Results
5.8 Smart-Filtering of Ribbons

The Fuse Analysis View is highly interactive view. As you click on the any of analyzer cells the activities shown
within the ribbons are automatically filtered to correspond to the activities in the activity browser.
Smart filtering
of activities
Figure 5-26 Smart Filtering of Activities Based on Analysis Results
5.9 Zooming in/out of Phases

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.
Figure 5-27 Zooming within Phases
To zoom out of a phase, hover over the Timeline header and click on the magnifying glass icon to zoom out.
5.10 Analysis Justification & Exclusions

5.10.1 Exclude Activities From the Analysis
You can optionally filter activities out of the Fuse analysis using the checkboxes within the activity browser. Run
your Fuse analysis, select a metric result and review the activities included in the activity browser. To exclude an
activity from the analysis, check the box on that activity and re-run your analysis. You will see the metric results
update.
Check to exclude
activities
Figure 5-28 Filtering Activities from the Fuse Analysis
5.11 Adding Annotations to activities

To add notes or annotations to the metric results, use the notepad icon found in the activity browser. You can
select to annotate a single activity or the entire activity browser. Click the notepad icon next to an individual
activity to only add the note to that activity. Click the notepad icon in the top right hand corner of the activity
browser to automatically annotate all activities within the browser.
Click the notepad in the

annotate column to annotate
a single activity.
Click the notepad on

the activity browser to
automatically annotate
all activities within the
view.
Figure 5-29 Activity Annotations
Multiple annotations can be added to the activities by re-clicking the notepad icon.
6 Deltek Acumen Fuse Driving Logic Analysis

The Fuse diagnostics view can also be used to run a driving 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, 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.
Figure 6-1 Logic Trace Menu
Figure 6-1 shows the three logic trace buttons in the activity browser that can be used as a fast-track 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-2 Triggering a Logic Trace from the Activity Browser
Figure 6-3 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.
Figure 6-3 Results from a Logic Trace
7 Deltek Acumen Fuse Comparison Analysis

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.
7.1 Running a Comparison Analysis

To run a comparison, do the following:
1) Create scenario A by clicking on any of the following:
Ribbon analyzer cell: selects all activities that trigger the tripwire for the selected metric within the
selected ribbon (across multiple phases).
Phase analyzer cell: selects all activities that trigger the tripwire for the selected metric within the
selected phase (across multiple ribbons).
Intersection analyzer cell: selects all activities that trigger the tripwire for the selected metric within
the selected phase within the selected ribbon.
Phase header: selects all activities across all ribbons for the selected phase.*
Ribbon header: selects all activities across all phases for the selected ribbon.*
2) Click on the Compare button within the Analyze menu.

3) Create scenario B by clicking on any of the same options as described above for scenario A.
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.
Figure 7-1 Compare Analysis Results
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., activities that have not 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.
7.2 Comparison Analyzer Printing

Results from the comparison analyzer can be printed by clicking on the Print icon within the Comparison Analyzer
window.
Figure 7-2 Printing the Comparison Analyzer Results
8 Deltek Acumen Fuse Metric Benchmarking

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, select Benchmark Comparison button found in the Other Settings 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 8-1 shows an example of benchmark comparison with the Northern Region ribbon being the selected
base scenario against the comparison analysis is being carried out.
Figure 8-1 Metric Benchmarking
9 Managing 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:
9.1 The Building Blocks of Acumen Fuse Metrics

Each metric is made up of a Primary Formula, a Secondary Formula and Tripwires.
9.1.1 Primary Formula

The primary formula is the formula used to calculate the primary result calculated in the analysis (e.g., total cost).
9.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.
9.1.3 Tripwire Formula

The tripwire formula is (optionally) used to determine the individual exceptions that are listed in the Activity
Browser. Metrics that do not contain a Threshold formula cannot be used to display activities in the Activity
Browser and also cannot be used in the Comparison Analyzer.
9.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.
Figure 9-1 The Metric Editor
9.2 Metric Definition
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
Activity Status
(planned, in-progress, complete)
Activity type
(normal, milestones, summary)
Time period
(starts or finishes in current time period)
Filters
Simple filters based on fields
(e.g. Actual Start Date > Baseline Start Date)
Multiple filters can be added - treated as AND compounds
Formulas
User-defined formulas. Useful when needing OR statements ,
divisions or other advanced functions.
Figure 9-2 Hierarchical Development of Metrics
9.3 Writing Metric 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. The formulas enable us to group and aggregate multiple activities together so that
results for a ribbon or phase or intersection can be calculated.
9.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 typically apply a container function such as SUM or AVERAGE or COUNT. This
enables 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. So, certain data
(duration, work and cost field types) gets prorated. 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 Remaining Duration =

2+5+5=12
Array
Formula
Remaining
Duration =
2+3=5
Figure 9-3 Calculation of Array Formulas
9.3.2 Developing Primary Formulas

Primary formulas can return any type of numeric or text-based result. To create a Primary formula:
1. Define inclusions. These are overarching filters that limit which activities get included in the
search by type/status/phase.
2. Define Filters. These are the next level of filters further filtering out specific activities. Many metric
definitions can be completed by just using inclusions and filters (e.g., Critical activities).
3. Optional formula. If additional advanced criteria definition is needed, then select the advanced
mode and define the function using the advanced metric editor.
Basic Formula
Definition
Advanced Formula
Definition
Figure 9-4 Basic and Advanced Primary Formula Definition
For both basic and advanced Primary formula definition, formatting of primary formula results is achieved using
the Formula Format drop down list.
9.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:
1. 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.
2. 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.
Auto Percentage
Mode
Manually Defined
Mode
Figure 9-5 Simple Percentage of Primary Formula and Advanced Secondary Formula
9.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).
9.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 because they are automatically inherited from the primary inclusions and filters.
Advanced: This mode enables you to manually create inclusions, filters and advanced functions that
together return the required set of activities.
Auto-calculated
Mode
Advanced Mode
Figure 9-6 Auto-Calculated and Advanced Tripwire Formula Definition
9.4.2 Tripwire Thresholds

Each metric includes an optional set of tripwire thresholds. These thresholds are used to graphically show when a
defined threshold is exceeded. Tripwire thresholds can be based on either the primary or secondary formula. If
the secondary formula is enabled (by checking the checkbox for the secondary metric), then the tripwire threshold
is automatically associated with the secondary metric. If this checkbox is not checked, the tripwire threshold is
automatically associated with the primary formula.
9.4.3 Defining Tripwire Threshold Scales

Tripwire threshold scales can be defined as having any number of intervals. To help with the creation of such
scales, use the Tripwire Thresholds > Color Scales menu to automatically create standard scales.
Figure 9-7 Tripwire Threshold Scales
This option provides three types of standard scale:
Lowest is better: creates a scale where the lowest values are preferable
Highest is better: creates a scale where the highest values are preferable
Ideal Value: creates a scale where the middle values are preferable
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.
9.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 does or does not
trigger a threshold. 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 a metric result is. 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).
9.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.
Figure 9-8 Inclusion/Exclusion of Metrics to Analyzers
9.5 Testing Metric Formulas

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.
9.6 Commonly Used Functions

The Acumen Fuse metric editor supports all MS Excel functions. The most commonly used formulas are grouped
in the Commonly Used menu.
Figure 9-9 Commonly Used Function Types
9.6.1 IF Function
The IF function returns one value if the specified condition is TRUE and returns another value if the specified
condition is FALSE.
IF(logical_test, value_if_true, [value_if_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 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.
Example: IF(TaskStatus="Inprogress",1,0) can be written in shorthand as (TaskStatus="Inprogress")
9.6.2 SUM Function

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
Example: SUM(ActualCost) returns the sum of the Actual Cost.
9.6.3 AND Function

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.
9.6.4 MAX Function

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.
9.6.5 AVERAGE Function

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
Example: AVERAGE(TotalFloat) returns the average Total Float.
9.6.6 COUNTIF Function

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.
9.7 Types of Acumen Fuse Fields

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.
9.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.
9.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]
9.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]
9.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]
9.8 Templated Metric Libraries

In addition to editing a metric library within a given workbook, metric libraries can be saved as templates and
reused within other Fuse workbooks.
9.8.1 Saving a Metric Library as a Template

Once a metric library has been customized, you can save it (for reuse) 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.
Figure 9-10 Saving a Metric Library as a Template
9.8.2 Reusing a Metric Library Template

To reuse a Fuse metric library template select 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.
9.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.
Figure 9-11 Setting Default Metric Library
9.9 Managing Metrics and Metric Libraries

Both metrics and metric libraries can be reconfigured with copy-paste functionality. Using either the Fuse
clipboard menu or the right click feature of a metric/metric library, metrics can be copied and moved to different
locations within the metric library.
Figure 9-12 Managing the Metric Library
9.10 Metric Weightings for Scorecards

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). 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 midpoint 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.
Figure 9-13 Metric Weightings for Scorecard Analysis
9.11 Metrics Using Variables

Fuse provides an extremely powerful means of defining metrics against generic fields and values prior to knowing
what these values actually are. There are two forms of variables within Fuse:
Variable Values: when defining a metric, instead of setting criteria based on a defined value, you can
describe a metric in terms of a variable. An example is a custom metric called high cost. At the time of
the metric being created, you do not know what this value should be. Instead you can create a variable
called say High Cost Value and use this in the metric definition. Then at run-time, when a Fuse analysis
is run, the user will be prompted to enter a value for this variable and Fuse will subsequently use the
value in its calculations.
Variable Fields: when defining a metric, if a field to be used in a metric definition is unknown, then a
variable field can be created. In a similar manner to the variable value concept, when a Fuse analysis is
run, the user is prompted for the actual field to be assigned. This is useful when a metric refers to say a
user defined or code field that is not known at the time of creation of the metric.
A metric can be defined using variable values, variable fields or even both!
9.11.1 Defining Variables

Variables are defined by clicking on the variables tab in the metric editor. Figure 9-14 shows an example of a
variable called My Unknown Cost. This variable will then be used in the definition of the metric. If no value is
specified in the Value field, the user is then prompted for this during a Fuse analysis. Upon entering this value (at
run-time), the variable will store and use this value unless altered at a later time by the user.
Figure 9-14 Defining Variables
9.11.2 Referencing Variables when Defining Metrics

Once a variable has been defined, it can be referenced when defining a metric in the exact same way a normal
defined value is referenced. Figure 9-15 shows an example of a metric called High Cost being defined using the
variable My Unknown Cost.
Variable
Figure 9-15 Referencing Variables
9.11.3 Running a Fuse Analysis using Variables
In our example, we have created a variable called My Unknown Cost and referenced it in a custom metric called
High Cost. When a Fuse analysis is run, if the variable value has not been set, the user is prompted to set a
value. Figure 9-16 shows an example of the user entering a value of $1,000,000 as the variable value at run-time.
The result is shown in Figure 9-17.
Figure 9-16 Setting a Variable Value During a Fuse Analysis
Figure 9-17 Results Being Driven by a Variable Value Fuse Analysis
To change the value of the variable, either go back to the variable definition in the metric editor or instead, within
the Analysis view, click on the little expand icon in the bottom-right corner of the Analyze menu.
Figure 9-18 Changing Variable Values in the Analysis View
9.11.4 Defining Variable Fields

As well as defining, referencing and analyzing variable values, variable fields can also be utilized. Exactly the
same in concept, a metric can be defined using a variable field. Figure 9-19 shows the definition of a variable
(unknown) field called Owner.
Figure 9-19 Creating a Variable Field
9.11.5 Referencing Variable Fields when Defining Metrics

Once a variable field has been defined, it can be referenced when defining a metric. In our example, we now
create a metric called Owner Activities. This metric references the variable field that we have created called
Owner. However, at the time of creating the metric, the exact field name is not known (as it will subsequently be
defined as a user defined field of an unknown field name).
Figure 9-20 Creating a Metric Using a Variable Field
Figure 9-21 shows the binding of Fuse variable field Owner to a user-defined field in Primavera called
Contractor. This means that the metric can be run against any project irrespective of the actual field name used
to represent Owner.
Figure 9-21 Setting a Variable Field to a Field During a Fuse Analysis
Figure 9-22 shows the results from our Fuse analysis using the metric called Owner Activities, a count of the
number of activities whose user-defined field Contractor has a value of InHouse.
Figure 9-22 Results Being Driven by a Variable Field Fuse Analysis
9.11.6 Working with Both Variable Fields and Variable Values

The two previous examples demonstrated working with either a variable value or field where the field value was
known. In some instances, the value of a variable field is not known. For this, we can use the Variable Field editor
to also create variable values.
Figure 9-23 Creating Variable Field and Variable Value
Once the variable field and variable value have been created, the metric can be defined as shown in Figure 9-24.
Figure 9-24 Creating a Metric Referencing a Variable Field and Variable Value
Upon run-time, the user is then prompted to define both the Variable field as well as the variable value.
Figure 9-25 Selecting Variable Field and Value at Fuse Runtime
Figure 9-26 Results from the Owner Activity Metric using a Variable Field and Value
Multiple variables against a variable field can be created. An example of this is creating a variable field called
Acceptable Cost that contains two variables Low Value and High Value.
A metric is then defined based on two criteria: the Total Cost being greater than Low Value and less than or
equal to High Value.
Figure 9-27 Defining the Custom Metric Called 'Acceptable Cost'
At run-time, Fuse then prompts the user for not only the field that is being used in the calculation but also the two
variable costs being used in the metric calculation.
Figure 9-28 Setting Variable Fields and Multiple Variance Values
Figure 9-29 Results from Analysis Using a Variable Field and Multiple Variable Values
10 Reporting Diagnostics Results

All components of an Acumen Fuse diagnostics check can be included in a MS Excel-based report including:
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. These editable reports subsequently can
be used in other applications such as MS PowerPoint.
Figure 10-1 Publish to MS Excel
10.1 Executive Briefing

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.
Figure 10-2 Example Pages within the Executive Briefing Report
10.2 Analyst Report

The analyst report is designed to serve as a checklist listing each of the individual activities that fail the various
metric tests that have been applied to the view.
Figure 10-3 Example of Analyst Report
11 S2 // LOGIC: Logic Analysis

In addition to using Acumen Fuse to perform diagnostic checks on schedule attributes, Fuse can evaluate
relationships between activities.
11.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)
Logic Sensitivity
Figure 11-1 Various Logic Analysis Options
11.2 Positive and Negative Leads and Lags

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.
11.3 Redundant Logic

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.
Figure 11-2 Redundant Logic in a MS Project Schedule
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.
Redundant logic link between

Electrical Design and
Mechanical Design
Duplicated logic between Electrical

Design and Mechanical Design
(through Telecoms Design)
Figure 11-3 Logic Analysis in Acumen Fuse
11.4 Logic Sensitivity

The logic sensitivity check allows you identify how potential delays affect key activities or milestones later in the
project. To run this check you must input three variables:
Nudge Activity: Select any activity or milestone from your project. This activity will be the starting point
of the test. A simulation will be run where a delay is added to this activity to see if it impacts an activity or
milestone later in the project.
Nudge Duration: Input the number of days you would like to nudge, or delay, the Nudge Activity by. By
default this number is set at 600 days.
Target Activity: Finally, select the target activity you would like to test the impact on.
Figure 11-4 shows the result of a Logic Sensitivity test where the Nudge Activity, was delayed by 600 days. The
test found that 30 days of delay could be added to the Nudge Activity before any impact was seen on the target
activity.
Figure 11-4 Logic Sensitivity Test
This interactive view can also be used to determine the impact on the Target Activity at any given amount of
nudge. Roll your mouse along the blue line to see the intersecting points.
11.5 Additional Logic Checks

11.5.1 Circular Logic
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.
11.5.2 Open Ends

Open ends analysis checks for any activities that are missing either predecessors or successors causing the
activity to be open ended.
11.5.3 Relationships on Summaries

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.
11.5.4 Out of Sequence Updates

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.
11.5.5 Reverse Logic

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.
11.5.6 Dangling Activities (Open Start and Open Finish)

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.
11.6 Sorting and Grouping Logic Analysis Results

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.
11.7 Logic Analysis Report

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.
Figure 11-5 Logic Analysis Report
12 FORENSICS: Identifying Additions, Deletions and

Modifications
12.1 Overview
The Acumen 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.
Forensic analysis can be used for:
Ongoing project surveillance
Schedule import/export integrity support
Contractor performance tracking
Claims Avoidance/Evaluation
Expert Witness Testimony
12.2 Setting up a Forensic Analysis

A forensic analysis requires, at a minimum, two or more projects within a workbook. Additionally, one of the two
projects must be designated as a snapshot against the primary project.
Creating such a hierarchy is very simple:
Create a new workbook (File > New)
Add a primary project to the workbook (click one of the Get External Data icons)
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)
Import all data (click on the Import All button to complete the import)
Figure 12-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.
Figure 12-1 Setting up a Forensic Analysis Workbook
12.3 Running a Forensic Analysis

Once a forensic analysis workbook has been setup, you can run the analysis by selecting the Forensic tab in the
main navigation ribbon.
Figure 12-2 Running a Forensic Analysis
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
Changed calendar definitions
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).
1. Data can be sorted by clicking on the required field header
2. 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
3. Absolute and percentage variances are shown for each of the comparison snapshots (compared to the
base schedule being compared against).
4. Refer to section 11.4 for details regarding creating new forensic reports/criteria.
Figure 12-3 Sorting and Grouping a Forensic Analysis Report
Acumen Forensic Analysis reports can be published to MS Excel by clicking the Publish to Excel button in the
projects tab.
Figure 12-4 Exported Forensic Analysis Results in MS Excel
12.3.1 Calendar Definition Forensics

One of the unique capabilities is the calendar forensics analysis. This utility interrogates multiple versions of a
schedule identifying changes to the calendar definition. This includes changes to standard working/non working
time as well as changes to exceptions (e.g., holidays). In addition, changes to calendar assignments on activities
can also be interrogated. Figure 12-5 shows an example of the calendar definition forensic analysis.
Figure 12-5 Calendar Definition Forensics
12.4 Modifying Reporting Criteria

Additional criteria (and columns) can be added to the Forensic analysis. This is achieved through the Fields tab.
To modify criteria and/or columns, either:
1. Click on the Fields tab
2. Click on the More button under the Activity Variances menu in the forensics tab
Figure 12-6 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
12-7):
Compare in Forensic Report: creates a new Forensic view that compares differences between the
snapshots for the given field
Show in Forensic Report: adds the selected column to all activity-based forensic reports (which can
then be used for sorting and grouping)
Figure 12-7 Customizing Forensic Columns
Figure 12-8 Customizing Columns and Criteria for the Forensic Analyzer
Figure 12-8 shows an example of a 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.
12.5 Forensics Analysis Report

The forensics analyst report published from Fuse is generated as a MS Excel file. A separate tab for each
forensic check is automatically created in the Excel workbook.
Figure 12-9 Example of Analyst Report
13 S5 // DASHBOARD: Reporting Results

The Acumen 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
Project Status
Activity Status
Forensics
Logic Quality
Status Overview
Fuse Analysis Widgets
Customizable widgets driven by the Fuse diagnostics metrics/views
Figure 13-1 Fuse Dashboard
All widgets within the dashboard can be directly copied to the clipboard using the copy icon in the top right corner
of the view.
13.1 Diagnostics Widgets

Results from a Fuse analysis created in the diagnostics view can be incorporated into the dashboard through
Diagnostic Widgets. Multiple Fuse Widgets can be added to a single dashboard. Diagnostics 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 within the Widget
Figure 13-2 Fuse Diagnostic Widgets
14 Schedule Cleanser
Acumen Fuse can not only analyze a schedule but also cleanse and resolve flaws in a schedule.
14.1 Running a Schedule Cleanse

A schedule cleanse can be conducted on MS Project and Primavera P6 schedules. To run a schedule cleanse,
select the project to be cleansed and then click the Cleanse Schedule button. Select the desired cleanse options
and then click OK to create the newly cleansed scenario. Individual activities can be explicitly included/excluded
in a schedule cleanse. Additionally, lags (durations on relationships) can either be removed or converted to
activities.
Figure 14-1 Schedule Cleanser
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.
14.3 Publishing a Scenario to MS Project and Primavera

Once a cleansed scenario has been created, it can be published back to its original format (MS Project or
Primavera). To publish, right click on the scenario in the Projects tab tree view and select Export Scenario, or
click the Export Scenario button in the Projects tab toolbar. These files are scheduled/CPM-time analyzed in
Fuse before being published and so have updated early/late dates, float etc.
15 The Acumen Application Programming Interface (API)

Acumen provides a powerful and flexible Application Programming Interface (API). This API can be used for:
Custom reporting
Integration with 3rd party applications
Exporting schedule data to custom formats
Integrating with web-services
Integrating with third party reporting tools such as Crystal reports
Publishing results to portals such as MS SharePoint
All of these custom reports/applications can be added into Fuse and launched through custom Publish menu
items.
Figure 15-1 Example Custom API Integration
More information about the Acumen API can be found in the Acumen API guide.
http://www.projectacumen.com/resource/acumen-fuse-api-user-guide/
16 S3 // RISK: Project Risk Analysis

16.1 Introducing Deltek Acumen Risk
Acumen Risk is an advanced risk analysis tool for managing both cost and schedule risk exposure within a
project(s). It incorporates proven approaches and utilities such as Monte-Carlo simulation and an integrated
project risk register together with unique-to-Acumen Risk approaches such as Uncertainty Factors and Risk
Contribution reporting.
Acumen Risk is designed for planners, schedulers, risk analysts and risk workshop facilitators alike. It has been
designed to be easy to use with meaningful reporting that doesnt rely upon complex statistical interpretation. In
short: it is designed with project teams in mind wanting to truly determine their cost and schedule risk exposure
together with establishing a sound plan for risk exposure reduction.
Acumen Risk is part of the Acumen toolset of products and can work either alongside or in isolation of Deltek
Acumen Fuse and Deltek Acumen 360.
16.2 Starting with Acumen Risk

As part of the Deltek Acumen platform all common platform capabilities such as importing from multiple
scheduling tools and running forensics are included in Acumen Risk.
16.2.1 Importing Cost/Schedule Data into Acumen Risk

The starting point for a risk analysis is to import a cost/schedule file from the likes of MS Project or Primavera or
MS Excel. Use the standard file import options within the Acumen platform to import data for a risk analysis.
A risk analysis can be conducted on both projects and snapshots within Acumen Risk.
16.2.2 Updating an Existing Risk Model with a Modified Schedule

If you are working on a risk model and have assigned uncertainties and risk events, Acumen Risk supports a
subsequent import of an updated cost/schedule file while still retaining your assigned uncertainty/risk values. This
allows you to run a risk analysis on updated schedules without having to re-create the risk model upon each
subsequent update.
Simply re-import the schedule/cost file from within the Projects view by clicking on the Import button.
16.2.3 Navigating the Risk View

The Risk view navigation follows the standard Acumen platform paradigm. Sub-views within the Risk view can be
selected through the Left/Right Panel menu options.
Figure 16-1 Assigning Views to the Left and Right Panels
17 Risk Inputs
17.1 Uncertainty
Assigning uncertainty is the first in two steps when developing a risk model. Uncertainty is typically driven by
unknown scope or complexity of work. Uncertainty can be assigned using one of two modes in Deltek Acumen
Risk:
Graphically assigned using the Uncertainty Factor sliders
Manual data entry of min, most likely, max ranges
It is recommended that the Uncertainty Factor approach is used for developing risk models. It provides a fast,
consistent and validated means of risk loading a model avoiding potential errors in data entry.
17.1.1 Uncertainty Factor Template

Prior to applying uncertainties to the risk model, the Uncertainty Factor Template should first be defined.
Uncertainty Factor templates are defined by clicking on the Uncertainty Template menu.
An Uncertainty Template is used by the project team to describe the degree of buy-in and confidence in the
underlying durations and costs in the risk model. IT should not be used for modeling the potential impact of risk
events. This is covered through the use of the risk register.
Figure 17-1 Defining Uncertainty Templates
The template can be configured to model varying number of uncertainty categories. Use the Size slider to set the
desired number of categories.
Once the number of categories has been defined, set the name, type and min, most likely and max percentages.
These percentages are then used when applying the template to the risk model.
It is recommended that the standard 5-point scale using the default Acumen Risk Workshop categories and
associated percentage values are used.
Templates can be saved and re-applied to other risk models or applied during different phases of the project
lifecycle.
If a new template is loaded or changes made to the template, you must hit the Apply button in the template editor
for the changes to be reflected in the risk model.
17.1.2 Setting the Uncertainty Loading Level

Once the Uncertainty Factor template has been defined, the level at which you are going to conduct your risk
workshop/risk loading needs to be set. This is done by adjusting the Display Level slider within the Activities View
Mode menu.
Figure 17-2 Setting the Risk Loading Level
Set the level based on the level at which you want to risk load your risk model. The next section describes how,
irrespective of the level that you set, the risk loading process actually applies risk and uncertainty to the entire
schedule. Setting the risk loading level is simply a means of making the risk loading process practical avoiding the
need to manually risk load every single activity within your potentially large schedule.
17.1.3 Assigning Uncertainty

Once the risk loading level has been set, you are ready to define your Uncertainty Factors to your risk model.
To do this, adopt a top down approach using the Uncertainty Factor sliders in the spreadsheet view.
As you assign an uncertainty factor value to any given parent node, you will notice that all children nodes
automatically inherit the same applied Uncertainty Factor category. This top-down inheritance approach results in
an extremely fast means of applying uncertainties to large schedules.
Each time you set a node, it (and its children) become locked so that any subsequent manipulation of uncertainty
values higher up in the schedule hierarchy do not impact the explicit change that you made at the node level.
Figure 17-3 Using the Uncertainty Factor Sliders
Figure 17-4 shows an example of a project that is using the standard Acumen 5-point scale. (refer to Figure 17-1
for the standard scale). The project as a whole has been set to Very Aggressive and thus all activities within the
entire project inherited a Very Aggressive ranking. However, Early Design has been overridden as Very
Conservative - hence all Early Design activities are set to Very Conservative.
Likewise, the FEED group has been set to Conservative and so all FEED activities inherited the same
categorization. However, within the FEED group, EPC Design has been singled out as being Aggressive. Any
subsequent changes to the FEED group (at the group level) wont impact the EPC Design activity until that activity
has its padlock icon released.
This hierarchical approach to uncertainty loading is unique to Acumen Risk and represents a huge step forward in
building risk models in a timely manner.
Manual uncertainty loading can also be adopted by entering three-point estimates and associated distribution
types (triangular, normal, uniform). If an activity is manually loaded, the Uncertainty Factor slider turns grey and
is locked until the slider is re-activated by trying to re-slide the slider.
17.2 Distribution Types

Acumen Risk includes three options for distribution types when modeling uncertainty: Triangle, Normal, and
Uniform. You can define the distribution type for each activity in the activities view or include this as part of the
Uncertainty template set up.
Figure 17-4 Distribution Types
17.3 The Risk Adviser

The Risk Adviser helps to speed up the uncertainty assignment process by suggesting uncertainty ranges for
each activity based on a given criteria.
To set up the The Risk Adviser use the Risk Adviser icon found in the toolbar. Four options are presented:
Schedule Quality: This option presents uncertainty assignments based on the Fuse Schedule Index
score for each activity and activity grouping. By default a score of lower than 10% will warrant a Very
Aggressive assignment. Conversely a score of greater than 75% will lead to a conservative uncertainty
assignment.
Historical Performance: This mode compares the baseline plan to the current schedule and looks for
discrepancies. The greater the variance between the two the more aggressive that activity will be
flagged.
Metric: Select any metric from Fuse to use as the basis for uncertainty assignments.
Field: Select any field from the project to use as the basis for uncertainty assignments.
Once the Risk Adviser has calculated the advice, the recommendations will be shown in the activities view.
Select the icon next to any activity or activity grouping to implement the recommended uncertainties.
Figure 17-5 The Risk Adviser
17.4 Modeling Task Existence
Figure 17-6 Modeling Task Existence
Acumen Risk provides a means of modeling what is known as Task Existence. If you are not 100% certain that a
task is going to happen in your schedule, you can assign a probability to the task to reflect this confidence level
(e.g. Re-work).
17.5 Activity Correlation

This option allows you to select activities within the schedule that may impact one another. Correlate the
uncertainty of one activity to another by first clicking the correlation icon next to the driving activity. A pop-up
window will appear where the driven activities can be selected. Add any activities that should be correlated to
the driver using this window. The uncertainty of the driving activity will then be correlated with any other activity it
has been linked to.
Add Correlation
Figure 17-7 Activity Correlation
Each symbol in the activity correlation column relates to a correlation option.

No correlation has been applied to this activity.
This activity is a driving activity for other correlated activities.
This activity has been included in a set of driven activities linked to a driving activity.
This activity is a driving activity linked to other activities and has also been selected as a
driven activity by another driver.
Figure 17-8 Activity Correlation Settings
17.6 Viewing Uncertainty Distributions

During the Uncertainty loading process, by default, the Gantt chart colors activities based on their uncertainty
ranking. In a similar manner, by clicking on the Views > Right Panel > Uncertainty Inputs, you can interactively
see the distribution of uncertainties as you develop the risk model.
Figure 17-9 Viewing Assigned Uncertainty Distributions
18 Risk Register
Risk events are discrete events (threats or opportunities) that carry both a probability and a potential
cost/schedule impact that may have a potential impact on the schedule/cost of the project. Risk events are
typically captured and modeled in a risk register. Deltek Acumen Risk includes a comprehensive risk register.
The risk register can be viewed by selecting Risk Register from either the Left or Right Panel View menu.
18.1 Defining the Risk Matrix

Before defining risks, a risk scoring matrix needs to be defined. This is done by clicking on the Risk Matrix
Template button.
The following can be defined in the risk matrix:
Number of probability ranges
Number of impact ranges
Number of risk event thresholds
In addition, the values for each of the probability and impact categories can be defined by manually entering
values into the template.
Acumen Risk provides automatic calibration for both scoring and ranging:
Scoring: used to automatically set the values in the Probability/Impact matrix
Ranging: used to automatically set the impact values based on the duration and the cost of the project
Figure 18-1 Defining the Risk Matrix
User defined fields can be added to the risk register and risk register templates can be saved and re-applied to
different project/snapshots.
18.2 Creating Risk Events

Once the risk matrix has been defined, risk events can be added to the risk register. There are two ways this can
be done in Acumen Risk:
Click on the risk matrix icon from within the main spreadsheet view: this will automatically create a new
risk event as well as link it to the activity from which you clicked.
Manually add a risk event from within the risk register
Risk events contain multiple attributes. For a risk analysis, at a minimum, you need to define the following:
Risk ID
Probability: chance of the risk event happening
Schedule Impact: direct impact on the activity/schedule
Cost Impact: direct cost impact on the activity/cost estimate in question
Type: Is it a threat, opportunity, calendar event, or risk window
Further, a risk event can carry both a Current State and Mitigated State. This allows a comparison to be made
between the current risk exposure state and a target state assuming mitigation is carried out.
Figure 18-2 The Risk Register
18.2.1 Risk Event Types

Acumen Risk includes threats, opportunities, calendar events, and risk windows as options for defining the risk
event type.
Threats
A threat is any event that may negatively impact the project. This risk can carry a probability of occurrence, the
likely impact on schedule and/or cost.
Opportunities
An opportunity is any event that may positively impact the project. This risk can carry a probability of occurrence,
a schedule impact and a cost impact.
Calendar Event
A calendar event is a discrete risk event that is tied to a certain period of time. This risk carries a time period
(months of the year in which it could occur) as well as a probability of occurrence for each month. Additionally the
minimum/most likely/ and maximum impacts can be included.
Risk Window
A risk window is a time period that may cause a delay for the project. This risk carries a minimum/most
likely/maximum time period of occurrence.
18.3 Mitigation
As part of defining a mitigated state for a risk, Acumen Risk can also calculate the cost/benefit of executing a
mitigation plan. In order for this to be calculated, a duration and cost overhead of mitigation needs to be defined
against the risk event. Subsequently, when running a risk analysis, alternate scenarios can be generated either
accounting for or ignoring both the impact and/or overhead of executing mitigation.
18.4 Mapping Risk Events to Activities

Risk events need to be mapped to activities/cost elements in order to be included in the risk model. If the risk
matrix icon was used to create a new risk, the risk in question is automatically mapped and no manual mapping is
required.
If a risk event is manually created in the risk register, then it needs to be mapped back to an activity or group of
activities. Risks can be mapped to both individual activities as well as groups/summaries/WBS elements.
One of the unique capabilities of Acumen Risk is the spreading of risk impact across multiple activities upon
mapping to a parent activity. If you map a risk event to say a parent WBS element, then all children activities get
automatically mapped as well. The impact of the risk event gets spread across all children activities and is prorated based on the relative duration/cost of the children. This provides a very fast means of mapping to summary
groups of activities yet still retaining accuracy of the model itself.
Manual risk mapping can be done either from a risk to activity(s) or activity to risk(s) perspective:
18.4.1 Manually mapping a risk to multiple activities

Set the left view panel to Risk Register and the right view panel to Activities. Click on the risk in question and then
use the Mapped column in the activity panel to map the selected risk to multiple activities.
Figure 18-3 Mapping a risk to multiple activities
18.4.2 Manually mapping an activity to multiple risks

Set the left view panel to Activities and the right view panel to Risk Register. Click on the activity in question and
then use the Mapped column in the risk register to map multiple risks to the selected activity.
Figure 18-4 Mapping multiple risks to an activity
Once mapping has been applied, you can optionally override the default mapped impacts through the mapping
table beneath the risk register.
18.5 Importing Risk Registers

Acumen Risk provides an easy means of both importing and exporting a populated risk register from/to external
applications. To export an Acumen Risk risk register, click on the Publish > Export Risk Register to Excel. Once
exported, risks can be edited/added/removed outside of Acumen Risk and then subsequently imported back into
the Acumen Risk risk register using the import feature.
19 Running A Risk Analysis

Acumen Risk uses a Monte Carlo simulation engine as the basis of its risk analytics. The engine is fast and
flexible with the most common and appropriate settings enabled by default.
19.1 Simulation Options

Acumen Risk provides options for setting the number of simulation options. While 1,000 iterations is adequate for
most schedules with an order of magnitude of 1,000 activities, there is the flexibility to set a specific number of
iterations. Further if you select Complete Automatically, Acumen Risk will automatically determine the number of
iterations to run based on a given level of accuracy (as defined in the Automatic Accuracy option).
Figure 19-1 Risk simulation options
19.2 Simulation Scenarios

Multiple scenarios can be generated in Acumen Risk. Four different analysis modes can be run:
Uncertainty only the risk model only takes into account uncertainty and ignores any risk event impact
Uncertainty and Risk Events (No mitigation) the risk model accounts for uncertainty and risk events but
excludes any mitigating impacts
Uncertainty and Risk Events (mitigated excluding overhead) the risk model accounts for uncertainty and
risk events in their mitigated state but ignores the cost/schedule overhead of achieving this mitigation.
Uncertainty and Risk Events (mitigated including overhead) the risk model accounts for uncertainty and
risk events in their mitigated state and takes into account the cost/schedule overhead of achieving this
mitigation.
All four scenarios can be applied to the base risk model or used in conjunction with creating alternate scenarios.
To create multiple scenario risk models, click on the Create Scenario menu option. Acumen Risk will then create
a copy of the currently selected risk model enabling you to subsequently run a what if analysis on the newly
created scenario using potentially different settings such as different scenarios analysis options.
Figure 19-2 Risk simulation scenarios
19.3 Interaction
Acumen Risk can run a risk analysis in three modes:
Automatic: runs the analysis without screen interaction. Benefits from multi threading (very fast)
Interactive: provides real-time screen updates during the analysis
Diagnose: allows you to manually step through each iteration
19.4 Repeatability
Acumen Risk has provision for repeated risk analysis giving the exact same results. This is achieved through
what is known as fixed seed. This option is on by default.
19.4.1 Cost/Schedule Integration

This option is used when running cost risk models and should be enabled if the impact of schedule delay is to be
taken into account in the cost model.
20 Risk Reporting
Reports from a risk analysis can be shown directly in the software by utilizing the view options under Left Panel
and Right Panel.
Figure 20-1 Viewing Risk Reports
Additionally, reports can be printed or copy and pasted to another tool.
20.1 Reporting Risk Exposure (Risk Histogram)

20.1.1 Reporting Cost, Duration, Float, Start, Finish Date Risk Exposure
The risk histogram is used to report the risk exposure. It is driven by the activity or summary that you select in the
activity panel. The histogram shows both a cumulative and non-cumulative chart showing the distribution of
duration, cost, float, start or finish dates for the selected activity.
P-values (probability values) can be added to the chart by clicking on the desired percentage on the right hand
side and selecting add/remove P value. Each time a new P-value is added to the chart, Acumen Risk will
automatically add the P-value data to the table beneath the histogram as well as automatically add it as a column
to the main activity spreadsheet.
Contingency (the difference between a deterministic and P value) can be plotted graphical by also clicking on the
right hand percentage and selecting add/remove contingency. Positive contingency is highlighted in red,
negative contingency (i.e. your estimate has too much contingency built into it) is highlighted in green.
Figure 20-2 Risk exposure report
The histogram can be configured (under the configuration options) to adjust the percentage increments as well as
the cost and duration units. Risk histograms can be exported to other tools either as a chart or as raw data
through the publish menu option.
20.2 Reporting Risk Drivers (Risk Tornado)

The risk tornado chart is used to show the key drivers within a risk model. Unlike older risk tools, Acumen Risk
uses a metric known as Schedule or Cost Contribution Factor that reports drivers in terms of actual cost and
duration rather than abstract relative %-based metrics.
The Acumen Risk tornado also differentiates between logic, uncertainty and risk events when reporting key risk
drivers. Further the Acumen Risk tornado can be configured to report risk drivers at any level of the cost/schedule
hierarchy bringing more meaning to executive risk reporting.
To report risk drivers, click on either a summary activity or an individual activity from within the activity panel. If a
summary activity is selected, then the Risk Drivers tornado will only report activities within the selected summary.
If an individual activity is selected, then Acumen Risk will automatically report only activities leading up to that
given activity.
20.2.1 Reporting Criticality

Criticality is a traditional risk metric reporting how often an activity (or group of activities) falls on the critical path. It
is an indication as to how stable the critical path is as a result of risk and uncertainty. While it is a useful measure
of stability of critical path, it is not a sound measure of which activities are most impacting risk exposure. For this,
use the Cost/Schedule Contribution Factor.
20.2.2 Reporting Schedule & Cost Contribution

Schedule and Cost Contribution are two risk metrics that report the actual schedule/cost impacts on any given
activity (or group) in terms of currency and duration.
Figure 20-3 Schedule Contribution
Schedule Contribution tornado shows which activities are the biggest risk drivers on the selected activity and
more importantly, it reports in terms of duration. Being able to report not just the biggest drivers or hot spots but
also being able to quantify their impact is a huge leap forward in risk reporting.
20.2.3 Risk Drivers Report Configuration

The Risk Drivers chart can be configured to show either summary bars or segmented bars differentiating between
logic, uncertainty and risk events. In detailed mode, the specific driver behind each activitys contribution to the
overall risk exposure profile can be determined. In this mode, Acumen Risk reports as to whether the risk
exposure is a result of preceding logic, the uncertainty of the activity itself or risk events impacting the activity.
Figure 20-4 Detailed risk driver report
20.2.4 Setting the Display Level

One of the capabilities of the Acumen Risk Risk Driver report is the ability to roll up the tornado chart to any given
level within the project hierarchy. This provides flexible reporting as well as eliminating the generation of reports
with inconsistent levels of detail within it.
Detailed Risk Driver Report
Summarized report
Figure 20-5 Rolling up risk driver report
20.2.5 Reporting Risk Event Drivers

In addition to reporting cost and schedule contribution by activity, the Risk Drivers report can be configured to
report the risk events contributing significantly to risk exposure. Under the Contribution drop-down menu select
the option for Mode. Two choices are presented: Activities and Events. Select Events to view the risk events
driving risk exposure.
20.2.6 Publishing/Printing Results

Risk Driver reports can be exported to other tools either as a chart or as raw data through the publish menu
option.
20.3 Risk Sensitivity

The Risk Sensitivity report allows you to evaluate the relationship between durations and/or costs by creating a
scatter chart showing their interaction.
20.3.1 Configuration
The X-axis and Y-axis must be defined in order to use the Risk Sensitivity report. Select the activities and
values for each activity to view their relationship. Once the set up is complete hit the Analyze button to create the
Risk Sensitivity report.
20.3.2 Deterministic Value

Using the checkbox at the bottom of the Risk Sensitivity report optionally turn on or off the Deterministic Value.
This will appear as a blue marker on the report.
20.3.3 Quadrants
Add quadrants to the risk sensitivity view for further insight into the probability of meeting deterministic durations
and/or costs. Figure 20-6 shows a Risk Sensitivity report where the X-axis is Finish Date and the Y-Axis is Cost.
The top left quadrant, for example, shows that during the analysis, 51% of the time Cost was greater than
deterministic while the Finish Date was earlier.
Cost > Deterministic
Cost > Deterministic
Finish < Deterministic
Finish > Deterministic
Cost < Deterministic
Cost < Deterministic
Finish < Deterministic
Finish > Deterministic
Figure 20-6 Risk Sensitivity Report - quadrants view
20.3.4 Joint Confidence Level (JCL)

Gain insight into the probability of meeting cost and schedule commitments using the Joint Confidence Level
(JCL) curve. At the bottom of the Risk Sensitivity report there is an option to turn on or off the JCL view as well as
set the P-Value for the JCL curve. This will show the combined probability of both axis, Cost and Finish Date for
example, at any P-Value.
Figure 20-7 Risk Sensitivity Report showing Joint Confidence Level (JCL)
20.4 Risk Comparison (Comparing Results)

20.4.1 Adding Scenarios
Scenarios can be added to the Risk Comparison Chart by clicking on the Add to Comparison Chart button when
viewing the risk histogram. There is no limit to the number of scenarios that can be added.
20.4.2 Risk Comparison Reporting

From within the Risk Comparison Chart, scenarios can be renamed and annotated by clicking on a given P or
Confidence level within the chart itself. Variances are shown in the table beneath the chart.
Figure 20-8 Risk Comparison
20.4.3 Publishing/Printing Results

Risk Comparison reports can be exported to other tools either as a chart or as raw data through the publish menu
option.
21 Cost Risk Analysis

21.1 Create a new Cost Estimate
A new cost estimate can be created directly within Deltek Acumen Risk in order to perform a cost risk analysis.
Click the Create Cost Estimate icon to begin the process.
This opens a new cost estimate that will automatically be populated with a single activity called New Activity.
Edit the activity name and details directly in this view or by using the fields in the Activity Details Pane.
Edit an activity in the Activity Details Pane
Figure 21-1 Create a new cost estimate
21.1.1 Add New Activities

To add a new activity to the cost estimate use the Add Activity icon found in the Deltek Acumen Risk menu or
right click on any row of the Activities view.
21.1.2 Organizing Activities into a Hierarchy or Cost Breakdown Structure

Activities can be dragged and dropped to create a Cost Breakdown Structure or other hierarchy within the cost
estimate. Select any activity or row within the activities view and simply drag and drop it into the desired grouping.
In Figure 21-2, New Activity 5 was dragged on to the row titled Parent 2. This made New Activity 5 a child of
Parent 2.
Figure 21-2 Create a Hierarchy
Any number of hierarchical levels or groups can be created in the cost estimate. In Figure 21-3 New Activity 5
has been turned into a parent activity by adding a new activity (New Activity 6) and dragging it onto the New
Activity 5 row.
Figure 21-3 Create a New Parent Activity
Any time an activity, or group of activities, is dragged onto another row it becomes a child of that row.
21.2 Importing an Existing Cost Estimate

Acumen Risk includes an Excel-based template called CostRiskTemplate.xls located within the Samples folder.
This should be used as the template file for importing cost estimates into Acumen Risk.
Once the cost estimate is populated into the template file, it can be imported into Acumen Risk using the normal
Excel import feature.
Figure 21-4 Importing a Cost Estimate into Acumen Risk
Once imported into Acumen Risk, follow the normal procedure for building your cost model with uncertainty and
risk events (same procedure as building a schedule risk model). Reports such as Risk Exposure, Risk Drivers and
Comparison Analyzer can all be run against cost models.
Figure 21-5 Cost Risk Analysis Results
The Cost Contribution Metric in the Risk Driver report shows the biggest cost risk drivers in terms of cost rather
than percentages. This is unique to Acumen Risk and provides more useful executive reporting than reporting
abstract relative cost risk drivers.
21.3 Linking Cost & Schedule Risk Models

Acumen Risk provides a fast yet effective means of linking cost and schedule risk models together. Some cost
elements (such as Labor or Project Management) are often time dependent. Acumen Risk offers a means of
linking the schedule risk exposure from either the project as a whole or from specific activities to specific cost
elements within your cost risk model.
This approach eliminates the need for having to cost or resource load a schedule in order to conduct a truly
integrated cost/schedule risk analysis.
The steps for cost/schedule integration are as follows:
1. Build and analyze your schedule risk model
2. Build your cost risk model applying uncertainties and risk events
3. Apply schedule impact to specific cost elements (or the cost estimate as a whole) by clicking on the
Activity Schedule Overlay icon and selecting the desired activities from the schedule model.
4. Run the cost risk analysis ensuring that the Cost/Schedule Integration option is turned on (on by default)
in the Risk Analysis options
Figure 21-6 Applying Schedule Impact to a Cost Model
By using the Risk Comparison Report you can then analyze the additional impact of schedule risk exposure on
your cost risk estimate.
Figure 21-7 Reporting the Impact of Schedule on Cost
22 Building A Risk Adjusted Schedule

Scenarios based on the risk inputs into the risk model and based on risk outputs can be generated.
22.1.1 Scenario based on Risk Inputs

This is useful when needing to re-calibrate a schedule based on the projects team uncertainty rankings. There
are two modes through which this can be achieved (PERT and Median Mode).
PERT uses the PERT algorithm ((max +4*most likely+min)/6 to re-calibrate the schedule/cost model.
Median mode takes the median value between min, most likely and max to re-calibrate the schedule/cost model.
22.1.2 Scenario based on Risk Outputs

This option creates a scenario based on the outputs of a risk analysis. Create a scenario based on any P-Value
from the risk analysis.
Once created, a risk-adjusted schedule can be published back to the scheduling tool or if desired, used as the
basis for building a new risk model.
23 Analyzing Risk Results

23.1 Forensics
The Acumen Forensic analyzer can be used to compare alternate scenarios built during a risk analysis. This is
useful when needing to report differences in risk exposure such as P50 Durations between alternate scenarios.
Figure 23-1 Forensics to Compare Risk Models
23.2 Diagnostics & Risk Metrics in Deltek Acumen Fuse

Acumen Fuse includes two risk metric libraries, Risk Inputs and Risk Exposure. Risk Inputs provide metrics that
give analytics around how the risk model has been put together as well as insight into the teams perception of
risk and uncertainty.
Risk Input Metrics
Risk Exposure Metrics
Figure 23-2 Fuse Metric Analysis on Acumen Risk Results
24 S4 // ACCELERATION: Deltek Acumen 360

Acumen 360 is a schedule remediation and acceleration software. It is used to accelerate or compress project
schedules to meet faster completion deadlines or to get a delayed project back on track. Additionally, 360 can be
used to hypothesize acceleration options or model potential delays.
24.1 How does Deltek Acumen 360 Work?

Acumen 360 runs a CPM simulation running hundreds of iterations progressively accelerating the project towards
a defined goal using sets of user-definable criteria.
There are three options for acceleration:
Automatic, Goal-Based: Define the acceleration target and let Acumen 360 automatically generate the
schedule scenario that meets that goal.
Targeted: Define the acceleration goal and the criteria for acceleration (i.e. accelerate construction
activities by 50%)
Interactive: Accelerate or decelerate individual activities or groups of activities using the duration
calibration sliders.
24.2 Automatic Goal Based Acceleration

Steps for Running a 360 Analysis
1. Define your goal e.g., accelerate by 3 weeks
2. Run the analysis
3. Compare the results; use forensics, timeline, analysis views
24.2.1 Defining a Goal

Defining a goal in Acumen 360 can be done in several ways:
Define the number of days acceleration
Define a target goal date
Define a percentage acceleration
Let Acumen 360 determine the best possible date possible
Project Goal
To define a goal relative to the end of the project, use the Accelerate Schedule tab in the Acumen 360 window
shown in Figure 24-1. Use the goal options (date field or sliding scale) to set the target goal for the acceleration.
Figure 24-1 Defining a Project Goal in Acumen 360
Activity Goal
To define an acceleration goal for a specific activity, use the Accelerate Activity tab in the Acumen 360 window
shown in Figure 24-2. 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.
Figure 24-2 Defining an Activity Goal in Deltek Acumen 360
24.2.2 Advanced Acceleration Settings

Acumen 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.
Figure 24-3 Advanced Acceleration Settings
24.3 Targeted Acceleration

Steps for running a targeted 360 acceleration:
Optionally select schedule cleanse options prior to running an analysis. This will enable the simulation to
create a more naturally flowing and realistic schedule
Select the goal (activity or project) options
Create a new acceleration script or select an existing acceleration script.
Hit the OK button to run the simulation
24.3.1 Defining Criteria Sets (Scripts)

Criteria Sets are contained in what are known as scripts. Scripts contain steps, which are the definitions for rules
and filters for the analysis. Scripts can be edited from either the Acceleration tab in Acumen 360 or by clicking the
Edit Script button in the Acumen 360 window.
Figure 24-4 Script Editor
Scripts can be exported from a workbook and re-used within other workbooks. Additionally, the default script can
be set in the 360 options window. Scripts can also be merged with other script libraries using the merge feature.
24.3.2 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.
24.3.3 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 24-5 shows an example
of a filter that defines all activities within the WBS grouping called Commissioning where the contractor is
ACom.
Figure 24-5 Filter Definition within a Step
24.3.4 Working with Script Templates
Steps are applied to a script by drag-dropping the steps from the step library into the script timeline. The timeline
defines the order in which the steps are applied during the simulation. Drag the steps in the timeline to rearrange
them.
Figure 24-6 Working with Criteria Set Scripts
Figure 24-7 shows an example of the results from an Acumen 360 targeted acceleration. The results show:
Number of iterations run: either the maximum number of runs or the number needed to reach the goal or
the number of runs before the criteria in the script were exhausted
Original, targeted and achieved goal dates
Targeted and achieved acceleration
Total activity reduction: total number of activity days reduced
Schedule Compression efficiency: an index showing how efficient the acceleration is (see white paper
on Acumen website for further explanation of this metric)
The results window also shows whether or not the target has been completely or partially achieved
Figure 24-7 Results from an Acumen 360 Acceleration
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.
24.4 Interactive Acceleration

The interactive acceleration mode of Acumen 360 allows you to accelerate or decelerate activities and
immediately view the impact on the rest of the schedule.
Steps for running an interactive Acumen 360 acceleration:
1. Set up your project view (see chapter 3) to apply acceleration or deceleration to activity groups.
2. Create a scenario for calibration.
3. Use the display level slider found on the Table View dropdown menu to optionally roll-up or expand the
project schedule.
4. Calibrate (add or remove durations) using the duration calibration sliders.
24.4.1 Calibration Overview

You will see duration calibration sliders on each activity row. By default these sliders have 6 calibration levels:
1. Off: No calibration applied
2. Dark Green: Requires Much Less Time
3. Light Green: Requires Less Time
4. Yellow: Realistic
5. Orange: Requires More Time
6. Red: Requires Much More Time
You can change the calibration levels using the Calibration Template option under Scenario Calibration.
24.4.2 Manipulating the Schedule with Calibration

To calibrate the schedule, select an activity row and move the grey slider to the desired level. To see the impact
of that activity taking less time than planned, set it to Light Green (Requires Less Time). You will see the Gantt
chart view adjust to this setting and the finish dates of that activity and any successor activities change.
To see the impact of an activity taking more time than planned, set it to Orange (Requires More Time).
2 Activities within
Commissioning have been set
to Requires Less Time
Accelerating these 2 activities

leads to a 14-day acceleration
on Handover.
Figure 24-8 View the Impact of Acceleration or Deceleration
You can calibrate each individual activity or use the grouping options (See Chapter 3 for setting up the Project
View) to calibrate groups of activities.
Calibration applied to a parent row automatically cascades down to the children of that row. If you want to set
exceptions, or activities that do not follow their parent, simply re-set the calibration slider on that activity. You will
notice that the lock icon next to that activity is enacted. Now, if you were to adjust the calibration of the parent, all
activities would follow except for the locked activity.
Manufacturing and
all of its children
have been set to
Requires More
Time
Phase 2 has been

flagged as an
exception and set as
Realistic
Figure 24-9 Calibration Settings Cascade Down to Children Activities
24.5 The Schedule Realism Adviser

The Schedule Realism Adviser provides suggestions for calibrating each activity based on a given criteria.
Select the Schedule Realism Adviser icon to define how the adviser should calculate suggestions. Four options
are presented:
Schedule Quality: This option presents uncertainty assignments based on the Fuse Schedule Index
score for each activity and activity grouping. By default an activity with a score of lower than 10% will be
flagged as needing more time than planned. Conversely an activity with a score of greater than 75% will
be flagged as needing less time than planned.
Historical Performance: This mode compares the baseline plan to the current schedule and looks for
discrepancies in order to suggest which activities should be accelerated.
Metric: Select any metric from Fuse to use as the basis for acceleration suggestions.
Field: Select any field from the project to use as the basis for acceleration suggestions.
View and
implement Adviser
suggestions for
calibration.
Figure 24-10 Using the Schedule Realism Adviser
Once the Schedule Realism Adviser has calculated the advice, the recommendations will be shown in the
activities view. Select the icon next to any activity or activity grouping to implement the recommended calibration
settings.
24.6 Analyzing the Results

The newly created scenarios can be analyzed using any of the standard analysis features within Acumen Fuse
including Forensics, timeline view and the Fuse diagnostics view. Acumen 360 includes a metric library called
Scenario Comparison that contains a set of metrics pertaining to scenario comparison analysis.
Figure 24-11 Results from an Acumen 360 Acceleration
24.7 Publishing Scenarios

Deltek Acumen 360 scenarios can be published to MS Project And Primavera using the publish button in the
projects view or by right clicking on the project name.
25 S2 // BENCHMARKING: Project Scoring and Ranking

The S2 // Benchmarking tab performs a benchmark analysis of the project including:
Standardized project scoring using the Fuse Schedule Index
Benchmarking against other projects across the world using Acumen Cloud
Forecasting of project success
25.1 Deltek Acumen Cloud Overview

Acumen Cloud is a web-based repository of results generated from running Fuse analyses. Acumen Cloud is
included as part of a Deltek Acumen Fuse license and is an optional module activated through an end-user opt-in
process as part of installation.
Figure 25-1 S2 // Benchmarking
25.2 Project Benchmarking

To run an Acumen Cloud benchmark analysis, go to the S2 // Benchmarking tab and select a metric library to
use for the analysis.
Figure 25-2 shows the flow of data during a benchmark analysis. Firstly, the analysis on your project is conducted
locally within Deltek Acumen. The results of the analysis are then securely (using Secure Socket Layer/SSL) and
anonymously sent to a cloud-based repository called Deltek Acumen Cloud. The project schedule itself is NOT
sent to the cloud. Acumen Cloud does not store project-specific attributes such as project name, type, owner,
author etc. Instead only the resultant score from running a Fuse analysis is stored. This data is then used to
compare against other calculated project scores also stored in the cloud.
Figure 25-2 Acumen Cloud Architecture
25.3 Scoring, Benchmarking & Forecasting

Three results are generated from a Deltek Acumen Cloud analysis:
Scoring: a standardized score in the form of an index is generated. This score is based on a standard set
of metrics that cannot be editing or re-weighted by an end-user. By adopting this standardization, projects
can be anonymously compared using the same scoring system. As a target, you should aim for 75 and
above with any Fuse Index score.
Benchmarking: while Fuse Indices give good insight into the quality of a plan, being able to compare
how your project ranks with other similar projects is even more valuable. Acumen Cloud automatically
calculates where in the population your project lies. This is presented in the form of a percentile e.g. you
rank in the top 60 percentile.
Forecasting: based on years of project benchmarking, Acumen is now able to deliver true benchmarking
in the form of forecasting project success. This is achieved by comparing your project score to other
completed projects with a similar score and examining how they fared with regards to on-time completion.
Based on an established correlation between quality of plan and chance of execution success, Acumen
Cloud is able to provide a forecast as to the probability of your project having an on-time completion.
Figure 25-3 shows an example of a project that scores 74 against the Fuse Schedule Index, ranking in the top
88th percentile of the population resulting in a 75% chance of completion on time.
Figure 25-3 Scoring, Benchmarking, and Forecasting
25.4 Fuse Schedule Index

The Fuse Schedule Index is a means by which projects can be scored with regards to their quality of plan. The
Fuse Schedule Index is based upon nine core metrics that all pertain to the overarching quality of a plan. Each
of these nine metrics are weighted according to importance to quality.
Missing Logic
In theory, all activities should have at least one predecessor and one successor associated with them. Failure to
do so will impact the quality of results derived from a time analysis as well as a risk analysis. This number should
not exceed more than 5%.
Logic Density
This metric calculates the average number of logic links per activity. An average of less than 2 indicates that there
is logic missing within the schedule. An average greater than 4 indicates overly complex logic, with a high
likelihood of redundant links. Therefore, Logic Density should be between 2 and 4.
Critical
While a highly critical schedule is not necessarily a sign of poor scheduling, it can indicate a highly risky schedule.
Use this metric as a point of reference.
Hard Constraints
Hard, or two-way constraints, such as Must Start On or Must Finish On should be avoided. Use of such
constraints can lead to inaccurate finish dates and a lack of insight into the impact of schedule changes, risk
events, and earlier delays.
Negative Float
Negative float is a result of an artificially accelerated or constrained schedule, and is an indication that a schedule
is not possible based on the current completion dates.
Insufficient Detail
Activities with a high duration relative to the life of the project are an indication of poor schedule definition. Detail
should be added to the schedule.
Number of Lags
A lag is a duration applied to a logic link often used to represent non-working time between activities such as
concrete curing. Lags tend to hide detail within the schedule and cannot be statused like normal activities;
therefore, lags should be converted to actual activities with durations.
Number of Leads
A lead, also known as a negative lag, is often used to adjust the successor start or end date relative to the logic
link applied. This is a poor practice as it can result in the successor starting before the start of the predecessor.
Merge Hotspot
Also known as merge bias, a merge hotspot is an indication as to how complex the start of an activity is. If the
number of links is greater than two, there is a high probability that the activity in question will be delayed due to
the cumulative effect of all links having to complete on-time in order for the activity to start on time.
25.5 Fuse Logic Index

The Fuse Logic Index is a cloud-based metric library that gives insight into the logic quality of a schedule. Logic
is viewed as one of the most important underpinnings of a schedule.
Redundancy Index
A redundant, or unnecessary logic link, is a link between two activities made redundant by an additional, often
more complex, logic link between the same two activities. A high Redundancy Index is a sign of an overly
complex schedule, which should be simplified.
Open Ends
A high number of activities missing either a predecessor, a successor, or both signals a poorly developed plan.
This number should be less than 5% of the schedule.
Open Starts
If the start of the successor activity is left open, with the predecessor activity tied to the finish of the successor, the
result is an open start or 'dangling activity.'
Open Finishes
If the finish of the predecessor activity is left open, with the predecessor tied by its start to the successor, the
result is an open finish or 'dangling activity.'
Leads
A lead, also known as a negative lag, is often used to adjust the successor start or end date relative to the logic
link applied. This is a poor practice as it can result in the successor starting before the start of the predecessor.
Lags
A lag is a duration applied to a logic link often used to represent non-working time between activities such as
concrete curing. Lags tend to hide detail within the schedule and cannot be statused like normal activities;
therefore, lags should be converted to actual activities with durations.
SF Links
A high number of SF links is indicative of a well-developed plan.
Figure 25-4 Fuse Logic Index
25.6 Metric Percentile Analysis

As well as generating overarching Indices, Acumen Cloud also analyses how you rank with regards to each
individual metric score. The percentile analyzer shows not only each metric score, but in addition, the red
indicator shows how you rank against the rest of the population. This is very useful when pinpointing root cause of
a poor Index score.
Figure 25-5 Metric Percentile Analysis
25.7 Points of Note

Acumen Cloud analysis is automatically triggered when a different project is selected from the project browser
on the left-hand side of the view.
If the same project is repeatedly analyzed, Fuse will update the score in the cloud for this project; it will not create
multiple separate entries.
Aim for an index and percentile score of 75 or above. The Acumen Cloud histogram is color-coded (red,
orange, yellow and green). The color segments represent the 25th percentile, 50th percentile, and the 75 and
above percentile.
26 Custom Field Mappings

26.1 Introducing Field Mapping
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.
List A
Source
Fields for
Project A
Project
A
Project
B
Mapped
Mapped
Fields
Fields
Project
C
Project
D
Mapped
Mapped
Fields
Acumen Fields
Fields
6 26-1 The Fields View
Figure 26-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 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 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. The bold
field names cannot be edited, but can have customized mappings assigned to them. The center columns 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 field called Baseline Work in Figure 26-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 normalizes these fields even though the field names
are actually different. Within your workbook, this field is then referred to as Baseline Work.
Acumen field mapping provides the flexibility to have different custom mappings from each of your data sources
to a common fieldin effect, standardizing data from multiple platforms that may have very different data
schemas.
26.2 Editing Field Mappings

Field mappings are edited as follows:
7. Select the data source. Before you can map a field, Acumen has to retrieve all the available fields for the
project in question. To update the available field list, click on the desired project (in Figure 26-2) this
would be either of the two columns showing Project A and Project B.
8. Select the desired field. The source fields are grouped into Standard, User Defined and Code fields. Click
on the relevant header to reveal the fields for the required field type.
9. Assign the field. Drag-drop the required field to either an existing Acumen field or a blank row to create a
completely new field in your workbook.
Figure 26-2 Creating Custom Field Mappings
26.3 Editing Field Names

When adding a new source field to your list of fields, by default, Acumen adopts the same field name as that of
the source. However, fields can be renamed by editing the field name directly within the table. The exception to
this rule is the list of Acumen fields that are highlighted in bold type (ID, Description, Critical, Percent Complete,
Start, Finish).
26.4 Deleting Fields

Any of the non-bold type faced Acumen fields can be deleted by clicking Activity Fields > Delete.
26.5 Deleting Field Mappings

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
Figure 26-3 Deleting Custom Field Mappings
26.6 Minimum Fields Required

In order to draw activities and ribbons in the ribbon analyzer view, only the Start and Finish fields need to
contain valid data. In reality though, in order to obtain useful results from the analysis, at a minimum, the standard
default mapped fields should be populated.
26.7 Working with Field Types

The custom field mapping enables fields of different types to be matched with each other. During analysis,
Acumen 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.
26.8 Field Mapping

26.8.1 Mapping a Field to Multiple Data Sources
If your workbook contains multiple projects or snapshots, you can map a single field (standard, user, code) to all
projects or 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 Map to All Projects
Figure 26-4 Map to All Projects
26.8.2 Map all Code Fields for this Project

If you need to map all code fields from a source project or snapshot, you can use 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 Acumen.
26.8.3 Map all Code Fields for all Projects

If you need to map all code fields from a source project or snapshot to multiple projects, you can use Source
Fields > Map All Code Fields for all Projects to assign all code fields all the projects in the workbook in a single
click. Acumen 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 Acumen.
26.8.4 Map all User fields for All Projects

If you need to map all User fields from a source project/snapshot to multiple projects, you can use Source Fields >
Map All User Fields for all Projects to assign all user 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 Acumen.
26.8.5 Load Default Mapping

To reset field mappings within a workbook, click on the Load Default Mapping button.
26.8.6 Field Mapping Context

Each workbook contains its own field-mapping template. Each project or snapshot within a workbook also has its
own mapping values back to the fields within the workbook template.
26.8.7 Mapped Fields and Metrics

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.
26.9 Standard Field Mappings

Acumen 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
Original Duration
Remaining Duration
Percent Complete
MS Project
Primavera P6
ID
Activity ID
Name
Activity Name
Calculated
Primavera Risk
Analysis
Open
UN/CEFACT
Plan
ID
Activity ID
ProjectScheduleTas
k.Name
Description
Description
Activity Desc.
ProjectScheduleTas
k.Description
Activity Type
Task Type
Calculated
Activity Type
ProjectScheduleTas
k.TypeCode
Critical
Critical
Critical
NA
Critical_Activity
ProjectScheduleTas
k.CriticalPathIndicat
or
Duration
Original Duration
Original Duration
NA
Original Duration
TotalDurationMeasur
e
NA
Computed
Remaining Dur.
ProjectScheduleTas
k.RemainingDuration
Measure
Remaining Duration
Remaining
Duration
ID
Deltek Cobra
Remaining
Duration
% Complete
Calculated
Percent Complete
NA
Calculated
ProjectScheduleTas
k.CalculatedComplet
ionPercent
Start
Start
Start
Start
Start
Early Start
CurrentScheduledBa
sePeriod.Start
Finish
Finish
Finish
Finish
Calculated
Early Finish
CurrentScheduledBa
sePeriod.Finish
Actual Start
Actual Start
Actual Start
Actual Start
NA
Actual Start
ActualScheduledBas
ePeriod.Start
Actual Finish
Actual Finish
Actual Finish
Actual Finish
NA
Actual Finish
ActualScheduledBas
ePeriod.Finish
Baseline Start
Baseline Start
Planned Start
Baseline Start
NA
Baseline Start
TargetScheduledBas
ePeriod.Start
Baseline Finish
Baseline Finish
Planned Finish
Baseline Finish
NA
Baseline Finish
TargetScheduledBas
ePeriod.Finish
Early Start
Early Start
Early Start
Early Start
NA
Early Start
EarliestScheduledBa
sePeriod.Start
Early Finish
Early Finish
Early Finish
Early Finish
NA
Early Finish
EarliestScheduledBa
sePeriod.Finish
Total Float
Total Slack
Total Float
TotalFinshFloat
NA
Total Float
ProjectScheduleTas
k.TotalFloatDuration
Measure
Baseline Work
Budgeted Labor
Units
Calculated
NA
NA
NA
Actual Cost
Actual Cost
Calculated
Cost[Actual]
NA
Calculated
NA
Budget Cost
Baseline Cost
Calculated
Cost[Budget]
NA
Calculated
NA
Remaining Cost
Calculated
Cost[Remaining]
NA
ETC
NA
Cost
Calculated
Cost[Total]
NA
Calculated
NA
Number of Predecessors
Calculated
Calculated
Calculated
NA
Calculated
Calculated
Number of Successors
Calculated
Calculated
Calculated
NA
Calculated
Calculated
Number of FF
Predecessors
Calculated
Calculated
Calculated
NA
Calculated
Calculated
Number of SF
Predecessors
Calculated
Calculated
Calculated
NA
Calculated
Calculated
Number of SS
Predecessors
Calculated
Calculated
Calculated
NA
Calculated
Calculated
Number of Lags
Calculated
Calculated
Calculated
NA
Calculated
ProjectScheduleTas
kRelationship.LagTi
meMeasure
Number of Leads
Calculated
Calculated
Calculated
NA
Calculated
Calculated
Project Start
Start Date
Start
Start
NA
Project Start
NA
Project Finish
Finish Date
Finish
Data Date
NA
Scheduled Finish
NA
Project Time Now
Status Date
Data Date
Finish
NA
Time Now
NA
Status
Activity Status
Calculated
NA
Progress Type
Calculated
Activity Constraint
Constraint Type
Primary Constraint
Constraint Type
NA
Calculated
NA
WBS Code
Outline Number
WBS
Work Breakdown
Structure
WBS Code
NA
NA
WBS Name
Outline Number
WBS Name
Work Breakdown
Structure
WBS Name
NA
NA
ACWP (AC)
ACWP
ACWP
ACWP (AC)
NA
NA
BCWP (EV)
BCWP
BCWP(EV)
Calculated
BCWP (EV)
Calculated
NA
BCWS (PV)
BCWS
Calculated
NA
BCWS (PV)
NA
NA
EAC
EAC
NA
EAC
NA
NA
NA
NA
NA
LIKELY
NA
NA
Baseline Work
Remaining Cost
Total Cost
Activity Status
EAC
LIKELY
CAM-EAC
NA
NA
NA
CAM-EAC
NA
NA
PLAN_ACC
NA
NA
NA
PLAN_ACC
NA
NA
ETC
NA
NA
NA
ETC
NA
NA
MOD
NA
NA
NA
MOD
NA
NA
OTB
NA
NA
NA
OTB
NA
NA
REPLAN
NA
NA
NA
REPLAN
NA
NA
WORST
NA
NA
NA
WORST
NA
NA
Risk Input - Duration

Description
NA
NA
Calculated
NA
NA

LowerPcent
NA
NA
Calculated
NA
NA
NA
Risk Input - Duration Max
NA
NA
Risk input- Duration

Maximum
NA
NA
NA
Risk Input - Duration Mean
NA
NA

Mean
NA
NA
NA
Risk Input - Duration Min
NA
NA

Minimum
NA
NA
NA

MostLikely
NA
NA

MostLikely
NA
NA
NA

MostLikelyPcent
NA
NA
Calculated
NA
NA
NA
Risk Input - Duration Notes
NA
NA

Notes
NA
NA
NA
Risk Input - Duration Risk

Distribution
NA
NA
Calculated
NA
NA
NA

RiskFunction
NA
NA
Calculated
NA
NA
NA
Risk Input - Duration RiskId
NA
NA
Calculated
NA
NA
NA

RiskOn
NA
NA
Calculated
NA
NA
NA
Risk Input - Duration Shape
NA
NA
Calculated
NA
NA
NA

StdDeviation
NA
NA
Calculated
NA
NA
NA

UpperPcent
NA
NA
Calculated
NA
NA
NA
Risk Input - Probabilistic

Description
NA
NA
Calculated
NA
NA
NA

Notes
NA
NA
Calculated
NA
NA
NA

RiskFunction
NA
NA
Calculated
NA
NA
NA

RiskId
NA
NA
Calculated
NA
NA
NA

RiskOn
NA
NA
Calculated
NA
NA
NA

Links Description
NA
NA
Calculated
NA
NA
NA

Links Notes
NA
NA
Risk Input Probabilistic Links

Notes
NA

Links RiskFunction
NA
NA
Calculated
NA

Links RiskId
NA
NA
Calculated
NA
NA
NA

Links RiskOn
NA
NA
Calculated
NA
NA
NA
Risk Input - Task Existence

Description
NA
NA
Calculated
NA
NA
NA

Notes
NA
NA
Risk Input - Task

Existence Notes
NA
NA
NA

RiskFunction
NA
NA
Risk Input - Task

Existence Function
NA
NA
NA

RiskId
NA
NA
Calculated
NA
NA
NA

RiskOn
NA
NA
Calculated
NA
NA
NA

Probability
NA
NA
Risk Input - Task

Existence
NA
NA
NA
P50 Start
NA
NA
P50 Start
NA
NA
NA
P80 Finish
NA
NA
P80 Finish
NA
NA
NA
P50 Finish
NA
NA
P50 Finish
NA
NA
NA
P50 Cost
NA
NA
P50 Cost
NA
NA
NA
P80 Cost
NA
NA
P80 Cost
NA
NA
NA
Risk Output CostSensitivity
NA
NA
Risk Output CostSensitivity
NA
NA
NA
Risk Output CostStdDeviation
NA
NA
Risk Output CostStdDeviation
NA
Risk Output
CriticalityIndex
NA
NA
Risk Output
CriticalityIndex
NA
NA
NA
Risk Output - Duration
NA
NA
Risk Output Duration
NA
NA
NA
Cruciality
NA
NA
NA
NA
NA
NA
Cruciality
Risk Output DurationStdDeviation
NA
NA
Risk Output DurationStdDeviatio

n
NA
NA
NA
Risk Output
DurationSensitivity
NA
NA
Risk Output
DurationSensitivity
NA
NA
NA
Risk Output MeanCost
NA
NA
Risk Output
MeanCost
NA
NA
NA
Risk Output
MeanDuration
NA
NA
Risk Output
MeanDuration
NA
NA
NA
Risk Output - MeanFinish
NA
NA
Risk Output MeanFinish
NA
NA
NA
Risk Output MeanStart
NA
NA
Risk Output
MeanStart
NA
NA
NA
Risk Output PercentageTaskExisted
NA
NA
Risk Output - %
Iterations Existed
NA
NA
NA
Risk Output ScheduleSensitivityIndex
NA
NA
Risk Output ScheduleSensitivityI

ndex
NA
NA
NA
27 System Requirements
Acumen is a Windows application. It requires no backend database installation. System requirements are as
follows:
Microsoft Windows XP Home or Professional Service Pack 3, Windows Vista, Windows 7,

Windows 8, Windows Server 2008, Windows Server 2003. Server installations require concurrent
licensing.
Microsoft .NET Framework version 4.0 SP1 (included as part of Fuse installer)
DirectX 7.0 (9.0 or higher recommended)
Memory: Minimum 1 GB RAM, recommended 2 GB RAM.
Processor: Minimum 1 GHz.
Hard Drive Space required: 40 MB
Mac OS X requires Parallels or VMWare
28 Installation
The Acumen installer uses Microsoft ClickOnce technology which provides a seamless means of installing and
maintaining updates to Acumen without the need for complex and often prohibitive administrative rights to your
computer.
To install Acumen, 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 license key. Upon successful validation, you will be ready to run Acumen.
Acumen includes sample files and documentation. These can be found in the Acumen Fuse folder within your
Documents folder on your PC.
29 Automatic Updates
Deltek Acumen 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 Acumen
installed. An Internet connection is required in order to receive these updates. Automatic updates can be disabled
in the Options menu of Acumen.

Deltek Acumen

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Deltek Acumen

Uploaded by

Copyright:

Available Formats

Deltek l Acumen

2.3.5 Deltek Open Plan .................................................................................................................................. 22

2.3.8 Deltek Cobra CAP Earned Value Data .................................................................................................. 23

4 Introducing Deltek Acumen Fuse .................................................................................................................... 43

5.1 Navigation ...................................................................................................................................................... 51

9 Managing Metrics ............................................................................................................................................... 75

9.11.1 Defining Variables ................................................................................................................................. 86

16 S3 // RISK: Project Risk Analysis .................................................................................................................. 112

20.2.3 Risk Drivers Report Configuration ....................................................................................................... 129

24.4.2 Manipulating the Schedule with Calibration ........................................................................................ 148

1 Overview of the Deltek Acumen Software Suite

1.1 Whats Included

Integration with all major planning tools

DCMA 14 Point Assessment

Schedule Quality Analysis

Schedule Risk Analysis

Cost Risk Analysis

Forensic Analysis/Schedule Comparison

1.2 Navigating through the Deltek Acumen Software Suite

S2 // Logic: Advanced logic checks. Available in Deltek Acumen Fuse

S2 // Benchmarking: Comparison of project data to cloud-based database of similar projects. Available

S5 // Dashboard: Reporting dashboard. Available in all three Deltek Acumen products.

Figure 1-1 Navigation through the menu bar

Figure 1-2 File Management Menu

1.2.1 The S1 // Projects Tab

Figure 1-3 The Projects View

1.2.2 The S2 // Diagnostics Tab

Ribbon analyzer: graphical/tabular view of analysis results for each ribbon

Phase analyzer: graphical/tabular view of analysis results for each phase

Activity Browser: tabular/Gantt/scorecard/heat map chart view of activities/results

Figure 1-4 The S2 // Diagnostics Tab

1.2.3 The S2 // Logic Tab

Figure 1-5 The Logic Analysis View

1.2.4 The S2 // Benchmarking Tab

Figure 1-6 S2 // Benchmarking Tab

1.2.5 The S3 // Risk Tab

Figure 1-7 S3 // Risk Tab

1.2.6 The S4 // Acceleration Tab

Figure 1-8 S4 // Acceleration Tab

1.2.7 The S5 // Dashboard Tab

Figure 1-9 The Dashboard View

1.2.8 The Forensics Tab

Figure 1-10 The Forensics View

1.2.9 The Metrics Tab

Metrics contain four properties:

1.2.10 The Fields Tab

1.3 Integrating With Project Management Platforms

MS Project 2003/2007/2010, MS Project Server 2007 and above

Primavera P6 (versions 5.x, 6.x, 7.x and R8)

Oracle Pertmaster/Risk Analysis V8.x

Deltek Open Plan V3.x

Deltek Cobra (Earned Value)

Phoenix Project Manager

Figure 1-13 Supported Platforms

2 Working With Deltek Acumen Workbooks

Imported project data

Metric libraries and metrics

Custom field mappings

2.1 Workbook File Formats

2.1.1 Standard File Format

2.1.2 XML File Format

2.2 Creating a New Workbook

Figure 2-1 Creating a New Acumen Workbook

2.2.1 Metrics within a Workbook