EIS Web User Interface Manual

Page tree

Versions Compared

Old Version 90

changes.mady.by.user European Dynamics Trans Contractor

Saved on

compared with

New Version Current

changes.mady.by.user TERRA HOMEM Miguel (EMSA)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
In order to access any of the EIS Consoles you there is a need to be authenticated and authorized. 
Each Console/Functionality requires at minimum to have a specific TaskPermission.Given that the Tasks are not directly assigned to users but to roles, eventually you need to have the appropriate role.
The role may or may not have Location or Source Restrictions:

Users are assigned roles to control their respective permissions, and there is a configuration of the application that maps each role to a set of Permissions that may or not have additional Location or Source restrictions setup.

A Location Restriction limits the geographic scope within which a user may exercise a given functionality (via WUI and/or System). That scope is defined by the location, country, or set of countries contained in the Location Restriction of the role /task of the user. 

For exampleExamples for clarity:-

  • Web User Interface: A user holding the LOCATION_MANAGER role

...

  • with a Location Restriction Level of "User's country" will find that the country-selection list, on the Search Location page of the Geo Console, includes only their own country.

...

  • System to System Interface: When notifying SSN for the creation of a PortPlus, a user holding the PORTPLUS_NOTIFIER role

...

  • with a Location Restriction Level of "User's country" may only designate a PortOfCall that belongs to that same country.

A A Source Restriction filters the exchange of information between an originating party (the notifier or requestor) and a counterparty (a potential recipient or source of information). It is imposed by determining whether the Source Restriction assigned to the counterparty includes the country of the originating user. A counterparty is eligible to receive from - or supply information to - the originator only when its permitted countries include the originator's country. 
For example:
- Web User Interface: On the Incident Report page of the Send Notification Console, a recipient country is present in the available recipients list only if it has at least one party whose Source Restriction includes the country of the logged-in notifier. For instance, if there is a country two parties by constraining, in terms of country, which counterparties a given party may exchange information with. It is defined by the set of countries permitted under the restriction (the user's own country, or the countries of a regional agreement), and an exchange is allowed only when one party's country falls within the other party's permitted countries. Which party's restriction is consulted depends on the direction of the information flow:

  • When sending information, the system checks each potential recipient's Source Restriction against the sender's country — a recipient is eligible to receive only if its permitted countries include the sender's country.
  • When searching for or requesting information, the system checks the requesting user's own Source Restriction against each provider's country — a notification is visible to the requestor only if the requestor's permitted countries include the provider's country.

Examples for clarity:

  • On the Incident Report page of the Send Notification Console, a recipient country is present in the available recipients list only if it has at least one party whose Source Restriction includes the country of the logged-in notifier. For instance, if there is a country that has only one party/user belonging to it, and that party/user has Source Restriction Level =

...

  • ”XW”, then only users of countries that belong to that specific regional agreement will have the country as an available recipient in the recipients list.

...

  • On the Voyage Information pages of the Find Notification Console, a ShipCall notification appears in the search results only if the searching user's own Source Restriction includes the country of the

...

  • party that originally provided it. For instance, a

...

  • console user whose Source Restriction Level is "XW" will

...

  • see ShipCall notifications only from providers whose country belongs to the "XW" regional agreement. 

...

The following restriction levels are available to be applied per case:

...

  • None: No restriction is imposed on Location

...

  • or Source Restrictions

...

  • ;
  • User’s country:

...

  • Restricts the scope to the user's Organization's country. Applies to both Location and Source Restriction.
  • Specific locations: Restricts the scope to a specific set of locations, identified by LOCODEs. The permitted LOCODEs are determined by the Duty Code assigned to the restriction (see Duty Codes below). Applies only to Location Restrictions

...

  • .

...

  • Countries list:

...

  • Restricts the scope to a specific set of countries. The permitted countries are determined by the Regional Agreement Code assigned to the restriction, which the system resolves to the corresponding ISO2 country codes (see Regional Agreement Codes below). Applies to both Location and Source Restriction.

The restriction levels for Source Restrictions and Location Restrictions are defined in the ROLES_TASKS table.

...

More  More specifically: 

Agency of the European Union

Information on this site is subject to a disclaimer, a copyright and personal data protection.

© 2023 European Maritime Safety Agency All Rights Reserved