Split a factory PDF notice board into two layers on one screen: an auto-advancing playlist that runs by default with touch off, and a locked touch kiosk layer for browsing, with an inactivity timer of 30 to 60 seconds returning the board to the loop. Keep the PDF as master and export pages as images at the screen's native resolution.
A production hall notice board that has to show PDFs is two jobs on one screen. The first job is broadcast: management posts the shift schedule, a quality alert and a safety topic, and the screen steps through the pages on a timer without asking anyone for input. The second job is lookup: an employee wants one specific document, reads it at their own pace, then walks away. Software that merges the two jobs into one mode usually does neither well, so plan them as two layers on the same panel. The bottom layer is a playlist that runs by default with touch switched off. The top layer is a locked touch kiosk that pauses, pages and jumps on demand, with an inactivity timer that hands the board back to the loop. This article gives you the decision rule, the timeout arithmetic, the PDF handling and the questions that sort software that can do this from software that cannot.
Do you need touch at all on a factory notice board?
Skip touch when the board only broadcasts what management posts, and build the touch layer only where staff need to find one document among many, because touch adds a kiosk app, an idle timer and a lockdown whitelist that all need looking after. Your case passes both tests: the pages come from management, and employees want to stop on one and read it through, so the main hall board earns its kiosk layer. Decide board by board, not hall-wide. A doorway board or a cell-side board stays a plain loop, because nobody stands there long enough to browse. If the real job at some screen is machine status and call lights, that is an andon board, and the guide to andon boards covers where a small screen fits and where it does not.
What runs a plain auto-advancing notice screen?
Any digital-signage player that schedules a playlist runs this build: export the PDF pages as images once, set a dwell of 10 to 15 seconds per page, and the loop advances on its own with touch switched off so nothing stalls it. The only setting that matters is the dwell: 10 to 15 seconds covers a page of about 30 words at a normal reading pace. The central point you want is just the playlist: one place defines which pages run, in which order, on which screen, and pushes changes without anyone visiting the screen. Your existing 75-inch screens stay on the wall and take a player, either a small player box feeding each screen over HDMI or the screen's own built-in signage mode if it has one. For close-range spots such as a doorway or a cell, the small panel-mount Android boards in our displays category play the exported pages straight from a memory card or USB stick, offline, with no subscription; a small panel is the wrong choice for a board read across a hall, because its text is too small at that distance.
How does a touch kiosk build work on the same screen?
The touch kiosk build keeps the same loop as its home screen and adds a browse layer: one tap pauses the page, swiping moves through the pages, a corner grid of thumbnails jumps straight to any slide, and an idle timer hands the board back to the loop. Two software categories deliver it. Kiosk management software runs one app, or a short whitelist of apps, full screen: it hides settings and the home screen and returns to the default app after inactivity, so the notice loop is the default and the document browser is the second app on the list. The other category is a page built for the job and shown in a locked browser on the screen: the page itself implements the pause, the swipes, the grid and the idle return. Either way, map swipe right to the next page and swipe left back one, and keep that mapping the same in the loop and in the grid.
Then test three behaviours on a live demo before you commit: pause on touch, jump from the grid, return after idle. Most cloud signage services ship playlists and touch templates, but hold-to-pause and a thumbnail jump menu are the two features that separate a notice kiosk from a slide deck, so they are exactly the two things to see working in the demo. One hardware check: capacitive touch glass needs bare skin, so a hall where staff wear gloves needs resistive touch or conductive-tip gloves, and the touch panel technology comparison sets out which layer suits which input. A 75-inch touch screen is also heavy enough to injure someone if its mount lets go: use the wall mount and fixings the screen maker specifies for that size and weight, and have the wall checked before the screen goes up.
| Build | What staff can do | What runs it | The catch |
|---|---|---|---|
| Plain loop, touch off | Nothing, the board broadcasts | Any signage player with a playlist and a per-page dwell | None for a broadcast board |
| Kiosk layer on the loop | Pause, swipe, jump from the corner grid | Kiosk management software with an app whitelist, or a purpose-built page in a locked browser | Needs an idle timer settable in seconds |
| Whiteboard alongside | Draw at shift meetings | A second whitelisted app | An unsaved drawing is lost when the board returns to the loop |
| Document viewer alone | Swipe through one PDF | A PDF viewer app full screen | No dwell loop, no grid, no idle return |
How long should the touch timeout be before it returns to presentation mode?
Set the inactivity timer between 30 and 60 seconds: long enough that a reader finishing a page is not yanked off it mid-sentence, short enough that the board is back on the notice loop before the next person walks up to it. The floor of the range comes from reading speed. A notice page runs about 30 words, a reader at a normal silent rate of about 200 words a minute covers that in about 9 seconds, and a slower reader takes close to twice as long, so anything under 30 seconds risks cutting someone off mid-page. The ceiling comes from the board's default job: every minute in browse mode is a minute the notices are showing nothing, and a board left sitting in the grid menu is a board no one reads. Inside the range, make the timer a setting you can change in seconds, because a quiet shift and a changeover morning want different values; 45 seconds is the starting point, and you adjust it after watching the floor for a week. The same idle-then-return logic runs machine screens the other way round; the 30-second idle-and-wake setup for a touch screen shows the timer mechanics on an HMI.
Recommendation: run each board as a plain auto-advancing playlist with touch off, add the kiosk layer only on boards where staff ask for specific documents, start the idle timer at 45 seconds inside the 30 to 60 second range, and keep the whiteboard as a separate whitelisted app entered on purpose.
Do you have to keep the content as PDF?
Keep the PDF as the master document and export its pages as images at each screen's native resolution, 1920 × 1080 or 3840 × 2160, because most signage players take images and video, and an export at the panel's real pixel count keeps the text crisp. The PDF stays the version-controlled original: it prints, it archives, and the next revision starts from it. Export each page to an image file at the screen's pixel count, name the files in page order so the loop order matches the document order, and re-export whenever the PDF is revised. An export at the wrong pixel count is the usual cause of a slide showing in one corner of the screen; the fix for a slide that shows in one corner walks through the size check. One exception to the export rule: a full-screen PDF viewer pages through the original document directly and keeps text sharp at any screen size, but then you supply the dwell and the idle return yourself, which is the build you were trying to avoid writing. And one content rule: a page nobody can read inside the dwell stalls the loop, so split anything longer than about 40 words into two pages.
Can staff use a whiteboard and still stay locked to the notice software?
Whitelist exactly two apps in the lockdown: the notice kiosk and a whiteboard app, entered deliberately and exited back to the notice screen, so staff get a marker board for shift meetings and still stay out of settings, a browser and everything else. Kiosk management software carries an allowed-apps list, and two entries is the right size here: anything longer becomes a shared tablet within a week. The whiteboard is a meeting tool, so staff enter it at the start of a shift meeting and leave it back to the notice loop when the meeting ends; it is never the screen a passer-by finds. Two details to check with the lockdown software: that the notice app's idle timer still applies after a whiteboard session, and that staff save or photograph a drawing before leaving, because an unsaved drawing is gone when the board returns to the loop.
What does a worked example look like for a production hall board?
A 75-inch board hanging in a hall corner, read from 25 ft, carries a 6-page PDF on a 72-second loop with a 45-second idle timer, and the arithmetic below shows where each of those numbers comes from. Scenario: a hall corner board, 75-inch 16:9 panel, showing a 6-page PDF (shift schedule, quality alert, two notices, safety topic, jobs board), nearest reading point 25 ft, kiosk layer enabled.
- Dwell. A page carries about 30 words. Normal silent reading runs about 200 words a minute, or 3.3 words a second, so 30 ÷ 3.3 ≈ 9 seconds of reading. Set the dwell to 12 seconds per page to cover the read plus a glance.
- Loop. 6 pages × 12 seconds = 72 seconds per full pass, so a given page comes round at least once every 72 seconds for anyone standing at the board.
- Idle timer. A reader taps, jumps to page 4, reads its 40 words in about 12 seconds and walks off. The 45-second timer, the midpoint of the 30 to 60 second range, has the board back on the loop inside a minute of the last touch.
- Text size. The FHWA planning figure is 30 ft of viewing distance per inch of capital letter height, with 1.7 times capital height between lines; 20 ft per inch is the safer figure for fast reading. At 25 ft: 25 ÷ 30 = 0.83-inch capitals as the minimum, 25 ÷ 20 = 1.25 inches for fast reading, with line spacing of 1.7 × 0.83 = 1.4 inches or 1.7 × 1.25 = 2.1 inches.
- Screen check. A 16:9 screen's picture height is 0.490 of its diagonal, so 75 × 0.490 = 36.8 inches. The 0.83-inch capital is 0.83 ÷ 36.8 = 2.3% of the picture height and the 1.25-inch capital is 3.4%, so both fit with room to spare.
- Farther reader. From 40 ft the same page needs 40 ÷ 30 = 1.33-inch capitals, or 40 ÷ 20 = 2.0 inches for fast reading, which is 5.4% of the picture height: still fine on the 75-inch board, but beyond what a doorway-sized panel delivers. At hall-crossing distances the answer changes display class, and choosing a large LED sign board for a shop floor covers that case.
Decision: the existing 75-inch board runs both layers with no new hardware. The plain loop needs only a player with a playlist; the kiosk layer is the only real purchase decision, and it is a software one.
What should you ask a vendor before you commit?
Ask a shortlist vendor four questions before you commit: whether the loop resumes after an idle timeout you can set in seconds, whether touch pauses the page, whether a thumbnail grid jumps straight to a slide, and whether PDFs load directly or need exporting to images. The four decide the build, so take the answers from a live demo on the kind of screen you own, in the hall's light, with a gloved hand on the glass:
- Idle timer: can it be set in seconds, and does the loop resume automatically when it expires?
- Pause on touch: does touching hold the current page without leaving the app?
- Grid jump: is there a thumbnail overview that jumps straight to any page?
- PDF handling: does the player take PDF files directly, or do you export pages as images, and at what pixel count?
- Lockdown: can the allowed-apps list hold exactly the notice app and the whiteboard, with settings and the browser out?
- Scheduling: can one central point say which pages run on which screen at which time?
- Input: does the touch layer register a gloved hand, or does it need bare skin?
If a vendor cannot show pause-on-touch, grid jump and idle return together on a real screen, the product is a playlist tool, and the plain build is what you are actually buying. Buy the plain build knowingly, or keep looking for the kiosk layer.
Questions
How many words fit on one notice page?
Plan 30 to 40 words per page. A reader at a normal silent rate of 200 words a minute covers 30 words in about 9 seconds, which fits a 12-second slide, while a 100-word page needs about 30 seconds and stalls the loop, so split it into two or three pages instead.
Does the idle timer interrupt someone who is still reading?
No. The timer counts from the last touch, and every new touch restarts it, so a reader who keeps swiping, tapping or holding the screen is never bounced back to the loop. It fires only after the reader stops interacting, which is why 30 to 60 seconds is enough for a page that takes about 9 seconds to read: the timeout races the reader's walking away, not their reading.
What size text does a doorway board need at 15 ft?
Use the same FHWA figures from the closer point: 15 ÷ 30 = 0.5-inch capitals as the minimum, 15 ÷ 20 = 0.75 inch for fast reading, and 1.7 times capital height between lines, so line spacing of 0.85 to 1.3 inches. Those sizes sit comfortably on a small panel board, which is why a doorway spot is a job for a compact display and not the hall screen.
When is a central content point worth adding?
With one or two boards, a USB stick or memory card updated by hand is the whole system, and an offline player needs no subscription. From about three boards, or once the pages change weekly, you want one place that pushes the same playlist to every screen at a set time, which is what the cloud signage services are for.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.