TRACES

Prepared by:
U.S. Army Corps of Engineers, in conjunction with various software developers.

Prepared for:
U.S. Army, Navy, and Air Force

Application:
Financial analysis:
Environmental impact analysis: ---
Waste management/P2:
Environmental cost listing/database: ---
Cost estimation: ---
Alternative product/process comparison: ---

Umbrella linking all automated cost engineering systems, and their databases. Scheduling software can also be linked to TRACES.

Elements of control:
Cost control
Resource control ---
Estimating control
Schedule control
Scope control
Risk control

Development date and updates:
The system was referred to as TRACES (that covers the whole system) only in March 1993. Some portions of TRACES (MCACES) are required to be used in federal facilities.

Public availability:
Available to the tri-services.

Purpose and current use:
In 1990 the U.S. Army, Navy, and Air Force agreed to pool their resources and develop a single automated cost engineering system. TRACES cannot as yet be fully integrated, as there are still some stand-alone modules. However, the objective is to completely integrate the system.

Cost information:
Private users can obtain TRACES by subscribing to the National Institute of Building Sciences, Construction Criteria Base (CCB) at a price of $750 for a one year subscription (includes 7 CDs). Government users and government contractors can obtain licenses through the US Army Corps of Engineers.

System requirements:
The software requirements will vary depending upon the modules used. The systems are IBM-PC based. The CCB is single-user and PC-based. Some of the systems (such as MCACES) are network compatible.

Software summary

Size and complexity of projects:
The system is directed to large projects. However, it can be used to manage projects of various sizes and complexities, constrained by the individual flexibilities of the constituent modules.

Other compatible systems offered:
The system is modular in design. All the modules are not integrated, primarily due to their diverse functions.

Nonquantifiable information:
This will vary with module. For example, MCACES (described in the resource guide as Composer Gold) has an annotation capability.

The TRACES system intends to provide a user-friendly cost engineering platform in a standard environment, that will provide the cost engineer the tools to prepare, review, and maintain all types of cost estimates. Software for scheduling construction can also be linked to TRACES. The system includes the following modules:

TRACES includes several databases and files. These include the Unit Price Book (UPB), a models database, an assemblies database, Work Breakdown Structure(data file providing separate hierarchical WB master structure), Cost escalation index, Area cost factor index, Facility cost ($/SF), and the Historical Cost Analysis System (HCAS). The QTO database consists of approximately 22,000 items covering a full range of data supporting military construction, large civil works estimates, tunneling, and highly toxic waste and radiation waste cleanup estimates. This database is also used with the maintenance and repair database to provide a life-cycle cost analysis.

Life-cycle stages covered

Raw material acquisition ---
Manufacturing stage
Use/reuse/maintenance
Recycle/waste management ---

The life-cycle cost module is designed to include all relevant facility costs incurred over the life of the facility. The life-cycle cost module consists primarily of

Type of costs considered

Conventional
Potentially hidden
Contingent ---
External ---

The method considers only conventional costs and some aspects of hidden costs. For example, the HTRW databases, and the HCAS databases will include some information on hidden costs. Also, the MCACES maintenance and repair database has information on hidden costs.

Method of cost estimation

Empirical estimating relies on historical data for cost development. It is based on the identification of building type, using historical unit cost (per square foot) and adjusting it by several standard factors including location, cost growth to the midpoint of construction, size, building sophistication, and a local site adjustment for each project that accounts for factors such as local contractor competition, site overcrowding, availability of crafts, etc. The quantity takeoff module is the U.S. Army Corps of Engineers' microcomputer system (MCACES). It is a step-by-step cost estimating tool that considers contractor layering, overhead, profit, and all indirect costs.

Generation of financial indicators

Net present value (NPV) ---
Payback period ---
Internal rate of return (IRR) ---
Benefits cost ratio ---
Other

Ability to include environmental costs

User-friendliness and flexibility

The objective is to develop an integrated system that is user-friendly and works in a standard environment. The flexibility will vary, depending upon the characteristics of the constituent modules.

User-support

The TRACES group (Huntsville Engineering Division-Automated System Branch)provides user-support for the software programs through operations, maintenance, and hotline telephone support. Also, the Cost Engineers Bulletin Board (CEBBS)allows cost engineers to exchange information between districts, divisions, and authorized commercial vendors.

Limitations

The QTO database may provide data applicable to DOE projects. The system is not currently available for use by private users. It is primarily focused on construction and engineering projects. Currently, no data on contingent environmental costs or less-tangible costs is estimated. A full range of hidden costs is not considered.

Basis for evaluation:
The information provided here is based on a profile of the tool presented Weitz et al. (1994), and information obtained from the US Army Corps of Engineers in June, 1995.

Contact information:
HQ, US Army Corps of Engineers
Attn. CEMP-EC
20 Massachusetts Ave, NW
Washington DC 20314-1000
202-761-1240
202-761-0999 (FAX)

CD-ROM subscription service
National Institute of Building Sciences
202-289-7800


Return to the top of this document.

Return to the Chapter 4 Index

Return to the Table of Contents