STATEMENT OF OBJECTIVES

FOR

NMD LEAD SYSTEM INTEGRATOR CONCEPT DEFINITION

AND

LEAD SYSTEM INTEGRATOR

1.0 Scope

1.1 This effort provides for a Lead System Integrator (LSI) responsible for the National Missile Defense (NMD) System's:

1. Development and Engineering performance

2. Integration (physical and performance) including system interfaces

3. Test and Evaluation

4. Deployment and initial sustainment

5. Design, development, production and deployment, as required, of the NMD Elements: (Ground Based Interceptor (GBI), Ground Based Radar (GBR) (excluding current GBR-P), Upgraded Early Warning Radar (UEWR), Battle Management, Command and Control and Communications (BMC3), and Forward-based X Band Radars (FBXB))

1.2 The program will be conducted in two phases:

1. An LSI Concept Definition (CD) phase for which up to three contracts will be awarded. During the CD phase, each contractor will develop and document plans and schedules to develop an NMD system that meets NMD system requirements. In addition, each contractor will conduct GBI configuration trade studies to achieve NMD system performance and provide a best value GBI solution. This phase will be followed by a down select to a single contractor for the LSI execution phase.

2. The LSI execution phase, anticipated to be approximately 10 years, is structured into two developmental periods: a nominal 36 month base period, followed by optional continued NMD acquisition periods, which provide for both continued development and optional NMD deployment. The specific objectives of each LSI period/option are as shown in Table 1.0-1.

10 January 1997

Table 1.0-1 LSI Execution Phase Program Periods and Options

Base Period During the baseline development program, the LSI shall integrate existing developmental efforts, as well as initiate any LSI-specific development and integration efforts, and will conclude with an integrated system demonstration and Deployment Readiness Review to assess the viability of deploying an NMD capability as early as FY2003.
Continued Development Period

During the continued evolutionary portion of the execution phase the LSI shall perform further evolutionary acquisition/development toward the objective NMD system while reducing program risk and improving system capability. This shall be performed in accordance with DODD 5000.1 and DOD 5000.2-R. The LSI will also maintain the capability and flexibility to deploy an NMD system within three years of a decision to do so. A single site version of this capability is the C2 architecture.
NMD Deployment Option If directed, the LSI shall acquire, deploy, and provide initial sustainment for the deployment of an NMD system. This deployment option can be executed at any time after the baseline period, and requires deployment within three years. The architecture that would be deployed, if a decision was made in FY2000 would be the C1 architecture.

1.3 The NMD system will provide defense of all territory in the 50 states. Specific system-level compliance requirements for two capability architectures are provided in the respective C1 and C2 System Requirements Documents (SRD) paragraphs 3.2 through 3.6, and associated verification requirements also provided in the SRD Section 4.0. A flow-down of the NMD element requirements is provided in paragraph 3.7 of the respective SRD's. Derivation of NMD System requirements from User-supplied requirements documentation will be performed by the Government, and provided to the LSI through these SRD paragraphs. A listing of C1 and C2 architecture elements, not all of which may be required to achieve system performance, is attached to this SOO. It is intended that the C1 architecture will, as a minimum, achieve Operational Requirements Document (ORD) threshold objectives. C1 will evolve as NMD system capability increases during contract performance. The C2 architecture may change as the system and element capabilities are further developed and verified. It may be necessary to plan for a multi-site architecture (C3) to achieve all ORD objective requirements, although this architecture has not been finalized. Alternative architectures C1(a) and C2(a) are described in SOO Attachment 1, which exclude FBXB radars.

1.4 Development of some of the candidate NMD system elements is currently being performed through a series of BMDO and Service element technology development and prototyping contracts. These include BMC3/IFICS, Exo-atmospheric Kill Vehicle, GBR-P, experimental upgrades to Early Warning Radars, and FBXB. In addition, the Air Force is continuing development of the Space and Missile Tracking System (SMTS) under a separate MDAP. Application of the results and products of these efforts may be essential to achieving the NMD program objectives.

2.0 Objectives of the Concept Definition Phase

The Contractor shall develop and document an integrated, cost effective concept for the design, development, integration, test and evaluation, production, deployment, sustainment, and disposal of an NMD System, in accordance with Government-supplied baseline deployment scenarios to be updated after award of the CD phase contracts. The Contractor shall verify and demonstrate that their concepts meet the C1 and C2 NMD System requirements in paragraphs 3.2 through 3.6 of respective SRDs. If the element requirements provided in paragraph 3.7 are changed, a description and rationale for the change shall be provided. The Contractor shall perform and document risk analysis and assessments of the recommended approach for NMD System integration and GBI development for early deployment and objective system requirements.

In performing this phase, the contractor shall assess the utility of incorporation of existing NMD element development efforts, including those shown in Table 2.0-1, into the proposed LSI program, and, if appropriate, shall document planning for transition of existing elements to the LSI program.

Table 2.0-1 Existing NMD Element Contracts

Element Contract Government Contracting Organization Contract Number Prime Contractor
BMC3 BMDO HQ0006-95-C-0018 TRW
GBR-P Army NMD Project Office DASG60-92-C-0184 Raytheon
Exo-Atmospheric Kill Army NMD Project Office DASG60-90-C-0166 Hughes
Vehicle (2 contracts) DASG60-90-C-0165 Rockwell
FBXB, GBI, GBR-O, and UEWR BMDO (via LSI) LSI LSI
Note: SMTS development is being performed under Air Force Management

2.1 NMD Integration Concept

The Contractor shall define an integrated, executable technical and management approach for design, development, integration, test and evaluation, production, deployment, sustainment and disposal of the NMD system that meets the objectives of the LSI periods described in Table 1.0-1, and that can be executed upon selection for the LSI award. This plan shall address the development of element capability, the integration of the elements into an NMD system, the test and evaluation program to be performed and production, deployment and sustainment planning and scheduling to execute the deployment option. This planning shall also address the transition of existing element developments to the LSI, existing infrastructure, and any technical or other architectural decisions that are reflected in this planning.

The contractor's documentation shall include supporting rationale, Life Cycle Cost analysis, and program schedules. The contractor's documentation shall identify the specific program activity supporting each LSI period described in Table 1.0-1.

2.2 GBI Development

The contractor shall analyze GBI alternatives (including infrastructure, booster and Kill Vehicle) and recommend a GBI program that address the LSI program phases shown in Table 1.0-1. This analysis will consider the re-use of existing Minuteman components, infrastructure, and designs to provide portions of the GBI element.

The contractor shall analyze and document the programmatic and technical implications of applying each of the alternatives for GBI development shown in Table 2.2-1 (as a minimum) to the following applications:

Base Period (FY 99 Demonstration and Deployment Readiness Review)

Continued development towards the CRD Objective requirements NMD System (C2 Architecture)

Optional deployment anytime after the Readiness Review (C1 Architecture)

A multi-sited deployment, if required

The contractor shall document the performance, schedule and cost implications of each alternative for each of the above applications.

Table 2.2-1 Test, Early Deployment and Objective GBI Alternatives
Alternative Infrastructure Booster

1 Contractor specified at Grand Forks, ND Contractor specified alternative booster stack, consisting of off-the-shelf components,

2 Contractor specified at a non-Grand Forks deployment site (e.g. Alaska North Slope) components currently under development, or new components

3 Minuteman-Based for a Grand Forks deployment.

4 Minuteman-Based for a Grand Forks deployment. Minuteman booster (Modified as Required)

5 Contractor specified at a non-Grand Forks deployment site (e.g. Alaska North Slope)

The contractor shall recommend appropriate GBI alternatives that address requirements for the above applications of the GBI program and provide configuration transition planning, if required. The Contractor shall document the rationale for selection of each booster/infrastructure alternative. The contractor shall provide a Kill Vehicle selection/down selection plan, including consideration of cost, schedule, performance and risk impacts, and provide the proposed selection criteria that will be applied.

The Contractor shall develop an executable, cost effective, technical and management approach, rationale and schedule for design, development, test and evaluation, production, and deployment of the selected GBI approach. The contractor shall reflect this GBI approach in the NMD Integration Concept provided in response to paragraph 2.1.

2.3 Architecture Performance Analysis

The Contractor shall analyze the performance that can be achieved with architectures C1 (a) and C2 (a) as described in SOO Attachment 1. The Government will provide updated C1 (a) and C2 (a) architectures no later than the first Technical Interchange Meeting.

3.0 Objectives of the LSI Phase

See Table 1.0-1

4.0 Program Management

The contractor shall document results in a manner that provides full insight into the processes, rationale, and results of the work. The contractor shall provide management reviews and documentation, and implement an automated paperless delivery of products, information, and status between contractor and Government facilities.

SOO Attachment 1 Architecture Elements

C1 Architecture Elements

Ground-Based Interceptor (GBI) (20)

Ground Based Radar (GBR)

Forward Based X-Band Radar (FBXB)

Upgraded Early Warning Radar (UEWR)

Battle Management, Command and Control and Communications (BM/C3)

C2 Architecture Elements

Ground-Based Interceptor (GBI) (100)

Ground Based Radar (GBR)

Forward Based X-Band Radar (FBXB)

Upgraded Early Warning Radar (UEWR)

Battle Management, Command and Control and Communications (BM/C3)

Space and Missile Tracking System (SMTS) / Space Based Infrared System/Low Earth Orbit (SBIRS/LEO)

C1(a) Architecture Elements

Ground-Based Interceptor (GBI) (20) at Grand Forks, ND

Ground Based Radar (GBR) at Grand Forks, ND

Upgraded Early Warning Radar (UEWR)

Battle Management, Command and Control and Communications (BM/C3)

C2 (a) Architecture Elements

Ground-Based Interceptor (GBI) (100) at Grand Forks, ND

Ground Based Radar (GBR) at Grand Forks, ND

Upgraded Early Warning Radar (UEWR)

Battle Management, Command and Control and Communications (BM/C3)

Space and Missile Tracking System (SMTS) / Space Based Infrared System/Low Earth Orbit (SBIRS/LEO)

C3 Architecture Elements (Notional Architecture )

Ground-Based Interceptor (GBI) (100) at Grand Forks, ND

Ground-Based Interceptor (GBI) (100) at North Slope, Alaska

Ground Based Radar (GBR)

Forward Based X-Band Radar (FBXB)

Upgraded Early Warning Radar (UEWR)

Battle Management, Command and Control and Communications (BM/C3)

Space and Missile Tracking System (SMTS) / Space Based Infrared System/Low Earth Orbit (SBIRS/LEO)

Not all elements may be required to achieve system performance.

DSP/SBIRS-HIGH available for all architectures.