Port management and business rules: how to implement IMO regulations
•Télécharger en tant que PPTX, PDF•
1 j'aime•800 vues
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.
![Industry solutions
Harbour / port management
[IMO] declaration processes](https://image.slidesharecdn.com/industrysolutionsoverviewharbour-121107095514-phpapp02/85/Port-management-and-business-rules-how-to-implement-IMO-regulations-1-320.jpg)
Recommandé
Contenu connexe
Similaire à Port management and business rules: how to implement IMO regulations
Similaire à Port management and business rules: how to implement IMO regulations (20)
Plus de 112Motion
Plus de 112Motion (20)
Dernier
Dernier (20)
Port management and business rules: how to implement IMO regulations
- 1. Industry solutions Harbour / port management [IMO] declaration processes
- 2. Our standard configurations • Tourism: quote and book an accommdation • Harbour: nautical (entry) rules
- 3. Harbour process Pre-arrival notification Dangerous goods and more
- 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. MCT Almak (tanker) to A’dam Linda Fortune (bulker) to R’dam
- 6. MCT Almak ship details
- 7. Log on using “agent” profile • Agent represents captain and can submit 4 “events”
- 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. Outstanding work items After entering ship details the agent knows he has to start three events
- 10. Next step -> declare dangerous goods History and Decision support inform the user (the agent)
- 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. sub-case: discharge at Vopak No rules for a tanker discharing at Vopak
- 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. 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. All case data is “collected” Harmony collects and time stamps all data and records all user access to the case
- 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. BULK CARRIER TO ROTTERDAM Linda Fortune
- 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. Linda Fortune to Rotterdam Linda Fortune can enter Port or Rotterdam 1. The maximum draught = 22.4 [mtrs]
- 21. Pre-arrival for Rotterdam Because of the ship’s length a pilot is required 1. And Pilot confirmation will be required
- 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. For more information • Visit – www.liquidsequence.com • Release overview – (all new features) • Contact us – http://liquidsequence.com/Contact.html