Operational Architecture

• Objectives

  • Describe the “To Be” functionality, activities, system behavior, operational elements, and information flows required to accomplish or support NORAD/ USSPACECOM missions
    
  • With the SMM performance requirements provides a “To Be” vector to evolve, augment, and add to current system capabilities

The Operational Architecture

evolves with time

Previous slide

Next slide

Back to first slide

View graphic version

The operational architecture is not an end point. It is provides an 80% solution for the future. The operational architecture will evolve over time (world situation, new mission requirements, etc.)

The operational architecture with the SMM provides you the contractor with the direction (vector) we want you to evolve our current capabilities. This vector is the input into evolutionary acquisition process.