Keep a local HMI panel at each of the 500 sites and reach it through the panel maker's documented remote access: one small wireless access point per site, one tablet per operator, and the site keeps a working interface whether or not a truck is parked there. Do not load 500 devices and 500 screens into one vehicle-mounted panel unless the maker's manual lists limits above that count and a pilot on the busiest screen holds its update speed.
Keep one HMI panel at each site and reach it through that panel's documented remote access. For 500 control panels, 5 operators and sites sitting miles apart, that means a small wireless access point at every panel, one tablet per operator, and the panel maker's remote-access server switched on in each panel project. The remote link is how you reach the panel you already own; it does not replace the panel. Loading 500 PLC devices and 500 screens into one panel bolted inside the truck looks cheaper on paper, and it only holds if the maker's manual lists device and screen limits above that count and a pilot on your busiest screen keeps its update speed. This page compares the three setups, works the arithmetic for the fleet and lists what to confirm before buying anything.
Why the panel stays at the site
A panel at each location answers a need that exists when no truck is parked there: an electrician tracing a fault, a contractor starting a pump, someone walking up to check a status. Remove the panels and every site loses its interface when the tablet is flat, left in another truck or miles down the road. So the 500 panels stay, and remote access rides on top of them.
Panel makers that ship the feature document the same pattern: the remote-access settings live in the HMI device configuration, load with the project, and the server has to be active before any client can connect. The tablet runs no HMI project at all. It joins the site's wireless network, opens a session to the panel and shows the screen the panel shows. Each site keeps one small project with one PLC device in it, small enough to test on the bench before the panel ships.
Against the fleet: the 500 panels already exist in the plan, so the remote-access design adds one access point per site and one tablet per operator, and nothing else.
The three setups compared
| Setup | What each site keeps | What the operator carries | Where it breaks |
|---|---|---|---|
| Local panel plus remote access | A working interface with or without visitors | One tablet, no HMI project on it | The risks are network path and client match, not screen count |
| Tablet as the HMI | No panel; the tablet is the interface | One tablet per operator holding 500 site projects | No interface when the tablet is absent, and 500 projects on 5 tablets is 2,500 copies to keep in sync |
| One panel mounted in the truck | No site interface at all | One panel with 500 device connections and 500 screens | Needs per-project limits above 500 devices and 500 screens, and the truck becomes the single point of failure for all 500 sites |
The tablet-as-HMI setup also puts deployment on people: change one screen and you redeploy to five tablets, and the tablet that misses the update runs a stale project against live equipment. That burden is why the setup only fits sites with no screen between visits.
Worked example: five operators, 500 sites
Take the fleet as stated: 500 control panels, 5 operators, sites separated by miles of road.
- Sites per operator: 500 ÷ 5 = 100 sites per operator.
- Radio coverage: one unmanaged access point per panel. Most hold a solid link within about 30 m indoors and reach 100 m or more with line of sight, so the truck parks within radio range of the panel being serviced. The sites sit miles apart, so each access point serves its own panel only; joining sites into one network is a separate long-distance link design, the problem class Connect a remote HMI screen 1,500 feet from the PLC covers at the 1,500-foot scale.
- Hardware added: 500 access points, one per site, and 5 tablets, one per operator. No new panels.
- Project copies: 500 small panel projects, one per site. The truck-panel design concentrates the same connections into 1 project carrying 500 devices and 500 screens. The tablet-as-HMI design spreads 500 projects over 5 tablets: 500 × 5 = 2,500 copies.
- Per visit: join that site's wireless network, open the site entry from the tablet's regional folder (500 entries in 5 folders is 100 entries per folder), open the remote session, compare the screen against the physical panel, then command.
Result: each operator services their 100 sites from the truck, and every site keeps an interface that works for whoever walks up with no tablet at all.
Safety note: confirm the screen on the tablet matches the physical panel before writing anything to the machine. A tablet that stayed associated with the previous site's network will show the previous site's panel, and every value on it belongs to different equipment.
When the other two setups win
Tablet as the HMI fits sites nobody stands at between visits: an unmanned pump pad, a tank site, a vault. Take the trade openly: no interface on site when the tablet is away, and every project change multiplies across five tablets.
The truck-mounted panel fits operators who spend the day driving between short visits. Two checks decide it. First, the maker's manual must list per-project device and screen limits above 500 devices and 500 screens; the manuals print those limits, so read the printed numbers before designing around that count. Second, a pilot must hold update speed on your densest screen: an HMI screen's update load comes from the tags and events that screen shows, so the pilot screen has to be the densest real screen in the project, not an empty demo page. Power the panel from the truck electrical system through a 12 to 24 V DC converter at the panel's 24 V DC input, use a wireless bridge with an external antenna mount for the site links, and mount the panel where direct sun cannot wash out the screen. One panel serving several PLCs is a working pattern at small counts; Point one HMI panel at multiple PLCs with per-device tags shows the per-device tag structure that keeps such a project organized.
If either check fails, the truck panel drops out and the local-panel design carries the fleet.
What to confirm before you buy
- Remote access on the panel models you actually buy: whether the server ships in the panel firmware or needs a separate license, and what the client side runs. Some ranges serve the project to any modern browser through an HTML5 web client; others need the maker's client app or a remote-desktop session. Match the client to the panel first; Remote HMI wireless access: choose the client first walks that choice.
- Access level: whether a session is view-only, fully operable, or both, and which level each stop on the route needs.
- Per-project device and screen limits in the manual for the model, if the truck panel stays in the running.
- Site network rules: a passcode on every access point, only the operators' tablets allowed, and no path from any site network to the internet. If panels must be reachable from outside radio range later, that is a separate routed design; where it is done by opening ports on each site's router, testing every hop of a port-forwarded HMI connection keeps each failure isolated.
- The site map: one row per site with the site name, the wireless network name and the panel address, kept with the work-order system, and tablet folders named to match the labels on the panels.
Pilot one site, then roll out the other 499
- Pick one representative site and record the panel model, its network address and the access point's network name.
- Join that network from one operator tablet and confirm the tablet reaches the panel's address.
- Open the remote session and compare its screen with the panel in front of the truck, value by value.
- Disconnect, drive out of radio range, return, rejoin and run the comparison again. That rejoin is the operator's normal arrival, so it gets tested, not assumed.
- If a session refuses to open, check in order: the tablet's association with the site network, the IP path to the panel, the remote-access server setting in the panel, then the client's match with the panel model.
Run the same pilot at a second site with different hardware or a different panel firmware revision before ordering 500 access points. One clean site is a data point; two unlike sites are a pattern.
Recommendation: Keep one HMI panel at each of the 500 sites with its remote-access server switched on, add one wireless access point per site, and give the 5 operators tablets that open sessions from regional folders, 100 sites per folder. Choose the truck-mounted panel only if the maker's manual lists limits above 500 devices and 500 screens and a pilot on your densest screen holds update speed. Choose the tablet-as-HMI setup only for sites nobody stands at between visits, and accept that every project change redeploys to five tablets.
Questions
Do the operators need special software on the tablets?
That depends on the panel range, and it is the first thing to confirm. Some ranges serve the project to any modern browser through an HTML5 web client, so the tablet needs only a browser. Others supply their own client app, or expose a remote-desktop session to the panel's screen. Read the remote-access section of the manual for the exact panel model before buying tablets, and match the client to the panel.
Can the five operators reach the panels from anywhere, without driving to each site?
Not with this design, and that is deliberate. Each site's access point covers tens of meters around the panel, and the sites sit miles apart with no radio path between them. Reaching panels from outside radio range means routing the sites together or using a VPN, which is a separate network design with its own security work. Start with per-site access, then design central access if the service workload proves it is needed.
How many PLC devices can one HMI panel connect to?
The maker's manual prints the per-project device and screen limit for each model, and that printed number governs. In practice the tags and events on the screen currently displayed decide how smoothly a project runs, so a project with 500 configured devices can run well if each screen stays light. Pilot the densest real screen with live data before committing a large device count to one panel.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.