Timeplan Overview
For a given Lane configuration, a timeplan is compiled based on capabilities information and transport step specifications, as well as fixed values. There are two main aspects to the timeplan; the duration of each process step and whether these steps can be performed in a temperature-controlled environment.
For the specifications, see the table below:
The timeplan is summarized in a Temperature Exposure Overview, which shows how long a shipment is temperature-controlled, temperature protected and not temperature-controlled along with the total
transport. See example:
Duration
1. In case the questions related to the Tarmac & Loading / Tarmac & Offloading have been answered, Validaide takes the answers from the Capabilities. In case they have not been answered, Validaide sets a default value for that specific process step.
2. Offloading/loading is not addressed in the capabilities checklist, therefore it is fixed at 30 minutes, and similarly ULD buildup/breakdown durations are fixed at 45 minutes.
3. Both at the origin and at the destination a total duration is set by the user who creates the lane. The following questions refer to this:
How many hours before the Scheduled Time of Departure is the cargo expected to arrive at the airport?
How many hours after the Scheduled Time of Arrival is the cargo expected to be picked up at the airport?
From this value, the known process step durations are subtracted and the remaining time is distributed evenly between Storage and ULD Storage.
See below a concrete example of origin handling durations:
- Offloading is a fixed value, 30 min.
- ULD Buildup is a fixed value, 45 min.
- Tarmac & Loading in this case is not available from the Capabilities so the default value is used, 3 hrs.
- The total duration is set to 6 hrs by the user.
- Storage and ULD Storage: (360-30-45-180)/2=52.5. We use whole numbers, so 52 min and 53 min are assigned for the duration.
- Tarmac & Loading: No tarmac protection has been selected by the user, therefore the value is "Unknown".
- Cargo Loaded before Departure is always Not Controlled. it is the cargo that is already loaded on the plane but the plane is waiting for departure.
It is fix set to 60 minutes.
Temperature-controlled environment availability
When a temperature-controlled environment is available for a specific process step (e.g. 15-25°C warehouse), it is assumed that the shipment will be placed there accordingly.
1. Tarmac protection is always selected by the person who is configuring the lane. If it is not selected, the value is "Unknown". Otherwise, the user can select the following options:
- No Tarmac Protection -> value will be "Not Temp. controlled"
- Thermal Blanket -> value will be "Temp. protected"
- Temp. Controlled Dolly -> value will be "Temp. controlled"
- Temp. Controlled Pallet -> value will be "Temp. controlled"
- Temp. Controlled Truck -> value will be "Temp. controlled"
2. For the other process steps, the temperature-controlled environment availability is derived from the Capabilities. This, however, can be overruled by the user per process step.
See below a concrete example of origin handling temperature-controlled environment availability:
- Offloading: it is indicated that this step is not temperature controlled. It is derived from the capabilities.
- Storage: it is indicated that this step is temperature controlled. It is derived from the capabilities.
- ULD Buildup: it is indicated that this step is temperature protected. It is by default derived from the capabilities, but in this case, the value has been overruled by the user (which is indicated in the configuration).
- ULD Storage: it is indicated that this step is temperature controlled. It is derived from the capabilities.
- Tarmac & Loading: No tarmac protection has been selected by the user, therefore the value is "Unknown".
Comments
0 comments
Please sign in to leave a comment.