Water and Wastewater Field Communication: A Pump-Station Route Test

Prepared by the ChatField Editorial Team. Evidence reviewed August 18, 2026.

Drinking-water and wastewater teams may move among treatment facilities, reservoirs, wells, pump stations, lift stations, tanks, collection-system assets and remote access roads. Cellular coverage can vary, yet field personnel still need a clear method for selected non-emergency coordination.

A phone-paired local LoRa mesh layer may supplement an approved utility plan for equipped users after a site-specific test. It is not SCADA, operational technology remote access, process control, water-quality monitoring, gas detection, an employee alarm or a replacement for public emergency services.

Short answer

Begin with the utility's emergency response plan, operations procedures, IT/OT security rules, confined-space program and field safety requirements. Map safe routes and define a narrow set of permitted messages. Test the exact phones, J25 terminals, regional configuration, checkpoints, power and fallbacks without connecting the pilot to control systems.

Define the utility workflow

Routine inspection, preventive maintenance, leak or overflow investigation, meter work, vegetation control, sampling support, storm preparation and contractor access create different roles and authorities. Do not treat one pump-station test as proof for every facility.

List the system owner, operator, field crews, contractors, laboratory, control room, emergency contacts and public-information roles. The local group should follow the approved chain of command rather than create a parallel incident structure.

The ChatField off-grid communication overview defines the local equipped-team role.

Keep field coordination separate from SCADA and OT

Water and wastewater utilities use information technology and operational technology for business and process functions. CISA and EPA warn that compromised OT can affect essential services and recommend reducing internet exposure, inventorying assets, protecting remote access and exercising incident response.

J25 does not read sensors, change pump or valve states, access programmable controllers or verify process conditions. Do not bridge a pilot phone or terminal into the utility's OT network without the utility's formal architecture, cybersecurity and authorization process.

A field observation remains an observation until the responsible utility role verifies and acts on it.

Preserve emergency communication

EPA emergency-response templates distinguish internal communication, external response partners, critical customers, communication equipment inventory, public notification and media outreach. A local mesh group can occupy only the approved internal role assigned by the utility.

Do not delay 911, emergency operations, employee alarms, public notification, mutual aid or regulator contact while waiting for a J25 message. Define the external fallback at every test checkpoint.

The ChatField technology page explains local architecture, not emergency authority.

Draw the complete J25 path

The smartphone application is the user interface. Bluetooth connects the phone to the carried J25 terminal. The configured terminal carries supported PTT, text, image or location traffic through the local LoRa mesh to another equipped terminal and paired phone.

A phone alone does not transmit LoRa, and the terminal is not held like a conventional walkie-talkie. Test phone permissions, pairing, terminal power, group configuration and recipient readiness separately.

Use the ChatField How It Works page to draw the troubleshooting path.

Map facilities and safe checkpoints

Select representative safe points at the administration or operations building, treatment-site gate, reservoir approach, well site, pump station, lift station exterior, remote valve or meter route, maintenance yard and assembly point. Mark restricted, flooded, traffic, chemical and confined-space areas.

Do not enter a permit-required confined space, chlorine area, energized enclosure, excavation, contaminated zone or unsafe road for a radio test. Qualified personnel determine access and required equipment.

Record terrain, concrete, steel, below-grade structures, vegetation, vehicles, device height and carrying position.

Define permitted message classes

Examples may include arrived at exterior checkpoint, routine inspection complete, supervisor requested, access road blocked, approved photo available, part required and returning to base. Use utility terminology and acknowledgement rules.

Do not send switching, dosing, process-control, confined-space entry, public-warning or emergency instructions as casual pilot traffic. Label every exercise message clearly.

Use range evidence correctly

Current J25 evidence includes 5 km in urban-obstructed testing and up to 10 km in ideal open terrain. Concrete tanks, below-grade assets, buildings, terrain, vegetation and vehicles can produce different results.

Test stable, marginal and failed checkpoints in both directions. Do not convert the open-terrain figure into a guarantee across a service area or underground structure.

Review the J25 specifications page before setting acceptance criteria.

Test direct and supported relay paths

Establish the direct path from the operations point to each safe route zone. For current J25 planning, evaluate no more than two participating relay nodes where the tested layout and configuration permit.

Place a participating node only in an approved, accessible location with a responsible owner, power plan, protection and retrieval procedure. Test movement or power loss and confirm the fallback.

Never place a terminal in a restricted space, process enclosure or hazardous location to improve coverage.

Address lone and remote work limits

NIOSH notes that lone workers may face greater difficulty when unexpected conditions occur. The utility must decide which tasks may be performed alone, required check-in intervals, escalation and the response to a missed contact.

J25 is not represented as an automatic man-down detector or guaranteed lone-worker monitor. A worker who cannot operate the phone may not send a message.

Exercise a missed check-in without sending unqualified personnel into a hazard.

Protect confined-space procedures

OSHA's permit-required confined-space standard addresses evaluation, permits, atmospheric testing, attendants, communication, rescue and other controls where applicable. A local message does not replace the required communication method or authorize entry.

Keep ordinary commercial phones and terminals outside any location where the exact equipment is not approved. The entry supervisor and written program determine equipment and communication.

Protect drivers and field attention

No person should read, type or troubleshoot a phone while driving, entering traffic, working near excavation, climbing, handling chemicals or performing another safety-critical task. Assign a passenger or require a safe stop.

NIOSH advises workers who drive to avoid phone use and pull over safely before texting or calling. PTT can also create cognitive distraction.

The current J25 product page presents a carried phone-paired terminal, not a hands-free safety system.

Test noise, PPE and wet conditions

Pumps, blowers, generators, traffic, wind and hearing protection can reduce speech understanding. Test supported PTT with the exact approved PPE and safe audio arrangement. Keep technical delivery and correct human understanding as separate results.

Do not remove hearing protection or expose equipment to water, chemicals or contamination beyond its documented evidence. Clean and handle devices under the utility's hygiene and contamination-control process.

Exercise power and storm disruption

Count phone and terminal batteries separately. Reproduce the expected shift message mix and define approved charging, spares and handoff. A short demonstration does not prove storm-duration endurance.

Use tabletop and controlled exercises for a blocked access road, lost power, unavailable checkpoint, failed terminal or loss of cellular service. Do not conduct product testing during an actual hazardous condition.

Measure procurement results

Record delivery, delay, acknowledgement, wrong recipient, speech understanding, failed checkpoint, battery state, user error, fallback and recovery. A pass applies only to the tested users, phones, versions, regional hardware, route and operating procedure.

Retest after facility construction, vegetation changes, route changes, OT policy changes, phone or software updates and revised emergency plans.

Contact ChatField procurement support with safe facility zones, roles, phone models, message classes and destination market to scope a bounded utility pilot.

Water-utility pilot checklist

• Utility chain of command and emergency response plan
• SCADA, OT, alarms and public notification kept separate
• Exact phone-to-terminal path
• Safe facility and route checkpoints
• Restricted, confined, chemical and traffic areas marked
• Approved routine message classes
• Direct and supported relay tests
• Lone-work and missed-contact limits
• Driver, PPE, noise and attention controls
• Phone and terminal shift power
• External fallback and recovery exercise
• Versioned evidence and retest triggers

Sources reviewed

• EPA: risk and crisis communication for water utilities
• EPA: Wastewater Utility Emergency Response Plan Template and Instructions
• CISA, EPA and FBI: cybersecurity actions for water systems
• OSHA 1910.146: permit-required confined spaces
• NIOSH: distracted driving at work
• NIOSH: lone-worker communication and risk controls

EPA, CISA, FBI, OSHA and NIOSH do not endorse ChatField or J25. Their material defines utility, cybersecurity and workplace-safety context, not J25 route performance or approval for OT, confined-space or emergency use.