How to Automate TankSoft Pro

A tank trailer cannot load until the last product is gone

A food-grade tanker that carried latex last week is not a food-grade tanker until somebody proves otherwise, and a wash is the only proof there is. That is the business TankSoft Pro runs: the office behind a tank wash rack, built by Agility ERP for wash providers across the United States and Canada, in the cloud or on a server in the building.

What comes through the gate is not only road tankers. The system handles tank trailers, IBC totes, ISO containers and rail cars carrying liquid and dry bulk, across chemical, food grade and Kosher wash processes, with its workflows grouped the way the business is, into Operations, Finance and ESH.

A wash rack is a bottleneck other people's schedules run through. A carrier's next load waits on a bay, a driver in the queue is burning hours he cannot get back, and the shipper at the far end will not take the trailer without a document saying what came out of it.

The wash ticket is only half of what the shipper wants

The wash takes the best part of an hour. The paperwork around it runs for days.

Every trailer has a prior product and a next product, and the pair decides the procedure. That information arrives by phone, on a bill of lading, in an email from a dispatcher, or written on a card handed through the window. Somebody reads it, picks the wash, and hopes the driver read the right line.

Then the requirements that belong to the customer rather than the trailer. A kosher wash depends on a certification being in date and, for some accounts, on supervision being arranged first. A food-grade wash has a sequence the shipper audits later. A reject means a reclean, and a reclean means a conversation with a carrier who is already late.

Around all of it runs the environmental side, which is not optional. What went down the drain, in what volume, against a discharge permit with limits written into it, reported to whoever issued that permit on their timetable and usually on their own website.

TankSoft Pro

Tomorrow's procedure known tonight Prior product confirmed against the carrier's own load record before the trailer joins the queue, so the wrong wash is caught at seven rather than at the window.

Certifications that expire on paper first Kosher and food-grade approvals read on the register that issues them and matched to the accounts booked this week, expiring ones listed first.

Discharge numbers already assembled Daily volumes and readings collected and set against the limits written into the permit, so the monthly report starts as a file rather than a search.

Invoicing and the washout document leave with the driver

What the software does best is the thing that matters most at a rack: getting the trailer out of the bay with the money already started.

Customer invoicing and complete DOT compliant documentation are produced at the time of service, so a driver leaves with his paperwork and the bill does not wait for Friday. The customer side runs end to end, from check-in at the window through the washout documents to the invoice, with Operations, Finance and ESH workflows carrying the rest of the office. There is also a piece most operational software has no equivalent for: a facility publishes its services and amenities on TankWashDirectory.com, where dispatchers hunting for a bay actually look.

Everything above happens inside your own fence.

Outside it sit the systems that decide whether the trailer turns up and whether the wash is accepted. The carrier's own dispatch system. The shipper's list of approved facilities. The register that shows whether a certification is still in date. The discharge authority's reporting site. Every one belongs to someone else and changes without telling you.

A wash bay that knows tomorrow's prior product tonight

Tomorrow's trailers are already on the schedule tonight, in time to read what everybody else knows about them.

Prior product checked against the carrier's own load record before the trailer is in the queue, so a wash needing a different procedure is known at seven rather than found at the window. Kosher and food-grade approvals read on the register that issues them and matched against this week's booked accounts, expiring ones at the top. Rejects and recleans gathered as they happen with the bay, the operator and the reason attached.

The rest is money and compliance. Wash tickets reconciled with what the carrier's system says it was billed, so a dispute surfaces in days rather than months. Chemical usage read off the supplier's portal against what the bays consumed. Discharge volumes and readings collected daily against the permit limits, so the monthly figure assembles itself.

Discharge reporting is regulated and invoices are money, so the boundary sits where you would put it. Reading, comparing and building the file run unattended. A filing, an invoice or a message to a carrier waits for the person accountable.

The wash bay clock beats the office clock

Racks run all day and the office runs eight hours, which is why this checking always happens after the fact.

WebRun is an AI agent that drives a real Chrome browser, signed in the way your own staff are. It opens TankSoft Pro, reads the schedule and the tickets, then opens the carrier's portal, the certifier's register or the supplier's site and compares what it finds there.

Runs happen on your schedule inside a private environment of your own, and a workflow can be held to a named list of sites. You can watch one while it happens and stop it part way.

Underneath this are the built workflows, each naming the screens it touches and the paper it will not release on its own.