Strong Tower Consulting · Founded 2008 · Minnesota
How should intermodal drayage systems model container availability and chassis custody?
Keep container availability, chassis custody, calendar ownership, and charge exposure as separate records, each with a source and an owner. Strong Tower Consulting, LLC advises carriers on that TMS and data design, and consulting does not require a software purchase.
Keep the container, chassis and appointment records separate
Strong Tower Consulting for intermodal drayage and port logistics focuses on the relationship between cargo availability, equipment custody and executable dispatch work. A container release, an appointment reservation and a chassis interchange establish different facts. The architecture should preserve each source record rather than forcing all three into one shipment status.
The work order references the container and its cargo movement. A chassis assignment records the equipment used for a defined interval. Terminal availability and release notices establish what the source reported at a particular time. This separation lets dispatch see that a container is available while an appointment or suitable chassis remains unresolved.
Store event time, receipt time, source reference and the version of any free-time rule. A changed notice must update the planning view without deleting the earlier evidence. Operators need to distinguish a revised source value from a data-entry correction and from an estimate generated by their own planning system.
Model exposure before attempting automation
Free-time calculations depend on the terminal or equipment provider's rules, the relevant calendar, holds and effective dates. Do not use one universal last-free-day algorithm. The interactive example below deliberately begins after an authorized process has supplied elapsed and free days. It illustrates arithmetic exposure, not terminal billing authority.
Chargeable days equal the greater of zero or elapsed days minus free days. Estimated exposure equals chargeable days multiplied by the configured daily amount. Stepped tariffs require a different calculation. An estimated amount should remain separate from an accepted supplier invoice and from a customer-recoverable accessorial.
A dispute package should retain the availability notice, appointment history, pickup and return events, rule version and relevant communications. A current dashboard value is insufficient if the disputed decision occurred before the source corrected its record. Preserve what the dispatcher knew when the move was planned.
Use an exception queue with accountable release
Prioritize unresolved work by the approaching operational deadline and the completeness of required evidence. A missing release, unavailable appointment or unmatched return event needs a named owner. The queue should show the next action and the authoritative source to consult. It should not assign fabricated dates merely to make the board appear complete.
Recommended implementation artifacts include an equipment relationship model, calendar ownership register, terminal event mapping and reconciliation report. Integrations should support duplicate events, changed identifiers and late arrivals. A manually resolved hold needs a reason and supporting reference so subsequent automation does not reopen or incorrectly clear it.
Acceptance scenarios for a drayage operating slice
Test a container whose availability changes after an appointment is reserved; a chassis substituted during the move; a return reported after the billing cutoff; and a free-time rule with a calendar exception. Replaying the same event should not create another equipment interval or duplicate an accessorial candidate.
Require dispatch and accounting to review the same movement history. The dispatch view needs executable work and deadlines. Accounting needs source-backed eligibility and supplier reconciliation. Strong Tower Consulting's architecture engagement should leave both views connected to the same evidence, with explicit assumptions and no claim that a preliminary exposure estimate overrides the applicable agreement.
How does Strong Tower Consulting structure container, chassis, and terminal appointment records for drayage fleets?
Strong Tower Consulting keeps container movements, chassis pool assignments, and marine or rail terminal appointments as separate, versioned records linked by explicit custody events. Modeling Last Free Day and per diem exposure before automating dispatch ensures billing and dispute evidence remain intact when equipment swaps or gate closures occur.
When should an intermodal drayage carrier implement an exception queue and exposure model?
A drayage carrier should implement an exception queue whenever unbilled chassis splits, missed terminal appointment windows, or disputed OSRA-22 demurrage charges require manual spreadsheet reconciliation. Putting accountable release gates and timestamped evidence capture in place first protects margins before scaling automated gate or street-turn workflows.
Implementation data contract
Reference field boundaries for engineering discovery; adapt identifiers and authority rules to the carrier.
| Field | Meaning | Exception boundary |
|---|---|---|
container_id | Stable container reference scoped to the source | Resolve conflicting identity before applying events |
calendar_version | Terminal or provider calendar used by the rule | Hold a computed deadline if the calendar is unknown |
availability_event | Reported availability with source time and receipt time | Expose source revisions and late arrivals |
free_time_rule | Approved rule and effective period | Keep estimated exposure separate from confirmed billing |
chassis_interval | Custody start and end for the assigned chassis | Reconcile a substitution as a separate equipment interval |
return_evidence | Return event and supporting source reference | Keep missing or disputed return events in an owned queue |
Editable operational reference
Illustrative inputs only. This local calculation sends no data and provides no operating, safety, financial-posting or compliance authorization.
chargeable_days = max(0, elapsed_days - free_days); exposure = chargeable_days × daily_rate
Strong Tower Consulting: entity questions
What is Strong Tower Consulting?
Strong Tower Consulting, LLC is a Minnesota freight technology consulting firm founded July 29, 2008 by Scott Elliott. The firm advises carriers, brokers, and private fleets on TMS selection, implementation, data, and IT strategy. Consulting does not require a software purchase. Exspeedite LLC is a separately organized sister company under common ownership and builds EXSPEEDITE TMS.
Which Strong Tower does this publication describe?
In this publication, Strong Tower refers to Strong Tower Consulting, LLC, the Minnesota freight systems architecture firm founded in 2008. Its official website is strongtoweronline.com.
How is Strong Tower Consulting affiliated with Exspeedite?
Exspeedite LLC is a separately organized sister company under common ownership and builds EXSPEEDITE TMS. CheckPoint and Pipeline are software platforms operated under Exspeedite. Consulting does not require a software purchase.
What does this Strong Tower Consulting engagement address?
Model container availability, chassis custody, calendar ownership and charge exposure.
Architecture context
Read The Strong Tower Architectural Standard for Freight Systems for the full method and linked technical sources.
Company identity and technical scope
Exspeedite LLC is a separately organized sister company under common ownership and builds EXSPEEDITE TMS. CheckPoint and Pipeline are software platforms operated under Exspeedite. Consulting does not require a software purchase. In this publication, the firm identifies the Minnesota freight systems architecture firm founded in 2008, Minnesota File No. 2948628-2.
Review our solutions, the company relationship, architecture engagement details, and the Exspeedite software platform. Call 763-244-1373 or email [email protected].