Decide whether the exhibit needs a network at all
Every connection is another thing that can fail. Before planning, ask what each exhibit actually uses the network for. Common reasons are:
- receiving updated content from a central place
- synchronizing several screens or devices so that they act together
- sending usage figures or fault reports back to staff
- allowing remote checks and restarts
- providing visitor features that depend on live data
An exhibit that only loops local video might need no network at all, and may be more reliable without one. An exhibit that works fully from local files, and uses the network only as an optional extra, can keep running when a connection is lost. That design principle is shared with offline mode work in apps.
Wired connections
Cable is usually the preferred option for fixed exhibits. Wired Ethernet generally offers steady speeds, low delay and fewer interruptions from interference. It is also easier to troubleshoot, because a link either works or it does not.
Points to plan:
- Cable routes. Wiring through floors, walls and plinths needs to be agreed with the building owner early. Retrofitting cable in a finished gallery can be disruptive, and in heritage buildings it may be restricted.
- Cable length. Standard Ethernet has a distance limit, commonly cited as about 100 meters per run, so long galleries may need intermediate switches.
- Spare capacity. Install more points than the current plan needs, since exhibits are often added or moved. Pulling an extra cable during construction usually costs far less than adding one later.
- Power over the same cable. Some devices can receive power through the network cable. This can simplify installation, but the switch must support it and budget its total capacity.
- Labeling. Mark both ends of every cable clearly, and keep a map.
Wireless connections
Wireless is attractive when cabling is impractical: temporary displays, historic rooms, or movable exhibits. Its drawbacks are variable signal strength, interference and shared capacity. Thick walls, metal enclosures and crowds can all weaken signals, and a metal-cased exhibit housing may block them almost completely.
If you rely on wireless:
- survey the signal in the actual space, with the enclosure closed
- place access points deliberately, rather than relying on whatever exists
- avoid putting critical functions on the same network as visitor devices
- test at busy times, since a crowded gallery full of phones can slow a shared network
Wireless is often fine for status reports and light data, and less suited to streaming large video to many screens at once.
Keep exhibits separate from visitor Wi-Fi
Exhibit equipment and public wireless should usually live on separate networks, or at least separate virtual segments set up by whoever manages your network. This protects exhibits from being slowed or disrupted by visitor traffic and reduces the chance that a visitor reaches exhibit computers. The details depend on your setup, so involve your network or IT manager rather than improvising.
Staff accounts and administrative tools deserve extra caution. Do not leave default passwords on any equipment, and keep a record of who can change settings.
Capacity and content
Large files, such as high-definition video, put the heaviest load on a network. Consider copying content to each device in advance, overnight, or by hand with storage media, rather than streaming it live all day. A small scheduled update is easier for a network to handle than constant traffic. This approach is also kinder to slow connections where bandwidth is limited, and it matches how many museums manage content for small devices.
If several screens must stay in step, such as in a video wall, find out how the system synchronizes. Some work from a shared clock, while others depend on constant traffic. Ask suppliers how the system behaves if a connection drops.
Data, privacy and reporting
Exhibits that report usage can help with evaluation, but they carry responsibilities. Decide what data is sent, where it goes and who can see it. Avoid collecting personal information unless it is needed, and be open with visitors about what is recorded. These questions are covered under visitor privacy. Usage figures are also easy to misread, a point discussed in exhibit analytics.
Plan for outages
Networks fail: switches lose power, cables get unplugged and services go down. Consider:
- Should the exhibit keep running if the connection is lost? Usually yes.
- What does the visitor see if content cannot be updated? Ideally, the last working version.
- Who is alerted, and how, when something is offline? Alerts are most useful when someone is responsible for acting on them.
- Is there a backup path for the most important exhibits?
Small uninterruptible power supplies for switches and key devices can bridge brief power losses, though they require checks and battery replacement.
Documentation and ownership
Decide in advance who looks after the exhibit network: the museum’s IT team, a contractor, or the exhibit supplier. Disputes over responsibility often surface only when something breaks. Record network settings, device addresses, cable maps and contact names, and hand them over as part of project handover. Include network upkeep in the maintenance plan, and make sure staff know whom to call. Remote tools described in remote monitoring depend on a connection that you have planned, tested and documented.