Why exhibits need watching
Interactive exhibits freeze, lose touch response, show an error message or go dark, and in a busy museum this can go unnoticed for hours. Visitors rarely report faults, and gallery staff have many other duties. A broken exhibit makes the space look neglected and wastes the effort that went into building it.
Monitoring exists to shorten the time between a fault and its repair. It does not need to be elaborate. A small museum with a handful of exhibits may do very well with a morning walk-through and a few simple tools, while a larger site with dozens of devices benefits from automated status reports.
What can be watched
Different signals tell you different things, and it helps to know what each can and cannot show.
- Is the device on the network? A basic check whether a computer responds. It shows power and connection, but not whether the exhibit software is working.
- Is the software running? A deeper check that the application process is alive. A program can be running and still frozen.
- Is the screen showing the right thing? Some systems capture a small image of the screen so staff can see what visitors see. This catches blank or error screens, but raises privacy considerations if a camera or touch input is involved, which links to visitor privacy.
- Is the hardware healthy? Temperature, storage space and memory use can warn of trouble before a crash.
- Is anyone using it? Use counts can hint that something is wrong: an exhibit that normally gets steady use and suddenly records nothing may be broken. Treat these figures carefully, because there can be other explanations, a point covered under exhibit analytics.
Choose the simplest signal that answers the question you actually have. A “heartbeat” message sent every few minutes by the exhibit software, with an alert if it stops, covers many cases cheaply.
Alerts that people act on
Monitoring is only useful if someone responds. Decide in advance:
- who receives alerts, and who covers when they are away
- how urgent each kind of fault is
- how alerts are delivered, for example email, text message or a shared dashboard
- what the first action should be
Too many alerts lead to people ignoring them. Set thresholds so that brief hiccups do not trigger messages, and review the alert list regularly. A daily summary of exhibit status, delivered before opening, is often more useful than a flood of real-time warnings.
Restart routines
Many faults clear with a restart, so a reliable restart routine is worth more than sophisticated diagnostics.
Scheduled restarts. Some exhibits are set to restart nightly, before opening. This clears memory build-up and recovers from small errors. It is simple and effective for many installations, but it does not fix underlying problems, and it should not hide them. If a nightly restart is needed to keep an exhibit alive, ask why.
Automatic recovery. The software can be set to restart itself if it closes or stops responding. Some systems use a watchdog that restarts the computer if the software stops sending signals. Test these features, because badly configured ones can cause endless restart loops.
Remote restart. Staff may be able to restart software or the computer from a distance using remote access tools. The connection should be secured, and access limited to a few trusted people.
Remote power control. Network-controlled power sockets let staff cut and restore power to a device that no longer responds. This is a useful last resort for frozen machines, but cutting power can corrupt data, so use it only after gentler methods fail.
Physical reset. Even with remote options, a clearly labeled switch or reset point that gallery staff can reach remains valuable. It should be simple enough for a volunteer to use with a short instruction card. Design for this in the enclosure; see screen enclosures.
Write the recovery order down
When an exhibit fails, staff should not have to guess. A one-page procedure might follow this order:
- Check that the screen is powered and the cable is attached.
- Try touching the screen or pressing the physical control to see if it wakes.
- Use the reset option for the exhibit software.
- Restart the computer.
- Cut and restore power if the device does not respond.
- If the fault continues, put up a simple “out of order” sign, and report it.
Keep the sheet near the exhibit area or in the staff office, and mention it in staff training. Always record faults, with the date, what was seen and what fixed it. Repeated entries point to a root cause, like a failing power supply or a heat problem, instead of an endless series of restarts.
Keep it proportionate
Remote tools add their own costs: software to maintain, accounts to secure and connections to manage. Network planning, covered under exhibit networks, decides what is possible. For some small venues, a printed checklist and a morning walk-around remain the most dependable approach. Whatever you choose, add it to your maintenance plan, assign a person to own it, and test it by deliberately unplugging something and seeing whether the alert arrives. If the monitoring system itself is not checked, it can quietly stop working while everyone assumes the exhibits are being watched.