SUBJECT
Fields | Type | Description | Purpose |
|---|---|---|---|
ID (identifier) | M | jobinstructionlist | GRAMMAR |
Subject Name | M | Job Instruction List | GRAMMAR |
Subject Type | M | Process | GRAMMAR |
Also known as | O | workinstruction queue, queue, work list, job list | TIC Description |
Definition | M | A job instruction is something (collection of orders) that a source (system/someone) tells to subjects (system/someone/something/equipment) to do to an object in a coordinate way. | TIC Description |
Further Detail | O | Job Instruction includes any type of action and objects to perform in the terminal, not only “move cargo”. It applies to actions like inspections, reefer plugin, reallocation of equipment, recharge, repairs, maintenance, etc. Order vs Job Instruction vs Job Instruction List: “Order” (order) includes only one action (to do) over one object. “Job Instruction” (jobinstruction) is a collection of Orders over the same object. These orders could be executed by different subjects but always over the same object. Orders are included in the same job instruction because they must be performed in a coordinate way (i.e. move a container by several machines, repair a machine by several teams). In the simplest case, jobinstruction includes only one order. “Job Instruction List” (jobinstructionlist) is a collection of Job Instructions of the same type, that can be over different objects and executed by different subjects. If the actions of the different subject over the same object don’t need any kind of coordination, then they should not be part of the same job instruction but could be part of the same job instruction list. “Job Instruction Pair” (jobinstructionpair): if two job instructions need to be coordinated because are done simultaneously by the same subject over two different objects then a link must be indicated. The information on this job instruction is usually built overtime. Basic information is which Order has to be done, the starting point and the Order object. Other information like the end position of the Order, the nominated subject that has to perform the Order and other details, could be added in later stages and can be updated/modified over time. Job Instruction Start and End events:  jobinstruction.creation event happens in the moment that the id is assigned to the jobinstruction, so it has a way to identify itself. It could have only the basic info but needs it own identity. Usually will include the action to do and the object but not the subject, when and where. jobinstruction.active status is "True" only when is avaible for the source. The first time is available would generate a jobinstruction.firsttimeactive event. jobinstruction.assigned status is "True" only when is the subject in charge of doing the action is defined. The first time is defined would generate a jobinstruction.firsttimeassigned event. May happen that the subject change several times or even disspear then the jobinstruction.assigned.status would be false. jobinstruction.dispach: (event) first time the subject has the specific order to do to on an object jobinstruction.dispached: (status) when the subject has the specific order to do to on an object jobinstruction.acknowled: (event) first time the subject acknowledged to have received the order jobinstruition.acknowledged (status) when the subject acknowledged it got the order. In most of the cases dispatched and acknowledged happens at same time or very small time difference. jobinstruction.cancel: (event) when the subject refuse or the source cancel the order for at least one specific subject. jobinstruction.dispached: when the subject has the specific order to do to on an object (status) jobinstruction.start event happens when it is first time dispatched jobinstruction.execution status is “true” between jobinstruction.start and jobinstruction.end jobinstruction.order.start event happens when the first of: the subject already has the jobinstruction dispatched and start the work (che.cycle.start or equivalent) or when the jobinstruction is “dispach” = jobinstruction.start and the subject is waiting for instructions but ready to perform any job (che.idle or similar) jobinstruction.inprogress status is “True” between the first jobinstruction.order.start and the last jobinstruction.order.end jobinstruction.order.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.end event happens when the last jobinstruction.order.end Job Instruction types: Action type (jobinstruction.actiontype): is closed list (could be extended)
Order Type (jobinstruction.ordertype): Cargo Move:
Service task:
Job Instruction objects (jobinstruction.object): jobinstruction.object
Job Instruction subject (jobinstruction.order.subject): Is the one that executes the order. As a job instruction can have many subjects this concept metadata is under “order”. | 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/c/3pujAL8E https://tic40.atlassian.net/l/c/uF2W63Ut https://tic40.atlassian.net/l/c/0X0Ad1XR Laden; Unladen; Paid; Unpaid; Useful; UnUseful; https://tic40.atlassian.net/wiki/spaces/REV/pages/420643176/Single+Review?atlOrigin=eyJpIjoiZDAyMDQ3MmEyZTMwNGM2ODk2YTBjZjJkMmNmNzE4ZTUiLCJwIjoiYyJ9 https://tic40.atlassian.net/l/c/0yoXXmak https://tic40.atlassian.net/l/c/rSFwbtAG https://tic40.atlassian.net/l/c/UXknxhhc; Hatchcover; Lashing cage; Breakbulk; Bundle; Gearbox; Chain; OHF; double Spreader; Double trolley; solid bulk; double Boom; Multi trolley. | TIC Description |
Example | M | see below diagrams and draws | TIC Description |
Example in the context of the grammar | M |  tos.jobinstruction.cycle pending 2022.005 release. | DATA MODEL |
Link to one or more operational processes | M | All cargo operation is related to cycle. | TIC Description |
Search tags | M | Technical | |
Version / Date | M | 2022.005 / 01.09.2022 | Technical |
Internal TIC Version | M | 20220727 | Technical |
M = Mandatory
O = Optional
Diagrams
(optional) add some process diagram which concept belongs
Created by | Edited by | Review / Approve | Published |
Christopher Saavedra | Christopher Saavedra | Francisco Blanquer Jaraiz 20/10/2021 Luisa Kempf 23/12/2021 | 26/10/2021 |
Christopher Saavedra Kalmar TIC delegates 13/12/2021 |