DRAFT ABS Program Task Order_OS 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 Operations and Sustainment

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 Reliability, Availability and Maintainability

3.3.4 Software

3.3.5 Cybersecurity

3.4 RESERVED

3.5 OPERATIONS & SUSTAINMENT

3.6 IMPROVEMENTS & MODERNIZATION

4.0 TRAVEL

5.0 DELIVERABLES

1.0 BACKGROUND

The AirBorne Sensors (ABS) Program focuses on limited, streamlined development/integration of airborne sensor assets 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 Operations and Sustainment (O&S) base year 1.

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 O&S support of HALO-I, -II, and –III.

3.2 PROGRAM MANAGEMENT

3.2.1 Management

3.2.1.1 The contractor shall provide comprehensive O&S 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 The contractor shall prepare and submit for Government approval a comprehensive program plan (CDRL A002) that details the management and technical standard operating practices and procedures for the conduct of all activities to accomplish a technically sound and orderly implementation of operations.

3.2.1.4 The contractor shall maintain and provide an Integrated Master Schedule (IMS) (CDRL A003) that accounts for all on-going ABS efforts, including those of associate contractors.

The IMS shall include:

a) All prospective data collection activities;

b) Aircraft maintenance periods;

c) Other required aircraft-related activities.

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 The contractor shall conduct annual in-process review meetings to review overall contract and technical program status and the performance against the comprehensive program plan identified in section 3.2.1.3. All issues, actions, and briefing materials presented shall be documented and delivered to the Government (CDRL A004).

These meetings shall present:

a) Past data collection efforts; planning status; data reduction status; activity cost to date; and the status of all non-data collection flight operations, including aircraft and sensor maintenance, on-going I&M efforts, and all other notable issues and statuses related to the program.

b) Overall contract status, to include current hour and dollar usage along with a projection of hour and dollar usage to task order completion.

c) Support annual performance review meetings and provide a self-assessment to support performance evaluation.

d) Contractor’s performance of contract security requirements (PWS section

3.2.1.8) and changes during the applicable year.

3.2.1.7 The contractor shall provide the opportunity for Government attendance at contractor training sessions and provide ABS orientation training for Government personnel on an as needed basis.

3.2.1.8 The contractor shall perform contract security requirements in accordance with (IAW) the contract DD254, Contract Security Classification Specifications.

a) The contractor shall prepare and submit an Operations Security (OPSEC) plan (CDRL A002) identifying and assessing threat concerns and detailing implementation of security practices for the ABS effort.

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 Transition

3.2.1.9.1 Transition In

The contractor shall:

1) Verify possession and command of all necessary facilities, personnel, and certifications required to perform the ABS PWS requirements.

Or

2) Upon award, the contractor shall execute the contractor’s transition plan. The contractor shall be responsible for executing PWS requirements NLT 90 days after the Post Award Conference. The contractor shall ensure transitional change management process does not create a constructive change for the contract.

a) Develop a phase-in plan and coordinate schedule with the incumbent;

i. Provide a milestone schedule outlining the contractor’s process to acquire and/or obtain the necessary facilities, qualified trained personnel, and/or facilities certifications for the proper storage of data, equipment, and Government property;

ii. The schedule must reflect successful conclusion, acquisition, certifications, and onboarding of personnel NLT task order award. Government approval of the submitted schedule will be a condition of contract award;

b) Coordinate with the incumbent and the Government at the beginning of this task order;

c) Work with the incumbent to finalize a joint phase-in/phase-out plan;

d) Assume overall contract responsibility upon successful transfer from the incumbent, as determined by the Government.

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 A conference will be held finalizing the contractor’s standard cost and software data reporting (CSDR) process to satisfy the guidelines contained in the DoD 5000.04-M, CSDR Manual, and the requirements in the Government-approved CSDR Plan, DD2794.

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 Instruction 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 (GP) 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 The contractor shall develop, maintain, and promptly update technical data packages (TDP) (CDRL A014) reflecting the capabilities and capacity of each aircraft, sensors, instrumentation, and support systems.

3.3.1.4 The contractor shall develop and maintain operational and maintenance procedures, technical data, test plans, test procedures, test reports, evaluation plans, evaluation reports, mission interface documents, and other documents required to conduct activities assigned under this task order. (CDRL A014, CDRL A015, CDRL A016, CDRL A017, CDRL A018, CDRL A022)

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 Reliability, Availability, and Maintainability

3.3.3.1 The contractor shall implement a Reliability, Availability, and Maintainability (RAM) program, which will integrate all aspects of mission support relating to RAM: program management, equipment/system reliability, maintainability analysis to include preventive/scheduled maintenance, and spares engineering. The contractor shall implement a tailored reliability program to mitigate system failures, track reliability, and focus improvements and modernization of ABS systems. (CDRL A013 Mission Assurance Implementation Plan – “System Support Plan” and “Reliability” sections). A quarterly reliability status shall be provided.

3.3.3.2 The contractor shall update the spares analysis and use it to define the spares requirements and provisioning processes needed. The contractor shall establish and execute processes to identify long lead parts needed to support future requirements

(CDRL A021).

3.3.3.3 The contractor shall notify the COR, PM, and PCO in writing of any foreseen situation that would interfere with the availability of ABS aircraft/sensors or support systems, as soon as practical. Availability shall not diminish the contractor’s responsibility to meet the mission support/availability.

3.3.3.4 The contractor shall establish and maintain prevention and mitigation procedures for component obsolescence to ensure operational availability for the ABS Program and shall encompass electrical, electronic, electro-mechanical and mechanical parts and equipment, as well as developmental or Commercial Off the Shelf (COTS) software. A proactive diminishing manufacturing sources and materials shortages program shall be implemented IAW SD-22, Diminishing Manufacturing Sources and Materials Shortages best practices.

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 The contractor shall integrate, validate, document, and maintain ABS software and data (CDRL A013 Mission Assurance Implementation Plan – “Software Quality Assurance Plan,” “Software Development Plan,” and “Software Configuration Management Plan” sections, CDRL A018, CDRL A022).

a) The contractor shall follow standard processes, based on MAP Section 3.3.1

(Software Management Process):

• The contractor shall implement software management and infrastructure processes that are based on industry software best practices (e.g., IEEE 12207-2017, ISO/IEC/IEEE International Standard – Systems and Software

Engineering – Software Life Cycle Processes, CMMI-DEV, Capability Maturity Model Integration (CMMI) for Development for Aviation, Space, and Defense Organizations, MAP Provision 3.1, and these requirements:

o The contractor shall ensure assigned projects are planned, managed, tracked, controlled, and reported.

o The contractor shall be responsible for negotiating commitments and developing, documenting, and implementing the software development plan, software projects activities, products, and results.

b) The contractor shall establish, maintain, and report monthly a software change request schedule depicting the contractor’s plan (by software release) to resolve, implement, and verify any outstanding software change requests.

c) The contractor shall resolve, implement, and verify any outstanding software change requests only after Government approval to do so. The contractor shall maintain existing software. The contractor shall not develop any new software variants of the existing software or develop any new software without Government approval. No proprietary systems or software shall be developed as part of the ABS system.

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 contract 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 contract 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 RESERVED

3.5 OPERATIONS & SUSTAINMENT

3.5.1 The contractor shall inform the Government technical monitor of all scheduled or required aircraft inspections, maintenance, or known repair activity at least six months prior to the scheduled activity.

3.5.2 The contractor shall provide all aircraft and sensor subsystem O&S required to ensure mission success. The contractor shall:

a) Perform aircraft/sensor system modifications;

b) Perform all aircraft/sensor system O&S and minor unscheduled maintenance that is within available resources;

c) Provide engineering sustainment for mission-unique applications;

d) Provide trained flight crew, mission specialists, and ground crew support personnel;

e) Provide facilities (CONUS), which include tarmac for storage of non-active aircraft, environmentally controlled facilities for the storage and maintenance of instruments (sensor packages), and suitable hangar space to support ABS aircraft operation and sustainment and mission preparation activities);

f) Operate and maintain aircraft IAW DCMA Instruction 8210-1D, Contractor’s Flight and Ground Operations;

g) Obtain and maintain airworthiness certification for all aircraft;

h) Operate and maintain aircraft IAW the intent of Federal Aviation Administration

(FAA) flight worthiness and flight safety regulations;

i) Operate and maintain aircraft and mission systems IAW MIL-STD-882E, DoD

Standard Practice for System Safety;

j) Provide weekly technical status on all O&S activities;

k) Conduct sensor repairs as needed;

l) Provide G-550 aircraft Rolls Royce engine and Honeywell avionics warranties.

3.5.3 ABS aircraft and systems shall not be used for any activities other than those described in this PWS or as directed or approved by the PCO.

3.5.4 The contractor shall ensure that all aircraft modifications and airborne support / sensor equipment installation plans are reviewed and approved, as necessary, to maintain Government flight safety and airworthiness certifications.

MDA aircraft HALO-I/-II/-III are public use aircraft; therefore, the Government is the final airworthiness authority. Decisions concerning readiness for flight will be at the sole discretion of the Government. The contractor shall support such decisions by providing the proper documentation as it pertains to efforts associated with this contract.

In order to ensure continued airworthiness, the contractor shall hold a current Title 14 Code of Federal Regulations (CFR) Part 145 certificate. In the case of a contractor team, one of the team members must be 14 CFR 145 certificated. The 14 CFR 145 contractor or team member will have the responsibility for ensuring that all activities performed under this contract are compliant with 14 CFR 145, the 145-certificate holder’s General Maintenance Manual, all other applicable Title 14 CFR provisions and the Original Equipment Manufacturer’s manual.

Contractor disagreements with a determination made by the Government pursuant to this section shall be a dispute under the Disputes clause. However, nothing in this section nor any Government determination made in conjunction with this section shall excuse the contractor from proceeding with its duties under this contract.

3.5.5 The contractor shall manage, plan, and conduct system maintenance and support such that the Government’s primary objectives defined in the mission-specific MRDs are met and data collection systems are available for scheduled missions 100% of the time (CDRL A023). Scheduled missions are defined as missions that are authorized by the Government four weeks prior to BETD.

3.5.6 The contractor shall maintain a list of all support equipment needed to maintain and operate the ABS Program and its support infrastructure. The contractor shall provide an integrated maintenance plan with all scheduled inspections and maintenance requirements for each aircraft and support systems (CDRL A017).

3.5.7 The contractor shall conduct and document long-range planning activities to analyze requirements and identify new capabilities to support current/future programs. This shall include developing a method for prioritizing these requirements, analyzing the scope of new/extended work, verifying capability and capacity to accept or retain the work, and recommending to the Government which aircraft/system would optimally support the work.

a) The contractor shall evaluate ABS system capacity and plan long-range activities for baseline work, extended work, or new work.

b) The contractor shall perform readiness activities, including planning, systems engineering, and technical support for future missions.

c) The contractor shall prepare, maintain, and deliver a general aircraft/sensor capabilities document derived from information contained in the TDP to assist user programs considering the use of ABS assets (CDRL A014).

3.6 IMPROVEMENTS & MODERNIZATION

3.6.1 The contractor shall continually review and assess the suitability of the ABS system architecture and make recommendations for potential hardware and software upgrades to the aircraft, sensor systems, and support systems. These recommendations are to be prioritized and presented along with plans for upgrade (CDRL A025).

These upgrades are to support the following ABS primary objectives:

a) Mission Assurance – Ensure that the ABS aircraft are available to support data collection flights 100% of the time over the length of the program;

b) Develop a long-range strategic plan for continued sustainment of the ABS aircraft, sensor systems, and support systems;

c) Assess supportability issues (obsolescence, end-of-life, dwindling supply chain, etc.) and associated risks;

d) Provide new mission capabilities to support current/future mission requirements.

3.6.2 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 meet O&S requirements.

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 3.2.1.3, 3.2.1.8 Program Plan DI-MGMT-81797 A003 3.2.1.4 Integrated Master Schedule DI-MGMT-81861C A004 3.2.1.6 Report, Record of Meeting Minutes DI-ADMN-81505

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 (1921-3) DI-FNCL-81765C

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

A012 3.2.4 Small Business Utilization Report DI-MGMT-82041B

A013 3.3, 3.3.1.2, 3.3.2.3, 3.3.2.4, 3.3.3.1, 3.3.4.1

Mission Assurance Implementation Plan DI-MISC-80048

A014 3.3.1.3, 3.3.1.4,

3.5.7 Technical Data Package DI-MISC-80508B

A015 3.3.1.4 T&E Program Plan DI-NDTI-81284

A016 3.3.1.4 Verification/Final Report DI-MISC-80508B

A017 3.3.1.4, 3.5.6 Test Plan DI-NDTI-80566A

A018 3.3.1.4, 3.3.4.1 Software Change Request DI-MISC-80508B

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

A020 3.3.2.2 Hazardous Waste Report DI-MGMT-82129

A021 3.3.3.2 Recommended Spare Parts List DI-PSSS-80134B

A022 3.3.1.4, 3.3.4.1 Software Change Approval DI-IPSC-81440A

A023 3.5.5 Mission Status/Mission Reports DI-MISC-80508B

A024 Reserved

A025 3.6.1 Improvement and Modernization Report DI-MISC-80508B