1 Getting Started

With the continuous growth in the Cruise Industry and the cruise ships are becoming larger, customers are looking for new ways to process passengers, crew members, and visitors coming on board or leaving the ship. The embarkation and disembarkation procedures which is a mandatory security process is performed at the ship’s gangway.

The regular operation consists of a fixed workstation connected to the ship's network. If there is a need to embark or disembark passengers more quickly, the IT Officers would need to set up additional workstations with scanner for connection to the network. Some of the challenges in setting up these workstations include limited space at the gangway, insufficient power supply sockets, and lack of network ports. With an application that runs on a tablet, this would enable crew the flexibility, mobility, and an expedited embarkation/disembarkation process

Note:

On the client PC, disabling the browser autofill option if preferred as it might update the data onto the wrong field.

Launching the application

To launch the application from a desktop browser:

  1. Open your browser. See Oracle Software Web Browser Support Policy for more information.

  2. Enter the URL for the application, for example, https://<webapp_hostname>:<portno>. See your system administrator to obtain the host name and port if you do not already have it.

To launch the application on an Android/iOS device:

  1. Open your browser. See Oracle Software Web Browser Support Policy for more information.

  2. Enter the URL for the application, for example, https://<webapp_hostname>:<portno>. See your system administrator to obtain the host name and port if you do not already have it.

  3. On an Android device, a pop-up notification Add to Home Screen appears. Click the button to add.

Log in to the application

  1. On the application page, enter your user name and password.

    Note:

    The user name and password is case-sensitive

  2. If you sign in with an incorrect user name, password or both, you will receive an error 'Invalid login. Please try again'. The field color changes to red and the account will be locked for a number of minutes after a few unsuccessful logins. The number of minutes is based on the value defined in the Lockout Minutes parameters.

  3. Upon successful login, your username and profile picture are displayed at the top right of the page, and it brings you to the Dashboard page.

  4. To log out from the application, press the arrow down icon on the page, and press the Sign Out button when shown. This brings you back to the login page.

  5. For user account that does not have permission to the application, an error ‘Permission is required to view this application’ will appear.

    Login by tapping the RFID card is supported. Users need to perform a manual login for the first time to generate the contactless key. During this process, a confirmation message ‘device/vm name want to see the change information on NFC devices that you tap with your phone’ shall prompt for you to enable the NFC device.

    These confirmation message is a default browser message.

    • Option Block - remain or disable the NFC reader

    • Option Allow - enable the NFC reader

  6. After selecting the Option Allow, user no longer need to log in manually and can log in by tapping the RFID card. However, users must perform a manual login again if they clear the browser cache, change the system cruise date, or remove the NFC device from the browser setting.

  7. If you tap with an invalid or inactive RFID card, you will receive an error message ‘Invalid card - please check your card and try again’.

  8. If the card format is incorrect, you will receive an error message ‘The system is unable to read the card’.

  9. If you tap an invalid RFID card and exceeds the number of attempts defined in the system parameter Account Lockout Duration’, an error message ‘RFID login feature is locked for xxx mins - Please try again later or sign in manually’ shall prompt.

    Note:

    RFID login is only supported on the Android device that has the NFC built-in.

Session Timeout

The application will time out when the screen is left idle for 45 minutes and prompts a 30 seconds countdown screen before expiring the session.

  • If the user does not perform any action within the countdown period, it logs out the user automatically and redirects to the Login screen.

  • If the Sign Out button is clicked, it signs out and redirects to the Login screen.

  • If the Continue button is clicked, the user remained signed in at the last visited screen.

Note:

The number of failed attempts is managed by System, Max Login parameter.