Atch 3- Initial Order PWS .pdf

PERFORMANCE WORK STATEMENT

FOR

MEDIUM ALTITUDE LONG ENDURANCE UNMANNED AIRCRAFT OPEN MISSION

SYSTEMS INTEGRATION SUPPORT, KIT PROCUREMENT, AND SUSTAINMENT

TASK ORDER 0001

03 FEBRUARY 2023

1.0 INTRODUCTION

USSOCOM requires a Procurement and Sustainment contract for an open mission system architecture and command and control system with advanced on-aircraft compute, artificial intelligence, machine learning, and dissemination capabilities.

Systems will provide operators the ability to command and control, collect, analyze, and share information from multiple SOF aviation and ground platforms in an expeditionary form-factor via man-portable Tactical Common Datalinks. The Command is seeking a flexible, stand-alone, aircraft agnostic, open mission system architecture and command and control system solution capable of being integrated on air or ground vehicle currently integrated, tested, qualified, and produced. The system should have demonstrated capabilities for aided target detection and recognition, an open-standards-based middleware infrastructure, services to support host-platform data feeds from the MQ-1C/ER mission computer and avionics data buses, and support for Assured Position, Navigation, and Timing onboard an MQ-1C/ER.

1.1 Scope

This Task Order Performance Work Statement (PWS) sets forth the requirements for the integration, test, assessment, procurement, fielding support and sustainment of core open mission system architecture (hardware and software), command and control system (expeditionary mission interface), and aircraft mission system capabilities for the Medium Altitude, Long Endurance, Tactical (MALET) Unmanned Aircraft System (UAS) programs.

The Contractor shall provide program support, conduct integration and test, deliver hardware and software solutions, execute sustainment activities, complete studies and analysis, and deliver required reports and artifacts. Requirements include delivery of five (5) core open mission system architecture A-Kits and an option CLIN to provide nine (9) command and control expeditionary mission interface B-Kits.

1.2 Period of Performance

The period of performance of this Task Order is 12 months from contract award.

2.0 TASKS

The Contractor shall perform the tasks identified below to successfully execute this Task Order.

2.1. Program Management Support

The Contractor shall identify a Program Manager (PM) to act as the single point of contact responsible for managing and directing the contractor's activities with respect to this contract and for interfacing with the Government. Program management tasks include all those tasks required to direct and support program bids and proposals as well as execution. The PM shall be responsible for all planning, organizing, scheduling, staffing, directing, controlling, orderly resource management and reporting required in the execution of this contract.

2.1.1 The Contractor shall conduct a Kick-off Meeting within two weeks after contract award. A program management plan for accomplishing all objectives specified in this PWS and a configuration and data management plan will be presented. The kickoff meeting shall be held via teleconference (e.g., TEAMS, ZOOM, etc.) and subsequent in-person meetings shall be pre-coordinated with at least 5 working days advance notice.

(CDRL A001, A011)

2.1.2 Monthly Status Report. The Contractor shall provide monthly status reports describing accomplishments from the past 30 days, issues encountered during the past 30 days, and projected accomplishments during the next 30 days. The report shall be provided in a USSOCOM and Contractor agreed upon format. (CDRL A002)

2.1.3 Final Technical Report. The Contractor shall provide a Final Technical Report that captures all technical progress accomplished during the contract period of performance and shall synopsize all management and financial results. The report shall be consistent with best commercial practices and provided in Contractor format. (A007)

2.1.3 Financial Management. The Contractor shall provide contract financial reporting in a USSOCOM and Contractor agreed upon format to ensure contract costs are within negotiated parameters on a monthly basis. (CDRL A003)

2.1.4 Schedule Management. The Contractor shall maintain accurate contract schedules throughout the duration of the contract. The Contractor shall provide schedule status reporting in a USSOCOM and Contractor agreed upon format to ensure contract tasks and associated schedules remain within the negotiated task order plans on a monthly basis. Focus of reporting shall be on identification of schedule challenges or delays, impacts, and corrective actions planned or taken to preserve the program schedules. (CDRL A002)

2.1.5 Additional meeting requirements will be defined through mutual agreement, including, but not limited to, teleconference coordination meetings and Technical Interchange Meetings (TIMs).

2.2 Integration and Test

2.2.1 The Contractor shall provide integration and test support for Contractor-developed and Third-Party Missions Systems enhancements, including design and test planning/reporting documentation for Airworthiness Release (AWR) approval of Special Operations Forces-peculiar (SOF-p) modifications. (A004, A005, A006, A008)

2.2.2 The contractor shall conduct roadmap planning and coordinate with the government to support integration of enhancements, upgrades, capabilities, and emerging technologies.

2.2.3 The contractor shall support and provide test plans, test procedures, and test reports for the following core open mission system architecture tests at government directed locations:

Two (2) weeks of developmental testing Two (2) weeks of system acceptance testing Two (2) weeks of operational testing

2.2.4 The contractor shall provide support to operational units for troubleshooting and technical support.

2.2.5 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to support and provide test plans, test procedures, and test reports for the following command and control system (expeditionary mission interface) system tests at government directed locations:

Two (2) weeks of developmental testing Two (2) weeks of system acceptance testing Two (2) weeks of operational testing Eight (8) weeks of joint demonstration and testing (2 x 4-week events)

2.2.6 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to provide support to operational units for troubleshooting and technical support

2.3 A-Kit Procurement

The Contractor shall provide modification A-kits as required to support integration, test, and fielding. A-kits include aircraft modifications such as wiring, cabling, circuit breakers, electrical power, and mounting hardware required for installation of the B-kit.

2.3.1 The Contractor shall deliver five (5) core open mission system architecture A-Kits no later than 12 months after task order award.

2.3.2 The Contractor shall provide a core open mission system architecture A-Kit supply chain assessment and establish contractor tiger teams focused on improving key supplier deliveries. (A004)

2.3.3 The Contractor shall provide engineering presence during production assembly and testing to address any issues.

2.4 B-Kit Procurement

The Contractor shall provide modification B-kits (hardware and software) as required to support integration, test, and fielding.

2.4.1 Removed.

2.4.2 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the Contractor will be required to deliver nine (9) command and control expeditionary mission interface B-Kits no later than 12 months after the exercise of the option.

2.4.3 The Contractor shall provide a command and control expeditionary mission interface B-Kits supply chain assessment and establish contractor tiger teams focused on improving key supplier deliveries. (A004)

2.4.4 The Contractor shall provide engineering presence during production assembly and testing to address any issues.

2.5 Sustainment

2.5.1 The Contractor shall provide sustainment support for the developed, produced, and delivered modification kits (hardware and software).

2.5.2 The contractor shall provide a Contractor Logistics Support (CLS) Strategy consistent with best commercial practices that address sustainment of all hardware and software capabilities. (A010)

2.5.3 Software Sustainment

2.5.3.1 The contractor shall resolve mission and safety critical software defect problem correction requirements (PCRs).

2.5.3.2 The contractor shall provide one (1) Major Software Baseline Release to support the core open mission system. Major Software Baseline Release(s) shall include a list of government approved SW defect corrections; cyber patch/STIGS; renewal of Software Licenses; incorporation of enhancements and government directed capabilities. (A008)

2.5.3.3 The contractor shall maintain the core open mission system Model Based System Engineering (MBSE) artifacts utilizing industry best practices and tools (e.g., CAMEO, MagicDraw). (A008)

2.5.3.4 The contractor shall maintain the core open mission system architecture Software Safety posture and corresponding artifacts. Any Software Baseline Release (Major or Minor) impacts to the core open mission system architecture Software Safety posture will be documented and approved by the government for risk acceptance and/or approval. (A008)

2.5.3.5 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to provide (1) Major Software Baseline Release to support the command and control (C2) system (expeditionary mission interface). Major Software Baseline Release shall include a list of government required SW defect corrections; cyber patch/STIGS; renewal of Software Licenses; incorporation of system enhancements; and government directed capabilities.

(A008)

2.5.3.6 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to provide (1) Minor Software Baseline Release to support the C2 system. Minor Software Baseline Release(s) shall include minor SW defect corrections and enhancements that do not impact the system form, fit, or function; cyber patch/STIGS and application of Software License renewals. (A008)

2.5.3.7 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to maintain the C2 system Model Based System Engineering (MBSE) artifacts utilizing industry best practices and tools (e.g., CAMEO, MagicDraw). (A008)

2.5.3.8 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to maintain the C2 system Software Safety posture and corresponding artifacts. Any Software Baseline Release (Major or Minor) impacting the C2 system Software Safety posture will be documented and approved by customer determined stakeholders for risk acceptance and/or approval. (A008)

2.5.3.9 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to provide (1) Minor Software Baseline Release to support the core open mission system. Minor Software Baseline Release(s) shall include minor SW defect corrections and enhancements that do not impact the form, fit, or function; cyber patch/STIGS; and application of Software License renewals. (A008)

2.5.3.10 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to migrate from RHEL

8.6 to RHEL 9.0 to incorporate Red Hat security and stability patches into the product baseline in alignment with the upstream Red Hat patch release cycle.

2.5.4 Cyber Security

The contractor shall implement a cyber security program and deliver a cyber security plan, documentation and artifacts developed during the execution of the following tasks:

(CDRL A008)

2.5.4.1 The contractor shall incorporate Red Hat security and stability patches into the product baseline in alignment with both the Red Hat patch release cycle as well as the fielding schedule established by the government to match the Software Baseline Release schedule. (A008)

2.5.4.2 The contractor shall provide raw compliance and vulnerability scan reports of the core open mission system architecture system and support customer cybersecurity representatives in development of IATT/ATO package artifacts. (A008)

2.5.4.3 The contractor shall provide raw compliance and vulnerability scan reports of the core open mission system architecture system Software Baseline Release updates as well as support customer cybersecurity representatives in development of IATT/ATO package artifacts. (A008)

2.5.4.4 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to incorporate Red Hat security and stability patches into the product baseline in alignment with both the Red Hat patch release cycle as well as the fielding schedule established by the customer to match the Software Baseline Release schedule. (A008)

2.5.4.5 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to provide raw compliance and vulnerability scan reports of C2 system as well as support customer cybersecurity representatives in development of IATT/ATO package artifacts. (A008)

2.5.4.6 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to provide raw compliance and vulnerability scan reports of C2 system in alignment Software Baseline Release updates as well as support customer cybersecurity representatives in development of IATT/ATO package artifacts. (A008)

2.5.4.7 The Contractor shall develop and implement system security plan(s) and any associated plans of action developed to satisfy the security requirements of DFARS 252.204-7012, and in accordance with NIST Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations”.

2.5.4.8 The Contractor shall develop and maintain current cyber security assessments (see 252.204-7020) for each covered contractor and subcontractor information system.

2.5.4.9 The Contractor shall develop and implement system security plan(s) (or extracts thereof) and any associated plans of action for each tier one level subcontractor(s), vendor(s), and/or supplier(s).

2.5.4.10 The Contractor shall create and maintain covered defense information (CDI) lists and associated CDI Protection Plan(s) as prescribed in DoDM 5200.01 Vol 4, Controlled Unclassified Information, and DoDI 5230.24, Distribution Statements on Technical Documents.

2.5.5 Training

2.5.5.1 The Contractor shall assess, develop, support accreditation, and deliver training materials detailing the operational use and maintenance of the core open mission system architecture capability in a government-approved format within (30) days of a configuration change being qualified. (A008)

2.5.5.2 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to assess, develop, support accreditation, and deliver training materials detailing the operational use and maintenance of the C2 system architecture capability in a government-approved format within (30) days of a configuration change being qualified. (A008)

2.5.6 Technical Manuals

2.5.6.1 The contractor shall deliver Operator and Technical Manuals and updates as configuration changes are made for the core open mission system architecture capability in contractor defined format. A configuration change shall be defined as a change that effects how the operator uses the system. Government will review and approve manuals and updates prior to release to the operational unit(s). (A008)

2.5.6.2 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor shall deliver Operator and Technical Manuals and updates as configuration changes are made for the C2 capability in contractor defined format. A configuration change shall be defined as a change that effects how the operator uses the system. Government will review and approve manual updates prior to release to the operational unit(s). (A008)

2.5.7 Safety and Airworthiness

2.5.7.1 The contractor shall deliver Airworthiness release information following a configuration change to the core open mission system architecture capability in Government-approved contractor format. A configuration shall be defined as a change to a flight critical component and/or software of the system. (A006, A008)

2.5.7.2 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to deliver

Airworthiness release information following a configuration change to the C2 capability in Government-approved contractor format. A configuration shall be defined as a change to a flight critical component and/or software of the system. (A006, A008)

2.5.8 Modification Work Orders

2.5.8.1 The contractor shall provide Modification Work Order (MWO) information packages to support hardware and/or software modification of the core open mission system architecture capability systems and subsystems. (A008)

2.5.8.2 OPTION ITEM: This option for increased quantity as a separately priced line item, if utilized by the Government, will be exercised in accordance with clause 52.217-

7. If exercised by the Government, the contractor will be required to provide Modification Work Order (MWO) information packages to support hardware and/or software modification of the C2 system architecture capability systems and subsystems. (A008)

2.5.9 Help Desk Support

The contractor shall provide email and/or voice help desk support. The contractor shall document and archive and provide the government all support requests monthly in contractor approved format. (A002)

3.0 DOCUMENTATION

The following Contract Data Requirements List (CDRL) are documentation requirements for this task order:

CDRL A001: Contract Kickoff/Review CDRL A002: Monthly Progress Report CDRL A003: Monthly Financial Status Report CDRL A004: Design Review Documentation CDRL A005: Developmental Test Plan for Performance Validation CDRL A006: Developmental Test Report CDRL A007: Final Technical Report CDRL A008: Sustainment Documentation CDRL A010: CLS Support Strategy CDRL A011: Configuration and Data Management Plan

4.0 TRAVEL

Travel will be necessary to satisfy the requirements of this contract. All travel requirements (including plans, agenda, itinerary, or dates) shall be pre-approved by the government and is on a strictly cost reimbursable basis. All planned trips will be considered approved at the time of task order award. Any unplanned travel determined to be required and still within travel cost ceiling of an individual task order must be approved in writing (email) by the Contracting Officer. Cost for travel shall be billed in accordance with FAR 31.205-46 Travel Costs. The contractor shall identify and propose travel needed to complete the PWS tasks throughout the 12-month PoP (Attachment 6, CLIN 0008AA). The contractor shall separately identify and propose travel needed for Option Items listed in this task order PWS CLINs (Attachment 6, CLIN 0008AB). CLIN 0008AB will be exercised if the Government exercises any of the separately priced option line items listed in this PWS. Planned travel may include Fort Campbell, KY and Huntsville, AL. Any required travel that will result in exceeding the travel cost ceiling must be approved by the Contracting Officer by either written (email) Authorization to Proceed or task order modification prior to beginning travel.

5.0 GOVERNMENT ACCEPTANCE

Final inspection and acceptance under this contract shall be made at the destination DoD Activity Address Code (located on Ft. Campbell, KY) specified in Section F of the task order.

6.0 RESERVED

7.0 SECURITY

7.1 Security will be in accordance with the attached DD254. Contractor team individual(s) supporting this task will be cleared at the TOP SECRET level at the start of the task. Contractors will require access to Communications Security (COMSEC) and Sensitive Compartmented Information (SCI) in performance of this effort. Contractor will not require access to government computer systems. Contractor will be authorized to courier classified information up to SECRET in performance of official duties upon approval of and designation by the COR.

7.2 The Contractor shall ensure requirements for safeguarding classified information and classified materials, for obtaining and verifying personal security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, and for the security of automated and non-automated management systems and data are fulfilled. The Contractor’s management system shall prevent the unauthorized disclosure of classified and sensitive unclassified information. The Government Contracting Officer and COR shall be notified immediately of any security incident or indication of a potential unauthorized disclosure or compromise of classified or sensitive information.

7.3 The Contractor shall provide security management support. Typical efforts include but are not limited to performing classified document control functions, classified materials inventories, program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases.

8.0 GOVERNMENT FURNISHED EQUIPMENT/INFORMATION

The Government does not anticipate providing any Government Furnished Equipment/Information (GFE/GFI) under this task order.