What are Container Event Notifications?
PortConnect can send email notifications when a range of events/changes occur against containers. The full details of these event types is available here,Container Visit Event Types
Event Code | Event Description | Container Category: (Import, Export, Domestic, Storage) | Supported Port Codes | Supported Inland port Facility Codes | Event Value 1 | Event Value 2 | |
---|---|---|---|---|---|---|---|
1 | ACTIVE | Container record becomes live in PortConnect system | ALL | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
2 | AVAILABLE | Availability Advice (Container is discharged and fully released) | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
3 | AVAILABLECANCELLED | Availability Advice cancelled.
Automatically sent if subscribed to Available | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
4 | BOOKINGDISCREPANCY | Discrepancy: Booking does not match Preadvise/Gate-in details | Export / Domestic | NZAKL, NZTRG, NZTIU, |
| Container Visit value | Booking value |
5 | CEDORELEASE | CEDO Release | Export | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA | Export Release Number |
|
6 | CEDOREVOKED | CEDO Revoked | Export | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
7 | CLEARED | Cleared Advice (Container is fully cleared) | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
8 | CLEAREDCANCELLED | Cleared Advice cancelled. *Automatically sent if subscribed to Cleared | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
9 | CUSTOMSRELEASE | Notice of Customs Release | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZOLT, NZRUA |
|
|
10 | CUSTOMSRELEASECANCELLED | Notice of Customs Release cancelled.
*Automatically sent if subscribed to CustomsRelease | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
11 | DISCHARGE | Discharge Advice | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT |
| Vessel Name | Voyage Number |
12 | DISCHARGEDNOTCLEARED | Discharged but not cleared | Import | NZAKL, NZTRG, NZTIU, NZLYT |
|
|
|
13 | EXPORTCLEARED | CEDO is in place and there are no other stops | Export | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
14 | EXPORTCLEAREDCANCELLED | Export Cleared cancelled | Export | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA |
|
|
15 | GATEIN | Gate IN advice | ALL | NZAKL, NZTRG, NZTIU, NZLYT, DEPOT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA | Mode of transport, eg. Road/Rail For the Depot GATEIN events the event value is the specific Depot Code. | Identifier for the truck or train, eg. REL328 |
16 | GATEOUT | Gate OUT Advice | ALL | NZAKL, NZTRG, NZTIU, NZLYT, DEPOT | NZMKL, NZWII, NZOLT, NZCHC, NZRUA | Mode of transport, eg. Road/Rail For the Depot GATEOUT events the event value is the specific Depot Code. | Identifier for the truck or train, eg. REL328 |
17 | HAZARDGATERULE | Specifies how many hours before Vessel ETA that an Export Hazardous container can gate into the port (24hrs or 72 hours). | Export / Domestic | NZAKL, NZTRG |
| Hazard Class number |
|
18 | LFTCHANGED | Container visit Last Free Time has been changed | Import / Domestic | NZAKL, NZTRG, NZTIU | NZMKL, NZRUA | Current last free time | Previous last free time |
19 | LFTEXCEEDED | Container visit Last Free Time exceeded | Import / Domestic | NZAKL, NZTRG, NZTIU | NZMKL, NZRUA | Last free time |
|
20 | LFT24HOURS | Container visit Last Free Time within 24 hours | Import / Domestic | NZAKL, NZTRG, NZTIU | NZMKL, NZRUA | Last free time |
|
21 | LOAD | Notice of item loaded to Vessel | Export / Domestic | NZAKL, NZTRG, NZTIU, NZLYT |
| Vessel Name | Voyage Number |
22 | LOPRELEASE | Notice of Line Operator Release | Import / Domestic | NZAKL, NZMKL, NZTRG, NZTIU, NZLYT | NZMKL, NZOLT, NZCHC, |
|
|
23 | LOPRELEASECANCELLED | Notice of Line Operator Release - cancelled | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZOLT, NZCHC, |
|
|
24 | MPIRELEASE | Notice of MPI Release | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZOLT, NZCHC, |
|
|
25 | MPIRELEASECANCELLED | Notice of MPI Release - cancelled. Automatically sent if subscribed to MPIRelease | Import / Domestic | NZAKL, NZTRG, NZTIU, NZLYT | NZMKL, NZOLT, NZCHC, |
|
|
26 | NOCEDO | No Cedo Warning | Export / Domestic | NZAKL, NZTRG, NZTIU, NZLYT |
| 48, 24, 2 hour warning text |
|
27 | PINAVAILABLE | ExpressPin Available Can only be sent to the part that obtained the pin. | Import / Export / Domestic | NZAKL |
| Express Pin number |
|
28 | PINSUSPENDED | ExpressPin Suspended Can only be sent to the part that obtained the pin. | Import / Export / Domestic | NZAKL |
| Express Pin number |
|
29 | PRIORITYGATEIN | Automated Gate-In Notifications when containers arrive at Metroport with a status of Priority. | Import | NZTRG | NZMKL | Inland Port Gate In time |
|
30 | VBSCHANGED | Container visit VBS Slot Time has been changed | Import / Export / Domestic | NZTRG, NZAKL, NZLYT | NZMKL | Current VBS slot time | Previous VBS slot time |
31 | VESSELARRIVAL | Vessel Visit Actual Time of Arrival | Import / Export / Domestic | NZAKL, NZTRG, NZTIU, NZLYT |
|
|
|
32 | VESSELDEPARTURE | Vessel Visit Actual Time of Departure | Import / Export / Domestic | NZAKL, NZTRG, NZTIU, NZLYT |
|
|
|
Pricing for Container Event Notifications
There are two parts to this cost:
Users must be signed up to Subscribed Track & Trace. Pricing can be found here, https://www.portconnect.co.nz/#/content/pricing
Notifications cost $0.20 per Notification. Users can sign up for as many or as few Notification event types (called Notification Defaults) as they like and based on this multiple Notification events could be sent for a single container.
e.g. If a user signed up to receive Notifications for Discharge and Gate-Out events then for Import containers they would receive two Notifications per container for a total cost of $0.40.
The monthly subscription provides users with access to the detailed container information that PortConnect holds.
Notifications provide users with access to automated updates when events occur against containers. Notifications are in an XML format that allows users to automatically process this information into their system rather than manually checking the website – the per Notification cost covers the cost of providing this service.
Note, there is no charge for sending registration of interest (ROI) messages, only for receiving Notifications.
Setting up Notifications Defaults
Access to Notifications
If you are logged in and do not have access to Manage Notification Defaults please contact info@portconnect.co.nz.
Access Notification Defaults
Before you can start requesting notification you need to set up the different types of notifications that you want to be able to receive. These are called Notification Defaults.
Hover your mouse over the PortConnect tab and and select Manage Notification Defaults.
This will take you for the Notification Defaults page. On this page you can set up the Notification Types you want to be able to receive. Note – you only need to do this once and the defaults will display on the Container Notifications page.
Create a Notification Default
To set up a Notification Type first select the type of notification you would like to receive. There are currently 17 different notification types.
Next you must enter the email address you would like the notifications to be sent to. You can add multiple Notification Defaults and also add multiple email addresses for a single Notification Type.
Click the Save button once you have entered the email address. By clicking Save you agree to accept all charges for these notifications.
Once you have clicked Save, the Notification Default will display under Current Notification Defaults.
Once you have finished setting up your Notification Defaults you can start requesting notifications against containers.
Delete a Notification Default
If you wish to delete a notification type, you can do so by clicking in the circle on the left hand side of the Notification Default and then clicking Delete. The Notification Default will then be removed from your list.
Viewing Notifications via PortConnect website
Once you have Notification Defaults set up you, go to Manage Current Notifications under Services. This screen will display all containers which are currently registered for notifications by anyone at your company.
Tick the boxes of the notifications you would like to receive for the selected containers. You can choose notifications for individual containers or you can click the set all box at the top of each column.
Requesting Notifications via an Excel spreadsheet (An Easy way to receive Notifications)
If you would like to register containers using the spreadsheet please contact info@portconnect.co.nz to request this option.
There is no limit on how many containers you can register for in one file. You can Select the title of the rows and a note will pop up with what data is required in that column.
NOTE: You need to set up your Notification Defaults first before you register containers. You can see Instructions on setting up your defaults are above.
Requesting Notifications via B2B ROI
Business to Business (B2B) Registration Of Interest (ROI) is a way to register interest in containers so that you can automatically receive Notifications. A ROI message can be generated by your system and sent to PortConnect in a XML format. PortConnect will then register your interest in the requested container(s) and begin sending Notifications based on the defaults you have set up. This is an alternative to manual Registration of Interest through the PortConnect website.
You can read more in the B2B Notifications ROI On-Boarding Guide.
Requesting Notifications via API
PortConnect has an API (Application Programme Interface) version of the notifications functionality providing a new, more modern way of sending and retrieving data from PortConnect. You can read more about this on our API Documentation.
Receiving Notifications
How long it takes for the status to be sent?
Within 30minutes of the event occurring in the port internal system, OR
Within 15minutes of the event being recorded in PortConnect
Once you have requested a notification on a container, notification emails will start being sent to the nominated email address. The first email will include all the events/changes that you have signed up for and have already occurred against the container. Future emails will include any new events/changes that have occurred against the container.
The emails also contain an XML file which contains the same data as the body of the email.