Tank Support and Foundation Interfaces: What Fabrication Needs From the Site Design

Direct answer: fabrication needs an approved interface schedule, not a foundation-design request

Tank support fabrication can begin responsibly only when the site and design teams provide a controlled support/foundation interface package. That package should identify the tank and support revision, the design documents and precedence, the responsible designer's load or action inputs, support points and directions, the installation coordinate and elevation framework, base and anchorage geometry, the intended bearing, levelling and grout state, the characteristics and tolerances to be fabricated or checked, the evidence required at each state, and the authority that can close an open item.

The package must distinguish supplied design facts from open questions. A missing anchor layout is not permission for the tank fabricator to choose one. A foundation sketch without an approved datum relationship does not release base-hole geometry. A phrase such as level on foundation does not define whether the relevant state is temporarily shimmed, supported on levelling devices, grouted, anchored, released from temporary restraint, or finally accepted. Each unresolved field needs an owner and a hold point.

This article does not design a foundation, assess soil or concrete, establish site loads, calculate a support or base plate, select or size anchors, choose grout, prescribe shims or levelling devices, set a universal tolerance, approve an erection method, or accept an installed tank. Those decisions belong to the structural, foundation, geotechnical, process, site, installation, inspection, and acceptance authorities appointed for the project. StelTank may review and fabricate only the interface scope stated in controlled order documents; this general guide proves no design, equipment, qualification, tolerance, or completed result.

Use the wider controlled tank drawing handoff to organize the complete drawing package. The tool on this page is narrower: it connects the site-designed support/foundation boundary to the characteristics that fabrication and later installation must preserve.

Lock the configuration, document precedence, and responsibility boundary

Begin with identity. Record the tank number, support-system identifier, foundation or pedestal identifiers, interface IDs, drawing and model numbers, revisions, units, status, and date of the authorized design input. State which document controls if a general arrangement, support detail, anchor plan, foundation drawing, calculation output, specification, and site survey disagree. Do not let the newest file in an email folder become the controlling file by accident.

One interface ID should mean one physical relationship. A leg base to a pedestal, a skirt base to an annular foundation, a support frame to several foundations, and a hold-down feature to an anchor group may require separate rows even when they appear on one sheet. If a shared support carries several items, identify the boundary at which tank-fabrication responsibility ends and site or structural responsibility begins.

Confirm roles rather than assuming a universal contract split:

• The customer or designated design authority supplies the functional tank layout, governing design basis, support concept, required interface performance, approved design changes, and acceptance authority assigned to its scope.
• The structural, foundation, and geotechnical authorities own their calculations, foundation and anchorage definition, substrate basis, and design dispositions.
• The site and survey authorities own the site grid, elevation network, physical reference realization, foundation and anchor as-built record, and discrepancies assigned to them.
• The installation authority owns the approved setting, temporary support, levelling, bearing, grouting, anchor installation, restraint-release, and protection activities assigned by the project.
• StelTank fabrication owns only the agreed manufacture and recording of the released tank-support features. It may raise manufacturability conflicts or propose a change, but cannot approve a site or structural design change unless separately appointed and evidenced to do so.
• Inspection and acceptance owners define methods and records within their authority and issue the actual disposition. A measurement value without its authority and state is not an approval.

Map the physical sequence before releasing a detail: authorized site/design input -> released tank-support definition -> as-fabricated support/base -> foundation and anchor as-built state -> pre-set verification -> tank set and temporarily levelled -> project-defined bearing/grout/anchorage state -> restraint released -> installed interface acceptance. Use only the states present on the real project. Never merge them because the same nominal coordinate appears in several records.

Receive design actions without turning fabrication into structural design

The fabricator needs the designer's output in a form that can be applied to the named interface. For each input, record the source calculation or drawing, revision, units, coordinate directions, sign convention, application point or distribution, relevant operating or installation state, combination or case identifier, and responsible authority. If the designer uses separate values for different states, retain those distinctions. Do not collapse them into one unlabeled maximum load field.

The public DOI record for ASCE/SEI 7-22 is titled Minimum Design Loads and Associated Criteria for Buildings and Other Structures. That title confirms a formal design-load subject; it does not select the standard for this project or supply any tank, support, foundation, wind, seismic, thermal, piping, operating, test, erection, transport, soil, or anchor value.^[1] The applicable design basis and its outputs must be identified by the responsible authority.

Fabrication should receive design outputs, not reverse-engineer them from a general arrangement. A support reaction shown without direction, state, application location, units, or combination reference is incomplete. A base drawing with an anchor group but no relationship to the calculated support interface leaves a traceability gap. A verbal instruction to allow for site loads is not a load input.

External equipment can introduce a separate information path. For example, the agitator nozzle and support drawing interface explains why equipment identity, reactions, geometry, and responsibility must be coordinated before fabrication. It does not supply a reaction or design case for this foundation schedule. Bring only the approved equipment-derived inputs into the responsible designer's controlled support/foundation package.

When an input is missing, use a hold, not a conservative-looking invented value. The fabricator can identify which feature cannot be released, what information is needed, who owns it, and the date or gate at which it must close. It should not choose a larger anchor, thicker plate, wider slot, additional weld, or stiffer support as an undocumented substitute for design authority.

Define base, anchor, and installation geometry from common references

Once the design basis is identified, translate its approved geometry into fabricable characteristics. Name the support or base feature, its location, size, orientation, interface face, hole or slot identity, and relationship to the tank. State material and product requirements only through the controlled design. Show whether a dimension applies to the fabricated base, an anchor template, the as-built foundation, a temporarily set tank, or the final installed state.

ISO 129-1:2018 is publicly titled for general principles governing the presentation of dimensions and tolerances in technical product documentation. That public subject does not provide a base dimension, hole or slot size, edge distance, projection, tolerance, units, document precedence, inspection method, or conformity result for this project.^[2] The schedule therefore records the actual project characteristic and its controlling source instead of borrowing a familiar shop note.

For anchorage geometry supplied by the designer, capture the anchor or group identifier, pattern, coordinates, orientation, nominal relation to the support feature, hole or slot intent, and the installation/access envelope needed for the released fabrication. Include projection, engagement, sleeve, template, washer, nut, or adjustment fields only when the controlled project definition requires them. Listing a field does not select its value or assign its design.

Slots deserve explicit intent. A slot might be part of an approved adjustment concept, movement interface, installation allowance, or another design decision, but the fabricator must not infer which. Record its direction, controlling reference, permitted use, protected dimensions, and authority. Do not enlarge a hole or redirect a slot to absorb an as-built discrepancy without a reviewed disposition, because the proposed change may affect a design relationship outside fabrication's authority.

Datums require the same care. ISO 5459:2024 publicly identifies datums and datum systems as a geometrical-tolerancing subject. Its public record does not choose a tank centerline, base plane, support axis, anchor reference, site grid, benchmark, elevation, physical realization, tolerance, method, or conformity result.^[3] Those choices and their controlled relationships must come from the project.

Keep at least four reference roles visible when they exist:

1. The design or product reference defines the intended tank/support relationship.
2. The fabrication reference realizes the required features in the shop.
3. The site grid or elevation reference locates the foundation and installed tank.
4. The survey realization is the physical network, benchmark, target, or setup used to produce a stated result.

These references may be related, but they are not interchangeable merely because they use the same label. The package should show how a shop reference transfers to the delivered interface and how the site reference relates to the design definition. If the relationship needs a transformation, offset, orientation convention, or survey record, identify the responsible owner and controlled document. The nozzle coordinate and orientation guide offers a nearby example of why angle, clock position, datum, and revision must travel together; it supplies no support datum or foundation tolerance.

Separate foundation, bearing, levelling, grout, and anchor states

A fabricated base and an as-built foundation are two independent histories. The base can conform to its released drawing while the foundation or anchors differ from their approved definition. A foundation can match its own survey record while the tank-support revision has changed. Compare both to the same authorized interface definition before deciding that they are compatible.

Name the bearing and levelling concept supplied by the responsible design and installation authorities. The project may use direct bearing, grout, plates, shims, levelling devices, another engineered arrangement, or a sequence of temporary and final states. This article selects none. Record which contacts support the tank at each state, which items are temporary or permanent, where adjustment is permitted, what surfaces or features must be protected, and what event transfers responsibility or load.

The American Concrete Institute DOI record titled Grouting for Support of Equipment and Machinery establishes only that grouting at an equipment-support interface is a distinct technical subject. Its public metadata does not select grout, thickness, preparation, placement, cure, bearing state, inspection, tank application, or acceptance for this project.^[4] A project with grout must therefore provide its own controlled definition and owners; a project without grout should not inherit grout fields as assumptions.

If grout is part of the approved interface, distinguish at least the pre-grout, placed or completed, and released states used by the project. Record who supplies and installs it, who confirms the receiving surfaces and geometry, which characteristics remain observable, what evidence is retained, and which authority accepts the state. Do not let grouted imply that voids, bearing, strength, cure, anchor condition, level, or structural performance have been checked unless those exact characteristics and results are present in the authorized record.

Levelling is also state-specific. An observation made while jacks, wedges, shims, temporary supports, or restraints carry load describes that recorded condition. When the support condition changes, the relevant interface rows may need impact review. That does not mean movement occurred or that every result must be repeated; the project decides what is material and which evidence is required.

Installed orientation can affect downstream functions. The StelTank guide on support orientation and the named low-point relationship shows why a drainage decision must identify its installed support state. It does not prescribe a foundation, level, slope, grout arrangement, or drainability result here. T2 only ensures that the design-defined orientation interface is transmitted and not overwritten by a shop assumption.

Coordinate site setting-out, as-built evidence, and fabrication inspection

Design coordinates and elevations describe intent; setting-out and as-built records describe a physical realization under a named survey plan. Preserve both. Before shipment or installation, identify which site record will be issued, when it will be valid, which foundations, pedestals, anchors, sleeves, recesses, or bearing surfaces it covers, and who resolves a discrepancy against the design definition.

ISO 4463-1:1989 is publicly titled for planning and organization, measuring procedures, and acceptance criteria in building setting-out and measurement. That public subject does not select this project's survey standard, grid, benchmark, instrument, personnel, foundation or anchor tolerance, acceptance value, correction, or tank-setting procedure.^[5] The project survey authority must supply the applicable plan and record.

An as-built record needs enough identity to be compared responsibly: interface and feature IDs, foundation or pedestal IDs, controlled design revision, site grid and elevation reference, realization date and state, surveyed locations and coverage, units, method owner, report or data identifier, limitations, and disposition of deviations. A screenshot or unlabeled coordinate list is not a controlled interface record.

Fabrication evidence needs an equivalent chain. Name the characteristic, drawing source and revision, support state, reference, measurement locations or coverage, method category, equipment or data identity, required status fields, result and units, limitation, record, and decision owner. Keep fit-up or process results separate from final as-fabricated evidence. Keep as-fabricated evidence separate from site acceptance.

ISO 10012:2003 is publicly titled Measurement management systems - Requirements for measurement processes and measuring equipment. Its public record does not choose an instrument, calibration interval, uncertainty, sampling, method, acceptance criterion, certification, or StelTank inspection capability.^[6] It supports only the bounded discipline of keeping the measurement process and equipment context attached when the project requires such evidence.

For a broader fabrication analogy, StelTherm's frame alignment state example discusses recording references, restraint, and measurement stages for another product family. It supplies no tank support condition, foundation input, tolerance, instrument, result, or responsibility allocation. Use it only as a reminder that a measurement state must travel with the value.

Use the Tank Support/Foundation Fabrication Interface Schedule

The Tank Support/Foundation Fabrication Interface Schedule is an editorial coordination tool. One row represents one identified interface, one controlled configuration, and one evidence or release state. Split a row when the physical interface, revision, state, characteristic, or decision owner changes.

The placeholder row intentionally contains no value. Do not fill it with a typical load, anchor pattern, hole clearance, grout thickness, tolerance, survey method, levelling instruction, or approval label. Replace each field only with controlled project information or mark it open with an owner and closure gate.

Read the schedule left to right before fabrication release. The source column proves which configuration is under review. The designer-input column shows whether the fabricator received an authorized input rather than an inference. The datum/geometry column converts that input into named interfaces. The state column prevents a temporary condition from being mistaken for final installation. The evidence and owner columns show how the decision will actually close.

Then read from right to left before site acceptance. Start with the decision the installed interface must support. Ask which authority owns it, which result and physical state are required, which foundation and tank-support geometry the result concerns, and which design input established that geometry. This reverse trace exposes an acceptance request that has no design source or a shop result being promoted beyond its state.

For example, a row may remain deliberately open as support interface S-___ / design source rev ___ / load input record ___ / design datum ___ / base and anchor relationship ___ / foundation as-built record ___ / temporary levelling state ___ / final bearing or grout state ___ / fabrication result ___ / site result ___ / owners ___ / reopen after revision, load, anchor, or state change. The blanks are release controls, not permission to choose values.

The schedule is not a structural calculation, foundation or anchorage design, exhaustive load list, code checklist, grout specification, survey plan, erection method, inspection plan, acceptance certificate, or StelTank capability statement. It organizes project decisions; it cannot make them.

Hold conflicts early and reopen only the affected interface

Hold the affected row when the controlling revision or precedence is unclear; the action/load input lacks an owner, direction, state, units, or source; the product, shop, or site references are unrelated; base, hole, slot, or anchor geometry is incomplete; foundation or anchor as-built evidence is missing; bearing, levelling, grout, or restraint state is undefined; a characteristic or tolerance has no controlled source; a method or record is absent; or nobody has authority to disposition the result.

Also hold when someone asks fabrication to absorb a site discrepancy by moving a support, enlarging a hole, redirecting a slot, adding a plate, changing a weld, altering the tank orientation, or accepting a different elevation without authorized design review. A proposal can be documented and returned quickly, but execution must wait for the responsible authority when it changes a controlled interface.

Reopen affected rows after changes to the design basis, loads or combinations, tank/support configuration, foundation or anchorage, site grid or elevation, base/hole/slot geometry, bearing/levelling/grout arrangement, installation sequence, restraint state, measurement process, evidence role, or document revision. Reopen means controlled impact review: identify what changed, which records remain valid, what needs new evidence, and who decides. It does not automatically require redesign, refabrication, rework, rejection, or acceptance.

The final handoff should contain the current tank/support and foundation interface documents, design-input references, completed schedule, drawing/model revisions, site datum and elevation relationship, base and anchorage definition, required as-built record, bearing/levelling/grout state definition, fabrication and site evidence requests, responsibility matrix, open-item register, and change route. Keep external lifecycle status truthful: a review-ready local article does not prove any project has supplied or accepted these records.

The stop line is simple: if the team cannot trace one support/foundation interface from an authorized design input through controlled geometry and state-specific evidence to a named decision owner, that interface is not ready for fabrication or installation release.

References

1. American Society of Civil Engineers, ASCE/SEI 7-22, Minimum Design Loads and Associated Criteria for Buildings and Other Structures. DOI record. Public-title and standard-identity use only; no project applicability, load, combination, coefficient, design method, or result is transferred. Back to citation
2. ISO 129-1:2018, Technical Product Documentation (TPD) - Presentation of Dimensions and Tolerances - Part 1: General Principles. Official ISO record. Public title and subject only; no project dimension, tolerance, presentation rule, method, applicability, or conformity is supplied. Back to citation
3. ISO 5459:2024, Geometrical Product Specifications (GPS) - Geometrical Tolerancing - Datums and Datum Systems. Official ISO record. Public title and subject only; no tank, support, foundation, anchor, site, or survey datum, tolerance, method, applicability, or conformity is supplied. Back to citation
4. American Concrete Institute, Grouting for Support of Equipment and Machinery, ACI Structural Journal, 1992. DOI record. Public metadata/title use only; no grout, foundation, bearing, installation, test, or acceptance requirement is transferred. Back to citation
5. ISO 4463-1:1989, Measurement Methods for Building - Setting-out and Measurement - Part 1: Planning and Organization, Measuring Procedures, Acceptance Criteria. Official ISO public record. Public title and subject only; no project survey plan, benchmark, instrument, foundation/anchor tolerance, correction, or acceptance is supplied. Back to citation
6. ISO 10012:2003, Measurement Management Systems - Requirements for Measurement Processes and Measuring Equipment. Official ISO record. Public title and subject only; no instrument, calibration interval, uncertainty, sampling, method, certification, acceptance, or StelTank capability is supplied. Back to citation