Economic Analysis
Key Concepts
Alternatives Analysis
Time Value of Money
Cost and Benefit Analysis
EA Process
What is Economic Analysis (EA)?
Economic Analysis (EA) is an objective study performed to
compare the costs and benefits of multiple alternatives.
EA aims to:
Because two key components of an EA are the cost estimate
and the benefits estimate, it is sometimes referred to as a
Cost Benefits Analysis (CBA).
Why Conduct an EA?
Time-phased Cost and Benefits
Decision Making
Assess Timing
of Funding
Economic Analysis (EA) is an objective study performed to compare the costs and benefits of multiple alternatives.
EA aims to:
*provide decision makers with the data needed to select the best solution for solving a problem or accomplishing a given objective or set of objectives;
*compare time-phased, economically-adjusted costs and benefits of
solutions/alternatives for a defined problem/objective; and
*assess the timing of costs and benefits and adjust the data economically for the
present value of money.
Because two key components of an EA are the cost estimate and the benefits
estimate, it is sometimes referred to as a Cost Benefits Analysis (CBA). However,
governing documents vary by each organization with some organizations
distinguishing between the two, while others view them as the same.
The primary purpose of EA is to facilitate
decision making.
Even when not required, EA can benefit programs when:
Even if an EA is not required, conducting one can be very beneficial, especially if:
*there is more than one competing objective or problem to address, or
*there is more than one competing alternative which addresses a given problem or objective.
The EA process facilitates the identification and thorough examination of all possible solutions to a given problem. By conducting an EA, an organization can better
allocate resources among competing programs or a program can select a solution that best meets its needs.
Decision-making support is the primary benefit of EAs. Another key benefit is objective documentation as to why a given alternative was chosen, thus making the decision more defensible. An EA also provides a baseline of data against which program execution can be measured
There are considerable dependencies between each
step, with green arrows representing possible
feedback to prior steps.
Objective
assumptions
Alternatives
Cost/Benfit estimates
Compare alternatives
Sensitivity Analysis
Recommendation
There are considerable dependencies between the EA steps, and it is common to revisit steps as the analysis progresses. Analysts should continually revisit earlier
steps and recalibrate to the objective. The orange arrows show the primary path
from setting the objective to the final recommendation, and the green arrows show possible feedback to previous steps.
Risk and uncertainty should also be addressed while developing an EA. The EA
process does not specifically address risk and uncertainty completely, but any good
analysis inherently includes them.
Step 1: Objective
* Define the objective
The Objective is the key to a successful EA. If an objective is ill‐defined, EA results will be questionable. Therefore, it is important to spend time properly addressing this first step.
The Objective usually highlights a problem or new mission need. The statement should be
broad enough not to constrain the analysis unnecessarily. At the same time, it needs to be narrow enough to focus the analysis on a discrete number of relevant alternatives.
Care should be taken to ensure it does not presuppose one of the alternatives.
Step 2: Assumptions & Ground Rules
* Formulate assumptions and ground rules
Examine problem thoroughly
* Develop complete list of assumptions and ground rules
* Mathematical/methodology assumptions
* Limits of analysis based on problem characteristics
* Address both strict constraints and assumptions of convenience
* Scrutinize assumptions for relevancy, necessity, and reasonableness
The next step in the EA process is to formulate and examine the assumptions. To develop assumptions, one must understand the problem well.
The assumptions will generally fall into one of two categories: mathematical or
methodological assumptions which govern the mechanics of the analysis; or “limits of
analysis”‐type assumptions which capture constraints that limit the analysis. Often
assumptions will be made out of convenience rather than being strict constraints directly
connected to program or external realities.
Note that often assumptions are gathered slowly as the analysis is conducted because not
all assumptions are known up front. Regardless of when an assumption is identified, the
assumptions should be scrutinized for relevancy and reasonableness.
Documenting and defining all assumptions well is critical to conducting a sound EA. . If too
many or too strict assumptions are used, the ideal solution could be overlooked. On the
other hand, if assumptions are poorly‐defined, analysis could be too loosely bounded to
produce effective results. Assumptions should be confirmed to confirm relevancy, validity
and appropriateness.
Finally The status quo should be considered a viable option even if it is not the desired solution.
Step 3: Alternatives
* Identify and examine alternatives
Examine problem with the assumptions to help identify
possible solutions
* Develop alternatives without boundaries
* Examine alternatives for unfeasible options
* Document reasons for eliminating alternatives in case
circumstances change to cause an alternative to be viable again
* Note that alternative list may change during analysis
Now that we have a solid objective and a preliminary set of assumptions, we can begin to define the candidate alternatives
It’s important to include all possibilities, then downselect. Equally important is the need
not to limit the brainstorming
Once a candidate list is developed, the alternatives can be examined for infeasibilities. All
alternatives, including those eliminated, should be documented. Sometimes an eliminated
alternative becomes feasible in the future, and since most EAs are updated with each
review, there are opportunities for alternatives to make it back on the list.
Note that cost alone should not be a reason for determining an alternative is infeasible. If
there are significant reasons that make an alternative not favorable due to costs, this will
come out in the cost analysis
Minimum Number of Alternatives
* Must always have at least two alternatives
Number of Alternatives
* Can have many alternatives
* Often have more than one variant of new acquisition or
modernization
* As number of alternatives increases, so does time and
effort required to develop cost and benefits
* Important to consider everything, but…
* Consider factors for down-selecting early if analysis
proves to be cumbersome or too exhaustive
However, an EA is not limited to four alternatives.
Often there is more than one “new acquisition” option to consider, or more than one type
of “modernization.” One word of caution, however: as the number of alternatives
increases, so does the time and effort involved in conducting the EA, especially the next
step of developing cost and benefit estimates.
Also, if there are too many options, some are likely to be “too similar,” and it will not be
clear which is the best alternative – ranking may be too close to formulate strong
recommendations. The bottom line is that it is important to consider the pros and cons to
the number of alternatives before deciding on a list to analyze.
Common Alternatives
* Many variants of binary alternative pair
* Examples include:
* Repair or replace
* Buy or lease
* Manual or automated
* Make or buy
* Centralize or decentralize
* Centralized or distributed architecture
* Status quo or system A or system B
There are many variants of the basic binary pair of EA alternatives, Status Quo and
Alternative. Should you repair an old system to keep it in service or should you get rid of it
and replace it with a new one? When acquiring a new system, should you buy or lease it?
Should you implement (or stick with) a manual process, or should you automate it? Should
you make a new item within your organization, or should you buy it from another
organization? Should you centralize a function within your organization, or should you
decentralize?
As you can see, the possible set of alternatives to which EA can be applied is nearly
boundless. Commonly, the Status Quo can be compared with at least a couple of new
system alternatives – call them System A and System B.
Step 4: Cost and Benefits Estimates
* Develop cost and benefits estimates:
* Define cost and benefits estimating parameters (or
mathematical assumptions)
* Develop comprehensive cost estimate for each alternative
* Define and quantify benefits for each alternative
* Cost and benefit estimating involves several non-
trivial sub-steps
* Cost and benefit estimates are important as they serve
as the objective basis for comparing alternatives
Once the alternatives have been defined, the cost/benefits estimates can be developed.
This is the most analytical and time‐consuming part of the EA process. It often involves
extensive data gathering and analysis, including interviews with future users, program
personnel, and other people with knowledge of the problem or new mission.
The first major step in the process is to define the estimating parameters. This step
involves determining mathematical and methodological rules that will govern the analysis.
More details will be provided on the next slide.
Once parameters have been developed, the cost/benefits estimates must be developed for
each alternative. Developing the estimates will involve data gathering and analysis,
development of CERs, and other activities that are not covered in detail in this module. The
portions of estimating specifically related to an EA are discussed in more detail in upcoming
slides.
The Cost and Benefits Estimate are important to the EA process as they provide the
mathematical foundation for comparing and ranking the alternatives. This is the
quantitative, analytical, and objective heart of the EA process, and we’ll spend a good bit of
this module exploring it. If the estimates are poorly done, a decision could be made to
implement a non‐optimal solution. Contrariwise, if the estimates are done well, thedecision‐maker can be confident that the alternative selected is the best one given all the
circumstances.
Estimating Parameters
* Define estimating parameters (mathematical assumptions)
* Determine economic life cycle for each alternative
* Economic life cycle is period during which alternative provides benefits
* Usually constrained by:
* Physical life,
* Mission life, and/or
* Technological life
* Determine period of analysis for each alternative
* Period of analysis is the time required to develop/implement the
alternative plus the economic life during which benefits accrue
* Economic life cycles and periods of analysis can differ between
alternatives
An important estimating parameter to establish is the Economic Life Cycle of an
alternative. The economic life cycle is defined as the period during which an alternative is
providing benefits. It is usually constrained by the system physical life, mission life, and/or
technological life.
Physical life is the time a system will work before physically wearing out.
Mission life defines how long a system will support a mission before the mission either
changes or is no longer required.
The end of technological life is defined as the time when the technology becomes
obsolete.
Once an economic life is defined for each alternative, the Period of Analysis for each
alternative can be defined. The Period of Analysis is the Economic Life plus any lead time
required to develop the system or get it implemented in order to provide the benefits. For
military systems, the lead time is usually defined by when the project will achieve Initial
Operating Capability. At IOC, most systems begin to offer some benefits.
Note that alternatives can and frequently do have different economic lives and periods of
analysis. This information is taken into consideration when determining the EA Period of
Analysis, which we turn to next.
Parameters – EA Period of Analysis
* When alternatives have differing periods of analysis, need to
determine what the common period of analysis will be for
comparing the costs and benefits
* Options include:
* Shortest life: estimate residual value for alternatives with
longer lives
* Common denominator life: assume replacement of worn
out material and equipment and chain together multiple
economic lives until reach point where all alternative end
concurrently.
* Uniform annual cost: economically adjusts dollars to
account for different life cycles between alternatives – more
discussion later
Once the Economic Lives and Periods of Analysis are determined for all alternatives, the EA
Period of Analysis can be defined. Usually one of the following methods is employed:
*Shortest Life, which sets the EA period of analysis equal to the shortest period of analysis
for all the alternatives. Because the analysis is confined to a period of time that does not
account for all of the benefits in the other alternatives, Residual Value for other
alternatives is estimated and included in the benefits estimate.
*Common Denominator Life, which assumes that the systems will continue to replace
themselves until a point when all alternatives end at the same time. For example if there
are three systems with lives of 3, 4, and 6 years, the common denominator period of
analysis would be 12 years. The first system, would be replaced 3x; the second system
would be replaced twice; and the third system would be replaced once.
*Uniform Annual Cost: This most common method economically adjusts dollars to
account for the different length lives. There will be more discussion on how to accomplish
this later.
Parameters - Type of Dollars
* Constant dollars or current dollars
* Constant Dollars
* Adjusted for the effects of inflation (reflects the
purchasing power of the dollar in a specified year)
* Most common
* Current Dollars
* Cost or benefits data expressed in terms of future
purchasing power of the dollar
Warning: Do not mix
Constant and Current Dollars
in the same analysis
Another important estimating parameter is the type of dollars ($) that will be used for the
analysis. Constant dollars are used most often, however, sometimes there is justification
for using current dollars. For example, if the data gathered is in current dollars or is
expressed in relative terms that do not take away the effects of inflation, then current
dollars could be used for the analysis. Either type of dollars is fine to use in the estimates,
but the EA should absolutely not mix both constant and current dollars in the same
analysis.
As we’ll see shortly, the type of dollars used will dictate which set of discount rates should
be used.
More information on different types of dollars and how to account for the effects of
inflation can be found in Module 5 Inflation and Index Numbers
Parameters – Base Year
* Determine base year for analysis
* Year to which estimates are adjusted:
* De-escalation – constant $ estimates only
* Discounting – both constant and current $ estimates
* More information on discounting and net present value
(NPV) on upcoming slides
* Mandated as the first year of analysis, or the first fiscal
year in which there is a difference in expenditures
between alternatives
Finally, the Base Year of analysis must be chosen. The Base Year is usually the first year in
which there is a difference in expenditures among the alternatives. If this is the first EA
conducted for a program, the Base Year is usually one or more years in the future. If this is
an update to an estimate, the Base Year is typically the current or a past year. If constant
dollars are used for the estimate, it is critical to establish Base Year up front as this is the
year to which all estimates are adjusted for inflation. If current dollars are used, the Base
Year can be decided upon later, but it still needs to be defined because discounting is made
according to the Base Year of the estimate.
More information on inflation can be found in Module 5 Inflation and Index Numbers.
Cost Estimates
* Develop comprehensive cost estimate for each alternative
* Use a work breakdown structure (WBS) / cost element structure (CES) to
help organize and capture all costs
* Identify all applicable cost categories
* EA cost estimate typically more extensive than life cycle cost estimate
(LCCE)
* Costs to include:
* Traditional LCCE costs such as development, acquisition, operations,
support, maintenance, disposal
* Opportunity costs of existing assets/resources used if those
assets/resources could be used elsewhere
* Imputed costs, which are value of services provided without charge to a
project (e.g., base operating support)
* Status quo phase-out costs for any alternative that requires the status quo
system to continue to operate while the alternative is developed
* Parallel operations costs should be captured with a potential transition plan
The next part of this EA Process step is to develop a comprehensive Cost Estimate for each
alternative. It is useful, and usually required, to use a WBS or Cost Element Structure as
the framework for the estimate. While determining the WBS/CES we need to ensure that
all applicable costs are captured. Here is where an EA Cost Estimate sometimes differs
from a Life Cycle Cost Estimate (LCCE):
An EA estimate is typically more extensive in terms of types of costs captured. Costs to
include in an EA are “traditional” LCCE costs such as development, acquisition, operations,
support, maintenance, and disposal, but also opportunity costs of existing assets and
resources that are used in a particular alternative if those assets/resources could be used
elsewhere….
….and imputed costs, which represent the value of services provided without charge to a
project (e.g., Base Operating Support). Finally, for any alternative that requires a
development and phase-in period he Operations and Phase-out costs of the Status Quo
system must be included in the Alternative’s cost estimate.
A significant cost element that needs to be addressed is “Parallel Operations” and how
it’s defined. Usually you’re not going to drop the status quo scenario and, the same day,
assume the alternative. A parallel operations scenario needs to be documented in the
assumptions section as well.
Cost Estimates
* Develop comprehensive cost estimate for each alternative
* Identify all applicable cost categories (continued)
* Costs to exclude:
* Societal costs and benefits outside of the US federal government
are usually not included in a DoD analysis
* Sunk costs –These should be addressed in the assumptions for the
analysis.
* Costs captured under benefits estimate
* Optional costs
* Wash costs, which are costs that accrue equally by all alternatives
* Include if required to report total program costs
* Exclude if required to streamline decision making material
Costs to exclude (per DoD Instruction):
1) Societal Costs and benefits outside the Federal Government are usually not included in a
DoD analysis. A project whose primary purpose is to produce benefits outside the Federal
Government falls under OMB Circular A‐94‐could be different if you are doing an EA for
HHS or EPA
2) Sunk costs and realized benefits are not included, but should be discussed in the
assumptions for the analysis. Even though sunk costs are not counted as part of the cost
estimate, they should be documented in the assumptions.
One cost that is optional to include or exclude are wash costs. These are costs that are
realized by all alternatives equally (as in, “It’s a wash”). Normally, if there is a requirement
to show total program funding, wash costs are included. However, if these is no such
requirement, it is often easier to remove the costs from the analysis to avoid “too much
information” being presented to the decision maker. If the costs are not included, a note
should be made to that effect in the documentation. Note that the inclusion or exclusion
of wash costs will affect multiplicative measures such as the Cost/Benefit Ratio (CBR),
which is one reason we prefer additive measures such as Net Present Value (NPV)..