Track and Trace
- 1 Summary
- 2 Functionality
- 2.1 Search by Vessel Visit
- 2.2 Filters
- 2.3 Group data
- 2.4 Detailed View
- 2.4.1 Events History
- 2.4.1.1 Current Status Rules:
- 2.4.2 Match Cargo to Messages
- 2.4.2.1 Automatic linking
- 2.4.2.2 Manual linking
- 2.4.1 Events History
- 2.5 Manage Holds & Stops
- 2.6 Roll/Remove Cargo
- 2.7 Print Docket
- 2.7.1 Docket Example:
- 2.8 Clear for Load
Summary
The Cargo Track & Trace page provides users with an overview of cargo against a completed vessel visit as well as manage Holds & Stops and also Roll/Remove cargo.
Functionality
Search by Vessel Visit
The user will need to select a Vessel Visit to return cargo items in the grid.
For containers created from documents, the container type may be pulled through from previous records we have of that container and its associated type.
Filters
Vessel Visit: text search and select from populated drop down. A vessel visit is mandatory to return results.
Exchange Type: default is to discharge (for import).
Clear filters: clears the ‘Cargo Type’ selected.
Cargo Type: filters by the type of cargo.
Container Status: only when selecting cargo Container, will the ability to filter by empty or full show.
Rolled/Removed: filter the shown cargo to include or exclude those that are Rolled or Removed.
LOP Holds: to filter the cargo with or without a LOP Hold.
Cust/MPI: filters cargo with either a 'Hold' or 'Cleared' status.
Search: free text search. Space will start a new line.
Holds & Stops: button enabled upon ‘ticking’ cargo. Allows holds & stops to be applied or removed.
Roll/Remove: button enabled upon ‘ticking’ cargo. Used to flag cargo as either ‘Rolled’ or ‘Removed’.
Print Docket: only available for exchange type: Discharge. The button is enabled upon ‘ticking’ cargo that has been cleared. Generates and sends a docket.
Pages to navigate through.
Group data
Cargo can grouped/sorted by using the stack icon: in the header columns.
The pink coloured stack icon indicates how the cargo items are grouped.
The default grouping is by Cargo #.
Cargo # will show the bill of lading, house waybill, booking number or waybill depending on what data we have. The Bill of Lading will take precedence in the case where we have multiple cargo numbers.
The data displayed is collapsable and expandable at both the individual item level and header level. This is done by clicking the + or - symbols.
Searching in the search box will expand all collapsed items.
Grouping by Consignee generates a dropdown box displaying the Consignees. Each is assigned to a unique page.
Detailed View
Further information for cargo items can be found in the detail view, by clicking the detail icon:
A pop-up window with details will show. The details can be edited by clicking the edit icon of the detail box you want to edit
After making the desired changes. Click either click the tick to complete the editing or cancel
to cancel the changes.
To save the changes to Track & Trace, after clicking the tick, click ‘Save Changes’ located at the bottom of the pop-up window. Clicking close, will not save any changes.
Any saved changes made in the detailed view will reflect on Track & Trace immediately and update in the grouping.
Data Origin box in the detailed view provides a link to preview the document from which the cargo was created. Other origins of cargo include Manual (manually created) and TSW (border instruction - specific to bulk cargo type).
Events History
Underneath the Holds & Stops box and Rolls/Removes, you can see an event history. This shows the associated border instructions, stops, holds and releases to the cargo.
Event name. The asterisk indicates the current status displayed.
Date of event (the linking of the border instruction with the cargo).
Source, from where the status has come.
Date of the receival of the message (when coming from TSW, otherwise no date).
Unlink message button.
Expand or collapse the history of events.
Cargo defaults to have a Customs, MPI and LOP hold on BBMS automatically for compliance. However, when border instructions are linked to a vessel visit prior to the cargo creation, when the cargo is created; the history will show the border instructions status and not the BBMS auto hold.
Current Status Rules:
The most recent TSW customs or MPI message determines the status.
If a manual status change occurs after the latest TSW receive date message, the manual status takes precedence as the current status.
The event that sets the current status is marked with an asterisk (*).
In the default view (when history is not expanded), only the event used to determine the current status is displayed.
When there is a border instruction with ‘Cancelled’ status, the events shown in history will revert back to the BBMS auto hold, removing the previously shown TSW message status. This will be until we receive a new update.
Match Cargo to Messages
Matching Messages to Cargo can be done automatically or manually.
Automatic linking
It is triggered when there is a new cargo item created, a saved edit to a cargo item, or every hour the system checks for auto-link.
Uses the following logic:
Linked to the vessel visit
Match by container number (for cargo type: Container, it looks at only container number to create a match)
Match by cargo identifier in hierarchical order (BOL, HWB, MB, BN) and quantity (for cargo type: BBK)
Manual linking
Manual linking of messages to cargo can be done by clicking the link icon found near the toggles: or in Holds & Stops window. A window will pop-up, search by Declaration Number. The customs search is filtered by messages from NZ Customs, the vessel visit and exchange type. The MPI search is filtered by messages received from MPI, the vessel visit and exchange type.
Check the boxes of the border instructions populated in the search and click ‘OK’ to link to the cargo.
Manually linked messages to cargo can be unlinked by clicking the unlink icon in the detailed view of the cargo under event history:
Manage Holds & Stops
To enable the button, check one or more checkboxes of cargo items, then click the ‘Holds & Stops’ button to trigger a pop-up window where Holds and Stops can be managed. Toggle the buttons to place a ‘Hold’ on cargo. By toggling the Hold, it will change it to Clear.
Manual linking of messages to cargo can be done by clicking the link icon found near the toggles:
View the border instruction message by clicking the view button:
Roll/Remove Cargo
To enable the button, check one or more checkboxes of cargo items, then click the ‘Roll/Remove’ button to trigger a pop-up window where the change can be managed.
Cargo can be Rolled, Removed or Reinstated. The Roll Date is automatically set. Users can provide a reason in the free text field.
Print Docket
Clicking the button will initiate a pop-up window where destination email address can be entered. To generate the docket and send via email as a PDF attachment, click ‘Email’.
A docket number will be generated and displayed on Track & Trace under column header ‘Docket’ for reference.
Multiple Dockets can be generated and sent in a single email. There will be one docket per cargo item.
Note, for most email accounts, there may be a limit of 10-25MB in the size of attachments.
Docket Example:
The clearance dates shown are structured as follows:
[Type]: [match date with cargo] [declaration number] [TSW message receival date]
“Cleared” date will show the removal date of the final hold.
'Goods Description/Commodity' and ‘Marks’ have a character limit of three lines and then will be truncated with an ellipsis.
‘Weights and Measure’ will show all of which we have as shown on Track & Trace.
Clear for Load
For outbound voyages, users have the ability to mark a vessel as Cleared for Load using button: found next to the filters. This is a user decision and not automated by the system.
A warning message will pop-up if there is cargo against the vessel that is not with status clear.
Once a Vessel has been cleared to load, the button be greyed out
To cancel the ‘Clear to Load’, click the cancel button:
Once a vessel has been cleared to load, a green tick will be visible on the vessel dashboard:
Audit button appears after a vessel has been cleared to load to verify the user who actioned
Related content
© PortConnect 2023