RB Pro Breath Test VOC Mitigation

Tomorrow, December 4th, 2024, SCRAM Systems will release an enhancement to the Ambient VOC Detected test results.

When an excess of Volatile Organic Compounds (VOCs) – usually picked up from the device’s surroundings – is detected in the SCRAM Remote Breath Pro (RB Pro) device’s breath testing flow path, the RB Pro device prevents breath tests from being performed, and an Ambient VOC Detected alert is displayed in SCRAMNET. With this enhancement, SCRAMNET will automatically initiate flow path checks every 10 minutes for up to two hours until the flow path is clear and the client may test.

Here is the complete process:

1. The device will generate a descending arpeggio (“uh-oh”) sound.
2. The device’s screen will display, “REMOVE STRAW AND PLACE UNIT IN A WELL VENTILATED AREA,” followed by, “PLEASE WAIT with a 30-second count down.”

3. The device will repeat this process automatically for two minutes. If the VOC does not clear, the device will end the current breath test process, and the screen will display “MONITORING …” At this time, an “Ambient VOC Detected” alert will be generated in SCRAMNET.

Advise the client to take the following steps to help clear the device’s breath-testing flow path:

4. Remove the breath tube from the device, wash it with dish soap, rinse it with water, and then thoroughly dry the breath tube before using it again. Moisture in the breath tube could impact test results.
5. Relocate the RB Pro device to an area of fresh air that is free of chemicals (like air fresheners) and cleaning agents (including freshly cleaned countertops).
6. Remove the device from its carrying case and place it on its side on a tabletop or other clean surface away from contaminants, with the vent on the bottom and the breath tube port unobstructed.

Once an Ambient VOC Detected alert has been generated:

7. SCRAMNET will record a “Mitigation Started” entry in the event’s Action History section of the Alert Management Console.
8. SCRAMNET will automatically initiate flow path checks (Air Blank Tests) every 10 minutes for two hours. These checks will also be recorded in the event’s Action History.
9. SCRAMNET will automatically send the device an On-Demand test once environmental ethanol (Ambient VOC) is no longer detected. The Action History will record this as a “Mitigation Stopped: On Demand Test Sent” entry.

10. If environmental ethanol is still detected after two hours of flow path checks, SCRAMNET will stop requesting Air Blank checks and record a “Mitigation Stopped – Ambient VOC Persisted” entry in the Action History for the event.

If the Ambient VOC Mitigation process is interrupted by another breath test (scheduled, on-demand, or client-initiated), this event’s mitigation process is discontinued. A new mitigation process will begin if the latest test request exceeds the Ambient VOC threshold. If, however, the level of VOCs detected in the flow path drops below the detection threshold but is still above 0.000, then the RB Pro device will allow a breath test. So, it is possible that a client’s breath test result that interrupts the Ambient VOC Mitigation process may register a very low-level alcohol detection. SCRAM Systems advises against violating clients for this very low-level alcohol detection, as the alcohol detected in the breath test could be from residual environmental VOCs still in the flow path and/or fuel cell.

Important Notes: Typically, the low-level alcohol detection we see following a lengthy VOC-clearing scenario is well below the monitoring program’s Lower Level of Detection (LLOD), which is the threshold at which alerts are generated in SCRAMNET. Most monitoring programs’ LLOD threshold is 0.020 BrAC. Based on SCRAM Systems internal testing, residual VOCs present in the device will not influence a BrAC value above 0.020. For customers with the LLOD threshold set below 0.020, the confirmation process of initial and confirmation tests being both positive and not drastically different is still required. If the LLOD threshold is set very low (0.005, e.g.), then the potential for a low-level VOC contaminant to influence both the initial and confirmation tests is increased. For these caseloads, SCRAM Systems recommends that customers allow the automated Ambient VOC Mitigation process to be completed uninterrupted.