TEXOL A railcar and repair tracking system for the dispatch team
Texol is a group of companies that ships freight in its own railcars, and repairs and builds rolling stock. We rewrote their internal tracking system from scratch: railcars, repairs and movements now live in one place, and a report that used to take a whole day is ready in minutes.
In transit
42
Depot · repair
9
Storage
17
- Client
- Texol, group of companies — rail freight, railcar repair and manufacturing
- What we did
- Internal railcar and repair tracking system, built from scratch
- Built for
- The dispatch team
The system is internal and not publicly accessible, so the interfaces in this case study are visual reconstructions of the delivered features. Railcar numbers and figures are illustrative.
One railcar, three answers
Before the project, railcar data lived in three places: Excel spreadsheets, the dispatchers' paper logs and an old 1C system. To find out where a car was and what was happening to it, you had to check all three — and they didn't always agree.
Data in different places
Excel, paper logs and the old system each kept their own version of the fleet's state.
Manual re-entry
Dispatchers recorded the same event several times — in the log, in the spreadsheet and in the system.
A day per report
To build a fleet summary, data was exported, merged and reconciled by hand. It took a full working day.
An awkward old system
The old 1C setup wasn't built for dispatch work: everyday actions were buried behind a dozen screens.
Where is railcar 51742386 right now?
updated 3 days ago
Dispatcher's log
51742386 — in transit
51742386 — in storage
57301195 — …
handwritten entry
last sync: yesterday
Under repairIn storageIn transitThree sources, three different answers
We rewrote the system from scratch
We didn't patch the old system. We designed a new one around the dispatcher's daily work: whatever they do most often is the fastest thing to do in the system.
Every event — arrival, repair, storage, departure — is entered once and is instantly visible to everyone. We migrated the history from the spreadsheets and the old system, so the team didn't start from a blank page.
Railcar registry
A card for every railcar: type, condition, current location and full history.
Dispatcher's log
A digital replacement for the paper log: an event takes a couple of clicks and goes straight into the shared picture.
Repairs
Scheduled and running repairs: what's in progress, what's queued and when a car returns to service.
Car location
Where every railcar is right now: in transit, at the depot or on the storage tracks.
Reports
Fleet and repair summaries are built from live data — no exports, no manual reconciliation.
1C exchange
Accounting data flows to 1C automatically, without re-entry.
The whole fleet on one screen
The system's main screen is the dispatch board. Filter by status, search by number, and you see at once which cars are in transit, which are under repair and which are waiting in storage.
| Railcar | Status | Location |
|---|---|---|
| 57310428 | In transit | Train 214 · en route |
| 51742386 | Under repair | Depot · track 3 |
| 52086613 | In storage | Storage track 2 |
| 57301195 | Under repair | Depot · track 1 |
| 60417732 | In transit | Train 187 · en route |
| 52091047 | In transit | Train 203 · en route |
| 57318870 | In storage | Storage track 4 |
| 60422581 | Under repair | Depot · wheel shop |
Every step of a railcar in one history
The system follows each railcar through its whole cycle. Every transition is recorded, so a car's history builds itself — no digging through logs.
01
Transit
The car is on its way, and the dispatcher sees where it's heading.
02
Arrival
The car has arrived — the event goes into the log.
03
Repair
Scheduled or running repair at the depot.
04
Storage
The car waits on the storage tracks.
05
Placement
The car is placed for loading and heads out again.
and back into transit
Reports in minutes, not a day
Fleet summaries used to be assembled by hand: export the data, merge the spreadsheets, check against the logs. Now a report is one button away — built from the same data the dispatchers work with.
Before
- 1Export data from the old 1C
- 2Merge Excel spreadsheets
- 3Check against paper logs
- 4Fix mismatches and format
≈ a working day
Now
Fleet status
minutes
* Figures in the example are illustrative
What's inside
Interface
Backend
Integrations
Access
One system instead of three sources
Dispatchers work in a single system: railcars, repairs and movements are kept in one place rather than across spreadsheets, logs and the old 1C at once.
Data is entered once, so the answer to “where is the car?” no longer depends on which source you check.
A report that took all day is now ready in minutes.
Internal systems are rarely visible from the outside, but they decide how fast a company actually works. We dig into processes and turn them into tools people are glad to use every day.
Discuss your system