The DITOPS Demo:
Load Move Requirements
Load Move Requirements
The move requirements are specified in a Cobol file in a format that we refer to as tpfdd records. These records specify all the information about the move requirements. One example of a tpfdd record is given below:
ABDR 7AUS477CO TRANS LIGHT MDM TRUCK CO 218220
WAMYAA7724TLM.CO
00177001770000304000007400091560003928000019100000600000000000000000000000606
HFTZ48C054BBNV48C057 LG 000
TVJDKSC072C076 00P 000 ESXMKSC080LD
00320940506940928 ABLBA
From these records we read the origin of the movement, the destination, the ALD, the LAD, the EAD, the type and quantity of cargo, and the mode. The ready date is the day the cargo is ready to be moved; we refer to it as the release-date. The due date is the latest date the movement should be completed. The preferred date is called earliest-arrival-date and we try to enforce it if possible. The mode can be sea or air. We consider 6 different types of cargo: bulk, oversize, outsize, pax, pol,and break-bulk. Each resource has different cargo capabilities, e.g. there are some resources that carry only pax (passengers), others carry only pol. Break-bulk and pol are used only for sea movements. The file we are loading, DEMO.SCENARIO, has only air movements. The move requirements we are using have been extracted from a large tpfdd file used in the Prairie Warrior exercise. The amount of cargo to be moved is: 308 passengers, 2748 stons of outsize cargo, 3909 stons of bulk cargo, and 2288 stons of oversize cargo. These move requirements use 12 different airports.
From the file menu, there are several different possibilities of loading a scenario. We can choose to load the entire scenario at once, or load the resources and the move requirements as separate steps. As OZONE is a generic scheduling tools, we refer to the move requirements by the generic term orders.
