Reporting of damage

The first important principle of container damage management is to determine whether the containers were damaged before they arrived at the terminal or at the terminal itself. It is therefore important that the damage is reported as soon as it is detected by those working with cargo handling. Reporting should require only a few clicks in the mobile interface of the TOS, so that damaged containers are also reported when they are detected on cold winter days.

The personnel working at the terminal will be able to easily register a damaged container using predefined categories on a tablet in the truck or stacker. The TOS suggests the best location in the yard based on predefined data in this case “owner and size”.
When containers are marked as damaged by personnel, the TOS suggests the best location for them. The container itself is automatically tagged as damaged and removed from the normal workflow. For those not using task handlers, damage can also be reported directly to the container history or in the damage module using the unit ID.

The operational personnel can use their mobile phones to take pictures of the damaged container. This will be added to the respective container and serve as documentation.

Terminal, Grieg Connects TOS, can also be set up with invoicing functionality. so that the container marked as damaged automatically gets a new invoice line.

Follow-up on reported damage

After the operational personnel report the damage, the back office can take over the work in the terminal system. The operational personnel can also continue working on the damage report, but it may be suitable to do this in the office.

Reporting fields that work via mobile and desktop where the type of damage is selected and the damage can be described. Pictures can be added.

Damaged containers have different statuses in the terminal: registered, i.e., reported; ongoing, a damage being worked on; completed, a damage that has gone through the flow and is archived; or repaired, a damage that is repaired and invoicable. The list of damaged containers will show the date of changes and who has reported them. The terminal supports EDI messages to Maersk, and facilitates a detailed damage report with PDFs that can be sent to a defined recipient list of container owners. Such emails may, for example, serve as an estimate for repair.

Grieg Connect is continuing to add more functionality to the damage module this winter with new lists and filter views as part of the plan.

For more information on damage reporting in Terminal, Grieg Connects TOS, please contact our sales or support team.

Posted in News