Baseline Evolution

Technical Baseline

The project-level system engineer is responsible for ensuring the completeness and technical integrity of the technical baseline, not the CM manager.

Technical baseline consists of:

  • Functional and performance requirements (or specifications) for hardware, software, information items, and processes.
  • Interface requirements
  • Specialty engineering requirements
  • Verification requirements.
  • Data packages, documentation, and drawing trees
  • Applicable engineering standards

Everyone working on a subsystem has a responsibility to maintain the integrity of that baseline by participating in the CM plan, with oversight by the subsystem lead engineer. The system engineers are responsible for the entire system.

The technical baseline evolves as the project moves through the life cycle.

The technical detail increases as the project moves through each gate.

As the technical detail increases, this detail should be placed under CM control. Initial CM may start with the top-level requirements defined in the mission needs statement. The typical gates (technical baselines) that a project progresses through the lifecycle are:

  • Functional Baseline at System Requirements Review (SRR)
  • Allocated Baseline at Preliminary Design Review (PDR)
  • Product Baseline at Critical Design Review (CDR)
  • As-Built Baseline at System Acceptance Review (SAR) 
  • Operational Baseline at Operational Readiness Review (ORR)