ID (SUBJECT identifier)

Position

GRAMMAR

SUBJECT name

Position

GRAMMAR

Also known as

Place, site, point, region, zone, premises, address, spot, location.

TIC Description

Definition

Position refers to a precisely defined and uniquely identifiable place within the subject's operational domain, well defined by its physical dimension, shape and location (mandatory), that can be used, occupied or referenced by an object. This definition includes fixed and moving or permanent and temporary positions.

TIC Description

Further Detail

In common language, a position is the place within which an object (usually another SUBJECT) can be placed. There are many ways to define positions (or places), and all the positions resulting could be used simultaneously, resulting in an overlap. ie (country, region, terminal, yard, road, ground slot).

The purpose (reason for being) of a “Position” subject is to organise the processes and the space. Positions are usually defined by a geometrical dimension to utilise the space for a primary purpose (to perform a task or to store an object).

Position vs Location (place vs address)

A Position is a subject itself (place) with a unique id, with its entity, concepts (mandatory to include location), observed properties, point of measurement or attributes and values. A Position always resides in a Location (address), i.e.:

• A Location is just the address where a subject is, e.g., Terminal 1

• A Position can have many Location values, it will depend on the logical or coordinate qualifier, but only one id.

Example

Position id=23XYZ is at Location terminal 1, yard North, block A, bay 33, and Location Spain, Valencia, reception CSP.

A Position can have a history relative to concepts (available, occupied, reachable, cycle, etc) with its observed properties: events, status, timers, durations, etc. A Location cannot have a history, it just defines “where”.

For example, how is Position used in a container terminal?

Position can be related to a cargo, or a cargo can be located inside one position. Position - like a container ground slot - can be linked to one or more pieces of objects (cargo), either because it physically holds them or because it's part of their movement (e.g. during a carrier visit).
Likewise, cargo can be linked to one or more positions—for example, a 40-foot container might span two 20-foot slots, or be assigned to positions marking its origin and destination within a planned move.
This creates a two-way, many-to-many relationship between positions and cargo, reflecting both how things are stored and how they move through the yard.

Position can be attached to an equipment or facility (general usage to express where those objects are located). A cargo “X” can be located in position “platform3” or the position “platform3” contains the cargo “X”

Two (or more!) Positions can be attached to a move/job instruction.

A list of Positions can be assigned to a terminal residing object (yard, quayside, gate, carrier, CHE etc.). This allows the terminal to organise the processes.

Operational Boundaries

The Position boundaries could be defined by the spaces where containers or equipment might reside or be processed:

• Terminal Yard

• Quay areas

• Gate complexes

• Rail sidings

• Carrier storage areas (vessels, external trucks, barges, trains, …)

• On-terminal equipment locations (e.g., being carried on or moved by a straddle carrier or AGV)

A typical example is the position “Berth-North” (designed to perform loading and discharging vessel operations) or the “Yard1” (designed to store cargo). They are usually defined by geometrical shapes but could also be defined by the type of pavement or any other particular characteristic, like the type of CHE.

Position Concepts

A concept is what is, does, consumes or contains a subject. A Concept can only be, do or consume one thing for a specific timestamp (cannot be true and false at the same time or cannot be a berth and a yard at the same time). A concept “type” is used for classification and can only be one class (one value) at a time.

• FunctionalType (design to contain):
  Explains the type of object the position (area) was design to contain inside (Yard for containers, Berth for loading/discharging vessel operations cargo, Vessel for carry cargo, Gate for inbound or outbound trucks, Machine for moving cargo, Train for carrying by rail cargo, Truck for carrying cargo on road, … )

• MobilityType: stationary, mobile, areal, underground…

• TemporalType: permanent, temporal, eventual…

• Location:
  Which is referring to where the position is located, composed of Logical (logical) and Coordinate (physical address).
  Position includes a list of Locations (Logical and Coordinate). A list is used because it is possible that multiple addressing systems are used at the same time for a position.

• Available / Not Available / reserved: Expresses the availability of the position to be occupied.

• reachable / notreachable: Express the ability of a CHE to collect/drop an object (usually cargo) in a position.

Position allows the nesting of subsubjects, the most common ones are the relative Positions around it: positionabove / positionbelow / position+1, +2, `+x, position -1, -2, -y,

As one position has many-to-many relations, it is recommended to make the relation through location. The most typical nest subject (object) in a position is the object that contains. ie the cargo or cargo visit that is dwelling in the position.

As TIC 4.0 is an ontology, some rules related to the definitions and the relations between them may be applied to guarantee that the information makes sense:

• FunctionalType Yard, Quay, Gate are MobilityType stationary

• FunctionalType Vessel, Train, CHE, Trucks are MobilityType mobile

• The position ID is unique, but in the case of a carrier or che could be defined with a combination of the subject ID and location technical or logical of the subject

TIC Description

Example

"position": [
{
"id": "Y 01A 035 B 3",
"functionalitytype": "(berth / yard / gate / railloadingspot / truckloadingspot / workshop / chassis / energystation / reefer / vessel / stowagecell / barge / train / truck)",
"berth": false,
"yard": false,
"gate": false,
"railloadingspot": false,
"truckloadingspot": false,
"workshop": false,
"chassis": false,
"energystation": false,
"reefer": false,
"vessel": false,
"stowagecell": false,
"barge": false,
"train": false,
"truck": false,
"mobilitytype": "(stationary / mobile / warehouse)",
"stationary": false,
"mobile": false,
"warehouse": false,
"TemporalType": "(permanent / temporal / eventual)",
"permanent": false,
"temporal": false,
"eventual": false,
"hazardposition": false,
"location": {
"available": {
},
"reserved": {
},
"notavailable": {
},
"reachable": {
},
"notreachable": {
}
},
"size": {
"size20foot": {
},
"size40foot": {
},
"size45foot": {
"positionabove": [],
"position+1": [],
"position+2": [],
"position+3": [],
"position+4": [],
"position+5": [],
"position+6": [],
"positionbelow": [],
"position-1": [],
"position-2": [],
"position-3": [],
"position-4": [],
"position-5": [],
"position-6": []
}
},
"cargo": [
{
"cargovisit": [],
"jobinstruction": [],
"positionlist": []
}
],
"positionlist": [
]
}
]

Location

CargoUnit, Position

Where something is (logical/coordinate)

• Where is the Occupant located within the Positoin?

• Where is the Position located within its parent subject/terminal?

Position

as Subject

A container/slot in a structure as an abstract thing that contains something

Occupant

Position

What is currently assigned to or stored in it

id

Unique ID (e.g. POS_Y01_035_2)

name

Human-readable name

residing_object

Reference to Yard, CHE, Vessel, etc.

type

Fixed, Moving, Temporary

address

Composite of logical and physical address

state

e.g., Available, Occupied, Blocked

associated_type

What it is intended to hold (e.g. CargoUnit, Truck, Vessel)

occupancy

identifier (container ID)

output.actual

state

status

output.actual

capacity

volume, dimensions

output or design

addressing

logical, technical, coordinate

output.actual

Majid Samar

draft

no