Road freight across the US, from Cleveland. Internal dispatch system and website

Romexpress Inc

Client

Romexpress Inc

Industry

Trucking · road freight, United States

Period

2020 – 2021

Services

Internal dispatch system · Company website

Romexpress Inc

Romexpress, in brief. The website and dispatch system

Romexpress Inc, a road freight carrier in Cleveland, Ohio, asked us for a company website and an internal dispatch system in 2020–2021. The dispatch board shows the week on a large office screen. Each order is entered once, with all its stops. Orders can be filtered by driver, broker, date or load number. The system is built with Java and Spring Boot, Angular and Firebase.

Context

Romexpress Inc is a road freight carrier based in Cleveland, Ohio, delivering across the United States. For Romexpress we built two things: the company website and the internal dispatch system, which keeps people, trucks and orders in one place.

The challenge: the dispatch week

Dispatch plans the week: each order has its internal number, the broker’s load number, the driver who picks up, the driver who delivers, the pickup and delivery cities, and the day and time of every stop. An order with two pickups and two deliveries, on different days and with two drivers, is easy to lose in a spreadsheet.

The company asked for an application where you see the week at a glance, on a large screen in the office. Anyone who is not a dispatcher has read-only access.

What we built

The internal system keeps staff, trucks, routes and orders in one place. Before, each dispatcher kept their own files. The dispatch board grew out of it.

The company website, on WordPress, in English: the services, the company history on a timeline, and the careers and contact pages.

The dispatch board, the part of the system the whole office sees.

The dispatcher enters an order once, with all its stops, and the application places it on the right days of the week. Orders can be filtered by date or range, driver, internal number, pickup location, delivery location, broker and the broker’s load number. Dates and times use the American format dispatch works with. Outbound loads sit apart from return loads.

Drivers and brokers are lists kept in the application: a name is typed once and then picked from the list, so the same person no longer turns up spelled three ways. The administrator adds users, and the other accounts can only view the week.

The main screen is made to stay open on a large TV in the office: whoever walks in first thing sees the week ahead.

Technologies

Java and Spring Boot, Angular, Firebase; WordPress.

Questions. Short answers

The week ahead: each order placed on the days of its stops, filtered by date or range, driver, internal number, pickup location, delivery location, broker and the broker’s load number. Outbound loads sit apart from return loads.
Dispatchers enter and edit orders. The administrator adds users; every other account can only view the week.
WordPress, in English: the services, the company history on a timeline, and the careers and contact pages.
Java and Spring Boot, Angular, Firebase; WordPress for the website.

Your dispatch process. Compare the options

To see whether a system like this makes sense for your company, read trucking dispatch software: custom or TMS and field service software.

For the development service, see custom software.

Tell us how it should work. We build the rest

we reply on the channel you wrote on