ID (identifier)

M

jobinstruction

GRAMMAR

Subject Name

M

JobInstruction

GRAMMAR

Subject Type

M

Process

GRAMMAR

Also known as

O

workinstruction

TIC Description

Definition

M

Something that a source (system/someone) tells to subjects (system/someone/something/equipment) to do to an object (system/someone/something/equipment) in a coordinated way.

It results in one or more Job Order Job Orders.

TIC Description

Further Detail

O

Job Instruction includes any type of objects and work to be performed in the terminal, not only “move cargo”. It applies to actions like inspections, reefer plugin, re-allocation of equipment, recharge, repairs, maintenance, etc.

Information on a Job Instruction typically develops over time. Basic information in which order it has to be done, the starting point and the Job Order object. Other information like the end position of the Job Order, the nominated subject that has to perform the Job Order and other details, could be added in later stages and can be updated/modified over time.

Job Order vs Job Instruction:

“Job Order” (order): it describes a piece of work (to do) to one object (i.e. plug in a reefer container, move a container from yard position A to yard position B)

“Job Instruction” (jobinstruction): it is realised by one or more Job Orders for the same object. These Job Orders could be executed by different subjects but always over the same object. Job orders are included in the same job instruction because they must be performed in a coordinated way (i.e. move a container by several machines from position A to final position C, repair a machine by several teams). In the simplest case, Job Instruction includes only one Job Order (i.e. move a container from yard position A to yard position B as for above example).

In the case that several Job Orders must be executed in a tight coordination (e.g., one subject works with another subject over the same object), then the job orders should be part of the same jobinstruction. For example, when a container is discharged from a vessel to the yard, there will be a Job Order for the STS to discharge from the vessel position to a position under the crane, and as a second step, an horizontal transport will execute the Job Order to move the container from the position under the crane to a yard or transfer position. More Job Orders to different or same subject could be still needed, until the container reaches the final planned position within the Job Instruction.

“Job Instruction Group” (jobinstructiongroup): if several Job Instructions need to be coordinated because they are to be done simultaneously by the same subject over more than one different objects then the link must be indicated. I.e an STS twin move of 2x20' containers (2 objects → 2 orders but one subject) or a quad 4x20' (4 objects → 4 orders but one subject).

Job Instruction Start and End events:

To consider that the Job Instruction is in execution, (the Job Instruction has started), the Job Orders need to be received and acknowledged by the subjects that are going to execute the Job Order. Considering this, the Job Instruction has several relevant “event” and “status” concepts.

Open

jobinstruction|creation event happens in the moment it is available for the source that has generated and it should have an ID assigned to it, so it has a way to identify itself. It could have only the basic info but needs it own identity. Usually it will include the action to be performed and the object but not the subject, when and where.

jobinstruction|active status is "True" only when it is available for the component which has to work on it (system/someone). The first time it is available would generate the starttimestamp event.

jobinstruction|assigned status is "True" only when the subject in charge of doing a Task related to one of the Job Orders is defined. The first time at least one Job Order subject is defined would generate starttimestamp event. It may happen that the subject changes several times or even disappears then the jobinstruction.assigned.status would be false.

jobinstruction|dispatched: (status) when at least one Job Order subject has the specific order to do to an object. The first time at least one order is sent (dispatched) to a subject, it would generate starttimestamp event.

jobinstruction|acknowledged (status) when the subject acknowledged receiving the order. Two subjects are required to acknowledge: a subject sending the message and a second one reading and acknowledging it. In most of the cases, dispatched and acknowledged happens at same time or within a very small time difference. It would generate starttimestamp (event) the first time the subject acknowledged it received the order.

jobinstruction|start event happens when its first Job Order is dispatched.

jobinstruction|execution status is “true” between jobinstruction.start and jobinstruction.end

jobinstruction|joborder|start event happens when the first of:

The subject already has the (first) Job Order of the Job Instruction is dispatched and started the work (che.cycle.start or equivalent) or when the jobinstruction is “dispatched” and the subject didn’t start the execution but it is ready to execute with only one single or grouped jobinstruction in the list. If more jobs are in the list we cannot determine the Job Instruction has started.

jobinstruction|@|joborder|1@|start

jobinstruction|inprogress status is “True” between the first jobinstruction.joborder.start and the last jobinstruction|@|joborder|1@|end

jobinstruction|joborder|end event happens when the subject already has the jobinstruction “dispatch” and ends the specific object and action work (che.cycle.end or equivalent).

jobinstruction|joborder|cancel: (event) is when the subject refuses or the source cancels the job order.

jobinstruction|end event happens when the last jobinstruction|joborder|end

Job Instruction types:

Action type (jobinstruction|type): is a closed list (could be extended)

• “Cargo Move” when the order is to transport a cargo

• “Service Task” when the order doesn’t involve cargo movement.

Job Order Type (jobinstruction|typeaction):

Some examples of Cargo Move:

• receival: export receival from truck

• delivery: import delivery to truck

• discharge: discharge a cargo from a vessel

• load: load cargo to a vessel

• rail discharge: discharge cargo from a train

• rail load: load cargo to a train

• yard move: move a cargo within the yard

• restow: discharge and reload the cargo to the same carrier

• shift on board: move a cargo within the carrier

• shuffle/rehandle: move a cargo in the yard to dig out the target container which is in below tier

• transfer: internal terminal transfer, different terminal within the same port without doing gate out.

• to be extended…

Service task:

• Plugging/Unplugging

• Inspection,

• Strip,

• Stuff,

• Charge,

• Clean,

• Repair,

• Seal,

• Fumigation,

• accessory move,

• paint,

• Lashing/Unlashing

• etc.

Job Instruction objects (jobinstruction|object):

jobinstruction|object

• Cargo Cargo 2023.009

• CHE CHE

• Accessories are payloads like hatch covers, gensets, frames. These are not considered as cargo

• Facility objects includes every area or physical equipment of the yard (light poles, bollards, fences, reefer stations, etc)

Job Instruction subject (jobinstruction|joborder|subject):

The subject is the one that executes the Job Order. As a job instruction can have many subjects this concept metadata is under “Job Order” includes only one action (to do) to one object (i.e. plug in a reefer container, move a container from yard position A to yard position B).

TIC Description

Required Information

M

SUBJECT, CONCEPT; OBSERVED PROPERTY and VALUE

TIC Description

SUBJECTS

tos;

CONCEPT

Id; loading; discharging; useful; unuseful; paid; unpaid; handling reason; start; end; active; inactive; idle; working.

Related standards

O

 TEU definition; Container definition; ISO 8601

TIC Description

Related TIC 4.0 definition

O

https://tic40.atlassian.net/l/cp/PJ1TDr1z https://tic40.atlassian.net/l/c/3pujAL8E Cargo 2023.009 CHE https://tic40.atlassian.net/wiki/x/AQC3kg https://tic40.atlassian.net/wiki/pages/createpage.action?spaceKey=REV&title=Whitepaper%3A%20Chain%20of%20command

TIC Description

Example

M

see below diagrams and drawings

TIC Description

Example in the context of the grammar

M