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 an inspection for fields not defined in this standard- the standard only defines common fields.
This standard encapsulates all different inspection types, unifying them under one standard. This results in several fields that are only populated on the condition that the inspection is of a certain type (as stated in the condition notes for that field).
A10.1 Entity under inspection
LOOKUP / STRING A1: Vessel, A2: Organisation
This is a unique identifier for the vessel, organisation or alternate entity type (using Internal ID) that was the primary subject of the investigation. In general, this will be the vessel, however; in some circumstances (such as a Technical Manager Self-Assessment) the entity may be an organisation or Terminal (in Terminal feedback).
A10.2 Primary inspection type
STRING NA
The name (or a description) of the type of inspection that was conducted- for example SIRE.
A10.3 Secondary inspection type
STRING NA
A name (or description) that identifies the sub-type of the inspection that was conducted. For example, ‘VIQ6’ is a sub-type of SIRE inspections.
A10.4 Inspection date
DATETIME NA
The date on which the inspection was conducted.
A10.5 Current status of inspection report
LOOKUP / STRING B11: Inspection Report Statuses
The value in the dictionary that best describes the current status of the inspection and its corresponding report. If no dictionary value applies, then a string can be entered.
A10.6 Vessel operation at the time of inspection
LOOKUP / STRING B12: Vessel Operations
The value in the dictionary that best describes the operation the vessel was conducting during the inspection. If no dictionary value applies, then a string can be entered.
1: Can only be populated if the inspection is of a vessel.
A10.7 Inspection location
TABLE Rows
This is a table identifying the location in which the inspection was conducted. A set of fields that can be included in this table are stated below.
1: If the inspection was conducted whilst in dock, the port and terminal should be recorded. 2: If the inspection was conducted offshore, the country in whose waters the inspection was conducted should be recorded, along with as many other details as possible. Note that ‘international waters’ is valid.
-
A10.7.1 Location type
LOOKUP / STRING B13: Location Types
Can be nullThe value in the dictionary that best describes the type of location in which the inspection was conducted. If no dictionary value applies, then a string can be entered.
-
A10.7.2 Name
STRING
Can be nullThe name (or identifier) of the location in which the inspection was conducted.
-
A10.7.3 Port
LOOKUP / STRING A3: Port
Can be nullAn identifier of the port in which the inspection took place (if the inspection was conducted within a port)- Internal ID from OMarine A3.
-
A10.7.4 Terminal
LOOKUP / STRING A4: Terminal
Can be nullAn identifier of the terminal in which the inspection took place (if the inspection was conducted within a terminal)- Internal ID from OMarine A4.
-
A10.7.5 Berth
LOOKUP / STRING A5: Berth
Can be nullAn identifier of the berth in which the inspection took place (if the inspection was conducted within a berth)- Internal ID from OMarine A5.
-
A10.7.6 Country
LIST (LOOKUP) Country ISO Codes
Can be nullThe country within whose waters the inspection was conducted. If the inspection was conducted in international waters, this value should be “International waters”.
-
A10.7.7 Latitude
FLOAT
Can be nullThe latitude value referencing the location at which the inspection was conducted.
-
A10.7.8 Longitude
FLOAT
Can be nullThe longitude value referencing the location at which the inspection was conducted.
A10.8 Inspection report last modified date
DATETIME NA
The date on which the report accompanying the inspection was last modified.
A10.9 Inspector conducting inspection
STRING NA
The name of the inspector (and the organisation they work for) that conducted the inspection.
A10.10 Inspection requesting organisation
LOOKUP / STRING A2: Organisation
The name (or Internal ID) of the organisation that submitted or requested the inspection.
A10.11 Inspection negative response count
INT NA
The number of responses to questions in the inspection that were ‘No’ or negative.
A10.12 Inspection positive response count
INT NA
The number of responses to questions in the inspection that were ‘Yes’ or positive.
A10.13 Count of un-answered inspection questions
INT NA
The number of questions within an inspection that were not answered or not applicable.
A10.14 Was the vessel detained?
BOOLEAN NA
This is a logical value indicating whether the vessel under inspection was detained as a result of the inspection.
1: The inspection must be conducted on a vessel, not an organisation.
A10.15 Detention start date
DATETIME NA
The date on which a detention commenced on a vessel as a result of the inspection.
1: Can only be populated (and must be populated) if ‘A10.14 Was the vessel detained?’ = TRUE
A10.16 Detention end date
DATETIME NA
The date on which a detention ended on a vessel as a result of the inspection.
1: Can only be populated (and must be populated) if ‘A10.14 Was the vessel detained?’ = TRUE
A10.17 Inspection dialogs
TABLE Rows
This is a table of comments recorded against the inspection by an interested party and the corresponding replies (if any were given). Fields to include in the table are listed below.
-
A10.17.1 Commenting party
STRING
Can be nullA description, identifier for or name of the party that made the comment.
-
A10.17.2 Comment
STRING
Can be nullThe comment made.
-
A10.17.3 Comment
DATETIME
Can be nullThe date and time that the comment was made.
A10.18 Inspection result
STRING NA
This is a field in which a final result or score for an inspection can be recorded. For example, if an inspection resulted in a pass or fail result.
A10.19 Inspection questions and responses
TABLE Rows
This is a table listing all questions asked during the inspection and the corresponding responses. There can be an infinite number of fields in this table, as an inspector can record an infinite number of responses to a question. Stated below are the primary fields that should be recorded in this table. The list below states the data types for the primary fields- the response fields (“A10.19.3 Primary response” and “A10.19.4 Secondary response”) can be of any data type, those stated are merely recommendations.
-
A10.19.1 Question number
STRING
Can be nullThe number assigned to the question- this is the number as it would appear in an inspection questionnaire or report.
-
A10.19.2 Question text
STRING
Can be nullThe question text. This is the text as it would appear in an inspection questionnaire.
-
A10.19.3 Primary response
BOOLEAN / STRING
Can be nullThe primary response to the question. If there is a binary response to a question (even if there are further responses to the same question), the binary response should be recorded in this field.
-
A10.19.4 Secondary response
STRING
Can be nullA secondary response to the question- this may be an explanation for the primary response stated in “A10.19.3 Primary response”.
A10.20 Additional Particulars Attributes
TABLE Rows
A table recording data about the inspection 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.
-
A10.20.1 Key
STRING
Can be nullA description or name for the attribute that this piece of data describes.
-
A10.20.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.
A10.21 Internal ID
STRING NA
An ID for internal purposes used to identify this entity and link it to other entities.