Attachment_II_DRAFT_USV_System_Tech_Demo_Plan.doc

Low Cost USV System Technology Demonstration Plan

N O T I C E

This document is disseminated under the sponsorship of the Department of Homeland Security in the interest of information exchange.

For use outside the United States Government, the Government assumes no liability for its contents or use thereof.

The United States Government does not endorse products or manufacturers. Trade or manufacturers’ names appear herein solely because they are considered essential to the objective of this plan.

Surface Branch United States Coast Guard

Research & Development Center

1 Chelsea Street

New London, CT 06320

(This page intentionally left blank.)

EXECUTIVE SUMMARY

In 2018 Congress tasked the United States Coast Guard (USCG) 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 USCG 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.

The demonstration will be comprised of Three major phases:

· Phase I – System Characterization

· Phase II – Operational Performance

· Phase III – Unmanned Surface Vehicle (USV) System Removal and Out-brief The goals of the demonstration include:

· Determine the operational utility of a USV System for USCG maritime missions in remote areas.

· Quantify the impact of utilizing the USV System.

· Demonstrate USV System operational capabilities in the maritime environment.

· Inform the development of Concepts of Operation (CONOPS) for a USV System.

· Demonstrate the integration of the USV System into the maritime law enforcement force structure.

(This page intentionally left blank.)

TABLE OF CONTENTS

ivEXECUTIVE SUMMARY viiiLIST OF FIGURES viiiLIST OF TABLES ixLIST OF ACRONYMS AND ABBREVIATIONS

INTRODUCTION

11.1 Demonstration Phases

11.2 Assumptions and Limitations

DEMONSTRATION FACILITY AND EQUIPMENT

22.1 Demonstration Facility

22.1.1 Location – South of Oahu, Hawaii

22.1.2 Demonstration Facility Requirements:

22.1.3 Logistics

32.1.4 Target Vessels

32.1.5 Instrumentation Plan

32.2 Communications Plan

32.3 Support Equipment

32.4 Payload

32.5 Daily Briefs

DEMONSTRATION DESIGN

33.1 Scope

33.2 Schedule

DEMONSTRATION METHODS AND PROCEDURES

44.1 Roles and Responsibilities

54.2 Operational Procedures

54.3 Safety Briefings

54.4 Data Collection

54.4.1 Data Sheets

54.4.2 Media Events

DEMONSTRATION EVENTS

65.1 Pre-Demonstration Preparations

65.1.1 USV Preparation and Functional Inspection

65.1.2 Demonstration Readiness Review

65.1.3 USV Transport

65.2 Phase I – On-Site System Design, Construction, and Operation Overview

75.2.2 Support Requirements

85.2.3 Personnel Requirements

85.3 Phase II – Operational Performance

85.3.1 Launch and Recovery

85.3.2 Sensor/Payload Calibration

85.3.3 Target Detection

95.3.4 Maritime Target Activity and Interdiction Situational Awareness

95.3.5 Missions

115.3.6 Standoff Determination from Surface Asset

125.3.7 Close out Summary Briefing

125.3.8

125.4 Phase III – USV System removal

125.4.1 Removal of USV

125.4.2 Removal of the CMS

125.4.3 Support Gear

125.4.4

135.4.5 Data Collection

DATA COLLECTION INDEX

RISK MANAGEMENT

147.1 Safety Requirements

147.2 Test Hazard Analysis

147.3 Security Requirements

147.4 Environment

147.5 USV Operations Risk

ADMINISTRATIVE CONSIDERATIONS

158.1 Personnel Contact Information

158.2 Demonstration Plan Revision History

158.3 Data Distribution List

158.4 Report Distribution List

158.5 Safety and Security

A-1APPENDIX A.

INSTRUMENTATION PLAN

B-1APPENDIX B.

DAILY DATA RECORD

C-1APPENDIX C.

COMMUNICATIONS PLAN

LIST OF FIGURES

2Figure 1. Proposed Operational Area for the USV System demonstration.

10Figure 2. Example ladder search pattern.

11Figure 3. Example spiral search pattern.

LIST OF TABLES

4Table 1. Technology Demonstration sequence (durations estimated/average).

8Table 2. Phase I demonstration team personnel.

12Table 3. Phase II demonstration team personnel.

12Table 4. Phase III demonstration team personnel.

13Table 5. Data Collection Index

LIST OF ACRONYMS AND ABBREVIATIONS

(This page intentionally left blank.)

1 INTRODUCTION

In 2018 Congress tasked the United States Coast Guard (USCG) to examine the feasibility, costs, and benefits of improving Maritime Domain Awareness (MDA) in the remote Pacific Ocean using a low cost unmanned surface system. The USCG 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 USCG’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 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.

RDC is collaborating with Global Fishing Watch (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 will be shared with GFW. They will assist in verifying ship detections and potentially assist in determining behavior of detected ships.

The goals of the demonstration include:

· Determine the operational utility of an Unmanned Surface Vehicle (USV) System for USCG maritime missions in remote areas.

· Quantify the impact of utilizing the USV System.

· Demonstrate USV System operational capabilities in the maritime environment.

· Inform the development of Concepts of Operation (CONOPS) for a USV System.

· Demonstrate the integration of the USV System into the maritime law enforcement force structure.

1.1 Demonstration Phases

The demonstration will be comprised of three major phases:

· Phase I – USV System Characterization

· Phase II – USV System Operational Performance

· Phase III – USV System Removal and Out-brief

1.2 Assumptions and Limitations

· The demonstration will focus on commercially available, low cost USV systems that have a minimal logistical footprint.

· For the demonstration, the USV will be in the operational area for 30 days. Set up and removal time is in addition to the 30 days.

· The demonstration will utilize contractor owned and operated systems.

2 DEMONSTRATION FACILITY AND EQUIPMENT

2.1 Demonstration Facility

2.1.1 Location – South of Oahu, Hawaii

The intent of operating just south of Oahu is to minimize the logistical impact on demonstration personnel. Should a recovery of the USV be required, it will be a reasonable trip. If the demonstration requires a staged passing ship, again, the distance is reasonable (see Figure 1). This is a suggested operational area and can be changed if necessary. However, the intent is to demonstrate the USV system in the Pacific Ocean, remotely and beyond line of sight to show the communications aspect of the USV system.

Figure 1. Proposed Operational Area for the USV System demonstration.

2.1.2 Demonstration Facility Requirements:

The contractor shall describe the plans for the Demonstration Control/Monitoring Center (DCMC) and any shore side facilities required.

2.1.3 Logistics

Facility logistics include:

· Communications links

· Power

· Fueling (if applicable)

· Targets

· Data collection

· Security

· Very Important Person (VIP) Events including Media and daily briefs

· USV(s) monitoring system

· Maritime Detachment “Deployed Configuration”

· Contractor provided afloat assets (Contractor shall provide specifications of afloat asset to support USV system and vignettes in accordance with SOW)

2.1.4 Target Vessels

The contractor shall describe target vessels to include the one contractor provided boats and expected targets of opportunity in the operations area.

2.1.5 Instrumentation Plan

The contractor shall document their instrumentation plan in APPENDIX A.

2.2 Communications Plan

The contractor shall document their communications plan in APPENDIX C.

The plan will describe the data links and communications system segment which provides the beyond-line-of-sight (BLOS) communication path between the USV(s) and the control/monitoring center along with communications to the remote locations and other platforms.

2.3 Support Equipment

The contractor shall describe all support equipment required. This could include but is not limited to spare parts, tools, office equipment, support boats, communications equipment, USV tracking equipment, launch and recovery equipment, and conference rooms for briefs and discussions.

2.4 Payload

The contractor shall describe the design and operations of the payload on the USV. This is to include power production, power consumption, onboard processing to minimize communications costs of the alert signals, and the integrity of the USV during the demonstration.

2.5 Daily Briefs

The contractor shall provide a daily briefs format that describes what will be included in the brief.

3 DEMONSTRATION DESIGN

3.1 Scope

The scope of the demonstration includes the preparation, inspection, transport, at sea demonstration, operation, and removal of a USV System for the purpose of generating data that examines the operational utility of a USV System for conducting Intelligence, Surveillance, and Reconnaissance (ISR) missions in remote ocean environments.

3.2 Schedule

The schedule presented in Table 1 is a draft for a proposed sequence of events that the demonstration will follow. The contractor shall modify Table 1 to suit their proposed technology while maintaining a 30 day demonstration. Weather events and other external factors may require that the schedule be altered over the course of the demonstration. The demonstration will be a 24/7 operational event but the alert system on the USV can be used to ease the manning needs during the night and weekends, allowing a longer time between the alert and the next step in the process. Each event in the table are estimates/averages and presented for information only. The USV System Tech Demo is expected to take place in July and August 2020. Current plans for the at sea 30 days is from 15 July to 13 August 2020.

Table 1. Technology Demonstration sequence (durations estimated/average).

Weeks 1-2 Demonstration Preparation

System Instruction

Week 4

Phase II

Detection Performance

Detection Performance

Detection performance

Completion, USV System Removal, and Summary Briefing

4 DEMONSTRATION METHODS AND PROCEDURES

4.1 Roles and Responsibilities

The contractor shall be responsible for the USV System and its operation in its entirety. The contractor will be responsible for directing the contractor provided boat according to the daily plan.

The USCG Project Manager will be responsible to be liaison between the contractor, the USCG customer, and GFW.

USCG operators and GFW will be responsible for verifying the USV System alerts.

4.2 Operational Procedures

The contractor is responsible for operational procedures.

4.3 Safety Briefings

The contractor is primarily responsible for safety and the safety elements of the daily morning briefings.

4.4 Data Collection

4.4.1 Data Sheets

Data will be collected during all aspects of the demonstration. For each event, the following data will be recorded (see APPENDIX B for sample data sheets):

· Date

· Time

· Environmental Conditions

· Location

· Alert

· Alert Verification Data/documentation for all support evolutions includes:

· Photographic and/or video documentation

· Written description of any support required Additional Data/documentation for all evolutions includes:

· Personnel requirements (number and qualifications)

· Equipment requirements

· Mishaps, warning lights, communications failures, faults, etc.

· Pre-, through-, and post-deployment and maintenance - photographic and descriptive summary documentation

· Photographic and/or video capture of screen (if applicable) Additional specific data requirements are included in the discussion of each day’s operations during the daily brief.

4.4.2 Media Events

The contractor shall describe a media strategy for responding to any media inquiries or events with the USCG’s authorization and preparations for up to three presentations for the media.

5 DEMONSTRATION EVENTS

5.1 Pre-Demonstration Preparations

5.1.1 USV Preparation and Functional Inspection

The contractor shall document a plan or action and milestones for the USV Preparation and Functional Inspection.

5.1.2 Demonstration Readiness Review

The contractor shall describe their high level plan for conducting the DRR.

5.1.3 USV Transport

The contractor shall describe how they will transport the USV system and supporting equipment.

Data/documentation to be collected:

· Transport configuration and assembly photographs

· Assembly data: data/documentation for all support evolutions

· Any calibrations required

· Any issues with the shipment

5.2 Phase I – On-Site System Design, Construction, and Operation Overview The contractor shall modify the following example sections to be consistent with their USV system.

5.2.1.1 USV System Design, Construction, and Operation Overview The overview may include a verbal briefing/walkthrough of the USV System furnished for demonstration. The briefing could 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.

Data may include:

· Storage requirements

· Fuel availability/commonality (if applicable)

· Climate restrictions

· Temperature

· Rain

· Sea State

· Communications

· Software (detection sensors, communications, training, etc.)

· Detect and avoid solutions

· Modularity

· Instrumentation and data collection capabilities

5.2.1.2 Mission Configuration

The contractor shall propose a format and content for the Mission Configuration Data Sheet.

5.2.1.3 Support Equipment Demonstration

The contractor shall list/document the support equipment needing a briefing/walkthrough.

Data to be collected:

· Support equipment/tooling

· Photographic documentation and list

5.2.1.4 Maintenance Evolutions

The contractor shall list/document all the maintenance activities to be demonstrated:

Data to be collected:

· Photographs/video of the processes

· Maintenance documentation/cards (if available)

· For each evolution:

· Data/documentation for all support evolutions

· Consumables

· Hazardous materials (HAZMAT)

5.2.1.5 Pre-deployment/Operations/Post-deployment Inspections The contractor shall list/document the procedures to execute pre-deployment, operations, and post-deployment activities for the entirety of the USV, CMS, and associated equipment.

Data to be collected:

· Pre-deployment check list.

· Operations check list.

· Post-deployment check list.

· For each evolution: data/documentation for all shore-side evolutions.

5.2.2 Support Requirements

5.2.2.1 Contractor Support.

The contractor shall identify all support that may be required to operate the USV system that only the contractor should do.

5.2.3 Personnel Requirements

Table 2 provides an example list of demonstration team personnel and roles for Phase I. (Contractor shall update Table 2 with contractor personnel and roles) Table 2. Phase I demonstration team personnel.

5.3 Phase II – Operational Performance

5.3.1 Launch and Recovery

The contractor shall describe the launch and recovery events.

Data to be collected:

· Data/documentation for all control/monitoring station/shipboard evolutions

· Photos/video of the Launch

· Special equipment requirements

· Photos/video of the Recovery

· Special equipment requirements

5.3.2 Sensor/Payload Calibration

The contractor shall list/document the sensors to be calibrated.

Data to be collected (as applicable):

· Procedures

5.3.3 Target Detection

The contractor shall describe a target detection regime.

Data to be collected for each evolution:

· General.

· Data/documentation for all evolutions

· Profiles and search patterns used

· Characterization of the surveille and detect process

· Range from USV to target at events

· Imagery

· Locations and types of targets identified

· Datalink usage

· Ability to maintain awareness of previous targets

· Detection

· Target location

· Method used

· Classification. (If applicable)

· Time

· Target type (description, course, and speed)

· Process (including sensor used)

· Identification. (If applicable)

· Imagery

· Any unique identifiers or behaviors

· Direction/location finding results

· Frequency

· Content (if available)

5.3.4 Maritime Target Activity and Interdiction Situational Awareness

The contractor shall describe demonstration events that allow USV(s) and sensor/payload to detect moving maritime targets to enhance situational awareness for law enforcement activities.

Data to be collected:

· Data/documentation for all evolutions.

5.3.5 Missions

In addition to the mission listed in this section, the contractor shall propose and describe specific missions to execute during the 30 demonstration that demonstrate the capability of the USV.

5.3.5.1 Loiter

The USV Can demonstrate the ability to loiter in a given location. The loiter will last for 24 hours and the USV will be tracked to show the actual drift during the loiter. This will be repeated in different environmental conditions. The actual loiter pattern will be recorded and be part of the submitted data.

Data collected during the loiter:

· GPS track

· Environmental conditions around the USV(s)

· Any alerts

5.3.5.2 Ladder Search Pattern – Maximize Efficiency

The USV will execute multiple ladder search patterns (Figure 2) with the goal of maximum efficiency.

Figure 2. Example ladder search pattern.

Data to be collected:

· GPS recorded continuously and reported twice daily

· Environmental conditions around the USV(s)

· Any alerts

5.3.5.3 Spiral Search Pattern – Maximize Efficiency

The USV will execute multiple spiral search patterns (Figure 3) with the goal of maximum efficiency.

Figure 3. Example spiral search pattern.

Data to be collected:

· GPS recorded continuously and reported twice daily

· Environmental conditions around the USV(s)

· Any alerts

5.3.6 Standoff Determination from Surface Asset

The USV will determine/demonstrate the maximum standoff distances associated with sustaining communications to the launching surface asset. This is to explore the possibilities of operating the USV from a ship to determine the viability of increasing the patrol area using the autonomous system. As this tasking aims to generate data on USV performance, while working in concert with a ship it will be required that the sensor and/or payload be operating during this activity.

Data to be collected:

· GPS track

· Environmental conditions around the USV(s)

· Any alerts

· Communications connectivity

5.3.7 Close out Summary Briefing

The contractor shall describe the contents of the Close out Summary Briefing.

5.3.8 Personnel Requirements

Table 3 provides a list of demonstration team personnel and roles for Phase II. (Contractor shall update Table 3)

Table 3. Phase II demonstration team personnel.

5.4 Phase III – USV System removal

5.4.1 Removal of USV

The USV shall be retrieved or programmed to return to the contractor’s site.

5.4.2 Removal of the CMS

All equipment and office gear shall be removed from the CMS in accordance with the contractor’s agreement.

5.4.3 Support Gear

All support gear will be removed and returned to the contractor’s site.

5.4.4 Personnel Requirements

Table 4 provides a list of demonstration team personnel and roles for Phase III.

Table 4. Phase III demonstration team personnel.

5.4.5 Data Collection

Record any issues or maintenance required upon removal of the USV System.

6 DATA COLLECTION INDEX

Table 5. Data Collection Index

Preparation

System Characterization/ Instruction

Detection Performance

Detection Performance

Detection performance

Completion, USV System Removal, and Close out Summary Briefing

7 RISK MANAGEMENT

Risk management is the process by which:

· Hazards are identified;

· An assessment is made of the risks involved;

· Mitigating procedures are established to reduce or eliminate the risks; and

· A conscious decision is made, at the appropriate level, to accept residual risks.

As a precursor to USV testing, it is prudent to assess hazards and implement processes and procedures to manage risk. Processes and procedures inherent to testing of manned craft frequently have to be adapted to accommodate USV technologies and capabilities, and new approaches have to be developed to address considerations unique to USVs. (NATO, 2010)

The contractor shall describe any risks in their approach to meeting the requirements of the SOW and describe how they will mitigate those risks.

7.1 Safety Requirements

The contractor shall describe how they will control and monitor safety for the demonstration. An example could be a Safety Checklist which consists of a series of standard questions for all USV testing that is intended to assure that all “lessons learned”, and appropriate preparations have been incorporated into the plan. The checklist is essentially a double-check of all configuration, envelope, and procedural actions implemented to minimize risk. The checklist is designed to stimulate the thinking process of all test team members so that the risks associated with all types of test operations can be materially reduced and is based on lessons learned from past mishaps. Yes and no answers are not considered adequate, but rather pointers to the location where the question’s appropriate response is addressed are cited. If a question is not applicable to the test, the reason should be explained. (NATO, 2010)

7.2 Test Hazard Analysis

The contractor shall describe the process they will use to identify all hazards or risks associated with the proposed demonstration, then to rate those hazards in terms of both severity and probability, and then to identify means by which the hazards can be reduced. For example, a failure modes analysis provided by the designers, if available, provides an excellent basis for developing this description. Those failure modes that pose a risk of loss of the USV, injury, or property damage must be considered, and appropriate corrective action employed. Actions such as proficiency, training, and simulator runs may be used to help mitigate risks. (NATO, 2010)

7.3 Security Requirements

The contractor shall describe any security requirements that will be addressed for successful completion of the demonstration.

7.4 Environment

The contractor shall describe how the USV system will monitor and report on the environment it is operating in.

7.5 USV Operations Risk

The risk of running a low cost USV in the open ocean is low. However, such things as being runover, netted, or just taken do exist. The contractor shall describe actions to be taken should any of these situations arise.

8 ADMINISTRATIVE CONSIDERATIONS

8.1 Personnel Contact Information

To Be Added

8.2 Demonstration Plan Revision History

To Be Added

8.3 Data Distribution List

To Be Added

8.4 Report Distribution List

To Be Added

8.5 Safety and Security

The classification of this project is unclassified. The demonstration plan, USV demonstration data, and reports are unclassified. This demonstration plan has been reviewed for OPSEC requirements, and it has been determined that a definitive OPSEC annex to this demonstration plan is not required.

(This page intentionally left blank.)

APPENDIX A. INSTRUMENTATION PLAN

[This will be provided by the contractor.] (This page intentionally left blank.)

APPENDIX B. DAILY DATA RECORD

These are modifiable by agreement between the contractor and the government.

APPENDIX C. COMMUNICATIONS PLAN

[This will be provided by the contractor.]

Distribution Statement A: Approved for public release; distribution is unlimited.

Destruction Notice: For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Mar 2019

Low Cost Unmanned Surface Vehicle (USV) System Technology Demonstration Plan