Survey of Step 3

In a technical baseline document or group of documents, identify

The program’s purpose and its system and performance characteristics;
All system configurations;
Any technology implications;
The program acquisition schedule and acquisition strategy;
The relationship to other existing systems, including predecessor or similar legacy systems;
Support (e.g., manpower, training) and risk items;
System quantities for development, test, and production; and
Deployment and maintenance plans

The technical baseline description completely defines the program, reflects the current schedule, and is technically reasonable.

A documented technical baseline description exists and resides in one location.
The technical baseline description has been developed by qualified personnel such as system engineers.
The technical baseline description has been updated with technical, program, and schedule changes.
The technical baseline description contains sufficient detail of the technical characteristics, risk, and the like, based on the best available information at the time.
The technical baseline description has been approved by management.

Without an adequate understanding of the acquisition program—such as the acquisition strategy, technical definition, characteristics, system design features, and included technologies—the cost estimator will not be able to identify the technical and program parameters that underpin the cost estimate and the quality of the cost estimate will be compromised.
Unless the technical baseline is maintained and updated in preparation for program reviews, milestone decisions, and major program changes, the credibility of the cost estimate will suffer.
Without explicit documentation of the basis of a program’s estimates, it will be difficult to update the cost estimate and provide a verifiable trace to a new cost baseline as key assumptions change during the course of the program’s life.