.Task_Order_0001_SOW 04.25.12.docx

Upgraded Early Warning Radar & Cobra Dane (UEWR & CD) Ballistic Missile Defense System (BMDS) Integration & Test

First Year Task Order Statement of Work

Contract HQ0147-XX-D-XXXX

TASK ORDER 0001

Prepared by Missile Defense Agency BMDS Sensors Directorate Huntsville, Alabama 35897-3801

25 April 2012

FOR OFFICIAL USE ONLY - COMPETITION SENSITIVE

SOURCE SELECTION INFORMATION - SEE FAR 2.101 AND 3.104

TASK ORDER 0001 // 25 April 2012

FOR OFFICIAL USE ONLY

FOR OFFICIAL USE ONLY - COMPETITION SENSITIVE

SOURCE SELECTION INFORMATION - SEE FAR 2.101 AND 3.104

FOR OFFICIAL USE ONLY

INTRODUCTION.

1.1 Overview.

This Statement of Work (SOW) details developmental test contractor responsibilities and activities necessary for accomplishment of the Missile Defense Agency (MDA) Integrated Master Test Plan (IMTP) and other Upgraded Early Warning Radars (UEWR) and COBRA DANE (CD) radar test requirements. The UEWR radars and Cobra Dane radar are major constituents of the MDA/Sensors (SN) radar portfolio and provide acquisition and tracking of ballistic missiles that may be launched against the United States, deployed forces, friendly nations, and allies as outlined in paragraph 1.1 of the Upgraded Early Warning Radar and Cobra Dane Ballistic Missile Defense System (BMDS) Integration and Test (UEWR & CD BIT) Indefinite Delivery/Indefinite Quantity (IDIQ) contract, hereafter IDIQ.

1.2 Scope.

This Task Order defines the tasks and scope of work as outlined in paragraph 1.2 of the IDIQ Statement of Work (SOW).

APPLICABLE DOCUMENTS.

See Applicable Documents listed in paragraph 2 of the IDIQ SOW.

REQUIREMENTS

3.1 Program Management.

The Contractor shall perform program management as outlined in paragraph 3.1 of the IDIQ SOW as necessary to meet the requirements of this task order SOW.

3.2 Training.

The Contractor shall perform all facets of training outlined in paragraph 3.2 of the IDIQ SOW as necessary to meet the requirements of this task order SOW.

3.3 Long Term Agreements.

The Contractor shall fulfill long term agreements outlined in paragraph 3.3 of the IDIQ SOW as necessary to meet the requirements of this task order SOW.

3.4 Delays.

The Contractor shall identify all circumstances that may hinder any completion date or required services delivery and fulfill requirements outlined in paragraph 3.4 of the IDIQ SOW as necessary to meet the requirements of this task order SOW.

3.5 Facility and Data Access.

The Contractor shall provide facility access to the Government and its representatives and fulfill all requirements outlined in paragraph 3.5 of the IDIQ SOW as necessary to meet the requirements of this task order SOW.

3.6 Systems Engineering.

The Contractor shall perform systems engineering required to define, develop, fabricate, integrate, document, and conduct UEWR & CD BMDS testing for each test event defined in this task order and in accordance with (IAW) the IDIQ SOW paragraph 3.6.

3.7 Configuration Management (CM).

The Contractor shall provide configuration management required to plan, integrate, test, and evaluate performance for each test event defined in this task order and IAW the IDIQ SOW paragraph 3.7.

3.8 Safety Quality, and Mission Assurance (SQMA).

The Contractor shall provide and perform SQMA required to plan, integrate, test, and evaluate performance for each test event defined in this task order and IAW the IDIQ SOW paragraph 3.8. The Contractor shall ensure that safety requirements are met for sensor hardware in the loop (HWIL) laboratories and other infrastructure identified in this task order. The Contractor shall provide Quality Assurance (QA) support to each test event identified in this task order. Mission Assurance Provisions (MAP) and Processes Mission Assurance Provisions (PMAP) provisions of the IDIQ SOW also apply to sensor HWIL infrastructure.

3.9 Test Infrastructure . (Contract Line Item (CLIN) 0004)

The Contractor shall operate and sustain the HWIL strings at Integrated System Test Capability–1 (ISTC-1), ISTC-2, and the Prime Consolidated Integration Laboratory-1 (PCIL) during Benchmark 1 (BM1) through BM5 testing, integration testing, Dry Runs, and Runs for Record. As part of the Sensors Test Plan for each test event, the Contractor shall provide details on the test provisioning approach and required facilities, HWIL equipment, and range resources. The Contractor shall perform operation and sustainment of HWIL equipment at ISTC-1 and ISTC-2 as necessary to sustain BM1 level of readiness.

The Government will provide certain support as described in Appendix C for Government Furnished Information (GFI), Government Furnished Facility (GFF) and Government Furnished Equipment (GFE). The Contractor may develop innovative, cost-efficient solutions for coordination with mutual support Government contractors, and military operators and maintainers as required to ensure mission execution success. The Contractor shall work closely with MDA/SN and the SN Mission Manager to identify provisioning issues early and generate recommended solutions.

3.10 Test and Evaluation.

3.10.1 The UEWR & CD system test and evaluation program shall be coordinated and synchronized with the test programs of Ground-Based Midcourse Defense (GMD) (MDA/GM), and other missile defense elements as may be required by the IMTP, along with UEWR & CD development schedules for hardware and software deliveries and integration with the BMDS.

The Contractor shall plan, integrate, execute and analyze test events in coordination with the five phase process and milestones directed in the MDA Directive 3002.03, BMDS Test Policy.

The types of testing covered by this Task Order are as follows:

a) BMDS Ground Tests, Focused (GTX); Ground Tests, Integrated (GTI); Ground Tests, Distributed (GTD);

b) BMDS Flight Tests (including Pre-Mission Tests (PMT) or System Pre-Mission Tests (SPMT));

c) Sensor Element Ground Tests (EGT) and Satellite Test Campaign (STC)

d) Level of Effort (LOE)

For each BMDS test event identified in A-D above, the Contractor shall meet the transmittal time and data handling requirements for each test data item as set forth in each test event’s Integrated Data Management Plan (IDMP) and Data Handling Plan (DHP). The Contractor shall deliver test mission data to the MDA Data Distribution Center (MDDC) as specified in MDA Directive 3200.06, Mission-Related Scientific and Technical Data – Information Management.

3.10.2 BMDS Ground Tests. (CLIN 0001)

The Contractor shall execute the following IMTP-defined BMDS ground test events for each test event defined in this Task Order and IAW the IDIQ SOW paragraph 3.10. Post-Flight Reconstruction (PFR)/ System Post-Flight Reconstruction (SPFR) activities will be limited to the Test Execution phase only, and all requirements, design and analysis will be conducted by MDA/ Sensors Engineering Directorate (SNE).

GTD-04e (N/P)

For each BMDS System Ground Test event the Contractor shall provide the following inputs:

a) Inputs to MDA/DT-conducted Event Working Group meetings, weekly status meetings, and Test Readiness Review (MDA briefing format)

b) Inputs to Joint Analysis Team (JAT) pre- and post mission analysis, reporting and reviews (Contractor format).

c) Status Reports to SN Mission Manager following each run day during scenario generator (i.e. Single Stimulation Framework (SSF), Objective Stimulation Framework (OSF)) Integration, IT, DR, and Runs for Record (RFR) (Contractor format)

d) Inputs to MDA Phase 1, 2, 3, 4, and 5 reviews (MDA briefing format).

e) Inputs to MDA Executive Test Requirements Review (ETRR), Executive Test Planning Review (ETPR), Executive Test Review (ETR), Executive Mission Review (EMR),Executive Quick Look Briefing (EQLB) and Executive Mission Data Review (EMDR) (Note: Both Pre-brief and Final brief in MDA briefing format).

f) Inputs to MDA/SN for test related Risk and BMDS Discrepancy Report (BDR) boards (MDA format).

g) Brief of Pre-Test Predictions (SN Analysis Review or equivalent) at completion of Phase 3 (contractor format)

h) Monte Carlo output files for each scenario, and associated configuration files (Mission Plan, Discrimination Database, System Adjustable Parameters and Environmental Variables)

i) Brief of test readiness (SN Test Readiness Review or equivalent) prior to entering Dry Runs and Runs for Record

j) Certification Data Package (CDP) for each test event No Later Than 14 days prior to the start of RFR (MDA format).

k) Brief of Post-Test Analysis (SN Analysis Review or equivalent) at least 3 days prior to presentation to the MDA JAT (Contractor format).

3.10.3 BMDS Flight Tests. (CLIN 0002)

The Contractor shall execute the following IMTP-defined flight test events for each test event defined in this Task Order and IAW the IDIQ SOW paragraph 3.10.

SPMT for FTG-08 should be included for this task order.

For each BMDS Flight Test event the contractor shall provide the following inputs:

a) Test Procedures for each Mission. Initial 14 days prior to mission best estimated test date (BETD). Final prior to mission Dress Rehearsal, nominally 2 days prior to the BETD (Contractor format, Government on-site review).

b) Certification Data Package (CDP) for each Mission. No later than 14 days prior to the mission BETD (MDA format).

c) Inputs to MDA Phase 1, 2, 3, 4, and 5 reviews (MDA briefing format)

d) Brief of Pre-Test predictions (BMDS System Missions Analysis Review (SMAR), or SN equivalent) for each Mission at the completion of MDA Phase 3, nominally held at 90 days prior to mission BETD (Contractor format)

e) Inputs to SN Readiness Reviews, Flight Readiness Reviews, Launch Readiness Reviews (FRR, LRR) and SMAR or equivalent as required (Note: Both Pre-brief and Final brief in MDA briefing format).

f) Inputs to MDA ETRR, ETPR, ETR, EMR, EQLB and EMDR (Note: Both Pre-brief and Final brief in MDA briefing format).

g) Pre-Mission Monte Carlo output files for each mission and associated configuration files (Mission Plan, Discrimination Database, System Adjustable Parameters and Environmental Variables) (as required).

h) Inputs to JAT pre- and post mission analysis, reporting and reviews (Contractor format).

i) Inputs to MDA/SN for test related Risk and BDR boards conducted by MDA (MDA format).

j) Status Reports to MDA/SN Mission Manager following each day during mission walkup (Contractor format, Site team input).

k) Inputs to MDA Flash Report following mission execution (MDA report format, site team input).

3.10.4 Satellite Test Campaign (STC). (CLIN 0003)

There are currently no Satellite Test Compaign activities planned for this Task Order.

3.10.5 Element Ground Test. (CLIN 0005)

The Contractor shall participate in the EGT events defined in this Task Order and IAW the IDIQ SOW paragraph 3.10. The SN element ground test campaign consists of several independent events specifically designed to address SN Critical Engagement Conditions (CEC). Data identified from past flight and ground tests will be used to develop scenario files for the EGT events.

The Contractor shall execute the CD and Element Ground Test Campaigns detailed as follows:

3.10.6 Test Provisioning. (CLIN 0004)

There are currently no Test Provisioning requirements planned for this Task Order.

3.11 Warfighter Support. (CLIN 0006)

There are currently no Warfighter Support requirements for this Task Order.

3.12 Modeling and Simulation (M&S). (CLIN 0007)

There are currently no M&S requirements for this Task Order.

TRANSITION. (CLIN 0012)

The Contractor shall perform Transition In activities as detailed in paragraph 4.1 and 4.3 of the IDIQ SOW to last no longer than sixty days (60d) post contract award.

ADDITIONAL TEST EFFORT. (CLIN 0010)

The Government may direct the use of LOE for Flight or Ground Testing to address advanced planning for potential future tests, and changes or special situations that may occur during the work in progress for a specific test event as directed in paragraph 5 of the IDIQ SOW.

APPENDICES.

Appendix A: Data Deliverables.

The Contractor shall meet the data deliverables, transmittal time, and data handling requirements for test mission data set forth in each test event’s IDMP and DHP and as directed in paragraph 3.10 of the IDIQ SOW.

For each test event assigned under Task Order 0001, a Draft and Final version (1 each) of the following shall be delivered under Contract Data Requirements List (CDRL) A006:

1. Sensors Test Support Plan within 45 calendar days after completion of MDA Phase 1 (contractor format)

2. Update to Sensors Test Support Plan within 30 calendar days after completion of MDA Phase 2 (contractor format)

3. Update to Sensors Test Support Plan within 15 calendar days after completion of MDA Phase 3 (contractor format)

4. Sensors Test Plan Review Brief (SN Pre-Phase 2 Review and MDA Phase 2 Review)

5. Sensors Configuration and Pre-Test Predictions Brief (SN Pre-Phase 3 Review and MDA Phase 3 Review) (contractor format)

6. CDP no later than 14 days prior to the start of RFR or the BETD as applicable (MDA format)

7. Sensors Test Readiness Review Brief (SN Pre-Phase 4 Review and MDA Phase 4 Review) (contractor format)

8. Sensors 48-hour Quick-Look Analysis Brief (contractor format)

9. Sensors 21-day Post-Test Analysis Brief (SN Pre-Phase 5 Review and MDA Phase 5 Review) (contactor format)

10. Final Test Report submitted within 90 days after completion of RFR or the BETD as applicable (contractor format)

11. Draft and Final Drawings, Schematics, and Inventory Lists

The contractor shall provide inputs to MDA in accordance with the event’s MDA Integrated Master Schedule (IMS). Inputs are normally as follows:

1. Inputs to MDA/DT-conducted Event Working Group meetings and weekly status meetings (MDA briefing format)

2. Inputs to the Integrated Operation Requirements document for an event (MDA document format)

3. Inputs on test risks to Government test event risk boards (MDA briefing format)

4. Inputs to MDA/DT-conducted readiness reviews (MDA briefing format)

5. Inputs to JAT pre- and post mission analysis, reporting and reviews (contractor format)

6. Inputs to MDA’s 1 hour Flash Report following flight test missions (MDA report format)

7. Status and issues inputs to the responsible SN Mission Manager following each test execution day during walkup events, scenario generator (i.e. SSF, OSF) Integration, Integration Tests (IT), Dry Runs (DR), and RFR (contractor format)

8. Inputs to MDA Phase 1, 2, 3, 4, and 5 reviews (MDA briefing format)

9. Inputs to MDA ETRR, ETPR, ETR, EMR, EQLB, and EMDR (MDA briefing format)

Note: Contractor format will be acceptable for other non-CDRL deliverables.

Appendix B: LIST OF ACRONYMS.

Acronyms

Appendix C: GFX List.

The Government will provide the Contractor the following GFI:

1. MDA/DE Test Objectives with required CEC/Empirical Measurement Events (EME) at 12 months prior to each test event.

2. (Flight Tests) Target and flight test scenario documentation at 12 months prior to each test event.

3. (Flight Tests) Two (Initial and Final) inputs of Government data will be provided for each test event for pre-mission analysis and Contractor mission data input development. Initial delivery no later than 180 days prior to each Mission BETD, and Final delivery no later than 120 days prior to each Mission BETD. Inputs will consist of the following:

a. Target Mission Description Document (or equivalent)

b. Up to 250 Monte Carlo trajectory sets (17-column format)

c. Up to 30 Debris trajectories and up to 12 unique models (including mapping file), if applicable

d. Approved Test Configuration (ATC) (or equivalent)

e. Range Safety Trajectories

f. Static Range Radar Cross Section (RCS) Measurements

g. X-patch inputs (CAD models, rsc, .xpd3)

h. Radar Data Signal Injection System (RDSIS)/ Radio Frequency Scene Generator (RFSG)/ Augmented Point Scatter Model (APSM) hi-fidelity models. N-Point APSM, if applicable.

Note: Trajectories and RCS must meet requirements. If RDSIS is desired by the Government, the Government will provide GFI the appropriate RCS models as GFE.

4. (Ground Tests) Scenario trajectory data and RCS data for each threat.

5. (Ground Tests) Test Case Description Document (TCDD)

6. IDMP, DHP, and Analysis Execution Plan (AEP) (initial no later than 3 months prior to test event and final at execution)

7. SPMT Plan will be provided by the Government no later than 3 months prior to the BETD.

8. (Flight Tests) Post-mission Truth Data will be provided by the Government in accordance with the event’s IDMP timeline.

9. SPFR Plan will be provided by the Government no later than 3 months prior to the execution.

The Government will provide the Contractor the following GFF/ GFE:

1. UEWR-CD sites and equipment with operators and maintainers, security, power, lighting, life support, and including a communication link for missions no later than 30 days prior to the execution for flight tests and no later than the start of scenario generator (i.e. SSF,OSF) integration testing for Distributed Ground Tests. The Government will coordinate the support of military operated sites as required.

2. Integrated System Test Center (ISTC)-1, ISTC-2 and PCIL Laboratories in Huntsville, AL with access, space for UEWR and CD HWIL console operations and initial analysis, computer network support, telephones, and HWIL strings for UEWR & CD.

Modeling and Simulation for pre-test predictions and pre-test End-to-End (E2E) analysis will be owned by the Government and operated by the Contractor for each test event.

For testing at remote locations not serviced by routine commercial air transport, the Government will provide transport of required personnel to/from the remote location from CONUS or other Sea/Aerial Port of Embarkation (SPOE/APOE), as directed.

image1.emf