Why exhibits age out
Digital technology changes quickly compared with the typical life of a gallery. A museum may want an exhibit to stay open for five, ten or more years, while the computers, operating systems and programming tools behind it may stop receiving updates well before that. Displays are discontinued, connectors change, browsers alter how they handle older code, and companies close or change their products.
Obsolescence does not mean the exhibit stops working on a particular day. More often it arrives gradually: a replacement part cannot be found, a security update is no longer available, or a new staff computer cannot open the old project files. The aim of planning is not to prevent change, which is impossible, but to make change manageable.
Types of obsolescence
- Hardware: parts that are discontinued or no longer repairable, such as a specific display model, a touch overlay or a sensor.
- Operating system and software: versions that no longer receive security or compatibility updates, or tools that cannot run on newer machines.
- File formats: media or data stored in formats that fewer programs can open.
- Services and dependencies: online services, licenses, plug-ins or libraries that change or disappear.
- Skills and knowledge: the know-how to maintain a particular system fading as people move on.
The last item is often overlooked, yet it can be the hardest to fix.
Choose technology with longevity in mind
When selecting equipment and tools, a few questions help.
- Is it common? Widely used hardware and software tends to have more replacements, more documentation and more people who understand it. Unusual or highly specialized items carry more risk.
- Is it standard? Equipment using established connectors and open standards is often easier to substitute than proprietary designs.
- How long will it be supported? Ask suppliers about their support and update policies and get answers in writing where possible. Treat vague assurances with caution.
- Does it depend on a service? Anything that needs a continuing subscription, account or remote server adds a dependency that may change.
- Can parts be swapped independently? A design where the display, computer and software can be replaced separately is more adaptable than a sealed unit.
The guidance on choosing media players and display types adds more detail on these trade-offs.
Keep content separate from the software
One of the most effective protections is keeping content apart from the program that displays it. Text, images, audio and video should be stored in standard, widely supported formats and held in editable, well-organized folders, with descriptive information as in collection metadata practice. If content is locked inside a single tool’s format, it may become difficult to reuse. If it is stored cleanly, a future team can rebuild the display layer without recreating the content.
Keep original, high-quality master files even if the exhibit uses smaller versions, since higher specifications will be useful when screens improve. The notes on image resolution explain why.
Build software conservatively
Where you commission or write software, favor mature, widely used technologies over novel ones, and keep dependencies few. Document each one, its version and where it came from. For exhibits delivered through the web, plain, standards-based code often ages better than something tied to a particular framework or plug-in. An offline mode can reduce reliance on outside services, though it brings its own update needs.
Spares, stock and refresh planning
Plan the physical side as well.
- Buy spares at the start. Items that fail or are hard to find later, such as a display or a power supply, are good candidates. Store them safely and label them.
- Record exact models and sources. The equipment inventory in your handover documents is the starting point for finding substitutes.
- Set a refresh horizon. Decide in advance when major components will be reviewed or replaced. A typical approach is to set a review date a few years out and treat it as a normal budget item rather than an emergency.
- Monitor warnings. Watch for end-of-support announcements from suppliers and software providers so you have time to react.
Security and updates
Computers that stay on the network and are not updated may become exposed to security problems. Equally, automatic updates can break an exhibit overnight. A common compromise is to keep exhibit computers on limited, controlled networks, apply updates on a schedule after testing, and take a backup or system image before any change. Details of network arrangements are covered in guidance on exhibit networks.
Document everything
A system that nobody understands is already obsolete in practice. The records described in documentation and handover, including versions, settings, source files and contacts, make later migration much easier. Include a plain statement of the exhibit’s intended behavior so a future developer knows what to reproduce.
Plan for a graceful end
Not every exhibit should live forever. Decide at the outset what happens at end of life: simplify it, replace it, convert it into a static panel or archive it. For web-based work, the principles of exhibit archiving help preserve a record of what was shown. A planned retirement is better than a screen that fails and stays dark.
Budget and time
Handling obsolescence costs money: spares, refresh cycles, periodic software work. Include these in the exhibit budget and the maintenance plan, rather than treating them as surprises. Thinking about future-proofing in a measured way, without trying to predict specific technologies, is usually more reliable than chasing the newest hardware.