A truck loading rack is the part of a terminal where tank trucks pull in and are filled with product, and it is where a lot of a terminal's automation and safety logic actually lives. Each loading position, or bay, pairs a metered flow path with a preset batch controller that governs how much product is delivered, a driver identification step that authorizes the load, and a chain of interlocks that must all be satisfied before a drop of product moves. It is a compact, repetitive, high-consequence operation: the same load happens dozens of times a day, custody-quality volume is measured every time, and any lapse in the permissive logic is a spill or a safety event. A cloud SCADA view of a rack turns those repeated loads into visible throughput and turns the interlock states into something a supervisor can watch from anywhere.
Truck Loading Rack in one line: A truck loading rack is the terminal facility where tank trucks are filled, with each bay controlled by a preset batch controller and metering that measure and stop the delivery at a set quantity. Driver authorization and a set of permissive interlocks govern each load, and the resulting throughput and status are what a cloud SCADA terminal view surfaces.
At the heart of every loading bay is a preset batch controller, a dedicated device that turns a requested quantity into a controlled delivery. The driver or the terminal system enters or authorizes a preset volume, and the controller opens the loading valve, counts flow from the meter as product moves, and closes the valve when the preset is reached, typically slowing to a low flow near the end so the final valve closure does not slam or overshoot. The result is a delivery that stops at the right quantity without a person having to watch the meter.
The metering is what makes the load a measured transaction rather than an estimate. A meter on each loading arm - often a positive displacement or Coriolis meter - measures the product delivered, and because loading is frequently a custody transfer point, that meter is held to accuracy and proving requirements. The batch controller records the delivered quantity for the ticket, and many racks also apply temperature correction so the volume booked reflects a standard temperature rather than the temperature at the rack, mirroring the correction logic used elsewhere in custody accounting.
The batch controller is also the local guardian of sequence. It will not open the loading valve until it has an authorized preset and every permissive is satisfied, and it enforces the two-stage flow profile that protects both the meter and the truck from a surge. Because it sits right at the bay, it can react in the moments that matter - closing on a high-flow fault, an interlock trip, or a completed batch - without waiting on a decision from a distant control room.
A rack is not just plumbing; it is an access-controlled operation. Before loading, a driver identifies themselves, commonly with a card or a terminal-automation credential, which ties the load to a carrier and a product authorization and prevents unauthorized or wrong-product loading. That authorization step is the front end of the whole sequence: it establishes who is loading, what product, and how much, and it links the physical load to the terminal's records so the movement is accounted for from the start.
Between authorization and product flow sits a chain of permissive interlocks, each of which must be true before the batch controller is allowed to open the valve. Typical permissives include a verified ground or bond on the truck to dissipate static, the loading arm or coupler properly connected, an overfill sensor on the truck showing not-full and healthy, and the emergency stop circuit clear. Any one of them failing withholds the permissive, so the rack fails safe: no permissive, no flow. This is where a rack's safety case is actually implemented, in logic rather than in signage.
Because a rack runs the same cycle over and over, its performance is naturally expressed as throughput - loads completed per hour, product volume moved, and how long trucks spend in a bay. Bay availability, queueing, and the mix of products being loaded all follow from that cycle. Watching throughput reveals bottlenecks a single ticket never would: a bay running slow because it keeps dropping a permissive, a product that always backs up the queue, or a meter drifting toward its proving limit and needing attention.
A loading rack generates exactly the kind of signals a cloud SCADA platform is built to aggregate: batch controller states, delivered volumes, meter readings, and the discrete status of every permissive interlock. When Merobix reads those from the rack's controllers, a supervisor gets a live terminal view that shows which bays are loading, which are idle, which are held on a failed permissive, and how much product has moved across the shift, without standing at the rack.
The permissive states are especially valuable to see remotely because they explain why a bay is not loading. A dashboard that shows a bay held because its ground verification is not made, or its overfill sensor is faulted, turns a stalled load from a mystery a driver reports into an actionable status a supervisor can already see. That shortens the loop between a stuck truck and someone who can fix the cause, and it makes patterns visible - a bay that repeatedly trips the same interlock is telling you about a real fault, not a run of bad luck.
Throughput and metering data historized over time turn the rack into a source of operational intelligence rather than just a set of tickets. Trends in loads per hour, per-bay utilization, and meter behavior let a terminal balance load across bays, anticipate proving and maintenance on meters before they drift out of tolerance, and reconcile rack throughput against tank movements. For multi-terminal operators, seeing every rack's status in one cloud view is the difference between managing terminals one phone call at a time and managing them as a network.
A preset batch controller takes an authorized target quantity and delivers exactly that amount to the truck. It opens the loading valve, counts flow from the meter, slows to a low flow near the end to avoid overshoot, and closes the valve when the preset is reached. It also enforces the loading sequence, refusing to open until permissives are satisfied and recording the delivered volume for the custody ticket.
Common permissives include a verified static ground or bond on the truck, the loading arm or coupler properly connected, a healthy overfill sensor on the truck reading not-full, a valid driver authorization for the product, and a clear emergency-stop circuit. Every required permissive must be true before the batch controller opens the loading valve, so if any one fails the rack withholds flow and fails safe.
It aggregates each bay's batch controller state, delivered volumes, meter data, and interlock status into a live terminal view a supervisor can watch remotely. That makes it clear which bays are loading, which are held and why, and how throughput is tracking. Historized data also reveals bottlenecks, recurring permissive faults, and meters drifting toward their proving limits before they cause a problem.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.