CONCEPT
Fields | Type | Description | Purpose |
---|---|---|---|
ID (Concept identifier) | M | queuingtodeliver | GRAMMAR |
Concept name | M | Queuing to Deliver | GRAMMAR |
Concept type | M | action | GRAMMAR |
Also known as | O | Waiting with cargo near the point of work, standing in line with cargo, waiting with cargo, waiting for equipment with cargo, waiting laden, At Yard to Deliver (AYTD), At Vessel to Deliver (AVTD) | TIC Description |
Definition | M | Concept (status) that describes the action to wait for the interlocks or sequence made by the subject (CHE) that is going to perform an order type cargo between the Moving to Deliver and Ready to Deliver activities and it is already in proximity of the “laden end location”, but didn’t reach it yet | TIC Description |
Further Detail | O | Queuing To Deliver is true between the moment the subject reaches the queuing (geofence) area and the moment the subject reaches the “laden end location” (the final position of the cargo for the cycle process included in the order, usually called drop location). This queuing area is usually next to the laden end location and must be defined by the terminal. The subject (CHE) will usually be idling (idle) within this area but in case it is not necessary to wait for any interlock then it could be just working and queuing will not last. The start of Queuing To Deliver is the end of the Moving to Deliver activities and the end is just when the CHE is Ready to Deliver for the first time. The Queuing To Deliver state is not mandatory and it may happen that it does not exist for a certain terminal, jumping from Moving To Deliver to Ready to Deliver. Specific cases, from the equipment point of view:
| TIC Description |
Required Information | M | SUBJECT; OBSERVED PROPERTY and VALUE | TIC Description |
SUBJECT | M | order; che, | GRAMMAR |
POINT OF MEASUREMENT | O | pom: output pomt: actual, estimated | GRAMMAR |
OBSERVED PROPERTY | M | status, duration, counter, totalcounter, timer, totaltimer, starttimestamp, endtimestamp | GRAMMAR |
Value | M | boolean | GRAMMAR |
Related standards | O | TIC Description | |
Related TIC 4.0 definition | O | https://tic40.atlassian.net/l/cp/4Q1bj1tt https://tic40.atlassian.net/l/cp/hLw2PTh0Moving To Collect Queuing To Collect Ready to Collect Collect Deliver Moving To Deliver Queuing to Deliver Ready to Deliver | TIC Description |
Example | M | A message from the TOS which confirms the job-step status of the terminal truck 01 from the perspective of the order, che and driver: tos.@.jobinstruction.@.order.@2343.movingtocollect.status.output.actual.value: FALSE. tos.@.jobinstruction.@.order.@2343.queuingtocollect.status.output.actual.value: FALSE tos.@.jobinstruction.@.order.@2343.readytocollect.status.output.actual.value: FALSE tos.@.jobinstruction.@.order.@2343.movingtodeliver.status.output.actual.value: FALSE tos.@.jobinstruction.@.order.@2343.queuingtodeliver.status.output.actual.value: TRUE tos.@.jobinstruction.@.order.@2343.readytodeliver.status.output.actual.value: FALSE tos.@.jobinstruction.@.order.@2343.che.output.actual.id: TT01
Optionally the information could be duplicated under the “che” subject. If there are a lot of elements in the che array and subsequently in the same message then it is mandatory to use the array identification after the “id” tos.@.che.@TT01.movingtocollect.status.output.actual.value: FALSE tos.@.che.@TT01.queuingtocollect.status.output.actual.value: FALSE tos.@.che.@TT01.readytocollect.status.output.actual.value: FALSE tos.@.che.@TT01.movingtodeliver.status.output.actual.value: FALSE tos.@.che.@TT01.queuingtodeliver.status.output.actual.value: TRUE tos.@.che.@TT01.readytodeliver.status.output.actual.value: FALSE | TIC Description |
Example in the context of the grammar | M | TIC Description | |
Link to one or more operational processes | M | All the jobinstructions “type” cargo move. https://tic40.atlassian.net/l/cp/4Q1bj1tt https://tic40.atlassian.net/l/cp/hLw2PTh0 | TIC Description |
Search tags | M | #waiting #geofence | Technical |
Version / Date | M | 2023.007 - 25/02/2023 | Technical |
Internal TIC Version | M | 20230227 | Technical |
M = Mandatory
O = Optional
Introduction to concept type “job-stepping”:
The concepts type job-stepping describes a status (what does or is the subject) related only to concepts (action) that “moves” cargo. The objective of this type of concept is to define what type of activity the CHE is doing to move the cargo. There are 6 basic sub processes to perform a move:
Moving to Collect
Queuing to Collect
Ready to Collect
Moving to Deliver
Queuing to Deliver
Ready to Deliver
All the steps are optional and would depend on the order. For one specific order, only one Job-stepping concept can be “true” at the same time.
TT order job stepping for Vessel load - 4 job steps example
TT order job stepping for Vessel discharge- 6 job steps example, geofence available
The https://tic40.atlassian.net/l/cp/S8dYAjXu (instruction to execute a sequence of steps) is the natural subject of the job-stepping, so we will include by default the concepts for each step under “order” but these concepts can be used with other subjects like CHE, user, cargo, etc.
Created by | Edited by | Review / Approve | Published |
Francisco Blanquer Jaraiz 2023-02-16 | Francisco Blanquer Jaraiz 2023-02-27 |
|
|
|
|
| |