SPECIFICATIONS.docx
DOCX document 16 KB Posted
- Attached to
- GNSS RECEIVERS
- Solicitation number
- 1305M220Q01443
View the file
Other files
| File | Type | Posted |
|---|---|---|
| QA for Amendment.docx | DOCX document | |
| Amendment A-20-001 to 1305M2-20-Q-01443-NCNL.pdf | ||
| Combined Synopsis - Solicitation.docx | DOCX document |
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
Trimble Alloy GNSS Receivers Specifications
Introduction/Background: The National Geodetic Survey (NGS) has a clearly stated mission to “define, maintain and provide access to the National Spatial Reference System” (NSRS). This mission is founded in Congressional mandates and Executive orders and has been the basic mission of NGS since its inception as part of the Survey of the Coast in 1807. In particular, the NGS Field Operations Branch supports positioning efforts with field surveys for Coastal Mapping, NERRS, Federal Aviation Administration Airport Obstruction Surveys, and various internal NGS surveying efforts. NGS requires GNSS receivers to capture geodetic quality observations to define and validate the geodetic framework needed for foundational data acquisition and support of NOAA mapping programs. Currently, satellite positioning constellations are evolving and this acquisition will replace older receivers not currently able to utilize all available satellite data for positioning purposes. This can lead to less accurate data and the inability to meet project demands of collecting data in all of the GNSS spectrum. In addition to updating receivers to capture data from new constellations, NGS also has a need to purchase geodetic quality receivers for deployment at NGS-owned and operated Continuously Operating Reference Stations (CORS) stations in direct support of the National Spatial Reference System (NSRS). NGS desires to purchase additional receivers that can meet the needs of NGS’ Spatial Reference System Division (SRSD).
Scope of Work This procurement is for nine (9) Trimble Alloy GNSS Receivers and associated constellation upgrades. This procurement is brand‐ specific and additional brand‐name justification is required.
Product Specifications Nine (9) Trimble Alloy GNSS receivers that meet the below requirements including all related cables, accessories, and software necessary for configuration/download.
| Item |
| Quantity |
| Description |
| 109100-00 |
| 9 |
| Trimble Alloy GNSS Receiver |
| 109UPG-BDS |
| 9 |
| Alloy Upgrade - Enable Beidou |
| 109UPG-GAL |
| 9 |
| Alloy Upgrade - Enable Galileo |
| 109UPG-IRNSS |
| 9 |
| Alloy Upgrade - Enable IRNSS |
| 109UPG-QZSS |
| 9 |
| Alloy Upgrade - Enable QZSS |
| 109UPG-RTX |
| 9 |
| Alloy Upgrade - Enable RTX |
Requested Delivery: Delivery no later than September 30, 2020 Deliver to:
NOAA/NOS/National Geodetic Survey Attn: Will Freeman #8821 1315 East West Highway Silver Spring, MD 20910
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. |
File details come from the government source that posted it. Updated .