Define the spatial interfaces
Identify where equipment, media surfaces, controls and service access meet the architecture and exhibits.
Design and coordination ↗ARCHITECTS & PLANNERS
Give the experience
room to work.
Mad coordinates experience systems with the building and exhibit design. We help the project team define the acoustic, equipment, network, power and access requirements that should inform the drawings, then keep those interfaces connected to the intended visitor experience.
WORKING WITH MAD
Translate the experience into coordinated requirements.
Plan the infrastructure
Develop the system’s power, network, cable pathway, compute and environmental requirements with the relevant consultants.
Coordinate early ↗Keep options visible
Review the implications of wired, wireless and distributed-compute configurations for the particular building and operating model.
Explore the computing foundation ↗PROJECT EVIDENCE
See the specific contribution.
Sound in an open science exhibition
Science Storms at Chicago’s Museum of Science and Industry brings AV and sound design into a space where multiple exhibits share the room.
Read the project ↗A designed visitor environment
The Albert Robles Center combines physical and digital exhibits, with complete English/Spanish changeover throughout the visitor center.
Read the project ↗TECHNICAL DETAILWhat a technology infrastructure brief can include.
Open the engineering detailClose this sectionLook for the red circuit symbol for engineering detail.
| Decision | What to define |
|---|---|
| Space and acoustics | Loudspeaker locations, coverage objectives, acoustic separation, projection geometry and sightlines. |
| Equipment and maintenance | Compute placement, mounting loads, ventilation, heat loads, access clearances and replacement routes. |
| Power and network | Power distribution, data outlets, network responsibilities and cable or wireless performance requirements. |
| Coordination and acceptance | Scope boundaries with MEP, IT, exhibit fabrication, lighting and media teams, plus decisions to be tested or resolved. |
Standard-compute and wireless options do not remove the need to engineer power, networking, cooling or service access. The brief should state which requirements apply to the chosen configuration.
CAPABILITY AND EVIDENCE
A clear scope for your project.
Establish the space, power, network and maintenance access each selected system needs while those decisions are still open. We distinguish delivered systems, working demonstrations and developing functions so that the architectural brief reflects the equipment, interfaces and acceptance requirements of the proposed installation.
LET’S BUILD WHAT COMES NEXT
What does your next decision need?
Tell us the project stage, the people involved and the question you are trying to resolve. We can agree a useful next step.
Start a conversation