What to share before a custom spray-booth layout begins

A clear requirement is enough to begin. A custom modular booth does not begin with a model number, and the first project brief does not need to imitate a finished engineering specification. Its job is to expose the conditions that shape the layout and the decisions that still need an owner. That gives the customer and StelBooth a shared basis for asking useful questions before geometry, equipment interfaces or shipping divisions are treated as settled.

A good opening package can be short. It may contain a workpiece photograph, a sketch of the available area, a description of the coating activity, a list of requested module groups and a note about who will assemble the kit. The value comes from clarity, not volume. State which information is confirmed, which is an estimate for discussion and which is not yet known. A confident-looking invented value can send several downstream decisions in the wrong direction; an explicit unknown invites the right review.

Research on design for manufacture and assembly treats manufacturing and assembly considerations as design inputs rather than checks added after a product is complete [1]. Research on modular product architecture likewise describes modularity through relationships among functions, components and interfaces, not merely through the appearance of separate pieces [2]. Those general findings support an early, structured brief. They do not determine a spray-booth layout, equipment choice or project acceptance criterion.

1. Describe the workpiece and the process outcome

Begin with the item or family of items that must pass through the booth. Identify the largest expected workpiece envelope, but also explain whether the range includes substantially different shapes. State how each item reaches the working position, how it is supported, whether it turns or remains fixed, and which faces need practical operator or applicator access. If a carrier, trolley, rail or conveyor is already part of the customer's process, show its relationship to the workpiece rather than describing the item alone.

Photographs and sketches should include context. A close view may show a surface, while a wider view can reveal handling points, protrusions, doors, lifting devices or surrounding obstructions. Mark the view direction and distinguish a representative item from the maximum design case. If dimensions are provisional, label them accordingly. StelBooth can then separate questions about the structural envelope from questions about movement, process clearance and site handling.

Describe the finishing activity in operational language. Explain what is applied, how the work enters and leaves, whether the operation is normally intermittent or follows a repeated flow, where people need to stand, and what cleaning or changeover activities the layout must accommodate. Record the customer's process authority and the party responsible for defining process parameters. Do not insert guessed airflow, temperature, efficiency or production values simply to fill a form. Those values, when required, must come from the actual process basis and the responsible project review.

The first brief should also identify variability. A layout intended for one stable workpiece presents different questions from a layout expected to serve a changing family of products. List the foreseeable variations without claiming that every future item is covered. This lets the design discussion distinguish current requirements from optional allowances and prevents an undefined future possibility from silently becoming a present commitment.

2. Make the destination visible early

The booth will meet a real building, access route, foundation or pit condition, utility system and local regulatory environment. Show the usable installation area rather than only the total room size. Identify nearby columns, walls, doors, roof members, existing equipment, traffic paths and areas that must remain accessible. State whether the proposed position is indoors or outdoors and whether the site has an assembly zone where delivered modules can be sorted before installation.

Delivery access and installation access are related but not identical. A vehicle may reach the building while a large module cannot pass through the final doorway or turn along the internal route. Share photographs or a simple route sketch from unloading point to assembly position. Note lifting restrictions, floor conditions and any planned building work that could change the route. The design can then consider module divisions against the real path instead of discovering the conflict after packing.

List the utilities that the site expects to provide and identify who will define and complete each local connection. The opening brief need not contain final electrical or service design, but it should show where the boundary is believed to sit. Foundations, pits, building penetrations, permits and work requiring a locally authorized party remain destination matters unless the written project scope says otherwise. A blank responsibility cell is not a neutral detail; it is an unresolved interface that should be assigned before release.

Destination country or region matters because local review, permitted work, documentation, travel planning and commissioning arrangements can differ. This does not turn the first brief into a claim of jurisdictional compliance. It tells the project team which questions require the customer's local authority, designer, contractor or other responsible party before the supply package can be finalized.

3. Separate structure, selected equipment and site work

A useful brief says what the customer wants StelBooth to coordinate. That may be the structural enclosure only, selected module groups, or a broader package that also includes project-specific generic equipment. The answer can remain provisional during the first conversation, but the current assumption must be visible. Otherwise one party may price a structural kit while another expects a complete destination installation.

Use three responsibility columns throughout the project, not only in the commercial quotation. The names make an important distinction between manufactured structure, bought-in equipment and destination work:

“Selected & supplied” does not mean “manufactured by StelBooth.” It means that an item can be included within the agreed procurement and interface package while retaining its true equipment identity and documentation. Likewise, “Made by StelBooth” should not absorb local construction or licensed connections simply because the booth structure must meet them. Each interface needs a drawing, schedule, note or other controlled definition that both sides can review.

The boundary may change while the project develops. Record every approved movement between columns and identify its effect on drawings, equipment information, packing, site work and support. Engineering-change research shows that a change can propagate through connected parts and tasks rather than remain isolated at its point of origin [4]. The paper supports the need to review connected decisions; it does not predict the effect of any particular booth change.

4. Explain movement, access and the expected assembly state

Describe how the customer expects the workpiece, operators, maintenance personnel and replaceable items to move around the finished system. Separate normal production access from installation access and later service access. A door that is convenient during daily work may not provide the route needed to install a selected equipment item. Conversely, an assembly opening may be closed once the related module or connection is complete. These states should be discussed explicitly.

Local assembly also changes how the structure is divided. The delivered kit needs joints that can be identified, reached and completed in the intended sequence. Published assembly-oriented design research connects product structure engineering with assembly sequence planning [3]. For this project, that general principle means the module map, joint map, access plan and packing logic should be reviewed together. It does not prescribe a module size or assembly method.

State who is expected to perform assembly and what tools, lifting arrangements or local materials that team expects to provide. At the brief stage, it is acceptable for details to remain open. What matters is avoiding the false assumption that “local assembly” is a complete plan. The final project package should distinguish supplied connection hardware from locally sourced consumables, temporary works and equipment, and should identify any activity that requires a qualified local party.

If the customer has a preferred sequence because of building access or production shutdown constraints, describe it early. Treat it as an input for feasibility review, not an automatic promise. StelBooth can compare the requested sequence with the structural divisions, equipment installation states and available access, then document questions before release.

5. Define equipment by function and interface before naming a package

For every fan, filter group, lighting item, control element or related generic item requested within the supply scope, begin with the project function and the responsible source of requirements. Identify where it connects to the fabricated structure, what space must remain available for installation and service, what local connection is expected, and which party will approve the selected item. A list of equipment nouns without interfaces is not yet a coordinated package.

Separate confirmed information from selection work. The customer may already nominate an item, may provide a performance basis for StelBooth to use during selection, or may ask StelBooth to coordinate a suitable project-specific option. Those paths create different approval and documentation needs. The brief should state which path applies to each item. It should also record whether any equipment will be free-issued, purchased locally or installed by another contractor.

Do not treat a visible mounting opening as the complete interface. Coordination may involve support points, transition geometry, access for replacement, connection direction, controls signals, local services and the document set required at handoff. Exact details depend on the real equipment and site. The website cannot replace the selected equipment data, controlled project drawings or the review of the responsible process, electrical and local authorities.

A useful first submission can therefore ask for equipment schedules already in use, preferred documentation language, available local service information and any customer-mandated selection constraints. If none exists, say so. The next action is to define the selection basis, not to fill the gap with an invented model, supplier or performance claim.

6. State how assembly and commissioning support should work

Local assembly is not the same as leaving the customer with a collection of unidentified panels. Ask who will receive, store and assemble the kit, what experience that team has, which document language and format it can use, and how questions should be raised. Confirm whether the customer expects remote review, agreed on-site assistance, or a different support boundary. Any travel or site attendance remains subject to a specific agreement rather than an unconditional website promise.

The support plan should follow the actual supply split. StelBooth can explain and review the structural kit and the coordinated interfaces within its scope. The selected equipment documentation should identify the equipment source and applicable instructions. The site team remains responsible for the foundations, pits, utilities, local connections, permits, licensed work and other destination tasks assigned to it. A support conversation should not blur those ownership lines.

Commissioning support needs a project-defined basis. Before work begins, list the installation state to be reviewed, the selected equipment and control functions within scope, the records required at handoff, the party responsible for each check, and the method for resolving an incomplete or disputed item. Acceptance criteria must come from the approved design, equipment information, customer requirements and governing local review. This article does not publish a generic commissioning standard.

Also identify the practical communication route. Name the people authorized to answer design, site and commercial questions. Decide how photographs, marked-up drawings and issue lists will be exchanged. A clear route prevents an installer from relying on an informal message that has not been reviewed by the appropriate authority.

7. Keep unknowns visible and revisions controlled

A first brief will contain gaps. Create an open-item register with a short description, an owner, the information needed, the decision that depends on it and the current status. Avoid invented deadlines or automatic default answers. Prioritize an item by its effect on the next release: a missing site opening may block module division, while a later labeling preference may not affect early geometry.

When drawings or models are exchanged, every controlled issue should identify the project, document, revision, status and responsible issuer. ISO 16792 specifies requirements for digital product-definition data practices when its framework is invoked [5]. ISO 7200 specifies data fields for title blocks and document headers when selected [6]. These standards support document definition and identification; they do not supply missing booth requirements or make an unapproved layout suitable for fabrication.

Use a simple change statement whenever a confirmed input moves: what changed, why it changed, who approved it and which documents, modules, equipment interfaces, packing tasks or site activities require review. ISO 11442 specifies basic rules for managing technical documents when adopted [7]. Document control helps people use the intended information, but it does not replace engineering judgment or customer approval.

Finally, label maturity honestly. “For discussion,” “for interface review,” “for approval” and “released for the agreed work” are different states. The exact status vocabulary can be agreed for the project, but no one should infer fabrication authority from a preliminary image or marketing illustration.

8. A concise first-brief checklist

• Workpiece type, range, largest expected envelope, support and movement method.
• Coating or finishing activity, operating pattern and responsible process authority.
• Usable site space, internal delivery route, assembly area and known obstructions.
• Foundation or pit condition, utilities, local connections and destination region.
• Requested module groups and the current Made by StelBooth boundary.
• Items expected under Selected & supplied, with a source for selection requirements.
• Foundations, permits, licensed work and other tasks under Prepared on site.
• Local assembly owner, available handling plan and expected support arrangement.
• Drawings, photographs, equipment information and notes already available.
• Known unknowns, decision owners, document status and approval route.

Once these points are visible, the next conversation can focus on decisions that materially shape the custom modular layout. A concise, truthful brief is more useful than a complete-looking package built on assumptions that no responsible party has approved.

References

The peer-reviewed papers below support only the cited general relationships among design for assembly, modular product structure, assembly sequence and change propagation. They do not provide a spray-booth design, equipment selection or project acceptance basis. The official standards support normative product-definition and document practices only when the customer or contract invokes the applicable edition; listing them does not claim certification or universal applicability.

1. G. Boothroyd, “Product design for manufacture and assembly,” Computer-Aided Design, 26(7), 505–520, 1994. https://doi.org/10.1016/0010-4485(94)90082-5
2. 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
3. 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
4. P. J. Clarkson, C. Simons and C. Eckert, “Predicting Change Propagation in Complex Design,” Journal of Mechanical Design, 126(5), 788–797, 2004. https://doi.org/10.1115/1.1765117
5. ISO 16792:2021, Technical product documentation — Digital product definition data practices. Official ISO record.
6. ISO 7200:2004, Technical product documentation — Data fields in title blocks and document headers. Official ISO record.
7. ISO 11442:2006, Technical product documentation — Document management. Official ISO record.