6 ms·
At my previous employer we had two people working on data analytics for container barge traffic within the Rhine delta in the Netherlands and Germany. They were
by superice 6y ago
At my previous employer we had two people working on data analytics for container barge traffic within the Rhine delta in the Netherlands and Germany. They were able to overlay their predictions with the partial barge plannings that we actually had because we supplied software to inland container terminals.
Conclusion was that yes, you can predict locations of the terminals, but it's quite hard to find and produce repetitive schedules from the data because it requires the ships not change their schedule for too long, and the reality is just too dynamic to properly predict this.
For seagoing vessels I expect that they have more predictable schedules, but the hard part there is knowing container volumes, because there is no way to predict from public data what the volume of containers loaded/discharged is at a specific terminal. The closest metric is measuring the turnaround time of the ship, but that is not a great predictor for number of containers moved because handling times per container will differ per port, as will the number of cranes assigned to the ship, as will the ratio between 20ft and 40ft boxes, as well as the capability per port to do twinning (picking up 2x20ft boxes in one handling) and dual-cycling (discharging and loading a container as part of the same crane cycle).
Basically: it's a tough problem, with too many variables you cannot reasonably deduce.
(Also, even if you have the container volumes, I personally think the highest potential for optimization is in the hinterland, but that's a different story altogether)
- bkor 6y ago> because there is no way to predict from public data what the volume of containers loaded/discharged is at a specific terminal It's doable for a competitor. AIS has the vessels depth. If you assume the weight of a container to be similar you can monitor the vessels depth as they discharge and then load containers. You'll have to account for bunkering, empty containers, etc. Still, it's doable. There's also some data (not sure if public, should be easy for any shipping company) for anything going to the US. You can use that data to further improve the previous estimates. See https://www.joc.com/regulation-policy/trade-data/united-states-trade-data https://www.joc.com/regulation-policy/trade-data/united-stat.... Interestingly the JOC is terrible at predicting future trends despite having one of the most detailed data on their trade. Note: the method above will not give you exact numbers. It's not actually needed to know the exact numbers, seeing the trends and the fluctuations/changes is already quite useful.
- superice 6y agoI would be very impressed if that was more accurate than turnaround time, but interesting approach, hadn’t thought of that. But I’m guessing that adjusting for bunkering is tricky since they might fuel up more in ports where fuel is cheaper, so you cannot assume they will be nearly empty close to every port they call. Would love to know if guessing based on this is actually being used though.
- tda 6y agoVessel depth (draught) is usually (or always) a static number;hard coded in the ais transponder and never again uodated and thus provides zero information. The only somewhat reliable data are position and heading and their derivatives. Next to that you can get something out of the broadcast frequency, and that's about it. Of course the data can and is easily manipulated by some, and the broadcast is lossy so sometimes a few bits get lost or mangled in transit, there is no proper error correction in the protocol