A loading terminal is more than a set of racks that meter product into vehicles; it is a business operation that has to decide who is allowed to load, what they are authorized to take, which tank it comes from, and what paperwork proves the transaction. The terminal automation system, or TAS, is the layer that runs all of that above the individual bay presets. It sits between the terminal's business systems and the rack controllers and SCADA, turning an order in a back-office system into an authorized, measured, documented load at a bay. This page defines the TAS, walks through what it handles from access control to reconciliation, and explains where its responsibilities end and where SCADA and the rack controllers take over.
Terminal Automation System (TAS) in one line: A terminal automation system (TAS) is the software layer that orchestrates a loading terminal above the bay-level presets, handling driver and carrier access control and authorization, order and bill-of-lading management, product allocation and tank assignment, and reconciliation of what was loaded against what was ordered. It sits between the terminal's business systems and the rack controllers and SCADA, translating orders into authorized loads and load records back into transactions. SCADA and the rack controllers handle the real-time measurement and interlocks at the bay, while the TAS handles the authorization, documentation, and accounting around each load.
The bay-level controller, often called a preset, handles the mechanics of a single load: it takes a target quantity, opens the flow control valve, watches the meter, ramps the flow down as it approaches the target, and closes at the set amount, all while enforcing the local safety interlocks. What the preset does not decide is whether this driver should be loading at all, what product and how much they are entitled to, or where that product comes from. Those decisions belong to the TAS, which orchestrates the whole terminal above the level of any single bay.
Access control and authorization are the first thing the TAS handles. Before a driver can load, the system checks that the driver and carrier are known and permitted, that any required training or certifications are current, and that they are authorized for the product and the site. This is where a driver identifies themselves, often with a card or a code, and the system decides whether to let them proceed and to which bay. Only an authorized driver against a valid order gets a load enabled at a bay, which is how the terminal controls who takes what.
Order and document management is the other core of the TAS. It holds the orders that say who is collecting what, matches an arriving driver to their order, and produces the bill of lading that documents the completed load: the product, the quantities, the temperatures and any corrected volumes, the destination, and the transaction identifiers. It also handles allocation and tank assignment, deciding which tank a product draws from given inventory, quality, and any allocation rules, so the load pulls from the right source. Taken together, access, orders, allocation, and documents are the business logic of loading that the TAS exists to run.
Allocation and tank assignment are where the TAS connects the abstract order to the physical terminal. An order for a product does not care which tank holds it, but the terminal has to draw from a specific tank with a specific inventory and quality, and it may have rules about which customers or contracts can draw from which stock. The TAS makes that assignment, choosing the source and reserving the quantity, so that when the load runs, the product moving through the meter is the product the order and the accounting expect. Getting this right is what keeps inventory records and the physical tanks in agreement.
Reconciliation closes the loop. After loads run, the TAS compares what was actually loaded, as measured at the bays, against what was ordered and against the tank movements, so discrepancies surface rather than hiding. If more product left the racks than the tanks say was drawn, or an order shows a different quantity than was loaded, the terminal wants to see that promptly. Reconciliation turns a day's worth of individual loads into an accounting the terminal can trust, and it is the basis for both operational checks and the numbers that flow back to the business.
Above the TAS sit the business systems: the enterprise software that holds orders, contracts, customers, and inventory at the company level. The TAS is the bridge between those systems and the terminal floor, receiving orders and authorizations from the business side and returning completed transactions, bills of lading, and reconciled quantities. This positioning is deliberate. The business systems do not want to talk directly to a flow computer at a bay, and a bay controller has no idea about contracts or customers, so the TAS translates between the language of the business and the language of the equipment.
The clearest way to understand a TAS is by what it does not do. It does not open valves, watch meters scan by scan, or enforce the safety interlocks that decide whether a load is physically permitted to run. Those are the jobs of the bay preset and the rack control, working in real time with the field instruments. The TAS authorizes and documents; the rack controller executes and measures. When the TAS enables a load at a bay, it is granting permission and providing the target and the product; it is the preset that then actually runs the load against the meter and the interlocks.
SCADA overlaps with both but has its own role. Where SCADA supervises the terminal is in the real-time monitoring and control of the process: tank levels, pump status, valve positions, alarms, and the general state of the plant, including the racks as part of that picture. SCADA is about the live condition of the equipment and the process, whereas the TAS is about the transactions and authorizations flowing across the terminal. In many terminals the two are integrated so that, for example, the TAS's tank assignment respects the real inventory SCADA sees and the rack loads appear in the SCADA view, but the responsibilities are distinct: SCADA watches and controls the process, the TAS manages the business of loading.
Understanding this split matters when a terminal considers cloud monitoring, because the questions each layer answers are different. A cloud SCADA or monitoring platform is concerned with the live process, is a pump running, is a tank at the right level, has an alarm fired, and with the historical trends of that process. That complements rather than replaces the TAS, which owns the driver authorizations, the bills of lading, and the reconciliation. A platform such as Merobix focused on remote monitoring of the process gives operators visibility into the plant's real-time and historical condition, while the TAS continues to own the transactional and documentary side, and the two together cover both what the equipment is doing and what business it is transacting.
A bay preset handles the mechanics of a single load: it takes a target quantity, opens the flow valve, watches the meter, ramps down, and closes at the set amount while enforcing local interlocks. A terminal automation system works above that level, deciding whether a driver is authorized, what product and quantity they are entitled to, which tank it comes from, and producing the bill of lading. The preset executes and measures; the TAS authorizes and documents.
SCADA supervises the real-time process, tank levels, pump status, valve positions, and alarms, including the racks as part of the plant picture, while the TAS manages the transactions, driver authorizations, orders, bills of lading, and reconciliation. The two are often integrated so tank assignment respects real inventory and loads appear in the SCADA view, but their responsibilities are distinct. SCADA watches and controls the process; the TAS manages the business of loading.
Reconciliation is the TAS comparing what was actually loaded at the bays against what was ordered and against the tank movements, so discrepancies surface instead of hiding. If more product left the racks than the tanks say was drawn, or an order shows a different quantity than was loaded, the terminal sees it promptly. Reconciliation turns a day of individual loads into an accounting the terminal can trust and feeds accurate numbers back to the business.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.