TIC 4.0
Carrier Productivity Carrier Ready to Work
KPI
Fields | Type | Description | Purpose |
---|---|---|---|
ID (KPI identifier) | M | To be published in “2024.012” | GRAMMAR |
KPI name | M | Carrier Productivity Carrier Ready to Work | GRAMMAR |
KPI type | M | Operational Performance | GRAMMAR |
Applicable to |
| Carriervisit (type vessel), trucks, train, barge, Berth, Terminal, Gate operations, rail operations |
|
Also known as | O | Port visit Productivity, Port stay productivity; | TIC Description |
Definition | M | The average number of units performed for a carrier visit from the time the carrier is ready to work until the terminal operations end. | TIC Description |
Further Detail | O | This KPI measures the performance of the terminal from the carrier’s perspective. It considers the cargo move during the time the carrier is ready to work, but only until the terminal operations “end” and the moment that the carrier can initiate the departure process (vessel departure or truck gate out process or rail gate out). If a 3rd party operation happens at the same but they are not compatible, the carrier will not be ready to work for cargo operations. By default, it considers the average number of cargo (boxes) performed by the terminal for a carrier visit during “carrier ready to work for the terminal” (between the first time carrier ready to work and first time terminal berth is ready for departure) discounting the time that the carrier is not ready to work and the “force majeure” of the carrier visit cargo operations, all in hours. The root of this KPI is Productivity but applied to a carrier visit from the first time the vessel is waiting for terminal operations to terminal job is done, discounting the time the vessel is not ready to work or any terminal forcemajeure.
Carrier Productivity Carrier Ready to Work (boxes per hour) Datapoints: tos|@|jobinstruction|@|order|deliver|counter|output|actual|box tos|@|carriervisit|@|carrierreadytowork|timer|output|actual|#unit#hour|value tos|@|carriervisit|@|terminaloperations|@|cargooperations|forcemajeure|timer|output|actual|#unit#hour|value Operator: SUM(tos|@|jobinstruction|@|order|deliver|counter|output|actual|box) / ( SUM(tos|@|carriervisit|@|carrierreadytowork|timer|output|actual|#unit#hour|value)-SUM(tos|@|carriervisit|@|terminaloperations|@|cargooperations|forcemajeure|timer|output|actual|#unit#hour|value)) Unit: box/hour KPI Elements: Timeframe: tos|@|carriervisit|id Split: Bucket: Carrier Visit Diagram This KPI represents the performance of moving cargo by the terminal for a whole carrier (aggregates all CHEs working in the same carrier) from the carrier’s point of view as long as the carrier is in the terminal ready to work. It is a good KPI to represent the cargo performance considering the entire port stay. KPI modifications: If the user of this KPI needs to introduce some changes they must indicate such in the KPI: i.e. “Carrier Productivity Carrier Ready to Work including 3rd parties” will be the same definition but considering also the time the carrier has to spend at the terminal to carry out the 3rd party services. The use of this KPI for a truck visit is recommended as it will represent the real performance perceived by the truck while it is waiting in the transfer zone. The arrival (gate) and departure (gate out) process is not included in this truck visit productivity
| TIC Description |
Required Information | M | Data Points | TIC Description |
SUBJECT |
| Carrier Visit (type vessel), Berth, terminal, |
|
CONCEPT |
|
|
|
Value |
| box/hour; boxes/minute ; TEU/hour |
|
Related standards | O |
| TIC Description |
Related TIC 4.0 definition | O | TIC Description | |
Example | M | Carrier Productivity Carrier Ready to Work (box per hour) 1st and 2nd January for vessels. Timeframe: 2023-01-01T00:00:00.000Z 2023-01-03T00:00:00.000Z
Datapoints: VESSEL A tos|@|carriervisit|@|firsttimecarrierreadyaccessible|time|timestamp = 2023-01-01T00:00:00.000Z tos|@|carriervisit|firsttimeterminalberthreadyfordeparture|time|timestamp = 2023-01-02T00:00:00.000Z tos|@|jobinstruction|@|order|deliver|counter|output|actual|box = 1000 tos|@|carriervisit|@|carrierreadytowork|timer|output|actual|#unit#hour|value = 24 tos|@|carriervisit|@|terminaloperations|@|cargooperations|forcemajeure|timer|output|actual|#unit#hour|value = 0
VESSEL B tos|@|carriervisit|@|firsttimecarrierreadyaccessible|time|timestamp = 2023-01-02T00:00:00.000Z tos|@|carriervisit|firsttimeterminalberthreadyfordeparture|time|timestamp = 2023-01-03T00:00:00.000Z tos|@|jobinstruction|@|order|deliver|counter|output|actual|box = 2000 tos|@|carriervisit|@|carrierreadytowork|timer|output|actual|#unit#hour|value = 24 tos|@|carriervisit|@|terminaloperations|@|cargooperations|forcemajeure|timer|output|actual|#unit#hour|value = 0 Operator: SUM(tos|@|jobinstruction|@|order|deliver|counter|output|actual|box) / ( SUM((tos|@|carriervisit|firsttimeterminalberthreadyfordeparture|time|timestamp)-(tos|@|carriervisit|@|firsttimecarrierreadyaccessible|time|timestamp))-SUM(tos|@|carriervisit|@|terminaloperations|@|cargooperations|forcemajeure|timer|output|actual|#unit#hour|value) - SUM(tos|@|carriervisit|@|carriernotreadytowork|timer|output|actual|#unit#hour|value)) = (1000+2000)/((24+24)-(0+0)) = 3000/48 = 62,5 bucked by carrier visit: Vessel A 1000/(24-(0)) = 41,66 Vessel B 2000/(24-(0)= 83,33 Filter: tos|@|carriervisit|type = vessel Split: by carriervisit|@|id Bucket: by carriervisit|@|id Carrier Productivity Terminal Operations (box per hour)
| TIC Description |
Example in the context of the grammar | M | Carrier Productivity Carrier Ready to Work From 2023-01-01T00:00:00.000Z to From 2023-01-01T00:00:00.000Z filter by carrier type vessel, split per carrier visit, and bucket per carrier visit name See the table below. | TIC Description |
Search tags | M | carrier productivity, vessel productivity | Technical |
Version / Date | M | 2024.011 | Technical |
Internal TIC Version | M | 20240521 | Technical |
carrier|@|name | Carrier Productivity Terminal Operations |
---|---|
A | 41,66 |
B | 83,33 |
Created by | Edited by | Review / Approve | Published |
@RBS EMEA | @Francisco Blanquer Jaraiz |
|
|
| Rik (EUROGATE) |
|
|
© Copyright - TIC 4.0 All rights reserved | Design web by Fundación Valenciaport