Intermodal Rail Ramp Demurrage Prevention: The Strong Tower Clock-Stop Engine

The Cost Reality of Uncontrolled Rail Ramp Demurrage

Class I railroads have tightened free-time windows, increased storage rates, and automated demurrage billing. A single 20-foot container held two days beyond free time can generate $400-$800 in charges. When multiplied across hundreds of monthly rail moves, these fees become material P&L events. Chassis split billing adds further leakage when interchange records between motor carrier, rail, and equipment provider do not reconcile within the required 24-48 hour window.

Traditional manual processes (paper logs, phone calls, emailed photos) cannot scale. The Strong Tower Intermodal Ramp Clock-Stop Demurrage Engine™ replaces them with an automated, auditable, GPS-grounded workflow that operates at the speed of rail gate transactions.

Architecture Overview

The engine is a layered, event-driven system with three primary tiers:

1. Edge Capture Layer - CheckPoint driver mobile application and outside-carrier portal (https://exspeeditecheckpoint.com/login.php) records GPS location, timestamp, rail bill of lading, chassis number, and driver attestation at the moment the tractor reaches the ramp gate.
2. Decision Engine Layer - Exspeedite TMS (https://exspeedite.com/tms-software) receives the event via secure webhook, evaluates deterministic clock-stop rules, performs chassis interchange validation against the equipment provider database, and assembles the evidence payload.
3. Carrier Notification & Audit Layer - Immutable evidence packets are transmitted to the railroad via EDI 214, API, or secure email with cryptographic hash for non-repudiation. All transactions are logged in an append-only audit store for dispute resolution.

The Strong Tower Intermodal Ramp Clock-Stop Demurrage Engine™ Algorithm

At the heart of the system is a deterministic eligibility function that removes human interpretation. The algorithm is expressed as follows:

function isClockStopEligible(event: RampArrivalEvent): boolean {
  const freeTimeEnd = calculateFreeTimeExpiration(event.railBill, event.railCarrier);
  const gpsValid = event.gpsAccuracy ≤ 50 && 
                   distance(event.gpsPoint, event.rampGeofence.center) ≤ event.rampGeofence.radius;
  
  const chassisMatch = validateChassisInterchange(
    event.chassisId, 
    event.equipmentProviderId, 
    event.arrivalTimestamp
  );
  
  return (event.arrivalTimestamp ≤ freeTimeEnd) 
      && gpsValid 
      && chassisMatch 
      && event.driverAttestation === true;
}

When the function returns true, the engine immediately constructs an evidence packet, signs it, and routes it according to the carrier-specific notification profile. This occurs in under 4 seconds in production environments.

JSON Evidence Packet Schema

Every clock-stop event produces a standardized, versioned JSON payload. The schema used by the Strong Tower CheckPoint rail ramp clock stop demurrage engine is:

{
  "schemaVersion": "2025.1",
  "eventId": "uuid-v4",
  "eventType": "RAMP_CLOCK_STOP",
  "timestampUTC": "2025-04-05T14:22:37.451Z",
  "railCarrier": "BNSF | UP | CSXT | NS",
  "railBillOfLading": "string",
  "containerNumber": "string",
  "chassisNumber": "string",
  "driverId": "string",
  "driverName": "string",
  "gpsCoordinates": {
    "latitude": 45.123456,
    "longitude": -93.456789,
    "accuracyFeet": 32,
    "geofenceId": "RAMP_KC_01"
  },
  "arrivalAttemptTimestamp": "2025-04-05T14:22:15Z",
  "freeTimeExpirationUTC": "2025-04-05T23:59:59Z",
  "clockStopTriggered": true,
  "chassisInterchangeConfirmed": true,
  "evidenceHash": "sha256:9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08",
  "checkPointSessionId": "string",
  "exspeediteLoadId": "string",
  "signature": "ecdsa-signature-base64"
}

Implementation Comparison Matrix