SON Maint eCognition.111425 Final.doc

DOC document 47 KB Posted

Attached to
Trimble eCognition Software
Solicitation number
141017-26-0001
Issued by

About this file

This document is a Statement of Need (SON) for NOAA's Office for Coastal Management regarding eCognition software licensing and maintenance. The requirement involves procuring three (3) eCognition Developer licenses and two (2) eCognition Server licenses for a 36-month performance period from December 1, 2025 to November 30, 2028. The solicitation is a sole-source procurement with Duncan Parnell, citing Trimble Navigation Limited as the sole authorized provider of maintenance and support services.

The document includes detailed IT security requirements, emphasizing compliance with various federal standards such as OMB Memorandum M-07-18, HSPD-12, IPv6 requirements, and NIST security configurations. The software is critical for NOAA's remote sensing operations, specifically for processing AVHRR and IKONOS data, and integrating with other geospatial software platforms like Imagine and ArcView. The North American Industry Classification Code (NAICS) for this acquisition is 561990 (All Other Support Services), with a business size standard of $16.5 million.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

NOAA Office for Coastal Management eCognition Software Maintenance and Support Statement of Need

SCOPE

The Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service’s (NOS), Office for Coastal Management (OCM) has a requirement for obtaining licensing, maintenance and support for Trimble’s eCognition software.

DESCRIPTION

To provide licensing and maintenance/support for three (3) eCognition Developer licenses and two (2) eCognition Server licenses for thirty-six (36) consecutive months.

TASK

To provide maintenance and support for three (3) eCognition Developer licenses and two (2) eCognition Server licenses for thirty-six (36) consecutive months. Support and maintenance should be provided both during the base period as well as during the chosen optional periods.

ENTITLEMENT #
DESCRIPTION
QUANTITY
18ee-9d61-13f7-d49e-ad79-0c
ECognition Developer licenses ECOG-DEV-N-M
3
1tnldwh82p64qqvoa3ng and n2opiwgfxx7qpg231ca7
ECognition Server licenses ECOG-SER-N-M
2

PERIOD OF PERFORMANCE

The base period of performance shall be from 12/1/2025 to 11/30/2028.

IT SECURITY REQUIREMENTS

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

The contractor will only supply software, product license and will not require the use of any contractor owned equipment. The contractor will not have remote access to any government owned equipment.

The contractor must 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 product or services being provided for this acquisition.

The contractor must provide all supporting documentation or a reference to obtain the necessary material which describes all product or service updates and enhancements as they are implemented.

The product or service supporting documentation could be the user and system administrator guides, which is documents the functional properties of the security controls employed to permit the analysis and testing of the security controls.

The contractor must provide sufficient document demonstrating the software being provided complies with Office of Management and Budget Memorandum M-07-18 entitled Ensuring New Acquisitions Include Common Security Configurations. For Windows applications, the provider of information technology shall certify applications are fully functional and operate correctly as intended on systems using the Federal Desktop Core Configuration (FDCC), United States Government Configuration Baseline (USGCB) initiative or other NIST identified (http://checklists.nist.gov) secure configuration. The standard installation, operation, maintenance, updates and/or patching of software shall not alter the configuration settings from the approved FDCC/ USGCB/other secure configuration. The information technology should also use the Windows Installer Service for installation to the default “program files” directory and should be able to silently install and uninstall. Applications designed for normal end users shall run in the standard user context without elevated system administration privileges.

The contractor must provide sufficient documentation which demonstrates the acquiring information technology has implemented common security configurations. Common security configurations are available from the National Institute of Standards and Technology’s website at http://checklists.nist.gov.

The contractor includes the necessary product support and supporting documentation for the hardware and/or software that allows the sanitization (following NIST Special Publications 800-88 Guidelines for Media Sanitization) of the hardware and/or software upon the disposal of the product.

The contractor must ensure that the product being purchased 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.

The contractor must ensure that the product being purchased complies with Internet Protocol Version 6 (IPv6) requirements from FAR part 11.002 (g) stating: when acquiring information technology using Internet Protocol, the requirements documents must include reference to the appropriate technical capabilities defined in the USGv6 Profile (NIST Special Publication 500-267) and the corresponding declarations of conformance defined in the USGv6 Test Program. The applicability of IPv6 to agency networks, infrastructure, and applications specific to individual acquisitions will be in accordance with the agency's Enterprise Architecture (see OMB Memorandum M-05-22 dated August 2, 2005).

File details come from the government source that posted it. Updated .