Petroleum and chemical motor carriers operate under some of the most stringent regulatory requirements in the transportation industry. Proper integration of vapor recovery systems, overfill protection, and closed-loop loading architecture is no longer optional. It is a core operational and compliance requirement that directly affects CSA scores, PHMSA audit outcomes, insurance premiums, and driver settlement accuracy.
Strong Tower Consulting has spent more than 18 years helping hazmat carriers translate terminal rack automation signals into actionable, auditable data within their existing technology stack. This guide details the engineering specifications, data architecture, and integration patterns required to achieve true closed-loop loading safety while preserving carrier independence.
Core Engineering Components
1. Scully Overfill Protection Telemetry
The Scully Intellitrol or similar optical liquid level sensing systems remain the industry standard for overfill prevention at loading racks. Modern implementations convert the two-wire Scully signal into a digital state using an edge gateway (typically a ruggedized industrial router with Modbus or discrete I/O). This state is transmitted in real time to the carrier's central system via cellular or Wi-Fi, allowing immediate validation before the EDI 214 status is generated.
When the Scully circuit indicates a full compartment, the system must prevent load tender acceptance and block driver settlement until the overfill protection has been cleared by a qualified technician. This logic is typically enforced through SQL triggers on the load event table.
2. Vapor Recovery Line Pressure Monitoring
Closed-loop vapor recovery requires continuous negative pressure in the vapor return hose. Pressure transducers installed between the tanker vapor valve and the terminal vapor recovery unit feed data to the same edge gateway. Thresholds are set according to 40 CFR Part 63 and state-specific VOC regulations. A pressure rise above -0.5 inches water column for more than 8 seconds triggers an immediate rack interlock and generates a safety event that is written to both the telematics platform and the carrier's SQL Server database.
3. Rack Loading Automation and Safety Lockouts
Terminal rack systems (OPW, Emco Wheaton, or custom PLC installations) must exchange authorization signals with the carrier's telematics gateway before product flow begins. This handshake is typically accomplished through a dry-contact relay or Ethernet/IP interface. Once the Scully, vapor recovery, and grounding systems are all verified, the rack controller releases the loading permit and the carrier system records the exact timestamp for both safety compliance and fuel surcharge validation.
Data Architecture and SQL Schema Patterns
Whether your fleet runs Truckmate, McLeod, TMW, or a custom SQL-based dispatch system, the telemetry must be stored in a normalized, queryable structure. Key tables include:
- LoadEvents - core load record linked to order, driver, and tractor
- OverfillSensorReadings - timestamped Scully state with compartment ID
- VaporPressureTelemetry - pressure readings at 2-second intervals during loading
- RackLockoutEvents - all safety interlocks with reason codes and resolution timestamps
- SettlementImpactLog - links safety events to driver pay calculations and detention billing
These tables are joined to existing EDI 204 tender, 214 status, and 210 freight bill tables to create a single source of truth for both operational dashboards and regulatory audits.
Strong Tower Consulting, LLC and our sister company Exspeedite LLC are separately organized entities under common ownership. We never require you to purchase or license dispatch software. Our role is to design and implement the integration architecture that lets you extract maximum value from the systems you already own.
Operational Impact on Carrier Processes
When properly implemented, closed-loop loading telemetry eliminates manual paperwork at the rack, reduces spill incidents to near zero, prevents fraudulent loading claims, and provides defensible data for fuel tax (IFTA), driver settlements, and CSA/SMS scoring. The same dataset can be used to optimize fuel surcharge recovery and automatically calculate detention when loading delays are caused by terminal equipment issues.
Implementation Roadmap
Strong Tower begins every hazmat telematics engagement with a detailed current-state assessment of your existing TMS (Truckmate, McLeod, TMW), ELD provider, and terminal relationships. We then design a vendor-neutral middleware layer that normalizes signals from Scully systems, vapor recovery sensors, and rack automation equipment into a consistent JSON payload that is consumed by your SQL Server or cloud data warehouse.
Our clients routinely achieve full integration in under 14 weeks without disrupting daily dispatch operations.
Call 763-244-1373 to speak with our transportation engineering team.
Frequently Asked Questions
What is Scully overfill protection and how is it integrated with fleet telematics?
Scully overfill sensors use optical or thermistor technology to detect liquid levels in hazmat tankers. When integrated with modern telematics systems, the sensor state is transmitted in real time via API or direct serial-to-IP conversion, allowing the carrier's TMS to block dispatch certification until the overfill circuit is confirmed clear.
How does vapor recovery line pressure monitoring prevent environmental violations?
Closed-loop vapor recovery systems must maintain negative pressure to prevent VOC emissions. Continuous pressure transducers installed on the vapor return line feed data to the onboard gateway. If pressure rises above EPA-defined thresholds, the system triggers an immediate loading interlock and alerts the terminal automation system.
Can a hazmat carrier implement closed-loop loading safety lockouts without replacing their existing TMS?
Yes. Strong Tower Consulting designs vendor-neutral integration layers that connect Scully, vapor recovery, and rack automation systems to any major TMS platform including Truckmate, McLeod, or TMW. Carriers retain full ownership of their data and never need to purchase additional dispatch software.
What SQL schema patterns are used to store hazmat loading telemetry for CSA and PHMSA compliance?
A normalized schema typically includes tables for LoadEvents, OverfillSensorReadings, VaporPressureTelemetry, RackLockoutEvents, and DriverSettlementImpact. These tables are joined to existing EDI 214 status and fuel surcharge tables to provide complete audit trails for both safety scoring and driver pay calculations.