Sol_140G0326Q0152.pdf

WOMEN-OWNED SMALL

BUSINESS (WOSB)

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NUMBER 3.AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NUMBER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

REQUEST

FOR QUOTE

(RFQ)

INVITATION

FOR BID

(IFB)

REQUEST

FOR

PROPOSAL

(RFP)

SEE ADDENDUM

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Government Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN 29. AWARD OF CONTRACT: REFERENCE

. YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 11/2021)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NORTH AMERICAN

INDUSTRY CLASSIFICATION

STANDARD (NAICS):

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM - DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FREE ON

BOARD (FOB) DESTINATION

UNLESS BLOCK IS MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4.

FAR 52.212-3 AND 52.212-5 ARE ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED.

8(A)

ECONOMICALLY

DISADVANTAGED

WOMEN-OWNED SMALL

BUSINESS (EDWOSB)

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

(SDVOSB)

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH

AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND

ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS

SPECIFIED

DATED.

OFFER

ADDENDA

ADDENDA

140G0326Q0152

See Schedule See Schedule

USGS OAG SACRAMENTO ACQUISITION BR.

MODOC HALL, CSUS

3020 STATE UNIVERSITY DRIVE EAST

SACRAMENTO CA 95819-6027

08/17/2026 0900 ED

0044041181

Joahnne Ongjoco 9162789328

GSB

GSB

Joahnne Ongjoco

334511

07/16/2026

0011287139

ADMINISTERED BY:

USGS OAG SACRAMENTO ACQUISITION BR.

MODOC HALL, CSUS

3020 STATE UNIVERSITY DRIVE EAST

SACRAMENTO CA 95819-6027 US

DELIVER TO:

Continued...

STOCK RECORD (S/R)

STANDARD FORM 1449 (REV. 11/2021) BACK

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE RECEIVED (MM/DD/YYYY) 42d. TOTAL CONTAINERS

40. PAID BY

32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

32g. EMAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

PARTIAL FINAL

37. CHECK NUMBER

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER

36. PAYMENT

COMPLETE PARTIAL FINAL

ACCEPTED,

Moffett ESC

350 N Akron Road

Building 19

Moffett Field CA 94035 US

Unrestricted opportunity.

A firm, fixed price five (5) year Indefinite

Delivery - Indefinite Quantity Contract is planned for Global Navigation Satellite System

(GNSS) Receivers in accordance with attached technical specifications, Section 508, FISMA, provisions, and clauses. Units will be ordered through delivery orders issued as specified in the contract using the pricing stated in the award document.

The Government shall place the first order, totaling the minimum of $29,000.00 over the full term of the base contract. The maximum quantity for the full term of the contract shall not exceed $2,999.999.00. The maximum quantity is not a representation to an offeror that the maximum quantity will be required or ordered or that conditions affecting delivery orders will be stable or normal.

FOB Destination:

Anchorage, AK 99508

Hilo, HI 96720

Moffett Field, CA 94035

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGES

NAME OF OFFEROR OR CONTRACTOR

SUPPLIES/SERVICES

(B)

UNIT

(D)

UNIT PRICE

(E)

AMOUNT

(F)

OPTIONAL FORM 336 (4-86)

Sponsored by GSA FAR (48 CFR) 53.110

ITEM NO.

(A)

QUANTITY

(C)

NSN 7540-01-152-8067

Pasadena, CA 91106

Seattle, WA 98195

Vancouver, WA 98683

Estimated ordering period/period of performance: September 15, 2026 - September

15, 2031

Evaluation method is Trade-Off. Please see evaluation factors as described in FAR 52.212-2 in the provisions of attachment.

It is the responsibility of all interested parties to check back periodically for any amendments to the solicitation. All amendments must be signed and included when the quotation is submitted.

Award will be made in accordance with

Revolutionary FAR Overhaul (RFO), FAR Subpart

12.204, Award. Anticipated award date is

August 28, 2026. All responsible sources may submit a quotation which will be jointly considered by DOI and USGS.

If interested, please include the following in your quotation:

1. Firm, fixed price; include completed Exhibit

A. Pricing Sheet

2. Sufficient information to be considered for evaluation factors

3. Subcontracting plan

4. Signed, standard form (SF) 1449

5. SAM UEI#

**Please submit your technical quote and price quote as separate attachments. Link submissions are not accepted.

Questions are due no later than July 31, 2026 at 0900 hours Eastern Time.

Quotations are due as indicated under block 8 of SF 1449.

Questions and quotations are accepted only by email to the contracting officer at

Joahnne_Ongjoco@ios.doi.gov. Hardcopy or

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGES

NAME OF OFFEROR OR CONTRACTOR

SUPPLIES/SERVICES

(B)

UNIT

(D)

UNIT PRICE

(E)

AMOUNT

(F)

OPTIONAL FORM 336 (4-86)

Sponsored by GSA FAR (48 CFR) 53.110

ITEM NO.

(A)

QUANTITY

(C)

NSN 7540-01-152-8067

submission by other means will not be considered.

Period of Performance: 09/15/2026 to

09/15/2031

00010 1 EAGlobal Navigation Satellite System (GNSS)

Receivers in accordance with the attached technical specifications, Section 508, provisions, and clauses.

IDIQ ordering limits:

Minimum order: $29,000.00

Maximum order: $119,000.00

Product/Service Code: 6655

Product/Service Description: GEOPHYSICAL

INSTRUMENTS

00020 1 EAGNSS Receivers - Separately Priced Optional

Features

Product/Service Code: 6655

Product/Service Description: GEOPHYSICAL

INSTRUMENTS

Attachment: 45 pages

The Department of the Interior (DOI), U.S. Geological Survey (USGS) Natural Hazards Mission Area, including the Earthquake, Volcano, and Landslide Hazards Programs seeks to award an Indefinite Delivery, Indefinite Quantity (IDIQ) contract for high-precision Global Navigation Satellite System (GNSS)-capable receivers for monitoring surface deformation and detecting ground motions (both small and large) for hazard assessment critical to public safety over time scales spanning seconds to years.

High-precision rapid position estimates from GNSS are a necessary component of the Earthquake Early Warning system. Characterizations of small-scale ground movements not detectable by other means have played crucial roles in assessing volcanic hazards prior to and during eruptions at US volcanoes and GNSS instruments are considered one of the three primary tools for volcano monitoring. These instruments are fundamental components of these monitoring stations in the US and globally. The ability to assess and understand rapidly emerging natural hazards relies on our continued ability to install high precision GNSS receivers at new locations and to replace equipment at existing sites in a timely manner when existing equipment fails.

Technical Specifications for GNSS Receiver

Required features include the following salient characteristics below.

Observables

• We require a multi-frequency GNSS (Global Navigation Satellite System) receiver able to simultaneously track all openly available signals, on all available frequencies, from all satellites in view, for the following GNSS: GPS, GLONASS, and SBAS. The capability to track and log all other GNSS, such as Galileo and BeiDou, and the regional QZSS and IRNSS signals, is preferred.

• Unsmoothed pseudo-range, signal-to-noise, Doppler, and carrier phase observables must be recoverable from the receiver.

• Receiver must provide a sample rate of 10 Hz or higher (pseudo range, carrier phase, signal-to-noise).

• Receiver must be able to simultaneously track all openly available signals on all in-view satellites, even if the SV is unhealthy, to an elevation angle of 0°. Receivers must allow simultaneous logging of multiple sessions with different length files at 15 samples/sec and 10 Hz sampling rates and must allow real-time streaming of 1 Hz observables.

• L1, L2, and L5 SNR in dB*Hz referenced to a 1 Hz (or better) bandwidth SNR (amplitude) discretization exceeds 0.5% of full scale. Signal to noise observations measured and stored at a resolution of 0.1 dB*Hz. The phase observations measured and

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 5 of 49 stored at a resolution of 0.001 cycle Pseudo-range observations measured and stored at a resolution of 0.001 meter

Input accepted and output produced

• The receiver must provide optional on-board (or in-the-box) Precise Point Positioning with Ambiguity Resolution (PPP-AR). The USGS strongly prefers to pay a one-time fee for this capability, rather than annual per unit and recurring fees for the necessary clock and orbit corrections stream needed for PPP-AR processing.

• Receiver is required to provide an “archival quality” stream protocol which includes all recordable GNSS data in BINEX format.

• Receiver must output 1 PPS with 5 ns or better timing accuracy and RTCM SC104 version 3.0 base station corrections.

• Receiver must support the input and output of MET, tilt, or accelerometer measurements:

a) As a serial/IP pipe using an NMEA string or in documented Vendors format and b) Recorded in receiver data file in BINEX format. Receiver must be capable of logging 8 independent sessions, each with multiple formats; the logging shall be independent of the GNSS satellite tracking and at user-selected intervals (e.g., every 5 minutes).

File formats

• Receiver must be capable of producing data streams and downloadable logged data files in BINEX format, containing all GNSS observables, navigation messages, attached MET, tilt, and other ancillary serial devices, site metadata, and system status records. Minimum requirement is BINEX 0x7f---05 with support for all GNSS observables, 0x00 for metadata and comments, and 0x01 for GNSS navigation messages. BINEX 0x7d for receiver state information is preferred.

• Receiver must be capable of producing data streams in RTCM3 format with support for IGS standard Multi-System Messages (MSM), using the protocols noted above.

• Full support for translation of data files to RINEX v3.02 format must be provided. This may be either onboard the receiver, in which case a data file is written in RINEX v3.02 format or files are translated on-the-fly when downloaded by a user, or in the form of software that will convert a native binary to RINEX v3.02 after downloading. All software executables must be compatible with LINUX operating systems.

• Proprietary (manufacturer’s) data formats used in data streams and logged files must be thoroughly documented so that USGS can update software to translate all pertinent contents and messages, including metadata. Modifications to proprietary formats that occur within the lifetime of the equipment must be documented and made available to USGS at the time of firmware release.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 6 of 49

File storage and memory

• Receiver must have a minimum of 16 Gb of industrial-grade internal memory.

• Receiver must stream and log to internal memory the GNSS observables at 10 Hz or greater. Streaming and logging rates must be configurable to 10Hz, 5Hz, 1 Hz, and 5, 10, 15, 30, 60, and 300 sec intervals.

• Receiver must provide internal data logging (with capacity equivalent to a minimum of 3 months at 10 Hz) or properly functioning continuous data streaming to external memory.

• Data storage for each logging session must be independently managed in partitions of user-configurable size using ring buffers or memory pools (i.e. automatic deletion of older data files will occur while newer files of lower sample rates are preserved). The option to stop logging a particular session when its memory pool has reached designated capacity instead of overwriting older files is required.

• The receiver shall support a user-specified data directory structure that allows for: 1) separate directories for each calendar month; 2) user-specified naming of the directories;

and 3) user-specified structure of the directories. At a minimum, each data logging session shall be stored in a unique directory. This is critical to facilitate data flow strategies that commonly involve directory content queries.

• File names must include either the ordinal date (e.g. YYYYDDD) or the Gregorian date (e.g. YYYYMMDD) from the time of creation of the file. A user-specified station name must also be included in the file name or must default to some known token such as the receiver serial number or some portion thereof. File names must also include characters to distinguish when multiple files are created on the same day.

Interaction with receiver

• A command-line API for uploading and application of receiver configuration files and firmware updates is required over TCP/IP and serial interfaces.

• A command-line API for gathering receiver state of health (e.g. temperature, voltage, and uptime) is required.

• Receiver must allow enabling or disabling any vendor defined code and carrier multipath rejection technology using a serial/IP command. In addition, vendor shall provide a list of other features capable of being modified by serial/IP command, such as switching between satellite and IP acquired clock and orbit corrections, opening or limiting RF bandwidth on the front-end, and any other functions modifiable through serial/IP commands.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 7 of 49

• The ability to save the configuration of the receiver in a downloadable file and upload it to other receivers remotely is required. Configuration files shall have the option of retaining network IP configuration or applying new user-specified IP settings.

• Network firewall or IP filtering scheme to protect the receiver from on-line attacks or unwanted access is required.

• User-accessible activity log files are required to aid in system troubleshooting that records system reboots, boot sequences, voltages, low voltage shutdown activity, temperature and shutdown sequences. The log file directory must be able to record the last 180 days of activity.

• Receiver must support FTP Push, Anonymous FTP support, Rsync, and SFTP (SSH) Support as well as FTP (TCP port configurable, REST support, MDTM support, Delete support).

• Streaming protocols supported include TCP/IP, UDP, and NTRIP.

• Wifi that can be enabled/disabled externally (without logging into the receiver)

• Web browser interface (http/https) for interacting with the receiver

• Web interface shall be configurable for use in a low-bandwidth environment.

• Receiver must be capable of differencing logged files and transferring only missing data segments rather than full files to minimize bandwidth usage.

• In order to facilitate the use of GNSS data in earthquake early warning, it is preferred that the receiver output the real-time data stream in either GeoJSON or tracebuf2 formats or both.

• Receiver interface includes a spectrum analyzer tool available for diagnosing interference.

• Receivers with integrated cellular modems will not be considered.

Ports

• Receiver must have at least 1 USB 2.0 (or better) and at least 2 serial ports with standard DB9 connector or 2 serial ports with custom connector and connector to DB9 cable.

• Receiver must have 2 power ports (one standard power input and one for battery backup) with power port logic.

• Receiver must have 1 Ethernet enabled port allowing for TCP/IP configuration of all receiver features, data files, and data streams. Port does not have to be in same enclosure as GNSS receiver. If it is an external serial to Ethernet adapter, the receiver must have a total of 3 serial ports.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 8 of 49

• Receiver must have serial port support for connection of at least 4 RS---232 meteorological devices, tilt meters, or other sensors (i.e. accelerometers) with data output integrated into both logged and streamed data. (4 ports, met support)

Power

• Maximum power consumption must be less than 5 watts with all available options utilized and must be capable of operating with less than 2 watts of power in a minimal configuration to preserve basic logging functions in situations where available power is extremely limited. These capabilities must be documented clearly in the proposal or product spec sheet. Receivers with lower power consumption are preferred.

• Receiver must automatically restart after loss of power and must power up in same configuration when powered down (or loss of power). The receiver must power-on at 11.85-12.0V and power off at 11.0-11.15V. Voltage range: Unit shall operate properly if external DC voltage of greater than 10.8 and less than 28 volts is applied. Wider operational power specifications are preferred.

• User-programmable reboot timer or other “watchdog” system is required that provides for automated system restarts without active user interaction (i.e. auto restart following power interruption and showing power-on voltage).

• User-programmable low-voltage behavior customization

• On-board battery or UPS is not required, and if present, should be removable at user option or must include user- configurable settings to control the circumstances under which power is used to maintain its charge. If a battery backup is present, the receiver must function properly if it loses its ability to maintain a full or partial charge to the backup system.

Physical requirements

• Receiver must meet the following environmental specifications: Operating temperature: - 40° C - + 65° C, IP Rating IP65 minimum. Preference for fully sealed IP68 and MIL- STD-810G shock rating (to survive a ~1m drop onto a hard surface).

• The receivers Mean Time Between Failure (MTBF) must be at least 57,500 hours according to the Bellcore “Ground Benign” specifications (quantifies the anticipated failure rate and is an "industry standard").

• The receiver must be compatible with existing USGS GPS antennas, (Topcon CR-G3, Ashtech choke ring, Septentrio/Tallysman VeraChoke, Trimble choke ring, and Trimble Zephyr Geodetic I, II, and III antennas).

• The selected receiver must have demonstrably low susceptibility to radio frequency interference at the primary GNSS frequencies, as well as side-band frequencies used for on-board PPP processing, including when using an existing USGS antenna.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 9 of 49

• Receiver must have USB, SATA, or other IEEE external housing (hardware failure protection).

• Receiver dimensions not to exceed 11” L x 7” W x 4” H (27.94 cm x 17.78 cm x 10.16 cm). Weight not to exceed 4.4 lbs (2 kg).

Accessories

• Price quotes should be provided for purchase of receiver both with and without a GNSS-capable antenna. Antenna model options should be compatible with all features of offered by the receiver (including but not limited to multi-frequency, multi-constellation GNSS;

onboard positioning; and multipath/radio frequency interference reduction) and be suitable for permanent field deployments.

• System must include either a universal AC power supply or DC power cable with polarity indicated as requested at time or order.

• System must include one RS232 cable (receiver to DB9) and one Ethernet 10baseT cable (receiver port to RJ45)

Field Performance

• The specific receiver proposed by the vendor, exactly as built in the proposal, will have a minimum of one year of documented service history in an established, continuously operating GNSS network. Proposals for equipment without at least twenty units having one year or more of field deployment history in an autonomous and continuously operating setting will be rejected.

• Receiver performance will match or be better than performance of receivers tested by EarthScope for deployment as permanent stations for the Network of the Americas (formerly the Plate Boundary Observatory) (https://kb.unavco.org/article/unavco-gnss-receiver-preferred-vendor-rfp-evaluation-report-830.html) o 1. Total Expected and Observed data—In the 90-10° elevation range receiver must have at least 99% observed to expected data with no more than 0.05% slips to observations. In the 10°- 5° elevation range receiver must have at least 90% observed to expected data with no more than 0.1% slips to observations. In the 5°- 0° elevation range receiver must have at least 30% observed to expected data with no more than 1.0% slips to observations.

o 2. MP1 and MP2 Tracking Statistics—In the elevation range 90-10°, 10°- 5° the receiver must have MP1 and MP2 values of less than 0.7 m. In the elevation range 5°- 0° the receiver must have MP1 and MP2 values of less than 1.0 m.

o 3. Observations per Slip—Over the elevation range 90°- 0° the receiver should have greater than 20,000 observations per slip (total number of observations

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 10 of 49 recorded divided by the combined MP1/MP2 slips). In the 10°- 5° and 5°- 0° elevation ranges the receiver must have less than 1% IOD slips.

o 4. Carrier phase precision must be at < 1 mm L1 and L2 (zero difference) and < 3 mm L3 (zero difference) at 15 sec sampling. Non-smoothed Pseudo range precision < 30 cm on L1 and L2 (< 100 cm L3) at 15 sec sampling rate.

o 5. Short baseline (~2 m), 24-hour solution precision must be 0.2 mm or better in the north and east components and 0.4 mm or better in the vertical component for L1 and L2. Solution precision must be 0.4 mm or better in the north and east components and 0.8 mm or better in the vertical component.

o 6. Short baseline (~2 m) residual troposphere delay must be no larger than 1mm (based on tracking down to 0° elevation range).

Separately Priced Options and Recurring Costs:

• Strong preference will be given to proposals that include no ongoing costs for receiver options, error correction services, or firmware upgrades, and in which lifetime product support is included.

• Report demonstrating the equipment’s ability to continue to track all signals through violent shaking, such as will occur during a large earthquake is of interest. In future requirements, potential vendors may be required to report acceleration and jerk tolerances of their equipment acquired though repeatable “shake tests”.

• The capability for event-triggered data logging sessions (e.g. a high sampling rate session that would activate if an attached accelerometer detects strong ground motion at the site) is preferred.

• On-board data compression is another capability that is very desirable. Smaller data files provide several benefits to USGS’s data flow operations. Vendor responses should clearly address tracking, logging, and streaming bandwidth and file size issues.

• On-board PPP-AR requirement must be separately priced option.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 11 of 49

Exhibit A. Pricing for Indefinite Delivery, Indefinite Quantity Contract Global Navigation Satellite System (GNSS) Receivers

Price may include Quantity Discounts.

Optional features are separately priced.

Ordering Period Year 1 Year 2 Year 3 Year 4 Year 5 GNSS Receiver, price per unit

GNSS Receiver with optional features, price per unit

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 12 of 49

ICT Accessibility Requirements Statement per Section 508 of the Rehabilitation Act

GNSS Receivers

E201 Application

E201.1 Scope. ICT that is procured, developed, maintained, or used by agencies shall conform to the Revised 508 Standards.

E206 Hardware

E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E208 Support Documentation and Services

E208.1 General. Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E302 Functional Performance Criteria

302.1 Without Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

302.3 Without Perception of Color. Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

302.6 Without Speech. Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 13 of 49

302.8 With Limited Reach and Strength. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

302.9 With Limited Language, Cognitive, and Learning Abilities. ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

Instructions to Offerors 1 Provide an Accessibility Conformance Report (ACR) for each commercially available Information and Communication Technology (ICT) item offered through this contract. Create the ACR using the Voluntary Product Accessibility Template Version 2.1 or later, located at https://www.itic.org/policy/accessibility/vpat.

Complete each ACR in accordance with the instructions provided in the VPAT template. Each ACR must address the applicable Section 508 requirements referenced in the Work Statement. Each ACR shall state exactly how the ICT meets the applicable standards in the remarks/explanations column, or through additional narrative. All "Not Applicable" (N/A) responses must be explained in the remarks/explanations column or through additional narrative. Address each standard individually and with specificity, and clarify whether conformance is achieved throughout the entire ICT Item (for example - user functionality, administrator functionality, and reporting), or only in limited areas of the ICT Item.

Provide a description of the evaluation methods used to support Section 508 conformance claims. The agency reserves the right, prior to making an award decision, to perform testing on some or all of the Offeror’s proposed ICT items to validate Section 508 conformance claims made in the ACR.

2 Describe your approach to incorporating universal design principles to ensure ICT products or services are designed to support disabled users.

3 Describe plans for features that do not fully conform to the Section 508 Standards.

4 Describe "typical" user scenarios and tasks, including individuals with disabilities, to ensure fair and accurate accessibility testing of the ICT product or service being offered.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 14 of 49 https://www.itic.org/policy/accessibility/vpat

Acceptance Criteria 1 Prior to acceptance, the government reserves the right to perform testing on required ICT items to validate the offeror’s Section 508 conformance claims. If the government determines that Section 508 conformance claims provided by the offeror represent an inaccurate level of conformance than what is actually delivered to the agency, the government shall, at its option, require the offeror to remediate the delivered item to align with the required Section 508 conformance claims prior to acceptance.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 15 of 49

FISMA 18-Point Checklist – IT Security Guidelines

U.S. Geological Survey Office of Acquisition and Grants Questions to askoag@usgs.gov

December 14, 2022 Page 1 of 6

COTS

Hardware or Software

Development or Maintenance of Custom Applications

Outsourced IT Services or On-site Support

Requirements herein are incorporated as part the Statement of Work/ Performance Work Statement:

1 N/A Background Investigations. The Contractor shall perform in accordance with clause “Security Requirements: Facility Access and Information Technology.”

2 N/A Non-disclosure Agreement. Prior to receiving access to USGS computers, contractor employees shall be required to sign nondisclosure or other system security agreements, depending on the systems to be used and level of access granted.

Applies whenever any contractor employee has unsupervised access to a USGS system (even if only basic network, internet or email or will develop custom applications) such as:

• User Access to USGS IT Systems known to contain sensitive or proprietary data

Contractor will have • IT Support services (greater than user access) access to Privacy • Development or Maintenance of Custom Applications Act System of Records - Work

• On-site contractor support and management of IT system

• Off-site contractor Oversight and Management of IT System under this contract will involve design,

• IT Security Services development or Privacy Act System: [Identify covered system(s) to which the contractor operation of (access

to) system(s) of records containing may have access] personal information protected by the

Work to be performed: [Summarize nature of the contractor's use of such records, such as]

Privacy Act (5 U.S.C.

Section 552a). • User-level access to system containing protected records

• Operation or maintenance of Privacy Act System of records or computers hosting such system

• Design or modification of a Privacy Act system of records] The contractor is not required or permitted to respond to requests for Privacy Act data or to make decisions about releases of data under the Act. Contractor shall ensure its employees are instructed to safeguard against improper use or release of such data and advise them that violation of the Act may involve criminal penalties. The contractor will comply with FAR clause 52.224-2, Privacy Act, incorporated herein by reference and with DOI Privacy Act regulations at 43 CFR 2, Subpart D

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 16 of 49 mailto:askoag@usgs.gov

Questions to askoag@usgs.gov

December 14, 2022 Page 2 of 6

COTS

Hardware or Software

Development or Maintenance of Custom Applications

Outsourced IT Services or On-site Support

Requirements herein are incorporated as part the Statement of Work/ Performance Work Statement:

3 N/A Training. The Contractor shall perform in accordance with clause “Security Requirements: Facility Access and Information Technology” - Contractor employees must successfully complete DOI’s end-user computer security awareness training prior to being granted access to DOI data or being issued a user account. Training must be renewed annually. Additionally, the contract employees must sign a Statement of Responsibility (SOR) that states they have read the appropriate Rules of Behavior and other applicable Information security policies.

4 N/A Personnel Changes. The Contractor shall perform in accordance with clause “Security Requirements: Facility Access and Information Technology” - The contractor must notify the COR immediately when an employee working on a DOI system is reassigned or leaves the contractor’s employ.

Applies whenever any contractor employee has unsupervised access to a USGS system (even if only basic network, internet or email or will develop custom applications) such as:

• User Access to USGS IT Systems known to contain sensitive or proprietary data

• IT Support services (greater than user access)

• Development or Maintenance of Custom Applications *

• On-site contractor support and management of IT system

• Off-site contractor Oversight and Management of IT System

• IT Security Services *

*May not be applicable for off-site performance.

5 N/A Contractor Location. The Contractor shall perform in accordance with clause “Security Requirements: Facility Access and Information Technology.”

Applies whenever any contractor employee has unsupervised access to a USGS system (even if only basic network, internet or email or will develop custom applications) such as:

• User Access to USGS IT Systems known to contain sensitive or proprietary data

• IT Support services (greater than user access)

• Development or Maintenance of Custom Applications

• On-site contractor support and management of IT system

• Off-site contractor Oversight and Management of IT System

• IT Security Services

No portion of the services to be performed hereunder may be performed outside the United States without the express written permission of the Contracting Officer.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 17 of 49

Questions to askoag@usgs.gov

December 14, 2022 Page 3 of 6

T

COTS

Hardware or Software

Development or Maintenance of Custom Applications

Outsourced IT Services or On-site Support

Requirements herein are incorporated as part the Statement of Work/ Performance Work Statement:

If services are proposed to be performed abroad, the Contractor shall provide an acceptable security plan that addresses mitigation of problems related to communication, control, and protecting the confidentiality, integrity, and availability of IT systems and information.

A Security Plan Template is available upon request from the Contracting Officer.

6 N/A N/A Applicable Standards. The Contractor shall perform in accordance with clause “Security Requirements: Facility Access and Information Technology” - Contractor must follow the DOI System Development Life Cycle (SDLC), NIST SP 800-64 and the DOI SDLC Security Integration Guide.

7 N/A Asset Valuation-Security Categorization: The Contractor shall perform in accordance with clause “Security Requirements: Facility Access and Information Technology.”

User Access to USGS IT Systems – The Government is responsible for security categorization on USGS systems to which the Contractor may have access under this contract.

IT Support Services greater than User-Level Services Choose one:

➔ The Government is responsible for security categorization on USGS systems to which the Contractor may have access under this contract.

-➔ he Government has defined the [insert name of system to be developed, operated or maintained by the contractor] to be a [Major Application], [Minor Application] or [General support system] as defined in OMB Circular A-130, Appendix III and NIST SP800-53. The following risk and sensitivity levels have been assigned based on the FIPS 199 and the NIST SP 800-60.

Mission impact:

Data sensitivity:

Risk level:

Bureau/departmental/national criticality:

Off-Site Oversight and Management of IT System- The Contractor shall use the FIPS 199 and the NIST SP 800- 60 to determine information types and security categorization based on mission impact, data sensitivity, risk level, and bureau / departmental / national criticality for Contractor-owned and operated systems used to provide services under this contract. Solicitations must include either the complete publication or a reference to public facilities, such as a website or office, where it may be accessed.

IT Security Services - Applies only if the purpose of the contract includes obtaining asset valuation services.

The Contractor shall use the FIPS 199 and the NIST SP 800- 60 to determine information types and security categorization based on mission impact, data sensitivity, risk level, and bureau / departmental / national criticality for Contractor-owned and operated systems used to provide services under this contract. Solicitations must include either the complete publication or a reference to public facilities, such as a website or office, where it may be accessed.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 18 of 49 https://doimspp.sharepoint.com/sites/usgs-OAG/AOP/guidefordevelopingsecurityplans.pdf

Questions to askoag@usgs.gov

May 11, 2021 Page 4 of 6

COTS

Hardware or Software

Development or Maintenance of Custom Applications

Outsourced IT Services or On-site Support

Requirements herein are incorporated as part the Statement of Work/ Performance Work Statement:

8 Property Rights.

1. For Federal Supply Schedule orders or orders under an existing contract, rights to software acquired hereunder are set forth in the basic contract.

2. For open market contracts, the Government's rights in software delivered hereunder shall be as described in software developer's commercial software license agreement or the clause FAR 52.227- 19, Commercial Computer Software-Restricted Rights, whichever is greater.

The Government Select either shall be granted COTS or custom unlimited rights in software software or data language as produced applicable. If hereunder as both apply, described in FAR identify clause 52.227- software/data 17, Rights in deliverables Data—Special governed by Works, each clause.

incorporated by reference herein.

9 N/A Independent Verification and Validation (IV&V). The Government is responsible for independent software verification and validation prior to being moved into production.

On-Site Contractor Support and Management of IT System Choose one:

➔ Software will be independently verified and validated by the Government or another selected contractor prior to being moved into production.

➔ Contractor will ensure that independent verification and validation is performed on software deployed on contractor managed systems containing USGS data, in accordance with DOI SDLC Security Integration Guide

Off-Site Contractor Operation and Management of IT System-Contractor will ensure that independent verification and validation is performed on software deployed on contractor managed systems containing USGS data, in accordance with DOI SDLC Security Integration Guide

IT Security Service - Applies only if the purpose of the contract includes obtaining IV&V services.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 19 of 49

Questions to askoag@usgs.gov

December 14, 2022 Page 5 of 6

COTS

Hardware or Software

Development or Maintenance of Custom Applications

Outsourced IT Services or On-site Support

Requirements herein are incorporated as part the Statement of Work/ Performance Work Statement:

10 N/A Certification & Accreditation.

User Access to USGS IT Systems or IT Supports Services (Greater than User Access Certification and Accreditation on USGS systems to which the Contractor may have access under this contract will be conducted by the Government or another of its contractors.

Development or Maintenance of Custom Applications The contractor will perform Certification and Accreditation (C&A) services on the application developed or maintained hereunder prior to going into production. The application must be re-accredited every three years or whenever there is a major change that affects security.

C&A documents will be provided to the COR in both hard copy and electronic forms. The contractor must follow NIST SP 800-37, 800-18, 800-30, 800-60, 800-53A, Federal Information Processing Standard (FIPS) 199 and 200, the associated DOI guides/templates, the DOI Security Test & Evaluation (ST&E) Guide, and the DOI Privacy Impact Assessment.

NIST documents are available on the internet at http://csrc.nist.gov/publications/nistpubs/ FIPS documents are available on the internet at http://csrc.nist.gov/publications/nistpubs/.

The contractor may request copies of DOI documents by contacting the Contracting Officer.

The government reserves the right to conduct the ST&E using either Government personnel or an independent contractor. The contractor will take immediate and timely action to correct or mitigate any weaknesses discovered as necessary to bring the application or system into compliance with the above requirement.

On-Site Contractor Support and Management of IT System or Off-Site Contractor Operation and Management of IT System The Contractor must maintain systems that are compliant with NIST SP 800-18, 800-30, 800-37, 800-53A, 800-60, Federal Information Processing Standard (FIPS) 199 and 200, the associated DOI guides/templates, the DOI Security Test & Evaluation (ST&E) Guide, and the DOI Privacy Impact Assessment. As required by the above, Major Applications and General Support Systems shall be certified and accredited (C&A) prior to going into production and re-accredited every three years or whenever there is a major change that affects security. C&A documents will be provided to the COR in both hard copy and electronic forms. NIST documents are available on the internet at http://csrc.nist.gov/publications/nistpubs/. The contractor may request copies of DOI documents by contacting the Contracting Officer. The government will reserve the right to conduct the ST&E, using either Government personnel or an independent contractor. The contractor will take immediate and timely action to correct or mitigate any weaknesses discovered as necessary to bring the application or system into compliance with the above requirement.

Applies if the purpose of the contract includes obtaining C&A services.

11 N/A for COTS HW & SW, User Access to USGS IT Systems (other than IT services), IT Support Services (User Level or greater access)

N/A Internet Logon Banner. The Contractor shall perform in accordance with clause “Security Requirements: Facility Access and Information Technology.”

Development or Maintenance of Custom Applications OR On-Site Contractor Support and Management of IT System OR Off-site Contractor Oversight and Management of IT System- Web-based applications developed or maintained under this contract must contain a USGS approved logon banner:

https://portal.doi.net/CIO/ITPMgmt/Documents/IT Standards/IT Security/DOI Security Control Standards (based on NIST SP 800-53 Revision 3)/Access Control v1.4.pdf

12 N/A Incident Reporting. The Contractor shall perform in accordance with contract clause “Security Requirements: Facility Access and Information Technology” - The contractor must report computer security incidents affecting DOI data or systems in accordance with the DOI Computer Incident Response Guide.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 20 of 49 mailto:askoag@usgs.gov http://csrc.nist.gov/publications/nistpubs/ http://csrc.nist.gov/publications/nistpubs/ http://csrc.nist.gov/publications/nistpubs/ https://portal.doi.net/CIO/ITPMgmt/Documents/IT%20Standards/IT%20Security/DOI%20Security%20Control%20Standards%20(based%20on%20NIST%20SP%20800-53%20Revision%203)/Access%20Control%20v1.4.pdf https://portal.doi.net/CIO/ITPMgmt/Documents/IT%20Standards/IT%20Security/DOI%20Security%20Control%20Standards%20(based%20on%20NIST%20SP%20800-53%20Revision%203)/Access%20Control%20v1.4.pdf

Questions to askoag@usgs.gov

December 14, 2022 Page 6 of 6

COTS

Hardware or Software

Development or Maintenance of Custom Applications

Outsourced IT Services or On-site Support

Requirements herein are incorporated as part the Statement of Work/ Performance Work Statement:

13 Quality Control. All software or hardware purchased must be free of malicious code such as viruses, Trojan horse programs, worms, spyware, etc. Validation of this must be written into the contract.

14 N/A N/A Self-Assessment. The Contractor shall perform in accordance with contract clause “Security Requirements: Facility Access and Information Technology” - The contractor must conduct an annual self-assessment in accordance with annual DOI guidance on all information systems in production.

15 N/A Vulnerability Analysis. Vulnerability Analysis on USGS systems to which the Contractor may have access under this contract will be conducted by the Government or another of its contractors.

16 N/A Logon Banner. Contractor employees who access DOI information systems must acknowledge a government-approved legal warning banner prior to logging on to the system. This includes contractor owned information systems hosting DOI data.

17 N/A Security Controls.

The Contractor shall perform in accordance with contract clause “Security Requirements: Facility Access and Information Technology” – The Contractor shall ensure compliance with the security control requirements of the current version of NIST SP 800-53, Rev.1, which are applicable to the security categorization of the data or system. FIPS 199 and the NIST SP 800-60 will be used to determine information types and security categorizations.

18 N/A N/A Contingency Plan.

The Contractor shall perform in accordance with contract clause “Security Requirements: Facility Access and Information Technology.”

For IT Support Services: The Contractor shall submit a contingency plan in accordance with NIST SP 800-34 and DOI IT Systems Contingency Plan Guide.

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 21 of 49

COMMERCIAL PROVISIONS

52.252-1 Solicitation Provisions Incorporated by Reference (Feb 1998) This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at https://www.acquisition.gov/far/ and at https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52.

The following provisions are incorporated by reference, with fill-ins noted as appropriate:

52.203-11 – Certification and Disclosure Regarding Payments to Influence Certain Federal

Transactions (SEP 2024) 52.203-18 – Prohibition on Contracting with Entities that Require Certain Internal

Confidentiality Agreements or Statements-Representation (JAN 2017) 52.204-7 – System for Award Management (NOV 2024)(Deviation MAR 2026) 52.212-1 – Instructions to Offerors – Commercial Products and Commercial Services (SEP

2023)(Deviation MAR 2026) 52.219-1 – Small Business Program Representations (FEB 2024)(Deviation JAN 2026, Updated FEB 2026) 52.222-18 – Certification Regarding Knowledge of Child Labor for Listed End Products

(FEB 2021)

52.212-2 – Evaluation-Commercial Product and Commercial Services (NOV 2021/Deviation APR 2026)

(a) Evaluation factors. The Government will award a contract resulting from this solicitation to the responsible Offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. Trade-Off evaluation method will be used. The following factors will be used to evaluate offers:

• Technical Capability. Provide sufficient information to indicate understanding, capability, and capacity to fully meet the requirement.

• Past Performance. Provide references, including points of contact and contact information, who can report past customer experience. Additionally, we will utilize Contractor Performance Assessment Reporting System (CPARS) for any available data on past performance and reserve the right to use any other source of past performance information.

• Price

• Subcontracting Plan

DOI, USGS RFP# 140G0326Q0152 GNSS Receivers Page 22 of 49 https://www.acquisition.gov/far/ https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52

Non-price factors are somewhat more important than price.

Offeror must submit sufficient documentation and information to be evaluated for the factors above.

Technical proposal and price proposal must be submitted as a separate attachments. Link submissions are not accepted.

Failure to provide the requested information may result in removal from further consideration.

(b) Notice of award. A written notice of award or acceptance of an offer furnished to the successful Offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer’s specified expiration time, the Government may accept an offer (or part of an offer), whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.

(End of Provision)

52.233-2 – Service of Protest (SEP 2006)

(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed…