Skip to content

Features

Thirteen modules. One audit trail.

Thirteen automation modules and three Motive fleet mirrors. Each is a self-contained capability with its own API route, carrier handler registry, database records and dashboard page — so you can adopt one, or all of them, without changing how the rest behave.

Execution model

Three ways a module runs.

Your TMS and your operators share the same doors. What differs is only how long Neo keeps working after it answers.

Instant

Runs inline in the request and answers with full results. The operational modules — billing, J1, chassis stock and bookings, the calculator — are instant on purpose: a dispatcher wants the answer now.

Scheduled

Registers a cron on the Central-Time clock — or a single moment, for a timed chassis booking — and keeps running: read results back, edit the watchlist, pause, resume or retrace on demand. The database, not the queue, is the source of truth for every schedule.

Dashboard-only sync

The Motive mirrors — geofences, drivers, vehicles — have no API route at all. They sync nightly, optionally every quarter hour, and exist so the other modules can measure a wait or a lane instead of guessing it.

The catalogue

Every module, in detail.

Live today unless marked experimental or next release. Coverage per carrier is on the integrations page.

Instant + Scheduled

Import Container Tracing

Trace inbound containers across BNSF, CN, CP, CSX, NS and UP for ETA, last free day, storage and customs holds and the full event history. Run once, or put a watchlist on a Central-Time schedule and get emailed only when something moved — with a morning brief that says what is at stake today.

  • ETA, last free day, holds and events normalized to one shape
  • Live progress while a run is on the portals
  • A dispatcher's report: next action, dollars at stake, calendar note
  • Change-gated email reports or a single daily digest
  • Finished units retire themselves from the watchlist

BNSF · CN · CP · CSX · NS · UP

Instant + Scheduled

Export Booking Tracing

Trace outbound bookings for earliest receiving date, rail ingate cutoffs, vessel and port-of-load details and revision tracking — the same instant-or-scheduled model, live progress and notification pipeline as import.

  • Booking revisions surfaced the moment a line changes them
  • Cutoff countdowns on the Coming-due board
  • Same watchlist, digest, spreadsheet upload and CSV tooling as import

COSCO · Evergreen · MSC · ONE · Yang Ming

Instant + Scheduled

Empty Return Check

Batch-check empty-return locations for containers across ten shipping lines, inline, with a well-formed row per container — even for a line that is not wired yet. Schedule it and get told only when a return location changes.

  • Ten steamship lines behind one request
  • Pickup and return pairs, portal-only pickups handled
  • Scheduled checks with on-change alerts or a daily digest

CMA CGM · ZIM · COSCO · Evergreen · Hapag-Lloyd · HMM · Maersk · MSC · ONE · OOCL

Instant + Scheduled

Empty Return Check — Chassis

One public page read per pool, no login: CCM's return grid, DCLI's seven region pages and FlexiVan's twelve pools across 108 depots. Every depot comes back with the sizes it takes, its published hours and whether it is open right now. Run once, or schedule it and be told when a depot gains or loses a size.

  • Provider › Pool › Region › Depot, the one chassis vocabulary
  • Sizes accepted, published hours and open-now per depot
  • On-change alerts by email or in the dashboard bell

CCM · DCLI · FlexiVan

Instant

Chassis Availability

Read TRAC's pools one market at a time, CCM's grid for today or tomorrow, or any of DCLI's seven region pages — up to five checks in one request — and list every location with its count. A row with stock books in one click; every location keeps a 30-day history. A check is a read: nothing is booked unless the dispatcher books.

  • TRAC in 31 markets, CCM today or tomorrow, DCLI's 202 locations
  • One-click Book from any row with stock
  • Stock board of each pool's newest read, 30-day history per location

TRAC · CCM · DCLI

Instant + Scheduled

Chassis Reservation

Reserve chassis by size, class, pool, region, depot and date. TRAC end to end; CCM through its dated grid across all 89 depots, cancellable with a reason; DCLI as a release request emailed to the depot's contact with the reply read back. Timed bookings fire at a Central-Time moment and retry until booked.

  • Book now or book at a moment, with retry-until-booked
  • Force-book and status polling for pending TRAC orders
  • Booking receipts and pool-availability captures kept as evidence
  • Cancel from the API or the dashboard

TRAC · CCM · DCLI

Instant

Chassis Provider Lookup

Look up to ten chassis at once in the public GIER registry for ownership, current IEP, pool, license plate and FHWA inspection — reCAPTCHA solved per chassis so nobody on your team has to — with results pushed live to the page as they land.

  • Owner, IEP, pool, plate and inspection in one answer
  • Ten chassis from one paste box, live updates
  • Stored registry payload for audit

GIER registry

Instant

Rail Billing — Empty

Submit empty rail billing per container: Yang Ming over its portal, Evergreen, Hyundai, Maersk, MSC and ZIM over direct steamship-line email. Every letter is signed with your company identity and logged with its Message-ID.

  • Portal or email per carrier, chosen automatically
  • Never bills the same box twice
  • TEST mode by default; LIVE requires an explicit switch

Yang Ming · Evergreen · Hyundai · Maersk · MSC · ZIM

Instant

Rail Billing — Laden

The sibling module for loaded containers: Maersk over direct email, ZIM over its dispatch form with hazmat routed by email. Destination comes back as an output, not a guess.

  • Hazmat detection routes to the right channel
  • Booking-level validation before any send
  • Delivery flips the record only when the mail is accepted

Maersk · ZIM

Instant

J1 Gate Records

Download ingate/outgate records for containers, trailers and chassis at Class I rail ramps, up to fifty pieces of equipment from one yard per run — and enrich them with measured dwell from your Motive geofences.

  • Fifty equipment numbers per run, per-line flags
  • Receipt images and raw portal payloads stored
  • Retry only the failed rows

BNSF · CN · CSX · NS · UP

Instant + Scheduled

Delivery Order Parsing

Drop one to fifty delivery-order PDFs on the form, or send signed links from your TMS. Neo recognizes the layout, prefills the form, and returns reference numbers, bills of lading, pickup and delivery locations and per-container details — import and export flavors — with every assumption it had to make listed beside the row.

  • Per-customer format adapters, layout recognized on upload
  • Every parsed row names what it had to assume
  • A stored batch can be parsed again after a format fix
  • Every-run digest so a missed document is never silent

Import: GOLDEN · OEC · OOCL · FNS · YANGMING · MAGID · MAERSK — Export: OEC · EUSU

next releaseInstant

Overweight Rules

Your overweight rules — by equipment, lane and permit — kept as a versioned table and applied wherever a weight shows up: a parsed delivery order, a laden billing, a J1 gate record. Validate one to five hundred boxes in a call, or let the verdict appear inline where the dispatcher already is.

  • Rules imported from your own sheet, every change logged
  • Verdicts inside Parse DO, laden billing and J1 listings
  • Bulk validation, one to five hundred boxes

Your rules, your lanes

experimentalInstant

EDT / LDT Calculator

Back-calculate the earliest and latest departure time from the delivery appointment: measured yard loading times, measured lane transit between yards your fleet actually runs, a driver hours verdict and a ready-to-send driver message. The module reports its own accuracy and suggests tuning — nothing self-adjusts.

  • Lane times mined nightly from geofence visits
  • Hours-of-service verdict beside the window
  • Measured accuracy and calibration suggestions

Your fleet's own lanes

Dashboard only

Fleet Mirrors

Read-only mirrors of your Motive geofences (with per-yard wait statistics and who is inside right now), licensed drivers (with hours-of-service and live locate) and vehicles (with a stored day-by-day location trail). Nightly sweeps, optional quarter-hourly refreshes, CSV everywhere.

  • Median and P90 wait per yard, not just the mean
  • Inside-now cross-checked against live GPS
  • A truck's day: summary, events, full trail

Motive

Roadmap

What comes next, in order.

Four planned modules, each built the way the live ones are: its own route, audit trail and dashboard page. No dates here — the changelog records what shipped, and the order can change when a customer needs one sooner.

planned

Shipment Monitoring

Watch a move through Motive: stuck at the ramp, detention, late, arriving.

Register a shipment as one container move with ordered stops — rail pickup, chassis depot, customer warehouse, empty return — and Neo watches the assigned truck through Motive every few minutes. It derives arrived, departed and dwell per stop with a GPS cross-check, and raises the action each situation calls for.

  • Pre-detention, detention start and detention end notices, with free time per stop
  • Late-delivery risk, pre-arrival and arrival notices, first to the dispatcher, then to the customer
  • A Today board of decision cards and one-click customer letters

Any yard or customer site in your Motive geofences

planned

Shipment Management

The load, its stops and its driver in one record the modules share.

A shipment record that the tracing, chassis, billing and monitoring modules all hang off: import the day's list from your TMS or a sheet, assign a driver, see every portal fact about the container beside the stops it has to make, and swap a driver or a stop without re-keying anything.

  • Import the day's moves from a spreadsheet or the TMS API, with customers and contacts
  • Load-to-driver assignment with the hours-of-service verdict beside it
  • Every module's result for the container shown on the shipment, newest first
  • Create, update and swap dispatches from the API or the dashboard

Your TMS, or a spreadsheet

planned

Container Reservation

Book the container pickup the way Neo books the chassis.

Reserve container pickups at the pools and depots that take appointments, with the same shape as chassis reservation: book now or at a Central-Time moment, retry until booked, keep the receipt as evidence, cancel from the API or the dashboard.

  • Instant or timed bookings with retry-until-booked
  • Booking receipts and availability captures kept per reservation
  • Cancellation with a reason from any surface

Pools and depots that take pickup appointments

planned

Chassis Breakdown Processing

A broken chassis reported to the pool without a dispatcher on hold.

When a driver reports a flat, a light out or a brake problem, Neo files the breakdown with the pool that owns the chassis, keeps the ticket and its replies on the chassis's timeline, and tells the dispatcher what the pool decided — repair on site, swap, or tow — so nobody sits on the phone.

  • File the breakdown with TRAC or DCLI from the chassis number and the driver's report
  • Pool replies read back and attached to the chassis's timeline
  • The driver's wait measured from Motive, not claimed

TRAC · DCLI

Get started

Give your dispatchers their day back.

A thirty-minute walkthrough on your own Chicago lanes and carriers. We will show a live trace on one of your ramps, a scheduled watchlist and the dashboard your team would open every morning.