D5 Annex report WP 3: ETIS Database methodology ... - ETIS plus

More documents

Recommendations

Info

D5 Annex WP 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL – FREIGHT TRANSPORT DEMAND 1. modes at origin and destination 2. modes before and after transhipment The records 2 and 3 result from the first decision rule and 1 and 4 from the second. Using the second decision rule has as advantage that it is made visible what type of transhipment has taken place. Again, due to the restriction of transhipment point loss of information occurs. What we learn from the problems described in this paragraph is that: · Including many variables results in a large database · restricting the number of transhipment points implies a reduction of information (smaller database) · restricting the number of transhipment points implies difficult interpretation of transhipment information · restricting the number of transhipment points implies that clear decision rules have to be chosen to avoid confusing results How to include empty loading unit flows in the database? To be able to analyse loading units movements it is also important to have information about the empty loading units transported. How should this type of information be included in the database? The question that arises is whether the empty loading units should be considered in the same way as the loaded loading units or as a commodity that is transported. Since in practice the transport of an empty loading unit is handled in the same way as the transport of a commodity it might be more convenient to do the same in the database; in practice one has to pay for this transport and a weight is registered for the loading unit. If the empty loading unit is treated as a commodity, a new code could be introduced for it. If this is done it can be treated in the same way as other commodities. A disadvantage of this method is that empty and loaded loading units must be traced in the database in different ways. It is also possible to introduce a variable indicating the number of containers transported. In this way the number of loaded and empty containers can be traced by combining it with the weight information (no weight means empty containers). In case it is considered in the same way as a loaded container, a special code can be defined for the loading unit variable for ‘empty container’. In case we use only one weight variable for the whole transport chain we register the weight of the transported commodities. As a result the weight of the transported ‘empty loading unit’ will be zero, which is a problem for both approaches. This means that if we want to know the amount of loading units transported we need to introduce another variable that registers for instance the weight of the loading units transported or the total weight of the commodities plus the weight of the container. 160 Document2 27 May 2004
D5 Annex WP 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL – FREIGHT TRANSPORT DEMAND Another option is to include another variable with the number of empty loading units. However since the characteristics of this variable is so different it might be an option to register the empty loading units separate from the rest of the transport chain database. The theoretical ideal record structure In this section the ideal record structure of the transport chain freight database is described. The elements described before are included here: · origin · active mode 1 · passive mode 1 · loading unit 1 · transhipment point1 · active mode 2 · passive mode 2 · loading unit 2 · transhipment point2 . . . . . . . . . . . . · active mode n · passive mode n · loading unit n · transhipment point n · destination · commodity · number of loading units · net weight · value It must be observed that this ideal record structure can handle all existing transport flows. So not only intermodal but also unimodal transport. Document2 27 May 2004 161
Page 1:
D5 Annex report WP 3: ETIS Databa
Page 4 and 5:
D5 Annex WP 3: DATABASE METHODOLOGY
Page 7:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67:
Page 71 and 72:
Page 73 and 74:
Page 75:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110: D5 Annex WP 3: DATABASE METHODOLOGY
Page 133: ANNEX C: EXPERIENCE FROM CONCERTED
Page 159: D5 Annex WP 3: DATABASE METHODOLOGY
show all

D5 Annex report WP 3: ETIS Database methodology ... - ETIS plus

Create successful ePaper yourself

Delete template?

Save as template?