For problems with connecting, logging on, or other problems of this nature, the best place to start is with your internal IT department. They will be able to identify if the problem is with their systems or with DIOR itself. For problems relating to the content or reports, or with specific reports themselves, please contact PBPL on email dior@portbris.com.au or phone (07) 3258 4888.
When data for a cargo exchange is entered into PBPL’s data systems, it is assigned various dates.
The Invoice Date is the date when the data input process is finalised. This will usually be within two weeks after the cargo exchange, but can be longer. As a result, data for an exchange can appear in an invoice a month after the date of the exchange.
Arrival dated data is based on when the ship arrived at the port. Due to the delays in imputing data, it can take up to two months for arrival date data to accurately reflect activity in a given period. For example, cargo unloaded on 30 January will probably appear as occurring in February according to invoice dates. It will appear as January by arrival date, but may not be visible until late February or March.
The Invoice Date is the date when the data input process is finalised. This will usually be within two weeks after the cargo exchange, but can be longer. As a result, data for an exchange can appear in an invoice a month after the date of the exchange.
Arrival dated data is based on when the ship arrived at the port. Due to the delays in imputing data, it can take up to two months for arrival date data to accurately reflect activity in a given period. For example, cargo unloaded on 30 January will probably appear as occurring in February according to invoice dates. It will appear as January by arrival date, but may not be visible until late February or March.
The primary cause of these discrepancies is typically due to the use of Invoice Dates instead of Arrival Dates, or delays between cargo exchanges occurring and their being reflected in DIOR (see Q2).
Minor discrepancies can usually be explained by input errors either on the part of PBPL or the shipping agent providing manifests.
PBPL’s data systems class transhipped cargo as cargo originally loaded outside of Brisbane, and transferred from ship-to-ship in Brisbane. The cargo may be unloaded onto a wharf before being loaded onto another ship, or be transferred directly from ship-to-ship.
Non-transhipped cargo either starts or finishes its ocean journey in Brisbane.
Non-transhipped cargo either starts or finishes its ocean journey in Brisbane.
In order to prevent users accessing specific data on a competitor’s activities, a degree of aggregation is applied. For example, providing data on the movements of a specific, low volume commodity to a specific port could possibly reveal a shipping line’s customers.
The DIOR reports are developed with security as a top consideration. Apart from your own company’s information, all data is provided at an aggregated level.
This problem is usually caused by the user’s security settings.
PBPL recommends users contact their IT department for help in altering security/firewall settings to allow download of excel files from the DIOR server.
PBPL recommends users contact their IT department for help in altering security/firewall settings to allow download of excel files from the DIOR server.