A restriction is a limitation upon a marine entity that, in some way, restricts their activity or enables an entity to bi-pass any constraints (meaning that an entity can perform an activity for a certain period without running any further assessments or tests). Some examples of restrictions are:
- If a flag is black listed, this places a restriction upon all vessels that operate under that flag.
- If a chartering organisation elects never to use a technical manager, this places a restriction upon all vessels that are operated by that technical manager.
- If a chartering organisation decides a technical manager is highly trustworthy and any of their vessels are always acceptable for usage without any tests (they are trusted to ensure vessel quality) then a restriction is placed upon all vessels operated by the technical manager stating that they can always be used.
Fields within this standard can be compulsory (must be completed to meet the standard) or optional. Fields are optional if they ‘can be null’. Data can be recorded against a restriction for fields not defined in this standard- the standard only defines common fields.
A9.1 Restriction type
LOOKUP B10: Restriction Types
This is the value in the dictionary that best describes the type of restriction that will be applied to the associated entities. This indicates whether the restriction allows or disallows activity.
A9.2 Does the restriction apply to all vessels?
BOOLEAN NA
A bit indicating whether the restriction applies to a global set of vessels. For example, if a company elected to never use a certain port, then this would apply to the global vessel set. However; if the restriction is a black listed flag, this does not restrict the global vessel set- just the vessels under that flag.
A9.3 Does the restriction apply to all locations?
BOOLEAN NA
A bit indicating whether the restriction applies to a global set of locations. For example; if a company elected to never use a certain group of vessels, this would apply to all locations. However; if they elected to not use a certain port, this would not apply to all locations.
A9.4 Restricted vessels
LIST (LOOKUP / STRING) A1: Vessel
A list of identifiers for the vessels on which the restriction applies. If a dataset using data standard “A1 Vessel” exists, these values should refer to elements within that dataset (Internal ID).
1: If ‘A9.2 Does the restriction apply to all vessels?’ = 0: this list must be populated and cannot be null. 2: If ‘A9.2 Does the restriction apply to all vessels?’ = 1: this list must be null.
A9.5 Restricted locations
TABLE Rows
A table of identifiers for the locations to which the restriction applies.
1: If ‘A9.3 Does the restriction apply to all locations?’ = 0: this table must be populated and cannot be null. 2: If ‘A9.3 Does the restriction apply to all locations?’ = 1: this table must be null.
-
A9.5.1 Location type
STRING
Can be nullThis should be a description or identifier of the type of location stated in “A9.5.2 Location name”.
-
A9.5.2 Location name
LOOKUP / STRING
Can be nullThis should be an identifier for the restricted location. If datasets using data standards “A3 Port”, “A4 Terminal” and “A5 Port” exist, restrictions upon locations within those datasets should referrer to the corresponding elements (Internal ID).
A9.6 Restriction effective date
DATETIME NA
The date on which the restriction becomes (or became) active- after which the restriction should be enforced.
A9.7 Restriction expiry date
DATETIME NA
The date on which the expiry ends and is no longer active- after which the restriction will no longer be enforced.
1: This value must be greater than or equal to the value of “A9.6 Restriction effective date” (or either value can be null).
A9.8 Is the restriction currently active?
BOOLEAN NA
A bit indicating whether the restriction is currently active and should be enforced.
A9.9 Restricting body
STRING NA
The name or identifier of the body or organisation that has applied the restriction if applicable.
A9.10 Reason for Restriction
STRING NA
A description of the reason for which the restriction has been applied.
A9.11 Additional Particulars Attributes
TABLE Rows
A table recording data about the restriction 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.
-
A9.11.1 Key
STRING
Can be nullA description or name for the attribute that this piece of data describes.
-
A9.11.2 Value
STRING
Can be nullThe 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.
A9.12 Internal ID
STRING NA
An ID for internal purposes used to identify this entity and link it to other entities.