D5 Annex report WP 3: ETIS Database methodology ... - ETIS plus
D5 Annex report WP 3: ETIS Database methodology ... - ETIS plus
D5 Annex report WP 3: ETIS Database methodology ... - ETIS plus
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>D5</strong> <strong>Annex</strong> <strong>WP</strong> 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL –<br />
FREIGHT TRANSPORT DEMAND<br />
1. modes at origin and destination<br />
2. modes before and after transhipment<br />
The records 2 and 3 result from the first decision rule and 1 and 4 from the second. Using the<br />
second decision rule has as advantage that it is made visible what type of transhipment has<br />
taken place. Again, due to the restriction of transhipment point loss of information occurs.<br />
What we learn from the problems described in this paragraph is that:<br />
· Including many variables results in a large database<br />
· restricting the number of transhipment points implies a reduction of information (smaller<br />
database)<br />
· restricting the number of transhipment points implies difficult interpretation of<br />
transhipment information<br />
· restricting the number of transhipment points implies that clear decision rules have to be<br />
chosen to avoid confusing results<br />
How to include empty loading unit flows in the database?<br />
To be able to analyse loading units movements it is also important to have information about the<br />
empty loading units transported. How should this type of information be included in the<br />
database? The question that arises is whether the empty loading units should be considered in<br />
the same way as the loaded loading units or as a commodity that is transported.<br />
Since in practice the transport of an empty loading unit is handled in the same way as the<br />
transport of a commodity it might be more convenient to do the same in the database; in practice<br />
one has to pay for this transport and a weight is registered for the loading unit. If the empty<br />
loading unit is treated as a commodity, a new code could be introduced for it. If this is done it<br />
can be treated in the same way as other commodities. A disadvantage of this method is that<br />
empty and loaded loading units must be traced in the database in different ways. It is also<br />
possible to introduce a variable indicating the number of containers transported. In this way the<br />
number of loaded and empty containers can be traced by combining it with the weight<br />
information (no weight means empty containers).<br />
In case it is considered in the same way as a loaded container, a special code can be defined for<br />
the loading unit variable for ‘empty container’. In case we use only one weight variable for the<br />
whole transport chain we register the weight of the transported commodities. As a result the<br />
weight of the transported ‘empty loading unit’ will be zero, which is a problem for both<br />
approaches. This means that if we want to know the amount of loading units transported we<br />
need to introduce another variable that registers for instance the weight of the loading units<br />
transported or the total weight of the commodities <strong>plus</strong> the weight of the container.<br />
160<br />
Document2<br />
27 May 2004