Migration to Cordel Cloud (NO)

This initiative is part of the Cordel Cloud journey. Started with Cordel 2.0 (DD-177)

What remains for Cordel 3.0 cloud solution, is a major redesign or all input/output interfaces to allow communication with an external hosted solution, rather than internal servers.

This will require development of new interfaces to transfer core data between Vivaldi and Cordel cloud solution.

Output from Vivaldi would probably need to be streamed via Kafka, to maintain updated product, vendor and core price information in Cordel 3.0. Kafka needs to be able to produce product and price files in EFO/NELFO 4.0 layout, which is used for nearly all norwegian customers, and also used for import to Cordel.

New offers calculated in Cordel 3.0 needs a broker or new API (in Ahlsell Azure solution) to allow insert/update of the related offer in Vivaldi, and retrieval of updated price information unique for the project / customer from Vivaldi back into Cordel.

So far the maturity of Cordel 3.0 solution is not optimal, as assessed by the Tilbudsteam members who participated in the PoC / test for Cordel 3.0 in 2024. The solution is built completely from scratch on modern components, but the web based client and modules used in the gui has several changes that was not optimal regarding speed and usability. The new web based solution would as such require more time to do the same amount of work, compared to Cordel 1.9/2.0.