How to Set Up a Tank Strapping Table in SCADA

Back to Blog

Enter the Certified Level-to-Volume Points

Start from the tank calibration certificate, the authoritative document that maps level to volume for that specific tank, and enter its points into the SCADA gauge table exactly as certified. Match the units, whether the certificate is in metric or field units, and confirm the reference the levels are measured from matches the level the SCADA tag reports. Transcription is the main risk here, so enter carefully and check a sample of points back against the certificate, because one wrong digit corrupts volume in that region of the table.

Confirm the certificate is current for the tank as it exists today. A modification since the last strapping, an added coil or a changed bottom, invalidates the old table, and using a stale one silently biases inventory. The certificate should be a traceable tank calibration certificate, and the table you enter must match it. Record which certificate revision the loaded table came from so a future audit can confirm the two agree.

Configure Interpolation Between Points

A strapping table lists volume at discrete levels, so SCADA must interpolate to get volume at the level actually measured. Confirm the platform interpolates linearly between adjacent certified points, which is the standard treatment, and that it does not extrapolate beyond the table ends into levels the certificate never covered. The behaviour and its pitfalls are covered in gauge table interpolation, and getting it right is what keeps the computed volume smooth and correct between the listed points.

Watch the table density where the tank shape changes fastest. Around a floating roof landing, a knuckle, or the bottom courses, the level-to-volume relationship curves, and a sparse table interpolated linearly across a curved region introduces error. If the certificate provides closely spaced points there, enter them all rather than thinning the table, because the extra points are exactly where linear interpolation needs help. Confirm the table covers the full working range so no operating level falls outside it.

Handle Deadwood and Roof Corrections

A real tank contains internal structure, heating coils, mixers, support legs, that displaces product, and the certified table already accounts for this deadwood, so your job in SCADA is to not double-count it. If the strapping certificate is a net table with deadwood already subtracted, enter it as-is; if any correction is meant to be applied separately, configure it once and confirm it is not also baked into the table. The concept is covered in deadwood in tank calibration.

A floating-roof tank needs its roof correction handled, because the roof floats on the product and displaces a volume that must be subtracted over the range where it is floating and not while it is landed. Confirm the SCADA configuration applies the roof correction only in the floating range and switches it off when the roof is landed on its legs, since applying it in the wrong regime skews volume. These corrections are where a strapping setup most often goes subtly wrong, so verify them explicitly against the certificate's instructions.

Verify the Computed Volume

Prove the table by feeding known levels through it. Pick several levels spanning the range, including one near a shape change, compute the volume the SCADA table returns, and compare each against the certificate value for that level. Agreement across the range means the points, the interpolation, and the corrections are all right. A mismatch at one level points to a mistyped point or an interpolation issue there; a proportional mismatch everywhere points to a units error.

Then tie it to reality with a physical check where practical, reconciling the computed volume against a measured receipt or delivery, or against a manual gauge and the certificate. When the volume tag feeds a monitoring history, a strapping error tends to show as an inventory that does not close against movements, and comparing computed volume against metered transfers over time is a strong ongoing check. The trend flags a volume that will not reconcile; the certificate says which table region is wrong.

Avoid the Common Mistakes

The recurring errors are transcription mistakes in the entered points, a units mismatch between certificate and tag, extrapolation past the table ends, and mishandled deadwood or roof corrections, either double-counted or omitted. Using a stale certificate after a tank modification is a quieter but serious error. Each of these produces a volume that looks reasonable but does not reconcile, which is why a level-by-level check against the certificate is the essential verification.

Because a strapping error shows up as inventory that will not close rather than as an obvious bad reading, it can persist through many transfers before anyone traces it to the table. Trending computed volume against metered movements in a monitoring platform surfaces the discrepancy as a persistent imbalance, pointing back to the strapping setup. The reconciliation flags the problem; a point-by-point comparison against the certificate isolates the specific table region or correction at fault.

Frequently Asked Questions