I started off as CSX. As of 2 days ago no new eta updates and it had been giving me etas to the next points. Now it’s saying something like no new eta information. So I thought I would just try UP to see if it had switched hands. Sure enough it was loaded and on its way at 5:20 this morning according to UP. CSX did not have that update in their phone tracking system. Maybe they take longer to update??
It's kinda cool how all this tracing works. I have a little insight into it from my day job.I'm on CSX as well. My first info/update was that it had arrive in Louisville, KY and that was on monday. On tuesday, it left Louisville for Atlanta, but I didn't have another update until this morning. That said, I think it's normal to have a lag between updates.
The likely reason behind the delay of CSX getting data is that it has switched to tracks owned by UP. When that happens, the tracing is collected by UP. All of this is done with what is called EDI 214. It is a type of logistics industry standardized data exchange and the actual tracing uses RFID.
So, when the train is now on UP tracks, the RFID information is collected by UP, then there has to be a data exchange to CSX... that is where the delay can come in. It depends how their feeds from UP to CSX are set up. It could be instant (unlikely, that's a lot of data exchange), or some increment of minutes or hours. Some of our feed only update daily (boats). Some weekly (long haul pallets).
Unfortunately, I cannot use my system to track any of this (even my own), or I'll get in BIG trouble if it's noticed.
Sponsored