Sol_140FC126R0018_Amd_0003.pdf

PDF 250 KB Posted

Attached to
NM BITTER LAKE NWR AERIAL IMAGING
Solicitation number
140FC126R0018
Issued by

About this file

This is Amendment 0003 to Solicitation 140FC126R0018, issued by the U.S. Fish and Wildlife Service (USFWS), FWS Construction A/E Team, with an effective date of August 13, 2026. The amendment addresses 27 Requests for Information (RFI) and provides clarifying responses from the Contracting Officer Representative (COR) and contracting office regarding a topographic and bathymetric LiDAR acquisition and detailed field survey project at Bitter Lake National Wildlife Refuge in New Mexico.

The project scope includes: aerial topographic and bathymetric LiDAR data collection across a defined Project Area encompassing the North, Middle, and South Tracts of the Refuge; development of a project Digital Elevation Model (DEM), bathymetric DEM, and hydro-flattened DEM with ESRI geodatabase deliverables; 4-band aerial imagery acquisition; establishment of six primary survey ground control points in the Middle and South Tracts; and detailed field surveys at twenty water control structures with utility locate mapping. Key technical requirements clarified include: bathymetric LiDAR must follow the October 2025 Bathymetric LiDAR Base Specification by the Joint Airborne LiDAR Bathymetry Technical Center of Expertise; UTM Zone 13N coordinates with NAVD88 vertical datum (EPSG 6342) for DEM deliverables; classification per ASPRS Standard LiDAR Point Classes; and LiDAR acquisition flights must occur between November 2026 and February 2027. The amendment confirms that Award and Notice to Proceed are anticipated in October 2026, with a 120-day Period of Performance, and notes that no-cost extensions may be granted if necessary to accommodate coordination constraints. The SF330 submittal deadline remains September 24, 2026 at 5:00 PM EDT. The Contract Specialist is Drew Ferrall at john_ferrall@ios.doi.gov.

View the file

Other files

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

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: is not is required copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7.ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

PAGESOF

Contractor

The hour and date specified for receipt of Offers to sign this document and return

Tracy Gamble

See continuation page

FWS, Constr A/E 1 FWS, Construction A/E Tea 5275 Leesburg Pike Falls Church VA 22041

FC1

140FC126R0018

08/13/2026

08/13/2026

1 10

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

140FC126R0018/0003

The purpose of this amendment is to address

Request for Information (RFI) questions:

RFI 01: What is the required quantitative bathymetric vertical accuracy for the submerged bottom surface specifically? The PWS states a

10 cm RMSE requirement for Non-Vegetated

Accuracy (NVA) and references a "bathymetric

LiDAR equivalent for QL1," but does not appear to specify a separate numerical RMSE requirement for submerged-bottom accuracy.

COR Response: Bathymetric LiDAR should follow the October 2025 Bathymetric Lidar Base

Specification by the Joint Airborne Lidar

Bathymetry Technical Center of Expertise.

RFI 02: What EPSG code or UTM zone is required for the secondary LiDAR/DEM deliverable specified as "UTM coordinates and meters"? The

PWS defines the primary project CRS precisely but does not specify the UTM CRS for the second deliverable set.

COR Response: The coordinate reference system for the DEM deliverable in UTM coordinates and meters is as follows:

Projection: UTM Zone 13N

Units: Meters

Vertical Datum: North American Vertical Datum of 1988 (NAVD88)

EPSG Code(s): 6342

RFI 03: What is the acceptable percentage and treatment of Class 45 (no-bottom-found) bathymetric returns relative to the PWS's requirement that there be no data voids?

COR Response: Bathymetric LiDAR should follow the October 2025 Bathymetric Lidar Base

Specification by the Joint Airborne Lidar

Bathymetry Technical Center of Expertise.

RFI 04: Are the six primary control points required by the PWS six total for the project, or six specifically within the Middle and South

Tracts with additional control required in the

North Tract?

Continued...

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)

COR Response: The primary controls required in

Task 2: Survey Ground Control are six total for the project. Primary survey control monuments are not required in the North Tract, only in the Middle and South Tracts. Non-permanent mapping control may still be required to meet mapping specifications, as necessary.

RFI 05: Does USFWS require the topographic/bathymetric LiDAR and the 4-band aerial imagery to be acquired in one simultaneous flight, or are separate acquisition windows acceptable?

COR Response: Separate LiDAR acquisition flight windows may be acceptable within the timeframe specified by the PWS. Proposed timeframes for separate windows will be evaluated on a case-by-case basis to determine if the extended timeframe will be able to meet project goals within the site condition constraints.

RFI 06: For the "utility locate" requirement associated with the twenty detailed field survey sites, does USFWS require formal utility designation, or is mapping of visible/known utility features sufficient?

COR Response: Task 4: Detailed Field Survey requires CAD file deliverables for individual field locations with One (1) plan view drawing with comprehensive planimetric and utility locate. Mapping of visible utility features is sufficient for utility locate.

RFI 07: Could USFWS clarify whether the registered PE/PS required for Contract Manager and CQCP Manager must be a direct employee or principal of the prime contractor, or whether a committed key-person subcontractor holding the required license and experience would satisfy this requirement?

COR Response: USFWS will evaluate the Contract

Manager and assigned person for implementing the CQCP based on how well they meet the intent of the PWS requirements for qualified technical

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) staff. A subcontracted Contract Manager and/or assigned person for the CQCP who holds the required PE/PS license and relevant experience may satisfy the requirement.

RFI 08: The provided shapefiles include three project-area polygons consisting primarily of land areas with several water bodies located throughout. Please clarify the required extent of the bathymetric LiDAR acquisition.

Specifically, is bathymetric LiDAR required for all water bodies within the three project-area polygons, or only for certain water bodies or portions of the project area? If the requirement is limited to specific areas, please identify the water bodies or locations where bathymetric LiDAR acquisition is required. This clarification will assist us in developing the appropriate acquisition approach, sensor configuration, flight planning, and level of effort for the project.

COR Response: The scope of work is intended to include topographic and bathymetric LiDAR as required to meet the tasks outlined in the PWS.

Applicants should clearly outline the methods and assumptions used to achieve this in their submissions. There are no limitations to the water bodies considered for bathymetric collection at this time, refinement of bathymetric LiDAR areas may be coordinated with the selected contractor.

RFI 09: The Task 3 deliverables identify a project DEM, a Bathymetric DEM, and hydro-flattened breaklines, and state that collected hydro-breaklines will be incorporated into the DEM deliverable. Please clarify whether FWS requires a separate hydro-flattened

DEM in addition to the specified project DEM and Bathymetric DEM, or whether the project DEM incorporating the required hydro-breaklines is intended to satisfy the hydro-flattening requirement.

COR Response: A hydro-flattened DEM and topobathymetric DEM are required. An ESRI geodatabase of hydro-flattened breaklines is

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) also required.

RFI 10: The PWS requires classification of

Classes 3, 4, and 5 for low, medium, and high vegetation, respectively. Please clarify whether FWS has project-specific height thresholds for distinguishing low, medium, and high vegetation, or whether the Contractor should apply its standard classification thresholds consistent with ASPRS/USGS LiDAR

Base Specification requirements.

COR Response: Classification codes will follow the ASPRS Standard LiDAR Point Classes conforming to the USGS LBS minimum data classification scheme standard with Joint

Airborne Lidar Bathymetry Technical Center of

Expertise (JALBTCX) classes for bathymetry.

RFI 11: Page limit and format. Is there a page limit for the SF330 submission, including the

Criterion 8 methodology narrative? If so, please specify the maximum page count and any font or margin requirements.

COR Response: There are no page limit or formatting requirements for the SF330 submission.

RFI 12: Submission mechanics. Please confirm that only a single electronic PDF submitted by email to john_ferrall@ios.doi.gov is required, and that the "sealed offer" and "original plus one copy" language in Item 13 of the solicitation does not apply to this SF330 request.

Contracting Response: Solicitation number

140FC126R0018 is requesting SF330's, not a

Request for Proposal (RFP) (nor a request for an offer with a copy). Submit to john_ferrall@ios.doi.gov.

RFI 13: Past performance documentation, per firm or per team. For team members without a completed CPARS evaluation, does the requirement to provide at least three past performances that are recent and relevant apply

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) per firm (prime and each subconsultant separately), or as a total of three references for the entire proposed team?

COR Response: Documentation of a minimum of three past performances per submission is required, this total can include CPARS evaluations if available. Documentation of at least one past performance is required per contractor; this includes both the prime and subcontractors. The past performance documentation must be for recent projects and relevant to this one.

RFI 14: Past performance format. Is a specific

Past Performance Questionnaire (PPQ) template required for projects without CPARS, or may the offeror submit narrative past performance summaries with client reference contacts?

COR Response: There is no required format for past performance documentation separate from

CPARS. The client, work purpose, project dates, and evaluation must be included. The past performance documentation must be for recent projects and relevant to this one.

RFI 15: Anticipated award and Notice to

Proceed (NTP) timing. Given the requirement that Task 3 LiDAR flights occur between

November 2026 and February 2027, what is the anticipated award date and NTP date for this contract, and is there sufficient schedule margin for the Project Plan/CQCP (Task 1) and ground control establishment (Task 2) to be completed before the flight window opens?

COR/Contracting Response: Award and Notice to

Proceed (NTP) are anticipated to occur in

October 2026. Tasks other than the flights may also occur within the Period of Performance window as long as the flight occurs within the

LiDAR flight window. Depending on the issuance date of the NTP and the timing of the selected

LiDAR flight window date, the government may consider a no cost extension of the Period of

Performance for completion of the remaining tasks if necessary.

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)

RFI 16: Refuge clearing scope. The Performance

Work Statement states the refuge will clear

Bitter Creek before LiDAR collection and that the flight must occur within two weeks of that clearing. Does this same clearing and two-week flight window requirement apply to any other water features in the project area, or is it specific to Bitter Creek?

COR Response: Other areas of the Refuge may be cleared in advance of the flight and would be considered in selection of the acquisition timeframe. The intent of flying within two weeks of Bitter Creek being cleared by the

Refuge is to provide ideal conditions for capturing bathymetric data. The LiDAR acquisition flight window must also consider weather conditions and other factors that may influence ideal collection conditions. Aerial

LiDAR acquisition will occur with close coordination between the Contractor, Project

Manager, and Refuge Point of Contact.

RFI 17: Government-furnished GIS data. Can the

GIS shapefiles referenced in Tasks 3 and 5, or any existing prior LiDAR, imagery, or survey data for the refuge, be made available now to support methodology and proposal preparation?

COR/Contracting Response: Please see Amendment

0001 attachment in Contract Opportunities

(SAM.gov).

RFI 18: Key personnel registration. Section

1.6.12 requires the Contract Manager/Alternate to be a registered professional (engineer or surveyor). Does this individual need to hold current registration specifically in the State of New Mexico, as referenced in Ranking

Criterion 1(a), or is registration in any state sufficient for this role?

COR/Contracting Response: All registered professional roles must have licensure in New

Mexico.

RFI 19: Interview scheduling. If our firm is

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) selected among the top three most highly qualified firms for interviews under FAR

36.602-3(c), what is the anticipated timeframe for those interviews?

COR Response: Interviews may be held with the top three most highly qualified firms.

Interviews are anticipated to occur in October

2026.

RFI 20: Bathymetric coverage expectations.

What are the expectations for bathymetric coverage, particularly within the sink holes?

COR Response: Bathymetric LiDAR should follow the October 2025 Bathymetric Lidar Base

Specification by the Joint Airborne Lidar

Bathymetry Technical Center of Expertise.

RFI 21: Brush clearance lead time. What is the expected lead time for brush clearance before an aerial survey can take place, and how would that affect the 120 days from Notice to

Proceed?

COR/Contracting Response: The intent of flying within two weeks of Bitter Creek being cleared by the Refuge is to provide ideal conditions for capturing bathymetric data. Clearing and aerial LiDAR acquisition timelines will be selected with close coordination between the

Contractor, Project Manager, and Refuge Point of Contact. Depending on timing of the selected

LiDAR acquisition flight window date, the government may consider a no cost extension for completion of the remaining tasks.

RFI 22: Ground access lead time. What is the expected lead time for ground access to perform the ground control survey, and how would that affect the 120 days from Notice to Proceed?

COR/Contracting Response: There is no specific lead time for access to Bitter Lake NWR related to the ground control survey. Access will be coordinated with the Refuge as much of the

Refuge is not open for public access. Depending on timing of the selected LiDAR acquisition

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) flight window date, the government may consider a no cost extension for completion of the remaining tasks.

RFI 23: Hydro-flattened DEM deliverable. Do you require a hydro-flattened DEM in addition to a topobathymetric (ground and bathymetric bottom) DEM, or only 3D hydro-flattened breaklines?

COR Response: A hydro-flattened DEM and topobathymetric DEM are required. An ESRI geodatabase of hydro-flattened breaklines is also required.

RFI 24: Sensor advancements have not eliminated the limitations inherent in topo-bathymetric data lidar collection and processing, including poor returns in turbid water, vegetation, debris or poor bottom reflectivity.

Bathymetric Lidar data may be limited or non-existent (void) in these challenging conditions. Interpolated data may not meet

QL1 accuracy standards. Will bathymetric data interpolated across incidental Lidar void areas be acceptable?

COR Response: Bathymetric LiDAR should follow the October 2025 Bathymetric Lidar Base

Specification by the Joint Airborne Lidar

Bathymetry Technical Center of Expertise.

RFI 25: Is ground based bathymetric data collection limited to the twenty (20) water control structures identified in Attachment 1?

COR Response: Aerial topographic and bathymetric LiDAR survey is required for the project area. Bathymetric data must be collected aerially due to project area restrictions. Detailed field survey is required for twenty (20) water control structures.

RFI 26: The Performance Work Statement references Attachment 1 multiple times as depicting the project area and square-mile coverage; however, we have been unable to locate Attachment 1 within the solicitation

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) documents posted on SAM.gov. Could you please provide Attachment 1 or advise where it can be accessed.

COR/Contracting Response: Attachment 1 from the

Performance Work Statement was included as

Attachment 4 in the solicitation.

RFI 27: Project Area / LiDAR Acquisition

Boundary - The available GIS files include both a "Project Area" shapefile and a "Bitter Lake

NWR Boundary" shapefile, and the boundaries are not the same. The Project Area shapefile extends beyond the Refuge boundary. During the pre-proposal/site visit, my understanding was that the work would encompass the three Refuge tracts shown on the Attachment 4 Project Area

PDF, which is also consistent with the PWS description of the North, Middle, and South

Tracts. Could you please confirm which boundary/AOI should be used for the required topographic and bathymetric LiDAR acquisition and associated aerial imagery:

the Project Area shapefile;

the Bitter Lake NWR Boundary shapefile; or another boundary identified in the referenced

Attachment 1?

COR Response: The Project Area should be used for high resolution digital orthophotography, topographic and bathymetric LiDAR acquisition.

The Project Area encompasses the Bitter Lake

NWR Boundary which includes the North, Middle, and South tracts.

The SF330 submittal deadline date is unchanged and remains as September 24, 2026 (5:00PM EDT) per Amendment 0002.

End of Amendment 0003

Contract Specialist

Drew Ferrall john_ferrall@ios.doi.gov

Amendment of solicitation/modification of contract
Contract ID code
Amendment/modification number
Effective date
Requisition/purchase requisition number
Project number
Issued by
Code
Administered by
Code
Name and address of contractor
Code
Facility code
Amendment of solicitation number
Dated
Modification of contract/order number
Dated
This item only applies to amendments of solicitations
Accounting and appropriation data
This item applies only to modifications of contracts/orders.
This change order is issued pursuant to:
The above numbered contract/order is modified to reflect the administrative changes
This supplemental agreement is entered into pursuant to authority of:
Other
Important:
Description of amendment/modification
Name and title of signer
Contractor/offeror
Date signed
Name and title of contracting officer
Signature of Contracting Officer
Date signed
Previous edition unusable
Standard form 30 (rev. 11/2016)
Continuation sheet
Reference Number
Name of Offeror or Contractor
OPTIONAL FORM 336 (4-86))

Sponsored by GSA FAR (48 CFR) 53.110

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