Technical SCADA FAQs for Systems Integrators and Controls Engineers
Evaluating cellular SCADA for a client? These answers cover what an engineering review needs to settle: which PLCs and protocols SimpliScada talks to, how connectivity challenges are handled, how HMI screens get built, and how remote access stays secure with no VPN and no local server.
For the architecture behind it, start with how Modern SCADA works without a server. For side-by-side detail, see SimpliScada vs. VTScada and SimpliScada vs. Ignition.
Which PLCs and industrial protocols does SimpliScada support?
–SimpliScada works with any PLC that has an Ethernet port and uses a supported protocol: Modbus TCP, Modbus RTU over TCP, DNP3, EtherNet/IP, OPC UA, Emerson+, and Profinet. If a protocol isn’t supported yet, SimpliScada can build a driver for it. The SimpliLink Hub talks directly to the controller, with no PLC programming and no middleware such as Kepware or Autosol.
Controllers without an Ethernet port still connect. A PLC that communicates over RS-232 or RS-485 links to the hub through a third-party serial-to-Ethernet gateway.
The hub mounts on a DIN rail in the control panel. It connects to the PLC through its Ethernet port, either directly or through the site’s existing network. The PLC and its tags are then configured in the SimpliScada management portal, and data starts reading as soon as at least one tag is set up. For Modbus work, SimpliScada also publishes a free Modbus address calculator for IDEC FC6A controllers.
Each hub logs data at intervals as short as one second, and capacity runs up to 900 PLCs and 15,000 tags per hub depending on the model (see the hub comparison below). On larger systems, a single Hub+ can connect to a master PLC that already aggregates data from many field sites.
Full hardware specs are on the SimpliLink Hub product page.
Can SimpliScada run alongside an existing SCADA system like VTScada or Ignition?
+Yes, as long as the PLC or controller can communicate with more than one device. SimpliScada sits on top of a utility’s current system rather than replacing it, so adding it doesn’t mean an overhaul, a cutover, or a vendor conflict. The PLCs keep running the same control logic, and the existing SCADA keeps doing its job. On older controllers, check how many simultaneous connections the PLC supports before adding SimpliScada alongside the existing master.
Integrators typically use it in three ways:
Adding reach to an installed system: cellular monitoring, mobile alarms, and remote access for sites the existing system never reached because running radio or fiber didn’t pencil out.
Unifying separate systems: one dashboard for a utility running several SCADA platforms, VPNs, or vendors across different sites.
Migrating in phases: moving a system site by site instead of in a single cutover.
SimpliScada scales from a single well or lift station at a small rural system to large, complex municipal systems. A single SimpliLink Hub+ handles up to 900 PLCs and 15,000 tags, and every site reports to the same dashboard. That range lets integrators run it alongside an existing platform on one project and as the full SCADA system on the next. In a parallel setup, agree early on which system owns setpoint and control writes, so operators always know where a change came from.
For where each one fits, see SimpliScada vs. Ignition.
How does SimpliScada store and report historical data?
+The SimpliLink Hub polls data from the controller, keeps a 30-day local history, and backs that history up to SimpliScada’s cloud storage. The long-term record lives on the platform, not on a server at the plant. There’s no historian server, database, or backup routine for the utility or the integrator to maintain. The hub logs tag data at intervals as short as one second, and operators reach the history from a browser or the mobile app. If the connection to the platform drops while the hub and controller are still communicating, the hub keeps logging locally and backs those reads up automatically when the connection returns.
Trends use dynamic graphs with a live mode, and operators can zoom into any historical period to see what changed and when. Reports are built in a drag-and-drop report builder, and operators can walk through site reports from a phone in the field. For water and wastewater systems, values such as turbidity, residual chlorine, and flow are captured automatically and compiled into audit-ready compliance reports, replacing hand-kept logs. Alarm acknowledgments made from a phone are logged automatically too, so there’s a record of who responded and when.
Because the long-term record doesn’t depend on a server in the back room, there’s no server refresh to budget for and no historian to rebuild when hardware fails. For more on how that architecture works, see how Modern SCADA runs without a server.
What cellular networks does SimpliScada use, and what if a site has weak coverage?
+The SimpliLink Hub uses a multi-carrier SIM. On power-up, it connects over 4G LTE using the best cellular network available at the site. Sites can also connect through a preferred ISP or a satellite service such as Starlink, using the hub’s Ethernet connection. On cellular, that means no new network drop, no static IP, and no port forwarding at the site.
Checking coverage is part of commissioning:
Open the hub’s local web interface and go to the Cell tab to confirm the hub is connected and read its signal quality.
Aim for signal quality above 50 percent. Below that, add an external antenna mounted in the open, outside any metal building or enclosure.
If the hub won’t connect, confirm the SIM card is detected and the correct APN is set, then power cycle the hub.
Once the site is live, watch the hub’s cellular status and RSSI remotely, so a fading signal shows up before it becomes an outage.
SimpliScada’s industrial 4G LTE antenna is a 5 dBi omnidirectional, weatherproof unit covering 698 to 960 MHz, 1710 to 2170 MHz, and 2300 to 2700 MHz. It mounts on a wall or through a hole, with a standard 10-foot cable or a custom length. Full steps are in the SimpliLink Hub setup instructions.
What happens when a site loses its cellular connection?
+The process keeps running, and so does data logging. Control logic lives in the PLC, so pumps, valves, and treatment follow their setpoints whether or not the hub is connected. The hub keeps a 30-day local history, so readings taken during the outage are backed up automatically once the link returns. What pauses is remote visibility and remote control.
What keeps running: the PLC program, field instruments, every pump, valve, and treatment step tied to local logic, and data collection from the PLC, with up to 30 days stored on the hub.
What pauses: live screens, remote commands, and phone alerts from that site, because none of them can reach the platform until cellular or ISP service is restored.
What happens when service returns: the hub reconnects on its own and backs up the readings it logged during the outage, with no site visit or manual restart.
The hub is built to ride through the conditions behind most field outages. A hardware watchdog restarts it if it hangs. A super capacitor gives a 20-second backup against brownouts and voltage spikes and protects against reversed polarity. It accepts a 9 to 36 VDC supply and runs from -25°C to 60°C.
Because the hub reports live cellular and device status, an integrator can tell from the dashboard whether a site is actually offline or just reporting a bad value. The design rule is the same as on any remote telemetry job: anything that must happen during an outage, such as a high-level pump shutdown, belongs in the PLC program. The operator-side version of this answer is in the SCADA FAQs for water and wastewater operators.
How fast does SimpliScada update, and is it fast enough for control?
+Data updates at a poll rate you set, but control commands don’t wait for it. A setpoint change or pump start is sent immediately, and SimpliScada confirms back to the operator that the PLC carried it out. Fast control loops stay in the PLC, the same as in any SCADA architecture.
The poll rate is configurable, down to intervals as short as one second. If it’s set to 30 seconds, data updates automatically every 30 seconds. Matching the poll rate to the process keeps cellular data usage down without slowing control. When an operator opens a site, Live Mode switches to a much faster refresh for as long as they’re watching.
Every reading and every command routes through the SimpliScada platform, even between two assets at the same plant. For most water and wastewater systems that’s an advantage. A utility with tanks, wells, and lift stations spread across miles gets them on one dashboard without building radio links, backhaul, or VPNs to tie them together. The more locations a system covers, the bigger that advantage gets.
Logic that needs assets to exchange data very quickly, such as an interlock between a pump and a valve, belongs in the PLC, the same as on any SCADA platform.
For a side-by-side look against a traditional on-premise architecture, see SimpliScada vs. VTScada.
How long does a typical SimpliScada deployment take, and what does the integrator do on site?
+Installing the SimpliLink Hub is quick, and a typical small system is deployed within a few days of SimpliScada receiving the integrator’s HMI and tag documentation. Larger systems take longer, because HMI development and tag integration scale with the size of the system. There’s no server to procure, no radio path to engineer, and no PLC programming, so the work comes down to hardware installation and configuration.
The integrator sends SimpliScada the HMI and tag documentation for the system, which is what sets the deployment timeline.
The site is created in the SimpliScada management portal and assigned to the hub’s serial number. The PLC and its tags can be configured ahead of time or on site. This is also the point to confirm the hub can read the controller directly and that the site has usable cellular coverage.
The hub mounts on a DIN rail inside a building or a weatherproof enclosure that stays between -25°C and 60°C, and runs on a 9 to 36 VDC supply. From a laptop connected to the hub, the integrator confirms the cellular connection and signal quality, adding an external antenna if signal is below 50 percent. The hub’s network settings are then matched to the existing network. On a new network, the PLC and other devices get addresses in the 10.0.0.4 to 10.0.0.254 range with the hub as the gateway. The PLC or site network plugs into the hub’s top Ethernet port, and the portal confirms the hub is active and tags are reading.
Screens, alarms, notification lists, and reports are built from anywhere, and later changes don’t require a return trip. Operator training and alarm and notification setup usually take one or two short meetings of an hour or less.
For what a shorter timeline is worth on the budget side, see what the implementation timeline costs you.
How does HMI configuration work in SimpliScada?
+Screens are built in SimpliScada’s drag-and-drop design studio. You place equipment graphics such as tanks and pumps, bind them to live tags, and share the screen with the team, where it’s available in the browser and the mobile app. There’s no HMI software to install, no development license, and no runtime to license per workstation.
The design studio covers what integrators usually script by hand. Formulas and formats handle calculated values and display formatting, and scaling support converts raw values into engineering units. Embedded graphs can run in live mode next to the equipment they describe, and tanks can be shown as 3D visualizations. On a phone, operators can switch to a landscape dashboard mode built for quick checks in the field.
The same drag-and-drop approach extends past screens. Dashboards, reports, and notification escalation workflows are built the same way. An escalation might text the on-call operator first, call a second person if there’s no response, and then notify a supervisor. Permissions are granular, so each user sees only the sites, screens, and reports they’re responsible for, while a manager can see everything.
Integrators decide how much of the HMI work they take on. SimpliScada’s support staff can build screens in collaboration with the integrator and operators, SimpliScada can train the integrator’s team to handle HMI development themselves, or the work can be split between them. For integrators evaluating the platform, the free demo includes an HMI built by SimpliScada’s engineers using 10 of the prospect’s own tags. Short walkthroughs of the studio are in the SimpliScada design studio videos.
How many PLCs, tags, and sites can SimpliScada handle?
+Capacity is set per hub. The SimpliLink Hub handles up to 20 PLCs and 5,000 tags, and the SimpliLink Hub+ handles up to 900 PLCs and 15,000 tags. Sites scale by adding hubs, and every hub reports to the same dashboard.
Adding a site means installing a hub at that site and adding it to the dashboard, with no new radio path or backhaul to engineer. That keeps the cost of site ten close to the cost of site two. A Texas deployment of 27 hubs runs this way, with every site on one screen. On systems that already aggregate field data into a master PLC, a single Hub+ connected to that controller can bring the whole network in at once.
As site counts grow, permissions keep the system manageable. A regional manager can see only their sites while utility leadership sees everything. For how this plays out for utilities, see SimpliScada for municipal water and wastewater.
How does SimpliScada secure remote access without a VPN or open inbound ports?
+Nothing at the site is open to the internet. The SimpliLink Hub sends data out over an encrypted cellular or satellite link to the SimpliScada platform, and operators reach the system through the platform, not through a path into the plant. There is no VPN endpoint, no static IP, no port forwarding, and no remote desktop session pointed at a machine on site.
No inbound path to the PLC: with no port forwarding and no exposed HMI, there is no address on the public internet that leads to the controller.
Encrypted end to end: data is encrypted on the link from the site and on its way to the operator’s browser or phone.
A firewall at every site: every site has its own firewall.
Nothing on site to patch: there’s no server, operating system, or database at the plant. Hosting, redundancy, backups, and updates are handled on the platform and included in the subscription.
That architecture lines up with the first step CISA and the EPA recommended after attackers manipulated internet-exposed HMIs at water systems in December 2024: find those interfaces and take them off the public internet. SimpliScada has also begun the SOC 2 process. For how this applies to the July 2026 attacks on more than 30 Minnesota water systems, see SimpliScada’s security brief on the Minnesota water cyberattacks.
How are user roles, permissions, and activity logs handled?
+Access in SimpliScada is set per user, down to which sites, screens, and reports each person can see. Alarm acknowledgments, changes, and access events are logged automatically.
Many SCADA systems work on an all-or-nothing basis: once someone is in, they can reach everything. SimpliScada’s permissions are built around hierarchy instead. An operator can be limited to the lift stations they cover, a regional manager can see every site in their area, and utility leadership can see the whole system along with its reports. Contractors and integrators get the same treatment, with access matched to the sites they support.
Because every site runs on one platform, access is granted and removed in one place. When someone leaves, there’s no separate VPN account, shared HMI password, or remote desktop login to track down at each site. Activity logging covers who acknowledged an alarm and when, along with configuration changes and access events, so there’s a record to point to when a regulator or a board asks what happened. This same structure is what makes the platform work across large, spread-out operations like oil and gas wellsites, tanks, and pipeline assets.
How does the SimpliScada Automation Partner Program work for integrators?
+Partners earn on both ends of a deployment: a discount on every piece of hardware they install, and a recurring monthly commission on each client site’s subscription for as long as that site stays active. The program lets integrators serve their full client list: smaller utilities that were priced out of traditional SCADA, and larger clients who want full supervisory control and custom HMI at a fraction of the cost of an on-premise system.
SimpliScada ships a demo unit to your office, so your engineers can connect it to a real PLC and see the platform working before a client meeting.
The agreement sets your partner hardware pricing and subscription commission.
Because the hub works with the PLCs clients already have and there’s no server to build, projects are measured in days, which means more projects per year from the same staff.
Every active client site pays a monthly commission, on small systems and large ones alike. On a traditional on-premise install, the integrator’s revenue usually ends at handover; with SimpliScada, it keeps coming in between projects.
A lower total cost for the client makes the proposal easier to win, and the recurring commission keeps paying after the install. To get started, request a demo unit for your team. To get started, request a demo unit for your team.
Ready to simplify your SCADA operations?
Connect with SimpliScada to discuss secure cloud SCADA for your water or wastewater system.