IMOS - DA Interface Information & Process Flow
Home > Integrations > DA Interface Information & Process Flow
Requires the Integrations module.
UN Code Changes May Affect Integrations
Starting in September, we will be standardizing UN codes by removing 2 digit codes, removing duplicates, and adding official UN codes to the database. This could affect integrations.
The following table describes the flow of information between the Veson IMOS Platform (IMOS) and Hub Agent systems:
Activity | Responsible Party | Manual/Automatic | Frequency | |
|---|---|---|---|---|
| 1 | Activate vessel for Voyage Reporting communication | Client Company | Manual | Initial bulk activation and when a new vessel is added |
| 2 | Schedule voyage | Chartering User | Manual/already happening | On voyage scheduling |
| 3 | Activate voyage to send/receive port call and DA Information | Veson IMOS Platform | Automatic | Automatic on port call entry/cancellation |
| 4 | Set data submission agent | Veson IMOS Platform | Automatic | Automatic on port call entry/cancellation |
| 5 | Nominate agent at port where port expense proforma/final is expected | Operations User | Manual | On each port call Note: There is a report created to support this process. |
| 6 | Port call information sent to Hub Agent | Veson IMOS Platform | Automatic | Automatic on port call entry/cancellation |
| 7 | Nominate agent in Hub Agent portal | Operations User | Manual | On each port call |
| 8 | Send PDA/FDA from Hub Agent to the Veson IMOS Platform voyage | Hub Agent | Automatic | On each port call with a nominated voyage |
| 9 | Approve port disbursement form | Veson IMOS Platform | Automatic | Once for each port disbursement form |
| 10 | Review approve/post port expense invoice | Operations User | Manual | In each port expense invoice |