Utilize "Auto-update from itinerary" in Estimated Demurrage without enabling CFGEnableMultiEstDem

27 votes

A new Estimated Demurrage feature was released in December 2022 - "Automatically update the Estimated Demurrage form with linked itinerary data". This seems smart.

The problem is however that the feature is not possible to utilize unless this Config Flag is also enabled: CFGEnableMultiEstDem - "If enabled, along with CFGAllowEstLaytime, estimated demurrage in the Voyage Manager will be editable per-charterer and per-port".

The problem about enabling above flag is however that it entails added complexity if a voyage is not a multi-one i.e. if the voyage only contains a single charterer and/or cargo.

So, hereby suggest that the Auto-update feature is separated from the MultiEstDem feature. Meaning that the "Automatically update the Estimated Demurrage form with linked itinerary data" can be used by all clients

Under consideration demurrage Suggested by: Hafnia BA (23 Feb, '23) • Upvoted: 08 Mar, '23 • Comments: 1

Comments: 1

03 Mar, '23
Retno Muninggar
There is no downvote button to click on, so I will write my comment here. Estimating demurrage manually gives ops the chance to review the earnings of their voyage daily. The way we use IMOS now, we only captures estimate arrival and departure in each ports, so there will be plenty of miscalculation if we let IMOS automatically calculates demurrage.

I will have to downvote NO on this as the team I am in do have more complicated port stays.