Factory status display or operator HMI

The boundary is what the interface does

A read-only sign presents information. It might show production totals, a current job reference or a summary of equipment states. It does not write commands or settings back to the equipment. Its absence must not remove the means to control the process or respond to conditions that require action.

An operator HMI is part of the control interface. Starting equipment, selecting operating modes, changing a setpoint and acknowledging a process alarm all move the application beyond simple signage. Even a page with mostly numbers becomes a control interface if one button can change the process.

Read-only does not automatically mean low consequence. A display used to decide whether equipment is safe to approach can carry serious consequences without having any buttons. Keep safety decisions with the machine's established procedures and safety functions, not an informational sign.

The andon board guide covers where small shop-floor screens fit. The narrower question here is whether your proposed page stays outside the control interface.

Compare the two roles

The table describes typical application roles. A dedicated HMI still needs suitable engineering, configuration and support. Its product category alone does not make an application safe.

Neither column replaces a machine safety system. Where a display participates in a safety-related function, that function needs its own suitable design and assessment.

Define the information before selecting hardware

Write a short content specification before choosing a screen. Separate reference material from live process data and control functions.

Reference material includes work instructions, identification graphics and general production notices. Offline images and video can suit this role, provided the content has a clear revision and an update procedure. Do not present a pre-rendered image as a current measurement.

Live process information includes counts, equipment states and job progress. Each item needs a defined source, unit, update expectation and meaning. For example, a production total should say whether it covers the current job, shift or another reporting period. A bare number leaves too much room for interpretation.

Control functions include commands, settings and acknowledgements that affect process handling. Keep these out of the signage specification unless the project is being developed and supported as a control interface.

Avoid copying an entire control screen onto a smaller display. Select the few facts that answer the local question. Use text labels alongside colors so that a state is not communicated by color alone. For letter sizing, use the screen size and viewing distance guide rather than treating pixel count as a measure of readability.

Live status needs a data-quality design

A plausible-looking value can be more misleading than a blank page. For every live value, define what counts as current and what should appear when its source is no longer current.

Specify the application so it is designed to distinguish a valid zero from missing data. It should also be designed to replace stale current-state indications with a clear unavailable state after the agreed timeout. Do not leave a green state beside an old timestamp and expect the timestamp to correct the message.

The timeout depends on the process and the purpose of the page. A slowly changing production total and an equipment-state indication may need different freshness limits. There is no single delay that makes every factory status page suitable.

Your specification should cover:

• The system that supplies each value and whether it provides a source timestamp.
• The difference between the last successful data update and the screen's local clock.
• How missing, invalid and stale values are displayed.
• How the application is designed to handle loss and restoration of its data connection.
• What independent indication is available if the application itself stops updating.

A clock drawn by the same application is not an independent health check. Monitoring should be designed to distinguish a running device from an application that is receiving useful data.

Our included signage software plays images and video from microSD or USB without internet or a subscription. That is not a claim of live process-data integration. A live dashboard needs a suitable application and a defined data connection. The offline or cloud signage guide covers the broader content-distribution choice, which is separate from control-system integration.

Full-screen mode is not read-only access

Full-screen mode can keep the intended page in view. It does not establish process permissions. Hiding a toolbar, removing a keyboard or selecting a non-touch screen does not make an application read-only.

For a status-only installation, use a documented data interface and an account that has only the access needed to read the required information. Enforce that restriction at the system providing the data, not just in the page layout. Review diagnostic pages and embedded navigation as well as the opening screen.

If process writes are required, define them explicitly. That includes who can authorize them, how the application indicates the selected equipment and how command acceptance is shown. Those requirements belong in the control-interface design, not in a later adjustment to a signage page.

A supported HMI is the better choice when the required application depends on control-specific engineering tools, alarm handling or operational navigation. Do not assume an Android display can run a control application simply because both can show a graphical page.

Plan replacement as part of the application

A useful comparison includes the recovery package, not just the appearance of the first working screen. Record the application version, configuration, supported operating environment and method for restoring the installation.

For a read-only dashboard, retain the page files or application package, data-source configuration, access-management procedure and a clear description of the expected startup screen. Store secrets through the site's approved method rather than embedding them in general maintenance notes.

For an operator HMI, include the editable project, required engineering software, legitimate licenses and the manufacturer's documented backup and recovery procedure. Confirm that a replacement can be configured using resources the site is authorized to use.

Define acceptance checks for both roles. For a status page, check normal data, missing values, stale values and restoration of the data connection. For a control interface, the checks must also cover its specified control functions under the machine's commissioning procedures.

Where automatic recovery is specified, describe what the application is designed to do after a power interruption or software fault. Do not treat a restart mechanism as proof that the page is accurate or that the control function is available.

Where a small signage display fits

We sell Android all-in-one displays for offline playback or your own Android application. A 15.6 inch display is one option to evaluate for a nearby read-only page when the application supports Android and the layout is legible at the installation position. Its resolution is 1920 × 1080, but the useful amount of information still depends on physical letter size and viewing conditions.

These units are not HDMI-input monitors. The HDMI port is an output. If your control system requires a separate video-input monitor, this is the wrong connection arrangement.

Physical suitability also needs a separate review. The IP65 rating applies to the front face only; the rear is not sealed. Plan power using the 12 to 36 V DC wiring guide. Neither the enclosure details nor the power arrangement establishes application compatibility.

Choose a dedicated, supported control interface when the required software is unsupported on the proposed platform, the display is essential to operating the machine or the recovery arrangement cannot meet the site's needs. A sign is useful because it communicates clearly, not because it can be made to resemble an HMI.

Make the decision with a written scope

Choose the read-only status display when the content is supplementary, process writes are excluded, data quality is visible and the application has a practical support plan. Choose the supported operator HMI when the interface has a defined role in controlling equipment or handling operational actions.

Before requesting a display recommendation, send:

• A sample page with each item marked as reference content, live data or a control function.
• The application name, supported operating environment and documented data interface.
• Viewing distance, mounting position and available installation space.
• Freshness requirements and the intended unavailable-data presentation.
• The required operating hours and environmental conditions.
• The backup, replacement and acceptance-check requirements.

We publish no duty-cycle rating for these units. Include operating-hour requirements in the review rather than assuming suitability.

If the scope cannot clearly separate information from control, resolve that boundary first. Selecting the screen should follow the application decision, not determine it.

Questions