A supervisor walking to the office three or four times a day is not walking for fun. The wall has no today’s backlog, pass-through, or line stop. Printed shift reports are already stale when they arrive. The screen must answer “which work order now,” not pose for a night-tour photo.
Staying out of the office needs three conditions. One: type large enough, seven or eight KPIs at most, readable in ten seconds. Two: work-order numbers present, exceptions mapped to a machine. Three: refresh follows the beat—three minutes on a pack line, faster on pick, operations margin still T+1. You do not need a company-wide real-time platform for the floor; see Does it have to be real-time, or is T+1 enough. What a plant and warehouse screen should show, see What a plant and warehouse screen should show.
A wall screen is not a projection of the operations dashboard. Leadership watches margin and collections. The floor watches output, backlog, and line stops. Two pictures, one master data. Mix tour animation with the crew screen and you are back to decoration; see Buying BI as decoration is the same as doing nothing. Align clocks and work-order keys before device collection hits the screen, or “line down” lands on the wrong machine; see Without master data, visualization lies.
Alerts must also reach a supervisor’s phone or station terminal. Red in the corridor only still sits overnight when the night shift faces away; see Alerts pushed to people, so exceptions rarely sit overnight. Once MES and WMS are extracted as work orders and stock, adding a warehouse screen is fast; see Once APIs are standardized, the next chart is faster. Visible efficiency is fewer printed shift reports and fewer office questions; see Visible efficiency a data capability actually delivers.
When DaXi builds a floor screen, we stand at the station first—light, distance, shift—before rendering a globe. Mid-size companies often need one screen and a few alerts, not a big platform. To turn the walks you want to remove into a screen, go to the Data service page and say what you print today and who walks. Device collection can be planned with Hardware-Software Integration.
Pre-shift talks look at the screen, not a printout. On handover, mark work orders already passed so the next shift does not ask the office again. Same master data as the weekly meeting, different KPIs; see After one definition, weekly meetings argue less. Cost is usually one screen plus APIs; see What dashboards or a data platform cost, and how long they take.
Keep wages and personal rankings off the wall
Do not put wages or personal performance rankings on the wall. The floor is a collaboration space. Private KPIs belong on a permissioned terminal. Tour mode can switch in one click so visitors do not see real backlog.
Offline needs a fallback: last successful refresh time and data stay on the screen and are marked stale. Fake real-time is more dangerous than none.
The office will still ask for numbers—for scheduling and QC, not as a vote against the floor screen. “Fewer walks” means “how much backlog now, which order is late” does not need another question. Analysis can stay on a computer; see Reporting vs analysis: which one is a data capability. A handsome screen that cannot read a work order is decoration; see A pretty wall screen is almost as bad as none. Why the floor is part of operations capability, see Why an operations dashboard is not optional.