Overview
You may want to use the Consolidated Laytime feature in the following scenarios:
You have multiple cargo handlings per port call (especially when activities overlap)
You want to manage all port activities for a single port call in a single list and apply specific cargoes to each activity in a single list.
Prerequisites
To use the consolidated laytime feature, enable the configuration flag CFGConsolidateLaytimeTabs.
When enabled, each port call will have a single tab in the laytime calculator that lists activities and deductions for all cargoes handled at that port. Cargo ID fields available in the activities and deductions grids indicate when a particular activity or deduction should only apply to some of the cargoes handled at that port. A blank Cargo ID field in these grids indicates that the activity or deduction applies to all cargoes handled at the port. You will have one Port Activities tab per Cargo handled at each port and one Port Activities tab per Port Call.
Usage
Link specific cargoes to port activities
In the Port Activities grid, use the Cargo ID field to indicate that a port activity is linked to a specific set of Cargoes handled at that port.
If you leave the Cargo ID field blank, port activities will apply to all cargoes handled at the port. This feature is helpful for splitting a single port call into multiple berth calls, where different cargoes are loaded at each berth.
Example 1
Half of the port activities at Berth 1 that only apply to Cargo 1. The other port activities are at Berth 2 and only apply to Cargo 2. Use the Cargo ID field to indicate which cargoes apply to each berth. This indication is critical for correctly calculating Used Time to calculate laytime.
Configuration for multiple laytime periods
Setup
If you create laytime calculations with multiple laytime periods, add the Laytime Commenced and Completed activities in Data Center > Port Activities. The activities must be entered in all caps with the activity type NM as shown in the following image.
Steps
By default, one Laytime Commence and Laytime Complete activity are imported from voyage port activities, and the cargo ID field is blank. In Example 1, Cargo 1 and Cargo 2 would share a laytime period.
To split out Cargo 2 to its own laytime period, remove it from the existing Laytime period by opening the Cargo ID dropdown on both activities and only selecting Cargo 1. A blank Cargo ID field indicates the activity is for all cargoes, effectively removing Cargo 2 in this case.
Using Laytime Commence/Laytime Complete activities
The Laytime Commence and Laytime Complete Port Activities are critical items to include for correct laytime calculations. The Cargo ID field logic applies to these activities similarly. Whether the configuration flag CFGConsolidateLaytimeTabs is enabled or disabled, the baseline for calculating laytime is subtracting the Laytime Commence date from the Laytime Complete date. Make sure to assign the correct Cargo IDs to each Laytime Commence/Complete activity to get this calculation correct.
When there is a need to split into multiple laytime periods (using the same example as in the Cargo ID field, with 2 cargoes handled at 2 berths), there is a process to follow. The steps are roughly: 1) by default, usually one laytime commence and complete activity are imported from the voyage port activities, and the Cargo ID field is blank. So in our example, this would mean both Cargos 1 and 2 share a laytime period. 2) In order to split Cargo 2 out to its own laytime period, first remove it from the existing Laytime Commence and Complete activities by opening the Cargo ID dropdown on both activities, and only selecting Cargo 1 (a reminder that “blank” Cargo ID field means “all cargoes”, so this is how you “remove” Cargo 2). 3) Make sure to do this in both Laytime Commence and Laytime Complete activities. 4) Now you can add new Laytime Commence and Complete activities representing the time used for Cargo 2, and select that cargo in the Cargo ID field.
Applying Deductions
Explain how deductions work (defaulting of Cargo ID field) - The Cargo ID field works for Deductions the same way it works for port activities - it is used to indicate which Cargo(s) this deduction applies to, and if the Cargo ID fields is blank, the deduction applies to all cargoes. Couple things to note 1) When adding a deduction, we do our best to figure out which cargo IDs should be added to this deduction, based on what laytime period the deduction falls in (continuing with our cargo 1 / cargo 2 example, if the deduction falls within the first laytime period we will default applicability to only Cargo 1. 2) If you leave the cargo id field blank (indicating “deduction applies to all cargoes”) but the deduction only occurs during the laytime period of some cargoes, it will only apply to those.
Configuring Cargo Handling Grid
Configurability of Cargo Handling grid (add/remove, re-arrange, freeze)
Do we already have general documentation around this? It is a platform paradigm, not something we implemented specifically in laytime. Same features available in Estimate Itin grid. Anyways - here are the deets
When the flag is on, users can make the following changes to the Cargo Handling (top) grid of the laytime calculator:
Re-arrange columns to any order you prefer
Show and hide columns at your discretion
“Pin” columns to the left / beginning fo the grid so that when you are side-scrolling the rest of the grid, you will always see the important info that gives you context to the rest of the fields (e.g. I know Exxon plans to pin Port name, berth name, function, cargo name, and cargo ID)
To pin, you have to drag the column header to the left, and hold it there for a couple seconds until you see a little pin icon, then drop it. Tbh it’s a little tricky.
Calculation Report Updates
Updates to Calculation Report - With the CFG enabled, the Calculation Report has been updated to a similar format as the calculation itself. Instead of a grid per cargo handling, there is instead a grid per port call. There’s an additional cargo handling grid (per portcall) to give additional contextual cargo info as well.
Exceptions/Limitations
Consolidated Laytime is not intended for use with “Continuous Laytime” checkbox.
This feature only applies to the “Deduction mode” of laytime calculations and will not make adjustments for “Time Counting” mode. You can use “Time Counting” mode, but the tabs will not be consolidated.
[Related Epics:
EN-23812 - Getting issue details... STATUS
EN-44896 - Getting issue details... STATUS
EN-45555 - Getting issue details... STATUS ]