WELS Reporting Client User Manual

Wellit AS

November 14, 2016

Contents

I User Manual 1

1 User Interface 51.1 Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1.1 Info Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1.2 Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1.3 Online Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1.4 Feedback Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.2 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 Voyage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3.1 Start or continue a voyage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.2 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.3 Sub Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.4 Current voyage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.5 Voyage Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.6 End voyage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.4 Deck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4.1 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4.2 Sub-menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.3 Deck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.4 Transit Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.5 Offload Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.4.6 Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.4.7 Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1.5 ROB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.5.1 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.5.2 ROB Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.6 Bulk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.6.1 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.6.2 Sub-Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.6.3 Bulk Tank Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.6.4 Bulk Tank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.6.5 Loading area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.6.6 Deviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.6.7 Offloading area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.6.8 Bulk Tank Content Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

iii

iv

Part I

User Manual

1

Introduction

To monitor and coordinate offshore operations, all vessels must report their activity. This is doneusing the WELS Reporting Client, which is a web based application running in the Google Chromeweb browser. The application allows a vessel to report events, consumables, the deck layout andbulk tank contents for each journey that it does.

Most of the system is available even when no internet connection is available. Clicking on ”SaveLocally” on any of the pages stores that data for the next time you open the page. Clicking on”Submit to Web” sends data to the WELS system, whilst Fetch from Web retrieves last saved data.To use the system, visit the web address reporting.welsoperator.com.

The majority of the reporting clients actions works offline, but some actions do need an active Internetconnection. This includes sending and fetching data from the server, the initial log-in and the buttonsthat are on the light-grey menu bar. If you do end up in a situation where you dont have an Internetconnection then keep reporting as much as possible locally and then do any additional operationsand submittals when you re-connect to the Internet. Input for voyage log, bulk actions and ROB inputworks fine without an Internet connection as well as placing containers.

When you have made a set of changes to the inputs press the Submit Web to send data to theserver. If you dont submit anything it will not be shown to anyone else. If you need to retrieve the lastsubmission press the Fetch Web button. Fetch Web will overwrite anything you have on your localmachine. In other words, if you have written and submitted 3 lines on the voyage log and write 3 newlines and press Fetch Web without submitting the last 3 lines then these will be overwritten.

Important: Try not to use more than 1 PC for reporting as all data is stored locally in the web browserbefore submittal. If anyone reports on a different PC without having done a Fetch Web first he mightoverwrite previous values with his own locally stored values. If you do use more than one PC pleasebe careful to make sure one PC always submits all data before the other PC fetches so that data issynchronized.

Voyage

Remember to send departure report to and from the rig. When starting a new journey, the last row inthe voyage log will become the top row on the new journey (the remainder of the log will be deleted).Bulk action history is also deleted except for the last which becomes the voyage ROB start. ROBvalues on the ROB page are deleted. Containers on deck are not modified.

All entries are supposed to be back-to-back, so that the start time for a new action is also the endtime for the previous action. New journey is started whenever you get to an onshore port and haveoffloaded everything that needs to be offloaded.

Fill in the estimated MT and M2 load/offload for deck cargo when doing a Cargo Action. Make surethat all events has a location and start time

Home

Here you can see the last 15 manifests and previous journeys from the WELS system. These can bedownloaded as PDF files. The manifests also state whether theyre open (working on it) or closed aswell as attachments.

3

Deck

To fetch any open or closed (no older than 12 hours) manifests from a location, select that locationfrom the dropdown list and press the Fetch Manifest button. The containers will be fetched and placedinto the Loadout area.

If you need to create your own containers, press the New Container button in the menu or doubleclickon the deck.

To offload containers move them to the Offload area. Once youve verified that theyre actually gone,press the Clear Offloading button to delete them.

Bulk

Location is where you did the load/offload action. Destination is where the cargo is headed for ( whichwill be NA- in an offload action).

Remember to fill in SG. Make sure that the date and time matches with a date and time for a cargoaction on the voyage log.

You don’t need to add ROB values here do any corrections on the ROB value when doing a load oroffload action (if applicable).

ROB

Midnight reporting for selected tanks. Fill in the remainder on the tank at the given time. Load/Offloadactions are done on the bulk page. Add your own time if needed, i.e. on-hire or off-hire values.

4

1 User Interface

5

1.1 Main Menu

The main menu consists of 4 main parts - a user-info area, the navigation area, an online status areaand feedback area.

1.1.1 Info Area

User-info area displays the name of the vessel that you are currently logged in as, along with a smallimage of the operator you are working for.

1.1.2 Main Menu

The main menu is the main naviation between home page, voyage, Selecting an option will highlightit, load new content on the page and display a submenu if applicable. If navigation elements aredisabled, this indicates that a voyage has not been loaded locally. Go to to voyage page to start anew voayage or fetch an existing one.

Home: Information page which shows the previous 15 manifests and voyages. These manifestsand voyage reports can be downloaded for external storage. If the operator also has the HSEQmodule then HSEQ can be reported from this page. Voyage: The voyage log for vessels to report thejourney’s details, start a new journey and send daily activity report.

Deck: Deck tool for fetching containers from manifests, or alternatively create them manually, andplacing these on the deck. Bulk: Layout of the bulk tanks where to report any load/offloads/tankcleaning and other actions. This is also where to upload fuel documentation. ROB: ROB reportingfor fuel/LNG and consumable that may need midnight reporting. Settings: Settings page for optionsor log out Help: Displays the help pages.

1.1.3 Online Status

This is an indicator to display whether an Internet connection is active or not. It also display thecurrent version of the application.

1.1.4 Feedback Status

This shows the last 3 lines of feedback from the system. This gives visual feedback for actions.Green colour indicates a successful action. Gray colour indicates generic information. Yellow colourindicates a warning, but which was expected (for instance, submitting to the server without an activeInternet connection). Red indicates an error that prevented an action from being performed.

6

1.2 Home Page

To view the contents on this page requires an active Internet connection as it automaticly downloadsthe latest content from the server.

The home page displays documentation that can be downloaded, this include checklists and 500mentry zone files if uploaded by the operator.

If the operator has activated the HSEQ module, HSEQ incidents and inspections can be reporteddirectly from the client,

The home page also shows a list of the last created manifests from the WELS system and the lastvoyage reports. All these can be downloaded as PDF files. Note the status open / closed. This isimportant when fetching manifested containers to deck state and manifested bulk to the bulk tanks. Ifa manifest is closed and older than 12 hours, you are unable to fetch the container and the manifesthas to be reopened until the containers are fetched. If for some reason there is a need to fetchcontainers from a closed manifest older than 12 hours, please contact your operator or support forassitance.

Figure 1.1: Figure shows the home page. In the top bar with blue background from left to right: InfoArea, Main Menu, Online Status. Below the Feedback Status with two messages.

7

1.3 Voyage

The voyage log consists the events that occur during a voyage. Examples include when a vesselsteams to new location, cargo action or being on standby. This is also the page where to senddeparture reports, daily reports and view documents attached to manifested container.

It also where to start or end an vessel.

Figure 1.2: Shows the voyage page

1.3.1 Start or continue a voyage

If a voyage has not been fetched or downloaded, the only available options in the Main Menu arethe Home Page, Voyage, Settings and Help. To start or continue a voyage, navigate to the voyagepage.

Click the ”Find open Voyages” to send a request to the server to fetch the oldest open voyage. If anopen voyage is found, this will be loaded and a notication will be shown.

The reason oldest voyages is selected is to minimize keeping multiple voyages open. If the voyageloaded is an old voyage , end this voyage without starting a new one. For how to end a voyage seethe section ”End voyage” later in the manual.

If there is no open voyages a choice between staring a new voyage or open a closed or rejectedvoyages (if any);

When starting a new voyage, the voyage log will shown and the application is ready to start report-ing.

8

Figure 1.3: 1. Click Find open voyages. 2. If a Open voyage is found this will be fetched. 3. If noopen voyages exist choose between starting a new voyage or re-open a closed/rejected voyage.

1.3.2 Menu

Save Local This option saves the event log to local storage. This means that it is saved on yourcomputer/web browser. This also allows you to work on the log even without an active Internetconnection. Save locally is done automatically when you go between the main menu pages. LoadLocal This option retrieves the latest event log previously stored in local storage. This is automaticallycalled when you enter a page.

Submit Web (Online access) This option submits/upload data to the WELS server so that otherusers can see what the vessel is reporting. An option is given to send either the voyage log, ROB logand bulk state together, just the deck data or everything.

Important: The submitted log will overwrite any previous log that may have been submitted on thecurrent voyage. This means that the vessel keeps the whole log and can edit any line wheneverneeded and then everything will be updated the next time the log is submitted.

Fetch Web (Online access) Fetches/downloads the voyage log, ROB log, deck state and bulk statefrom the server. A fetch will overwrite any data on the client.

Remove All This removes all log entries that are currently stored locally. This does not affect anylogs already submitted.

1.3.3 Sub Menu

Departure Form (Online Access) Open up a page in allowing a vessel to submit departure formsbefore leaving a location. Cargo orders are for ordering fuel, potwater etc. This is only saved when thedestination is a base. Estimated MT and M2 are reported as well to calculate deck efficiency.

9

Figure 1.4: The Departure report

Voyage Documents (Online Access) Open up a page in the back-end system that shows docu-ments relating to dangerous goods and other documents that may be of interest to the vessel andthat have been uploaded in WELS.

The vessel can mark manifests as approved or reject specific containers which might be missing DGdocumentation, backload documentation or similar reasons.

Note: This does not stop the vessel receiving any containers nor does it stop the manifests frombeing fetched at the rig or base. This is used to log any discrepancies that the vessel has regardingthe manifest in an effort to improve the verification process and to notify those creating the manifestsabout missing details.

Click on the Voyage documents button. A list of manifests created for the vessel will be displayed.

10

Figure 1.5: All manifests connected to the vessel

The approval button will only be displayed if the manifest is closed. If closed, then the approval buttonwill approve manifest. If a manifest is re-opened after approval it will revert to a non-approved statusagain.

Specific containers can also be clicked on to be rejected a comment regarding the rejection has tobe included. A container can be re-approved again by clicking on the rejection button. If one or morecontainers have been rejected, the manifest cannot be approved; approve all containers first.

Figure 1.6: Showing all documents connected to a manifest

Daily Reporting/Summary (Online Access) Open up a page which allows the vessel to set infor-mation for current captain and POB and what the plan for the day is. Todays and yesterdays planshould be updated once a day. The bottom half shows a summary of the submitted data for thecurrent day. Pressing the Submit button will send this summary as an email to interested parties whohave subscribed to the mailing list. A list of previously submitted summaries are displayed at the verybottom of the page.

11

The daily report allows a vessel to specify the captain on shift, its current POB and how many of thePOB are considered extra personnel. The planned actions and yesterdays plan can also be writtendown.

Figure 1.7:

The Report Date field allows a vessel to change the date for the report. It also updates the 7-daylook-back field on POB.

• ”Captain on Shift” - the current captain on the shift

• Next Crew Change enter when next crew change is scheduled. The date should then autoadjust for next crew change

• Current POB: The total amount of personnel on board

• Extra Bedding: Any POB considered extra

• Extra Meals: Any meals considered extra

• Location: The current location where vessel is located

• Today’s Plan: The plan for today

• Yesterday’s Actions: Summary of what happened yesterday

The values entered here will be available for marine coordinators to view and edit from WELS Oper-ator

List Voyages: Open up a list of all rejected and closed voyages within the last 60 days. Re-opena voyage to do corrections in voyage log, rob and bulk actions. Note that re-opening a old voyageautomaticly submits the current voyage, and that it is not possible to alter old deck states.

1.3.4 Current voyage

Mission type: Chooses what kind of mission type the voyage is (E.g Support, Anchor handling). Themission type will determine what types of event types it is possible to select in the event type fromthe event entries.

Start Date: Calculated from the date of the first event in the log.

End Date: Calculated from the date of the end voyage event

1.3.5 Voyage Log

Each row specifies an event.

12

Event Dropdown list of available event types to register. Some events, like ”Cargo action”, may triggeraddtional columns like ”Load/Offlead.

Location where event occurred. If a steaming event is selected then location should be the destina-tion.

Quay If the location has a quay, a dropdown will be available.

Date/Time When event occurred.

ROB Fuel / ROB LNG: It is an option to add ROB for both Fuel and Lng* before each event. Con-sumption of each event is the ROB event is calculated by the difference between the rob on the entry,and the next entry or ROB on end voyage.

Important to note that the rob entry will not be added to the Rob or Bulk page.

*Lng will only show if there is registered an LNG consumption tank on the vessel.

Additional Info For cargo events it is required to add extra information regarded how much M2/MTwas loaded on and of during the event. Press the Load/Offload button to activate a dropdown list. Ifthere is no information in entered, the button will be marked with a red border.

These 4 values are used when doing a Cargo action for loading or offloading. Write in the tonnageand m2 of cargo and bulk that has been offloaded and loaded.

Bulk (M3) is readonly, and only a summary from the actions int the bulk page.

Remarks Additional comments on the event

Remove and Add Deletes the row and adds a new row below the selected one.

1.3.6 End voyage

To end a voyage, there is an ”End Voyage” event at the bottom of the voyage log. This event hasthe event type locked, otherwise it behaves like any other event. To activate the ”End Voyage” buttonthere must be entered an valid date and time.

When the user press the end voyage button all the information will be sent for validation. If there areany messages these will listed in a popup for validation. The user can cancel to fix the eventual errorsor choose to ignore the messages and end the voyage regardless.

Choose ”End and Start voyage” to start a new voyage automatically. All information should be cleared,and the bulk tanks updated with a new start rob.

13

Figure 1.8:

1.4 Deck

The deck and container reporting page allows a vessel to receive containers from manifests andthen position those containers on the deck where they are physically located. This data can then besubmitted to the other users of the WELS system to show the deck layout at the current time anddate. As opposed to the voyage log, ROB log and bulk state, each submit adds a new snapshot ofthe deck instead of deleting the previous entry.

1.4.1 Menu

Save Local This option saves the containers to local storage. This means that it is saved on yourcomputer/web browser. This also allows you to work with already fetched ( or locally created) con-tainers even without an active Internet connection. Save locally is done automatically when you gobetween the main menu pages.

Load Local This option retrieves the containers previously stored in local storage. This is automati-cally called when you enter a page.

Submit Web (Online access) This option submits data to the WELS system so that other users can

14

see what the vessel is reporting. An option is given to send either the voyage log, ROB log and bulkstate together, just the deck data or everything. Deck/All should only really be done if changes havebeen done to the deck since last Submit and the deck is not empty.

Fetch Web (Online Access) This option retrieves the last deck state, ROB log, voyage log and bulkstate that was submitted to the server.

New Container This option displays a pop-up to the user where details for a new container canbe entered. The container can then be used as any other container. This should mainly be usedwhen containers are not included from the manifest or if back-end system is not being used formanifests

Clear Deck This moves all containers from the vessel deck to the offloading area which are not setas storage or roundtrip.

Clear Outgoing This removes all containers in the offload area. This does not affect anything in theback-end system, but is a way of deleting containers that have been offloaded and are no longer onthe deck.

Remove All This removes all containers on the screen. This does not affect anything in the back-endsystem, but is a way of starting with an empty deck.

1.4.2 Sub-menu

Fetch Manifest (Online Access) Select the location you want to fetch manifests from. This will fetchall open (those in planning stage) manifests and any closed manifest that are not older than 12 hoursfrom the given location. The containers will be put on the transit area. If some containers have beenfetched previously these will not be fetched again.

View And Synch Containers (Online Access) This shows the containers that were last submitted.This page shows additional information that is retrieved from the WELS system and also allows thevessel to delete containers that should not be part of the deck state anymore. This is an extra optionfor removing containers that should really be gone

1.4.3 Deck

The deck shows the width and length of available deck space for containers. It is scaled correctlyand may also show areas where cargo can’t be loaded or where only certain cargo can be loadedas a visual aid. Any containers fetched from manifest and which show up in the Transit Area can bemoved onto the deck to show where the location they are loaded upon. Once all containers havebeen placed from a base or rig, it is possible to save this information to the back-end system sothat other users can see the vessel’s current deck state. Double clicking on any part of the deck willmake a window appear for creating container at that spot. Containers that are to be taken off thedeck can be moved to the Offload Area. To move all containers atonce, except roundtrip and storagecontainers, into the offload area, just press ”Clear Deck” button.

The area above the deck displays a colour-coded list of which rigs are destination/origin on the placedcontainers. A search bar is also available to look up container labels.

1.4.4 Transit Area

Transit area shows any containers that have been loaded from a manifest at that base or rig. Themanifests are defined in the back-end system and when they are closed they can be fetched by thereporting client. The transit area will only show containers that don’t already exist on the page andwhich are on manifests that have not been received yet.

15

1.4.5 Offload Area

To mark containers that are not on the vessel anymore, move containers into the Offload area. Press-ing ”Clear Outgoing” button in the menu will remove any container that currently reside in the OffloadArea.

1.4.6 Container

Containers can be moved around by drag and drop. Pressing down the mouse button over a containerwill display a small window with more information. To see even more information or to edit it, justdouble-click on a container. Containers marked as dangerous, backload, roundtrip or storage will alsoreceive an icon on it to show what type it is and are colour coded based on which desitination/origin.Containers going to or coming from the same rig have the same colour. To create a new ad-hoccontainer, double click on the deck. A window will appear. It is possible to create one or severalcontainers of a predefined type or a completly custom.

Figure 1.9: New Container

16

Figure 1.11:

Figure 1.10: Update container.

When fetching containers the system searches for same or similar tags of the ad-hoc. If a ad-hoccontainer has the same tag as a manifested container then a popup will appear and it is possible toswitch the containers position.

Also note that properties on the manifested containers will update the containers on deck when

17

fetched. Example: A container is fetched from manifest, without weight and DG information. Thiscontainer is placed on deck. Later the manifest is updated with weight and DG information. Byfetching from the location, this information will automaticly be updated on the placed container.

1.4.7 Other Features

Figure 1.12:

Search for containers Search for a tag, all matching containers will be highlighted.

Clear Hightligth Remove the highlight of selected containers.

Total Weight When dragging containers onto deck, the total weight is updated. If one or more con-tainer are missing weigth a warning will appear. Clicking on the warning will hightlight the containerswithout weight.

Zoom Zoom in and out

Rotate Rotate a selected container 90 degrees.

Matching Manually Search for manifested container that share the same tag as a ad-hoc container.(The same function is used when containers are fetched from manifest.

18

1.5 ROB

This page allows a vessel to report ROB values. The daily ROB is reported at the end of the day,although ROB can be reported at any other time as well. Bulk tank reporting should be concernedwith load and offload operations whilst this page is for the ROB at the given time.

1.5.1 Menu

Save Locally This option saves the ROB log to local storage This also allows you to work on thelog, even without an active Internet connection. When you leave the ROB log page, the log is savedautomatically.

Load Local This option retrieves the latest ROB log that was saved in local storage.

Submit Web This option submits the whole ROB log, voyage log and bulk state to the server. Note:This overwrites any data that may be been submitted previously on the same journey.

Fetch Web Fetches the ROB log, voyage log, deck state and bulk state from the server. The wholelog for the current voyage is retrieved and displayed. This overwrites any existing data on in theclient.

Delete Log This removes all log entries that are currently displayed. This does not affect any datapreviously submitted to the server.

1.5.2 ROB Entry

The ROB log entries show all the changes that have been entered for a journey.

Date The date for the ROB report entry. Should be one per day and set as reported for end of the day23:59. The new ROB at the end of the day for that specific tank. If the header is empty then valuesin that column will not be needed and consequently not be saved. ROB values are also available toread from the Fuel, Potwater, Drillwater e.ge tank at the Bulk Page.

19

1.6 Bulk

The bulk reporting page shows the list of available bulk tanks the vessel has and the content within.It also allows a user to report the changes on each bulk tank as necessary.

The bulk tanks are grouped with all the tanks that carry content to and from the rig and the consum-able tanks in the rear (fuel, potwater etc).

Figure 1.13:

1.6.1 Menu

Submit Web (Online Access) This option submits bulk tank content, the ROB log and voyage log tothe back-end system. Note: This overwrites any previous data that may have been submitted on thesame voyage.

Save Local This saves the current state of the bulk tanks. This allows bulk tank data to be automati-cally fetched the next time the page is loaded, even without an active Internet connection.

Load Local This option retrieves bulk data from local storage.

Fetch Web (Online Access) This option retrieves the last submitted state for the ROB log, voyage log,bulk state for each of the tanks and deck state from the back-end system.

Remove All This clears the bulk tanks of content and its history. This does not affect any datasubmitted to the serve

20

1.6.2 Sub-Menu

Fuel Documentation: When fuel is loaded the accompanying documentation should be uploaded. Af-ter the bulk tank data has been submitted to Web, open up the Fuel Location and find the appropriateload/offload entry and upload any files. If there are missing a fuel event, try to submit to web andopen the fuel documents again.

Tank Clean Overview: Opens up a popup window to search for all tankcleanings.

1.6.3 Bulk Tank Overview

The bulk tank overview shows an approximation of the number and types of bulk tanks. The color ofeach tank is based on the last action. The default color is dark orange, and the port colors is definedin the Wels operator application.

The importance of the color is following:

• Destination is a rig: The color of the destination rig

• Origin is a rig: The color of the origin rig

• Destination (no rig)

• Origin (no rig)

• Default color

A legend that explains the colors is shown above the bulk tank overview.

The shape of the tank can be a circle or a square and is determined in the WELS operator applica-tion

1.6.4 Bulk Tank

A specific bulk tank on the vessel. It displays the tank name, and additional information if it has orhas had content in it. It shows the current ROB, name of the liquid and SG value. Clicking on a tankwill open a window with details of tank contents.

21

Figure 1.14: When clicking on a bulk tank it is possible to add, edit and remove bulk actions

1.6.5 Loading area

To view manifested bulk, select the port that bulk should be loaded from and press ”Fetch”. A loadingbar will appear, and manifested bulk and ad-hoc bulk will be displayed in the loading area. To registerload actions, drag manifested content into the bulk tanks.

(Component required) If the bulk matrix component is activated in Wels, there will be a color chartthat will help determine if the bulk could be mixed or not.

22

Figure 1.15: When dragging in to a tank a popup will appear. Input the quantity of the load action,unit, date/time and remarks.

Press ”Load to tank” and a load action is created. If this is the latest action, the bulk tank is updated.If the remaining qty is zero, the manifested bulk is removed.

To view or edit the load action, click on the bulk tank. See 2. Bulk Tank Content History for moreinfo.

If the load action is deleted the bulk apears back in the loading area.

Ad-hoc bulk from manifest does not always have a quantity attached. In these occasions it will beremoved from the loading area once loaded, regardless of the quantity

1.6.6 Deviations

To add an deviation when loading, drag from the loading area to the deviation area. Qty here willindicate the size of the deviation.

Example: There was manifested 100m3, but only 99m3 was loaded. Load 99m3 to the correct tank.1m3 will remain in the loading area. Drag the remaining 1m3 to the deviation area. Let the quantitybe 1m3, and correct the date and remarks.

Example 2: To much. There was only manifested 100m3 but there was loaded 110m3. Load 110m3to the tank. -10m3 will remain in the loading area. Drag the remainder to the deviation area. Load110m3 to the tank. -10m3 will remain in the loading area. Drag the remainder to the deviation area.Let the qty be -10m3 and correct the date and fill in remarks.

The deviations can be seen when you click on the deviation area. It is possible to remove or edit thedeviations from here.

To add a deviation from an offload action. Drag from the tank to the deviation area. These deviationswill be visible to the tank.

1.6.7 Offloading area

To offload bulk, drag and drop from the bulk tank to the offload area.

23

If there is a mix of cargo items and/or ad-hoc bulk, select what type of bulk (This can be a little artifical,but is to keep tracability from the manifest.)

1.6.8 Bulk Tank Content Input

The input fields for a tank allows content to be updated on the tank. Most of the fields keep the samevalue from previous entry of the bulk tank to make input processing faster.

Map cargo events Find all cargo events from the voayge log, sets the date and origin.

Action The type of action performed on the bulk tank. These are different ways to say what contentwas off-loaded or added to the tank.

Qty The quantity that was offloaded ,loaded, dumped etc. on/off the tank.

Unit If the quantity is added as mt, m3 or kg

ROB now calculated automatically.

Type of bulk loaded onto the tank.

Definition Write definition or specifics about the content being loaded.

SG value of the content. SG is required if unit is sat as m3

Origin Where the action is located. E.g. A load action on Mongstadbase, an offload action onYme.

Destination Where content is bound for. If content is bound for several destination, the best option isto put in the first location and keep that value until location has been visited and then update to nextone.

Company Which company supplied the content.

Date When the action occured. Make sure that there is at least 1 minute difference between actionson the same bulk tank so that the dates are compared properly.

Remarks Any additional remarks needed for the bulk entry.

Once information has been entered, click on add ad-hoc bulk. If an input is invalid, a validation willbe shown.

Bulk Tank Content History

The history of all actions during the voyage. It is possible to edit or delete all actions except ROB,which should be updated from the ROB page.

Tank Clean

To add a Tank Clean, select a bulk tank as if adding a bulk action. Select the tab ”Tank Clean”.Enter date and if applicable location. Note that there is no type, so use the remark field if this isneeded.

24