"Utilities by customer" is not an interface definition. It does not identify the required service, termination location, approach direction, isolation point, available condition, connection owner or acceptance evidence. "Foundation by others" is equally incomplete when the module drawing does not state its datum, footprint, anchor relationship and required handoff state. A custom booth needs a point-by-point boundary, not a general disclaimer.
Three responsibility groups remain visible throughout this guide. Made by StelBooth covers the agreed structural sheet-metal modules and defined connection hardware. Selected & supplied covers project-specific fans, filters, lighting, controls and other agreed equipment without representing every selected item as StelBooth-manufactured. Prepared on site covers foundations, pits, utilities, local connections, permits, licensed work and other destination responsibilities agreed for the project.
The customer and responsible local designers own the process basis, building conditions, utility capacity, local requirements, risk decisions, permits, licensed design and work, and acceptance of the completed installation. StelBooth can coordinate supplied information into the modular layout, manufacture the agreed kit and provide the contracted assembly or commissioning support. This article does not select utility values, approve a building, authorize local work or claim universal compliance.
1. Freeze the responsibility matrix at item level
Build the matrix around identifiable interfaces. Instead of one row called "electrical," list incoming supply boundary, local disconnect or isolation boundary, control enclosure, field cables, cable support, equipment feeds, grounding or bonding information, instruments and final connection where they exist in the approved scope. Do the same for foundations, exhaust connections, air supply, drains, water, fuel, communications and other project services. Each row should name the design owner, data provider, supplier, installer, connector, checker and acceptance authority.
Separate commercial supply from technical responsibility. An item can be selected and purchased within one coordinated package while its site installation remains licensed local work. A site contractor can install a connection while the selected-equipment supplier still controls its mating requirements. StelBooth can manufacture a structural interface without owning the building structure that receives it. The matrix should preserve these differences rather than forcing one label to cover every action.
Attach a document and revision to every boundary. A utility schedule without an interface drawing can leave position and approach unresolved. A drawing without the current selected-equipment data can freeze an obsolete connection. If a boundary remains provisional, state the missing input, responsible provider, decision date and affected release gate. Do not release adjacent modules on the hope that a later site adjustment will absorb the uncertainty.
Wan and Kumaraswamy studied improvement of building-services coordination at the pre-installation stage [1]. Their construction-management work does not define a spray-booth utility or contract boundary. Its limited relevance is procedural: service interfaces benefit from deliberate coordination before installation, when conflicts can still be resolved through controlled information rather than field rework.
2. Put booth and building information on one site basis
Start with a controlled site plan and survey basis. Identify the building grid or another approved coordinate system, finished-floor reference, project north or orientation zero, booth origin and the elevation used by pits, curbs, bases, doors, ducts and service terminations. State the units and survey status. A scan, photograph or hand measurement can support early planning, but the package should identify what information is verified and what remains reference-only.
Show the complete installation zone, not only the final booth footprint. Include columns, walls, roof or ceiling structure, doors, floor level changes, trenches, existing services, equipment, egress routes and other fixed features supplied by the site team. Identify features scheduled for removal or change and who confirms that work. A clear area in an old drawing is not evidence that the current site is ready.
Use a common origin across the module layout, foundation plan, utility plan and local connection drawings. Avoid redrawing the booth independently on each discipline sheet without a shared reference. Coordinate handedness and viewing direction. A duct shown on the left in one elevation and referenced from the opposite viewing direction in another can create a correct-looking but incompatible set.
Record survey uncertainty and access limitations through the responsible site process. Hidden construction, incomplete finishes, inaccessible areas or continuing work may prevent confirmation. Identify the risk, the next verification point and the module features affected. Do not turn an unverified field dimension into a fabrication datum simply because it appears in a model.
3. Define foundations, floors, pits and anchor interfaces
The responsible project documents should show the site-prepared support boundary, booth footprint, curb or pit geometry where applicable, openings, levels, anchor pattern relationship, edge conditions and the final surface state expected before assembly. They should identify the building or civil design owner and the information StelBooth supplies for coordination. This guide does not calculate foundation or anchor capacity.
Tie every receiving feature to the shared site datums. A foundation plan should not locate anchors only from an unfinished wall that may move or from an isolated module edge whose accumulated position is not controlled. Identify the primary setting references and the method by which the local team transfers them. Where site-drilled anchors are approved, define the controlled layout and conflict-check route rather than leaving drilling to visual alignment.
Coordinate pits, drains, curbs and floor transitions with module installation. Check whether a base channel bridges an opening, whether a floor slope changes panel height, whether waterproofing or finishes alter the receiving surface, and whether local access remains for fasteners and sealing. Identify temporary covers or edge protection required by the responsible site plan without presenting this article as a site safety procedure.
State the readiness condition. The handoff may require the support area to be complete, cleared, cured or otherwise accepted according to the local design and method; those criteria must come from competent local parties. The readiness record should identify the surveyed references, outstanding work and authority that releases module assembly. A delivery date alone is not foundation acceptance.
4. Close electrical and control boundaries connection by connection
List every selected electrical item and the party that provides its approved data. The schedule can include selected fans, lighting, controls, actuators, sensors and other equipment within the agreed package. For each, identify the equipment revision, connection point, location, cable-entry or terminal interface, local isolation boundary, field wiring responsibility and verification owner. Values and protective design must come from the responsible electrical documents.
Separate factory wiring from destination wiring. If an item is prewired within a module, show where that wiring ends and what remains for local connection. If modules use connectors or terminal boxes, identify their mating side, module identity and assembly sequence. If all wiring is local, preserve routes, penetrations, support points and service access in the structural design without implying that StelBooth performs licensed work outside the agreed scope.
Coordinate control responsibility as well as physical wiring. State who provides the approved control philosophy, selected hardware, field devices, interlocks, software or configuration, local integration and final acceptance. This article does not create operating logic or a commissioning test. A structural opening and mounted enclosure can be verified at the factory while the completed control function remains a later project responsibility.
Keep electrical routes out of moving and service envelopes. Door swing, filter removal, fan access, removable panels, lifting paths and later equipment replacement can all conflict with cable support or local enclosures. Lee, Tsai and Kang distinguished visual, approachable and operational accessibility in a design-stage pipeline-maintenance study [2]. Their system is not a booth electrical installation, but the distinction is useful: seeing a terminal is different from reaching and servicing it.
5. Coordinate supply, exhaust and discharge interfaces as one air path
Define where StelBooth's agreed duct, plenum or transition scope ends and the site or another supplier begins. Show the mating geometry, orientation, connection method, support boundary, access and permissible assembly state from approved project information. Identify whether selected fans, dampers, filters or other components arrive installed, ship loose or are provided locally. Do not infer performance from an illustrative module.
Coordinate the route with building structure, roof or wall penetrations, weathering, external support, neighboring services and maintenance access. The local responsible parties own building openings, structural assessment, weatherproofing, discharge location, permits and other destination requirements unless the contract states otherwise. The interface register should name these actions even when they are outside the supplied booth kit.
Show how the connection is assembled. A flange visible in the final model may be unreachable after an adjoining module, ceiling panel or local duct is installed. Identify fastener access, temporary support, seal or gasket responsibility, closure sequence and inspection stage from the approved design. If a flexible connection or field trim is selected, define its controlled range and owner rather than treating it as unlimited correction.
Keep process claims separate from geometric coordination. The customer and responsible specialists define coating process, airflow basis, selected equipment, discharge treatment and acceptance criteria. StelBooth can coordinate the structural and selected-equipment interfaces included in scope. A completed duct connection does not by itself prove process performance or compliance.
6. Schedule every other utility and termination state
Create a utility schedule from the actual project rather than a standard list. It may include water, drainage, compressed air, fuel, heating or cooling services, communications, fire-protection interfaces or other approved needs. For each service, identify its purpose, design owner, source, available condition, required condition, termination point, approach direction, isolation boundary, local connection party, testing responsibility and readiness evidence. Do not publish generic values as project requirements.
Draw termination points in three dimensions and tie them to the site datum. A plan coordinate without elevation can place a service behind a frame or above an inaccessible ceiling. An elevation without approach direction can leave no space for the connection. Include valves, traps, regulators, drains, flexible sections, supports or other selected items only when they are part of the approved project definition.
Coordinate penetrations and sealing responsibilities. Identify which holes or sleeves are Made by StelBooth, which mating items are Selected & supplied, and which building penetrations, local lines and closures are Prepared on site. State who verifies the finished boundary. Avoid uncontrolled field cutting through a module when a service route could have been frozen before fabrication.
Define temporary construction services separately from permanent services. Assembly tools, temporary lighting, lifting equipment or test supplies may need their own site arrangement and owner. Do not assume that a permanent utility is available or suitable for construction use. The responsible assembly method and site plan must establish those needs.
7. Preserve the delivery, laydown and assembly route
Map the complete path from unloading boundary to final module position. Use the packed module envelope, not only the installed geometry. Include transport frames, protection, lifting or handling space, turning areas, doorway constraints, vertical clearances, floor changes and temporary staging. Identify who confirms the current route and when that confirmation occurs relative to dispatch.
Plan laydown around the installation sequence. Modules, hardware and selected equipment should arrive with identities that connect packing to assembly. Reserve space for the next required module and for removal of packaging without blocking the route. If the site cannot store all packages, define the approved delivery sequence and the information needed to release each shipment.
Keep final and temporary site states separate. A wall, local duct or utility that belongs in the completed installation may need to remain open until large modules pass. A permanent platform may be installed after upper connections are complete. The interface and schedule documents should show these dependencies so that one trade does not close the route required by another.
Accessibility research can help teams formalize checks, but it cannot replace a defined task or current geometry. Akanmu, Olayiwola and Olatunji studied automated checking of building-component accessibility for maintenance [3]. Their work supports explicit object and access information; it does not validate the delivery route, lifting method or assembly space for this project.
8. Assign risk, permits and local work to competent parties
List local design, permit, inspection and licensed-work responsibilities explicitly. These can involve building modifications, foundations, utilities, electrical connections, fuel or fire-related systems, lifting, work at height, environmental controls and other destination matters selected by the project. The customer and local responsible parties determine what applies. StelBooth's modular documentation does not replace local professional judgment or legal approval.
ISO 12100:2010 addresses general principles for machinery design, risk assessment and risk reduction [4]. ISO 14122-1:2016 addresses selection of fixed means of access and general access requirements [5]. ISO 6385:2016 addresses ergonomics principles in work-system design [6]. These official records are cited only for their public titles and normative subjects. The complete standards, applicable laws and project assessment control where selected.
Use the risk and responsibility reviews to protect interfaces from late assumptions. A locally selected access platform can obstruct a service door. A building penetration can weaken a required boundary if it is created without the approved detail. A utility termination can create an uncontrolled trip, heat or impact exposure. Return each conflict to the authorized design and local review route rather than solving it informally during assembly.
State the limit of remote or agreed on-site support. Support can clarify the supplied documents and help coordinate contracted checks, but local teams retain the responsibilities assigned to them. Name who directs the work, who can approve a change, who records completion and what happens when site conditions differ from the basis.
9. Use staged readiness gates instead of one delivery promise
Create gates for design freeze, site-information freeze, foundation release, utility rough-in, access-route confirmation, pre-dispatch readiness, receipt and pre-assembly verification. Each gate should list required evidence, open exceptions, responsible reviewers and the decision owner. A green overall schedule does not close an unresolved anchor pattern or missing utility termination.
Use a pre-dispatch site record. It can include dated survey information, current photographs, foundation and anchor checks, route dimensions, laydown confirmation, utility status, remaining building work and named local contacts. Compare the record with the packing and assembly plan before modules leave. If critical site work is incomplete, record the disposition and revised sequence rather than assuming recovery after arrival.
At receipt, check package identity, condition and completeness against the controlled list. Confirm that the site basis has not changed and that temporary works or construction storage have not occupied the planned route. Do not start assembly against an outdated foundation drawing or superseded module plan. Quarantine unclear items and use the agreed clarification path.
Close the handoff with staged records. Factory evidence can cover module identity and agreed fabricated interfaces. Site evidence covers prepared features, local connections, assembly state and destination work. Commissioning evidence covers only the criteria and scope actually agreed. Keep these boundaries visible so that completion of one stage is not presented as proof of every downstream condition.
10. Use a site-interface release checklist
| Interface layer | Question before release | Required project evidence |
|---|---|---|
| Responsibility | Who designs, supplies, installs, connects, checks and accepts each item? | Item-level boundary and contact register |
| Site basis | Do booth, building, foundations and services share datums and orientation? | Controlled plan, elevations and survey status |
| Foundations | Are support, pit, curb, anchor and finished-surface relationships defined? | Approved local design and readiness record |
| Electrical | Where does factory scope end and licensed destination work begin? | Equipment schedule, single boundary map and field-connection plan |
| Air path | Do ducts, fans, building openings and supports form an accessible interface? | Coordinated route, mating details and responsibility schedule |
| Other utilities | Are service, termination, approach, isolation and test owners identified? | Project utility and interface schedule |
| Delivery | Can every packed module reach its position in the required sequence? | Route, laydown, package and delivery plan |
| Local work | Which permits, licensed activities and risk controls remain destination duties? | Local responsibility and approval record |
| Readiness | What evidence releases dispatch, receipt and assembly? | Staged gate checklist with open exceptions |
| Change | How are site differences and revised interfaces approved? | Clarification, revision and disposition route |
Review the checklist from both directions. Start at each booth interface and trace outward to the building or utility source. Then start at every site-prepared termination and trace inward to the exact module or selected equipment it serves. The two paths should meet at the same coordinate, product state, responsibility and document revision.
The useful deliverable is a controlled site-interface package: common datums, item-level responsibility, selected-equipment information, foundation and utility boundaries, delivery and assembly routes, staged readiness evidence and a change process. It is not a generic promise that any prepared space or utility arrangement will suit the custom booth.
For an initial review, provide the current site plan, photographs or survey status, workpiece and process basis, desired supply scope, destination, building constraints, foundation or pit concept, known utilities, access route, local responsible parties and target installation state. StelBooth can then identify which inputs must be frozen before structural modules and interface details are released.
References
- S. K. M. Wan and M. M. Kumaraswamy, "Improving building services coordination at the pre-installation stage," Engineering, Construction and Architectural Management, 2012. https://doi.org/10.1108/09699981211219580
- C.-H. Lee, M.-H. Tsai and S.-C. Kang, "A visual tool for accessibility study of pipeline maintenance during design," Visualization in Engineering, 2014. https://doi.org/10.1186/s40327-014-0006-y
- A. A. Akanmu, J. Olayiwola and O. A. Olatunji, "Automated checking of building component accessibility for maintenance," Automation in Construction, 2020. https://doi.org/10.1016/j.autcon.2020.103196
- ISO, "ISO 12100:2010 - Safety of machinery - General principles for design - Risk assessment and risk reduction." Official ISO record.
- ISO, "ISO 14122-1:2016 - Safety of machinery - Permanent means of access to machinery - Part 1: Choice of fixed means and general requirements of access." Official ISO record.
- ISO, "ISO 6385:2016 - Ergonomics principles in the design of work systems." Official ISO record.