The requirement that decides everything: nobody is there
In a theme park, technical services walk the site. In an escape room a game master stands behind the desk. In a museum gallery there is an attendant who was not trained for this and is not paid for it either.
So the installation has to look after itself. Come on without anyone pressing anything, keep running without supervision, and come back after a fault without anyone having to call.
Everything you would normally solve with an action has to be solved in the design here.
On and off with the building
The installation starts with opening hours and follows closing time. That can be on a schedule, but preferably on a signal from building management, because opening hours change and schedules get forgotten.
After a power cut everything returns to the home state by itself. No PC asking for a password, no device booting in the wrong order and then waiting for something that never arrives.
And there is a mode for the days the museum is closed: everything off, except what has to stay on.
Parts you can still order in five years
This is the biggest difference from a temporary installation. We choose industrial components on DIN rail from manufacturers that will still exist in ten years, and we avoid anything that is a closed ecosystem.
A consumer media player discontinued after three years is a time bomb. The same goes for software that only runs on an operating system whose support is ending.
We record what sits where and of which type. If a part needs replacing in six years, the documentation says what it is and what the alternative is.
Quiet in the room
No humming fans in a gallery where people whisper. No blue status LEDs in a darkened space. No equipment in sight where the attention belongs on the object.
That is partly component choice, partly placement and partly a cabinet layout that sheds heat without active cooling. It is easier if you think about it early and nearly impossible to solve once the building is finished.
Interaction that survives visitors
A button in a museum gets pressed more than a button anywhere else. By children, by people unsure whether it works, by people pressing it ten times because nothing happened immediately.
So: industrial push buttons instead of panel buttons, and immediate feedback so the visitor knows they registered. A lamp coming on at the moment of pressing prevents most of the wear.
And the logic has to cope: ten presses in a row is one playback, not ten queued.
Knowing it works without being there
The installation reports when something is off by itself. A lamp that stopped responding, a player that will not start, a sensor that has reported nothing for three days.
That notification goes to whoever needs to know, not to a screen in a gallery nobody looks at. That way a fault becomes something you schedule on Monday morning instead of something a visitor reports at the desk.
What you get handed over
Schematics, source code and credentials are yours. For a museum that is not a luxury but a necessity: the installation outlives most contracts, and whoever adapts it in eight years is probably not the party that built it.
Why you should get the source code →
To the relevant pages
