If a sample of the bunkered liquid or gas is taken, its analysis is handled as a **separate entry below the bunker report** - with its own view, its own buttons and its own status history. The result is completed in two steps: the check on board and the approval in the office. The workflow is the same as in the Lube Oil module, so the two behave consistently. ## Where the analysis lives Open **Bunker Reports** and unfold a report in the tree. Below it you will find an entry **Analysis: <number>**. Click it, and the analysis view appears on the right, including its status history. The buttons belonging to the analysis sit on the ribbon tab **Analysis** while this entry is selected: Button | What it does {class="compact"} ---|--- Edit Analysis | Corrects the details of the analysis. Confirm Analysis | The check on board. Approve/Reject Analysis (Office) | The approval in the office. ## The workflow at a glance Step | Who does it | Where | Result {class="compact"} ---|---|---|--- Create report and analysis | Vessel | **New**, then **Request/Edit Analysis** | Report and analysis exist Record the receipt | Vessel | **Request/Edit Analysis**, tick **Analysis Received** with date | Analysis entry appears in the tree Check the result | **Vessel only** | **Confirm Analysis** | Moves to **waiting for approval** Approve or reject | **Office only** | **Approve/Reject Analysis (Office)** | Analysis is complete - or goes back to the vessel Close the report | Vessel | **Close** | Report is closed As in Lube Oil: **checking happens on board, approval happens in the office.** Each button is only shown where it belongs. !!! If a button is missing **Confirm Analysis** is not shown in the office, **Approve/Reject Analysis (Office)** is not shown on board. **Standalone vessels** act as vessel and office at the same time and see both - there the four-eyes principle is achieved through the rights instead. Both buttons also depend on the status of the analysis, so check which folder it sits in as well. !!! ## Checking and approving **On board:** select the analysis entry, click **Confirm Analysis**, then enter the date, the checker and the result - **Passed** or **Failed**. For a failed result please add a remark; this is what the office reads when deciding. **In the office:** select the analysis entry, click **Approve/Reject Analysis (Office)**, then choose **Approve**. **Rejecting:** choose **Reject** and enter a reason - this is mandatory. The check is reset, the vessel can check the analysis again, and the rejection stays visible in the status history together with its reason. This can be repeated as often as necessary. ## The status history The analysis view contains a **Status History** table. Every step is one line with date, user and comment - requested, sent, received, waiting for approval, approved or rejected, closed. The newest entry is at the top. ## Status colours The status label uses the same colours as in Lube Oil, so the workflow stage is recognisable at first sight: Status | Colour | Meaning {class="compact"} ---|---|--- requested | light grey | Created together with the bunker report, no result yet sent | blue | Sent to the laboratory, result outstanding received / not checked | orange | Receipt recorded, waiting for the check on board waiting for approval | violet | Checked on board, waiting for the office decision closed | green | Approved - the analysis is complete, the report can be closed failed | red | Checked as failed and confirmed by the office - close the report with **Close (Analysis not okay)** rejected | dark grey | A rejection by the office, shown as a line in the status history - the analysis itself goes back to **received / not checked** ## Closing a report with an analysis Closing checks the actual state of the analysis. If something is missing, the message tells you exactly which step it is - in this order: Message | What to do {class="compact"} ---|--- *Please attach bunker delivery note first.* | Attach the delivery note to the report. *Please attach analysis first.* | Attach the analysis document. *Please set analysis as received first.* | Record the receipt of the analysis. *Please set analysis as checked first.* | Check the analysis on board with **Confirm Analysis**. *Analysis is waiting for office approval. Please have it approved first.* | The office still has to approve it. Once everything is done, the report closes after the usual confirmation prompt. For an analysis whose result was **Failed**, use **Close (Analysis not okay)**. This still requires the special right and a remark. Reports **without** a linked analysis behave exactly as they always did. ## Comments, reminders and documents **Comments, reminders and documents can be attached directly to the analysis.** These entries belong to the analysis and are **not** shown on the bunker report itself, which keeps the two apart. If you are looking for them on the report, that is why they are not there. Reminders appear in the **reminder overview** of the module and in the **User Dashboard**, in the existing section for bunker reminders - nothing has to be switched on separately for analyses. Each line shows two columns telling you what the reminder belongs to: Column | What it shows {class="compact"} ---|--- Site | The vessel the analysis or report belongs to. Subject | The analysis reference and title - or, for a reminder on the report itself, the report reference and port. This is how you tell the two apart at a glance. Clicking a reminder opens the analysis on the right, including its status history. When a bunker report is **deleted**, its analysis is removed together with it - including its comments, reminders, documents and status history. ## Optional: approval only for failed analyses **Bunker Reports → Configuration → "Office approval only required for failed analyses"** Setting | Effect {class="compact"} ---|--- Off (default) | Every analysis needs office approval. On | Only analyses with the result **Failed** need approval. A **Passed** analysis can be closed straight away. The setting is separate from the one in Lube Oil, so both modules can be configured independently. ## Rights you need The rights must be assigned to the relevant roles. **After a change of rights, users have to log off and log on again** - otherwise the new buttons will not appear. Right | What it allows {class="compact"} ---|--- Approve Analysis (Office) | Approving or rejecting an analysis in the office. Deliberately separate from the right to check an analysis, so that the two steps can be done by different people. Existing analysis rights | Requesting, editing, receiving and checking an analysis, and attaching analysis documents. *[PO]: Purchase Order *[AZA]: local folder *[(PO]: Purchase Order *[RQ]: Requisition *[(RQ]: Requisition *[RfQ]: Request for Quotation *[(RfQ]: Request for Quotation *[SO]: Service Order *[(SO]: Service Order *[SQ]: Service Requisition *[(SQ]: Service Requisition *[SRfQ]: Service Request for Quotation *[OoB]: Open on Board *[(OoB]: Open on Board *[ART]: Average Running Time (operation hours per day) *[MC]: Master Contract *[ADS]: Advantage Database Server (database engine used in previous versions of the ZeeBORN software) *[.replic]: file extension for replication files (aka data transfer files)