Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 4

RATE CLOUD Process Refresher

Discussion Points:
OF Update:

 Alternative surcharge code for GRI is GRA.


 As per Robert latest confirmation he is the first contact point for Asia contracts.
 As per latest sprint in FOCIS transit days listing in rate search.
 In catapult template need to create column name transit days to update transit time.
 While working on US files, validate twice before sending confirmation to route manager, especially Codes and
Trades(Based on trades only surcharges we are updating).
 Don't miss to adhere the HWS surcharge tons detail while updating either in Rates or eft sheet.
 Henceforth update only MFR value. If BAF value is included in contract-Just ignore (MSC Carrier).
 Seaquest rate structure need to check and validate for surcharge incase mismatch please clarify with RM
 SEAL Surcharge Changed from Carrier to Origin in Charge Group, as per NPC-Spain RM confirmation.
 Contract Number is mandatory for all the trades , If not available address to Robert Holderf and then Hold
the request until we get confirmation.
 We need to update contract number in column name "Contract rate id"
 Check twice while consolidating the RPA File. (Whether its Blank or Special characters just remove and run
the same)
 Connections updation mandatory for every contracts
 While spot-check rates need to verify under Carrier Contract Details
 In case contract receiving without any variation from Global and Local follow either one which received
initially

2
 Only following “O-D”, “DO”,”O”,”D” Arbitrary Construct options are allowed.
 Here after OBS need to follow. Hence, you can simply disregard the remark “BAF included” if it’s listed in any
of the ONE FAK contracts
 Terminal charges need to follow as Carrier "TERM" for carrier CMA-CGM under Canada exports.
 LSS20 will consider as Fuel charge and will ignore to update BAF as not mandatory for CMA-CGM carrier.
 Further to our discussion with Paddy , Kindly stop using the values -1, -2 & -3 in the Base rates of “GSSC OF
FCL P2P“ templates:
Since, surcharge logic getting applied for the following values in base rate(20, 40 & 40HC)
1. (-1) included
2. (-2)subject to
3. (-3) current.

Also don’t use the above mentioned rates(-1,-2,-3) in origin & destination arbitrary base rates. Instead please
use the value “ 1 “.

Air Update:
 BSC has been published for Q1 and RC team has achieved their target for Q1 same like Q4.
 As per the updates received from Robert on ONEY Contract update on OBS, we’ve modified in Rate Cloud to the
respective contract.
 For ONEY Contract, for Bunker Surcharges, we need to consider only the Charge “OBS” and not “BAF” – which
confirmed by the Route Manager “Robert”.
 Deactivated BD Air Local Charges as per the confirmation received from Niklaus Wasem. FCL/LCL Local Charges
are remains in activated status.
 Pickup charge setup deactivated for Poland as per instruction received from Niklaus.

You might also like