A manufacturability review package is the controlled context for a fabrication conversation. It lets the manufacturer see what the equipment must be, which decisions are fixed, which interfaces carry risk, what information is provisional, and what condition must be delivered. A collection of drawings without status, ownership or acceptance context can be technically detailed and still fail to support a reliable manufacturing review.
The package does not need to be complete enough for production before the first inquiry. It does need to be internally consistent enough to expose gaps. A useful starting set includes the current overall arrangement, interface schedule, component or material requirements, quantity, project requirements, intended delivery state and a short statement of design maturity. The review then returns specific questions and proposed manufacturing changes instead of hiding assumptions inside a quotation.
Set the responsibility boundary on the first page
The customer owns thermal duty, heat-transfer design, overall geometry, equipment envelope, material and interface requirements, applied loads, operating conditions, project requirements and approval of changes to those decisions. StelTherm reviews manufacturability and the agreed fabrication scope: component readiness, fit-up, weld access, frame and support detailing, assembly sequence, tolerance and distortion risks, handling, staged checks, protection and handoff.
That division allows useful DFM work without transferring thermal or code responsibility. A proposed access opening, support detail or sequence change is a manufacturing proposal. If it alters flow arrangement, heat-transfer area, pressure boundary, material, customer interface, structural basis or another controlled requirement, it must return to the customer's design authority for approval. StelTherm does not perform thermal sizing, select the exchanger, guarantee thermal performance or claim certification through this review.
Put the boundary in the transmittal or review cover sheet. Name the customer design authority, the person authorized to answer manufacturing questions, the current document stage, and the fabrication scope requested for quotation. Identify customer-supplied, project-selected, sourced, fabricated, subcontracted and excluded items where known. Conditional wording is appropriate when scope remains open; an assumption should never be written as an established StelTherm capability.
Design-for-manufacture literature provides the broader rationale for doing this work before release. Boothroyd describes product design for manufacture and assembly as an integrated design concern [1], while O'Driscoll reviews design for manufacture as a discipline connecting product decisions with manufacturing considerations [2]. These sources are general, not exchanger-specific. They support early structured review; they do not authorize a particular fabrication route.
Control revision, maturity and assumptions
Start with a document index. Give every drawing, model, schedule and specification a title, identifier, revision, date and status. State which representation controls if a model and drawing disagree. If the customer sends native CAD plus neutral files, identify both and record the intended use. Include a transmittal so the manufacturer can distinguish the current package from an earlier email attachment with a similar filename.
Define maturity in practical terms. “Concept” may permit movement of interfaces; “quotation issue” may freeze the envelope but leave fabrication detail open; “approved for manufacture” should have a controlled meaning agreed by the parties. Do not rely on those labels alone. List fixed decisions, provisional inputs, approved alternatives and known open points. A package can then advance without pretending unresolved information is final.
Maintain an assumption register for anything needed to review or quote before confirmation arrives. Each assumption should state why it was introduced, what drawing or cost area it affects, who must confirm it, and what event invalidates it. Examples include whether finned tubes are customer-supplied or sourced within the order, whether a header is included, or which party owns the flat pattern for a frame component. Do not put unverified grades, capacities, test methods, tolerances or lead times into that register as public facts.
Complex products can propagate a local change into connected systems. Clarkson, Simons and Eckert modelled change propagation risk in a rotorcraft design case [6]. That work is not evidence about exchanger geometry, but it supports an interface-aware change process: a proposed movement at one connection should trigger review of the frame, tube group, access, installation and acceptance relationships that depend on it.
Define the product, interfaces and design authority
The overall arrangement should show the complete customer-intended equipment, not only the part expected from the fabricator. Include orientation, principal envelopes, tube-bank or bundle relationship, connections or headers where applicable, frames and supports, mounting points, lifting or handling restrictions supplied by the customer, and the condition expected at handoff. Context lets the manufacturer see where one local detail competes with another operation.
Create an interface register alongside the drawing. For each nozzle, flange, tube end, mounting point, support node, electrical or instrumentation provision if present, and installation boundary, record the controlling drawing reference, orientation, mating responsibility, required protection and acceptance source. Mark customer-supplied mating items and reference information. An interface should not depend on a note hidden in an unrelated document.
For finned tubes and grouped tube components, state the project-selected or requested configuration, supply responsibility, tube-end condition, fin termination and protected areas without assuming an attachment method that has not been confirmed. Give the arrangement, quantity and orientation controlled by the customer design. If source selection remains open, say so and define the information needed before commitment.
Material information should identify the governing customer requirement, product form, condition and traceability expectation. Avoid loose labels such as “stainless” when the design authority requires a specific material basis, but do not ask StelTherm to select a grade through a DFM article. Clarify permitted substitutions and who approves them. Identify surface condition, corrosion-sensitive handling restrictions and dissimilar-material concerns supplied by the project where they affect fabrication or protection.
Make product definition measurable, not merely detailed
Dimensioned drawings and models should identify the features that control assembly function. Show customer-defined datums, interface locations, orientations, profiles, clearances and tolerances needed at the relevant delivery state. Separate reference dimensions from acceptance requirements. Identify whether a requirement applies before welding, after joining, under fixture restraint, after release, after final assembly or at handoff.
ISO 16792:2021 is formally titled “Technical product documentation — Digital product definition data practices” [7]. ISO 1101:2017 addresses geometrical tolerancing for form, orientation, location and run-out [8]. These official records are cited only to identify their normative subjects. If either standard governs a project, the applicable edition and complete controlled requirements must be stated by the design authority; this page does not reproduce clauses or claim conformity.
Tolerance choices affect more than inspection. Hallmann, Schleich and Wartzack's literature review describes tolerance allocation as consequential to both product quality and cost [3]. Chase and Parkinson survey tolerance analysis in mechanical assembly design [4]. Those sources do not justify relaxing a customer tolerance. They support asking which function a tolerance protects, how related dimensions accumulate, and whether the proposed manufacturing and measurement route can address it.
Li and Hou model how geometric and dimensional tolerances can accumulate and propagate through assembly relationships [5]. Their CAD and simulation method is not a StelTherm service claim. Its relevance to the package is informational: include the mating and datum relationships needed to understand an assembly chain instead of submitting isolated part tolerances with no functional connection.
Show the intended build route and scope transitions
A manufacturer cannot review sequence from a bill of materials alone. Provide the intended relationship among finned tubes, tube groups, headers or connections, flanges, frame, supports, base and final assembly. Identify customer-mandated sequence restrictions and components that arrive already finished. Mark operations or items that may be in the quoted scope, but keep sourced, subcontracted and in-house responsibility conditional until the quotation confirms it.
The review should ask where components are prepared, how they enter the assembly, what holds them temporarily, which joints close access, when datums are checked, and how vulnerable fins or faces are protected. These are fabrication questions, not thermal calculations. A proposed sequence can be returned as an annotated state map showing loose components, subassemblies, frame integration, connection work, agreed checks and delivery protection.
Include handling and delivery-state inputs early. State permitted contact areas, lifting or support restrictions defined by the customer, insertion paths, transport envelope and interfaces needing covers or local guards. If packaging design is not yet agreed, identify exposed risks rather than inventing a packaging performance claim. The final route should make clear when protection is installed and which checks occur first.
Supply a quantity and target date as commercial planning inputs, but do not expect the article to promise a response time, production duration or minimum order. Identify whether the order is a single development unit, a repeat build or a staged quantity because review and document needs may differ. A delivery target becomes credible only after scope, inputs, sourcing dependencies and open questions are understood.
State inspection, acceptance and document expectations
List the characteristics the customer expects to accept and the state in which each applies. Examples may include mounting relationships, interface orientation, bundle position, protected openings or agreed visual conditions, but the actual list comes from the project. For every item, name the drawing or requirement, responsible party, stage, acceptance source and record expected. Do not insert a test or NDT method merely because it is common elsewhere.
Separate process checks from final acceptance. A fit-up reading can guide a weld sequence without becoming a product tolerance. A staged frame check can prevent compounding error without replacing the final interface measurement. If later joining, surface treatment, restraint release or packaging can affect the characteristic, define whether another check is required. Make the decision rule visible before results arrive.
Document expectations should be equally explicit. Ask for the records the project actually needs, such as agreed material traceability, approved drawings, dimensional results or subcontract records, without claiming that StelTherm automatically supplies a fixed dossier. Name format, identification and approval needs where known. If a certificate, procedure qualification, third-party activity or code document is required, identify the governing project requirement and responsible organization.
Turn review findings into controlled decisions
DFM questions should be specific enough to answer. Replace “access problem” with the joint identifier, obstructing member, affected operation and assembly state. Replace “tolerance difficult” with the controlled characteristic, datum, manufacturing concern and verification issue. Replace “drawing unclear” with the conflicting document references and the decision needed. A clear question reduces the risk that different teams close different problems.
Prioritize findings by consequence and timing rather than by how easy they are to discuss. A practical classification is: blocks quotation, blocks sourcing, blocks fabrication release, blocks a later assembly state, or can be resolved during detailed planning. This is a workflow aid, not a risk certification. Assign an owner and approval authority, then connect the response to a drawing revision, accepted redline, scope note or documented no-change decision.
Proposed changes should include the manufacturing reason and affected interfaces. If moving a brace improves weld access but changes a customer load path, the responsible designer must evaluate it. If extending a bare tube end changes thermal design or supplier selection, it cannot be accepted as a shop-only detail. If a temporary fixture solves alignment without altering delivered geometry, it may remain a manufacturing control, subject to the agreed process documentation.
Close questions in a decision log. Record the original issue, response, approver, date, affected documents and verification action. Supersede old files rather than leaving two plausible current versions in circulation. The log should also show rejected proposals so the same route is not reintroduced later without context.
Close the review with quoteable outputs
A useful review concludes with a prioritized query list, a controlled redline or clarification set, a scope matrix, an assumption register, and a route for remaining approvals. The quotation basis should identify included and excluded work, customer-supplied items, sourcing dependencies, drawing status, inspection assumptions and the intended handoff condition. Open issues stay visible as qualifications or hold points rather than disappearing into general language.
The review output is not production approval unless the parties explicitly make it so. A conceptual DFM response can identify risks while leaving engineering and commercial inputs unresolved. A manufacturing-release package should have the level of control, approval and acceptance definition required by the order. Name the transition rather than assuming every redline is automatically released.
StelTherm's deliverable is manufacturing clarity: questions tied to evidence, agreed changes tied to documents, and a fabrication scope that can be quoted and planned. It is not a replacement thermal design, equipment selection, performance guarantee, structural certification or code approval. Those boundaries should remain visible in the transmittal, the issue log and the final scope.
Review package checklist
| Package element | Minimum question it should answer | Typical review outcome |
|---|---|---|
| Cover and index | What was sent, at which revision and for what decision? | Controlled review baseline |
| Responsibility map | Who owns design, approval, supply, fabrication and interfaces? | Scope matrix and approval route |
| Overall arrangement | How do tube groups, connections, frame, supports and envelope relate? | Assembly-context questions |
| Interface register | Which mating features, orientations and protected surfaces control? | Clarified customer and manufacturing interfaces |
| Models and drawings | Which representation controls dimensions, datums and tolerances? | Product-definition issue list |
| Materials and sourced items | What is specified, supplied, selected, substitutable or unresolved? | Sourcing dependencies and approval needs |
| Build-route inputs | What sequence, access, restraint, handling and protection constraints exist? | Proposed manufacturing state map |
| Acceptance basis | What is checked, when, against which controlled requirement and by whom? | Order-specific check and record plan |
| Commercial context | What quantity, target and handoff state are being quoted? | Visible quotation assumptions |
| Open-item log | What blocks the next commitment, who answers and how is closure recorded? | Prioritized DFM query list |
Before sending, run a consistency check. Confirm that drawing and model revisions match the index, interface names are used consistently, units are unambiguous, provisional information is marked, links or attachments open, and superseded files are removed. Verify that the responsibility statement appears in the same package as the technical content. A clean submission will not eliminate DFM questions; it will make them easier to identify and close.
For an early inquiry, send what is available and say what is missing. StelTherm can then identify the information needed for the next review stage. Do not fill gaps with invented equipment data, material availability, tolerances, inspection methods or project history. A transparent unknown is safer and more quoteable than an unsupported exact claim.
References
- G. Boothroyd, “Product design for manufacture and assembly,” Computer-Aided Design, 1994. https://doi.org/10.1016/0010-4485(94)90082-5
- M. O'Driscoll, “Design for manufacture,” Journal of Materials Processing Technology, 2002. https://doi.org/10.1016/S0924-0136(01)01132-3
- 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, 2020. https://doi.org/10.1007/s00170-020-05254-5
- K. W. Chase and A. R. Parkinson, “A survey of research in the application of tolerance analysis to the design of mechanical assemblies,” Research in Engineering Design, 1991. https://doi.org/10.1007/BF01580066
- C. Li and W. Hou, “Analysis of Assembly Tolerance Based on Assembly Constraint Information Model,” Mathematical Problems in Engineering, 2021. https://doi.org/10.1155/2021/7438966
- P. J. Clarkson, C. Simons and C. Eckert, “Predicting Change Propagation in Complex Design,” Journal of Mechanical Design, 2004. https://doi.org/10.1115/1.1765117
- ISO, “ISO 16792:2021 — Technical product documentation — Digital product definition data practices.” Official ISO record.
- ISO, “ISO 1101:2017 — Geometrical product specifications (GPS) — Geometrical tolerancing — Tolerances of form, orientation, location and run-out.” Official ISO record.
Review-package evidence atlas
A useful package connects the overall arrangement to the manufacturing states that need decisions. These illustrations are not project records. They show the level of context needed to ask about tube readiness, interface geometry, assembly sequence and staged checks without taking ownership of the customer's thermal design.
For each open item, include four labels
- The controlling drawing, model view or interface reference.
- The customer decision that is fixed or still open.
- The manufacturing conflict involving access, sequence, support or inspectability.
- The output needed: clarification, redline, fabrication detail, scope note or agreed check point.
Build a package that can survive the review cycle
The goal is not to make the first submission look final. It is to create a package in which every manufacturing question can be traced to the current design basis and every accepted answer can be carried into the next revision without losing ownership or scope.
1. Establish the document hierarchy
List the overall arrangement, interface drawings, models, material requirements and project specifications with their current revision status. Identify which source controls when two views disagree. Mark superseded files and preliminary sketches clearly. This prevents the manufacturing review from resolving a conflict against a drawing that is no longer authoritative or from treating a concept image as released geometry.
2. Create an interface register
Record mounting points, flange faces, nozzles, openings, support locations, customer datums and installation-envelope constraints. For each interface, state the owner, the controlling source and whether it is fixed or open to proposal. The register does not need numeric capability claims from StelTherm; it needs enough context to identify which manufacturing details can be developed without changing customer intent.
3. Separate confirmed facts from working assumptions
A missing source fact should remain visible. If a reversible assumption is needed to continue a draft, label it and state what later information will replace it. Do not turn a representative material appearance, illustrative process or common shop practice into a public capability statement. Exact dimensions, grades, tolerances, tests, certifications, lead times and records require verified sources and order-specific agreement.
4. Write manufacturing questions as decisions
Each question should name the affected feature, the physical conflict and the consequence of leaving it unresolved. Then state the information or approval needed. Useful questions ask which side remains open, what establishes position, when an interface can be checked or which component closes access. Vague requests for more detail make it difficult for the design authority to provide a targeted answer.
5. Return accepted answers to the controlling artifacts
Meeting notes alone are not a durable fabrication basis. An accepted change should update the drawing, redline, interface register, scope assumption, fixture concept or check point that downstream work uses. Record who approved the decision and which customer-controlled requirement remains unchanged. If approval is pending, keep the item open rather than silently freezing one option in the manufacturing detail.
6. Convert the review into a quotation basis
The quotation should state supplied and sourced items, fabrication and assembly work, selected checks and records, protection, delivery state and exclusions. It should also list assumptions that affect price or sequence. This creates a shared starting point for later detail without promising thermal performance, certification, material range or inspection activity that the available sources do not support.
A manufacturability review can begin with incomplete information, but release for fabrication requires a controlled basis. The customer retains design authority; StelTherm owns only the manufacturing detail and fabrication scope explicitly agreed for the order.
Refresh the package when one controlling input changes
A revised arrangement, interface, material request, quantity, delivery state or governing requirement can affect several earlier answers. Reissue the interface register and open-item list with the new source identified. Mark which manufacturing proposals remain valid, which need review and which assumptions have now been replaced by confirmed facts. Avoid leaving conflicting revisions active in parallel.
The refreshed package should also update quotation assumptions, fabrication details and selected check points that depended on the changed input. If a new request adds work, records or third-party activity, treat it as a scope decision rather than an editorial update. This discipline lets an early review remain useful without allowing preliminary information to become an unrecorded production instruction. Archive the superseded basis so later teams can trace why the manufacturing route changed. Keep the replaced source and approval traceable for later review.
The package should remain usable when it moves between design, purchasing, manufacturing and quality teams. Give every open item a stable reference, current source, responsible owner and required response. Separate information needed to price the work from information needed before release, then show which later detail depends on each answer. If an assumption is temporarily carried, label its trigger for replacement and prevent it from becoming public capability language. A clean open-item register reduces repeated questions while preserving the difference between a reversible manufacturing proposal and an approved customer-design decision.