Attachment_I_Satement_of_Work_MDA.docx

DEPARTMENT OF HOMELAND SECURITY (DHS)

U.S. COAST GUARD

RESEARCH AND DEVELOPMENT CENTER

STATEMENT OF WORK (SOW)

FOR

LOW COST MARITIME DOMAIN AWARENESS (MDA) PILOT STUDY

GENERAL

Background Congress has directed The United States Coast Guard (CG) to examine the feasibility, costs, and benefits of improving Maritime Domain Awareness in the remote Pacific Ocean using a low cost unmanned surface system. The CG faces challenges with respect to conducting maritime surveillance in the Pacific Ocean necessary to support its statutory missions related to marine safety, security, and protection. One of the three tenets of the Coast Guard’s Western Hemisphere Strategy is the defensive posture of this strategy to sustain effective offshore awareness capability. This is the comprehensive ability to detect threats and safeguard our homeland, prevent illegal fishing, and stop intrusion into protected marine sanctuaries. One of the Fourteenth Coast Guard District’s (D14) primary Maritime Domain Awareness (MDA) concerns is identifying where Illegal, Unreported, and/or Unregulated (IUU) fishing activity is most prevalent. Their current focus is on transshipments of fish at sea.

Department of Homeland Security (DHS) entities, including the Coast Guard (CG) have limited surface and aerial assets to cover 12.2 million square miles of maritime territory in the Pacific Ocean, so with such limited resources the CG needs to use intelligence and technology to ensure they are using the assets the most efficient way possible. The use of advanced sensors and MDA maritime systems could help provide additional coverage in the maritime environment to leverage existing assets for greater effectiveness.

In order to increase MDA of the vast area of operations, the Coast Guard relies on partnerships with the Pacific Island Nations for information sharing and enforcement. To share information with these Island Nations, all data must be kept at the unclassified level.

The USCG is interested in learning about the efficacy of using low-cost commercially available Unmanned Surface Vehicles (USVs) with an appropriate sensor suite to provide alerts of IUU fishing activity in the Western Pacific as an enhancement to maritime domain awareness. The research will look at a USV system solution deployable by the CG fleet, including the Coast Guard Auxiliary, with a key factor of being low cost and having a minimal logistics footprint.

The CG RDC plans to conduct a thirty day long demonstration of onsite autonomous capability that will augment the existing complement of manned Coast Guard assets and enhance the effectiveness of the Pacific Island partnerships. During the month long demonstration, the RDC is seeking to evaluate a commercially available USV system(s). Current plans are to schedule the 30 days of in water evaluation to begin on July 15, 2020 and end August 13, 2020.

Global Fishing Watch (GFW) uses cutting-edge technology to visualize, track and share data about global fishing activity in near real-time. The RDC is collaborating with GFW to utilize their data analysis and advanced mapping capabilities to assist in developing a suspicious ship activity-monitoring program with machine learning and artificial intelligence. For the demonstration, to be successful, data such as ship detection must be shared with GFW.

Scope The scope of this Statement of Work (SOW) includes preparation, inspection, transport, ground and open ocean demonstration, operation, and removal of a contractor owned and operated USV system in an approximately 20 square mile area 30 miles south of Oahu, Hawaii. The scope also includes planning, briefing reporting, progress meetings and a deliverables archive. The purpose of the demonstration is to generate data that examines the operational utility of a USV system for improving CG MDA in remote Pacific regions.

Applicable Documents Compliance Documents The following documents provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract:

· DI-MGMT-80227

· Department of Homeland Security Suitability and Fitness Program, Instruction Handbook 121-01-007, Revision 01 [Internet Release Authorized]

· Coast Guard Operations Security (OPSEC) Program Manual, COMDTINST M5510.24 (Series)[Internet Release Authorized]

1.1.1 Reference Documents

The following documents or information may be helpful to the contractor in performing the work described in this document:

· RDC Report Format Guide

· Fourteenth Coast Guard District Honolulu, Hawaii, https://www.pacificarea.uscg.mil/Our-Organization/District-14/

· Global Fishing Watch, https://globalfishingwatch.org/

SPECIFIC REQUIREMENTS/TASKS

TASK ONE: Kick-off Meeting The contractor shall provide agenda items for the meeting to the Contracting Officer Representative (COR)/Project Manager (PM) and schedule the Kick-off Meeting within 10 days of award. The meeting shall be held at the contractor’s facility.

Meeting Minutes The contractor shall deliver Meeting Minutes (Deliverable 1).

USV System Demonstration Plan The contractor shall review and complete the contractor sections and provide comments/changes on the Government prepared USV Draft Demonstration Plan [Provided as Government Furnished Resource as listed in SOW Paragraph 4]. The contractor shall elaborate in the plan on how the contractor will meet the intent of the Demonstration goals. In the plan the contractor will propose design reference missions to highlight the capabilities of their system. The contractor shall deliver a Draft USV System Demonstration Plan (Deliverable 2) at the Kick-off Meeting for Government review and comment. The contractor shall prepare the Final USV System Demonstration Plan (Deliverable 3) that incorporates comments from the kickoff meeting, that details the demonstration, the proposed USV system, the data management proposal, and measures of success. The plan shall finalize the timeline for demonstration preparation, Capability Characterization, Demonstration Readiness Test and the 30-day demonstration and address all sections noted in the draft demonstration plan. After acceptance of this deliverable, the Final USV System Demonstration Plan will become a living document managed by the contractor. Changes to the plan can be proposed by the contractor or the Government and once agreed to by both parties; the contractor shall update the plan to reflect the change.

The contractor shall provide two demonstration plan briefings. One briefing will be to the USCG and GFW in San Francisco CA. The second briefing will be in Oahu, HI with USCG personnel planning to participate in the demonstration. The goal of these briefings shall be to convey how the USV system will alert, what it will alert to and identify any contact verification mechanisms/processes.

TASK TWO: Demonstration Preparation At its own facility, the contractor shall provide and prepare a USV system, a control/monitoring station, support package, and ten report receiving devices that collectively are suitable for executing the applicable portions of the Final USV System Demonstration Plan (Deliverable 3). The USV system components (vehicle, control/monitoring station, and mission package) shall each be technologically mature and have a TRL 8 (threshold) or TRL 9 (goal) as published in the Defense Acquisition Guidebook (2010) – Department of Defense (DoD) Technology Readiness Level (TRL) descriptions. The USV(s) shall be capable of achieving the threshold performance requirements outlined in Table 1 – Minimum USV Performance Specifications in order to fulfill the required data generation service. The report receiving devices shall allow the USCG locations to receive reports from the USV during the demonstration and shall not be integrated into any CG network. The contractor shall supply all required communications equipment, channels, and bandwidth required to transmit the data from the USV and disseminate to the various contractor and Government locations. The contractor shall prepare a Functional Inspection Report (Deliverable 4) which includes the results of a functional system and equipment inspection that documents system readiness, discrepancies and mitigating actions.

Table 1 – Minimum USV System Performance Specifications

Performance Requirement

The USV(s) participating in the demonstration shall have the ability to continuously monitor and record the fuel burn rate (if applicable), energy use/production, Global Positioning System (GPS) tracks, time, operational status, etc. Specific data include:

· Fuel burn rate monitor and recorder (if applicable).

· Energy use/production.

· Operational status.

· Air temperature.

· Sea state.

· GPS tracking.

· Time.

· Ship detection.

1The condition or quality of being self-governing. An unmanned system’s own ability of sensing, perceiving, analyzing, communicating, planning, decision-making, and acting, to achieve its goals as assigned by its human operator(s) through designed human-robot interface. Autonomy is characterized into levels by factors including mission complexity, environmental difficulty, and level of human-robot interaction to accomplish the missions.

2Operations of an unmanned system wherein the unmanned system receives its mission from the human and accomplishes that mission with or without further human-robot interaction. The level of human-robot interaction, along with other factors such as mission complexity, and environmental difficulty, determine the level of autonomy for the unmanned system. Finer-grained autonomy level designations may also be applied to the tasks, lower in scope than the planned mission.

3Levels of Autonomy (based on - https://www.researchgate.net/figure/Levels-of-Autonomy-adopted-by-the-VSP-HALE-Sector_tbl1_263925826 [accessed 12 Mar, 2019]) 1 - Remote Control – Remotely piloted surface vessel with a human in the loop, making all the decision. Operator is in constant control (100% hands-on-time.)

Simple Automation – Remotely piloted with some automation techniques to reduce operator workload. Human monitoring to start/stop tasks. (80% hands-on-time.)

2 - Remotely Operated – Human operator allows USV on-board systems to do the piloting. As part of the outer control loop, the human makes decisions as to where to go, when, what to do once there. Remotely supervised, with health monitoring and limited diagnostics. Operator allows USV to execute preprogrammed tasks, only taking over if the USV is unable or fails to properly execute them. (50% hands-on-time.)

3 - Highly Automated or Semi-Autonomous – USV automatically performs complex tasks. System understands its environment (situational awareness) and makes routine decisions and mission refinements to dynamically adjust to environment and mission variables. Limited human supervision, managed by exception. Adaptive to failures and evolving environmental conditions. (20% hands-on-time.)

4 - Fully Autonomous- USV receives high-level mission objective (e.g., location, time), translates them into tasks that are executed without further human intervention. USV has the ability and authority to make all decisions. Extensive situational awareness (internal and external), prognostics, and on-board re-planning capability. Single vehicle operations. (Less than 5% hands-on-time.)

5 - Collaborative Operations - Brings in aspects of multiple USVs working autonomously together as a collective intelligent system. Group coordination. Individual vehicles/systems in a collaborative group will have at least semi-autonomous LOA (3) to keep the operator workload of the collaborative operation at a manageable level. (total hands-on-time for the sum of USVs would not exceed a single operator hands-on-time of 100%.)

The contractor shall prepare, provide and man a Demonstration Control/Monitoring Center (DCMC) in Oahu, HI for the duration of the demonstration. The DCMC shall:

· contain a Demonstration Control/Monitoring Station;

· have adequate space for 13 USCG observers during initial/kick-off and final briefings. During the remaining days of operations, the DCMS shall have adequate space for 10 USCG observers; and

· have adequate power for communications, video screens, and presentation space.

For 20 days of the 30 day demonstration, the contractor shall provide a target/observation boat that can be safely operated in the weather and sea conditions in the demonstration area. This boat shall be used as a target including varying degrees of role-playing, detection range verification, and vessel behavior characterization. The boat shall also be used as a means for verifying USV detected traffic and be capable of conveying two Government personnel in addition to the contractor personnel requirements.

The contractor shall provide all required information for the USCG to attain a frequency authorization 90 days prior to the demonstration.

The contractor shall provide a Demonstration Director to manage the operations and maintenance of the USV system, coordinate demonstration activities with the USCG and respond to any media inquiries or events with the USCG’s authorization.

The contractor shall prepare and provide photographic and video data and evidence during the execution of the SOW tasking with the goal of visually illustrating critical preparation, operational, maintenance and communications issues in the final report and during the various briefings.

TASK THREE: Demonstration Readiness Review (DRR) The contractor shall host and participate in a DRR with the Government, guided by the Final USV System Demonstration Plan (Deliverable 3). The review will take place a minimum of (2) weeks prior to the scheduled demonstration start date and may include topics such as test objectives, methods, and procedures, safety, environmental impacts, risk assessments, data collection plans, test schedules, lost-link procedures, etc. The contractor shall provide accurate information concerning the system preparations, test resources, risk levels, logistics, contingency plans, etc. for which it is responsible. A detailed example of topics for the DRR is in the USV System Demonstration Plan paragraph 5.1.2 TASK FOUR: USV System Transport The contractor shall arrange for and transport the USV, control/monitoring station, and required support equipment to Oahu at the contractor’s selected and funded DCMC in a condition representative of expeditionary deployment. Upon arrival at the DCMC, the contractor shall demonstrate the associated field assembly, set-up, calibration, etc. necessary to return the system to an operational status.

TASK FIVE: USV Characterization The tasking contained in TASK FIVE shall occur at a contractor facility in Oahu, HI and events may be attended by Government personnel. The dates for these briefings/walkthrough shall be proposed by the contractor and agreed to by the Government at the kick-off meeting.

1.1.2 System Design, Construction, and Operation Overview

The contractor shall provide a verbal briefing/walkthrough of the USV(s) furnished for demonstration. The briefing shall cover system familiarization topics such as design concept, construction, component functions, operation, maintenance, and any other topics applicable to the ownership, operation, and deployment of the system. The contractor shall include at least two operational demonstrations of their USV System. The first is independent patrol by the USV with remote alerting and the second as an enhancement to be launched from and retrieved by the contractor’s localized asset.

1.1.3 Mission Configuration

The contractor shall document all USV System mission configurations intended to be utilized during the demonstration and provide a Mission Configuration Data Sheet (Deliverable 5). The data sheet shall include the necessary specifications to document the configuration of the system such as weight and balance, fuel load, payloads installed, and data analysis capability used/available.

1.1.4 Support Equipment Demonstration

The contractor shall provide a verbal briefing/walkthrough of the support equipment required for operation of the USV both from shore and from a surface asset. The briefing shall include all equipment unique to the operation of the subject system as well as the integration of data equipment.

1.1.5 Maintenance Evolutions

The contractor shall document all maintenance activities necessary to sustain the system during the demonstration and for the life of the system. Examples of these activities may include, inspections, servicing, routine repairs, and other maintenance activities associated with the operational deployment of the system. The contractor shall provide a verbal briefing/walkthrough of maintenance activities which are too extensive to practicably demonstrate, but may be required during actual USV operations. The intent of the documentation is not to provide step-by-step maintenance procedures but to document the maintenance requirement sufficiently for a life-cycle cost estimate.

1.1.6 Pre-deployment/Operation/Post-Deployment Inspections

The contractor shall demonstrate the procedures to execute pre-deployment, operation, and post deployment activities utilizing the entirety of the USV(s), Monitoring/Control Station, and associated equipment. The contractor shall produce and provide an Operational Check List (Deliverable 6) for these activities.

TASK SIX: USV(s) Demonstration The contractor shall conduct the demonstration in Oahu HI as documented in the Final USV System Demonstration Plan (Deliverable 3) (Paragraph 5.3). For the duration of the thirty day at sea demonstration, the contractor shall operate/monitor the USV system. The system shall sense, detect, and alert to maritime traffic in the demonstration area. The system shall transmit the detection, position, date and time to contractor provided devices at GFW, CG Sector 14 and 17 Command Centers, CG PACAREA Intel Center, CG RDC, and a CG asset. Available data beyond position, date, and time may also be transmitted. The contractor shall demonstrate the maximum level of autonomy of the USV(s) system as described in footnote 3 to Table 1, Minimum USV System Performance Specifications.

The USCG and GFW will verify the Alert data using AIS, VMS, other Electronic Intelligence, and satellite imagery as is available. The USCG will provide a verified or unverified assessment to the contractor. The contractor shall maintain a record of alerts and their verification status for analysis and inclusion in the final report.

1.1.7 Launch and Recovery

The contractor shall demonstrate the capability of the USV(s) to safely launch and recover. All mechanisms by which the USV(s) is/are designed to complete these operations shall be demonstrated, i.e. launch from a ship, launch from shore, autonomous, etc.

1.1.8 Sensor Calibration

The contractor shall demonstrate the sensor calibration of the sensors and USV.

1.1.9 Design Reference Missions

The contractor shall demonstrate the capability of the USV(s) to execute multiple design reference missions guided by the Final USV System Demonstration Plan (Deliverable 3). The contractor will be given example missions to demonstrate USV(s) performance of patrol search patterns, vessel alert, station keeping, etc. All mechanisms by which the USV(s) is designed to complete these operations shall be demonstrated. Examples of potential missions are in the Demonstration Plan (Paragraph 5.3.5).

1.1.10 Maritime Target Activity and Interdiction Situational Awareness The contractor shall demonstrate the capability of the USV(s) and sensor/payload to detect vessel and discern their activity if capable. The contractor shall include at least two operational vignettes during the demonstration of their USV System. The first is independent patrol by the USV with remote alerting. The contractor shall also demonstrate the capability of the USV(s) and sensor/payload to be launched, then operate beyond line of sight while providing situational awareness to law enforcement surface assets conducting interdictions. This activity will require the USV(s) to alert to local assets. The contractor and USV(s) shall perform the USV(s)/mission package performance vignettes outlined in the Final USV System Demonstration Plan (Deliverable 3).

1.1.11 30 Day Endurance The contractor shall demonstrate the capability of the USV(s) to achieve the 30 day autonomous endurance while in a maritime mission configuration.

1.1.12 Daily Demonstration Planning and Reporting

On every weekday during the 30 day demonstration, the Contractor shall host a meeting at the contractor’s DCMC, (teleconference and in person) with the Government and provide a Daily Data Sheet. The Daily Data Sheet shall contain a written mission plan to include a safety brief for the current day or current day and weekend if a Friday and provide a written consolidated activity report for the previous day or weekend if a Monday.

The contractor shall also be prepared for up to three presentations for the media. The presentation shall include pictures of the USV and the system, video as applicable, and discussion on the operation and features of the USV System. The contractor shall produce a poster for display in the operations center at all times. Media presentations related to the demonstration shall be joint presentations with the USCG.

1.1.13 Close out Summary Briefing

At the conclusion of the demonstration, the contractor shall host and provide a summary briefing that is focused on the attainment of the demonstration outcomes, preliminary demonstration findings, data quality and completeness, and lessons learned.

TASK SEVEN: USV(s) System Removal At the conclusion of the technology demonstration, the contractor shall remove the USV(s), control/monitoring station, and all support equipment from the control center and demonstration area.

TASK EIGHT: Post-Demonstration Review The contractor shall provide accurate information concerning the performance of the system, demonstration resources utilized, and any missing data. To support Government estimates of total ownership burden, the contractor shall document the resources associated with the transportation, logistical foot print, operation and maintenance of the USV system during the demonstration to include fuel, maintenance, parts, consumables, USV(s) and sensor operators and maintainer hours, etc. The contractor shall use this information to create a ROM life-cycle cost. The contractor shall prepare and submit a USV System Performance Summary (Deliverable 7), which documents the system’s performance, vessel detection range, maintenance completed, resources expended, equipment failures, etc. during the demonstration. This deliverable shall also include the ROM life-cycle cost estimate. After final delivery of the USV System Performance Summary (Deliverable 7), the contractor shall review and comment on government changes to the USV System Performance Summary resulting from the USCG Headquarters approval process.

TASK NINE: Progress Reporting and Deliverables Archive

1.1.14 Progress Meetings

The contractor shall meet with the COR/PM on a biweekly basis to discuss progress, exchange information and resolve emergent technical problems and issues. These meetings shall take place via teleconference unless the PM or COR determines that a meeting at the contractor’s facility is necessary.

The contractor shall also be responsible for keeping the COR/PM informed about contractor progress throughout the performance period of this contract, and ensure contractor activities are aligned with USCG objectives.

1.1.15 Monthly Progress Report

The contractor shall provide Monthly Progress Reports (Deliverable 8) via electronic mail. These reports shall include a summary of all contractor work performed, including an assessment of technical progress, schedule status, and any contractor concerns or recommendations for the previous reporting period.

1.1.16 Daily Demonstration Meeting and Data Review

A record of all the Daily Data Sheets generated in Task 2.6.5 shall be gathered into a single Daily Data Sheet History (Deliverable 9).

1.1.17 Deliverables Archive

The contractor shall provide a Deliverables Archive (Deliverable 10) on CDROM or DVD format of all deliverables generated during the course of this tasking. The contractor shall organize the archive as follows:

· Each deliverable shall have its own folder at the highest level of the archive

· The deliverable will be placed in its own deliverable folder and all supporting documentation to include the deliverable forwarding letter or mail shall be in a subfolder to the deliverable folder.

· All folders and files shall have names that clearly identify the folder or file contents.

OTHER APPLICABLE CONDITIONS

Security All information and deliverables under this contract are Unclassified and will not require access to Sensitive but Unclassified (SBU) information.

Access to Government Facilities All work shall be performed at the contractor facility and the demonstration area. Should non-recurring access to government facilities be required, arrangements will be made through the Project Manager/COR.

Access to Government Information Systems The contractor shall not require access to U.S. Coast Guard IT Systems.

Additional contractor travel may be required to support this requirement.

GOVERNMENT FURNISHED RESOURCES

The Government and its partner GFW will verify alerts generated by the USV system.

The Government will provide copies of the references cited in SOW 1.3, if requested, at the Kick-off meeting.

The Government will provide the following information, data and documents to the contractor for work required under this task order:

· Government prepared USV Draft Demonstration Plan

The contractor shall use Government Furnished Information (GFI), data and documents only for the performance of work under this contract, and shall be responsible for returning all GFI, data and documents to the Government at the end of the performance period. The contractor shall not release GFI, data and documents to outside parties without the prior and explicit consent of the Contracting Officer.

CONTRACTOR FURNISHED PROPERTY

The contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract, except for the Government Furnished Resources specified in SOW 4.

DELIVERABLES

All deliverables are in “Contractor Format” unless otherwise indicated. The contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with Coast Guard workstations (Windows Operating Systems and Microsoft Office Applications). The contractor shall not release deliverables to outside parties without the prior and explicit consent of the Contracting Officer.

COR

PM2

Contract Specialist –Transmittal Only

COR

PM2

Contract Specialist –Transmittal Only

PM2

Contract Specialist –Transmittal Only

PM2

Contract Specialist –Transmittal Only

Demonstrated Mission Configuration: 2 Weeks after Demonstration

COR

PM2

Contract Specialist –Transmittal Only

PM2

Contract Specialist –Transmittal Only

Draft: 30 days after completion of Demonstration Government Review: Within 30 days of Draft submission Final: Within 15 days of Government review

COR

PM2

Contract Specialist –Transmittal Only

PM2

Contract Specialist

PM2

Contract Specialist

PM2

Contract Specialist

1RDC Report Format

2TBD