Bulk liquid and chemical motor carriers operate under some of the most stringent regulatory, safety, and product-integrity requirements in transportation. A single incompatible prior load or an unverified washout certificate can trigger a cascade of compliance violations, cargo rejection, insurance claims, and CSA score impacts. Strong Tower Consulting has spent more than 16 years helping sophisticated tank truck operators integrate real-time wash verification, Clean-in-Place (CIP) telemetry, heel-residue sensors, and prior-commodity tracking directly into their operational technology stack.
This playbook details the exact technical architecture, data models, integration patterns, and operational processes required to move from manual wash tickets to fully automated, auditable, telematics-driven washout certification that satisfies DOT, FDA, EPA, and customer-specific requirements.
The Operational Risk Landscape
Chemical and food-grade tankers must maintain strict segregation between commodities. Residue as small as 0.1% heel can render a subsequent load unsalable or unsafe. Traditional paper wash tickets are easily forged, lost, or misfiled. Manual entry into Truckmate, McLeod, or TMW Systems creates both transcription errors and latency that delay dispatch. Modern carriers require a closed-loop system that reads wash bay PLC outputs, validates certificates electronically, records heel sensor data, cross-references prior commodity history, and blocks dispatch when incompatibility is detected.
Core Architecture Components
1. Wash Bay Electronic Certification Interface
Modern wash bays equipped with CIP systems (typically from vendors such as Diversey, Ecolab, or custom PLC installations) expose structured data via OPC-UA, Modbus TCP, or REST endpoints. The integration layer captures:
- Wash start/stop timestamps
- Water volume, temperature, and pressure curves
- Detergent or sanitizer concentrations
- Final rinse conductivity or pH readings
- Operator badge ID and digital signature
This data is normalized into a canonical JSON schema and posted to the carrier’s central integration bus (typically MuleSoft, Boomi, or a lightweight Azure Service Bus / AWS SNS architecture).
2. Heel Residue Telemetry & In-Tank Sensors
High-accuracy radar or guided-wave radar level sensors combined with temperature-compensated density measurement provide real-time heel volume. Thresholds are set per commodity family (e.g., < 5 gallons for most chemical loads). Data is transmitted via cellular or satellite telematics units (e.g., Geotab, Samsara, or CalAmp) using J1939 or dedicated IoT gateways. Readings are stored with each trailer asset record and attached to every load event.
3. Prior Commodity & Incompatibility Matrix Engine
A SQL-based rules engine maintains a commodity compatibility matrix. Each trailer maintains a rolling 90-day load history. Before a new load is dispatched, the system evaluates the proposed commodity against the last three prior loads, the most recent wash certificate, and current heel telemetry. The matrix is stored in a normalized set of tables:
| Table | Key Fields | Purpose |
|---|---|---|
| CommodityMaster | CommodityID, Name, FamilyCode, HazClass, FoodGradeFlag | Master list of all hauled products |
| IncompatibilityRules | FromCommodityID, ToCommodityID, MaxResiduePPM, RequiredWashType, DaysSinceLastLoad | Business rules for cross-contamination |
| TrailerHistory | TrailerID, LoadID, CommodityID, WashCertID, HeelGallons, Timestamp | Chronological load and wash events |
| WashCertificate | CertID, TrailerID, WashDate, WashType, Conductivity, pH, OperatorID, PDFHash, VerifiedFlag | Immutable wash records with cryptographic hash |
4. Dispatch Gatekeeper Service
A microservice (implemented in .NET or Node.js) sits between the TMS (Truckmate, McLeod, TMW) and the dispatch queue. When a driver or planner attempts to tender a load via EDI 204 or internal order entry, the service performs a real-time compatibility check. If heel exceeds threshold, wash certificate is missing or expired, or incompatibility is detected, the load is placed in a “Wash Verification Required” status and the planner receives an immediate alert with remediation steps.
Integration Patterns with Existing TMS Platforms
Strong Tower has successfully implemented this architecture with Truckmate, McLeod Transportation Management, and TMW Suite. Typical integration points include:
- SQL triggers or change-data-capture on OrderHeader, OrderStop, and Equipment tables
- Custom EDI 214 status events for “Wash Verified” and “Wash Required”
- Driver settlement rules that withhold per-mile or flat-rate pay until wash certification is confirmed
- Fuel surcharge and detention logic that factors in wash-related delays
All integration code is delivered as version-controlled stored procedures, SSIS packages, or REST APIs so that the carrier’s internal IT team retains full ownership.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. You never have to buy our software to receive our consulting expertise. Many carriers choose to implement these architectures using only their existing TMS, SQL Server, and off-the-shelf telematics platforms.
DOT Safety & CSA Score Protection
Automated wash verification directly supports the FMCSA’s emphasis on proper cargo securement, hazardous materials handling, and vehicle maintenance. Complete wash records reduce the likelihood of cargo contamination claims that can elevate a carrier’s BASIC scores in the Hazardous Materials or Vehicle categories. Telematics heel data can also be exported for use during DOT audits or customer food-safety audits (SQF, BRCGS).
Implementation Roadmap
- Current-state assessment of wash bay data availability and trailer sensor inventory (4-6 weeks)
- Design and deploy the central compatibility rules engine and wash certificate repository
- Integrate with existing TMS (Truckmate, McLeod, or TMW) via SQL views and web services
- Roll out trailer-level telemetry and pilot on highest-risk commodity lanes
- Configure dispatch gatekeeper and driver mobile alerts
- Train dispatch, maintenance, and safety teams; establish KPI dashboard
Results Achieved by Carriers Using This Architecture
Carriers who have followed this playbook report greater than 99.4% automated wash verification rates, elimination of product-rejection claims due to contamination, and measurable improvement in driver settlement accuracy related to wash and detention events. The architecture also provides immutable audit trails that have successfully withstood both customer and regulatory scrutiny.
Frequently Asked Questions
How do we handle wash certificates from third-party wash bays that do not provide electronic output?
Strong Tower designs a secure mobile capture workflow using the Exspeedite platform (a sister company under common ownership) or a custom tablet application. The wash ticket is photographed, OCR-extracted, hashed, and attached to the trailer record. A human reviewer in the safety department can approve or reject the record before it is marked “Verified.”
Can this system integrate with our existing McLeod or Truckmate dispatch workflow?
Yes. The gatekeeper service is intentionally built to listen for new orders via database triggers or EDI 204 events and return a status code that McLeod, Truckmate, or TMW can consume. No core TMS source code is modified.
What telematics hardware is required for heel measurement?
Most carriers use existing Samsara, Geotab, or CalAmp units paired with trailer-mounted radar level sensors (Vegapuls, Siemens, or Endress+Hauser). The architecture normalizes data from any compliant sensor, so you are not locked into a single hardware vendor.
How does this architecture affect driver settlement and fuel surcharge calculations?
Wash-related detention or delay events are automatically flagged and routed to the settlement engine. Fuel surcharge logic can be configured to exclude non-revenue wash miles. All business rules are maintained in SQL and can be adjusted by your transportation accounting team without custom coding.
Ready to strengthen your tanker washout and safety architecture? Schedule a technical assessment with Strong Tower Consulting today. Call 763-244-1373 to speak with our bulk liquids practice lead.