What a Chemical Tank Drawing Handoff Needs

01 / Name the design authority

A chemical-tank drawing handoff is not merely a transfer of CAD files. It is a transfer of an approved product definition into manufacturing. Before the package reaches quotation, name the organization and person responsible for the process design, operating conditions, medium, capacity, overall geometry, design pressure, governing requirements and interfaces. Also identify who can answer technical questions and who can approve a change.

That ownership remains with the customer or its appointed design authority. StelTank reviews the supplied definition for manufacturability, plans fabrication and welding, coordinates frames and agreed valve or interface work, assembles the agreed scope, and performs the checks stated in the approved package. A manufacturing comment can expose a conflict or propose a practical alternative. It cannot silently redefine the process duty or certify that missing service inputs are acceptable.

State the intended deliverable in one paragraph. Is the order for a tank body, a tank with supports, or a complete assembly that includes a frame and named interface items? Which components arrive from the customer or another supplier? Which items are installed, shipped loose or excluded? An explicit scope paragraph lets every later drawing note be read against the same boundary.

If confidentiality limits the first exchange, begin with a controlled project overview: equipment type, design maturity, broad geometry, manufacturing scope, interface count, required checks and the questions that need DFM review. An NDA can be executed before detailed models and drawings are sent. Confidentiality changes the exchange route; it does not justify guessing at withheld technical requirements.

Put open decisions in a register rather than embedding assumptions in an email chain. A field such as "test procedure: customer to issue" is truthful and actionable. A shop-selected value placed on a quotation without authority looks complete but creates an unstable basis for price, schedule and acceptance.

02 / Create one controlled definition

List every file that forms the product definition and state its role. A typical package may contain a three-dimensional model, general arrangement, fabrication details, nozzle schedule, interface drawings, bill of materials, welding or inspection requirements, test procedure, finish notes and delivery instructions. The list should say which documents are for reference and which control manufacture and acceptance.

When a model and drawing coexist, define priority for geometry, dimensions, tolerances, notes and part identity. Research on model-based definition has examined whether annotated three-dimensional models can replace or complement traditional engineering drawings across the product lifecycle [1]. Separate work places model-based definition inside a product-lifecycle-management context and emphasizes the need to manage the definition as lifecycle information, not as an isolated display file [2]. Both studies come from broader manufacturing settings; neither makes a particular tank model complete by itself.

Those findings lead to a practical handoff rule: do not force the manufacturer to reconcile two unofficial truths. If the drawing controls notes and tolerances while the model controls nominal geometry, say so. If the annotated model is the sole authority, identify the required viewing method and any presentation state needed to expose annotations. If a neutral exchange file is supplied, confirm whether it is controlled geometry or only a convenience copy.

ISO 16792 specifies requirements for preparing, revising and presenting digital product-definition data when its framework is invoked [5]. ISO 7200 specifies data fields for title blocks and document headers when contractually selected [6]. These standards support consistent identification and presentation; they do not supply the tank's missing geometry, design values or manufacturing acceptance criteria.

The transmittal itself should carry project ID, document number, title, revision, issue date, status, originator and recipient. Include a manifest with file names and hashes or another agreed integrity method for critical digital packages. A later recipient should be able to establish that the model, drawing and schedules belong to the same release without comparing screenshots.

03 / State the customer-owned service basis

A geometrically complete model can still be an incomplete manufacturing package. The customer should state the stored medium, relevant operating and upset conditions, required capacity, temperature basis, design pressure, external or internal loading cases, cleaning approach, installation environment, governing requirements and interface loads or constraints. Only the customer or its design authority can decide which cases apply and how they are combined.

Material requirements need an exact specification and condition, together with any customer-controlled compatibility, corrosion, contamination, surface or traceability requirements. StelTank can review availability, forming, joining and inspection implications after those requirements are supplied. It does not select a material from the product name "chemical tank" or warrant compatibility with an undisclosed medium.

Show liquid levels, nozzles and internals only as they relate to the customer-approved design. Working volume, free space, venting, overflow, drainability, mixing, heating, cleaning and process connections are process-design matters. A fabricator may identify a manufacturing conflict or request a missing dimension, but it should not decide the functional arrangement from customary practice.

Distinguish installed, transport and test conditions. A temporary support arrangement, lifting orientation or water-filled factory check may load the assembly differently from operation. The responsible designer needs to approve the relevant temporary cases and any restraints assumed. StelTank can describe the proposed fabrication and test setup so that approval is based on a real configuration.

Reference the governing documents by exact title, identifier, edition and project applicability. Avoid a note such as "build to all applicable standards," which gives neither party a usable acceptance hierarchy. If requirements conflict, the package should define the precedence route and the authority that resolves it.

04 / Make geometry and interfaces buildable

Provide overall dimensions and a stable datum framework before detailing local features. Identify tank axes, center planes, support references, installed orientation and any interface coordinate system. A chain of dimensions copied across several views can accumulate ambiguity when one value changes. Prefer dimensions and relationships that connect each functional feature to a declared reference.

Define shell courses, heads, cones, transitions, openings, manways, supports, lugs, frames and permanent attachments with enough geometry to form, locate and inspect them. State which surfaces, centerlines, faces or theoretical intersections control each value. Where formed geometry is supplied as a model, include the information needed to distinguish nominal shape from a convenient visual approximation.

Each external interface needs an identifier shared by the drawing, schedule and model. Record its location, axis or face orientation, connection definition, projection basis, mating geometry, required tolerance and surrounding keep-out envelope. If connected equipment is outside StelTank's supply, its controlled interface still belongs in the package. A nozzle cannot be reviewed for fit against equipment that is represented only by a tag name.

Show internal relationships that affect manufacture: dip pipes, baffles, coils, spargers, sensors, cleaning devices or customer-supplied internals. Identify who supplies and installs each item and when it enters the assembly. If an internal is intentionally schematic, state which dimensions and envelopes remain controlling so the shop does not treat a diagram as fabrication geometry.

The frame and tank should be reviewed as one assembly when StelTank is asked to deliver them together. Locate supports, mounting holes, valve access, lifting points, handling areas and transport restraints against the same coordinate system. Include the installation and removal path for agreed valves or components where access is a requirement. The customer defines the interface and service needs; StelTank proposes a practical fabrication and fit-up sequence.

05 / Allocate requirements deliberately

A drawing should not make every dimension equally restrictive. Identify the features that protect fit, sealing, alignment, access, interchangeability, drainability or another customer-defined function, and assign their limits accordingly. Use general requirements for genuinely general features, not to hide a critical interface whose function depends on a specific relationship.

Hallmann, Schleich and Wartzack reviewed tolerance allocation and tolerance-cost optimization literature, describing the connection between product quality objectives and manufacturing cost [4]. Their review does not provide a default tolerance for a chemical tank or a cost multiplier for StelTank. It supports a disciplined handoff principle: place restrictive tolerances where variation affects the declared function rather than tightening the entire drawing without analysis.

For each controlled feature, state the requirement, datum or reference, evaluation method if prescribed, and delivery state at which it applies. A dimension before coating or final assembly may not describe the same condition as a delivered interface. If the customer requires a particular measurement method, sampling plan, report format or witness point, include that requirement in the package rather than adding it after fabrication.

Surface requirements should identify the affected surface and the parameter or acceptance language that matters. Words such as "smooth," "polished" or "clean finish" are not complete acceptance criteria by themselves. The customer defines the functional and process need; StelTank reviews whether the specified result and inspection access are compatible with the proposed manufacturing route.

Material, welding, cleaning and finish notes should distinguish mandatory requirements from proposed shop methods. If the customer controls a procedure, qualification, consumable, examination or documentation requirement, cite the exact approved source. If StelTank proposes the method, mark it for review and acceptance rather than presenting it as part of the original design basis.

06 / Define verification and delivery

Convert each important requirement into an inspection or evidence request before quotation. The package should identify critical feature IDs, required checks, acceptance authority, sampling or full-inspection expectations, witness points and retained records. A request for a "full inspection report" is incomplete if neither party knows which features, methods and decision rules it includes.

Define the hydrostatic or leak-check requirement as a customer-approved procedure, not as a value selected from factory capability. StelTank's approved statement is in-house hydrostatic test capability for the tank body up to 0.8 MPa, subject to the customer drawing and agreed procedure. That facility limit is not a product rating and does not establish a design pressure. Higher or otherwise different requirements need separate review of the drawing, procedure and applicable authorization boundary.

Mark the test boundary, installed items, temporary closures, orientation, supports, fill, vent and drain points. State required pressure stages, observation or hold conditions, acceptance language, instrument evidence, witness needs, post-test draining and preservation. Values and criteria come from the customer or its named authority. StelTank confirms the practical route within the agreed manufacturing scope.

Describe the final delivery state. List installed and loose items, shipping splits, temporary braces, protective covers, surface protection, preservation, packing, lifting provisions and documents that travel with the assembly. If site installation completes an interface, state which dimensions or alignment features are guaranteed at factory handoff and which work remains outside scope.

A documentary closeout index can prevent late arguments. Typical entries include the approved drawing list, material records required by contract, fabrication or joining records, dimensional results, test report, nonconformity and deviation dispositions, as-built definition, packing list and release approval. The actual list should match the customer's project requirements; this article does not promise every document for every order.

07 / Control questions and revisions

Manufacturing questions are expected in custom equipment work. The risk comes from resolving them outside the controlled definition. Give every clarification a unique ID, affected document and feature, question, proposed response, design-authority decision, implementation responsibility and closure revision. Verbal decisions should be captured before the related work proceeds.

Engineering-change research describes change as a lifecycle activity with causes, propagation and management consequences across product development [3]. Jarratt and co-authors' review is not a tank-fabrication procedure, but it supports looking beyond the changed dimension itself. A moved nozzle may affect an internal, frame, valve envelope, inspection plan, test boundary, drawing view, bill of materials and work already released.

Use impact questions before approval: what physical features change, which interfaces consume them, which documents repeat the information, what manufacturing has started, what needs reinspection, and whether cost or schedule must be revised? The answer can be concise, but it should be explicit. A change that is technically acceptable may still require disposition of material or work made to the previous revision.

ISO 11442 specifies basic rules for managing technical documents when it is adopted [7]. Applying a document-management framework does not make the content technically correct; it helps identify and control the content that the responsible parties have approved. Revision control and engineering approval are complementary, not interchangeable.

At final handoff, reconcile redlines and approved deviations into the required as-built state. Label any unit-specific concession so it is not treated as a general design update on a repeat order. Retain the clarification register with the document index so a later reviewer can trace why the delivered configuration differs from the initial inquiry.

08 / Use a handoff checklist

A good package lets StelTank quote the real manufacturing problem and return specific DFM comments. It does not need to be visually elaborate, but it must make authority, product definition, interfaces and acceptance traceable. Use the checklist below as a gap finder; the customer's governing requirements may add or replace fields.

• Named design authority, technical contact, change approver and final acceptance authority.
• Document manifest with project ID, file role, document number, revision, status and issue date.
• Priority rule for model, drawings, schedules, specifications and approved clarifications.
• Customer-owned process, medium, operating conditions, capacity, geometry, design pressure, loads, governing requirements and interfaces.
• Material and surface requirements, including condition, compatibility decisions and required traceability.
• Controlled geometry for tank body, formed sections, openings, supports, frame, internals and complete-assembly boundary.
• Interface schedule with IDs, datums, orientation, mating definition, tolerance, envelope and supply owner.
• Critical dimensions and requirements tied to function, inspection method, evidence and delivery state.
• Approved test and leak-check procedures, boundaries, acceptance rules, witness points and records.
• Delivery, packing, preservation, loose-item, site-work and as-built-document requirements.
• Clarification register, deviation route, revision process and NDA or controlled-exchange instructions.

StelTank's response should mirror the package. It should confirm the quoted scope, list manufacturing assumptions, identify DFM questions, describe the proposed fabrication and assembly route at an appropriate level, state agreed checks and evidence, and flag every item still awaiting customer approval. That response is more useful than a generic claim that the drawing is "understood."

When the package is not mature enough for a firm manufacturing commitment, label the review stage honestly. A preliminary feasibility review can identify major access, forming, joining and assembly questions without pretending the design is released. The next revision can then close those questions under the same authority and document controls.

References

The peer-reviewed papers support the bounded statements cited above about model-based definition, engineering change and tolerance allocation. They do not provide a chemical-tank design. The official standards support normative document practices only when the customer or contract invokes the applicable edition; listing them does not claim certification or universal project applicability.

1. V. Quintana, L. Rivest, R. Pellerin, F. Venne and F. Kheddouci, "Will Model-based Definition replace engineering drawings throughout the product lifecycle? A global perspective from aerospace industry," Computers in Industry, 61(5), 497–508, 2010. https://doi.org/10.1016/j.compind.2010.01.005
2. M. Alemanni, F. Destefanis and E. Vezzetti, "Model-based definition design in the product lifecycle management scenario," The International Journal of Advanced Manufacturing Technology, 52(1–4), 1–14, published online 2010. https://doi.org/10.1007/s00170-010-2699-y
3. T. A. W. Jarratt, C. M. Eckert, N. H. M. Caldwell and P. J. Clarkson, "Engineering change: an overview and perspective on the literature," Research in Engineering Design, 22(2), 103–124, published online 2010. https://doi.org/10.1007/s00163-010-0097-y
4. M. Hallmann, B. Schleich and S. Wartzack, "From tolerance allocation to tolerance-cost optimization: a comprehensive literature review," The International Journal of Advanced Manufacturing Technology, 107, 4859–4912, 2020. https://doi.org/10.1007/s00170-020-05254-5
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

Back to resources