Selection guide
HMI Panel PC RAM, SSD and Windows Selection Guide
Short answer
Order 4 GB of RAM as the default: the documented floor of one size lower suits only a panel running a single lightweight runtime such as AdvancedHMI. Take 128 GB of SSD storage unless logs are small or purged quickly, when 64 GB is enough. Order 64-bit Windows 10, ideally the IoT Enterprise LTSC build, and have RAM, SSD and the OS printed on the quotation before the enclosure is cut.
On this page
Order 4 GB of RAM, the default SSD capacity described below, and 64-bit Windows 10, unless the panel runs nothing but one lightweight HMI runtime — that case works at the documented floor on a 64 GB drive. The floor figure applies to a single AdvancedHMI-style runtime, not to a panel that also carries services, and oversized storage usually comes from component availability rather than the HMI's needs. Size all three from the software list, then have RAM, SSD and the Windows build printed as line items on the quotation before anyone cuts the enclosure.
How much RAM the panel needs #
Start from the software list, not from the panel. A clean Windows 10 64-bit image idles near the figure that forms the floor below, a lightweight .NET runtime such as AdvancedHMI adds roughly 0.5 GB, and every background service — an OPC UA server, a data logger, VNC, antivirus — adds another 0.5 to 1 GB. These are typical figures, so measure them in Task Manager on a comparable running system before you commit. The arithmetic is short: the idle load plus 0.5 GB gives 2.5 GB for the bare case, and one real service alongside the runtime brings the total to 3.5 GB. That is why the floor is a floor, not a target.
- 2 GB: only for a panel dedicated to a single runtime with services trimmed. A vendor that shipped exactly this class of panel judged it sufficient for an AdvancedHMI application, and nothing more.
- 4 GB: the default. Runtime plus one or two services, with headroom for patching and growth.
- 8 GB: a SCADA client, a local historian, a second runtime, or remote clients served from the panel.
AdvancedHMI and similar PC-based runtimes need a Windows host rather than a proprietary terminal, and that choice interacts with the hardware — read which HMI software works with which panel hardware before you lock the platform.
How big the SSD should be #
The fixed load lands around 25 to 30 GB: a Windows 10 64-bit image with .NET and the HMI project, and Windows patching grows that by several gigabytes a year. What varies is log retention, so size for it. One vendor line proved its drives in testing and moved to 256 GB in production only because its mid-size module went end-of-life — an availability decision, not a workload requirement, and a good reminder not to read a shipped capacity as a technical recommendation.
Worked example, one logged row per second at 500 bytes per row: 500 B × 1 row/s = 500 B/s; × 3,600 s = 1.8 MB per hour; × 24 h = 43 MB per day; × 365 days ≈ 15.8 GB annually. On a 64 GB drive with 30 GB of image and applications, free space is 64 − 30 = 34 GB; hold back 15 % of the drive (9.6 GB) so the controller has room for wear leveling, and retention is (34 − 9.6) / 15.8 ≈ 1.5 years. On the default drive, the same holdback leaves 78.8 GB usable, or about 5 years.
The decision follows directly: 64 GB for a panel whose logs are small or purged weekly; 128 GB as the default whenever anything is retained on the panel; 256 GB only when the drive also carries a historian database, stored images or a backup partition. A smaller drive also has proportionally less write endurance for the same logging rate, which is a second reason the default capacity is the comfortable choice.
Choosing the Windows build #
64-bit is the default image and the right one. 32-bit Windows tops out at 4 GB of address space, which caps the machine the day you add a service, so take it only when a legacy driver or license genuinely requires it — and get the vendor's written confirmation that the 32-bit build was validated on that hardware. Windows 7 ended extended support in January 2020; a special-request Windows 7 image is defensible only on a machine with no network path.
For the edition, order Windows 10 IoT Enterprise LTSC when the panel runs one application for a decade. Under Microsoft's fixed-lifecycle policy the LTSC build carries about ten years of security-only servicing with no twice-yearly feature updates, which removes surprise reboots and compatibility shifts from a production line. The IoT Enterprise license ships with the hardware — one industrial PC vendor, for example, lists Windows 10 IoT Enterprise 2021 LTSC as available only with a new device — so it belongs on the order, not on a later retrofit. Windows 10 Pro is the fallback when the runtime vendor certifies Pro but not IoT Enterprise.
Adding memory later #
Many panel PCs take standard laptop SO-DIMM memory, so a field upgrade is realistic — but note the requirement at order time anyway, because a unit delivered configured with its final memory is one less service call. Before buying a module, read the datasheet for slot count, module speed and maximum capacity; none of that is guessable from outside the housing. Sealed housings change the answer: on a washdown-rated unit, opening the case can compromise the gasket seal, so have the factory install the larger module.
Confirm every option on the quotation #
Configuration slips between datasheet and order, so close it on paper:
- RAM size, slot count, module speed and maximum capacity, taken from the datasheet.
- SSD capacity and the exact Windows build — edition, bitness, LTSC or not — as printed line items, not defaults.
- The current mounting drawing pulled on order day: published drawings have been corrected by vendors after the fact, so treat the drawing you download at order time as the controlling document and re-measure the delivered unit against it; for an existing opening, compare against the panel cut-out reference before the enclosure is cut.
- Display size confirmed as shipping now, not planned — announced sizes have slipped before.
When the new panel replaces an aging terminal, pinning the exact part number matters as much as the configuration; read how to verify an obsolete HMI replacement before ordering alongside this list.
Selection summary #
| What runs on the panel | RAM to order | SSD to order | Windows build |
|---|---|---|---|
| One lightweight runtime, nothing else | Documented floor, 4 GB preferred | 64 GB | Windows 10 64-bit, IoT Enterprise LTSC |
| Runtime plus one or two services | 4 GB | 64 GB or the default | Windows 10 64-bit, IoT Enterprise LTSC |
| SCADA client, historian or a second runtime | 8 GB | Default capacity or 256 GB | Windows 10 64-bit, IoT Enterprise LTSC |
| Legacy driver that requires 32-bit | 4 GB | 64 GB | Windows 10 32-bit, vendor-validated |
Pick the row that matches the software list you wrote down. If two rows apply, take the larger value in each column: RAM and storage scale up cheaply at order time and expensively in the field.
Questions asked
Can I add RAM to a panel PC after it is installed?
Often yes, when the unit uses standard laptop SO-DIMM modules: power down, open the housing and fit a larger module. Before buying one, get the slot count, module speed and maximum capacity from the datasheet, because some units ship with one slot occupied or with memory soldered down. On a sealed washdown unit, opening the housing risks the front-gasket seal, so order the larger module installed at the factory instead.
When does a panel PC genuinely need a 256 GB SSD?
When the drive holds more than the operating system and the HMI project: a local historian database keeping years of records, stored process images or recipes, or a full bare-metal backup image for fast recovery. For a runtime-only panel whose logs are small or copied off regularly, the extra capacity buys nothing, because SSD size does not change screen performance.
Will more RAM make the HMI screens respond faster?
No. Once the runtime, operating system and services fit in memory, additional RAM sits idle. Screen update speed tracks the processor, the graphics output and how quickly the controller answers tag requests, so a slow screen with 8 GB stays slow with 16 GB. If pages lag, measure processor load and controller scan time before buying memory.
How do I keep the SSD from filling up over years of service?
Build a purge job into the project that deletes or exports log rows older than a set age, and alarm when free space drops below 15 percent using the HMI system tags or a scheduled task. Windows patching grows the image by several gigabytes annually, so check free space after every servicing round, not only at commissioning.