DRAFT ABS Program Task Order_Mission Planning and Test Execution PWS_5.2.25.pdf

Solicitation # HQ0855-25-R-E001

Attachment #1 – Performance Work Statement i

MDA/DTR

Missile Defense Agency

Building 5222 Martin Road Redstone Arsenal, AL 35898-0001

AirBorne Sensors Program Year 1 Mission Planning and Test Execution

Performance Work Statement

March 17, 2025

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Approved for Public Release 25-MDA-12077 (24 Apr 25) ii

TABLE OF CONTENTS

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 REQUIREMENTS

3.1 General

3.2 PROGRAM MANAGEMENT

3.2.1 Management

3.2.2 Cost Reporting

3.2.3 Government Property

3.2.4 Small Business Utilization

3.3 MISSION ASSURANCE

3.3.1 Configuration Management

3.3.2 Environment, Safety and Occupational Health (ESH)

3.3.3 Reserved

3.3.4 Software

3.3.5 Cybersecurity

3.4 MISSION AND TEST EXECUTION

3.4.1 Pre-Mission Activities

3.4.2 Mission Execution

3.4.3 Post-Mission Activities

3.4.4 Mission Locations

3.4.5 Deployment Pricing

3.5 RESERVED

3.6 RESERVED

4.0 TRAVEL

5.0 DELIVERABLES

Attachment 1 - Standard Mission Support Scenario

Attachment 2 - Planned Mission Outline

1.0 BACKGROUND

The AirBorne Sensors (ABS) Program focuses on limited, streamlined development/integration of airborne sensor assets and flexible contracting vehicles to support a wide variety of Missile Defense Agency (MDA) and other Government agency customers. The ABS Program includes the High ALtitude Observatory (HALO) -I, -II, and -III aircraft (modified Gulfstream 550s), Portable Uplink Ground Station (PUGS), and Mission Data Center (MDC).

This task order is for mission support and mission data reduction/analysis activities.

2.0 APPLICABLE DOCUMENTS

• AFI 90-901, Operational Risk Management, 11 July 2008

• DCMA INST 8210-1D, Contractor’s Flight and Ground Operations, 6 February 2023

• Joint Travel Regulations (JTR), at https://www.defensetravel.dod.mil/

• MIL-STD-882E, Change 1, DoD Standard Practice for System Safety, 27 September

• MIL-HDBK-516C, Airworthiness Certification Criteria, 12 December 2014

• MIL-STD-881F, Work Breakdown Structures for Defense Materiel Items, 13 May 2022

• MIL-HDBK-1785, System Security Engineering Program Management Requirements, 1 August 1995

• National Aerospace Standard (NAS) 411, Hazardous Materials Management Program, 30 September 2020

• MDA-QS-001-MAP-Rev C, Missile Defense Agency Assurance Provisions (MAP), 1 October 2019

• SD-22, Diminishing Manufacturing Sources and Materials Shortages Guidebook, March

• MDA Manual 5000.64-M, Accountability and Management of MDA Equipment and Other Accountable Property, 26 June 2020

• DoDM 5000.04, Cost and Software Data Reporting, Effective 7 May 2021

• MDA Directive 4250.02, Missile Defense System Cost Estimating, 21 November 2022

• MDA Cost Estimating and Analysis Handbook, Rev. 3.0, dated 22 July 2021

3.0 REQUIREMENTS

3.1 General

The period of performance of this task order is one year from date of task order award.

This task order is for mission support and operations of the contract.

3.2 PROGRAM MANAGEMENT

3.2.1 Management

3.2.1.1 The contractor shall provide comprehensive program management to ensure the technical, schedule, and cost objectives of the task order are met. The contractor shall:

a) Ensure timely and effective communication of all task order status and issues.

b) Provide adequate numbers of qualified management, technical, engineering, flight operations, and support personnel to accomplish the requirements of this Performance Work Statement (PWS).

3.2.1.2 The contractor shall define a Contract Work Breakdown Structure (CWBS) and integrate with cost and schedule management tools (CDRL A001).

3.2.1.3 Reserved

3.2.1.4 Reserved

3.2.1.5 The contractor shall identify a single point of contact to the Government for management of the contractor effort and coordination with the Government to ensure successful implementation of task order requirements.

3.2.1.6 Reserved

3.2.1.7 Reserved

3.2.1.8 The contractor shall perform contract security requirements in accordance with

(IAW) the contract DD254, Contract Security Classification Specifications:

a) Reserved

b) The contractor shall obtain and maintain up to SECRET/NOFORN level electronic connectivity to the MDA CNet to provide classified post-mission data and reports.

3.2.1.9 Reserved

3.2.1.9.1 Reserved

3.2.1.9.2 Reserved

3.2.1.10 The contractor shall develop/review and provide subject matter expertise on ABS-related technical or contractual documentation, when requested by the Government.

3.2.1.11 The contractor shall participate in various Government approved technical interchange meetings, conferences, and symposiums associated with airborne test and measurement activities.

a) The contractor shall prepare and present technical papers and/or briefings that address the subject/issues under consideration as directed.

b) The contractor shall submit technical papers and/or briefings for conferences and symposiums to the Government 60 days in advance of meetings, conferences, and symposiums for approval.

c) The contractor shall submit technical papers and/or briefings for technical interchange meetings to the Government five business days in advance.

3.2.1.12 The contractor shall provide tours of ABS assets as required.

3.2.2 Cost Reporting

3.2.2.1 The contractor shall provide financial controls to allow for the tracking of expenditures on behalf of the various users and for “core” (non-user funding) support funds.

3.2.2.2 The contractor shall prepare and submit a comprehensive monthly progress report detailing all significant activities by Government fiscal year funding (CDRL A006, CDRL A007):

a) Cost status (including cost estimates, funding allocation, costs to date, invoicing status, and projected funding balance);

b) A schedule forecasting future activities;

c) Milestone accomplishments;

d) Programmatic issues; and

e) Mission scorecard with primary and secondary objectives results.

3.2.2.3 The contractor shall notify the Contracting Officer Representative (COR), Program Manager (PM), and Procuring Contract Officer (PCO), in writing, of projected or known cost/budget problems as soon as they are identified.

3.2.2.4 The contractor shall provide reports and informal reviews that integrate technical accomplishments with the cost and schedule status of work progress on the contract, when requested by the Government.

3.2.2.5 The contractor shall systematically collect and report actual task order costs segregated by non-recurring and recurring, functional category, and by unit and/or lot as designated by the Cost and Software Data Reporting (CSDR) Plan DD2794 to provide DoD cost analysts with needed data to estimate future costs (CDRL A008, CDRL

A009, CDRL A010).

3.2.2.6 The contractor shall provide the Government with a list of all performers on the contract in a resource distribution table. The contractor shall notify the Government of all subcontractors expected to have a contract value greater than $50M or, if the subcontractors have not been selected, the subcontracted effort in this category. At that time the Government will determine if subcontractor direct reporting is required. The contractor shall flow down requirements contained in its prime contract to the subcontractors required to report. (CDRL A006 through CDRL A010)

If a subcontractor is not initially estimated to exceed $50M, but during the life of the contract, is indeed estimated to exceed $50M, the contractor shall identify this subcontractor to the Government. The contractor’s submission cannot be evaluated if the subcontractor’s submissions have not been delivered to MDA Cost Estimating Directorate (MDA/DZJ). If this occurs, the contractor’s submission will be rejected due to incomplete information.

3.2.2.7 Reserved

3.2.2.8 The contractor shall accept or propose changes to expand the Government-provided preliminary WBS as provided in the CSDR Plan DD2794 to represent how the contractor plans to accomplish the entire contract scope of work consistent with the contractor’s internal organizations and processes.

The contractor shall support the Common Cost Methodology Working Group (CWG) as described in MDA Directive 4250.02, Missile Defense System Cost Estimating. The contractor (and major subcontractors) shall support quarterly CWG meetings, perform cost estimating analysis IAW the MDA Cost Estimating and Analysis Handbook Rev 3.0, dated 22 July 2021, and provide data to support the CWG.3.2.3 Government Property.

3.2.3.1 Property Management

The contractor shall manage Government property (i.e., both Government Furnished Property (GFP) and Contractor Acquired Property (CAP)) IAW Federal Acquisition Regulation (FAR) 52.245-1 and its associated Defense Federal Acquisition Regulation Supplement (DFARS) clauses. GFP and CAP inventory levels shall be reported IAW CDRL A011, Government Property Inventory Report. The data fields required for this reporting are listed in Data Item Description (DID) DI-MGMT-80441D, Government Property Inventory Report, which can be found on the Defense Logistics Agency (DLA) ASSIST website.

3.2.3.2 Physical Inventory

The contractor shall perform a physical inventory of Government property (i.e., GFP and CAP) annually with the Government’s fiscal year (October – September). This includes Government property located at subcontractor facilities.

3.2.3.3 Acquisition of CAP

Prior to the acquisition or fabrication of items of CAP that are not pre-approved on a Basis for Estimate or Bill of Materials, the contractor shall obtain Contracting Officer’s written authorization for all items of any value.

3.2.3.4 End Item Deliverable(s)

When an item of Government-Furnished Material (GFM) with a unit acquisition cost of $250,000 or more is consumed into an end item being delivered, the contractor shall upload an attachment to the Wide Area Workflow (WAWF) Receiving Report with the following information:

a. MDA asset identification number of GFM (if known)

b. Item description of GFM

c. Serial number of GFM

d. Unique item identifier of GFM (if applicable)

e. Unit acquisition cost of GFM

f. Item description of end item

g. Serial number of end item

3.2.3.5 CAP Delivery

In accordance with DFARS 252.232-7003(b), the contractor is required to submit a

WAWF Receiving Report at the time of each delivery to include CAP deliveries. The contractor shall complete and upload the MDA Minimum Data Elements for Hardware & Software Deliverables spreadsheet (DA-86-T02) (Section J – Exhibit XX) as an attachment to each WAWF Receiving Report submitted. The spreadsheet shall include the listed data elements for each item being delivered to include the fully burdened unit acquisition cost.

The contractor shall provide a Unique Item Identifer (UII) for all delivered items, to include CAP IAW DFARS 252.211-7003.

3.2.3.6 Transfer of Government Furnished Property

The contractor shall formally submit transfer requests in writing to the Contracting

Officer in accordance with FAR 52.245-1(j)(1). Once transfer of GFP requests are approved and authorized by contract modifications to both the losing and gaining contracts, the contractor shall use the GFP module in the Procurement Integrated Enterprise Environment to document the property transfer.

3.2.3.7 Maintenance of Government Property

The contractor shall repair or replace items of Government property that have not been deemed as excess to the contract when the repair or replacement costs does not exceed $5,000.00. The Contracting Officer’s written authorization is required prior to the repair or replacement of Government Property items when the repair or replacement costs exceeds $5,000.00. If a Government Property Administrator is assigned to the contract, his or her approval/recommendation is required prior to the request being sent to the Contracting Officer. The contractor shall support the repair or replacement costs exceeding $5,000.00 with quotes from a minimum of three sources.

3.2.3.8 Disposition of Government Property

Disposal of excess items shall be conducted at the time the items are determined to be excess to contractual needs and in accordance with FAR 52.245-1 and DFARS 252.245-7005.

Proceeds from the disposal of scrap shall be credited to overhead. All other proceeds received from the disposal of Government property shall be applied as a credit against the next contract billing.

Items requiring demilitarization (DEMIL) will be processed in accordance with DoDM

4160.28. Prior to any DEMIL action, the contractor shall notify the Contracting Officer or Plant Clearance Officer of the DEMIL requirement and requisite funding. No DEMIL action shall take place until the requirement is funded via contract modification.

3.2.3.9 Communications Security (COMSEC) Property

COMSEC property, if provided, shall not be dispositioned through Plant Clearance Automated Reutilization Screening System (PCARSS). Disposition instructions for COMSEC property shall be requested in writing to the PCO and coordinated with the MDA COMSEC Manager.

3.2.3.10 Contract Closeout for Government Property

In preparation for the prompt completion of contract closeout actions, the contractor shall perform a final inventory at the end of the period of performance (CDRL A011).

The contractor shall coordinate the final inventory with MDA to ensure that a Government representative is present. This final inventory requires the physical count of all Government Property (both GFP and CAP) at all locations (to include subcontractor locations) and subsequent reconciliation against the contractor’s and subcontractor’s Property Management System records.

Once all Government Property close-out actions are complete, the contractor shall submit a written certification to the Government Property Administrator stating that all Government Property closeout actions have been completed and that no Government Property remains accountable against this contract. This certification includes all subcontractor locations.

3.2.4 Small Business Utilization

IAW with the IDIQ base PWS 3.2.4, the contractor shall submit a Small Business Utilization Report (CDRL A012) derived from the Small Business Participation Commitment Document (Section J, Attachment 7) to the MDA Office of Small Business Programs (MDA/SB). Reporting should be a single report (semi-annually) cumulative covering all task orders.

3.3 MISSION ASSURANCE

The contractor shall prepare, maintain, and comply with a Mission Assurance Implementation Plan (MAIP) IAW a Government approved version of the MDA Assurance Provisions (MAP) tailored specifically by the contractor for the ABS Program (CDRL A013).

3.3.1 Configuration Management

3.3.1.1 The contractor shall work with the Government and associate contractors to manage data and ensure documents remain current and easily accessible.

3.3.1.2 The contractor shall perform configuration management of all ABS hardware and software, including mission related databases, files, and mission unique software (CDRL A013 Mission Assurance Implementation Plan – “Configuration Management Plan” section).

3.3.1.3 Reserved

3.3.1.4 Reserved

3.3.1.5 The contractor shall ensure e-mail, briefings, and data provided by the contractor are in a format which is compatible with MDA information management systems.

3.3.2 Environment, Safety, and Occupational Health (ESH)

3.3.2.1 The contractor shall integrate applicable federal, state, and local ESH laws and regulations, Executive Orders, treaties, and policies into all phases of program execution to minimize impact on program life cycle cost. All facilities, processes, and operations (including those of subcontractors) shall be compliant to ensure a safe work environment IAW FAR 23, “Environment, Sustainable Acquisition, and Material Safety.”

3.3.2.2 The contractor shall minimize the impact of environmental laws, regulations, and policies on the life cycle of the ABS Program through pollution prevention using National Aerospace Standard (NAS) 411, Hazardous Material Management Program, as a guide (CDRL A019, CDRL A020).

3.3.2.3 The contractor (and subcontractors as applicable) shall comply with mitigations outlined in the National Environmental Protection Act (NEPA) documentation developed by MDA (CDRL A013 Mission Assurance Implementation Plan – “Environmental/Safety Plan” section). The NEPA process assesses environmental impacts from all test and evaluation approaches and the pollution prevention actions will strive to mitigate programmatic and operational life cycle impacts from ESH issues.

3.3.2.4 The ABS program has implemented a system safety program IAW MIL-STD-882E, DoD Standard Practice for System Safety, to ensure all safety hazards are identified, eliminated, accepted, or controlled, and verified within the constraints of program cost, schedule, and performance. The contractor shall formally identify risk hazards and mitigations, and assess their final level of risk for Government approval as defined in MIL-STD-882E (CDRL A013 Mission Assurance Implementation Plan – “Safety” section).

3.3.2.5 The contractor shall notify the COR, PM, and PCO in writing of any mishap IAW DCMA INST 8210-1D Contractor’s Flight and Ground Operations. The contractor shall cooperate with and support Government-led mishap investigations as required.

3.3.3 Reserved

3.3.4 Software

ABS software supports mission planning, mission operations, instrument and instrumentation control, communications, data collection, as well as mission data analysis in support of the overall ABS Program.

3.3.4.1 Reserved

3.3.5 Cybersecurity

All data that is controlled unclassified information (CUI) on nonfederal information systems shall be protected in accordance with National Institute of Standard and Technology (NIST) SP 800-171 (latest revision).

3.3.5.1 Information Management and Control Plan (IMCP)

The contractor shall flow the IMCP to its first tier subcontractors with the requirement to flow down the IMCP to all tiers of the supply chain that utilize CUI. Through the

IMCP, the contractor shall address implemented practices to minimize and restrict the sharing and/or flow of CUI down the entire supply chain to only those suppliers who have a need-to-know/lawful government purpose. This includes, but is not limited to, minimizing the information provided on contracts/purchase orders for procurement of logistics and transportation services, systems, or critical components. The contractor shall also address in the IMCP its plan for providing adequate security and for executing cyber incident reporting.

The contractor and its subcontractors shall submit a Supplier Compliance Supplement (see paragraph 3.3.5.2). The contractor and its subcontractors shall submit or make their System Security Plan (SSP) and Plan of Action and Milestones (POA&M) available for inspection to the Government as required.

The contractor shall provide adequate security on covered Contractor information systems IAW DFARS clause 252.204-7012, “Safeguarding Covered Defense Information and Cyber Incident Reporting” (hereafter referred to as “DFARS 7012”).

Hereafter, Covered Defense Information (CDI), CUI, Technical Data, or Operationally Critical Support information is referred to as CUI.

The contractor shall maintain the IMCP throughout the period of performance and deliver periodic updates IAW CDRL A005. Each update to the IMCP will be incorporated into the task order at time of approval.

3.3.5.2 IMCP Supplier Compliance Supplement (SCS)

The contractor, and all Subcontractors handling CUI, shall document suppliers that receive or generate CUI in performance of the task order and maintain on file an IMCP SCS. The contractor shall complete and deliver the IMCP SCS IAW CDRL A005.

3.3.5.3 Marking, Delivery, and Destruction

The contractor shall use DoDI 5200.48, “Controlled Unclassified Information,” and any applicable Security Classification Guide for the identification, marking, safeguarding, dissemination, records management, and destruction of CUI. The contractor shall adhere to Information Security Oversight Office Notice 2019-03, “Destroying Controlled Unclassified Information in Paper Form.” The contractor shall address questions of categorization of CUI to the cognizant PCO or COR.

3.4 MISSION AND TEST EXECUTION

The contractor shall provide mission support functions. Mission and test execution includes pre-mission activities, mission execution, post-mission activities, and other support events as required. A standard mission deployment is outlined in Attachment

1. The contractor should plan to support up to, but not limited to, the missions as detailed in Attachment 2.

3.4.1 Pre-Mission Activities

Pre-mission activities include Flight Readiness Review (FRR), Due Diligence, Mission

Readiness Review (MRR), Mission Support Plan (MSP), local simulation flights, dress rehearsal, and dry run flights, as required by the mission and the customer.

3.4.1.1 The contractor shall coordinate mission execution with the

ABS Government Program Manager, and, as directed, the contractor shall coordinate with other Government agencies, support contractors, test range representatives, and other user agency’s support contractors (CDRL A023). The contractor shall perform site survey activities as needed and requested by the customer and shall support early deployment activities to ensure adequate integration with range systems.

The contractor shall respond effectively, efficiently, and rapidly to any changes in test requirements and test conditions.

3.4.1.2 The contractor shall conduct pre-flight tests of sensors and support equipment to ensure optimal performance during mission execution.

3.4.1.3 The contractor shall perform Continental United States (CONUS) training flights during the task order period as necessary for flight crew and operator qualification.

3.4.1.4 The contractor shall coordinate with potential users, as directed by the Government, to determine specific airborne data collection activities.

a) The contractor shall, in coordination with the ABS Government Mission Team, work closely with each user to address those tasks necessary to satisfy the user requirements.

b) Specific data-gathering requirements will be provided to the contractor in the form of a user-prepared Mission Requirements Document (MRD). The contractor shall conduct planning to accomplish the requirements provided in this MRD.

c) The contractor shall review the MRD, as well as other user program documentation, and participate in initial planning and requirements meetings with potential users.

d) The contractor shall provide a descriptive work summary, cost estimate, and support schedule.

e) For each mission data collection activity, the contractor shall prepare and submit a MSP 30 days prior to Best Estimated Test Date (BETD) or otherwise based on Government discretion (CDRL A023), for Government approval, to include:

• Support schedules and activities;

• Instrumentation configuration;

• Derived mission objectives from MRD;

• Test Support Positions (TSPs);

• Mission team members;

• Performance predictions;

• Data management information.

The contractor shall participate in pre-mission planning meetings as requested by the Government.

For each mission, the contractor shall prepare and present briefings to address instrumentation capabilities, aircraft performance, equipment performance, support status, and data management and delivery.

The contractor shall procure, develop, update, install, checkout, and calibrate all sensor platforms/configurations as required to conduct mission support IAW the MSP, including integration and operation of guest sensors. The contractor shall coordinate with and provide assistance to other contractors in support of guest sensors.

3.4.1.5 The contractor shall assess measurement requirements stated in the MRD as directed by the Government, and:

a) Recommend instrumentation configurations and/or modifications as required to configure the aircraft;

b) Define and assess aircraft placement and maneuvers required to ensure optimal sensor performance with regard to the mission requirements.

3.4.1.6 The contractor shall provide any modification, upgrades, or procurements to the PUGS system, in order to relay voice and data communications with other ABS assets, as needed for each mission.

3.4.1.7 The contractor shall perform a local simulation flight for each test event, typically before deployment.

3.4.1.8 The contractor shall establish channels of communication, in coordination with the Government Mission Team, with test range personnel/organizations to address the details of various data collection-related topics, to include range safety, target trajectory, voice and data communications, beacon parameters, logistical support, and aircraft vectoring instructions.

a) Planning for range interface shall include participation in pre-deployment range interface meetings;

b) The contractor shall coordinate with range safety representatives to ensure that the aircraft test support position meets all range-imposed safety constraints and aircraft performance safety standards.

3.4.1.9 The contractor shall establish channels of communication with civil and military air traffic control agencies to ensure availability of air space and submission of any required notifications or flight plans.

3.4.1.10 The contractor shall establish, coordinate, and submit an aircraft itinerary for each data collection activity, identifying all Government facilities, airfields, customs offices, and commercial airports to be utilized as primary or secondary aircraft stops.

3.4.1.11 The contractor shall arrange for or provide, in coordination with the Government Mission Team, pre-flight logistical support to designated deployment location, which is mission-dependent.

3.4.2 Mission Execution

Mission execution activities include the deployment and retrograde of the ABS aircraft, equipment, and mission operators.

3.4.2.1 The contractor shall:

a) Deploy ABS systems (aircraft, sensor platform, PUGS, etc.), aircraft crew, and all required technical personnel to support each data collection activity;

b) Conduct airborne flight operations;

c) Perform mission data collection;

d) Coordinate all mission execution activities with the Government Mission

Team daily.

e) Provide a Daily Status Report (DSR) at the end of each mission support activity to the Government Mission Team.

3.4.3 Post-Mission Activities

Post-mission activities include processing the quick-look information, data reduction, and delivery of the mission data to MDA or supporting program.

3.4.3.1 The contractor shall provide a quick-look assessment of their support performance and data collections and communicate these results to the “on-site” Government test representative. The Government will review and have final approval of all reports prior to distribution.

a) The contractor shall process/reduce collected data into radiometric calibrated test data, photo documentation data, engineering parametric information, or other forms required by the user.

b) The contractor shall conduct data reduction operations to ensure that all mission reports and data required by the MRD or Data Handling Plan are delivered on schedule (CDRL A023, CDRL A024).

c) The contractor shall support post-mission technical interchange meetings.

d) The contractor shall provide post-mission reports as specified in the MRD or

Mission Data Handling Plan (CDRL A023).

3.4.4 Mission Locations

Deployment locations may include but are not limited to: Alabama, Alaska, California, Florida, Guam, Hawaii, Puerto Rico, and RTS Kwajalein Atoll, Republic of the Marshall Islands. Travel to other locations may be required for pre-mission planning and post-mission data reviews.

3.4.5 Deployment Pricing

The contractor shall break out the price of each aircraft deploying to each planned deployment location.

3.5 RESERVED

3.6 RESERVED

4.0 TRAVEL

The contractor shall expect to travel to various locations to include manufacturing sites, integration sites, training sites, test sites and meetings as required. Locations may be within CONUS and outside the continental United States (OCONUS). Under no circumstance shall the contractor incur travel costs in excess of the funded CLIN amount.

All travel that is directly billed under this contract shall be in accordance with the JTR guidance.

The contractor is required to ensure Common Access Card renewals are accomplished in a timely fashion and planned for in the most cost effective manner (i.e. planned around existing mission related travel plans or selecting the closest facility to renew accordingly).

Travel within the local area or duty station to attend meetings, conferences, seminars, or perform work shall be considered a cost of doing business and shall not be separately reimbursed as a travel expense. Local area travel is defined as a 50-mile radius around the duty location or designated place of employment. Travel outside a 50-mile radius is considered ‘Non-Local’ travel and mileage is reimbursable if otherwise allocable, allowable, and reasonable.

The contractor shall propose travel to support the test events associated with the Planned Mission Outline (Attachment 2) IAW the Standard Mission Support Scenario (Attachment 1).

5.0 DELIVERABLES

The contractor shall deliver data by the Contract Data Requirements List (CDRL), DD Form 1423. Specific CDRL items will be identified in individual Task Orders under this contract.

Reports and data related to tasks defined in this contract are listed below:

CDRL Paragraph Name DID

A001 3.2.1.2 Contract Work Breakdown Structure DI-MGMT-81334D

A002 Reserved A003 Reserved A004 Reserved

A005 3.3.5.1, 3.3.5.2 Information Management and Control Plan DI-MGMT-82383 A006 3.2.2.2, 3.2.2.6 Contract Funds Status Report (CFSR) DI-MGMT-81468A A007 3.2.2.2, 3.2.2.6 Status Report DI-MGMT-80368A A008 3.2.2.5, 3.2.2.6 Cost and Hour Report DI-FNCL-82162

A009 3.2.2.5, 3.2.2.6 Maintenance and Repair Parts Data Report DI-MGMT-82163

A010 3.2.2.5, 3.2.2.6 Contractor Business Data Report (DD Form

1921-3) DI-FNCL-81765C

A011 3.2.3.1, 3.2.3.10 Government Property Inventory Report DI-MGMT-80441D

A012 Reserved

A013 3.3, 3.3.1.2 Mission Assurance Implementation Plan DI-MISC-80048

A014 Reserved

A015 Reserved

A016 Reserved

A017 Reserved

A018 Reserved

A019 3.3.2.2 Hazardous Materials Management Program Report DI-MGMT-81398D

A020 Reserved

A021 Reserved

A022 Reserved

A023 3.4.1.1, 3.4.1.4,

3.4.3.1 Mission Status/Mission Reports DI-MISC-80508B

A024 3.4.3.1 Mission Data Products DI-MISC-80508B A025 Reserved

Attachment 1 - Standard Mission Support Scenario

Below is a typical mission support scenario. Each mission may vary based on specific customer requirements, and this is only intended to be representative of a nominal mission.

• Dates:

o FY26 and FY27

• Locations:

o Including, but not limited to: Alabama, Alaska, California, Florida, Guam, Hawaii, and RTS Kwajalein Atoll, Republic of the Marshall Islands.

• Mission Objective: Collect optical data of targets, interceptors, or multiple reentry vehicles as defined in the mission requirements document.

• Systems required:

o HALO-I, HALO-II, HALO-III, PUGS/Range Representatives, and MDC as required by the missions.

• Number of Flights:

o Standard mission events should include one local simulation, round-trip ferry flights, one dress rehearsal, one BETD, and one backup.

• Backup Days: Plan for one backup day without flight, and one with flight per event.

• Pre-mission meetings: Including, but not limited to: Three day planning meetings and three supporting teleconferences.

• Post mission meetings: Including, but not limited to: Three day post mission meetings.

• Deliverables: Mission Support Plan (MSP), raw data, quick look video, reduced imagery and signatures, final report as identified in ABS Program Year 1 Mission Planning and Test Execution PWS 3.4.3.1.

• Nominal schedule o L-12 days – PUGS Setup and Checkout o L-10 days – Ground Support Crew deploy o L-6 days – Aircraft deploy o L-4 days – Dry Run on the ground o L-2 days – Dress Rehearsal o L-0 Mission day o L+1 – L+2 Backup Mission days

Attachment 2 - Planned Mission Outline

Below is the planned number of missions for each platform and location for this period of performance. Exact numbers of mission may vary based on specific customer requirements, and this is only intended to be representative of a nominal mission.

HALO-I HALO-II HALO-III PUGS

Alabama 0 0 0 1 Alaska 1 1 1 0 California 1 1 1 0 Florida 1 1 1 0 Guam 1 1 1 0 Hawaii 1 1 1 4