Statement of Work - Lidar Upgrade.pdf

Upgrade of Coastal Mapping Program

Bathymetric Lidar System for the National Geodetic Survey

NCNL3000-20-00571

Statement of Work

March 11, 2020

1. Introduction/Background

The National Oceanic and Atmospheric Administration (NOAA) is congressionally mandated to survey the National Shoreline and nearshore bathymetry. Currently, the National Geodetic Survey (NGS), Remote Sensing Division (RSD) utilizes both a Riegl VQ-880-G topographic/bathymetric lidar system

(installed aboard the NOAA Dehavilland Twin Otters) and a Riegl LMS-Q680i topographic lidar system

(typically used separately as a standalone topographic system, and/or in conjunction with cameras) to support the Coastal Mapping Program (CMP) safety of navigation mission to update NOAA Nautical

Charts as well as:

● emergency response activities related to manmade and natural disasters

● airport obstruction surveying in support of the Aeronautical Survey Program (ASP)

● coastal change analysis, ecosystem mapping and monitoring

● storm surge modeling

● related research and development initiatives

These state-of-the-art systems have provided enhanced mapping capabilities when compared to traditional aerial photographic imagery methods by providing cost-effective, digital elevation data with high spatial resolution and accuracy. These systems are specifically designed for topographic and bathymetric use and are merged with aerial photographic imagery taken simultaneously in order to create a seamless depiction of shoreline and terrain features. Ability to rapidly preview data for basic quality and completeness during and immediately after flight is important.

In order to provide tidal-datum-based shoreline and nearshore bathymetry as efficiently and effectively as possible for a wide variety of project sites, NOAA requires the capability to collect seamless, high-resolution elevation data on both sides of the land water interface, including in the marine nearshore zone to a minimum depth of 5 meters. To meet this need, an airborne topographic-bathymetric lidar system, capable of simultaneously mapping both the subaqueous and subaerial areas of the coastal zone is required. Additionally, topographic-bathymetric lidar data enable determination of water depths for application on NOAA Nautical Charts shoreward of the 4 meter / Navigation Limit Line (NALL) – an area that is traditionally difficult and dangerous to survey with marine vessels and therefore contains the greatest amount of gaps/uncertainty on charts. Other applications of topographic-bathymetric lidar with

NOAA/NOS include coral reef habitat mapping, nearshore modeling including inundation and storm surge, and riverbed mapping. Simultaneously serving these various geospatial data needs will strengthen

NOAA's Integrated Ocean and Coastal Mapping (IOCM) role, as well as meeting NOAA mission requirements.

The current lidar systems were last upgraded in 2013. As with the standard life cycles of complex technical equipment, maintenance issues are occurring more regularly and exposing the program to greater risk. In an effort to increase capabilities, reduce program risk, and reduce time lost to maintenance, NGS is pursuing the upgrade of the existing topographic-bathymetric system.

2. Requirements

The government requires upgrade and support services, maintenance, and licensing, of a Riegl VQ-880-G topographic-bathymetric lidar system to a modern, two-channel airborne topographic-bathymetric lidar system that includes the following subsystems:

● housing for the sensors narrow field of view (FOV) shallow bathymetric lidar (Dmax = 2.7/Kd),

● topographic lidar

● 80MP or greater mid-format camera collecting both Red, Green and Blue (RGB) and Color-

Infrared (CIR) coalingned images.

● the ability to add an additional wide FOV deep-channel lidar (Dmax = 4/Kd) on an as-needed basis

● the sensor control unit, operators console, pilot display, and all sensor peripherals for operation of the systems

The specific systems being replaced are a Riegl VQ-880-G and Riegl LMS-Q680i which include the following components:

Riegl VQ-880-G Riegl LMS-Q680i

Component Component

VQ-880-G (Scanner) LMS-Q680i (scanner)

DR1560 (Data Recorder) Riegl Data Recorder

Phase One iXController Applanix Inertial Measurement Unit (IMU)

Applanix Inertial Measurement Unit

(IMU) Applanix POS AV

Applanix Position and Orientation

System for Airborne Vehicles (POS

AV)

3. Product Specifications:

The new airborne, topographic-bathymetric lidar system must meet the following minimum requirements:

Sensor Head, consisting of

Integrated lidar sensors and Quality Control (QC) camera with all necessary cabling, storage, power, control units, accessories and documentation manuals.

Topographic lidar sensor with the following capabilities:

● Infrared laser capable of 500,000 points/second or greater.

● Able to operate at a minimum altitude of 300 m and max altitude 1,600m.

● Capable of a point density of 10pts/m2 or greater at an operating altitude of

400m Above Ground Level (AGL), 60 m/s aircraft speed.

Shallow bathy lidar sensor with the following capabilities:

● Green laser capable of 140,000 points/second or greater, with digital full waveform capture.

● Depth range of 2.7/Kd or greater

● Capable of a point density of 5 pts/m2 or greater at an operating altitude of

400m AGL, 60m/s aircraft speed.

Modular deep bathy lidar sensor with the following capabilities:

● Green laser capable of 40,000 points/second or greater, with full waveform capture

● Depth range of 4/Kd or greater

● Capable of a point density of 1 pts/m2 or greater at an operating altitude of

400m AGL, 60m/s aircraft speed.

QC Camera

● QC camera that is 5MP or greater

● Able to capture imagery at a minimum of 1 frame per second.

Integrated Camera Head with lidar sensor with all necessary cabling, lens, filters, storage, power, control units, accessories, peripherals, and documentation manuals.

Camera Sensor with the following capabilities:

● Camera with 80MP or greater RGB and Near Infrared (NIR) frame sensors and beam splitter to produce co-registered 4-band imagery.

● Camera must be able to capture imagery at a minimum of 1 frame per second.

Integrated Global Navigation Satellite System/Inertial Measurement Unit

(GNSS/IMU) with all necessary cabling and documentation

● IMU data rate of 200 Hz or greater.

● IMU must be non-export restricted

● GNSS Receiver must be able to track GPS and GLONASS L1/L2 signal

● 1 year license and software maintenance

Operator Console, consisting of:

● Operator Console and display for Camera Operator with all necessary cabling and peripherals

Pilot display, consisting of:

● Pilot Display with all necessary cabling and peripherals

Gyro stabilized mount for sensor head consisting of:

● Gyro stabilized mount to accommodate sensor head with all necessary cabling, documentation, accessories and peripherals.

● 1 year extended warranty

Software package, consisting of

Lidar processing software (3 license) with the following capabilities:

● Point cloud generation for lidar

● Lidar calibration tool

● 3D viewing/editing tool

● Automatic water refraction correction

● Automatic data classification

● Waveform viewing

● Image viewing

● Lidar data Q/A tools

● Lidar data export

● 1 year license and software maintenance

Imagery software with the following capabilities:

● Imagery Development

● Imagery Orthorectification

● Boresight calibration

● Camera orientation calculation

● 1 year license and software maintenance

Flight management system software with the following capabilities:

● Flight guidance and sensor control

● 1 year software license and maintenance.

GNSS/IMU software with the following capabilities:

● Able to control and configure GNSS/IMU hardware

● Able to post-process kinematic GNSS and IMU data

● 1 year license and software maintenance.

Mission planning software with the following capabilities:

● Flight line planning for both Lidar and Imagery

Additional Specification

● A system that can be operated in both pressurized and unpressurized aircraft.

● Total unit weight of 260 kilograms or less (including deep channel module). Total unit weight of 180 kilograms or less without deep channel module.

● Compatible with a Dehavilland DHC-6-300 (Twin Otter) or Beechcraft

350ER (King Air) aircraft

4. Deliverables:

The following documentation and items specific to the replacement system are required:

1. NOAA NOS has a range of research interests involving topographic-bathymetric lidar. Current research objectives include analyzing recorded waveforms to better resolve coastal vegetation

(e.g., dense marsh grass) and the underlying terrain, as well as very shallow water depths in subaqueous waveforms. Other areas of interest include: a) generation of seafloor reflectance images to support benthic habitat mapping, b) detection of objects (e.g., wrecks and rocks) protruding above the seafloor, as well as generation of models to estimate probability of detection of different types of objects under different operating conditions, c) merging of topographic-bathymetric lidar with acoustic survey data using algorithms and methods familiar to the hydrographic survey community, and d) generation of total propagated uncertainty (TPU) models for shoreline and other coastal data products derived from lidar. To accomplish many of these tasks, there will be both a hardware component and a software component that the vendor will have to work with NOAA to develop. The vendor shall address the option for collaborative

Research & Development (R&D) on these and other coastal research topics of interest to NOAA.

2. Established calibration procedures (both in-flight and lab calibration) geometric stability over time shall be provided.

3. Depth Calibration procedures and methodologies shall be documented and provided.

4. A full accounting for the time necessary to collect and process point cloud data.

5. A detailed description of the installation / removal procedures shall be submitted, including time estimates to complete the iteration, including an ensuing calibration / quality assurance required.

6. The warranty and maintenance structure shall be detailed thoroughly. Technology upgrade paths shall be addressed if available.

5. Hardware/Software Maintenance and Licensing

The government intends to have one (1) full year of hardware and software maintenance, licensing, and support included to begin upon delivery with four (4) additional option years for hardware and software maintenance, licensing, and support. Maintenance and software updates shall be performed throughout the applicable performance period. The vendor shall have the ability to provide around-the-clock (24 hr.)

technical service and troubleshooting.

A Technical Service Representative shall be able to respond on-site to the Aircraft Operations Center in

Lakeland, FL, within 12 hours. When technical issues are encountered, the vendor shall make every effort to have them resolved within 24 hours. In cases where the issue cannot be quickly resolved on-site, the vendor shall provide an equal or better replacement (loaner) system or replace the failed component until technical issues with owned system are resolved.

Interim, no-charge, substantially-equivalent product will be provided during maintenance and/or repair periods subject to equipment availability and logistics limitations.

6. Training

Conduct 3 individual, but separated 1-week training sessions to include 5 – 10 attendees

1st Week of Training will be conducted at NOAA's Aircraft Operations Center (AOC) at 3450 Flightline

Dr. Lakeland, FL. This training will cover project planning, equipment installation, calibration of system, flight operations, post processing, and bathymetric best practices.

2nd Week of Training will be conducted at NOAA's Aircraft Operations Center (AOC) at 3450 Flightline

Dr. Lakeland, FL at least one month after 1st week of training. This training will reexamine as NOAA deems necessary project planning, equipment installation, calibration of system, flight operations, post processing, and bathymetric best practices, as well as address any significant issues or concerns NOAA has experienced since the 1st week of training and resulting operations of the system.

3rd Week of Training will be conducted at 1315 East West Highway, Silver Spring, MD at least one month after 2nd week of training. This training will reexamine as NOAA deems necessary project planning, equipment installation, calibration of system, flight operations, post processing, and bathymetric best practices, as well as address any significant issues or concerns NOAA has experienced since the 1st week of training and resulting operations of the system.

There are no prerequisites for the training.

7. IT Security Requirements

The Assessment and Authorization (A&A) requirements of Clause 48 CFR 1352.239-72 do not apply, and a Security Accreditation Package is not required.

The Contractor shall only supply Information Technology (e.g., hardware, software, firmware, etc.)

and/or product license and shall not require the use of any contractor owned equipment. The contractor will not have remote access to any government owned equipment. The Contractor shall ensure the acquiring Information Technology provided disables “phone home” or similar capabilities.

The Contractor shall include the necessary product support and supporting documentation that allows the sanitization for the acquiring Information Technology and/or service(s) upon the disposal of the product.

The Contractor shall use one of the methods for secure destruction of unclassified but sensitive information recommended by either NIST Special Publications 800-88 Guidelines for Media Sanitization

(https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r1.pdf) or the National Security

Agency in the Media Destruction Guidance (https://www.nsa.gov/resources/everyone/media-destruction/).

The Contractor shall ensure the acquiring information technology or service(s) are engineered for trustworthy and security and shall be maintain throughout the lifecycle of this contract following the engineering-based trustworthy secure solutions as outlined in NIST Special Publication 800-160 Systems

Security Engineering: Considerations for a Multidisciplinary Approach in the Engineering of

Trustworthy Secure Systems (https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-

160v1.pdf).

The Contractor shall provide sufficient document demonstrating the acquiring information technology or service(s) complies with Office of Management and Budget Memorandum M-07-18 entitled Ensuring

New Acquisitions Include Common Security Configurations and the Federal Acquisitions Regulations

(FAR) 39.101(d) regulations require NIST common security configuration checklists including United

States Government Configuration Baseline (USGCB) initiative. The Contractor shall provide sufficient documentation, which demonstrates the acquiring information technology or service(s) has implemented common security configuration checklists. Common security configuration checklists are available at

National Checklist Program (NCP), (https://nvd.nist.gov/ncp/repository), the U.S. government repository of publicly available security checklists (or benchmarks) that provide detailed low-level guidance on setting the security configuration of operating systems and applications. If the Contractor does not have common security configuration checklist for the acquiring information technology or service(s), than the

Contractor shall provide a rationale for not meeting the OMB M-07-18 requirement.

The Contractor shall ensure that the acquiring information technology or service(s) complies with the

Homeland Security Presidential Directive 12 (HSPD-12) requirements from FAR 4.1302 stating: (a) In order to comply with FIPS PUB 201, agencies must purchase only approved personal identity verification products and services, (b) Agencies may acquire the approved products and services from the GSA, Federal Supply Schedule 70, Special Item Number (SIN) 132-62, HSPD-12 Product and Service

Components, in accordance with ordering procedures outlined in FAR Subpart 8.4. If the Contractor does not comply with HSPD-12 requirement for the acquiring information technology or service(s), than the

Contractor shall provide a rationale for not meeting the HSPD-12 requirement.

The Contractor shall ensure that the acquiring information technology or service(s) complies with Internet

Protocol Version 6 (IPv6) requirements from FAR part 11.002 requirements. FAR part 11.002 requirements state that unless the agency Chief Information Officer waives the requirement, when acquiring information technology using Internet Protocol, the requirements documents shall include reference to the appropriate technical capabilities defined in the USGv6 Profile

(https://www.nist.gov/programs-projects/usgv6-program) and the corresponding declarations of conformance defined in the USGv6 Test Program. DOC acquisition of IP protocol technology shall express requirements for IPv6 capabilities in terms of the USGv6 Profile (e.g., using the USGV6

Capabilities Check List) and vendors shall be required to document their product’s support of the requested capabilities through the USGv6 test program (reference https://www.nist.gov/programs-projects/usgv6-program) using the USGv6 Suppliers Declaration of Conformity. If the Contractor does not meet the IPv6 / FAR part 11.002 requirements for the acquiring information technology or service(s), than the Contractor shall provide a rationale for not meeting the FAR part 11.002 requirement.

The Contractor shall provide all supporting documentation or a reference to obtain the necessary material, which describes the security capabilities, the design and development processes and the testing and evaluation procedures used by the acquiring information technology or service(s). The Contractor shall provide all supporting documentation or a reference to obtain the necessary material, which describes all information technology or service(s) updates and enhancements when implemented. A few examples of the information technology or service(s) supporting documentation includes the user guide, system administrator guides or hardening guide. The Contractor shall provide document(s) or a reference to obtain the information that describes the functional properties of the security controls employed to permit the analysis and testing of the security controls for the acquiring information technology or service(s).

The Contractor shall provide sufficient document demonstrating the acquiring information technology or service(s) provided complies with the following:

a) The standard installation, operation, maintenance, updates and/or patching of software shall not alter the common secure configuration settings (e.g., USGCB and/or other secure baseline),

b) Applications designed for normal end users shall run in the standard user context without requiring elevated system administration privileges.