Production dashboards and efficiency trackers on factory floor screens
Quick answer: DigitalSignage.com puts production dashboards on factory floor screens on its free plan: the first 3 screens are free forever, then $3 per screen per month, on Windows, Android, Chrome OS or Raspberry Pi players behind any display. A floor dashboard shows output against target, OEE, downtime, quality and days since the last incident, fed by a shared Google Sheet, a Power BI report through the SignStudio Web Page component, or a dashboard page your MES or SCADA already publishes. Mount the screen where the line can see it, at 700 nits or more under factory lighting, in an enclosure if there is dust, and refresh the data every 1 to 15 minutes.
Last updated October 22, 2026. Product facts from the SignStudio components, Power BI integration and spreadsheet pages; hardware figures from our manufacturing, brightness and typography pages.
What a floor dashboard should show
A dashboard on the floor is read in a glance from ten or twenty feet by people who are busy. It should answer four questions: are we on plan, what is stopping us, how good is what we make, and is everyone safe. Everything else belongs on a supervisor's laptop.
| Metric | What it is | Shown as |
|---|---|---|
| Output against target | Units this shift against the plan at this hour | Two big numbers and a bar |
| OEE | Availability multiplied by performance multiplied by quality | One percentage against the target (our manufacturing page's example: 87.3 percent against 85) |
| Takt time | Available production time divided by customer demand, the beat the line must keep | Seconds per unit, beside the actual cycle time |
| Downtime | Minutes lost this shift and the top reason | A number and a short list |
| Quality | First-pass yield or defects per thousand | A percentage with a colour and a word |
| Safety | Days since the last recordable incident, today's focus | A countdown-style number |
| Shift | Which shift, who is supervising, next handover | A small fixed line |
Keep it to six or seven tiles. A dashboard with twenty widgets is a report, and nobody on the line reads reports.
Data routes, from simplest to most connected
| Route | SignStudio component | Who it suits | Refresh |
|---|---|---|---|
| A shared Google Sheet that a team lead or a script updates | Google Sheets component, sheet shared with the SignStudio service account | Small plants, pilot lines, anything counted by hand or exported hourly | Screen follows the sheet when it changes |
| An Excel file exported from the MES or ERP | Excel upload with a sheet and cell range (see our Microsoft 365 page) | Plants that already produce a shift report in Excel | Each upload |
| Power BI report | Web Page component showing a Publish to web report, or a page you host with secure embed | Plants with Power BI on the ERP or historian; secure embed for anything confidential | Page refresh interval you set; Power BI Pro allows page refresh every 30 minutes, Premium down to seconds |
| A dashboard page from the MES, SCADA, historian or Grafana | Web Page component with a URL that loads without a login | Plants that already have a dashboard; the screen just shows it | Refresh interval you set |
| JSON or XML from an API | JSON or XML data component mapped to text fields | Custom counters, PLC gateways that expose an endpoint | Interval in seconds |
| Direct PLC, OPC-UA or database reads | Through the API or SDK, or a gateway that writes to one of the routes above | Integrators | Depends on the gateway |
Two practical rules. First, anything that needs a user to sign in cannot be shown by an unattended player, so publish the dashboard, export it or use a secure embed; our Microsoft 365 page explains the options. Second, the Google Sheets route is a legitimate production tool, not a stopgap: a cell updated by a team lead at the end of each hour is more accurate than a half-configured integration, and the sheet can be fed by a script from the MES later without changing the screen.
Days since the last incident is the one tile that needs no integration: SignStudio's countdown component counts up from a date, as our workplace safety page describes.
Where to put the screen
The floor is the hardest environment in the building for a display, and the manufacturing page's hardware table applies in full.
| Factor | What to specify | Why |
|---|---|---|
| Brightness | 700 nits or more under high-bay lighting; 350 to 500 is enough in a dim assembly cell | Our brightness guide; factory lighting is often 500 to 1,000 lux |
| Protection | IP65 or better enclosure where there is dust, coolant mist or washdown | Manufacturing page |
| Temperature | Extended range panel or a ventilated enclosure near ovens, presses or loading doors | Panels throttle or fail outside their rated range |
| Mounting | Industrial bracket rated for vibration, above forklift height, cabling in conduit | Manufacturing page |
| Size | 55 inches at 10 to 15 feet, 75 inches at 15 to 25 feet, larger or a video wall beyond that | Our screen size guide |
| Type size | Body text 36pt at 10 feet, 60pt at 20 feet, 84pt at 30 feet; numbers twice that | Our typography guide |
| Position | Facing the line, not the aisle; at the point where the cycle naturally pauses | Operators look up between units, not while working |
Put the player in the enclosure with the display or in a cabinet with the line's own network gear, and use wired Ethernet; a plant floor is unkind to Wi-Fi. The DigitalSignage.com SignPlayer needs only outbound HTTPS, which usually fits an OT network's rules; check our network requirements page with IT.
Refresh rates and what "real time" means
A floor screen does not need sub-second data. Operators act on trends across minutes, and a counter that flickers every second is harder to read than one that updates each minute.
| Data | Sensible refresh |
|---|---|
| Output and target | 1 to 5 minutes |
| OEE, yield | 5 to 15 minutes |
| Downtime reason | When a stop is logged |
| Safety days, shift, targets | Once a shift |
| Andon status (line running, stopped, call for help) | Seconds, from the andon system; keep it on its own zone or screen |
Set the Web Page component's refresh to match, and give every live tile a visible "updated at" time so a stale screen is obvious. When the connection to the data source drops, the SignPlayer keeps playing cached content; a web dashboard will show its last state or an error, so keep a cached fallback scene (the shift plan and the safety message) that takes over if the live page fails to load.
What not to show
- Individual performance by name. A public leaderboard of operators invites blame and, in many jurisdictions, an HR or works council problem. Show team and line figures; keep individual numbers for one-to-ones.
- Costs, margins and customer names. Floor screens are seen by visitors, contractors and auditors.
- Anything from a system that requires a login, on a screen the public can reach.
- Stale targets. A target that stays on screen after the plan changed teaches people to ignore the board.
- Red everywhere. Use red for a stopped line and nothing else, with a word beside it, so colour-blind operators are not guessing.
Setup in six steps
- Pick the six or seven tiles above with the line supervisor and agree the data source for each.
- Create a free DigitalSignage.com account, install the SignPlayer on a Windows, Android, Chrome OS or Raspberry Pi device, and pair it: the player shows a registration code, which you type into SignStudio under Register SignPlayer.
- Build the scene from a dashboard template at the screen's native resolution, with large numbers and one accent colour.
- Connect the data: share the sheet with the SignStudio service account, or paste the dashboard URL into the Web Page component with its refresh interval.
- Add the safety countdown and a shift-change schedule so each shift sees its own target.
- Mount the display at the line, walk to where operators stand, and check that the numbers read at that distance.
Cost
Software is free for the first 3 screens forever, then $3 per screen per month for every screen once the account has 4 or more: a plant with 10 line screens pays $360 a year. Hardware is the larger line: a $40 to $100 Android TV stick or an $81 to $137 Raspberry Pi build per screen, a commercial 55-inch panel at $995 to $1,450, and an industrial enclosure where the floor needs one. Electricity is about $75 a year per 55-inch screen at 12 hours a day, double for a 24-hour plant.
Frequently asked questions
Production dashboards and efficiency trackers on factory floor screens
A floor dashboard shows output against target, OEE, takt against cycle time, downtime and its top reason, quality and days since the last incident, in six or seven large tiles readable from the line. Feed it from a shared Google Sheet, an exported Excel file, a Power BI report through the Web Page component, or a dashboard page your MES or SCADA publishes. Mount it at 700 nits or more, in an enclosure if there is dust, refresh every 1 to 15 minutes, and keep names, costs and customer data off it.
How do I get OEE and production data onto a TV on the factory floor?
Four routes on DigitalSignage.com: a Google Sheet shared with the SignStudio service account, which the screen follows as cells change; an Excel export uploaded with a cell range; a Power BI report or any dashboard page shown through the Web Page component with a refresh interval; or a JSON or XML endpoint mapped to text fields. Anything that needs a login must be published or securely embedded first.
What brightness and protection does a factory floor screen need?
700 nits or more under high-bay lighting, 350 to 500 in a dim cell, an IP65 or better enclosure where there is dust, mist or washdown, an extended temperature panel or ventilated enclosure near heat, and a vibration-rated industrial mount above forklift height. Size it for the distance: 55 inches at 10 to 15 feet, 75 inches at 15 to 25 feet.
How often should a production dashboard refresh?
Output and target every 1 to 5 minutes, OEE and yield every 5 to 15, downtime reasons when a stop is logged, targets once a shift. Andon status needs seconds and belongs on its own zone or screen. Show an updated-at time so a stale board is obvious.
Should factory screens show individual operator performance?
No. Show team and line figures on the floor and keep individual numbers for one-to-ones. Public leaderboards by name invite blame and can raise HR or works council issues. Also keep costs, margins, customer names and anything behind a login off a screen that visitors and contractors can see.
What does a factory floor dashboard cost to run?
Software is free for the first 3 screens on DigitalSignage.com, then $3 per screen per month for every screen once the account has 4 or more, so 10 line screens are $360 a year. Hardware per screen is a $40 to $100 Android TV stick or an $81 to $137 Raspberry Pi build plus a commercial 55-inch panel at $995 to $1,450 and an enclosure where needed; electricity is about $75 a year at 12 hours a day, about $149 around the clock.
Related guides
- Manufacturing digital signage
- Manufacturing facility case study
- Power BI integration
- Show Excel sheets and Microsoft 365 on screens
- Workplace safety digital signage
- Network requirements
Try it on your own screens, free
DigitalSignage.com, which publishes this guide, runs a permanent free plan: the first 3 screens are free forever (no credit card, no ads, no time limit), then from $3 per screen per month with volume pricing via a public calculator. The free SignPlayer runs on Windows, Mac, Android and Android TV, Chrome OS, Raspberry Pi, iPad or any modern web browser. Start free · 2026 pricing