HMI Fundamentals in Roll Forming — Recipes, Alarm Architecture, Trend Screens & Audit Logs

1. Introduction — Why the HMI Is More Than Just a Touchscreen

In a roll forming machine, the HMI (Human Machine Interface) is often misunderstood as “just the screen.”

In reality, the HMI determines:

• Operator efficiency

• Production consistency

• Fault response speed

• Quality traceability

• Changeover accuracy

• Training requirements

• Warranty disputes

A poorly designed HMI causes:

• Wrong recipe selection

• Incorrect length entry

• Unnoticed alarms

• Unsafe overrides

• Operator confusion

• Production scrap

A professionally engineered HMI becomes:

• A control layer

• A diagnostic tool

• A quality assurance system

• A production reporting platform

This guide explains how to structure HMI systems correctly for industrial roll forming machines.

2. The Role of HMI in Roll Forming Control Architecture

The PLC controls logic.
The HMI controls interaction.

The HMI must:

• Display machine state clearly

• Allow safe parameter input

• Prevent unsafe operation

• Record changes

• Log faults

• Display real-time process variables

The HMI should never directly control outputs.

All commands must pass through PLC interlocks.

3. Recipe Management — The Core of Production Consistency

3.1 What Is a Recipe in Roll Forming?

A recipe is a structured group of production parameters including:

• Panel length

• Quantity

• Line speed

• Shear delay compensation

• Punch position offsets

• Deceleration ramp

• Tension settings

• Stacker drop count

Without recipe management:

• Operators manually re-enter values

• Errors increase

• Quality varies

• Setup time increases

3.2 Recipe Structure — Engineering Approach

Recipes should include:

Identification

• Profile name

• Material type

• Gauge

• Customer reference

Motion Parameters

• Target length

• Line speed

• Acceleration rate

• Deceleration rate

Timing Parameters

• Shear delay

• Valve compensation

• Punch window offset

Production Parameters

• Quantity

• Batch size

• Stacker drop count

Recipes must be structured in data blocks, not loose tags.

3.3 Version Control

Professional systems include:

• Recipe revision number

• Last modified date

• Modified by (operator name)

• Change comment

This protects:

• Warranty claims

• Production traceability

• Quality audits

3.4 Common Recipe Mistakes

• No validation limits

• Operators allowed to modify compensation values

• No separation between operator and engineer access

• No backup storage

Proper design includes permission levels.

4. Alarm Architecture — Designing Alarms That Actually Help

Alarms in roll forming machines should:

• Identify cause

• Provide action guidance

• Record timestamp

• Record duration

Poor alarm design causes:

• Alarm flooding

• Operators ignoring warnings

• Delayed fault resolution

4.1 Types of Alarms in Roll Forming

Safety Alarms

• E-stop activated

• Guard open

• Emergency circuit fault

Process Alarms

• Hydraulic pressure low

• Encoder mismatch

• Length deviation

Mechanical Alarms

• Stacker jam

• Shear timeout

• Punch position error

Electrical Alarms

• VFD fault

• Servo following error

• Communication loss

Each alarm must include:

• Clear description

• Probable cause

• Suggested action

4.2 Latching vs Non-Latching Alarms

Latching alarms:

• Require manual reset

• Used for safety-critical events

Non-latching alarms:

• Clear automatically when condition resolves

Incorrect latching logic causes nuisance resets.

4.3 Alarm Prioritization

Alarms should be categorized:

• Priority 1 — Safety
• Priority 2 — Production Stop
• Priority 3 — Warning

This ensures operators focus on critical events.

5. Trend Screens — Monitoring Process Stability

Trend screens are underused in roll forming.

They provide real-time graphs of:

• Hydraulic pressure

• Line speed

• Tension

• Encoder speed

• Temperature

Trends allow detection of:

• Gradual pressure drop

• Speed oscillation

• Overheating

• Slippage events

Without trends, maintenance becomes reactive.

5.1 Real-Time vs Historical Trends

Real-Time:

• 10–60 second window

• Used for tuning

Historical:

• Hours or days

• Used for maintenance analysis

Both are valuable.

5.2 Engineering Example

Hydraulic pressure:

Normal: 160 bar
Trend shows drop to 140 bar over weeks

This indicates:

• Pump wear

• Filter clogging

• Internal leakage

Trend analysis prevents unplanned downtime.

6. Audit Logs — Protection and Traceability

Audit logs record:

• Recipe changes

• Parameter adjustments

• Alarm resets

• Login activity

• Manual overrides

Audit logs are essential for:

• Quality disputes

• Warranty analysis

• ISO compliance

• Customer traceability

6.1 What Should Be Logged?

• Old value

• New value

• Timestamp

• User name

• Machine state

Without audit logging, responsibility cannot be determined during production issues.

7. Operator Interface Engineering Principles

7.1 Keep Screens Simple

Main screen should show:

• Machine state

• Current recipe

• Length target

• Current count

• Line speed

• Active alarms

Avoid clutter.

7.2 Avoid Deep Menu Navigation

Critical operations must be within two screen touches.

Complex navigation slows response time.

7.3 Use Clear Language

Avoid vague messages like:

“Fault 27 Active”

Instead display:

“Hydraulic Pressure Below 120 Bar — Check Pump or Filter”

8. Access Levels and Security

Professional roll forming HMI should include:

• Level 1 — Operator
• Level 2 — Supervisor
• Level 3 — Maintenance
• Level 4 — Engineer

Operators should not modify:

• Shear compensation

• Encoder scaling

• Motion parameters

Security prevents production errors.

9. Commissioning HMI Properly

• Step 1 — Verify tag mapping
• Step 2 — Validate recipe save/load
• Step 3 — Test alarm triggers
• Step 4 — Confirm audit logging
• Step 5 — Verify trend data accuracy
• Step 6 — Confirm user permissions

Never ship a machine without verifying HMI logging.

10. Common HMI-Related Production Problems

1. Wrong recipe loaded

2. Shear delay accidentally modified

3. Alarm not visible on main screen

4. Trend disabled

5. No login control

6. Manual override left active

Most are design flaws, not operator faults.

11. Best Practices for Modern Roll Forming HMI Systems

• Use structured recipe storage

• Enable audit logs

• Provide trend monitoring

• Separate operator and engineer access

• Display clear machine state

• Integrate production reporting

HMI should enhance control, not complicate it.

6 Structured FAQ — HMI Fundamentals in Roll Forming

1. Why is recipe management critical in roll forming machines?

Recipes ensure consistent production by storing all required parameters for each profile. Without structured recipes, operators must manually enter settings, increasing errors and scrap rates.

2. What information should a roll forming alarm display?

An effective alarm should display a clear description, probable cause, suggested action, timestamp, and severity level.

3. How do trend screens improve production stability?

Trend screens allow monitoring of variables such as hydraulic pressure and speed. Gradual changes can be detected before they cause downtime or quality issues.

4. Why are audit logs important for roll forming machines?

Audit logs record parameter changes and user actions, protecting against disputes, quality claims, and unauthorized adjustments.

5. Should operators be allowed to change shear compensation values?

No. Compensation values should be restricted to maintenance or engineering access levels to prevent accidental production errors.

6. What is the most common HMI design mistake in roll forming?

Overcomplicating the interface with excessive screens and unclear alarm messages, leading to slow response and operator confusion.