Reviewing a Replacement Finned-Tube Module for an Existing Frame: Datums, As-Built Baselines, and Physical-Fit Evidence

Direct answer: relate four evidence states before reviewing physical fit

Retained evidence can support a future physical-fit review only when the existing asset and interfaces are identified and the project can relate four separately labelled states: the controlled as-designed definition, the accepted as-built evidence, the current as-found evidence, and the proposed replacement evidence. The comparison must preserve a traceable relationship between functional reference systems, or document an authorized controlled transformation when the references differ. It must also relate connection identities, measurement meaning, and relevant physical states while recording the changes and uncertainty or condition information required by the appointed authorities. Under this project-review rule, equal nominal dimensions alone leave interchangeability unresolved. Retained evidence can support the review, but it never guarantees interchangeability.

A physical-fit review is a decision about named physical interfaces in named states. It does not establish installation acceptance, thermal duty, process behavior, pressure-boundary integrity, structural adequacy, vibration behavior, material compatibility, cleaning performance, reliability, or service life. No public project record supports a concrete conclusion here about a StelTherm replacement result.

Route the article-level decision into exactly one branch:

• Ready for appointed physical-fit review: the four states, critical interface rows, comparison basis, and appointed authority are complete enough to begin the named review. This is not an interchangeability, installation, acceptance, or performance conclusion.
• Refresh required before appointed physical-fit review: a missing, stale, or non-comparable record can be named, refreshed, and returned by an assigned owner before the review begins.
• Insufficient for physical-fit review: the current as-found evidence cannot be related to the controlled as-designed definition and accepted as-built evidence with the available records. Stop the affected replacement conclusion rather than inventing continuity.
• Stop and escalate: design, measurement, configuration, installation, deviation, acceptance, or performance authority is unresolved, or the requested conclusion exceeds physical-fit evidence.

Open, stale, or conflicted may explain a row, but they are not decision branches. Every non-ready critical row needs a non-ready route and named action.

Start with the asset, then separate four evidence states

Identify the parent equipment, existing frame, existing module, site or project, orientation or handedness, and unit or serial identity where assigned. Name the configuration owner and reconcile physical tags with the controlled record index. A record from a similar unit, an earlier revision, or an earlier physical condition is not a substitute for the named asset. An inaccessible, unauthenticated, superseded, or mismatched file is an evidence gap, not remembered proof.

Keep the four states separate throughout the record:

The record set needs an explicit precedence and revision rule. A model, drawing, schedule, redline, deviation, measurement file, and photograph can serve different purposes. The public catalog record for ISO 16792 identifies digital product-definition data practices as a technical-documentation subject when that framework is invoked.^[1] The public record does not prescribe this four-state model, a project file hierarchy, a replacement dossier, a retention period, or a StelTherm data-management capability. The four-state separation used here is an editorial decision model.

The original controlled bundle and interface definition is where as-designed manufacturing input can begin. It is neither accepted as-built evidence nor current as-found evidence by itself. An adjacent controlled drawing, revision, and as-built handoff example shows useful document discipline in another equipment context; it does not define an exchanger replacement decision.

For a real review, request the named asset register, current controlled document manifest, accepted as-built record, current as-found record, and proposed replacement definition. This article has no public named-asset package from which to populate those fields.

Preserve the datum, connection, and envelope that make comparison meaningful

Begin each interface row with its physical function: locate, support, guide, mate, seal, clear, insert or remove, or protect another approved relationship. Then assign a stable Interface ID that appears on the controlling definition, physical identification where required, measurement records, change records, replacement evidence, and final disposition. The list of real interfaces must come from the controlled equipment definition and the current asset; this article does not create a universal finned-tube module interface list.

For the datum story, record the controlling datum features or system, orientation, physical targets, condition, and reference realization used for each measurement. If the four states do not use physically identical references, require a traceable relationship or an authorized controlled transformation. Do not silently treat different reference systems as equivalent. The ISO 5459 public catalog identifies datums and datum systems as a formal geometrical-product-specification subject when the responsible authority selects that framework.^[2] Its public record does not choose project datum features, tolerance, measurement state, method, comparability rule, or conformity status.

The record of carrying datums and measurement states through original fabrication can supply accepted final-state evidence when the project retained and accepted it. This replacement review does not repeat welding sequence, fixture release, insertion stages, or the original alignment plan. It asks whether the accepted record can still be related to the current frame and the proposed replacement evidence.

Connection identity must go beyond a nominal designation. Use the project definition to capture applicable mating faces or axes, locating features, joining or fastening details, supports, guides, locators, shims, seals, condition, revision, and supplied-item owner. A shared connection label is not a complete physical relationship.

Treat the envelope in the same way. Accepted as-built evidence may need the critical measured surfaces or points, keep-out or insertion and removal relationship, connected-equipment boundary, support or restraint state, evidence record, deviations, and acceptance owner. Current as-found evidence must record its own envelope and condition rather than borrowing the accepted as-built label. Proposed replacement evidence must describe the same characteristic or provide an approved relationship between different representations.

Li and Hou's mechanical-assembly research models how geometric and dimensional tolerances can accumulate and propagate through assembly relationships.^[3] That abstract-level result supports reviewing connected relationships instead of comparing one local nominal value. The paper does not study finned-tube modules or existing frames, define this four-state model, supply a tolerance or probability, or prove a replacement result. The project therefore keeps interchangeability unresolved until its complete controlled evidence and appointed decision rule close the relevant rows.

No public project evidence here identifies the actual datum features, connection details, approved limits, envelope measurements, condition records, or authorities for a StelTherm asset. Those remain named project inputs rather than article examples.

A measurement is comparable only with its meaning and state attached

A retained value needs enough context for the appointed measurement authority to decide what was measured and whether another result can be compared with it. For each Interface ID, record the characteristic or measurand, datum realization, target or feature condition, and whether the product was installed or removed. Record the support, restraint, load, protection or coating, foundation, and connected state that matter to the decision. Temperature, time, and environmental information belong in the record only where the appointed authority requires them.

Also retain the method, data or report ID, traceability reference where required, operator or organization, date, required uncertainty statement, and decision rule and owner. Keep the role explicit: controlled as-designed, accepted as-built, current as-found, and proposed replacement results are different evidence states.

NIST Technical Note 1297 addresses reporting a result with uncertainty, keeping referenced measurement-process documents current, defining a measurand through a particular method, and, in a separate standards and calibration context, cautions that transport, time, and changed environment can introduce effects in later use.^[4] That guidance supports retaining method, result, uncertainty, and current-document context, and it supports asking whether changed conditions matter. It is NIST policy and guidance, not an exchanger standard, the project's physical-fit criterion, an instrument choice, an uncertainty budget, a decision rule, or evidence of StelTherm metrology capability.

Compare results only after the appointed measurement authority determines that the measurands, datum realizations, physical states, methods, conditions, and uncertainty treatment are suitable for the specific decision. A photograph, model, point set, report, instrument name, rounded dimension, or calibration record is not self-validating physical-fit evidence. If the meaning or state cannot be recovered, route the row to refresh required, insufficient, or stop and escalate; do not invent comparability.

There is no public approved StelTherm measurement plan, equipment list, uncertainty budget, environment, traceability chain, decision rule, accepted as-built report, current as-found report, or proposed replacement report for this article.

Current as-found evidence must not inherit as-built acceptance silently

Review intervening events only where they can affect an interface row. Possible inputs include approved revisions, concessions, nonconformances, repairs, field drilling or cutting, altered locators, shims, coatings, corrosion, wear, damage, foundation settlement, support changes, piping or header changes, and adjacent-equipment changes. These are review prompts, not claims that any condition exists on a particular asset.

For each relevant event, record affected Interface IDs, implementation evidence, approving authority, and whether the definition, survey, measurement treatment, or disposition must be refreshed. Keep “no recorded change” separate from “current condition confirmed.”

Clarkson, Simons, and Eckert model change propagation and its likelihood and impact in a rotorcraft design case.^[5] The abstract supports asking which connected records and relationships a change may affect, but it supplies no exchanger impact map, risk score, approval route, or mandatory remeasurement rule. Reopen an interface row when project evidence shows that the event can alter that row's decision; do not assume that every change affects every interface.

The guide to preserving identity and accepted records across known-module transport states provides a useful contrast. It concerns the same approved modules returning after separation and transport. A proposed replacement has a separate manufacturing history, and that known-module reassembly evidence does not establish current as-found condition or replacement interchangeability.

No public service or change ledger, repair or deviation record, current as-found survey, or authorized relationship between current as-found and accepted as-built evidence is available here for a named StelTherm asset.

Compare one functional interface at a time

The Four-State Replacement Evidence Tool is an editorial synthesis, not a standard, tolerance-stack method, inspection procedure, digital-twin schema, interchangeable-part method, acceptance rule, or proof of StelTherm capability. Create one row pair for every project-defined critical interface. Possible families include a mounting reference, locator, support, guide, approved connection, envelope, or protected target, but only the project definition decides which rows exist.

Table A preserves the first three states without collapsing them. Do not fill it from memory or copy nominal values into physical-evidence columns.

Table B uses the same Interface ID to relate proposed replacement evidence and route the decision. Never rely on row position alone.

Read the pair in order: establish the controlled as-designed definition; inspect accepted as-built evidence; inspect current as-found evidence and its relationship to the accepted record; then use the same Interface ID to assess the proposed replacement evidence and comparison state.

Route each interface row before selecting the article-level branch. Use one complete row result:

• ready for appointed physical-fit review - not interchangeable, installed, accepted, or performance-qualified;
• refresh required before appointed physical-fit review, with the missing or stale evidence, owner, and return gate;
• insufficient for physical-fit review, with the affected conclusion stopped and the evidence discontinuity named; or
• stop and escalate, with the unresolved authority or out-of-scope decision named.

Do not shorten the first status to ready or reviewable. A completed noncritical row cannot compensate for a missing critical interface. The article-level branch is ready only when every required critical row carries the complete ready status. Otherwise select the strongest applicable non-ready branch. Physical-fit review status does not establish installation or performance.

Retain the controlling drawings or models, raw and processed measurement data or reports, target or feature map, condition record, change and deviation evidence, approvals, record locations, and evidence owners needed to reconstruct each decision. No real table row is populated here because no public named StelTherm asset, value, method, result, or acceptance status is available.

Name who defines, measures, changes, installs, and accepts

Turn every missing item into an owned action. Confirm the following roles in the contract and controlled project record rather than assuming that one party holds all authority.

• Asset or configuration owner: identifies the installed unit, current controlled records, service changes, and evidence access. This role confirms configuration identity but does not automatically own engineering acceptance.
• Responsible design authority: owns assigned functional interfaces, datum scheme, nominal definitions and approved limits, engineering changes, and the applicable structural, pressure, thermal, or process boundaries.
• Measurement authority or metrology planner: defines the measurand, datum realization, physical state, method, uncertainty and reporting treatment, traceability needs, comparability basis, and measurement decision rule.
• Manufacturer or StelTherm, when included in the agreed scope: reviews manufacturability, access, datum transfer, inspectability, fabrication implications, and proposed evidence capture. This role does not invent unassigned project values, certify interchangeability from nominal equality, or assume performance authority.
• Installer: follows the approved installation route, preserves interface evidence, and records departures. Installation activity does not silently authorize a design change.
• Acceptance authority: dispositions the named physical-fit evidence or concession. Separate appointed authorities address pressure, thermal, process, structural, vibration, material, cleaning, or service performance.

Stop the affected replacement release when asset identity or revision cannot be reconciled; a functional datum is unusable or unrelated to the controlling definition; connection identity remains nominal; or the three physical evidence states cannot be related. Also stop when uncertainty or condition can change the decision without disposition, a change lacks impact review, or a required authority is unnamed.

Do not use force, uncontrolled heating, cutting, hole enlargement, unapproved shims, relocation, or another unauthorized field change to convert a blocked row into an apparent result. Escalate the exact interface, missing evidence, affected connected relationships, and authority needed. The route belongs to the project's contractual and safety framework; this article does not create a universal stop-work rule.

When gaps require a new review, the broader controlled manufacturing review package can help organize inputs and decisions. It cannot replace design, metrology, installation, deviation, or acceptance authority, and it does not establish a standard StelTherm replacement dossier.

The handoff package should contain the completed two-table tool, current controlled document index, datum or target and connection map, separately labelled controlled as-designed, accepted as-built, current as-found, and proposed replacement evidence references, change and deviation ledger, non-ready branch register, named authorities, and the required owner and route for every unclosed row. This is a project-requested package, not a claimed standard deliverable.

Close on evidence, not nominal similarity

A controlled as-designed definition, accepted as-built evidence, current as-found evidence, proposed replacement evidence, complete relevant change history, and named authorities can make a future physical-fit review auditable. The strongest available conclusion is ready for appointed physical-fit review - not interchangeable, installed, accepted, or performance-qualified. That evidence cannot guarantee interchangeability or establish pressure, thermal, process, structural, vibration, material, cleaning, or service performance.

Complete both tables for the named asset. Proceed only on the complete ready status; send refreshable rows to their named evidence owners; stop replacement release where evidence is insufficient for physical-fit review; and stop and escalate unresolved design, measurement, configuration, installation, deviation, acceptance, or performance authority.

References

1. International Organization for Standardization, ISO 16792:2021, Technical product documentation - Digital product definition data practices. Official catalog record. Only the public title and subject are used; no licensed clause is reproduced or treated as a project requirement. Back to citation
2. International Organization for Standardization, ISO 5459:2024, Geometrical product specifications (GPS) - Geometrical tolerancing - Datums and datum systems. Official catalog record. Only the public title and subject are used; the record does not establish project conformity or select project datums. Back to citation
3. Li, Chunxi, and Wenjun Hou, “Analysis of Assembly Tolerance Based on Assembly Constraint Information Model,” Mathematical Problems in Engineering (2021). https://doi.org/10.1155/2021/7438966. Only the abstract-level assembly-variation proposition is transferred; the study does not establish an exchanger result. Back to citation
4. Taylor, Barry N., and Chris E. Kuyatt, Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results, NIST Technical Note 1297 (1994), sections 7.1, 7.2, 7.6, and Appendix D.4.1. Official NIST landing page. The note is guidance, not a project acceptance rule or evidence of StelTherm capability. Back to citation
5. Clarkson, P. John, Caroline Simons, and Claudia Eckert, “Predicting Change Propagation in Complex Design,” Journal of Mechanical Design 126(5), 788-797 (2004). https://doi.org/10.1115/1.1765117. Only the abstract-level connected-change caution is used; the rotorcraft case does not define an exchanger impact map or review process. Back to citation