Attachment 1 - Undersea Systems Test and Evaluation Support SOW 20210916 Ver 6 (Final).pdf

USSOCOM SOF AT&L – Maritime Undersea Systems Test and Evaluation Support

Statement of Work 16 September 2021

1. Scope

1.1 Background. The U.S. Special Operations Command (USSOCOM) Undersea Systems Program Management Office (USPMO) is developing dry submersibles with diver lock- in/lock-out capability for use by Naval Special Warfare (NSW) Forces. The paragraphs below summarize the USPMO areas of effort supporting development of this technology.

1.1.1 Technology Baseline Vehicle (TBV). USPMO developed and delivered the TBV to the fleet in 2017. USPMO is using this platform to evaluate new technologies and support program Engineering Change Proposals (ECP).

1.1.2 Dry Combat Submersible (DCS). USPMO is fielding a one atmosphere, diver lock-in/lock-out submersible system that is launched & recovered from a surface platform. This undersea mobility capability is composed of commercially classed submersibles for use by Special Operations Forces.

1.1.3 Dry Combat Submersible Next. USPMO is currently performing acquisition planning and developing associated documentation. DCS Next will provide increase capability to meet NSW operational requirements.

1.1.4. Future Technology Development. USPMO is developing additional supporting technologies in and out of the Undersea Mobility Portfolio to improve, modify, or integrate emerging technologies to the mobility systems.

1.2 Project Overview. This SOW defines the required services in Section 2. The contractor must have the personnel expertise and capacity to provide support immediately upon contract award for tasks in progress and be able to start new work as required by

USPMO.

Contractor personnel must have direct experience with small manned dry submersible operations, engineering, and test & evaluation processes/procedures to support both Developmental and Operational Testing. Direct experience with NSW undersea Tactics, Techniques and Procedures as they relate to small manned dry submersible operations is highly desirable.

2. Requirements

DCS Program Test Support- NSW and Test and Evaluation (T&E) SME support for the

DCS Program Initial Operational Test and Evaluation (IOT&E), Verification of Correction of Deficiencies (VCD), and Follow-on Test and Evaluation (FOT&E).

2.1.1 Assist the Commander Operational Test and Evaluation Force (COTF) in IOT&E execution with tasks including, but not limited to, test schedule planning, test execution management, data collection, data extraction, data processing, and data transfer/storage.

2.1.2 Assist COTF with IOT&E data analysis and reporting.

2.1.3 Assist COTF with VCD event execution including data analysis and reporting.

2.1.4 Assist COTF with FOT&E test planning including development, stakeholder review, and approval of the FOT&E Integrated Evaluation Framework (IEF), test plans, data collection plans, and test procedures.

2.1.5 Assist COTF in FOT&E execution with tasks including, but not limited to, test schedule planning, test execution management, data collection, data extraction, data processing, and data transfer/storage.

2.1.6 Assist COTF with FOT&E data analysis and reporting.

2.1.7 Assist USPMO with SME and engineering analysis in support of troubleshooting IOT&E and FOT&E deficiencies.

2.2 DCS Next-Development of Acquisition Program and Test Documentation

2.2.1 Provide contractor SME support to the Government Program Office in the planning, development & execution of required test and evaluation acquisition & programmatic documentation to any of the applicable DODI 5000.02 adaptive acquisition framework pathways. Review and provide SME input to acquisition documentation including, but not limited to, the Concept of Operations (CONOPS), Capability Development Document (CDD), Design Reference Mission Profile (DRMP), and Technology Readiness Assessment (TRA).

2.2.2 Assist USPMO by providing SME input during Preliminary Design Review (PDR), Critical Design Review (CDR), System Verification Review (SVR), Functional Configuration Audit (FCA), and Production Readiness Review (PRR).

2.2.3 Assist the USPMO with development, stakeholder review, and approval of test planning documentation including the Test and Evaluation Master Plan (TEMP), DT Requirements Traceability Verification Matrix (RTVM), and Developmental Evaluation Framework (DEF).

2.2.4 Assist COTF with development, stakeholder review, and approval of the Integrated Evaluation Framework (IEF), and the Test Measures (TMs).

2.2.5 Assist the USPMO with development, stakeholder review, and approval of DT execution documentation including, but not limited to, test plans, data collection plans, and test procedures. Assist COTF with development, stakeholder review, and approval of IOT&E execution documentation including, but not limited to, test plans, data collection plans, and test procedures.

2.3 Related SOF AT&L Maritime Portfolio Test Support- Perform as NSW Test and Evaluation SME, engineering, and test support for current and future dry submersible systems and related subsystems.

2.3.1 Provide operational SME and engineering input during development of plans, designs, and products intended to enhance current and future capability of NSW dry submersibles and ancillary equipment.

2.3.2 Assist USPMO or third-party organizations with review of vendor-developed verification test plans and procedures to determine quality, applicability, and utility of collected data.

2.3.3 If directed by the USPMO, assist in execution of vendor-developed test procedures with tasks including test management, data collection, and data transfer/storage.

2.3.4 Assist USPMO with data analysis and reporting as requested. In addition, review and provide SME input to reports generated by third-party organizations.

2.4 Technical Engineering Support. Support technical engineering working groups/teams’ efforts as the Test and Evaluation SMEs.

2.4.1 Participate in technical working groups/teams and meetings as directed by USPMO (Examples includes but not limited to evaluations of Engineering Change Proposals (ECPs), Configuration Management reviews, Emergent test and evaluation working groups, and Integrated Product Teams)

2.4.2 Assist in site surveys of testing locations and provide input on feasibility for event execution.

2.5 Program Management.

2.5.1 The contractor shall possess qualified personnel expertise to meet the requirements outlined in the SOW. This includes adequate level of management structure, personnel training & certifications, quality assurance processes, financial management and security requirements as delineated in the DD 254.

3. Place of Performance. Contractor personnel duty location will be as directed by the Government. For planning purposes only, the projected place of performance are Tampa, FL and Little Creek, VA. Contractor personnel must possess a U.S. SECRET or higher facility security clearance and personnel working on the contract should have access to SIPRNet.

Normal duty hours are Monday – Friday, 0800 – 1630 hrs. All Federal holidays are observed in this contract. Should operational needs arise, periodic work on holidays and/or weekends will be required.

The Contractor shall be required, as directed and approved by the Contracts Officer Representative (COR), to travel by himself/herself or with other Government/Contractor employees to government sites for moderate durations of time, typically no more than two weeks at one time. Travel shall adhere to the Department of Defense Joint Travel Regulations.

4. Deliverables. The contractor shall prepare and deliver all data in accordance with (IAW) the instructions specified in the DD Form 1423-1 (Contract Data Requirements List (CDRL)) in Section J of the solicitation/contract.

4.1 Program Status and Management Report (PSMR) (CDRL 1)

Frequency: Monthly (10th of each month) Date of first submission: First full month after issuance of TO Final submission: Month after completion of TO Number of copies: 1 electronic .pdf copy submitted to the COR via email

4.2 PSMR Monthly Finance Report (MFR) (CDRL 2)

Frequency: Monthly (10th of each month) Date of first submission: First full month after issuance of TO Final submission: Month after completion of TO Number of copies: 1 electronic .pdf copy submitted to the COR via email

4.3 Test Plans and Procedures (CDRL 3)

Frequency: As Required.

Submit in format as specified by COR. Includes documentation as described in SOW paragraphs 2.1, 2.2, 2.3, and 2.4. Deadlines for initial drafts and final submissions to be determined by COR.

4.4 Technical Analysis and Test Reports or Reviews (CDRL 4)

Frequency: As Required.

Submit in format as specified by COR. Includes documentation as described in SOW paragraphs 2.1, 2.2, 2.3, and 2.4. Deadlines for initial drafts and final submissions to be determined by COR.

4.5 Trip Reports (CDRL 5)

Frequency: As Required. Estimate one each for Builder Trials, GAT, and various DCS vendor testing events.

Date of first submission: 5 Days after completion of Travel Final submission: As required based on Government feedback from draft Number of copies: 1 electronic .pdf copy submitted to the COR via email