port management and business rules: how to implement imo regulations

Post on 26-May-2015

506 Views

Category:

Technology

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

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.

TRANSCRIPT

Industry solutions

Harbour / port management[IMO] declaration processes

This presentation reflects a “build” with an old release ([1:0] of Harmony – it will be updated by

5 May 2014 – reflecting many new Harmony featuresOn the last slide there are references to more recent materials

Our standard configurations

• Tourism: quote and book an accommdation

• Harbour: nautical (entry) rules

Harbour process

Pre-arrival notificationDangerous goods

and more

• 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

MCT Almak (tanker) to A’damLinda Fortune (bulker) to R’dam

MCT Almak ship details

Log on using “agent” profile

• Agent represents captain and can submit 4 “events”

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

Outstanding work items

After entering ship details the agent knows he has to start three events

Next step -> declare dangerous goods

History and Decision support inform the user (the agent)

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

sub-case: discharge at Vopak

No rules for a tanker discharing at Vopak

sub-case: ship-ship transfer at Oiltanking

Discharge is allowed … but a Permit is required, this is just an text message – no process associatedDangerous goods control is required …by the dangerous goods department

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”

All case data is “collected”

Harmony collects and time stamps all data and records all user access to the case

Decision table “declare"

__

Decision table “berth approval"

__

The above is copied from port of Amsterdam website.Below is a sample of a multiple dimension decision table

BULK CARRIER TO ROTTERDAMLinda Fortune

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 Amsterdam2. No access

Linda Fortune to Rotterdam

Linda Fortune can enter Port or Rotterdam1. The maximum draught = 22.4 [mtrs]

Pre-arrival for Rotterdam

Because of the ship’s length a pilot is required1. And Pilot confirmation will be required

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

For more information

• Visit– www.liquidsequence.com

• Release overview – (all new features)

• Contact us– http://liquidsequence.com/Contact.html

top related