How a modular booth is divided for shipping and local assembly

A modular booth is not divided by applying a standard panel size to every project. Its boundaries emerge from the approved layout and the practical route from manufacture to the assembled state. A division that looks convenient on a general arrangement may be unsuitable if it hides a connection, blocks installation of selected equipment, creates an inaccessible fastening step or cannot follow the destination route. The project therefore needs a module map, not merely a count of pieces.

The map should explain what each unit contains, which adjacent unit it meets, what must happen before and after that connection, and which party performs the work. It should also distinguish a structural module from loose connection hardware, selected equipment, local services and site construction. With those relationships visible, packing and assembly information can refer to the same controlled structure.

Published work on assembly-oriented design links product structure engineering with assembly sequence planning [1]. That research supports reviewing divisions and sequence together. It does not prescribe a spray-booth module dimension, fastening arrangement, lifting method or local installation procedure. Those choices must come from the project design, destination conditions and responsible parties.

1. Begin with the finished system, then describe its assembly states

Start with the approved functional arrangement: enclosure, ceilings, doors, frames, plenums, ducts or transitions, filter supports, access structures and equipment interfaces within scope. Identify the relationship that must exist in the finished state. Then work backward through the states needed to reach it. A state may show a base or frame established, an enclosure zone closed, a plenum connected, a selected equipment item installed, or an access panel left open for a later task.

Each state should answer three questions. What is stable and available at its start? Which module, connection or item is added? What access or reference must remain available for the following state? This exposes dependencies that a single final-view drawing can hide. It also gives the site team a way to understand why a module carries a particular identifier and why some loose items belong with a later step rather than the first visible location.

Do not assume the most obvious physical split is the best assembly split. A large wall face might be divided because of the delivery path, while a smaller interface zone might remain a distinct subassembly because it coordinates several later connections. Conversely, pieces that could be separated geometrically may be better shipped together when the project design and handling review support that state. The decision remains specific to the real structure and route.

Assembly-state planning should include selected equipment even when StelBooth does not manufacture it. If an item can be installed only before another module closes access, its state belongs in the sequence. If an item arrives separately or is sourced locally, the plan must show the hold point and owner without pretending that it is part of StelBooth's fabricated structure.

2. Choose boundaries that preserve functions and interfaces

A useful boundary separates work without losing control of the relationship across it. For each proposed split, list the structural function, attached or adjacent features, datum or reference logic, joining access, alignment need, sealing or closure detail where applicable, and any equipment interface that crosses the boundary. The final design should define these details; this article deliberately supplies no generic joint or tolerance.

Research on product architecture describes modules through relationships between functions and components [3], while a broader review of product modularity discusses definitions and reported benefits across the literature [4]. These papers support treating interfaces as part of the module decision. They do not show that more divisions are always better or that a particular booth architecture will produce a promised outcome.

More pieces can reduce the size of an individual transport unit, but they also create more identities, joints and assembly activities to control. Fewer pieces may simplify some connections while making access or handling more demanding. Neither direction is a universal target. The project should compare alternatives against the delivery route, available assembly space, intended handling, structural design, selected equipment states and the site team's capability.

Use a boundary review to catch awkward hybrids. Examples include a transition divided from the plenum without a clear reference, a door module whose frame cannot be set before neighboring walls, or a support delivered loose without showing the equipment it serves. These examples are questions to investigate, not standard design faults. The controlled project drawings decide whether a particular arrangement is acceptable.

3. Keep the three responsibility boundaries on the module map

Shipping documents should not turn every delivered object into a StelBooth-manufactured item. Use the same responsibility language from quotation through packing and destination handoff:

The table should be supplemented by an item-level schedule. A piece fabricated by StelBooth can meet an item selected and supplied within the package, while both depend on a site-prepared service or support condition. Showing all three on one interface record prevents a physical connection from being mistaken for a transfer of design, installation or regulatory responsibility.

Local purchases need the same discipline. If the customer plans to source an item at the destination, record the information that must be approved before StelBooth releases the mating interface. Do not leave a generic opening and assume an unknown local item will fit. Equally, do not publish a supplier, model or interface value before the project has selected and approved it.

When scope changes, revise the responsibility schedule and every affected drawing, packing list and assembly note. A commercial change alone is insufficient if the site team still holds an earlier technical package. Name the current revision and withdraw or mark superseded information through the agreed document route.

4. Map the route from packing position to final location

The destination survey should follow the physical journey. Record the unloading area, external approach, building openings, internal turns, overhead and side obstructions, floor conditions, staging zone and final assembly position. Photographs need orientation and scale supplied by the project; isolated images without a route reference can be misleading. Confirm which conditions are existing and which will change before delivery.

Ask the customer or local installation party to identify its proposed handling resources and any restrictions on their use. StelBooth can then review module divisions and handling features against that declared plan. The review must remain project-specific. This page does not state a lifting capacity, center-of-gravity rule, transport limit or rigging method.

Consider the return route for packaging, temporary supports and handling devices as well as the incoming module. A staging area that can receive the first unit may become blocked after several units are placed. Sequence sketches should show where remaining packages wait and how the next item reaches its position. If the site cannot reserve enough space, the packing groups and delivery order may need a different plan.

Record route assumptions as release conditions. If a doorway, pit, foundation or roof opening is unfinished when the kit design is reviewed, state who will confirm the as-built condition and when that confirmation is required. An unverified site promise should not silently become a fixed manufacturing input.

5. Control every connection and the access needed to make it

Create a connection register tied to module identifiers. For each connection, record the two sides, drawing reference, supplied and local items, required assembly state, access direction, responsible installer, required check and evidence defined by the project. The level of detail should match the connection. The register is an index to controlled information, not a replacement for drawings or approved procedures.

Accessibility research in design for assembly examines how component access relates to assemblability [2]. The paper supports making access an explicit design consideration; it does not define an acceptable clearance or installation method for this booth. The project review should use the actual connection, tools, neighboring geometry, handling plan and installer responsibilities.

Check access across time. A connection visible in the empty structure may be hidden after a filter support, light, control enclosure or duct transition is installed. A selected equipment item may require its own installation and future service route. Mark which panels or openings remain temporary during assembly and who authorizes their closure. If temporary removal is part of the plan, identify how the part returns to its controlled location.

Connection hardware should retain its relationship to the joint. Use package and item identifiers that trace back to the connection register. Avoid relying only on appearance; similar pieces can serve different positions. Where orientation matters, show it in the project information rather than asking the local team to infer it from a photograph.

6. Make identification and packing serve the assembly sequence

A packing list should bridge the factory release and the site plan. Group information by package, then list each module, loose item, selected equipment item and document set inside it. Include the controlled identifier, quantity and intended assembly zone or state. Keep the manufactured-versus-selected distinction visible so receiving personnel know which documentation and responsibility follow each item.

Loading order, unloading order and assembly order are related but may not be identical. Review all three instead of promising that one sequence automatically satisfies the others. An item needed late in assembly may still need early inspection after arrival; a package unloaded first may need to remain closed until the staging area is ready. The agreed plan should state these relationships and provide a route for deviations.

ISO 780:2015 specifies graphical symbols for handling and storage of distribution packages when that standard is invoked [5]. Its official record is cited only for that normative subject. The project must select the applicable marking framework and determine which symbols, words, languages and handling information are required. A symbol does not replace the project-specific handling plan or make an unsuitable package safe.

Protect identity as well as condition. Labels should remain associated with the item through unpacking and staging, and the packing list should provide a controlled method for reporting a missing, damaged or uncertain item. Do not encourage site personnel to substitute similar-looking hardware or modify a module without an approved disposition. Photographs can support receiving records, but they should show the identifier and context needed to connect the image to the item.

7. Prepare the site team before the first package opens

The customer should name the local assembly lead, site coordinator and people authorized to resolve design, equipment and commercial questions. Confirm the working language, document access, communication method and expected response path. If remote support is included, define the information the site team should provide when raising an issue. If agreed on-site support is included, define its scope separately; attendance does not transfer responsibility for local construction, licensed work or the installer's execution.

Before assembly, compare site readiness with the release conditions. Foundations, pits, access routes, utilities, local connections and permits under Prepared on site should be at the agreed state. Selected equipment that must enter an early assembly state should be present, identified and supported by its applicable information. The Made by StelBooth modules should be received against the packing list, with exceptions recorded before they are dispersed around the site.

Use a start-of-state check rather than one broad statement that the whole site is ready. A later zone may remain under preparation while an earlier, independent zone proceeds, but only when the approved sequence permits it. Record the decision and prevent work in one area from consuming access, references or items needed elsewhere.

At each hold point, capture the evidence agreed for the project. That may include an identified photograph, a completed check entry, a measurement from the responsible party or an approval to continue. This article does not define the evidence or acceptance value. The customer requirements, controlled design and agreed assembly plan must do that.

8. Keep drawings, lists and site status on the same revision

The general arrangement, module map, connection register, packing list and assembly sequence describe different views of one delivery. Their identifiers should allow a user to confirm that the views belong together. ISO 16792 specifies digital product-definition data practices when invoked [6], and ISO 7200 specifies data fields for title blocks and document headers when selected [7]. These standards support definition and identification; they do not validate the project's technical content.

ISO 11442 specifies basic rules for technical-document management when adopted [8]. Apply the project's chosen control method to site markups and dispositions as well as factory drawings. If a connection changes during assembly, record the approved outcome, identify affected modules and documents, and state whether later work can continue.

Do not hide departures inside an informal chat thread. A photograph or message can explain an issue, but the approved decision should enter the controlled record used by the people doing the work. Likewise, as-built information should represent authorized final conditions, not every temporary mark made during installation.

Handover closes the sequence only when the agreed responsibilities and records are complete. Separate incomplete site work, pending selected-equipment matters and StelBooth structural items rather than reporting one ambiguous overall status. That preserves a truthful basis for commissioning support and later operation.

9. Questions to close before release for packing

• Does the module map match the current approved layout and responsibility schedule?
• Has the destination route been reviewed against every proposed transport unit?
• Does each connection have an identifier, drawing reference, access state and owner?
• Are selected equipment installation states visible without calling those items StelBooth-made?
• Are foundation, pit, utility, local connection and licensed-work prerequisites assigned?
• Do package identifiers trace to modules, loose items, connection hardware and documents?
• Have loading, unloading, receiving, staging and assembly sequences been compared?
• Can the local team identify the current revisions and raise a controlled issue?
• Are checks, hold points and handoff records defined by the actual project?

Closing these questions does not make every project identical. It makes the chosen project divisions explainable from manufacture through local assembly.

References

The peer-reviewed papers support only the cited general relationships among product structure, modularity, accessibility and assembly-sequence planning. They do not provide module sizes, joints, handling instructions or acceptance criteria for a spray booth. The official standards support normative marking and technical-document subjects only when the customer or contract invokes the applicable edition; listing them does not claim certification or project conformity.

1. F. Demoly, X.-T. Yan, B. Eynard, L. Rivest and S. Gomes, “An assembly oriented design framework for product structure engineering and assembly sequence planning,” Robotics and Computer-Integrated Manufacturing, 27(1), 33–46, 2011. https://doi.org/10.1016/j.rcim.2010.05.010
2. H.-Y. Hsu and G. C. I. Lin, “Quantitative measurement of component accessibility and product assemblability for design for assembly application,” Robotics and Computer-Integrated Manufacturing, 18(1), 13–27, 2002. https://doi.org/10.1016/S0736-5845(01)00020-5
3. R. B. Stone, K. L. Wood and R. H. Crawford, “A heuristic method for identifying modules for product architectures,” Design Studies, 21(1), 5–31, 2000. https://doi.org/10.1016/S0142-694X(99)00003-4
4. J. K. Gershenson, G. J. Prasad and Y. Zhang, “Product modularity: Definitions and benefits,” Journal of Engineering Design, 14(3), 295–313, 2003. https://doi.org/10.1080/0954482031000091068
5. ISO 780:2015, Packaging — Distribution packaging — Graphical symbols for handling and storage of packages. Official ISO record.
6. ISO 16792:2021, Technical product documentation — Digital product definition data practices. Official ISO record.
7. ISO 7200:2004, Technical product documentation — Data fields in title blocks and document headers. Official ISO record.
8. ISO 11442:2006, Technical product documentation — Document management. Official ISO record.