AtilaxVENECORR NDT, C.A.
Tank management · Transfer and custody

The system a tank farm uses to keep its inventory and its deliveries

TankOS brings together in a single record what today is scattered across forms, emails and spreadsheets: the tank measurement, the laboratory analysis, the movements and the farm's instruments.

TankOS — Oil storage tank management software, transfer-and-custody grade, from the Atilax suite. VENECORR NDT brings it to market.

ContactTry the live demo ↗
TankOS: a tank farm’s inventory and deliveries5:56Share →
The figure

A fiscal figure is not typed in: it is derived

From the tank level, the laboratory test and the gauge table. And every step is written down.

The fiscal figure is set by the authority that oversees it. What TankOS provides is the backing: how the farm arrived at its own figure, what it measured it with, and who answered for it.

So that a barrel that left a Venezuelan tank farm can be reconstructed number by number, years later.

How it works

A single record, from measurement to entry

What is measured in the farm and in the laboratory feeds one and the same calculation. From it come the ticket, the inventory and the reports, and everything lands in the operations log.

Illustration of the operations flow: the gauging, the farm's instruments and the laboratory feed the calculation engine, from level to mass; out of it come transfer and custody, inventory and reports, and everything stays in the operations log, from noon to noon.
What it covers

From the farm to the report, in the same system

TankOS screen: the instruments registered in the farm, each with the tank it belongs to and its status.

Configuration

The farm, just as it is in the field.

Sites and farms, the farm canvas with its tanks and its lines, and the instruments that measure: tapes and radars, and the equipment that connects them to the system.

  • Sites and farms
  • Farm canvas
  • Tanks
  • Instruments
TankOS screen: capture of a manual gauging next to the live radar reading.

Capture

What is measured, and who measured it.

Manual gauging is recorded in feet, inches and fractions and checked against the radar reading. The laboratory enters its test and who approved it. The gauge table is kept by versions: the one in force and the previous ones.

  • Manual gauging in feet · inches · fractions, checked against the radar
  • Laboratory test with its approval
  • Versioned gauge table
TankOS screen: detail of a tank with the provenance of each input and the calculation chain, from total observed volume to mass, each step with its factor and where it comes from.

Calculation

From level to mass, step by step.

Every stage of the calculation stays in view, with its correction factors and the provenance of each figure: what was measured, with which instrument, which table was in force and who approved each thing.

  • Step by step, from level to mass
  • Correction factors in view
  • Provenance of each figure
TankOS screen: list of tickets with sequential numbering, one of them voided with its reason.

Transfer and custody

The batch, its two gaugings and the numbered ticket.

The batch is opened and closed with its gaugings; the ticket carries a sequential number, with no gaps, and if it is voided the reason is kept. The inventory is the sum of the entries, not a typed-in balance.

  • Batches
  • Numbered tickets, no gaps
  • Inventory
  • Counterparties
  • Lines
TankOS screen: one day's operations log, with its entries and the missing items flagged.

Monitoring and log

What happened in the farm, written down once.

Alarms with per-tank templates, and an operations log that runs from noon to noon and cannot be modified or deleted: gaugings, samples, movements, issued tickets, alarms and also what was not done.

  • Alarms
  • Per-tank templates
  • Immutable operations log, from noon to noon
TankOS screen: an issued daily report, with its hourly rows and the integrity fingerprint of the PDF and the Excel file.

Output

The same data, for whoever needs it.

Seven reports from the same data, each with its scope and its period; the audit trail can be exported; six roles with separate responsibilities. Integration is through an outbox: when a ticket is issued, it is delivered to webhook, sftp or file, with retry.

  • Seven reports
  • Exportable audit trail
  • Six roles
  • Outbox: webhook, sftp or file, with retry

Screenshots from the development bench. The figures shown do not belong to any client.

Responsibilities

Six responsibilities, and each one answers for its part

Whoever enters data does not approve it. The operator takes the gauging, the lab technician enters the sample, the supervisor approves what others entered and issues the ticket, the engineer defines the farm, the administrator touches no figure, and the custody inspector looks without writing.

Illustration of the six responsibilities —operator, lab technician, supervisor, engineer, administrator and custody inspector— with what each one can do and what it cannot. Whoever enters data does not approve it.
Videos

TankOS, explained from the inside

What TankOS is3:47Share →
TankOS in four minutes4:42Share →
TankOS, the full walkthrough5:53Share →
AtilaxVENECORR NDT, C.A.

TankOS, from the Atilax suite.

National technology, for national processes.

Contact