Port management and business rules: how to implement IMO regulations

610
-1

Published on

Slideshow demonstrating the business rules and processing logic involving the following processes:
1. declaration of dangerous goods
2. pre-arrival notification
3. MARPOL declaration
The Slideshow presents screenshots of the workflow application and some samples of the way the rules are implemented.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
610
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Port management and business rules: how to implement IMO regulations

  1. 1. Industry solutions Harbour / port management [IMO] declaration processes
  2. 2. Our standard configurations • Tourism: quote and book an accommdation • Harbour: nautical (entry) rules
  3. 3. Harbour process Pre-arrival notification Dangerous goods and more
  4. 4. • MCT Almak & Linda Fortune are real ships that have visited port of Amsterdam and Rotterdam in 2012 • A port “Anydam” exists with max port sizes – for testing only • Disclaimer on the rules – Not all rules are exactly adhering to port regulations About the cases
  5. 5. MCT Almak (tanker) to A’dam Linda Fortune (bulker) to R’dam
  6. 6. MCT Almak ship details
  7. 7. Log on using “agent” profile • Agent represents captain and can submit 4 “events”
  8. 8. Agent enters ship details Once destination is entered … Harmony rules “fire” and the results are shown in decision support: 1. Three processes are required (see ) 2. As ship length < 150 mtr no pilot required
  9. 9. Outstanding work items After entering ship details the agent knows he has to start three events
  10. 10. Next step -> declare dangerous goods History and Decision support inform the user (the agent)
  11. 11. Pre-arrival is required Agent starts pre-arrival … and plans a voyage (to a berth). Note that the workflow “behaves” as a User Interface dialog
  12. 12. sub-case: discharge at Vopak No rules for a tanker discharing at Vopak
  13. 13. sub-case: ship-ship transfer at Oiltanking Discharge is allowed … but a Permit is required, this is just an text message – no process associated Dangerous goods control is required …by the dangerous goods department
  14. 14. sub-case: ship-ship transfer at Oiltanking Ship-to-ship transfer is NOT allowed … emails will be sent (addresses are mapped to roles “Harbour master” and “DG dept”
  15. 15. All case data is “collected” Harmony collects and time stamps all data and records all user access to the case
  16. 16. Decision table “declare" __
  17. 17. Decision table “berth approval" __ The above is copied from port of Amsterdam website. Below is a sample of a multiple dimension decision table
  18. 18. BULK CARRIER TO ROTTERDAM Linda Fortune
  19. 19. Linda Fortune to Amsterdam Once port of destination is entered … Harmony rules “fire” and the results are shown in decision support: 1. Ship is too big for Port of Amsterdam 2. No access
  20. 20. Linda Fortune to Rotterdam Linda Fortune can enter Port or Rotterdam 1. The maximum draught = 22.4 [mtrs]
  21. 21. Pre-arrival for Rotterdam Because of the ship’s length a pilot is required 1. And Pilot confirmation will be required
  22. 22. Configuration overview Part Number of Total rows Rules 34 (50) - Dialogs (process steps) 11 (24) 85 Reference files 10 (15) - MDT 2 (5) < 40 DT none (4) Expressions none (?) Templates 6 (10) Groups 5 (8) Development time (weeks) 1 (3) (in brackets) is the estimate for a fully developed version
  23. 23. For more information • Visit – www.liquidsequence.com • Release overview – (all new features) • Contact us – http://liquidsequence.com/Contact.html
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×