TIC 4.0
Ready to Deliver
CONCEPT
Fields | Type | Description | Purpose |
---|---|---|---|
ID (Concept identifier) | M | readytodeliver | GRAMMAR |
Concept name | M | Ready To Deliver | GRAMMAR |
Concept type | M | action | GRAMMAR |
Also known as | O | At POW with cargo, at row with cargo, under RTG with cargo, waiting for equipment with cargo, At Yard to Deliver (AYTD), At Vessel to Deliver (AVTD) | TIC Description |
Definition | M | Concept (status) that describes the action that is going to be performed by the subject (CHE) to execute an order (action type cargo), at the “laden” end location (end position of the cargo) to drop the cargo. It starts when the subject (CHE) arrives at the end location of the cargo and ends when the cycle ends the laden phase (the cargo is delivered or dropped). Usually, this action is related to the unlocking activities (hoist down and spreader unlocking). | TIC Description |
Further Detail | O | The start of Ready To Deliver is the end of the Moving To Deliver or Queuing To Deliver activities and the end is just when the cargo is unlocked the first time. 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: FALSE tos.@.jobinstruction.@.oder.@2343.readytodeliver.status.output.actual.value: TRUE 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 recomended 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: FALSE tos.@.che.@TT01.readytodeliver.status.output.actual.value: TRUE | 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 | #laden at row, #wait, #waiting | 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 |
|
|
|
|
|
|
|
|
|
|
© Copyright - TIC 4.0 All rights reserved | Design web by Fundación Valenciaport