Remedial Action Cost Engineering and Requirements

(RACER) System

Contingency Plan and Operating Procedures

Version 2002

4 April 2002

HQ AFCESA/CESC
Tyndall AFB, FL
Record of Changes

Record of Reviews and Changes

Date Date
Change ID Reviewed Approved Comment Signature
Initial 15 Jan 01 15 Jan 01 Initial Issue //signed//
K. Stuart Millard

Change 1 5 April 01 Added models and //signed//

updates K. Stuart Millard

2
Table of Contents

Purpose....................................................................................................................................... 4
Scope.......................................................................................................................................... 4
References.................................................................................................................................. 4
Description of RACER................................................................................................................. 4
Hardware Environment................................................................................................................ 4
Software Environment................................................................................................................. 5
Event Analysis and Assessment................................................................................................. 5
Operating Procedures………………………………………………………………………………… 5
Contingency Events.................................................................................................................... 5
Data File Loss.......................................................................................................................... 5
Database Loss......................................................................................................................... 6
Backup and Restore Processes Error! Bookmark not defined. Attachment 1
Backup Process....................................................................................................................... 6
Restore Process......................................................................Error! Bookmark not defined.
License................................................................Error! Bookmark not defined.Attachment 2

3
Purpose
The purpose of this document is to outline those anticipated events that would prevent the
successful completion of the Base Civil Engineering mission through the unavailability of the
RACERTM 2002 data system.

This contingency plan is designed to minimize the downtime for the end user of the RACERTM
2002 application system. This plan does not cover failures at the end user location, and the
RACERTM 2002 system is not loaded to a network infrastructure. Refer to this web address
http://www.afcesa.af.mil/Directorate/CES/Civil/CostEngr/CostEngr.htm for the Air Force approved
loading permissions for a PC connected to a network. A failure is considered to be a
“catastrophic failure”, if it has an effect on the end of year budget and the budget verification
documentation provided with use of RACER.

Individual US Air Force Civil Engineering users must always be prepared to implement local
contingency plans which include the manual collection of data from the point in time that an event
occurs for later input when the or database has been restored.

The Primary Point of Contact for the issues discussed in this document is Mr. K. Stuart Millard,
HQ AFCESA/CESC, Tyndall Air Force Base, Florida, 32403-5319, DSN 523-6171, or commercial
(850) 283-6171, and E-mail at stuart.millard@tyndall.af.mil. Contractor Earth Tech, DSN 926-
1110, 303-771-3103 http://www.talpart.com/. Base CE squadrons should write here their
MAJCOM POC and base computer/network POC.

Scope
This document applies only to the RACERTM 2002 data automation system installed on separate
Personal Computer disk drives. This document does not identify any base level contingency
plans, as that function lies with the Base Civil Engineer. The BCE can add this RACER
contingency plan as an annex to their contingency plan. This document does identify those
situations where the BCE should have locally developed plans as an extension of this plan.

References
RACERTM 2002 is a patented licensed (Attachment 2) software system. Reference the RACER
training link: http://www.talpart.com/products/racer/index.html and the RACER Quick Reference
Guide, a paper pamphlet included with the software package; and RACER Frequently Asked
Questions: http://www.talpart.com/products/racer/racerfaq.html . These items and the data file
backup should be maintained in a secure location

Description of Remedial Action Cost Engineering and Requirements

(RACER) System
In order to properly plan for any contingency involving computer systems, a description of the
environment must be made. RACERTM 2002 is a standalone PC based application and has no
external networked writing capability. The RACERTM 2002 system is the primary tool for
preparing programming cost estimates for environmental remediation.

Hardware Environment
The RACERTM 2002 application and databases reside on Personal Computer systems. In the
event of a computer system failure, the only way to restore the RACERTM 2002 systems is to
reinstall the original CD. Periodic backups must be made in order to save project information
each user has created.

4
The following list indicates the minimum hardware and operating system requirements that you
must have installed on your computer before you can install RACER 2001:

 Pentium 133 mHz (166 or above recommended)

 32 MB RAM (64 or above recommended)
 50 MB free hard disk space (100 or above recommended)
 CD ROM drive
 Windows 95/98/NT/2000 operating system
 Backups made to 3.5 inch floppy, Zip drive, or CD-R.

Software Environment
Once installed all information created by the RACERTM 2002 application and related data is
contained in a Microsoft ACCESS database;

Event Analysis and Assessment

Any corrective action to restore missing, deleted, or corrupted information is the responsibility of
the user of the Personal Computer.

Operating Procedures
Normal Backup procedures (attachment 1) should be performed when the user determines that
the RACER project information is not expendable. This can be hourly, daily, weekly, monthly,
etc. The complete database should be saved, minimally, on a yearly basis and more frequently if
necessary.
New or updated versions of the software can be obtained from Earth Tech, 9100 E. Panorama
Dr. Suite 200 Englewood, CO 80112-3463, 303-771-3103 www.talpart.com, email:
racer@earthtech.com

Contingency Events
Contained herein are contingency events, from least damaging to most damaging, and an outline
of steps that will be taken at each PC to restore the RACERTM 2002 data files to the point where
normal operation can continue successfully.

Individual US Air Force Civil Engineering installations must be prepared to implement local
contingency plans which include the manual collection of data for later input to the database
when restored.

Project Data File Loss

Event:

A project data file is lost, damaged, or deleted on a specific PC. This is an End User
identified problem. See attachment 1.

Plan:

Within the RACERTM 2002 application, individual project information cannot be restored
unless this project information has been previously saved.

5
 Database Loss

Event:

An entire database is lost, damaged, or deleted at a specific location.

Plan:

The loss, damage, or deletion of the entire RACERTM 2002 database is an event, which
requires reinstallation of the original RACERTM 2002 CD. To obtain a replacement CD
contact Earth Tech, 9100 E. Panorama Dr. Suite 200 Englewood, CO 80112-3463, 303-
771-3103 www.talpart.com, email, racer@Earthtech.com.

Backup and Restore Processes

Within the RACERTM 2002 system, database backups are possible (attachment 1).