How to Use SeQent Wi-Fi Messenger for Plant-Floor Communication

SeQent Wi-Fi Messenger is a mobile application for Android, iOS, and Wear OS smartwatches that delivers alarm notifications and enables two-way text communication over plant Wi-Fi. Unlike MOTOTRBO radio infrastructure or third-party apps, Wi-Fi Messenger is integrated directly into SeQent, requires no separate network or hardware, and provides a low-cost alerting channel for facilities with existing enterprise Wi-Fi.

What Is Wi-Fi Messenger and When to Use It

Wi-Fi Messenger is a mobile-native alternative to radios or PA systems. Operators and technicians install the app on their personal smartphones or the company’s deployed mobile devices. When an alarm triggers in SeQent, the app delivers a push notification with the alarm details. Users can acknowledge alarms, send two-way text replies (“Fix complete,” “En route,” “Need assistance”), and track response status — all from their phone.

When to use Wi-Fi Messenger:

• Facilities with strong enterprise Wi-Fi coverage (typical in modern plants)
• Lower-cost alternative to MOTOTRBO or other radio infrastructure
• Remote or roaming technicians who move between areas frequently
• Facilities with high mobile device adoption among field teams
• Integration with existing helpdesk or ticketing systems

When NOT to use (use MOTOTRBO or PA instead):

• High-noise production floors where audible notification (radio beep or PA voice) is required
• Facilities with poor Wi-Fi coverage on the plant floor
• Safety-critical, time-critical alarms where sub-second delivery is mandatory (Wi-Fi latency is typically 2-5 seconds)

Prerequisites

Before deployment, ensure:

• Enterprise Wi-Fi coverage across the facility (minimum signal strength -70 dBm at operator work areas)
• SignalSwift server with the Wi-Fi Messenger feature enabled
• iOS 14+, Android 9+, or Wear OS 3+ on user devices
• Mobile device management (MDM) system optional but recommended for large deployments (Intune, MobileIron, Samsung Knox)
• Users have Wi-Fi network access and SeQent login credentials

Installation and Configuration

1. Enable Wi-Fi Messenger on the SignalSwift Server

On the SignalSwift server, enable Wi-Fi Messenger in the admin console: Settings > Notification Channels > Enable Wi-Fi Messenger. Configure:

• Push notification service (Apple APNs for iOS, Google Firebase for Android)
• Notification sound and vibration defaults
• Message retention (how long messages stay in the app’s local cache)

2. Configure Admin Tool for Operators

In the SeQent admin console, go to Users > Mobile > Configure Wi-Fi Messenger Users. Create a user group for field operators. Assign permissions:

• View alarms for assigned areas
• Acknowledge alarms
• Send/receive text replies
• View response status

3. Deploy Clients to Devices

Wi-Fi Messenger is deployed to users’ devices through your mobile device management (MDM). On first launch, they enter their SeQent username and password. The app automatically downloads their assigned alarms, permissions, and notification rules.

For bulk deployments (50+ devices), use your MDM system to auto-deploy the app and pre-configure SeQent authentication.

4. Connect to SCADA Data Source

In SeQent, go to Integrations > Data Sources and select your SCADA system (FactoryTalk, AVEVA, CIMPLICITY, OPC UA). Configure which alarms are eligible for Wi-Fi Messenger delivery. Most deployments exclude low-priority informational alarms and only route High and Critical severity to the mobile app.

5. Test End-to-End

Have a mobile user install the app and log in. From the SeQent console, trigger a test alarm. Verify:

• Push notification arrives on the user’s phone within 3-5 seconds
• Alarm details are readable on the mobile screen
• User can acknowledge the alarm; status updates immediately in SeQent
• User can send a reply message (“In progress”, “Fixed”, “Need help”); message appears in the alarm history

Wi-Fi Network Requirements

Ensure your Wi-Fi network is sized and configured for manufacturing environments:

• Coverage: Minimum -70 dBm signal strength at all plant-floor work areas; outdoor areas may need -65 dBm or better
• Capacity: Support all field users simultaneously; typical consumption is 500 KB per day per active user
• Reliability: Implement mesh Wi-Fi or multiple access points to avoid dead zones and hand-off issues

Combining Wi-Fi Messenger with Other Notification Channels

A typical multi-channel strategy:

• Critical alarms → MOTOTRBO radio (immediate audible alert) + Wi-Fi Messenger (backup text notification)
• High-priority operational → Wi-Fi Messenger + email to supervisor
• Medium-priority → Wi-Fi Messenger only
• Informational → Wi-Fi Messenger and logged (no active notification)

This approach ensures critical alarms reach operators via the fastest, most reliable channel (radio), while secondary alarms use lower-cost infrastructure (Wi-Fi).

Troubleshooting

Push Notifications Not Arriving

Verify user is connected to Wi-Fi and has internet connectivity. Confirm the user’s device has enabled push notifications for the SeQent app (in iOS Settings or Android Settings > Apps > SeQent > Notifications). Check SeQent gateway logs for push notification service errors. If iOS: verify APNs certificate is current and not expired. If Android: verify Firebase connectivity from gateway to Google servers.

Slow Notification Delivery (>10 Seconds)

Check Wi-Fi signal strength on user’s device (in Wi-Fi settings, look for signal bars). If signal is weak (-80 dBm or lower), users may experience high latency. Recommend users move to areas with stronger signal, or add Wi-Fi access points in weak-signal areas. If Wi-Fi signal is good, check gateway CPU load; high load may indicate notifications are queued waiting for processing.

Messages Not Sending (Two-Way Text)

Verify the user has permission to send replies (checked in Users > Wi-Fi Messenger Permissions). Confirm Wi-Fi and internet connectivity. If sending fails, check SignalSwift server logs for errors. For large reply volumes, increase the notification service message queue in the admin console.

App Crashes on Login

Update SignalSwift server to the latest version; old versions may have authentication bugs. Update the mobile app to the latest version through your MDM. If crashes persist, clear the app’s cache: iOS (Settings > General > iPhone Storage > SeQent > Offload App, then reinstall); Android (Settings > Apps > SeQent > Storage > Clear Cache).

Wi-Fi Messenger is the lowest-friction way to scale alarm notification to all field personnel without dedicated radio infrastructure. For deployments that need to span Wi-Fi plus cellular coverage, see the Mobile Data section below.

Mobile Data and External Network Connectivity

For sites with patchy Wi-Fi or for technicians who roam beyond plant coverage, two architectures provide cellular fallback:

• Cloud-hosted SignalSwift server reachable over the public internet. Mobile devices connect over cellular or Wi-Fi without needing direct line-of-sight to the plant network.
• External firewall access exposes the on-premises SignalSwift server through a controlled NAT or reverse proxy so cellular-connected clients can reach it.

Push notifications (APNs for iOS, FCM for Android) require the user device to have internet connectivity at the moment of notification. If the device is on a private plant Wi-Fi without internet, push will not deliver; in that case, configure SignalSwift to maintain a direct WebSocket connection to the client (preferred for fully on-premises deployments).