What a Header, Manifold, and Nozzle Interface Register Must Define Before Exchanger Fabrication

Direct answer: bind every connection to one controlled Interface ID

Before exchanger fabrication, give every project-defined header, manifold, and nozzle connection a stable Interface ID. Use that same ID on the controlled drawing or model, coordinate schedule, mating-item record, fabrication review, access review, inspection request, change record, and disposition. A name such as header outlet or customer nozzle is not enough when several connections, revisions, or supplied items could match it.

For each Interface ID, close two linked records. The first defines connection identity, coordinate and datum system, orientation, mating envelope, and supplied-item boundary. The second defines the fabrication and weld-access state, inspection and retained evidence request, authority, release status, holds, and change triggers. If either half is missing, conflicting, or tied to another revision, hold the affected interface rather than filling the gap with a customary location, pressure class, flange standard, shop detail, or inspection practice.

This register records controlled project inputs. It does not choose process location, connection duty, pressure class, flange or end standard, pressure-boundary design, material, load, welding procedure, inspection method, tolerance, or acceptance value. It also does not prove a StelTherm capability or result. The responsible authorities must supply and approve those decisions before the interface enters the named fabrication scope.

Establish the coordinate and datum system before listing dimensions

Start with one equipment identity and revision. Name the coordinate convention, origin, axes or directions, units, viewing convention, and physical features that realize the references. State whether coordinates locate a connection center, axis, face plane, tangent or intersection, or another project-defined characteristic. A coordinate triplet without its measurand and reference system cannot tell manufacturing what physical relationship it represents.

For each interface, identify the datum features or system used for location and orientation and how those references are available in the relevant fabrication state. ISO 5459:2024 publicly addresses datums and datum systems as a geometrical-product-specification subject.^[1] That official subject supports making the reference basis explicit, but it supplies no exchanger datum, coordinate, orientation, tolerance, method, applicability decision, or conformity result.

Control datum transfer rather than assuming identical labels mean identical physical references. A reference used on a header detail may need a defined relationship to the bundle, frame, support, or site coordinate system. The adjacent guide to preserving datums through shipping and reassembly states shows why a physical reference and its realization must remain visible, but it does not choose this exchanger's interface datums or fabrication state.

A tank-nozzle guide offers a useful cross-product example of defining nozzle coordinates and orientation from controlled references. Its tank geometry does not transfer to an exchanger, and a local connection reference must not silently become the overall exchanger datum. Use the project design authority's own coordinate and datum framework.

The coordinate record should also expose revision precedence. If a general arrangement, header detail, nozzle schedule, supplied-item drawing, and model all describe the interface, state which source governs each characteristic and how an approved deviation is recorded. Do not average conflicting coordinates, choose the newest file by timestamp, or treat a model view as self-authorizing.

Define connection identity, mating envelope, and the supplied-item boundary

Connection identity begins with the Interface ID, equipment and subassembly, project function label, governing document, and mating-item identity. Add only the project-approved connection definition needed for manufacturing: the controlled face, axis, end, opening, orientation, and detail references. If the design uses a class, flange/end standard, facing, gasket, fastener, or preparation designation, record the authority-approved value and revision; this article selects none of them.

One physical component may participate in several controlled relationships. Keep separate Interface IDs when a branch-to-header joint, an external mating connection, a support relationship, or another project interface has a different definition, owner, access state, or evidence route. Cross-reference shared geometry instead of hiding several decisions in one overloaded row.

Separate the connection itself from its mating envelope. The envelope may need the controlled mating face or insertion relationship, axial and radial occupation, orientation or clocking, adjacent keep-out geometry, assembly approach, removable-item path, tool approach, insulation or cladding boundary, and the state in which those relationships apply. Include only fields relevant to the real connection. Do not create a generic clearance or assume that an unobstructed drawing view proves assembly or weld access.

Hsu and Lin studied quantitative component accessibility and product assemblability in a design-for-assembly context.^[2] That work supports treating access as an explicit relationship rather than a visual impression. It does not study exchanger headers, manifolds, nozzles, welding, inspection, or supplied items and provides no project clearance, approach direction, tool envelope, value, or StelTherm result.

Define the supplied-item boundary in physical and documentary terms. State which party supplies the header, manifold, nozzle neck, flange or end component, gasket or seal, fasteners, transition, loose mating item, temporary closure, and any project-defined accessory only where applicable. Identify who controls the supplied item's drawing, material and traceability evidence, dimensional record, protection, delivery state, and change approval. A commercial label or purchase-order line does not by itself define the physical interface.

The controlled finned-tube bundle drawing package provides the broader assembly definition from which interface IDs and relationships can be derived. It does not populate this register automatically. A separate drawing and revision handoff example illustrates document identity in another product context; it does not choose an exchanger connection, supply boundary, or priority rule.

Where a component is supplied by another party, distinguish supplier proposed, design-authority approved, received, and verified for the named evidence request rather than collapsing them into vendor item. Those labels are editorial workflow prompts, not universal contract states. The controlled project must define what evidence moves an item between them.

Record weld-access state without writing a welding procedure

Weld access is state-dependent. For each connection, identify which adjacent tubes, fins, headers, branches, supports, frame members, closures, temporary fixtures, restraints, supplied items, and protective elements are present or absent when the joint is approached. State the intended access direction, joint visibility, tool or process envelope supplied by the responsible manufacturing review, temporary support or restraint state, and the later assembly step that closes access.

This state record does not select a welding process, parameter, consumable, joint preparation, qualification, sequence, heat treatment, repair route, or acceptance. It asks whether the already approved joint definition can be reached and executed in the named assembly state and whether required surfaces, datums, mating faces, and nearby components remain protected.

ISO 2553:2019 publicly addresses symbolic representation of welded joints on drawings.^[3] A controlled symbol may identify joint information under the selected project framework, but the official subject does not provide a welding procedure, access state, assembly sequence, inspection method, acceptance rule, or proof that this joint can be fabricated.

The StelTherm article on designing weld access into an exchanger assembly develops the assembly-state review in more detail. This register consumes only the approved access state, affected Interface IDs, and open conditions. It does not repeat weld-sequence design or convert an access review into technical approval of the pressure boundary.

Inspection access is separate again. Record the characteristic and evidence requested by the responsible inspection or design authority, the fabrication state in which it is required, the access or surface condition it assumes, and the owner of the method and disposition. Do not select radiography, ultrasonics, visual testing, dimensional measurement, leak testing, or another method from this article. A method name without the requirement source, feature, stage, record, and authority is incomplete.

Use the two-part Interface Register

The Header, Manifold, and Nozzle Interface Register is an editorial coordination tool. It is not a pressure-boundary design sheet, piping class, flange schedule, welding plan, inspection procedure, tolerance table, acceptance record, or StelTherm capability statement. One paired Part A and Part B row represents one project-defined interface. Add a pair for every additional Interface ID and never join tables by row position alone.

Part A - Definition and boundary. One row records project inputs for one Interface ID. It is incomplete and non-evidentiary by itself without the matching Part B row.

In Interface ID / connection identity, enter the stable ID, equipment and subassembly, project function label, mating item, governing definition and revision, and approved connection-detail reference. Record an approved class or standard only when the responsible authority has supplied it; the register does not propose one.

In coordinate and datum definition, enter the coordinate convention, origin and directions, units, datum system, physical realization, measurand, location definition, governing view or model, and revision relationship. Keep any unresolved discrepancy visible with its owner.

In orientation and mating envelope, enter the approved axis, face plane, clocking or directional characteristic, mating occupation, approach or insertion relationship, adjacent keep-out geometry, protected surfaces, and state to which the envelope applies. Do not populate a generic clearance.

In supplied-item boundary, enter included and excluded components, supplier and design owner, controlled supplier drawing or data, material/traceability record requested by the project, delivery and protection state, loose-item identity, and responsibility for mating compatibility. The field records ownership; it does not transfer design responsibility.

Part B - Fabrication, evidence, and decision. One row repeats the same project Interface ID. It is incomplete and non-evidentiary by itself and establishes no release unless its state, requirement, evidence, authority, and holds are closed.

In fabrication and weld-access state, enter present and absent components, temporary supports and restraints, access direction and protected zones, assembly stage, operation scope, closure trigger, and open manufacturing conflicts. This is a state description, not a WPS or sequence approval.

In inspection and retained evidence, enter the requirement source, characteristic, project-selected method category, stage and physical state, evidence/report ID, result format, deviations, and record owner. Method and acceptance authority remain with the appointed project parties.

In authority, status, hold, and change trigger, enter design, supplied-item, manufacturing, inspection and disposition owners; current status and date; open fields and return gates; approved deviations; superseded record; and every change requiring impact review or re-release.

Read Part A first to establish what and where the connection is and who supplies each item. Read matching Part B to establish how its named fabrication state remains accessible, what evidence is required, and who may release or hold it. Compare connected rows for shared headers, branches, mating items, datums, access closures, or documents. One closed interface cannot compensate for another unresolved connection.

The blank rows are intentional. Do not invent an equipment ID, process location, class, standard, size, material, coordinate, orientation, envelope, joint, method, result, supplier, approval, or status to make the template appear complete.

Control evidence, holds, and interface changes

Keep the controlled definition and evidence identities together. ISO 16792:2021 publicly addresses digital product-definition data practices.^[4] That official subject supports explicit file, revision, and definition identity, but it provides no project hierarchy, interface register, retention rule, fabrication release, supplied-item approval, applicability decision, or conformity result.

Use four local workflow states:

• Open: a required definition, relationship, evidence request, or authority is missing; fabrication release is not established.
• Reviewing: inputs exist but the technical, manufacturing, supplied-item, access, or evidence review is incomplete; fabrication release is not established.
• Released for named interface fabrication: both rows, revisions, access state, evidence request, and authorities are closed for the stated operation only; pressure-boundary acceptance and later operations are not implied.
• Superseded or held: a conflict or change has cancelled or paused the earlier authority for the affected scope.

Hold an interface for an ambiguous coordinate or datum; mismatched connection identity; incomplete mating envelope; uncontrolled supplied item; inaccessible approved operation; missing evidence request or owner; conflicting drawing/model/schedule; or attempted use of an old revision. Isolate the hold only when connected effects can be identified safely. Otherwise hold the connected header, manifold, branch, or release set.

Clarkson, Simons, and Eckert modeled change propagation likelihood and impact in a rotorcraft design case.^[5] That bounded research supports asking which connected definitions and interfaces a change may affect. It supplies no exchanger impact map, risk score, mandatory hold, reinspection rule, approval route, or StelTherm result.

Reopen affected rows when a datum, coordinate, orientation, connection definition, mating item, envelope, supplied-item boundary, access state, assembly stage, requirement, method owner, evidence, or governing revision changes. Reopen means controlled impact review and disposition, not automatic redesign, rework, reinspection, or rejection.

Assign owners and send one controlled package

The responsible exchanger/process design authority supplies process location and function, pressure-boundary definition, connection specification, pressure class or rating where applicable, flange/end standard, materials, loads, design limits, and acceptance criteria. The register carries those approved inputs without selecting or validating them.

The supplied-item owner provides controlled mating geometry, included components, records, delivery state, and changes. The manufacturing owner reviews buildability and access within written scope. The inspection authority selects the method, stage, evidence, and decision rule. Document control preserves the current definition and superseded states. The acceptance or deviation authority disposes only the decisions assigned to it.

Use the controlled manufacturability review package when interface conflicts need broader coordination. That review does not replace process, pressure, piping, design, welding, inspection, supplier, or acceptance authority.

Send one package containing the completed paired register, governing document index, coordinate/datum map, connection and mating-item definitions, supplied-item schedule, access-state views, inspection/evidence request, open-item list, owners, deviations, statuses, and change record. Mark assumptions open instead of converting them into shop defaults.

This article concerns original fabrication release. It does not decide whether a future replacement is interchangeable, relate as-built and as-found states, design supports or thermal movement, select maintenance access, purchase finned tubes, or assign post-release contractual change authority.

Evidence boundary and final stop line

No first-party StelTherm interface register, pressure design, supplied-item record, access study, inspection plan, fabrication result, or customer acceptance record supports this general article. The sources provide bounded documentation, datum, access, weld-representation, and change context; they prove no StelTherm capability or project result.

If the same Interface ID cannot connect the controlled definition, physical location, mating and supply boundary, fabrication/access state, evidence request, current revision, and authorized decision, that interface is not yet defensibly released for fabrication.

References

1. ISO 5459:2024, Geometrical Product Specifications (GPS) - Geometrical Tolerancing - Datums and Datum Systems. Official ISO record. Public title and subject only; no project datum, coordinate, tolerance, method, applicability, or conformity is supplied. Back to citation
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. DOI. General design-for-assembly accessibility context only; no exchanger or weld-access value transfers. Back to citation
3. ISO 2553:2019, Welding and Allied Processes - Symbolic Representation on Drawings - Welded Joints. Official ISO record. Public title and subject only; no joint, procedure, access state, sequence, inspection method, acceptance, applicability, or conformity is supplied. Back to citation
4. ISO 16792:2021, Technical Product Documentation - Digital Product Definition Data Practices. Official ISO record. Public title and subject only; no project hierarchy, register, release, retention rule, applicability, or conformity is supplied. Back to citation
5. P. John Clarkson, Caroline Simons, and Claudia Eckert, "Predicting Change Propagation in Complex Design," Journal of Mechanical Design, 126(5), 788-797, 2004. DOI. The rotorcraft case supplies only connected-change context, not an exchanger impact map or disposition. Back to citation