Life-Cycle Cost Estimation
Definition: Cost analysis is "the process of collecting and analyzing historical data and applying quantitative models, techniques, tools, and databases to predict the future cost of an item, product, program or task." Cost estimates "translate system/functional requirements associated with programs, projects, proposals, or processes into budget requirements, and determine and communicate a realistic view of the likely cost outcome, which can form the basis of the plan for executing the work."
Keywords: budget, cost analysis, cost benefit, cost estimation, regression analysis, tradeoffs
MITRE SE Roles & Expectations: Systems engineers (SEs) are expected to use cost analysis to identify and quantify risks, and to evaluate competing systems/initiatives, proposals, and tradeoffs. They are expected to collaborate with the cost/benefit analyst and sponsor/customer to define the approach, scope, products, key parameters, and tradeoffs of the analysis. SEs support and provide direction to the analyst, review results, guide and evaluate the sensitivity of the analysis, and provide technical, programmatic, and enterprise-wide perspectives and context for the analyst.
A Perspective: Cost analysis is an often misunderstood and frequently overlooked practice that encompasses many areas of a program's business management. It combines the knowledge of many different disciplines and produces results that have far-reaching impacts on a program and its success. In many cases, the analyst who built a program's life cycle cost estimate (LCCE) will have more knowledge and understanding of the program than any other member of the program team.
Cost Estimate Development Overview
Cost estimation methodologies and techniques vary widely depending on the customer and program. These variations are based on a number of factors. What is being estimated, the extent of available data, existence of an agreed upon work breakdown structure (WBS), regulatory requirements, agency requirements, and industry best practices all influence the methodologies and techniques that may be applied when creating a cost estimate. For example, the LCCE for a Department of Defense weapon system will be conducted differently and look very different from an estimate for a data center or the development of a computer application for a civilian agency. Also, the type of estimate will influence the methodology and approach used. A much more rigorous process is required for a budgetary estimate or a full LCCE than for a rough order of magnitude or "back of the envelope" type of estimate. Although there is no "cookie-cutter" approach to developing a cost estimate, the flow chart in Figure 1 depicts a generic cost estimating process.
Figure 1. General Depiction of Cost Estimating Process
- Define Cost Estimate Scope: The initial step is to define the possible scope of the cost model. The scope will determine the content of the cost elements that must be included in the model. Sources for scope definition of a program include the project management plan, the scope statement, the WBS, and any requirements documentation, etc.
- Identify Assumptions and Constraints: Assumptions are statements that are used to limit the scope of the model. They are a "given" as opposed to a "fact." They usually relate to a future occurrence and therefore contain uncertainty. Assumptions must be evaluated during sensitivity analysis. Constraints are usually fixed, externally imposed boundaries such as schedule, policies, and physical limitations.
- Develop Cost Element Structure: The cost element structure can also be thought of as a chart of accounts. It is a listing of the possible categories of cost contained in the model. Each element must be defined so that all costs are covered, and there are no duplications of costs within the structure.
- Collect and Normalize Data: Cost data is collected for all of the elements within the model. Information from benchmark research and actual cost experience is used. Normalization is the process for ensuring that cost data are comparable.
- Develop Cost Estimating Relationships: The cost data is used to develop equations that will be entered into the cost model. The equations will be the basis for estimating costs as a function of system capacity and service level.
- Document Approach: Documentation is provided for each cost element that indicates the sources of data, assumptions used, and any equations that have been used in the calculations.
- Customer Review: A walk-through on the model and results is conducted with the sponsor to ensure that all expected costs have been adequately represented and to achieve acceptance of the estimate.
Best Practices and Lessons Learned
The Three "R"s: For an LCCE to be credible and effective, it must meet three basic requirements, also known as the three Rs of cost estimation: Replication, Rationale, and Risk.
- Replication: The estimator must provide an audit trail that is sufficiently detailed including clearly stated assumptions for each cost element to allow for an independent replication of the estimate by a third or external party.
- Rationale: The estimator must provide convincing and justifiable rationale for the selection of key parameter values, labor estimates, cost factors, assumptions, and all underlying inputs to the estimate. These can come from early project experience, other similar projects, parametric models, and documented engineering judgments.
- Risk: The estimator must conduct risk/sensitivity analysis to assess the impact of the inherent uncertainty in input values. Regression analysis is the most frequently used method of conducting sensitivity analysis in this area.
Utility to the Program: Investments require clear identification of benefits, which can be categorized as either tangible or intangible. The benefits can be packaged in a program that will most likely yield desirable outcomes. As a cautionary step, one must consider the cost to stand up the program, the cost to incur the chain of activities for the identified investment such as implementation, operation, and maintenance from both quantitative and qualitative perspectives. When properly done, cost analysis provides the following utility to the program:
- Supports budgeting process by:
- Integrating the requirements and budgeting processes
- Assessing affordability and reasonableness of program budgets
- Providing basis for defending budgets to oversight organizations
- Quickly/accurately determining impacts of budget cuts on program baselines and associated functionality
- Enables early identification of potential pitfalls such as cost growth and schedule slips
- Enables identification of future cost improvement initiatives
- Provides for the identification and objective quantification of the impact of program risks (technical and schedule risks)
- Provides a basis for evaluating competing systems/initiatives (cost/benefit analyses and analysis of alternatives [AoA])
- Enables proposal pricing and evaluation of proposals for cost reasonableness (independent government cost estimates)
- Captures cost impacts of design decisions to facilitate tradeoffs in cost as an independent variable/design to cost/target costing
- Facilitates evaluation of the impact of new ways of doing business (e.g., in-sourcing vs. outsourcing, commercial off-the-shelf vs. custom software)
An art, not a science: As with any discipline, the actual application and practice of cost analysis is more difficult than the academic description. It is seldom the case that the process outlined above can be applied with complete precision. In most cases many factors conspire to force the systems engineer and the cost estimator to step "outside the box" in completing a cost estimate.
When data is unavailable: Oftentimes data to support the estimate is not readily available through the customer organization. Finding supportable data will often require creative thinking and problem solving on the part of the systems engineer and cost estimator. An example is an AoA in which one of the alternatives was to build roads. The agency in question did not possess any in-house knowledge on road construction, ancillary costs (such as drainage ditches and easements), or permit and legal requirements for construction of several hundred miles of access road. The situation required reaching out to the civil engineering community and several state departments of transportation in order to bridge the knowledge gap and obtain the information in question. This resulted in a detailed and supportable estimate that the customer was able to use in justifying managerial decisions.
Adaptability is key: As stated in the cost estimation development discussion of this article, there is no single way to construct a cost estimate—too much depends on the details of the circumstances at hand. An estimator cannot do a parametric estimate, for example, if the data and situation does not support that approach. Another AoA provides an example of this. When tasked to provide an AoA for an out-sourcing or internal development of a customer's financial management system, the estimator predetermined that an engineering build-up based on engineering knowledge of the problem set would be performed. Unfortunately, the customer organization had no internal engineering expertise in this area. The estimator was forced to change its approach and build an estimate based on analogy of similar systems and industry benchmark studies.
Keep program needs in sight: Overall, the most important perspective on cost estimating is to keep the process in context. Remember that the cost estimate is not an end in itself but a means to an end. Understand what the program needs to accomplish through cost estimation and work with the cost estimator to tailor your product accordingly.
References & Resources
- The International Society of Parametric Analysts and The Society of Cost Estimating and Analysis (ISPA/SCEA) Professional Development and Training Workshop proceedings, 2-5 June 2009, training presentation on Cost Estimating Basics, [slide 5].
Additional References & Resources
Army Financial Management Home Page, accessed June 8, 2010.
GAO, March 2009, GAO Cost Estimating and Assessment Guide, "Best Practices for Developing and Managing Capital Program Costs."
Software Engineering Institute, accessed June 8, 2010.
The Data and Analysis Center for Software, accessed June 8, 2010.
The Project Management Institute, accessed June 8, 2010.
The Society of Cost Estimating and Analysis, accessed June 8, 2010.
"Financial & Contract Management," MITRE Project Leadership Handbook, accessed February 22, 2010.
"Tradeoff & Engineering Analysis," MITRE Project Leadership Handbook, accessed February 22, 2010.
Not all references and resources are publicly available. Some require corporate or individual subscriptions. Others are not in the public domain.
References and resources marked with this icon are located within MITRE for MITRE employees only.
For more information on the Systems Engineering Guide, or to suggest an article, please Contact Us.