TIC 4.0
2023.007 Release
Introduction
This publication TIC4.0 2023.007 contains the following topics:
Job Instruction: some missing statuses have been added like assigned, dispatched and not dispatched.
“job-stepping” concepts: related to cargo move the most important process steps during the “collect” and “deliver” have been added.
Spreader: this is the second set of definitions the release is focused on the different modes, movements and functions that the spreader can do.
This publication in addition to continuing to populate in detail what a CHE can do with its spreader-related definitions, adds the definitions of the job-steeping concept to the digital world of terminals. 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
These definitions allow the user to compare easily what is doing the CHE versus what should be doing if following the job instruction. This is key information for the integration of reality and processes data with high value for the users that needs to improve their processes.
These definitions are part of TIC4.0’s ongoing work to develop a common vocabulary for the cargo handling industry and will be followed by future releases, as defined by the TIC4.0 Dataset Roadmap. The current list of definitions being worked on can be accessed on the digital platform of TIC4.0. This publication release provides the actual definitions and includes them in the TIC4.0 templates with the general approach on how to use these in Data Models, Data Schema's, JSON formats and provides high-level scenarios as examples.
1. TIC 4.0 scope
The purpose of TIC4.0 is to define a common language that can be represented in an understandable format, including data and information elements suitable for digitalization.
With the definitions and language, any reality (equipment or process) in a port terminal environment can be uniquely described. The vocabulary needs to be valid for any equipment, process and protocol (digital or human) in any port terminal in any location. The typical elements that make up the port terminal activities are cargo handling equipment (any kind of machine within the terminal that performs a job or task), external vehicles (trucks, vessels, trains), terminal infrastructure (berth, yard, gate), or auxiliary elements (energy, light, refuelling…).
For data-driven terminal operations, the subject of standardization concerns the data and information elements linking the digital solutions to the physical equipment and hardware.
To achieve the above goal TIC4.0 has developed a Semantic set of rules based on human language which helps in the creation process of the definitions/vocabulary. The definitions/vocabulary can be considered as the building blocks and together with the TIC4.0 semantic rules, allow the user to describe any reality in a specific, unambiguous way, irrespective of the level of technology used in a terminal.
The vocabulary is managed in a Dataset, which is basically a one-dimensional database list. This list is not static and will grow exponentially as TIC4.0 continues to work on more and more segments and areas of a terminal.
The work of TIC4.0 is to define the individual entries of the Dataset/Dictionary, focusing on a logical group or theme. In the Dataset/Dictionary the user can see the status of each entry and which entries are published and a link to the definition is provided.
To apply the vocabulary in each entry in several digital protocols, a Data Schema is needed. TIC4.0 will propose a Data Schema for each of the most common protocols, but the Data Schema is compatible with any protocol. In the examples that are provided, TIC4.0 usually uses JSON as it is very user-friendly and easy to read.
2. Data Model
For the digital formatting of the Semantic and Dataset, we need a Data Model to structure the data and a Data Schema to define the details of the content such as the validity of the format, the type of data (boolean, entire, real etc.), which data is mandatory or could be omitted etc.
The Dataset has been defined based on the RDF Resource Description Framework using the subject->predicate->object schema.
Following the semantic web standard (subject: object) the model has 3 main components: header, asset description and measurement.
SUBJECT creates the hierarchy tree structure (we have sub-subjects) that helps to identify the boundary of the value. The hierarchy is fixed by TIC4.0 for each kind of subject (CHE, TOS, Terminal) and can mix any type of subjects (e.g. machine.process = che.move). The subjects conform to an array defined by the (concept) metadata so various identical subjects but with different metadata (id or name or location or…) can be sent in the same message (one message with several CHE's or one CHE with several spreaders).
The CONCEPT's metadata defines “what is” and the CONCEPT “what does”. Both are flat (no hierarchy, no arrays) and as many as necessary can be used. Additionally, two concepts can be combined with “and” or “or” creating a new concept which includes the condition that makes both true. For e.g. “hoisting_and_trolleying” represents the action of hoisting and trolleying at the same time (both statuses must be true).
OBSERVED PROPERTies define the “magnitude” of the CONCEPT, are flat (no hierarchy) and can be used as many times as necessary with a CONCEPT.
For each OBSERVED PROPERTies an array created by the combination of the different POINT OF MEASUREMENTs in time (actual, estimated, etc), place (input, iinput, ioutput, output), timestamps and the different Units will give an array (a list) of VALUEs. The array could be as long as necessary in each message. The length will depend on the relation between the data frequency and the message frequency and also the amount of different POINT OF MEASUREMENTs that need to be represented.
A detailed definition of the Data Model can be found in https://tic40.atlassian.net/l/c/XBT1vEBA
The Data Schema was provided as part of the 2022.004 release and it defines the rules that the Data Model will follow and allows the translation from a hierarchy format to a flat format.
The Dataset is the content of the Data Model, a flat version without hierarchy or rules. The Dataset is used by humans but machines need the Data Model and the Data Schema to translate it to a digital format.
3. Generic Documentation
In this release we are publishing the following element:
Release | Title | Link | Definition | TIC4.0 classification |
---|---|---|---|---|
2023.007 | CHE Data Model 2023.007 | Change Log:
| Data Model
| |
2023.007 | TOS Data Model 2023.007 | Changes log:
| Data Model |
4. Definitions
In this release we defined the following elements:
Generic Definitions
Release | Definition | Link | Definition | TIC4.0 semantic |
---|---|---|---|---|
2023.007 | Tandem | Operational mode to perform two payloads (containers) in one cycle with two spreaders ,each spreader is connected to a single container. Both containers (typically being 40ft long) are positioned in such a way that the long sides of the containers are facing each other. | CONCEPT | |
2023.007 | Quad | Operational mode to perform four payloads (containers) in one cycle with two spreaders in Twin Mode, each spreader is connected to two containers. All four containers are 20ft long and positioned in such a way that the short sides of the containers are facing each other on each spreader. | CONCEPT | |
2023.007 | ExtendingWidth | Operation performed by the subject in order to increase its width to a larger one. | CONCEPT | |
2023.007 | RetractingWidth | Operation performed by the subject in order to decrease its width to a smaller one. | CONCEPT |
Job Instruction
Release | Definition | Link | Definition | TIC4.0 semantic |
---|---|---|---|---|
2023.007 | Assigned | Assigned Concept (status) is "True" only when the subject in charge of executing an order is defined. | CONCEPT | |
2023.007 | Not Dispatched | “Not Dispatched“ concept (status) is true when the order is not acknowledged by any subjects (not sent or cancelled). | CONCEPT | |
2023.007 | Dispatched | “Dispatched“ concept (status) is true when any order is acknowledged by any subject (sent and not cancelled). | CONCEPT | |
2023.007 | Moving To Collect | Concept (status) that describes the action to move (displace) and/or trolleying (positioning the spreader) as made by the subject (CHE) that is going to perform an order type cargo from wherever it is to the “laden or queuing” location (X,Y origin position of the cargo, not including Z). | CONCEPT | |
2023.007 | Queuing To Collect | 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 Collect and Ready to Collect activities. | CONCEPT | |
2023.007 | Ready to Collect | Concept (status) that describes the action to be performed by the subject (CHE) to execute an order (action type cargo), at the “laden” start location (origin position of the cargo) to pick up the cargo. It starts when the subject (CHE) arrives at the location of the cargo and ends when the cycle starts the laden phase (the cargo is picked). Usually, this action is related to the locking activities (hoist down and spreader locking). | CONCEPT | |
2023.007 | Moving To Deliver | Concept (status) that describes the action to move (displace) and/or trolleying (positioning the spreader) as made by the subject (CHE) laden (locked) while performing an order type cargo from the “laden” start location (X,Y origin position of the cargo, not including Z) to the Waiting To Deliver area or Ready To Deliver transfer zone. | CONCEPT | |
2023.007 | Queuing to Deliver | 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 | CONCEPT | |
2023.007 | Ready To Deliver | 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). | CONCEPT |
Spreader
Release | Definition | Link | Definition | TIC4.0 semantic |
---|---|---|---|---|
2023.007 | Twingap | Twingap is the center to center (longitudinal) measurement between two center housing twistlocks of the spreader. | CONCEPT | |
2023.007 | SideShifting | Operation performed by the subject in order to move the point of gravity to the left or to the right of the spreader. The movement is a linear movement of the main frame related to the attachment points of the subject. | CONCEPT | |
2023.007 | SideShiftingLeft | Operation performed by the subject in order to move the point of gravity to the left. The movement is a linear movement of the main frame related to the attachment points of the subject. | CONCEPT | |
2023.007 | SideShiftingRight | Operation performed by the subject in order to move the point of gravity to the right. The movement is a linear movement of the main frame related to the attachment points of the subject. | CONCEPT | |
2023.007 | SideShiftAtCenter | Status indicated by the subject that the main frame is in it's center position. The movement is a linear movement of the main frame related to the attachment points of the subject. | CONCEPT | |
2023.007 | LandingPin | A mechanical device with electrical indication on correct landing of the spreader on the container | SUBJECT | |
2023.007 | LockingDevice | If the subject is related to spreaders, the locking device is typically used for connecting the spreader to an ISO corner casting. Also known as Twistlock, Sideclamps, LockingPin, Shooting Pin, Pin, Fillout pin | SUBJECT |
© Copyright - TIC 4.0 All rights reserved | Design web by Fundación Valenciaport