Amendment 0001 - Questions and Answers.docx

RFIFogTesterInstrumentImage-AnalysisSoftwareJUN2026 Questions and Answers

1. Interface simulation availability. Will the Python simulation of the FogTester TCP interface referenced under Government Furnished Property be made available at the time of any future RFP release, and will it include the TCP interface specification (port assignments, message/command structure, and data formats) needed to develop and test the improved analysis application?

Full documentation, access to current software coding, will be made available to contractor upon contract award.

2. Image characteristics. Can the Government provide the format, resolution, bit depth, and approximate quantity of video stills acquired per test, per camera, so offerors can appropriately scope image-processing and performance considerations?

Images are currently saved in the .PNG format at resolution of 2590x1942 pixels, 16bit depth. Depending upon testing requirements as frequently as 2 frames/sec per camera or as few as 0.2 frame/sec per camera are acquired. Typical 60 seconds-long test duration will acquire 120 frames per camera.

3. Existing algorithm documentation. Is the current BarTarget contrast-ratio computation methodology and region-of-interest selection approach documented, and would that documentation be available as reference material to ensure continuity of results between the legacy and improved applications?

Yes. Full documentation to date will be provided to the contractor upon contract award.

4. Calibration and pass/fail criteria. Will the Haze Standard calibration values and designated pass/fail thresholds be Government-furnished, or is the contractor expected to derive them from the calibration test data as part of the calibration sub-program?

The Haze Standard calibration values are determined via test operation in a separate procedure. The Pass/Fail thresholds will be user inputted as these thresholds may change as anti-fog performance by the eyewear industry improves over time.

5. ASD STIG applicability. Given that the delivered software is categorized as Non-Critical, Untethered, and intended for a disconnected standalone laboratory system, does the Government anticipate assessment against the full DISA Application Security and Development STIG, or a tailored checklist limited to the requirements applicable to a non-networked desktop application?

From our IT Security staff “Short answer is yes, they should use the STIG.

The below statement is from the STIG itself. It states that any Enterprise Application(EA) should use the STIG. An EA is defined as an application or software used by the organization to assist in the execution of the organization’s missions or meeting organizational goals or tasks so they should use the STIG. While I expect the STIG to be applied, the majority of them would be “Not Applicable” to this software. The ASD checklist is there to ensure that government applications are being coded and designed as securely as possible, many of those checks apply only to server or web applications and desktop applications end up being NA but that just means the process should not be a huge LoE.”