Check out the latest updates below.
Implemented the following improvements in the Settings under Berth Admin:
-Renamed the existing dropdown ‘Number of Days’ to ‘Number of Days in Future’.
-Introduced a new dropdown ‘Number of Days in Past’ that allows the users to select the number of days in the past to view along with the future dates in the graph view. This new dropdown has the following values:
NONE (default) - If NONE is selected, the graph starts from the current time up to the number of days mentioned in the ‘Number of Days in Future’ dropdown. The working vessel visits are displayed at the top of the section. (This is the existing behavior of application.)
Past 1 Day
Past 3 Days
Past 7 days
If any value apart from NONE is selected, the graph displays the vessel visits in the past days as per the selection up to the number of days mentioned in the ‘Number of Days in Future’ dropdown. In this view, the working vessel visits are displayed as part of the graph (not in the section header). The working vessel visits are displayed between the ATB and the ETD of the vessel visits. Thus, the ETD value must always be greater than ATB.
Added a new option to improve the print functionality for planning views. Users can now select the desired orientation to optimize space utilization.
Landscape: Displays 5-6 days per page
Portrait: Displays 13-15 days per page
The Vessel Visit Inspector window now includes a clear display of counts for planned, pending, and completed moves. This allows the users to view these counts directly within the inspector window.
When a user assigns a vessel visit from the N4 column, there is now an option to view 'All Proforma Instances' in the Direction dropdown in the Match Vessel Visit to Proforma modal. When the user selects 'All Proforma Instances', the available instances are listed for all the directions in the order of ETB. The maximum number of instances that can be listed is 20 currently.
Introduced a new feature that provides auto recalculation of berth position by BWM when invalid berth position in entered in N4. The recomputed values will be sent back to N4. This functionality is controlled by a new setting ‘Enable Berth Recalculation’ in the TOS Integration Configuration section. The default value is TRUE. Disabling the setting will skip the berth recalculation logic even if invalid values are entered in N4 falling back to the old behavior.
BWM follows the logic below to compute the valid berth position based on the ship length and grouped section length (Soft section lengths are grouped and added up):
1. Checks if Bollard Aft position is valid and recomputes Bollard fore and offset, if required.
2. If Bollard Aft is invalid, BWM recomputes the berth position based on Bollard fore value and derives Bollard Aft and offset.
3. If both the Bollard Aft and Fore are invalid, BWM places the vessel in the middle of the grouped section.
4. If all the above fails due to mismatch of grouped section length and ship length, BWM rejects the update and reverts the berth position to the previous value in N4. If there is no previous berth position, the vessel is placed in the U/A column and the added berth record is removed in N4.
Note:
XvelaUtils.groovy must be redeployed with the latest version to support this enhancement as the default status of the setting BOLLARD_OFFSETS_SCALE_IN_CM has been made as false.
Introduced a new value ‘per Quarter’ in the Show entries dropdown in the Berth Archive. When this value is selected, the user can see 90 days of data in the Berth Archive graph/table view.
As needed, users can now dynamically modify the date range for the actuals and proforma data directly from the graph view. Users can select from 7, 14, 30, and 60 days. By default, the date range in the graph view aligns with the selected ‘Number of Days in Future’ in the Settings under Berth Admin and resets to this default value after relog in or saving the settings again. The ‘60 days + all records in the table’ option is not available for selection in the graph view. However, if the ‘60 days + all records in the table’ option is selected in the settings, the graph view defaults to a 60-day view while displaying all records in the table.
Added a new setting ‘Auto Calculate ATS’ in Berth Admin to enable or disable the auto-calculation of ATS based on the ‘Idle Before’ time. If the ‘Auto Calculate ATS’ checkbox is checked, ATS is automatically calculated using the ‘Idle Before’ time. If the ‘Auto Calculate ATS’ checkbox is unchecked, the ‘Idle Before’ time" is null and ATS is not auto calculated.
The berth/api/v1/terminal/list API used for third-party integration now includes two new fields: etb (Expected Time of Berth) and voyageIn. External clients, such as Awake AI or EESea, use etb and voyageIn fields to send back timestamps associated with specific visits, enabling enhanced tracking and timestamping for these visits. Below is a sample response structure.
Sample response:
{
"payload": {
"ESALG-GTTI": [
{
"imo": "9225263",
"mmsi": null,
"voyageIn": "303W",
"etb": "2025-01-09T10:23:00.000000+0000"
}
],
"ESALG-TTI": []
},
"errors": null
}
Line operator and carrier service created or updated in N4 will now be automatically synced to My Navis Account. The code extensions ‘XvelaCarrierOutbound’ and ‘XvelaCarrierServiceOutbound’ will intercept the line operator and carrier service and will push the data to BWM. BWM will receive those updates and create corresponding records in My Navis Account. Configure the following extension triggers in N4 if not done already:
‘XvelaCarrierOutbound’ groovy for LineOperator entity
'XvelaCarrierServiceOutbound’ groovy for CarrierService entity
Note:
‘XvelaDmeJob’ must be redeployed with the latest version to support this enhancement.
-Enhanced the application performance with better memory management and smoother interactions across various views and actions.
-Reintroduced the Fit-to-Width functionality with a slider to ensure consistent behavior when toggling views and refreshing the page.
Background:
Print preview was empty when the user printed the table or graph for the first time in the Actual Graph/Table view.
Resolution:
Provided fix so that the Print preview now displays the data in the table or graph on the user’s first attempt to print from the Actual Graph/Table view.
Implemented the following improvements in the Settings under Berth Admin:
-Renamed the existing dropdown ‘Number of Days’ to ‘Number of Days in Future’.
-Introduced a new dropdown ‘Number of Days in Past’ that allows the users to select the number of days in the past to view along with the future dates in the graph view. This new dropdown has the following values:
NONE (default) - If NONE is selected, the graph starts from the current time up to the number of days mentioned in the ‘Number of Days in Future’ dropdown. The working vessel visits are displayed at the top of the section. (This is the existing behavior of application.)
Past 1 Day
Past 3 Days
Past 7 days
If any value apart from NONE is selected, the graph displays the vessel visits in the past days as per the selection up to the number of days mentioned in the ‘Number of Days in Future’ dropdown. In this view, the working vessel visits are displayed as part of the graph (not in the section header). The working vessel visits are displayed between the ATB and the ETD of the vessel visits. Thus, the ETD value must always be greater than ATB.
Added a new option to improve the print functionality for planning views. Users can now select the desired orientation to optimize space utilization.
Landscape: Displays 5-6 days per page
Portrait: Displays 13-15 days per page
The Vessel Visit Inspector window now includes a clear display of counts for planned, pending, and completed moves. This allows the users to view these counts directly within the inspector window.
When a user assigns a vessel visit from the N4 column, there is now an option to view 'All Proforma Instances' in the Direction dropdown in the Match Vessel Visit to Proforma modal. When the user selects 'All Proforma Instances', the available instances are listed for all the directions in the order of ETB. The maximum number of instances that can be listed is 20 currently.
Introduced a new feature that provides auto recalculation of berth position by BWM when invalid berth position in entered in N4. The recomputed values will be sent back to N4. This functionality is controlled by a new setting "Enable Berth Recalculation" in the Tos Integration Configuration section. The default value is TRUE. Disabling the setting will skip the berth recalculation logic even if invalid values are entered in N4 falling back to the old behaviour.
BWM follows the logic below to compute the valid berth position based on the ship length and grouped section length (Soft section lengths are grouped and added up):
1. Checks if Bollard Aft position is valid and recomputes Bollard fore and offset, if required.
2. If Bollard Aft is invalid, BWM recomputes the berth position based on Bollard fore value and derives Bollard Aft and offset.
3. If both the Bollard Aft and Fore are invalid, BWM places the vessel in the middle of the grouped section.
4. If all the above fails due to mismatch of grouped section length and ship length, BWM rejects the update and reverts the berth position to the previous value in N4. If there is no previous berth position, the vessel is placed in the U/A column and the added berth record is removed in N4.
Note:
XvelaUtils.groovy must be redeployed with the latest version to support this enhancement as this setting BOLLARD_OFFSETS_SCALE_IN_CM has been made default status as false.
Introduced a new value ‘per Quarter’ in the Show entries dropdown in the Berth Archive. When this value is selected, the user can see 90 days of data in the Berth Archive graph/table view.
As needed, users can now dynamically modify the date range for the actuals and proforma data directly from the graph view. Users can select from 7, 14, 30, and 60 days. By default, the date range in the graph view aligns with the selected ‘Number of Days in Future’ in the Settings under Berth Admin and resets to this default value after relog in or saving the settings again. The ‘60 days + all records in the table’ option is not available for selection in the graph view. However, if the ‘60 days + all records in the table’ option is selected in the settings, the graph view defaults to a 60-day view while displaying all records in the table.
Added a new setting ‘Auto Calculate ATS’ in Berth Admin to enable or disable the auto-calculation of ATS based on the ‘Idle Before’ time. If the ‘Auto Calculate ATS’ checkbox is checked, ATS is automatically calculated using the ‘Idle Before’ time. If the ‘Auto Calculate ATS’ checkbox is unchecked, the ‘Idle Before’ time" is null and ATS is not auto calculated.
The berth/api/v1/terminal/list API used for third-party integration now includes two new fields: etb (Expected Time of Berth) and voyageIn. External clients, such as Awake AI or EESea, use etb and voyageIn fields to send back timestamps associated with specific visits, enabling enhanced tracking and timestamping for these visits. Below is a sample response structure.
Sample response:
{
"payload": {
"ESALG-GTTI": [
{
"imo": "9225263",
"mmsi": null,
"voyageIn": "303W",
"etb": "2025-01-09T10:23:00.000000+0000"
}
],
"ESALG-TTI": []
},
"errors": null
}
Line operator and carrier service created or updated in N4 will now be automatically synced to My Navis Account. The code extensions ‘XvelaCarrierOutbound’ and ‘XvelaCarrierServiceOutbound’ will intercept the line operator and carrier service and will push the data to BWM. BWM will receive those updates and create corresponding records in My Navis Account. Configure the following extension triggers in N4 if not done already:
‘XvelaCarrierOutbound’ groovy for LineOperator entity
'XvelaCarrierServiceOutbound’ groovy for CarrierService entity
Note:
‘XvelaDmeJob’ must be redeployed with the latest version to support this enhancement.
-Enhanced the application performance with better memory management and smoother interactions across various views and actions.
-Reintroduced the Fit-to-Width functionality with a slider to ensure consistent behavior when toggling views and refreshing the page.
Background:
Print preview was empty when the user printed the table or graph for the first time in the Actual Graph/Table view.
Resolution:
Provided fix so that the Print preview now displays the data in the table or graph on the user’s first attempt to print from the Actual Graph/Table view.
Background:
The red color background indicating overlapping vessel visits was displayed for all BWM users.
Improvement:
You can now enable or disable the mentioned indication for external users through a new setting ‘Show conflicts (overlaps) color as background’ in Berth admin -> Vessel Visit Box -> External Users View. When ‘Show conflicts (overlaps) color as background’ checkbox is enabled, the external users can see the red color background indicating overlapping vessel visits. When ‘Show conflicts (overlaps) color as background’ checkbox is disabled, the external users cannot see the red color background indicating overlapping vessel visits. By default, this new checkbox is enabled.
Background:
Line operator and carrier service created in N4 were not automatically synced to My Navis Account which impacted BWM.
Improvement:
Enhanced the sync capabilities of BWM to help sync the created line operators and carrier services from N4 to My Navis Account.
Added two new code extensions 'XvelaCarrierOutbound' and 'XvelaCarrierServiceOutbound' that intercept the line operator and carrier service and push data to BWM. BWM will receive those updates and create corresponding records in My Navis Account. Configure the following extension triggers in N4:
‘XvelaCarrierOutbound’ groovy for LineOperator entity
‘XvelaCarrierServiceOutbound’ groovy for CarrierService entity
Note:
‘XvelaDmeJob’ must be redeployed with the latest version to support this enhancement. Currently, only create operation is synced from N4 to BWM and updates will be synced in the future releases.
Background:
For external users with the privilege ‘Ext - Display other vessel visits as blank boxes’, BWM displayed ghost visits (unallowed carriers/services) as empty boxes.
Improvement:
Rather than just empty boxes, how BWM displays the ghost vessel visits (unallowed carriers/services) for external users can now be configured in the Berth App -> Berth Admin -> Vessel Visit Box-> External User View. The following fields are available for configuration in the External User View:
Vessel Name, Carrier Logo, ETB, ETD, Vessel Visit ID, Service Code, Voyage In-Voyage Out, Service Name, Carrier Code, Terminal Stay, ETA, Vessel Berth Direction, Bollard Aft/Bridge/Fore, Mark Aft/Bridge/Fore, Ship LOA.
External users with the privilege ‘Ext - Display other vessel visits based on settings’ can now view the ghost vessel visits with the configured fields.
Note:
The privilege ‘Ext - Display other vessel visits as blank boxes’ is replaced with ‘Ext - Display other vessel visits based on settings’.
Introduced two new columns ‘From Mark’ and ‘To Mark’ for vessel berth position display in the BWM Print (Actual) view. This improvement ensures that the first value (From Mark) is always smaller than the second (To Mark) regardless of the vessel direction, improving clarity for Port Authorities.
Added a new toggle option in the Proformas Graph view to allow users to hide or unhide non-regular and ad-hoc vessel services a more customizable graph view.
Introduced Fit To Width button in the top navigation bar of the Actuals Graph view. If the length of the terminal is longer than the screen width, a horizontal scrollbar is displayed to scroll to the next section. When the user clicks on the Fit To Width button, all the sections will be displayed in a single screen view. If the user wants to go back to the normal scrollbar view, the user must refresh the page.
Background:
Crane assignments from N4/XPS/BWM were not recorded in the vessel visit activity logs.
Resolution:
Crane assignments and changes in the crane’s operating start and end times are now recorded in the vessel visit's activity logs in BWM. Also, BWM now updates the cranes from N4 without removing any of the existing cranes for that vessel visit.
Updated the following code extensions:
Background:
When the vessel was updated in the Vessel Inspector > Actions > Edit Vessel Visit Details form in N4, the updated vessel was not reflected in BWM.
Resolution:
Provided fix so that changes made in N4 are synchronized and displayed correctly in BWM. This ensures that the vessel is updated in both systems.
Background:
Vessel name and other information for small vessels or vessels with more cranes were not properly displayed in the BWM Main view.
Resolution:
Adjusted the font size of the vessel name in the BWM main view for improved readability. The display now adapts to the vessel size and crane assignments width for better visibility.
Provided fix so that BWM will now accept empty values for ATA and ATB from N4.
Background:
Xvela cargo moves job triggered an expensive query.
Resolution:
Updated the ‘XvelaCargoMovesUtils’ code extension to fix the expensive query. This groovy must be deployed via SNX import and all xvela code extensions must be recompiled
Provided fix in BWM to sync crane assignments from N4 without any error when there are regular and limited work shifts created on the same dates.
Introduced a new setting ‘Phase updates to TOS’ in BWM to control the groovy behavior in N4. When ‘Phase updates to TOS’ is enabled, the vessel visit phases are automatically updated by XvelaVesselVisitInbound.groovy based on the timestamp information provided by BWM. Below are the conditions for the different vessel visit phases:
Departed: If ATD is present
Complete: if ATC is present
Working: if ATS is present
Arrived: if ATA is present
Inbound: if berth is present without Actual timestamps
Created: if berth is not present and only estimated timestamps are present
Cancelled: if vessel visit is cancelled in BWM
Note:
ATS will not be computed automatically if this setting is enabled to support the Arrived and Working phases in N4. Also, the above setting will work only from the BWM groovy version V1.18.0.
ATS can now be empty or can now be cleared. Regardless of the value of the new setting ‘Phase updates to TOS’,
-if ATS is cleared, the top operations bar displays ETS. ETS is now calculated based on ATB and ‘Idle’ time before operations start configured in the Settings tab under Berth Admin.
-if ATS is entered, the top operations bar displays ATS.
Introduced a new setting ‘Enable Adhoc Visit auto match’ under TOS Integration Configuration in the Settings under Berth Admin. If this new setting is enabled, when you update the berthing for a vessel visit generated in N4 and there is no defined proforma in the terminal, BWM automatically attaches adhoc proforma to the vessel visit and berth the vessel in the Actuals/Graph. The direction considered is the first direction specified in the attached carrier service.
The already existing ‘Transshipment units’ check box in the ‘Base optimization on’ options in the Auto Planner screen is now split into three different checkboxes
Export units
Import units
Transshipment discharge
Transshipment load
Transshipment connection
Transshipment has been removed from the distance chart of the optimization result and is now divided into import and export as per the calculation below:
Background:
Users could not delete old crane assignments because past dates were not displayed on the left-side panel.
Resolution:
Added an option in the Vessel Visit Inspector>Cranes tab>’Delete Conflicting Crane(s)’ so that users can now delete the old crane assignments. This new option will only be available if there are conflicting crane assignments. To delete old crane assignments, click on ’Delete Conflicting Crane(s)’ then save.
Provided fix so that the Company Service module is always displayed for the user who has the privilege.
Background:
No error was displayed when two vessel visits were created for the same vessel/voyage.
Resolution:
Provided fix in the XvelaVesselVisitInbound.groovy. Please redeploy the code extension via SNX import and recompile all the "xvela" code extensions.
Provided fix so that when you hover over a vessel visit in the Actuals Graph view, the mini inspector at the bottom now displays the full name of the vessel.
Background:
Discrepancy in Gang Count Calculation with Multiple Cranes Assigned to a Vessel
Resolution:
Fixed an issue where the gang count was incorrectly calculated when multiple cranes were assigned to a vessel for overlapping periods within the same shift.
The gang count now accurately reflects the number of gangs working, even when multiple cranes are assigned with overlapping times.
Background:
Possibility to display all cranes in graph view
Resolution:
Introduced a visible horizontal scrollbar in the left crane section to improve accessibility and navigation.
This update allows users to scroll through all cranes efficiently, ensuring better visibility and ease of use, especially when working with a large number of cranes.
Background:
Vessel visit ETA field from N4 is not synced with BWM ETA. This becomes an issue when "UPDATE_VALUES_FOR_ETA_ETD" setting is configured in N4.
Resolution:
Introduced a new setting ‘Accommodate Tos ETA’ in BWM. If the setting is enabled,
1. ETA in BWM will be synced to ETA in N4 with ETA source in BWM set to ‘manual’ instead of settings.
2. ETB in BWM will be synced to Berth ETA in N4.
This provides support for the N4 setting UPDATE_VALUES_FOR_ETA_ETD to use ACCOMMODATE_VESSEL_VISIT_RANGE_FOR_BERTH. By default, the setting is disabled and ETA in N4 will be synced with ETB in BWM. This setting should not be enabled if the N4 setting has contradicting value
If the vessel visit has a manual ETA and is dragged vertically in BWM, then the ETA will be computed based on the ETB and Pilot in time and the ETA source will be set to ‘settings’.
A groovy fix is provided to stabilise this functionality, and this is a mandatory redeployment for all the customers. The groovy fix is provided in the XvelaVesselVisitInbound.groovy code extension. If the customers have old set of code extensions lower than v1.17, it is recommended to redeploy all the latest code extensions of BWM.
Enabling the setting "Accommodate Tos ETA" in BWM will overwrite the pilotEta customisation in N4 and the BWM ETA value will be synced with N4 vessel visit ETA. To continue using the pilotEta customization, the value for the flex field “{{useVvFlexDate02ForPilotEta}}" should be set to true in XvelaVesselVisitInbound code extension. By default, this value is set to false.
Background:
If ATA is cleared in N4, it was not cleared in BWM. And when the visit was dragged in BWM, the ATA in BWM was updated back to N4.
Resolution:
Provided fix in BWM to accept empty ATA value from N4.
Background:
BWM displayed the crane blockage for vessel visits which are out of range for the crane blockage.
Resolution:
Provided fix so that only vessel visits which are in the crane blockage range will get the warning.
Background:
Transshipment units with current position as yard were not displayed in the heatmap.
Resolution:
Provided fix so that the heatmap now includes the transshipment units with current position as yard.
Background:
Previously, for Azure specific SaaS deployment of N4, the crane assignments done in BWM were not reflected in N4.
Resolution:
Provided a fix so that for both cloud and on-prem deployment of N4, the crane assignments sync between N4 and BWM remains consistent.
Introduced a new setting ‘Enable Adhoc Visit auto match’ under TOS Integration Configuration in the Settings under Berth Admin. If this new setting is enabled, when you update the berthing for a vessel visit generated in N4 and there is no defined proforma in the terminal, BWM automatically attaches adhoc proforma to the vessel visit and berth the vessel in the Actuals/Graph. The direction considered is the first direction specified in the attached carrier service.
Background:
Vessel visits that were created in N4 with invalid timestamps were not reflected in BWM.
Improvement:
Introduced a new setting ‘Relax timestamp validations’ under TOS Integration Configuration in the Settings under Berth Admin.
By default, this setting is disabled. When you enable this setting, the following happens:
-BWM displays the vessel visits that are created in N4 with invalid timestamps listed below:
Past date in the ETA, ETB, and ETD fields
Future date in the ATA, ATB, and ATD fields
Past date in the ATD field but no value in the ATB field
Large terminals stay duration of more than 14 days computed based on the ETA and ETD fields
-BWM displays the vessel visits that are created in N4 with invalid timestamps only in the Table view and not in the Graph view. Added a new column ‘Violation’ in the Actual Table view. This new column displays the invalid timestamps the vessel visit has. If the value in the column does not fit the column width, ellipsis and info icon are displayed. Hovering over the info icon displays the entire content.
-In the Table view, users can perform all the regular operations for the vessel visits described above.
Note:
Even if this new setting is enabled, ETA and ETD values are mandatory so that the vessel visits created in N4 are displayed in BWM. Also, vessel visits with invalid timestamps created when this setting is disabled will not be displayed in BWM when the setting is enabled.
After one hour of inactivity (idle/no mouse movement), BWM now displays a pop-up to confirm if the user wants to keep BWM open. Depending on the user’s response, BWM either refreshes the screen or logs out the user.
The following improvements are made to the timeframe in the Settings under Berth Admin:
- ‘Number of weeks’ is replaced with ‘Number of days’
- New dropdown values:
Next 7 days
Next 14 days
Next 30 days
Next 60 days
Next 60 days + All Records in table
The Actuals and Proformas views load vessel visit data based on the value selected in the dropdown. The default value is Next 30 days.
Background:
There was only one check box for the service code, service direction, and voyage out in the Vessel Visit Box settings.
Improvement:
Added a separate check box for the service code in the vessel visit box settings so that the service code can now be displayed in the vessel visit box without displaying the service direction and the voyage out.
To provide improved synchronization between ABS and BWM, introduced a new configuration ignoreXpsUpdates in the XvelaVesselVisitBerthingOutbound code extension to control the XPS berthing updates reflecting in N4 and BWM.
By default this configuration is set to ‘true’ which ignores the XPS updates. For the XPS berthing updates to reflect in N4 and BWM, set this configuration to ‘false’.
Background:
In the previous release, a fix was provided so that when N4 sent an update for a vessel visit in the Cancelled phase, BWM ignored it if the vessel visit was not available in BWM.
Resolution:
Provided fix so that BWM now creates the vessel visit as ‘Cancelled’ when BWM receives a new vessel visit in the Cancelled phase from N4.
Background:
When you matched a regular vessel visit from N4 to the proforma, the values in the estimated move counts (Dicharges, Loads, and Restows) were not inherited from the proforma.
Resolution:
Provided fix so that the following happens:
-If any of the Estimates values from N4 is not zero, BWM uses the Estimates values from N4. For example, if Estimates in N4 are: Load = 2 Discharge = 0 Restow = 0, then BWM uses these values from N4.
-If all Estimates values from N4 are zero, the values in the estimated move counts (Dicharges, Loads, and Restows) are inherited from the proforma. For example, if Estimates in N4 are: Load = 0 Discharge = 0 Restow = 0, then BWM uses the values in the estimated move counts (Dicharges, Loads, and Restows) from the proforma.
Background:
You could not delete an existing line operator in the Edit Proforma and Copy Proforma modals.
Resolution:
Provided fix so that you can now remove a line operator in the Edit Proforma and Copy Proforma modals using the Minus icon.
Note:
The Minus icon to remove a line operator in the Edit Proforma and Copy Proforma modals is displayed only if there are no vessel visits linked to the proforma.
Background:
The value of the Country field from N4 was not synced with My Navis Account>Vessel Master Data>Ships and BWM vessel visit.
Resolution:
Introduced a new Country field in My Navis Account>Vessel Master Data>Ships so that the value from N4 will be synced with My Navis account and BWM when you create or update a vessel.
You can do bulk upload of the ship file in the terminal library to populate the value of the Country field from N4 to My Navis Account. To do bulk upload of the ship file,
1. Open N4 script runner and choose groovy.
2. Copy and paste the contents of XvelaVesselExporter groovy and click play.
3. Copy the ships and barges results into separate text files and save it as a .csv file. (Remove the ship and barge labels from the result). Here is a sample file content:
SHIP NAME,IMO,VESSEL CODE,CALL SIGN,FLAG,LOA,BRIDGE TO BOW
DETROIT EXPRESS,9610169,DEXPR,VRLX4,,228,
ASIATIC ISLAND,9366483,ISLAN,9V3933,,149,
4. Open terminal library (My terminals >Options >Bulk upload ships/Bulk upload barges) to upload the ships and barges csv files, respectively.
Once the bulk upload is done, any new update in the vessel visit will populate the value of the Country field to BWM - vessel visit floating inspector and table view.
Background:
From the berthing view, when some menu tabs or options were selected, the berthing view was refreshed and returned to the current timeframe.
Resolution:
Provided fix so that the berthing view remains in the currently selected timeframe when you select some menu tabs or options.
Delete All Vessel Visit button in the Settings under Berth Admin will now be displayed based on the privilege ‘CLEANUP_VESSEL_VISITS’. Clicking on the Delete All Vessel Visit button will delete all the vessel visits for the terminal in BWM and will not affect N4. It is used for cleanup purposes. The Delete All Vessel Visit button is available only in the Sandbox environment and will not be applicable in the Production environment.
Background:
BWM did not display Print button for external users.
Resolution:
Print button is now enabled for external users.
Background:
For users with N4 version below 3.7, Bollards values in N4 and BWM were not in sync.
Resolution:
Provided fix in the two code extensions XvelaUtils and XvelaVesselVisitBerthingOutbound so that they are now compatible across different N4 versions. Please do SNX import and recompile all the xvela code extensions. With this fix,
-Any berthing update from N4/XPS will now reach BWM.
-N4 now records UPDATE_BERTHING followed by SEND_VV_TO_XVELA events in the vessel visit history events.
A new release of BWM is made available in the sandbox. Please do a hard refresh in the browser and verify the changes. Please contact the Navis support team if you have any queries.
Added the Cranes and Berth Limitations functionality in BWM. This new functionality is enabled for users with the privilege ‘Manage Crane and Berth Limitations’ assigned in their role.
At the terminal level, under Sections/Berths, added the following:
Depth of the existing bollards
Automatic Mooring Bollards – you can give the number of automatic mooring bollards, name of each bollard, and the distance of each bollard
Cold Ironing Bollards – you can give the number of cold ironing bollards, name of each bollard, and the distance of each bollard
Also at the terminal level, under Cranes, you can now configure which type of vessel the crane can handle by marking the checkbox. You can indicate whether the crane is:
1. Barge compatible
2. Feeder compatible
3. Deepsea compatible
4. Megavessel compatible (Megavessel is Deepsea with LOA > 350 meters)
BWM displays the newly added Automatic Mooring Bollards and Cold Ironing Bollards in the UI if you enable the newly added field ‘Show Berth Constraints’ under settings. In the Actuals Graph view, BWM displays Automatic Mooring bollards in orange color and the Cold Ironing bollards in blue color.
Introduced a new validation to compare the draft of the vessel with the depth of the bollard. You must define the Under Keel Clearance (UKC) under settings. UKC is the distance between the draft of the vessel and the depth of the berth. The difference between bollard depth and draft should be greater than the defined UKC in the settings. BWM displays an alert icon on the vessel if the vessel does not match the draft/depth criteria. For example, BWM displays an alert to say that Bollard 12 has a depth of 3.2 meter and arrival fore draft will be 3.1.
BWM now validates if the assigned crane to the vessel is compatible with the vessel classification. For example, if Vessel A is a deepsea vessel and you assigned QC1 to Vessel A but QC1 is not deepsea compatible, then BWM displays an alert on Vessel visit A to say that Vessel is deepsea and QC1 assigned is not configured as suitable for this classification.
Training and help sections are now available in the BWM app. Users can find these new sections in the Administration module>Username. Users can click on the Stack Academy Training option and the users will be directed to the BWM training page. Below the Stack Academy Training, users can click on the Help option and the users will be directed to an external Salesforce page containing the latest BWM documents, release notes and groovies.
Users can now view the activity logs of event updates related to ETA, ETB and Pilot on board time from Third party integration services like DCSA/ Awake AI in the activity logs section. If the user wants to view Pilot on board time related logs in the activity
logs section, the user must have the privilege 'Manage Pilot On board time' assigned to his role.
Introduced a new privilege ‘MANAGE_TERMINAL_COMMENTS’ to manage terminal comments. Now, users who have the privilege ‘MANAGE_BERTH_SHIP_CALLS’ or ‘MANAGE_TERMINAL_COMMENTS’ can edit/delete/create terminal comments.
Background:
The vessel visit floating inspector did not reflect the updated crane intensity values from N4.
Resolution:
Provided fix so that the vessel visit floating inspector reflects the updated crane intensity values whenever the said values are changed in N4.
Background:
When logged in as a user with assigned external user role for a particular line operator, vessel visits with an ETA greater than 2 weeks were previously not visible in BWM.
Resolution:
Provided fix so that vessel visit data is displayed for external users according to the ‘Number of Weeks’ setting selected by the berth admin in the Berth Admin > Settings page.
Background:
When the meter fore is entered, the meter aft value should automatically be calculated based on the vessel length. Similarly, when meter aft is given, meter fore should automatically be calculated. There were some errors in the said calculations when the bollard meter fore/end is at the corner of the section.
Resolution:
Provided fix so that the meter aft or the meter fore value is calculated correctly.
Background:
BWM displayed different ETS field values in the Floating Vessel Visit Inspector and the Vessel Visit Inspector modal.
Resolution:
Provided fix so that BWM displays the same ETS field value at both places for the same vessel visit.
Background:
Vessel comments were duplicated after cancelling and restoring a vessel visit.
Resolution:
Provided fix so that restoring a vessel visit does not result to duplicated vessel comments.
Background:
Vessel comments were duplicated after associating a vessel visit from N4 in the Main Grid view.
Resolution:
Provided fix so that associating a vessel visit from N4 in the Main Grid view does not result to duplicated vessel comments.
Background:
When a vessel visit was deleted from the N4 column in BWM, the berthing details of the vessel were deleted in N4.
Resolution:
Provided fix so that BWM will no longer send updates to N4 when a vessel visit is deleted in BWM. This ensures that all information, including berthing and operational times, will be kept in N4.
Background:
Changes made to Arrival forward draft, Arrival aft draft, Departure forward draft, and Departure aft draft values in BWM were not communicated to N4.
Resolution:
A groovy fix (v1.16.0) has been provided to ensure that these values are now sent to N4.
Please redeploy the following code extns by doing an snx import
The following changes have been done to improve the UI performance:
1. Native scrollbar has been implemented.
2. Crane panel does not redraw the berth drawing.
3. You can now select the data to be loaded in the Admin Settings.
a. If you select 3,5,7 weeks, BWM loads the vessel visit data whose ETB and ETD is between 3/5/7 weeks respectively in all the table and graph views.
b. If you select All, BWM loads all the data including the past data which has null ATD (not omitted) and the future vessel visits in the Actual table view. All the other graph views draw 7 weeks of data only as maximum.
4. In the Zoom In and Zoom Out,
a. 3h and 1h – can load only 3 weeks of data
b. 6h and 12h – can load data based on the Admin Settings
Note: This is an optional deployment.
Added a new boolean flag in the XvelaUtils groovy - BOLLARD_OFFSETS_SCALE_IN_CM. You can set this boolean to false so that N4 stores the Bollard Offset value in meter and does not convert the value when sending to BWM. By default, this boolean is true. This means that by default, N4 maintains the Bollard Offset value in cm and converts the value to meter when sending to BWM.
Please redeploy the following code extns by doing an snx import
Background:
When you cancelled a vessel visit in N4, BWM created a new vessel visit for it in the app. The issue occurred because when a vessel visit was initially created in N4 with incorrect data, such as missing ETB/ETD, BWM validated and rejected the vessel visit. This vessel visit was later updated with the required data and was then cancelled in N4. BWM checked its database for the vessel visit. Since BWM previously rejected the vessel visit, BWM created a new vessel visit in the Created phase.
Resolution:
Provided fix so that BWM does not create a new vessel visit when N4 sends an update for a vessel visit in the Cancelled phase.
Background:
BWM did not display the vessel visits created in N4 even though the proforma auto matching was enabled. The issue occurred because the carrier service and other descriptions such as ETA and ETD were matching but the line operator used in the vessel visit did not match the ones in the proforma.
Resolution:
Provided fix so that if you enable the proforma auto matching, when a vessel visit is created in N4, BWM automatically matches the vessel visit to the proforma that has matching carrier service and line operator. Otherwise, BWM displays the vessel visit in the N4 column.
Background:
BWM was supposed to display the details of the vessel visit of the carriers and services that a user is allowed to view. When a user who had restricted access to a specific liner logged in, BWM displayed a blank box for the vessel visit of that liner. However, when a user who had restricted access to a specific liner logged in and there was a live update from N4 or from other users, the user could view the vessel visit with all the details that the user was not supposed to see.
Resolution:
Provided fix so that when a user who has restricted access to a specific liner is logged in and there is a live update from N4 or from other users, BWM only updates the vessel visit of the carriers and services that the user is allowed to view. BWM keeps the blank boxes as they are even if there are live updates for those vessel visits (blank boxes).
A new release of BWM is made available in production. Please do a hard refresh and reach out to Navis support for any issues
New groovy xml file version 1.14 is available in this link. You must import the SNX in the file, select all the xvela code extensions and compile.
Another groovy DeleteQrtzFiredTriggerForGroovyJobs is available in the same link. Unzip the folder and search for the filename DeleteQrtzFiredTriggerForGroovyJobs. You can use this groovy in case you observe the job XVELA_BWM_DME_JOB or LIVE_ETC_JOB or XVELA_CARGO_MOVES_JOB is getting stuck or you are unable to reschedule the job. Please follow the steps below to use this groovy:
Precheck
1. Open the Script Runner in N4 HTML UI.
2. Select HQL Radio button and run the script. Select job from FiredTrigger job where job.qrtzFTTriggerName like 'XVELA%' or job.qrtzFTTriggerName like 'LIVE_ETC%'.
You will find the Xvela Fired triggers as shown in the screenshot. If the trigger is not going away or it the trigger is stuck, you will find that the firedTime will not change even if you execute the script and the process will display 'EXECUTING' always.
Fixing the issue
Follow the step by step process to delete the fired trigger using a utility groovy script and reschedule the stuck job:
1. For example CARGO_MOVES_JOB is stuck. Go to Groovy jobs in N4. Select CARGO_MOVES_JOB.
2. Double click on the job in edit mode and select the execution logs row which shows job 'in progress' for a long time and is not completing.
3. Delete it by pressing '-' button on the right.
4. Open the Background Jobs view in N4 and halt the job that is stuck.
5. Go back to GroovyJobs and unschedule the job. You should now be able to unschedule it.
6. In case you cannot unschedule the job, try to delete the Background job and unschedule it again.
7. The job is unscheduled.
8. Open the Script Runner in N4 and select the groovy option in Radio button.
9. Execute the attached script as it is. This helps us in clearing the FiredTrigger of Quartz Job scheduler.
Refer to the screenshot below for the execution of the script.
9.1. If trigger is stuck, it gets deleted and display an OK response when the script has done its work.
9.2. If trigger is not stuck, it displays an ERROR. This is normal and means that there’s is nothing to be cleared.
10. Try to go back to the Groovy jobs and execute the jobs once (manually) and check if the jobs have spun and scheduled again.
11. Schedule the job. You will observe the job will start getting scheduled as per the cron.
Note:
This is a short term solution or a mitigation script and should be used/applied only when the quartz scheduler is not able to schedule jobs/Bwm jobs are stuck. This requires further more investigation from the N4 Team to come up with a long term solution which would probably be handled by quartz framework.
Enable com.xvela.n4groovy in the Logging Package as shown below:
Please update the XVELA_BWM_DME_JOB to use this cron expression: 0/10 0/1 * 1/1 * ? *
.png)
Once Saved, please schedule the job.
Provided general UI fixes so that BWM app works as expected.
Provided stability fix in the BWM UI.
Provided fix for the Live ETC updates from N4 to BWM.
Provided fix so that when the Actual Time of Arrival is updated in BWM, the Actual Time of Arrival in N4 is also updated. Likewise, when the Actual Time of Berthing is updated in BWM, the Actual Time of Berthing in N4 is updated as well.
Highlights
BWM has been integrated with the My Navis Account and provides the following additional capabilities through the My Navis Account:
1. Multi Factor Authentication and Single Sign On
2. Terminal’s complete control over the terminal’s reference data - Ships, Carriers and Carrier services
3. Effective and centralized user management for Navis apps
4. Oauth2 Secured integration with N4 and external apps
Note: All the user data and reference data of the terminal has been migrated to the My Navis Account and any further updates to those data should be done in the My Navis Account page. For ships, only terminal specific data are migrated and unused ships from the old ship library are not included for the terminal. Please report to Navis for any missing data.
Important
For the N4-BWM integration to work, you must update the N4 General Reference by referring to the API key management topic in the Migrated Functionalities to My Navis Account section of this release notes. You also need to reapply the groovy xml file that you can find in this link. You must import the SNX in the file, select all the xvela code extensions and compile.
Sections
1. Changes in the UI
2. Migrated Functionalities to My Navis Account
3. Other Update
CHANGES IN THE UI
1. Redirect you to the My Navis Account if you have not registered or logged into the My Navis Account earlier.
2. Authenticate you via Single sign on (and not prompt you to log in) if you have logged into the My Navis Account
1. Berth Window Management
2. BWM Scenarios
3. Terminal Library
4. Administration
5. Company Service
Administration module
Menu items under the Administration module:
1. Org Settings
2. EDI
MIGRATED FUNCTIONALITIES TO THE MY NAVIS ACCOUNT (NAVIS COMPANY SERVICE/NCS)
1. Terminal creation (for Navis Admin)
2. User and role management
3. Reference data management
4. API key management
You can see the migrated functionalities by clicking on the BWM waffle menu>Company Service.
Terminal creation (for Navis Admin)
User and role management
The following are the privileges/features that can be assigned to the BWM users by the Navis Admin.
1. Click on the INVITE MEMBER button
2. Enter the email address of the new member or click on the hamburger + in the upper right corner of the New Member Invitation form to display the Bulk Import Members form.
3. Select role from the dropdown
4. Check the Send invitation email and click on the INVITE button
Note: The user details and email address should be based on the email domains provided in the organization.
Note: You must create external users like how you create direct terminal users. The only difference is that you assign a limited set of privileges to the external users. The external users must have the new privilege ‘External User Role’. The terminal users must not have the privilege 'External User Role'.
Inviting members can be done in three ways:
1. Invite members through the invitation link
2. Invite guests through access code
3. Invite members through access link
Note: Please refer to the My Navis Account-Quick Start Guide for detailed information regarding inviting members.
Reference data management
Terminal users now have full control over the terminal’s reference data which includes ships, barges, carriers, and carrier services.
Take note of the following steps to create vessels and barges:
To create vessels,
5.a. Click on the IMO Number of the newly created vessel
5.b. Navigate to SHIP BASE DATA tab>Hull Details
5.c. Click on the EDIT button and enter the LOA value
5.d. Click on the SAVE button
To create barges,
7.a. Click on the Custom ID of the newly created ship
7.b. Navigate to SHIP BASE DATA>General
7.c. Select Barge under Ship Type
7.d. Navigate to Hull Details and enter the LOA value
7.e. Click on the SAVE button
Note: When you create a carrier, enter the Line Operator Id found in N4 Line Operators view in the Code field shown above.
API key management
Note: You must enter the API key in the Data Value 4 field in the N4 Edit General Reference Entry form. Please contact Navis for entries to the Data Value 2 (client ID) and Data Value 3 (client secret) fields.
Here’s a sample:
Other updates:
A new release of BWM is made available in production. Please do a hard refresh and reach out to Navis support for any issues.
The "Vesselvisit ID" column will be displayed in the "Columns to select" option in Tables. When selected, BWM displays vessel visit ID column in Table view.
Now when you select "Save template" option in print dialog box, BWM saves sections, vessel types and status as part of the template.
You can now view the total moves for each type in the Moves tab in the Vessel Visit Inspector. When you edit the value, the total will be computed according to the inputs. You can click on "Copy TOS values" button in the Moves tab to copy the values from TOS for estimation.
Optional: Introduced an option to encrypt the password in General References tab. Do SNX import of the XvelaRestOperations.xml
To encrypt the password in Data value 3 field in General References tab, follow the below steps:
A fix is provided so that when you select "No crane Info" in the print options, BWM application does not display the gangs count in the printed pdf.
