Whole museum customization should not enter procurement or design approval until the project team has confirmed six groups of requirements: the venue purpose and audience, the building and local compliance inputs, the content and visitor journey, the technical and manufacturing acceptance criteria, the site and delivery interfaces, and the operating and handover needs. These requirements let owners compare proposals on the same basis and prevent a visual concept from being mistaken for a buildable scope. DEEPBLUE can connect planning and design, R&D and manufacturing, engineering construction and sustainable operation, but the owner and qualified local professionals must still confirm project-specific approvals, building conditions and responsibilities. The framework below explains what information should exist, who should own it and what evidence should be approved before the next commitment.
1. Start with an owner-approved project definition and decision brief
The first requirement is a single project definition that the owner, designer, procurement team, manufacturer, site team and future operator can all recognize. It should name the venue type, location, building status, approximate public area, priority audiences, educational or family-experience purpose, intended opening window and the scope being explored. It should also identify decision makers, available budget information, known constraints and the documents that already exist. A children's museum, a science center gallery and a family exploration venue may use similar interactive elements, but they require different content depth, visit patterns, staffing and operating support. Without an approved definition, suppliers will price different assumptions and their offers will not be meaningfully comparable.
Turn the brief into decision criteria. State what the project must achieve in observable terms: a coherent visitor journey, appropriate age and accessibility choices, coordinated exhibit and building interfaces, maintainable products, usable operating information and a practical opening-readiness path. Do not substitute attendance, revenue or learning promises for project requirements; those results depend on market, management and evidence beyond the supplier's scope. Record exclusions as clearly as inclusions. If catering, ticketing systems, base-building work, local permitting or another package is outside the requested scope, say so before proposals are prepared.
The approval record should show the brief version, open questions, assumptions and the person authorized to accept changes. That does not require a complex software system; a controlled document and issue log are enough if everyone uses them. Require suppliers to list deviations instead of silently filling gaps. The first gate is complete when every bidder or project party is responding to the same purpose, scope boundary, evaluation criteria and source information. This creates a defensible basis for design and procurement without pretending that early information is already final.
2. Provide verified building data and assign local compliance responsibilities
Whole-venue customization depends on the real building. Provide current plans, surveys and photographs; clear dimensions and levels; structural information; floor and wall conditions; access routes, doors and lifts; power, data, lighting, ventilation, water and drainage information where relevant; loading and fixing restrictions; and the status of base-building work. Mark what has been verified and what remains an assumption. A beautiful layout can fail at site if a transport module cannot enter, an electrical point is missing, a floor cannot accept the proposed load or drainage is shown where none exists.
Create a responsibility matrix for architecture, structure, fire protection, electrical and mechanical systems, accessibility, materials, permits, inspections and public operation. These duties vary by destination and must be assigned to qualified parties authorized for that market. An overseas museum supplier may coordinate information and provide exhibit engineering, but whole-museum language does not automatically transfer every regulated responsibility. The owner should name the local architect, engineers, contractor, authorities and operator contacts, then define which interfaces require their written review before design release.
Ask for an interface register that converts building information into project actions. Each entry should identify the exhibit or zone, required utility or support, source drawing, responsible party, due date and approval status. Changes to one discipline should trigger review by affected parties. The building-input gate is complete when the project team has an agreed baseline, unresolved surveys are planned, regulated decisions have qualified owners and major interfaces can be traced from the venue plan to the party responsible for confirming them.
3. Define content, visitor and operating requirements before selecting products
A customization requirement should describe what visitors need to do, not merely what equipment should be purchased. Define priority age ranges, family and school-group needs, accessible participation, expected visit patterns, the balance between active and reflective experiences, and the relationship between free exploration and facilitated programs. Organize themes into a content hierarchy and map the visitor journey from arrival through orientation, active zones, quieter discovery, family support, learning activities and departure. This gives each proposed exhibit a reason to exist and reduces the risk of decorating a space around a catalogue.
For every key experience, record the visitor action, intended feedback, participant capacity, approximate footprint, supervision assumption, reset behavior, loose parts or consumables, sound or water effects, cleaning need and maintenance access. State how the experience connects to the theme and neighboring activities. Also define the content and graphics languages, reading levels and media requirements. These entries become design inputs and later acceptance points; they allow the owner to ask whether the approved experience was actually developed rather than only checking whether an object was delivered.
Include operating assumptions now. Identify staff roles, sightlines, storage, preparation areas, daily opening and closing checks, cleaning, basic troubleshooting and escalation. XPLOPLO gives DEEPBLUE a real venue for observing how visitors, staff and exhibits interact, but its plan is not a universal template. Each owner must define the local operating model and resources. This gate is complete when the content brief, visitor journey, zone schedule, experience requirements and operating assumptions are mutually consistent and have named owners.
4. Set design, prototype and manufacturing acceptance evidence
Design approval needs a defined package. At concept stage, require a plan, zoning and circulation logic, content structure, exhibit schedule, visual direction, preliminary material and system assumptions, building interfaces, operating implications, budget alignment and an issue list. At design development, require coordinated dimensions, materials, mechanisms, controls, digital interfaces, graphics, lighting coordination, service access, replaceable parts, transport modules and relevant calculations or specifications. Agree which documents control when a rendering, drawing and schedule appear to conflict.
Prototype requirements should focus on uncertainty. Specify what question the prototype must answer—reach, force, timing, stability, feedback, reset, software flow, finish or cleaning—and how acceptance will be recorded. A photograph of a sample is not enough when the decision concerns function. Likewise, manufacturing approval should identify production drawings, approved materials and finishes, inspection points, change control, assembly and functional checks, documentation, module identification and packing readiness. Factory size and general capability support confidence, but evidence must remain tied to the items being built.
Define who may approve, approve with comments or reject each package, and how open items carry forward. Independent or destination-market testing remains with the qualified parties assigned to it; factory checks must not be described as universal certification. The release gate is complete only when the owner can trace the approved intent into buildable information, the uncertain functions have been tested appropriately, changes are controlled and the manufacturing team is working from one current set of documents.
5. Confirm delivery, handover and lifecycle requirements before commitment
Procurement documents should define delivery interfaces before price and schedule are treated as comparable. Confirm transport assumptions, packaging, labels, access and lifting constraints, site storage, base-building readiness, local labor, installation supervision, utilities, protection, sequencing with other trades and the method for reporting site differences. State which party bears each dependency and how delay caused by missing inputs will be handled. A site-readiness checklist should be project-specific and linked to drawings rather than copied from a generic form.
Handover requirements should include installed functional checks, issue close-out, as-built or final documents where applicable, operating instructions, inspection and cleaning guidance, reset and troubleshooting information, spare and wear-part information, training scope and escalation contacts. Define what the future operator must be able to do after training. Include a route for recording recurring faults and operational observations so useful evidence can reach designers and manufacturers. Sustainable operation is not a guarantee of commercial performance; it is a managed connection among purpose, people, products, maintenance and responsible renewal.
Before final commitment, ask for an assumptions register covering budget, programme, approvals, owner inputs and third-party work. Confirm what could change the price or dates and what evidence will be required to authorize a change. The project is ready to proceed when requirements are specific enough for comparable proposals, responsibilities are assigned, acceptance records are defined and unresolved issues are visible. DEEPBLUE can then assess the connected scope across planning, manufacturing, construction support and operation preparation using real project information rather than guesses.
Owner input and approval checklist
- Approved project definition, audience, purpose, scope and exclusions
- Current building drawings, surveys, utilities, access and site status
- Responsibility matrix for owner, supplier, local professionals and operator
- Content hierarchy, visitor journey, zone schedule and experience requirements
- Design-stage deliverables, controlling documents and approval authority
- Prototype questions, acceptance methods and records
- Manufacturing release, inspection, testing and change-control evidence
- Packing, transport, site-readiness and installation interfaces
- Handover, training, maintenance, spares and escalation requirements
- Budget, schedule and third-party assumptions with change triggers
Frequently asked questions
What is the minimum information needed for an initial assessment?
Provide the venue type and location, approximate area, building status, audience, purpose, target opening window, desired scope and any drawings or budget assumptions already available. Unknowns should be labelled rather than guessed.
Can a supplier complete the requirements brief for the owner?
A supplier can facilitate workshops and structure the brief, but the owner must confirm objectives, decision authority, available resources and local responsibilities. Qualified local professionals must confirm regulated building and approval matters.
Should procurement begin before concept design is complete?
Early market engagement can test capability and assumptions, but comparable commitment requires a common brief and defined deliverables. Otherwise proposals may contain different scopes, exclusions and unpriced interfaces.
Do factory tests replace local compliance checks?
No. Factory checks verify agreed product information and functions. Tests, approvals or inspections required by the destination market remain with the qualified parties and authorities assigned to them.
What should owners send DEEPBLUE first?
Send the project brief, city and venue type, approximate area, drawings or site information, target audience, opening goal, expected service scope and the main questions that the assessment must answer.
