On March 3–4, 2026, Visn AI participated as a featured speaker at the Puerto Rico Water & Environment Association (PRWEA) Annual Conference & Technical Exhibition 2026, held at the Puerto Rico Convention Center. The conference brought together 48 expert speakers, making it one of the leading professional gatherings in the water and environment sector in the region.

Hector Monroy, Founder & Partner of Visn AI, delivered a presentation on how Municipal Separate Storm Sewer System (MS4) permit data can be leveraged to improve planning and operational performance.

The Data Is Already There

Monroy opened by recognizing that many MS4 programs already collect substantial operational data; inspections, maintenance records, complaints, rainfall measurements, and field activities. Each individual record may appear routine in isolation. But analyzed over time, that same data can reveal something far more valuable: patterns of accumulation, locations sensitive to rainfall, and areas where system performance repeatedly degrades.

Despite this, day-to-day planning in many programs remains reactive; driven by complaints or specific incidents, even when historical records already contain consistent, identifiable patterns between rainfall and operational demand.

The Right Question to Ask

Monroy was clear that the challenge is not about technology, nor about a lack of data. What is often missing is the ability to turn existing data into actionable operational insights. He framed it as a practical operational question:

At what level of rainfall does the system stop behaving routinely and begin to generate operational pressure? And in which areas do that shift occur first?

In many MS4 programs, these signals already exist within operational and environmental records. They are simply not visible when events are viewed in isolation. They only emerge when inspections, maintenance logs, rainfall data, and field responses are analyzed together over time.

From Reporting to Anticipation

Operational value, Monroy argued, emerges when data is analyzed collectively, not in silos. The goal extends beyond compliance reporting. It is about identifying patterns, improving planning, and anticipating where attention will likely be needed before pressure builds.

A key point raised during the discussion was that many organizations already collect significant operational and compliance data yet still use it primarily for reporting rather than for forecasting operational conditions. The opportunity is not necessarily collecting more data; it is learning how to analyze what already exists to support forward-looking decisions.

“The real question is whether the organization has a method to translate rainfall into operational behavior, identifying the precipitation threshold at which urgent work orders begin to rise and anticipating which areas of the system will come under pressure first,” Monroy concluded.