A11: Incident

The date and time at which the incident started. If the time is unknown, a time of midnight should be recorded.

The date and time at which the incident ended. If the time is unknown, a time of midnight should be recorded.

1: This value must be greater than or equal to that recorded in ‘A11.1 Incident start date’.

The values in the dictionary that best describe the type of the incident that occurred. The ‘type’ can consider the cause, result and what occurred during the incident. An incident can be of multiple types. If no dictionary value applies, then a string can be entered.

A list of identifiers for vessels that were involved in the incident (Internal ID from OMarine A1).

The country in whose waters the incident took place. If the incident took place in international waters, record the country as “international waters”.

1: This value can only be an ISO code, null or “International waters”. 2: If ‘A11.8 Incident location’ refers to an element in datasets corresponding to data standards “A3 Port”, “A4 Terminal” or “A5 Berth”, then this value cannot be null.

This is the value in the dictionary that best describes the severity of the incident. This should consider the event and its consequences. If no dictionary value applies, then a string can be entered.

This is a table identifying what operations each vessel (involved in the incident) was conducting at the time the incident occurred. The fields included in this table are stated below.

1: Any vessel with an operation listed here must also be present in “A11.4 Vessels involved”.

• A11.7.1 Vessel identifier

  LOOKUP / STRING A1: Vessel

  Can be null

  An identifier for which vessel (involved in the incident) was conducting the operation (Internal ID from OMarine A1).

• A11.7.2 Vessel operation

  LOOKUP / STRING B12: Vessel Operations

  Can be null

  The value in the dictionary that best describes the operation the vessel was conducting (or attempting to conduct) at the time of the incident. If no dictionary value applies, then a string can be entered.

This is a table containing all known identifiers of the location in which the incident took place. Fields that can be included in this table are listed below.

• A11.8.1 Location name

  STRING

  Can be null

  The name of the location in which the incident took place.

• A11.8.2 Location description

  STRING

  Can be null

  A description of the location in which the incident took place.

• A11.8.3 Location type

  LOOKUP / STRING B13: Location Types

  Can be null

  The value in the dictionary that best describes the location in which the incident took place. If no dictionary value applies, then a string can be entered.

• A11.8.4 Port

  LOOKUP / STRING A3: Port

  Can be null

  If the incident took place in a port, this should be an identifier for that port (Internal ID from OMarine A3).

• A11.8.5 Terminal

  LOOKUP / STRING A4: Terminal

  Can be null

  If the incident took place in a terminal, this should be an identifier for that terminal (Internal ID from OMarine A4).

• A11.8.6 Berth

  LOOKUP / STRING A5: Berth

  Can be null

  If the incident took place in a berth (or its approached), this should be an identifier for that berth (Internal ID from OMarine A5).

• A11.8.7 Longitude

  FLOAT

  Can be null

  The longitude value for the location in which the incident took place.

• A11.8.8 Latitude

  FLOAT

  Can be null

  The latitude value for the location in which the incident took place.

This is a table stating the origins of all the vessels involved in the incident (if they are known). Fields to include in this table are listed below.

1: All vessels with an origin listed must also be present in ‘A11.4 Vessels involved’.

• A11.9.1 Vessel

  LOOKUP / STRING A1: Vessel

  Can be null

  An identifier of the vessel (involved in the incident) who was travelling from the corresponding port (Internal ID from OMarine A1).

• A11.9.2 Port of origin

  LOOKUP / STRING A3: Port

  Can be null

  An identifier of the port from which the vessel originated on its current voyage- the last port the vessel visited before the incident.

This is a table stating the destinations of all the vessels involved in the incident (if they are known). Fields to include in this table are listed below.

1: All vessels with a destination listed must also be present in ‘A11.4 Vessels involved’.

• A11.10.1 Vessel

  LOOKUP / STRING A1: Vessel

  Can be null

  An identifier for the vessel (involved in the incident) that was travelling to the corresponding port (Internal ID from OMarine A1).

• A11.10.2 Destination port

  LOOKUP / STRING A3: Port

  Can be null

  An identifier for the port which the vessel intended to visit next- note that the incident may have changed these intentions (this value should be represent the intentions prior to the incident).

A count of the number of vessels lost (unable to be used after) during the incident.

The number of humans killed as a direct result of the incident.

The number of humans injured as a direct result of the incident.

The number of humans missing as a direct result of the incident.

This is a table describing the cargoes carried by each vessel at the time of the incident. The fields included in this table are stated below.

1: All vessels with a cargo listed must also be present in ‘A11.4 Vessels involved’.

• A11.15.1 Vessel

  LOOKUP / STRING A1: Vessel

  Can be null

  An identifier for the vessel (involved in the incident) that was carrying the corresponding cargo (Internal ID from OMarine A1).

• A11.15.2 Cargo name

  STRING

  Can be null

  The name of the cargo that the vessel was carrying at the time of the incident.

• A11.15.3 Quantity

  FLOAT

  Can be null

  The quantity of the cargo that the vessel was carrying at the time of the incident.

• A11.15.4 Quantity units

  LOOKUP / STRING B16: Units Of Measurement

  Can be null

  The units in which “A11.15.3 Quantity” is measured. If no dictionary value applies, then a string can be entered.

A logical stating whether anything was spilt by a vessel during or as a result of the incident.

This is a table providing details of all polluting that occurred during or as a result of the incident. The fields included in this table are stated below.

1: If ‘A11.16 Did pollution occur?’ = FALSE then this value must be null. 2: All polluting vessels listed must also be present in ‘A11.4 Vessels involved’.

• A11.17.1 Vessel

  LOOKUP / STRING A1: Vessel

  Can be null

  An identifier for the vessel (involved in the incident) that spilt the corresponding pollutant (Internal ID from OMarine A1).

• A11.17.2 Pollutant type

  STRING

  Can be null

  The name of the entity spilt.

• A11.17.3 Quantity

  FLOAT

  Can be null

  The quantity of the pollutant spilt by the vessel as a result of the incident.

• A11.17.4 Units

  LOOKUP / STRING B16: Units Of Measurement

  Can be null

  The units in which “A11.17.3 Quantity” is measured. If no dictionary value applies, then a string can be entered.

A collection of identifiers for other incident records that occurred as a direct result of the incident. The list should contain identifiers of the incident records as stored in this dataset (Internal ID).

1: Items in this list must refer to other incident records in the dataset.

A description of the data source for the inicent data.

A list of consequences that occurred as a result of the incident.

A list of causes identified for the incident.

A table recording data about the incident that does not allign with other fields in the schema. This data can be very generic and is recorded in a table with two fields as defined below.

• A11.22.1 Key

  STRING

  Can be null

  A description or name for the attribute that this piece of data describes.

• A11.22.2 Value

  STRING

  Can be null

  The value of the particulars attribute. Note that while this is a string value, xml or other data forms can be stored as a string in this field.

An ID for internal purposes used to identify this entity and link it to other entities.