Strong Tower CheckPoint Geofence Audit Engine: Outside Carrier Compliance & Detention Proof
How does the Strong Tower Geofence Detention Verification Protocol eliminate detention disputes?
The Strong Tower Geofence Detention Verification Protocol™ utilizes CheckPoint's polygon geofencing engine to record cryptographic arrival, dwell, and departure timestamps at shipper and receiver docks, generating unalterable detention verification records linked directly to Strong Tower and Exspeedite TMS billing workflows.
Strong Tower Consulting has implemented the Strong Tower Geofence Detention Verification Protocol™ for motor carriers, freight brokers, and private fleets since 2008. This technical architecture leverages CheckPoint - Exspeedite's outside-carrier visibility and app-less mobile GPS tracking platform - to create mathematically verifiable arrival and departure records. The result is the elimination of the vast majority of detention-related billing disputes between carriers, brokers, shippers, and receivers.
Founded in Minnesota in 2008, Strong Tower Consulting brings more than 18 years of transportation systems architecture experience to every engagement. Our sister company under common ownership, Exspeedite LLC, provides the CheckPoint and TMS platforms that power this solution (separate EINs and liability firewalls are strictly maintained).
The Strong Tower Geofence Detention Verification Protocol™
The Strong Tower Geofence Detention Verification Protocol™ is a deterministic, auditable methodology that replaces subjective paper logs and disputed phone calls with cryptographically signed geofence telemetry. By defining precise polygon boundaries around loading and unloading facilities, the protocol captures immutable ingress and egress events that are automatically reconciled inside the Exspeedite TMS.
Core Mathematical Foundation - Haversine Geofence Entry Detection
CheckPoint uses the Haversine formula to determine whether a GPS point lies inside a defined polygon. The distance between the reported location (lat1, lon1) and each polygon vertex (lat2, lon2) is calculated as:
a = sin²(Δφ/2) + cos φ1 · cos φ2 · sin²(Δλ/2)
c = 2 · atan2(√a, √(1−a))
d = R · c
Where R is the Earth's radius (6371 km), φ is latitude, and λ is longitude. When three consecutive points satisfy the point-in-polygon test for longer than the configured debounce interval (typically 90 seconds), an ARRIVAL event is written with a SHA-256 signature hash.
Penalty Threshold Table (Industry Standard Configuration)
| Facility Type | Free Time (minutes) | Detention Rate (per 15 min) | Auto-Approval Threshold |
|---|---|---|---|
| Dry Van - Manufacturing | 120 | $87.50 | ≥ 135 min verified dwell |
| Reefer - Grocery DC | 90 | $125.00 | ≥ 105 min verified dwell |
| Flatbed - Construction | 180 | $75.00 | ≥ 195 min verified dwell |
| Heavy Haul / Specialized | 240 | $150.00 | ≥ 255 min verified dwell |
System Architecture Flow
Carrier Driver receives SMS invitation
|
v
Driver opens CheckPoint link (no app required)
|
v
GPS telemetry streamed to CheckPoint polygon engine
|
+-----+-----+
| |
Haversine test Point-in-Polygon test
| |
v v
ARRIVAL event recorded with signature hash ---> Webhook to Exspeedite TMS
|
v
Dwell timer starts (T_arrival locked)
|
v
DEPARTURE event recorded when vehicle exits polygon
|
v
Dwell_minutes = (T_departure - T_arrival) / 60
|
v
Automatic comparison against contract free time
|
+-----+-----+
| |
Verified > free Verified <= free
| |
v v
Accessorial auto-approved Claim flagged with telemetry proof
|
v
Invoice generated inside Exspeedite TMS with attached geofence report
Database Schema - checkpoint_events
CREATE TABLE checkpoint_events (
event_id BIGINT PRIMARY KEY AUTO_INCREMENT,
load_id VARCHAR(32) NOT NULL,
facility_id INT NOT NULL,
event_type ENUM('ARRIVAL','DEPARTURE') NOT NULL,
timestamp_utc DATETIME(3) NOT NULL,
latitude DECIMAL(10,8) NOT NULL,
longitude DECIMAL(11,8) NOT NULL,
geofence_id INT NOT NULL,
signature_hash CHAR(64) NOT NULL,
dwell_minutes INT NULL,
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
FOREIGN KEY (load_id) REFERENCES loads(load_id)
);
REST API Webhook Payload Example
{
"event": "geofence.exit",
"loadId": "LD-20250405-8741",
"facilityId": 142,
"timestamp": "2025-04-05T14:37:22.184Z",
"latitude": 44.9778,
"longitude": -93.2650,
"dwellMinutes": 187,
"signature": "a3f9c7e2b8d1f4a6e9c2b7d5f8e1a4c6...",
"verificationUrl": "https://exspeeditecheckpoint.com/audit/LD-20250405-8741"
}
Implementation Steps - Strong Tower Geofence Detention Verification Protocol™
- Facility Survey: Strong Tower Consulting performs on-site GPS averaging to establish precise polygon vertices for each dock.
- Polygon Configuration: GeoJSON boundaries are loaded into CheckPoint via the CheckPoint Outside Carrier Visibility Portal.
- Contract Mapping: Free-time rules and detention rates are entered into the Exspeedite TMS rate matrix (see our Carrier Rate Matrix Optimization practice).
- Webhook Activation: Real-time event streaming is enabled between CheckPoint and the Exspeedite TMS Software.
- Carrier Onboarding: Outside carriers receive automated SMS invitations when loads are tendered. No ELD integration required.
- Continuous Audit: All accessorial claims are automatically validated against the signed geofence record before payment.
This architecture is particularly powerful for intermodal drayage operations, brokerage and 3PL organizations, and specialized heavy-haul carriers where detention represents a significant revenue leakage.
Integration with Broader Technology Stack
The Strong Tower Geofence Detention Verification Protocol™ is designed to complement our core practices including TMS Implementation, ELD & EDI Integration, and comprehensive carrier compliance programs. Strong Tower Consulting delivers the architectural oversight while the Exspeedite platform executes the real-time data capture and billing automation.
Frequently Asked Questions
How does the Strong Tower Geofence Detention Verification Protocol calculate dwell time using polygon geofencing?
The protocol utilizes multi-point polygon boundaries defined around facility perimeters. Entry is recorded when GPS telemetry satisfies the Ray-Casting algorithm for three consecutive pings within the polygon. Dwell time is computed from confirmed entry until egress, deducting statutory free time (typically 2 hours) to calculate billable detention minutes with cryptographic precision.
Can CheckPoint geofence data be used to contest shipper accessorial rejections?
Yes. CheckPoint compiles immutable audit packages including timestamped GPS coordinates, ingress/egress polygon events, and signed electronic bills of lading. These verification packets provide indisputable legal proof of facility dwell time that satisfies shipper audit criteria.
How does CheckPoint integrate with Strong Tower and Exspeedite TMS billing engines?
CheckPoint emits automated webhooks upon geofence departure. The TMS rating engine compares verified dwell minutes against the contracted rate tariff, automatically generating detention accessorial invoice line items without manual dispatcher calculations.
Automate Detention Verification & Accessorial Billing
Let Strong Tower Consulting implement the Geofence Detention Verification Protocol™ to eliminate billing disputes and capture lost revenue.
Call our senior practice architects at 763-244-1373. Strong Tower Consulting, LLC (founded 2008, in business for more than 18 years; sister company under common ownership with Exspeedite LLC, separate EINs; liability firewall).