360_Camera_RFI_Sources_Sought.pdf

FOR INFORMATIONAL PURPOSES ONLY

REQUEST FOR INFORMATION/SOURCES SOUGHT

General Services Administration (GSA)

Office of Centralized Acquisition Services (OCAS) 360-Degree Camera for Construction Project Capture

November 10, 2026

GENERAL INFORMATION:

Document Type Request for Information/Sources Sought

Notice number: OCAS_RFI_360 Camera

Responses due: Tuesday December 08, 2026, 11:00am EST

Points of Contact:

Daniel Ortiz, Contract Specialist email: daniel.ortiz@gsa.gov

OBJECTIVE:

The General Services Administration (GSA) is conducting market research to identify commercially available, handheld 360-degree cameras capable of capturing visual construction-progress documentation for federal facilities. Captured media will be handled as Controlled Unclassified Information (CUI) and ingested into a FedRAMP-authorized IT system via removable media or a direct encrypted connection to that system.

SCOPE:

The Government seeks a capture device that operates independently of vendor cloud services and consumer mobile applications. The Government will consider two capture configurations, described in Section 2.3. The offline configuration transfers imagery by removable media. The managed connected configuration transfers imagery over a Government-controlled encrypted connection directly to the Government’s FedRAMP-authorized system.

The Government recognizes that few commercial products may meet every requirement today.

Vendors are encouraged to respond if a current product meets some of the requirements, or if the vendor could offer a government variant that meets them.

REQUIREMENTS

Section 2. Technical and Security Requirements

2.1. Physical and Capture Capabilities

A1. Form Factor Handheld, single-operator device capable of continuous spherical capture at normal walking speed. Fixed-mount cameras are outside the scope of this RFI.

A2. Format & Processing Produces spherical video in a standard, openly documented format, such as equirectangular MP4 with spherical video metadata, and still imagery in JPG format.

Files must be usable by the Government’s reality capture platform without proprietary desktop decoding or stitching software on Government-Furnished Equipment (GFE). Vendors should state whether stitching occurs in the camera and list native and exported file formats.

A3. Capture Specifications Vendors should state still image resolution, video resolution and frame rate, lens configuration, battery life, and operating temperature range.

2.2. Storage and Data Handling

B1. Removable Media In the offline configuration, all imagery must write directly to removable media (e.g., microSD). After the media is removed, onboard memory must hold no imagery, thumbnails, cache, or capture metadata. Vendors should describe how the Government can verify this. In the managed connected configuration, imagery may be held in encrypted onboard storage until transfer to the Government system completes, and must then be erased.

B2. Encryption at Rest FIPS 140-3 validated cryptographic protection for data at rest on the device and on removable media, or compatibility with self-encrypting removable media validated to FIPS 140-3. Vendors should provide the Cryptographic Module Validation Program (CMVP) certificate number for each module and state whether imagery is encrypted in the camera at the time of capture.

B3. Encryption in Transit In the managed connected configuration, imagery must be transmitted only to the Government’s FedRAMP-authorized system using FIPS 140-3 validated encryption, with no routing through vendor-operated servers.

2.3. Network, RF, and Device Controls

C1. Offline Configuration, Wireless Interfaces Removed or Permanently Disabled Wireless hardware for Wi-Fi, Bluetooth and Bluetooth Low Energy (BLE), cellular, and Near Field Communication (NFC) is removed or permanently disabled in manufacturer-controlled firmware. The device must operate with zero RF emissions. If wireless is disabled by firmware, the user must be unable to re-enable it through the user interface, settings files, or firmware rollback. Vendors should state which method they use and how the Government can verify it.

C2. Managed Connected Configuration Wireless interfaces may remain enabled if the device is enrolled in a Government mobile device management (MDM) or equivalent enterprise management tool, connects only to Government-approved networks, and transmits imagery directly to the Government’s FedRAMP-authorized system. Vendors should identify supported management platforms and describe how wireless functions are restricted when not in use.

C3. USB and Wired Interfaces USB ports must be limited to charging or to mass-storage transfer of imagery and firmware. Webcam, network adapter, and debug modes must be disabled or removed.

C4. Zero Cloud/Network Dependency Full standalone field operation without requiring a companion mobile app, device pairing, or vendor cloud account, and without transmitting telemetry or imagery to vendor-operated services.

C5. Offline Lifecycle Management Firmware updates must be deployable entirely offline via removable media without connecting to external networks. Firmware must be cryptographically signed by the manufacturer, and the device must reject unsigned firmware. Vendors should describe secure boot capability and provide a software bill of materials (SBOM) on request.

C6. Physical Integrity Surface design must support property serialization and tamper-evident sealing over battery, media, and USB ports.

2.4. Statutory and Supply Chain Compliance

D1. NDAA Section 889 Compliance with FY2019 NDAA Section 889(a)(1)(A)/(B); device must contain no components from covered telecommunications/video surveillance entities (e.g., Huawei, ZTE, Hytera, Hikvision, Dahua, or their subsidiaries and affiliates). Vendors should provide their Section 889 representations as recorded in SAM.gov.

D2. Trade Agreements Act (TAA) Products must be manufactured or substantially transformed in a TAA-designated country (documented at the SKU level). Vendors should identify the current country of origin for each SKU, provide supporting documentation such as a Declaration of Conformity or certificate of origin, and state whether they will notify the Government of changes in manufacturing location.

D3. Federal Listings Vendor and hardware must not appear on the FCC Covered List, Department of Commerce Entity List, System for Award Management (SAM) exclusions, or any Federal Acquisition Supply Chain Security Act (FASCSA) exclusion order. Vendors should provide the FCC ID for each SKU.

RFI RESPONSES:

Submit a written capability statement of no more than five pages in Word or PDF. Submit the compliance matrix and supporting documentation as separate attachments. These attachments are excluded from the five-page limit.

Company Information Company name, Unique Entity ID (UEI), CAGE code, business size and socioeconomic status under the NAICS code shown under General Information, and a point of contact.

Product Information Make, model, and SKU of each product, and the capture configuration in Section 2.3 that each product supports.

Compliance Matrix Use one row per Section 2 requirement for each SKU and capture configuration addressed. Include the requirement ID, SKU, configuration, status, explanation and evidence reference. Use Meets, Partially Meets, Planned, Does Not Meet or Not Applicable. Explain gaps and any Not Applicable entries. For planned capabilities, provide the estimated availability date.

Supporting Documentation FCC ID, CMVP certificate numbers, Declaration of Conformity, country-of-origin documentation, and Section 889 representations.

Government Variant Whether the vendor would offer a modified government variant to meet requirements the current product lacks, with estimated lead time and minimum order quantity.

Commercial Information Existing contract vehicles such as the GSA Multiple Award Schedule, estimated unit price range, delivery lead time, warranty, support, and planned end-of-life date.

GENERAL QUESTIONS AND FEEDBACK:

Email questions and responses to the points of contact listed under General Information by their respective deadlines. Use “Questions – [RFI number] – 360-Degree Camera” or “Response – [RFI number] – 360-Degree Camera” in the subject line.

Submit questions in a separate attachment. For each question, provide a sequential question number, the applicable section or requirement ID, and the question text. GSA may issue consolidated answers through an update to the notice.

NO OBLIGATION TO ISSUE REQUEST FOR QUOTE

GSA is issuing this RFI solely for market research and acquisition planning. This notice does not constitute a solicitation or commit the Government to issue one or make an award.

Responses are not offers and cannot form a binding contract. The Government will not reimburse response costs or return submissions. GSA may contact respondents for clarification.

PUBLIC RECORDS AND REQUESTS FOR CONFIDENTIALITY:

Do not submit classified information, CUI, or imagery of actual federal facilities. Clearly identify any proprietary material and segregate it where practicable.