From pickup request to reset, in one shared record
AFMS gives tank owners, vendor dispatchers, drivers, and back-office teams one shared workflow from request creation and acknowledgment through scheduling, dispatch, at-tank proof, invoice or credit closeout, and reset for the next cycle.
More than a monitor. More than a pickup portal.
The portal is the operating flow that connects tank context, request ownership, dispatch, field execution, proof, and closeout.
Canonical workflow from request to reset
Requested > Acknowledged > Scheduled > Complete > Closeout > Reset
Requested
Pickup demand exists from sensor context or manual entry.Acknowledged / Pending Scheduling
A responsible party has received the request and owns it, but a pickup window is not yet confirmed.Scheduled / Dispatched
The pickup window exists and truck / driver ownership is visible.Pickup Complete
Core field work is done and gallons are captured.Invoice / Credit Pending
Operational work is done, but financial closeout is still open.Closed
No further operational action is pending.Reset / Ready
The cycle is cleared and the asset is ready for the next request.Dispatch with ownership, not guesswork
AFMS helps dispatch teams move past "someone saw the alert" and into true ownership. Requests can be acknowledged, kept visible while pending scheduling, then assigned to a truck and driver with a documented handoff into field work.
At-tank execution built for drivers
The QR-first iOS and Android app helps drivers confirm the right asset, preserve route context, and complete the stop in a few taps. Offline store-and-forward lets crews capture work first and sync later without losing the record.
Proof customers can trust
AFMS can capture before/after state, gallons, photos, signatures, timestamps, and exception notes at the tank. That proof becomes part of the shared history instead of living in separate texts, photos, or paper receipts.
Closeout that includes the back office
The workflow does not end at "pickup complete." AFMS supports invoice or credit closeout so financial references can stay tied to the operational record before the request resets.
Value by role
Dispatcher / vendor admin
Cleaner queue ownership and scheduling visibility.
Driver / technician
Faster at-tank workflow with less paperwork.
Site manager
Cleaner proof and fewer update calls.
Back office
Invoice or credit closeout tied to the service record.
Spill and safety exception path
If a spill or safety issue is found during routing or field execution, AFMS can create a spill report, raise stakeholder notifications, place the asset into digital lockout/tagout, and keep follow-up service or inspection actions attached to the same timeline.
Want pickup coordination that is easier to execute and easier to prove?
See how AFMS connects request ownership, dispatch, field proof, and closeout.