Statement of Need_CORIOLIX Draft.docx

STATEMENT OF NEED

Purchase Request Number: 140802-24-0343 Cruise Observations Real-time Interface & Open Live Information eXchange (CORIOLIX) for the NOAA Marine Operations Ship Fleet

PURPOSE:

OMAO uses a system called the Scientific Computing System (SCS) for data acquisition but requires additional purpose-built tools and services to access, visualize, monitor, and manage data and metadata in real-time from the ship and from shore. This includes mechanisms for shoreside technical support to monitor data quality, manage metadata for scientific sensors and systems, and to provide troubleshooting and evaluation of data in real-time. In consultation with the SCS team, the existing SCS system could not be leveraged or expanded to encompass all requirements and therefore it was determined that CORIOLIX meets the requirements and is compatible and easily integrated to meet the data management objectives.

TECHNICAL SPECIFICATIONS:

A security review of CORIOLIX has been completed by the Marine and Aviation Cyber Center (MACC) and has been approved for installation and use.

Technical Components:

· Operating System: Linux Debian 11

· Web Framework: Django 3.2 LTS

· Database: Postgres 15, with PostGIS

· SymmetricDS two-way database synchronization for cruise events & metadata

· MQTT publish-subscribe network transport protocol for real-time data

· API tools for data access on both ship and shore

· GLOBUS use for data distribution to repository

Services Provided:

· Shipboard and shoreside Web User Interfaces for access to real-time data

· Sensor metadata preservation, controlled vocabulary, and documentation of sensor historical information

· Charting tools for real-time visualization of data, route planning, and spatial awareness, with planned expansion to utilize the current NOAA Enterprise Agreement with Esri

· Built-in event logging (ship & shoreside event logs are synchronized)

· Dashboard style live and interactive data display pages

· System status for situational awareness of system health

· Repository for documentation including calibration files, standard operating procedures, best practices, and manuals

· User defined alerts & notifications over SMS, Email, or other messenger of choice

· Integrated (low effort) data access and integration and leveraging NOAA ERDDAP publish/subscribe client service

· Compatibility with Marine Facilities Planner (MFP) and capacity for integration to other cruise planning tools for ease of import for cruise planning documentation and two-way communication to maintain a source of truth for available shipboard sensors

· Automated data pipelines and data subscription services

· Integration of NOAA QARTOD real-time flagging standards

· Customizable user privileges for security

· Operations support including software updates, security patches, user feedback through ticketing, and continued development

Layer Features:

Sensor Layer - Sensor/Network Hardware & Software Interface:

· Hardware: Networked Industrial Single Board Computers w/analog and digital inputs

· Software: Standardized sensor datagram (JSON) w/optional output protocols (TCP, UDP, message queue) Data Transport Layer - Shipboard Data Network:

· publish-subscribe model for shipboard underway (and BYOD) sensors

· provides easy interface to “on the wire” data (enabling ad-hoc system extension) Data Management Layer – Well-structured shipboard data store:

· Data acquisition

· Data Storage

· Real-time data quality assessment capability implementing standard methods (QARTOD) Service Layer

· Notification Server - user defined alerts on multiple common channels (email, slack, sms)

· Map & GIS Server - OGC compliant map services

· Data Server - REST API for JSON & geoJSON, ERDDAP, OPeNDAP

· Event Logging

· Working implementation of a secure ship to shore message queue for real-time data streaming to shore Client Layer - Situational Awareness

· Common web user Interface for both shipside and shoreside users

· Individual user accounts

· Customized real-time data visualization for underway sensors

· Map application for visualization of underway and historic/external geospatial data

· Sensor information/metadata pages for maintenance management Data Stewardship

· Automated packaging of data for shipment to R2R, NCEI, or other archive

· Push capabilities to work with existing R2R post-cruise workflows and future development to NCEI

· Pull capabilities to permit data harvest by archives

DELIVERY SCHEDULE AND ADDRESS:

Services will include the integration, installation, deployment, and operational support of CORIOLIX on all current 15 and 2 future NOAA Ships in the fleet. Year 1 would begin immediately upon award and include the required development, metadata discovery, installation, initialization and deployment aboard each Ship as well as Survey Technician community training. Year 2 through 5 would include services related to operational support including software updates, security patches, user feedback and subsequent improvements through a ticketing system and continued development to meet future needs of OMAO Ship users.

Year 1: To begin immediately upon award approval for the integration of CORIOLIX including any required development, metadata discovery, installation and initialization of each NOAA Ship and end-user training for the following Ships and the Survey Technician Community:

1. NOAA Ship Bell M. Shimada

2. NOAA Ship Fairweather

3. NOAA Ship Ferdinand R. Hassler

4. NOAA Ship Nancy Foster

5. NOAA Ship Okeanos Explorer

6. NOAA Ship Oregon II

7. NOAA Ship Oscar Dyson

8. NOAA Ship Oscar Elton Sette

9. NOAA Ship Pisces

10. NOAA Ship Rainier

11. NOAA Ship Rueben Lasker

12. NOAA Ship Thomas Jefferson

13. NOAA Ship Ronald H. Brown

14. NOAA Ship Henry B. Bigelow

15. NOAA Ship Gordon Gunter

16. NOAA Ship Oceanographer

17. NOAA Ship Discoverer

Year 1 deliverables:

· Improved CORIOLIX compatibility with NOAA SCS

· Streamlined archive requirements with NOAA NCEI

· Address NOAA specific cybersecurity controls

· Installation guide and installer tailored for use on NOAA CI

· Population of vessel and sensor metadata across all systems and platforms

· Functional Testing of NOAA CORIOLIX infrastructure

· Training of personnel Total estimated value of Year 1

Years 2 through 5: Operations support including software updates, security patches, user feedback through ticketing, and continued development.

Total estimated value of Year 2-5 varies depending on schedule deliverables= renewal dependent on funding availability.

SPECIAL REQUIREMENTS: N/A