The HMI on a low-pressure polyurethane metering machine is not a control-panel summary. It is the only place where an operator can see whether the polyol and isocyanate streams are still inside the accepted ratio window before the pour starts. A useful HMI organizes that information into three layers: the active recipe with saved setpoints and limits, live trends that show pressure, temperature, flow and mix-head behavior over time, and tamper-evident shot records tied to the mold or order. The test of any screen is simple: can the operator catch a deviation before it becomes scrap, and can the plant trace the cause after it happened?
What Belongs on the Main Run Screen
The main run screen should be designed for the first thirty seconds of a shift, not for an equipment brochure. Operators need to confirm that the selected recipe matches the mold or order, the ratio is inside tolerance, material temperatures are at target, and the mix head is ready. Once pouring starts, the most useful screen shows actual values against limits, because a number without a boundary does not tell the operator whether to stop.
| Display group | What the operator should see | What it catches |
|---|---|---|
| Component ratio | Target ratio, live ratio, high and low alarm limits | Gradual pump drift, wrong recipe selection |
| Flow rates | Polyol and isocyanate flow in the active engineering units | Cavitation, clogged filters, feed starvation |
| Material temperatures | Tank, line and mixing head temperatures with limits | Viscosity shift, incomplete mixing, cold material |
| Mixing | Mix head speed, motor current or both | Dynamic mixing failure, high-viscosity overload |
| Pressure | Pump inlet and discharge pressure | Inlet starvation, blocked line, worn pump |
| Shot status | Cycle state, shot counter, mold or order identity | Missing mold synchronization, wrong part data |

The run-screen values are only meaningful if the metering and mixing hardware behind them can hold the recipe. <Guide to Low-Pressure Foaming Machines for PU Elastomers> covers the low-pressure machine configurations that determine which parameters the HMI should expose.
Recipe Screens Should Act Like Controlled Documents
A recipe that lives as a set of free-text notes is not repeatable. The HMI should store structured fields: material codes and lots, ratio, output or shot size, temperatures, mix head speed, pour time, degassing or vacuum steps where present, and alarm limits. There should be one active revision, with a change log showing who changed a value, when, and from what to what. Operators should be able to load a recipe, not retype it. If a formula change requires engineering approval, the recipe screen should enforce that role rather than leave the decision to a whiteboard.
The same logic applies whether the machine is a simple two-component unit or a multi-stream elastomer system. A recipe should include the process limits that protect the part, not only the setpoint values. For example, a recipe that stores target ratio without high and low limits gives the operator no objective reason to stop a drifting pour.

Trend Screens Should Show Stability, Not Just Current Values
Current values hide intermittent faults. A short pressure spike, a temperature dip when a new drum comes online, or ratio drift during start-up may last only a few seconds and then disappear. Trend displays should record flow, pressure, ratio, temperature and mix head speed at a resolution fast enough to catch those events. The operator should be able to zoom to a single cycle and compare it with a known good shot.
Trends are also the fastest way to separate a machine problem from a material problem. A ratio upset that follows a pressure drop points to feed or cavitation. A slow ratio drift at stable pressures points to pump wear, calibration error or a temperature-related viscosity change. If the HMI shows only current values, the operator may see the effect but not the sequence that produced it.

Shot and Batch Records Must Be Searchable and Tamper-Evident
A shot record should read like a quality record, not a production counter. At minimum it should capture timestamp, recipe ID and revision, operator ID, mold or order number, raw material lots, actual ratio and total output, temperature and pressure range during the shot, alarm events, and pour duration. The key requirement is that the operator cannot edit the record after the fact. If the record can be changed, it stops being useful evidence for customer claims or internal root cause analysis.
Export matters more than storing years of data inside the HMI. CSV or PDF export, or transfer to an MES or ERP system through a defined interface, lets the plant retain long-term history without overloading the machine panel. If the parts serve regulated applications, the plant should also confirm whether electronic records need audit trails, electronic signatures, or stricter retention rules.

Historical records become valuable only when they stay tied to a specific machine and formula. <The Ultimate Guide to Low-Pressure Foaming Machines for PU Elastomers> covers the low-pressure machine options that affect how much process data a line can realistically capture and retain.
Alarm and Interlock Text Should Tell the Operator What to Do
An alarm that says only “pressure fault” transfers the diagnosis to the operator. The HMI should show the alarm name, setpoint, actual value, consequence, and required action. Warnings and interlocks should be visually separate. A warning means the process is outside the preferred band but may continue under supervision. An interlock means the machine will not pour, or will stop, because the condition can create scrap or a safety risk.
Overrides need their own audit trail. If a supervisor can bypass an interlock, the HMI should record who, when, and for which shot. This preserves accountability without forcing the line to stop for every minor deviation.
Match the HMI to the Operating Mode
A laboratory machine and a production machine need different HMI behavior even when the underlying metering unit is similar. In research and development, the engineer needs manual control, frequent setpoint changes, and high-resolution trends. In production, the operator needs a locked recipe, clear pass or fail prompts, and a simple way to attach the mold or order number.
Role-based access helps both groups. Operators, process engineers and maintenance staff each see the functions they need without being able to change parameters outside their responsibility. If the line will run multiple products, recipe selection should include a confirmation against the work order before pouring begins.
What to Check Before Accepting the Machine
During factory acceptance testing and site acceptance testing, test the HMI with a real operation rather than a prepared demonstration. Create a recipe, modify one setpoint, verify the change log, run a short pour, and call up the shot record. Check that trend data is stored at a useful interval and that exports open in a standard format. Try to edit a completed shot record as an operator and confirm the system rejects it. Verify that alarm history remains after a restart and that the HMI date, time and language settings suit the plant.
The screen shown in a brochure matters less than the data the machine can prove it saved. If the HMI cannot recreate the sequence of events for a single bad shot, it is not yet ready for production traceability.

Turn HMI Requirements Into a Specification
Before comparing suppliers, convert these points into a written HMI requirement list: recipe fields, trend variables and retention time, shot record contents, role-based access, alarm actions, and export format. Haifeng Polyurethane Machinery can review your list against the machine configuration and clarify how the control architecture will meet it. Contact info@haifeng-automation.cn or WhatsApp: 86 13566296633.
FAQ
Does a single-product line still need recipe storage?
Yes. Even if you run only one product, a stored recipe creates an approved baseline with limits and a change log. Material lot changes, seasonal temperature shifts, or pump wear can require a controlled setpoint adjustment. A stored recipe shows that the change was deliberate and approved.
How long should shot records and trend data be kept?
Keep them long enough to cover customer complaint windows and your internal traceability policy. For many producers, that means the life of the product batch plus any applicable warranty or quality period. Define retention before purchase because the HMI may store only short-term data while an MES or export function handles long-term storage.
Can operators edit shot records?
No. Shot records should be read-only for operators and editable only through a controlled correction process. If an operator can change a completed shot record, the data loses its value as objective production evidence. Corrections should leave an audit trail showing the original value, the new value, and the reason.
What is the difference between a trend and an alarm history?
A trend is a continuous time-series record of process variables such as pressure, flow, ratio and temperature. An alarm history is a discrete event list showing when a value crossed a limit, the actual value at that moment, and whether the alarm was acknowledged. Both are useful, but they answer different questions.
Is a touchscreen HMI enough, or do we need a separate industrial PC?
A well-designed touchscreen HMI is usually sufficient for operator functions such as recipe loading, pour control and alarm handling. A separate industrial PC or edge device becomes useful when you need long-term trend storage, complex reporting, MES integration, or analysis of many machines. Define the data demands before choosing the hardware.
If you’re interested, check out these related articles:
Foam Filled Tires vs Solid Tires
Roof and Wall Sandwich Panel Production Line: Machine Selection for Industrial Buildings