Figure 1. StormSensor Scutes™ deployed at priority outfalls across Jersey City.

Pilot Study Summary

StormSensor originally installed a pilot network of Scute sensors in Jersey City in Fall 2018 with the goal of detecting CSO events in real-time. Prior to installing the StormSensor network, Jersey City was completely reliant on EPA SWMM model estimates for reporting CSO frequency and volume. Twenty additional StormSensor Scutes™ were installed in November 2019 as an expansion of an existing CSO detection pilot project.

Pilot Study Summary

StormSensor originally installed a pilot network of Scute sensors in Jersey City in Fall 2018 with the goal of detecting CSO events in real-time. Prior to installing the StormSensor network, Jersey City was completely reliant on EPA SWMM model estimates for reporting CSO frequency and volume. Twenty additional StormSensor Scutes™ were installed in November 2019 as an expansion of an existing CSO detection pilot project.

Figure 1. StormSensor Scutes™ deployed at priority outfalls across Jersey City.

Figure 2. StormSensor data showing the first four CSO events detected during the first phase of the expanded monitoring project.

Continued...

As the City moves forward with its CSO Long Term Control Plan (LTCP) and anticipates spending $700 million dollars on CSO and flood reduction, validation of the current model is warranted. In the first month of operation with the expanded StormSensor network, four CSOs were successfully identified. StormSensor transmits data from the sewer system to the cloud every five minutes, allowing for detection of CSO events within ten minutes of beginning. Identifying CSO events in real time allows the City to be more responsive in terms of warning the public in a timely manner and prioritize maintenance over the course of the event.

Figure 2. StormSensor data showing the first four CSO events detected during the first phase of the expanded monitoring project.

Continued...

As the City moves forward with its CSO Long Term Control Plan (LTCP) and anticipates spending $700 million dollars on CSO and flood reduction, validation of the current model is warranted. In the first month of operation with the expanded StormSensor network, four CSOs were successfully identified. StormSensor transmits data from the sewer system to the cloud every five minutes, allowing for detection of CSO events within ten minutes of beginning. Identifying CSO events in real time allows the City to be more responsive in terms of warning the public in a timely manner and prioritize maintenance over the course of the event.

Figure 3. StormSensor’s summary charts present basic statistics for each monitoring point. In this case, we quantify the impact of the first four CSO events detected during Phase One of the expanded monitoring project.

Management Impacts

Once a CSO event has ended, quantifying the volume of each CSO event aids in compliance reporting and is vital for planning and citing control efforts. The StormSensor Summary tool was used to quickly calculate the volume of each event.

Jersey City plans to use StormSensor data for (1) improving compliance reporting, (2) validating EPA SWMM model predictions, (3) prioritizing retrofits as part of LTCP, and (4) reducing LTCP implementation costs. As the LTCP progresses, Jersey City will leverage the StormSensor network to quantify the success of those efforts.

Management Impacts

Once a CSO event has ended, quantifying the volume of each CSO event aids in compliance reporting and is vital for planning and citing control efforts. The StormSensor Summary tool was used to quickly calculate the volume of each event.

Jersey City plans to use StormSensor data for (1) improving compliance reporting, (2) validating EPA SWMM model predictions, (3) prioritizing retrofits as part of LTCP, and (4) reducing LTCP implementation costs. As the LTCP progresses, Jersey City will leverage the StormSensor network to quantify the success of those efforts.

Figure 3. StormSensor’s summary charts present basic statistics for each monitoring point. In this case, we quantify the impact of the first four CSO events detected during Phase One of the expanded monitoring project.

StormSensor transmits data from the sewer system to the cloud every five minutes, allowing for detection of CSO events within ten minutes of beginning.

Contact Us

At StormSensor, we believe that good decisions are driven by good data. As a team, we're bringing to life solutions that streamline insights for smarter decisions. If you're involved with water infrastructure, then send us a note. Tell us your challenges and learn more about how we're leveraging new technology to solve old problems.

Green InfrastructureIllicit Discharge DetectionCombined Sewer OverflowsStormwater Model ValidationUrban flooding managementCoastal management and sea-level riseCommercial stormwater managementOther