HQ0147-09-R-0006 atch 15 Mission Spt Pricing Instructions.docx

HQ0147-09-R-0006

Attachment 15

HQ0147-09-R-0006

MDA/DTR

Airborne Sensors (ABS) Program

MISSION SUPPORT PRICING INSTRUCTIONS

(CLINs X005, X006, X007, and X008)

5 FEBRUARY 2010

MISSION SUPPORT PRICING INSTRUCTIONS

(CLINs X005, X006, X007, and X008)

1. Mission support pricing includes specific processes involving High Altitude Observatory One (HALO-I), HALO-II, HALO-III and Widebody Airborne Sensor Platform (WASP) aircraft in support of a Missile Defense Agency (MDA) Ballistic Missile Defense System mission. These processes include Pre-Mission Activities, Mission Execution and Post-Mission Activities as required.

2. For each scenario outlined in Section 3, the Offeror shall provide pricing for the following tasks and reporting requirements in accordance with the ABS SOW. The Offeror shall price the number of each scenario in the government fiscal year (FY) given in the attached table. The Offeror must provide basis of estimate documentation to support the pricing information.

2.1. Pre-mission Activities. The contractor shall perform the pre-mission activities to support HALO-I/II/III and WASP operations according to SOW Paragraph 4.1.2 inclusive. These pre-mission activities include the mission planning as identified in Section 3. Pre-mission activities also include accomplishing a Flight Readiness Review (FRR), Mission Readiness Review (MRR), local simulation flights as required, and dress rehearsal flights as required by the customer. The contractor will also deliver accurate, complete and timely Mission Assurance briefings to the government.

2.2. Mission Execution. The contractor shall perform the mission execution activities according to SOW Paragraph 4.1.3 inclusive. These mission execution activities include the deployment, employment, and re-deployment of the ABS aircraft and mission operators.

2.3. Post-Mission Activities. The contractor shall perform the post-mission activities according to SOW Paragraph 4.1.4 inclusive. These post-mission activities include processing the quick-look information and data reduction, and delivery of the information to MDA.

3. Mission Support Scenarios

3.1. Scenario A: Pacific Missile Range Facility (PMRF)

Scenario A entails the support of a BMDS intercept test executed at PMRF. The target will be launched from a C-17 and the interceptor will be launched from a land based launcher at PMRF. Mission support specifics are as follows:

· Deployment Length: 7 Days

· Flight window 1400-1800 ( HST)

· Mission Objective: Intercept imagery and signature, pre-intercept target signature, and pre-intercept interceptor imagery and signature data.

· Aircraft required: HALO I, HALO II and WASP

· Mission control representatives at PMRF

· Number of Flights: 3 flights, 1 mission dry run at home base, 1 dress rehearsal at the staging location, 1 mission flight at the staging location

· Pre-mission meetings: 1 single day sensor planning meeting in Hawaii, and 3 supporting telecons.

· Post mission meetings: 1 two day post mission meeting in Huntsville, AL

· All data reduction on site

· Deliverables: Mission Support Plan (MSP), raw data, quick look video, reduced imagery and signatures, final report as identified in ABS SOW

· Nominal schedule T-3 days- Dry Run on the ground T-2 days- Dress Rehearsal T-0- Mission day T+1 day- backup mission day T+3 days- backup mission day

3.2. Scenario B: Reagan Test Site (RTS)

Scenario B entails the support of a BMDS intercept test executed at RTS, Kwajalein Atoll. The target will be launched from Vandenberg Air Force Base, CA, and the interceptor will be launched from an island in the Atoll. Mission support specifics are as follows:

· Deployment Length: 7 Days

· Flight window 1400-1800 ( GMT)

· Mission Objective: Intercept imagery and signature, pre-intercept target signature, and pre-intercept interceptor imagery and signature data.

· Aircraft required: HALO I, HALO II and WASP

· Mission control representatives at RTS

· Number of Flights: 3 flights, 1 mission dry run at home base, 1 dress rehearsal at the staging location, 1 mission flight at the staging location

· Pre-mission meetings: 1 single day sensor planning meeting in Huntsville, AL, and 3 supporting telecons.

· Post mission meetings: 1 two day post mission meeting in Huntsville , AL,

· All data reduction on site

· Deliverables: Mission Support Plan (MSP), raw data, quick look video, reduced imagery and signatures, final report as identified in ABS SOW

· Nominal schedule T-3 days- Dry Run on the ground T-2 days- Dress Rehearsal T-0- Mission day

3.3. Scenario C: Navy Sea Range, Point Mugu, California

Scenario C entails the support of a BMDS intercept test executed at the Navy Sea Range, Point Mugu, CA. The target will be launched from a C-17 and the interceptor will be launched from a land based launcher Point Mugu. Mission support specifics are as follows:

· Deployment Length: 7 Days

· Flight window 1000-1400 (PST)

· Mission Objective: Intercept imagery and signature, pre-intercept target signature, and pre-intercept interceptor imagery and signature data.

· Aircraft required: HALO I, HALO II

· Mission control representatives at Point Mugu

· Number of Flights: 3 flights, 1 mission dry run at home base, 1 dress rehearsal at the staging location, 1 mission flight at the staging location

· Pre-mission meetings: 1 single day sensor planning meeting in Huntsville, AL, and 3 supporting telecons.

· Post mission meetings: 1 two day post mission meeting in Huntsville , AL,

· All data reduction on site

· Deliverables: Mission Support Plan (MSP), raw data, quick look video, reduced imagery and signatures, final report as identified in ABS SOW

· Nominal schedule T-3 days- Dry Run on the ground T-2 days- Dress Rehearsal T-0- Mission day T+1 day- backup mission day T+3 days- backup mission day

3.4. Scenario D: Edwards Air Force Base, CA (EAFB)

Scenario D entails the support of an Airborne Laser test executed at the Navy Sea Range, Point Mugu, CA. The target will be launched from San Nichols Island, CA, and the Airborne Laser aircraft will stage from EAFB. Mission support specifics are as follows:

· Deployment Length: 7 Days

· Flight window 2000-2400 (PST)

· Mission Objective: Perform Airborne Laser Airborne Diagnostic Target (ADT) functions.

· Aircraft required: HALO III

· Mission control representatives at EAFB

· Number of Flights: 3 flights at the staging location

· Pre-mission meetings: 1 two day sensor planning meeting in EAFB and 3 supporting telecons.

· Post mission meetings: 1 two day post mission meeting in EAFB

· All data reduction on site

· Deliverables: Mission Support Plan (MSP) and final report as identified in ABS SOW

· Nominal schedule T-3 days- Dry Run T-2 days- Dress Rehearsal T-0- Mission day