Mobile-Friendly SCADA Dashboards: Monitoring the Plant From Your Phone

The on-call engineer is at home with family when the alarm notification arrives. A critical pump has tripped at a remote lift station 20 miles away. The engineer needs to see what is happening before driving to the site. Is the pump actually failed, or is this a false alarm from a faulty level sensor? What is the current wet well level? Are the standby pumps available?

Without mobile access, the engineer must call someone who is at a plant computer to read values over the phone. Or drive to the site blind. Both options waste time. Mobile-responsive SCADA dashboards solve this by putting real-time data in the engineer's pocket, accessible from any phone with a browser.

This guide covers why mobile dashboards matter, how to design them for industrial use, and the critical security consideration: never expose SCADA directly to the public internet.

Why Mobile Access Matters

Plant operations are not confined to the control room. Engineers, managers, and maintenance staff need access to data from wherever they are:

On-Call Response

When alarms occur after hours, on-call engineers need immediate visibility. Is this a critical alarm that requires immediate response, or a warning alarm that can wait until morning? Can the problem be resolved remotely, or is a site visit required? Mobile dashboards enable informed decision-making without requiring travel or phone calls.

Management Visibility

Plant managers and directors need visibility into operations without walking to the control room. Is production on track? Are there any active issues? What was last night's downtime? Mobile access provides situational awareness from anywhere—office, home, or travel.

Field Maintenance

Maintenance technicians in the field can check equipment status from their phone while standing in front of the machine. Is the VFD actually showing the fault code, or is this a mechanical issue? Can I verify the repair worked without walking back to the control panel?

Multi-Site Operations

Operators managing distributed sites (water utilities with 50 lift stations, building portfolios with scattered mechanical rooms) cannot be everywhere at once. Mobile dashboards allow one operator to monitor dozens of sites from a single device, prioritizing responses based on real-time conditions.

Business Continuity

When the control room is unavailable (power outage, building evacuation, network issue), mobile access provides a backup path to monitor critical operations. Not ideal for daily operations, but essential for continuity planning.

Mobile Dashboard Design Principles

Designing SCADA dashboards for mobile is different from designing for desktop. The screen is smaller. Touch interaction replaces mouse precision. Network connections may be slower. The design must adapt.

Status-First Information Architecture

Mobile screens should prioritize status information at the top. The user should see the most critical values without scrolling:

• Active alarms (with severity indicators)
• Equipment status (running/stopped/faulted)
• Key process values (tank levels, pressures, temperatures)

Secondary information (setpoints, configuration values, detailed diagnostics) should be available below the fold or on separate screens. The goal: immediate situational awareness at a glance.

Large Touch Targets

Fingers are less precise than mouse cursors. Interactive elements should meet minimum touch target sizes:

• Buttons: minimum 44x44 pixels (iOS) or 48x48 pixels (Android)
• Gauges and charts: sufficient spacing to avoid accidental touches
• Navigation links: clearly separated, easy to tap

Avoid cramming controls densely. The mobile screen is limited—prioritize the most frequently used controls and move advanced operations to separate screens.

Simplified Navigation

Mobile navigation should be shallower than desktop. Instead of complex multi-level drill-downs, use flat navigation with clear entry points:

• "All Sites" overview showing status summary
• Individual site screens with detailed equipment status
• Trend viewer for historical data
• Alarm list and acknowledgment

Avoid deep navigation hierarchies that require many taps to reach critical data. Each additional tap is friction.

Optimized for Slow Connections

Mobile networks may have latency or inconsistent bandwidth. Dashboards should:

• Load progressively—show critical data first, details later
• Handle connection drops gracefully—display last known values with "connection lost" indicator
• Auto-reconnect without requiring page refresh
• Minimize JavaScript and asset sizes for faster loading

The user may be checking from a location with poor cellular coverage. The dashboard should still load and be useful.

High Contrast for Visibility

Mobile screens are viewed in various lighting conditions—outdoor sunlight, dim control rooms, bright offices. Use high-contrast colors:

• Alarm states: bright red/green against neutral background
• Text: high contrast (not light gray on white)
• Status indicators: distinct colors with clear meaning (green=good, red=bad, amber=warning)

Avoid subtle color differences that are hard to distinguish on small screens or in bright light.

Responsive Layout

Use responsive design techniques that adapt to screen size:

• CSS Grid and Flexbox for adaptive layouts
• Media queries to adjust element sizes for mobile
• Touch-friendly controls (sliders, toggle buttons)
• Vertical stacking for content that appears side-by-side on desktop

The same dashboard should work on a phone, tablet, and desktop without requiring separate layouts.

Security: Never Expose SCADA to the Public Internet

Mobile access is convenient, but it introduces security risk if implemented incorrectly. The critical rule: never expose your SCADA system directly to the public internet.

The Wrong Way: Public-Facing SCADA

Opening your SCADA server to the internet is a security vulnerability:

• If you open port 80 or port 443 on your SCADA server to the world, anyone can attempt to connect.
• Automated bots scan the internet continuously for open ports and will find your SCADA server within hours.
• Brute-force login attempts will hammer your authentication system.
• Any vulnerability in your SCADA software becomes an attack surface for the entire internet.
• If authentication is weak or the software has a vulnerability, an attacker can access your control system remotely.

This is unacceptable for industrial systems. The risk is not theoretical—industrial facilities have been compromised via public-facing SCADA interfaces.

The Right Way: VPN or Zero Trust Remote Access

Secure mobile access requires that the SCADA server remain behind your firewall. Mobile users establish a secure tunnel to your network first, then access the SCADA interface:

• VPN (Virtual Private Network). Users install a VPN client on their mobile device. When they need to access SCADA, they connect to the VPN first. The VPN establishes an encrypted tunnel to your network. Once connected, the user's browser can reach the internal SCADA URL as if they were on the local network. The SCADA server never sees the public internet—only authenticated VPN connections.
• Zero Trust Network Access (ZTNA). Modern alternatives to VPNs, like Cloudflare Access or Tailscale, provide more granular access control. Users authenticate to the ZTNA service, which then proxies traffic to the internal SCADA server. No VPN client required—just a web browser. Access is logged per-user, per-resource.

Both approaches keep the SCADA server behind your firewall. Public internet traffic cannot reach it directly.

Additional Security Layers

Beyond VPN/ZTNA, implement these additional protections:

• Multi-factor authentication (MFA). Require a second factor (mobile app code, hardware token) in addition to password. This protects against compromised passwords.
• Least-privilege access. Mobile users should have read-only access by default. Enable write/control permissions only when explicitly needed. This reduces the risk of accidental or malicious changes from mobile devices.
• Session timeout. Automatically log out mobile users after a period of inactivity (15-30 minutes). Do not allow "remember me" indefinitely.
• Audit logging. Log all mobile access: who connected, when, from what IP, what data they viewed or changed. This logging is essential for security incident response.

Mobile-Friendly vs Native App: Which Approach?

Two approaches to mobile SCADA access: mobile-friendly web dashboards (responsive design) vs native mobile apps (iOS/Android applications).

Mobile-Friendly Web Dashboards

Mobile-friendly means the SCADA web interface uses responsive design to render correctly on mobile browsers. No app installation is required:

• Pros: No app installation, works on any device with a browser, no app store approval process, automatic updates (server-side), simpler deployment, cross-platform (iOS, Android, tablet) from a single codebase.
• Cons: Requires network connection to render (no offline access), browser features may be limited compared to native apps, push notifications require additional infrastructure.

For most SCADA applications, mobile-friendly web dashboards are sufficient and preferred. They are simpler to deploy and maintain.

Native Mobile Apps

Native apps are installed from the App Store or Google Play:

• Pros: Can work offline (cache data locally), native push notifications for alarms, better performance for complex visualizations, tighter integration with device features (biometric auth, background refresh).
• Cons: Require app installation and updates, app store approval process (weeks), separate iOS and Android codebases (higher development cost), users must keep app updated.

Native apps make sense when offline access is critical (e.g., checking equipment status in areas with no connectivity) or when push notifications for alarms are required.

The Hybrid Approach

Many SCADA platforms support both: a mobile-friendly web interface for general access and an optional native app for users who need push notifications or offline access. This provides flexibility without forcing a choice.

Making Legacy SCADA Systems Mobile-Accessible

Legacy SCADA systems with desktop-only clients present a challenge. The HMI is a Windows application that does not run on mobile devices. Two approaches:

Remote Desktop Gateway

Install a remote-access gateway that allows mobile devices to remote-desktop into a PC running the SCADA client:

• Parsec, Apache Guacamole, or Windows Remote Desktop Gateway allow browser-based remote desktop connections.
• The user connects via mobile browser, sees the desktop SCADA client, and interacts as if sitting at the PC.
• This works for short-term needs but has drawbacks: requires constant network connection, sluggish over mobile networks, poor experience on small screens.

Migration to Web-Based SCADA

The long-term solution: migrate to a modern SCADA platform with web-based dashboards:

• Ignition Perspective, Voltrus, VTScada all provide web-based HMI that works on mobile devices.
• Migration requires effort (recreating HMI screens, reconfiguring tags), but provides a better long-term solution.
• The result: a SCADA system that works on desktop and mobile from day one, with better security and simpler deployment.

For systems with 5+ years of life remaining, migration is usually justified by the operational benefits beyond just mobile access.

How Voltrus Implements Mobile Dashboards

Voltrus is built as a web application from the ground up. All dashboards are mobile-friendly by default.

Responsive Web Interface

Voltrus dashboards use responsive design that adapts to screen size. The same dashboard works on a desktop monitor, a tablet, and a mobile phone. Layouts automatically adjust—side-by-side gauges on desktop stack vertically on mobile.

Touch-Optimized Controls

All interactive elements meet minimum touch target sizes. Buttons, gauges, and navigation links are designed for touch interaction. No pin-zooming required—the interface is properly sized for mobile screens.

Progressive Loading

Voltrus dashboards load progressively. Critical status information appears first. Detailed data and trend charts load as data arrives. The interface remains responsive even on slow connections.

Secure by Design

Voltrus is designed to run behind your firewall. It does not require public internet exposure. For secure mobile access, pair Voltrus with Voltrus Remote for Zero Trust network access without VPN complexity.

Frequently Asked Questions

Why do SCADA dashboards need to be mobile-friendly?

On-call engineers and plant managers are not always at a desktop computer. When a critical alarm occurs at 3 AM, the operator needs to see what is happening from their phone before driving to the plant. Managers need to check production status while traveling. Mobile-responsive dashboards enable remote decision-making without requiring a laptop. The alternative—calling someone who is at a plant PC to read values over the phone—is slow and inefficient. Mobile dashboards put real-time data in the hands of whoever needs it, wherever they are.

What are the design principles for mobile SCADA dashboards?

Mobile dashboard design prioritizes status-first information. Show critical values (pump status, tank levels, active alarms) at the top without scrolling. Use large touch targets—buttons and gauges should be at least 44x44 pixels for reliable touch interaction. Simplify navigation—mobile screens should focus on single-site or single-equipment views rather than complex multi-site dashboards. Optimize for slow connections—mobile networks may have latency, so dashboards should load quickly and gracefully handle connection drops. Use high-contrast colors for visibility in various lighting conditions.

Is it safe to access SCADA systems from mobile devices?

Accessing SCADA from mobile devices is safe if done correctly. The critical rule: never expose SCADA directly to the public internet. Do not open port 80 or port 443 on your SCADA server to the world. Instead, require users to connect via VPN or Zero Trust remote access before reaching the SCADA interface. The mobile device establishes a secure tunnel to your network, then accesses the SCADA dashboard. This keeps the SCADA server behind your firewall while still allowing mobile access. For additional security, enforce multi-factor authentication and limit mobile access to read-only operations unless write access is explicitly required.

What is the difference between mobile-friendly and mobile app SCADA access?

Mobile-friendly means the SCADA web interface is responsive and renders correctly in mobile browsers. No app installation is required—the user opens a browser and navigates to the SCADA URL. Mobile app means a native iOS or Android application that must be installed from the app store. Mobile-friendly is simpler—no app updates, no app store approval process, works on any device with a browser. Mobile apps can provide better offline access and native notifications, but they add maintenance overhead and deployment complexity. For most SCADA applications, mobile-friendly web dashboards are sufficient.

How do I make legacy SCADA systems accessible from mobile?

Legacy SCADA systems with desktop-only clients cannot be made directly mobile-accessible without modernization. Two approaches: first, install a remote-access gateway like Parsec or Apache Guacamole that allows mobile devices to remote-desktop into a PC running the SCADA client. Second, migrate to a modern SCADA platform with web-based dashboards. The second approach is more work but provides a better long-term solution. For short-term needs, remote-desktop solutions work, but they require a constant network connection and can be sluggish over mobile networks.

Further Reading

• SCADA for Water and Wastewater: A System Integrator's Guide
• SCADA Historian: Data Logging and Trend Analysis That Actually Helps
• Ignition vs Node-RED vs Voltrus: 2026 SCADA Comparison