Live factory data display: signage or dashboard?

Decide what the information must do

Start with one question: Would the message become misleading if nobody updated the files today?

A work instruction, a location map or a fixed quality reminder can suit offline playback. A current production count, machine state or process temperature needs a path from the data source to the display. A saved image of a dashboard is still a snapshot, even if it looks identical to the live page.

Write the requirement as a statement about the information, not the hardware. For example: “Show the current count, identify when it was last updated, and clearly mark unavailable data.” That statement gives you something useful to check against the dashboard supplier's supported configuration.

The andon board guide covers where a small screen fits in the space. This comparison addresses a different decision: whether that screen needs a live data client or only local media playback.

Compare the two display paths

A live dashboard does not necessarily need the public internet. It may use a local network service. Equally, a browser-based page is not automatically independent of external services. Authentication, fonts, scripts or other resources may introduce dependencies that the application owner must identify.

For the wider distinction between local playback and managed network services, use the offline or cloud signage guide. A live process display is a separate compatibility question, not simply another name for cloud signage.

Where offline signage wins

Offline signage fits information whose meaning does not depend on a current connection to the process. Examples include a changeover diagram, a fixed escalation procedure or a reminder about a work area's requirements.

It also keeps the content workflow straightforward. Prepare the media, approve it, load it and check the result at the screen. Put a revision date in the artwork when an old instruction could cause confusion. Decide how obsolete files will be removed rather than relying on a new file to make the old one irrelevant.

We sell Android all-in-one displays that play locally stored images and video from a microSD card or USB stick, with included software and no subscription. That playback function does not establish support for a live dashboard, a process protocol or a particular browser application.

The shop-floor display category includes offline playback or the option to use your own Android app. An app requirement still needs its own compatibility review. Android availability alone is not a support statement for your chosen application.

Choose something else if the essential requirement is an automatically changing process value and no supported data application has been established. Do not present manually exported images as current measurements.

Where a supported dashboard wins

A dashboard is the better path when the displayed information must follow the process without someone exporting and loading new media. It can also provide the context a number needs: units, equipment identity, update time and an indication that the source is unavailable.

Specify what “live” means for this job. A production total used for progress review may have a different acceptable delay from a condition requiring an immediate response. The appropriate interval comes from the process requirement and the data system's capabilities, not from the screen's diagonal size.

Keep the display informational. Do not use ordinary signage as the sole means of presenting a safety-critical warning or as a substitute for a required machine safety function. If the job includes process control, use a supported control interface designed for that purpose rather than adding control actions to a signage page.

A dashboard client also needs a maintenance path. Browser updates, application changes and authentication policies can affect operation. The digital signage player guide covers general player selection; for this job, supported dashboard compatibility must be an additional requirement.

Confirm the complete client configuration

Ask the dashboard software supplier to identify its supported client requirements before committing to a display. “Works in a modern browser” is too broad for an installation specification.

Record these details together:

• Application: dashboard product, release and the specific display function being used.
• Client: operating system release, browser or app version, and any required components.
• Page behavior: display resolution, scaling, orientation and whether the layout needs scrolling.
• Access: supported sign-in method, session duration and any required certificate handling.
• Network: approved service addresses, required connections and dependencies outside the local network.
• Maintenance: how supported updates are approved and installed.

A consumer TV browser and a supported browser on a managed client are not interchangeable merely because both can open web pages. Likewise, a browser application and a separately installed app can have different support requirements.

If the intended configuration is not supported, select a compatible client or another supported presentation method. Do not rely on an undocumented workaround to turn a successful demonstration into a supported system.

Assign ownership and check the result

Name an owner for the complete display service, not just the panel. Assign responsibility for the source values, dashboard layout, network access, client updates and content approval. One service owner should coordinate those boundaries so a blank page does not become an unresolved handoff between systems.

Before acceptance, agree on checks using the intended hardware, software and network:

• Compare displayed values, units and equipment labels with an authorized reference.
• Confirm that update times and refresh behavior meet the written requirement.
• Check the dashboard's defined response to unavailable or stale data. A plausible old value must not be mistaken for a current one.
• Check the supported recovery procedure after a session expires, a connection is interrupted or the client restarts.
• Confirm that a display-only account cannot change process settings where the application supports that separation.
• Read the actual page from the intended viewing position, including timestamps and status labels.

These are acceptance requirements for the selected dashboard system, not claims about the included offline player. Ask for the dashboard's documented behavior and record the outcome of the installation checks.

A dense dashboard can be technically compatible yet unreadable. Use the screen size and viewing distance guide for sizing basics, then evaluate the actual layout rather than a full-screen sample number.

Make the choice before specifying the panel

Choose offline signage if approved, locally stored messages answer the requirement. Choose a supported dashboard client if the information must track changing process values. If both are needed, define each function separately rather than assuming a local-media player also provides the live data connection.

For a hardware review or quote, send the intended viewing distance, available mounting space, orientation, power source and a sample of the actual content. For a live dashboard, also send its supported client requirements, required resolution, authentication method and expected update behavior. Do not send credentials.

Power remains a separate installation check. If considering these displays, use the 12 to 36 V DC wiring guide to plan that part of the installation.

The final decision should be traceable to two things: how current the information must be, and which complete configuration the application supplier supports. Select the screen only after those answers are clear.

Questions