SOW.docx

STATEMENT OF WORK

PROJECT: ELECTRONIC REPORTING OF LOGSHEET DATA IN PACIFIC ISLAND REGIONAL LONGLINE FISHERIES

Background/Overview:

This requirement is for National Oceanic & Atmospheric Administration (NOAA) Fisheries, Pacific Islands Fisheries Science Center (PIFSC) in Honolulu, Hawaii. Captains of Hawaii and American Samoa-based longline vessels must submit their catch logbook within 72 hours of returning to port in accordance with 50 CFR § 665.14. The logbook forms are on hardcopy paper media and can mailed, faxed, or dropped off at an approved location. Since 2006, captains have been allowed to electronically report for managed fisheries that require logbooks. Electronic reporting (ER) is believed to be more efficient than paper logbook reporting and can reduce errors, thus saving time for both fishermen and NMFS data technicians alike.

Through this project, participants in the Hawaii and American Samoa-based longline fishery shall be provided with electronic hardware loaded with electronic reporting software, with the objective of increasing daily electronic reporting within the fleet. In order to support daily reporting, the electronic logbook software will be required to submit data through satellite transmission to PIFSC.

Objectives:

The goal of this requirement is to enable longline fishery participants to electronically submit daily catch and effort data to PIFSC. The objectives are to improve longline fishery monitoring and data collection. The implementation of an ER system should improve the quantity and quality of relevant fishery data and increase the efficiency in data submission by reducing the tag lag of incorporating data into PIFSC fishery databases. Full implementation to fishery participants will enable PIFSC to better monitor fishery Annual Catch Limit quotas.

Scope of Work:

The contractor shall develop an ER software and transmission for submitting daily longline catch and effort data. There are a total number of 165 vessels currently in the fisheries. The scope of work is initially envisaged to apply to approximately 60 participants given a staggered implementation plan with an ideal situation where approximately all of the 165 vessels will eventually participate.

Tasks:

Task 1. The contractor shall develop electronic software to load on Government-provided tablets.

1) Software shall replicate logbook forms functionality.1

2) The required data formatting is included in Appendix 1.

3) Software interface must allow accurate entry of required data by fishers.

4) Software shall be capable of supporting cost-optimized over-the-air form modifications.

5) Software shall meet NMFS certification standards.2

1 http://www.pifsc.noaa.gov/fmb/fmap/federal_forms/hawaii_longline_logsheet_2015.pdf

2 NOAA Pacific Islands Fisheries Science Center. 2009, Electronic Logbook Certification, Guidelines For Logbook Reporting in Pacific Island Fisheries, Version 1.7, June 11, 2009, PIFSC, 1845 Wasp Blvd, Building 176, Honolulu, HI 96818 https://www.federalregister.gov/articles/2009/07/07/E9-15958/fisheries-in-the-western-pacific- certification-requirements-for-electronic-logbook-applications. www.wcpfc.int/system/files/WPFMC.pdf

6) Software and hardware must be capable of securely transmitting required data to authorized entities near-real-time when “submitted” via the interface. Securely transmitted data will constitute end to end encryption. See: Security Requirements

The tablets supplied for the project are currently Nexus 7 running an Android version 5.1.1. operating system. The operating system can be upgraded if required by the software. The hardware should be capable of supporting a certified COTS cryptographic module. See: Security Requirements. If the hardware Nexus 7 is not sufficient, offerors should indicate proposed hardware in their proposal.

The contractor is anticipated to provide replacement tablets in the three Option Periods (below). Approximately 30 tablets are estimated to be replaced annually. The tablet should have an Android OS and be capable of receiving supported OS updates. PIFSC intends on using Android OS as this is the most widely available operating system for tablets on the current market.

Task 2. The contractor shall include the costs for daily satellite transmission of logbook data and provide an annual airtime plan to be included and separately identify cost structure. It is anticipated that data will be delivered to PIFSC via satellite and secure connection or as an email attachment. Initial estimates are that data transmission will be ~20 kilobytes per month for a vessel.

Task 3. The contractor shall produce a user manual for the ER software.

The contractor shall assign to the contract a Project Manager as the primary point of contact for this requirement. The duties of the Project Manager are as follows:

Project Manager:

Project Manager (PM) will assist in definition and development of project requirements and in planning, scoping and management of individual projects and sub-projects in support of the overall program. Individual must understand the contracting process, contracting and other procurement document preparation, monitoring of ongoing projects, meeting with key stakeholders and project status presentation and reporting.

Period of Performance:

The Period of performance for the base period is October 1, 2016 to September 30, 2017 with three additional one-year option periods that may be exercised at the sole discretion of the government. If options are exercised, dates are as follows:

Option Period I: October 1, 20176 – September 30, 20178 Option Period II: October 1, 20187 – September 30, 20198 Option Period III: October 1, 20198 – September 30, 202019

Place of Performance:

The contract shall be performed at the location of the contractor’s facility. The contractor shall visit the PIFSC on at least one (1) occasion per year for software discussion and demonstration or conduct a teleconference or webinar type meeting as appropriate.

Government-Furnished Property (GFP):

There is no Government-Furnished Property, special escort requirements, neither Applicable Standards nor Special Requirements.

IT Data and Security Requirements:

Secure Communications: The contractor must verify with the Government prior to transmission of information that all information designated will meet National Institute of Standards and Technology (NIST) Federal Information Processing (FIPS) 140-2 (security level 1), validated cryptographic module(s) which requires external service providers to use FIPS for processing, storing, or transmitting federal information or operating information systems.

The following items relate to IT Data and Security consideration:

1. Encryption shall be implemented with a FIPS compliant algorithm such as AES256 and SHA2, whereby there shall be software libraries to accomplish the encryption.

2. Encryption shall be implemented to safeguard logbook data at rest and in transit with FIPS 140-2 encryption.

3. Logs should be readable by authorized people (e.g. Coast Guard while boarding a vessel) by using the vessels AES256 shared key.

4. Logs should be encrypted from the time data are submitted until it is received by PIFSC or an authorized person (Coast Guard or the captain that signed the log) retrieves it. This could open up the data transmission methods and allow for more control or competition.

5. The chosen encryption implementation shall minimize the labor and infrastructure required to manage encryption keys. If a symmetric cryptography will be implemented (AES256) this shall make use of a shared private key. Operators are to be provided with a simple, secure management interface that allows encryption components on devices to be expired or changed periodically as needed.

The work required under this contract will not require access to NOAA IT systems.

Applicable Standards:

The industry specific standards that need to be adhered to when fulfilling the contract are: FIPS 140-2 Security Level 1; GSA Section 508 Standards (especially 1194.21, 1194.22, and 1194.25, seehttp://www.section508.gov/content/learn/standards/quick-reference-guide#1194.25); NIST 800-64 Rev. 2; OPM System Development Life Cycle Policy and Standards

Special Requirements:

Training and documentation shall be provided by the successful contractor for Government personnel on how to accomplish routine tasks, management of keys, and systems administration.

Deliverables Schedule:

Base Period

Option Periods

Acceptance Criteria:

The PIFSC will conduct validation tests for the ER software attaining the Electronic Logbook Certification. Validation tests comprise sending simulated logsheet data through the electronic software, satellite system and ensuring that it arrives at PIFSC. Data arriving at PIFSC are then reconciled with these simulated data. PIFSC will conduct tests within one (1) week of obtaining a software version.

APPENDIX 1

Data Stream Format

General Requirements

· Data securely transmitted via satellite (including end-to-end encryption)

· Data transmitted in CSV format

· Trip ID and Log ID formats to be specified at a later time

· Date formats to be specified at a later time

· CSV transmission data files formats

· Depart from port o Set information o Return to port

“Depart from Port” Data File Requirements

· Data to be transmitted when captains begin a trip and depart port.

· Data in Depart From Port CSV to include the following:

· Trip ID – Format to be specified (Generated by application)

· Vessel Name

· Permit Number o Departure Date o Departure Port

· Data output to be in the following format TripID,VesselName,Permit,DepartDate,DeparturePort

Set Information Data File Requirements

· Data to be transmitted within 24 hour of haul completion.

· Location would be manually entered from the GPS unit or connecting to an external GPS unit.

· Captains should be able to enter data as they complete different set events:

· Begin a set

· End a set

· Begin a haul

· End a haul

· Record their catch

· Data to be transmitted after a captain has completed entering the entire set information (after the catch report)

· Data in CSV to include the following:

· Log ID – Format to be specified (Generated by application) Ideally, would be entered before the captain begins a set.

· Side Set – T/F

· Observer on Board – T/F

· Date of Set

· Target Species

· Set Begin Time

· Set Begin Latitude Degrees

· Set Begin Latitude Minutes

· Set Begin Latitude Direction (North/South)

· Set Begin Longitude Degrees

· Set Begin Longitude Minutes

· Set Begin Longitude Direction (East/West)

· Mainline Length

· Bait

· Min. Hooks Between Floats

· Max. Hooks Between Floats

· Number Lightsticks

· Set End Time

· Set End Latitude Degrees

· Set End Latitude Minutes

· Set End Latitude Direction (North/South)

· Set End Longitude Degrees

· Set End Longitude Minutes

· Set End Longitude Direction (East/West) Entered after the captain finishes setting the gear.

· Haul Begin Time

· Haul Begin Latitude Degrees

· Haul Begin Latitude Minutes

· Haul Begin Latitude Direction (North/South)

· Haul Begin Longitude Degrees

· Haul Begin Longitude Minutes

· Haul Begin Longitude Direction (East/West) Entered before the captain begins the haul.

· Haul End Time

· Haul End Latitude Degrees

· Haul End Latitude Minutes

· Haul End Latitude Direction (North/South)

· Haul End Longitude Degrees

· Haul End Longitude Minutes Entered after the captain completes the haul.

· Haul End Longitude Direction (East/West)

· Captain Name

· Submission Date

· Species Code (1-n)

· Number Kept

· Number Released

· Protected Species Code (1-n)

· Number Uninjured

· Number Injured

· Number Dead As far as events go, catch report could be entered immediately after the End of Haul data.

· Data output to be in the following format:

· Line 1: Begin Set Data TripID,LogID,SideSet,ObserverOnBoard,SetDate,SetBegTime,SetBegLat Deg,SetBegLatMin,SetBegLatDir,SetBegLongDeg,SetBegLongMin,SetBegL ongDir

· Line 2: End Set Data NumHooksSet,MainlineLength,Bait,MinHooks,MaxHooks,NumLightstick,S etEndTime,SetEndLatDeg,SetEndLatMin,SetEndLatDir,SetEndLongDeg,Se tEndLongMin,SetEndLongDir,

· Line 3: Begin Haul Data HaulDate,HaulBegTime,HaulBegLatDeg,HaulBegLatMin,HaulBegLatDir,Ha ulBegLongDeg,HaulBegLongMin,HaulBegLongDir

· Line 4: End Haul Data HaulEndTime,HaulEndLatDeg,HaulEndLatMin,HaulEndLatDir,HaulEndLong Deg,HaulEndLongMin,HaulEndLongDir,NumHooksLost

· Line 5: Captain information from Catch Report CML,CaptainName,SubmissionDate

· Line 6 – n: Species Kept/Released data from Catch Report SpeciesCode,NumberKept,NumberReleased

· Line n+1 – x: Protected Species Interaction data from Catch Report ProtectedSpeciesCode,NumberUninjured,NumberInjured,NumberDead

· Sample Ouptut: 1234,123456,20160331,0623,15,32,N,155,2,W 3375,36,10,25,25,,1125,15,13,N,155,26,W 20160331,1808,15,14,N,155,26,W 0,0731,15,33,N,155,8,W CaptainA,999999,20160401 16,19,0 17,1,0 22,12,0 1,2,0 5,3,0

6,1,0 11,3,0 13,4,0 21,1,0 7,0,3 9,0,1 51,1,0,0 o 52,0,1,0

“Return to Port” Data File Requirements

· Data to be transmitted when captains ends a trip and returns to port.

· Data in Return to Port CSV to include the following:

· Trip ID – Format to be specified (Generated by application)

· Return Date

· Return Port

· Data output to be in the following format TripID,ReturnDate,ReturnPort