Consumer Landscape

Applications	Point of Contacts
GCSS	steve.handel@maersk.com
AFLS - Athena	lavanya.m@maersk.com
CW1	petra.schopman@maersk.com k.c.tong@maersk.com
OIPC & Pricing	partha.n@maersk.com, nino.stokbro.ag@lns.maersk.com sambit.tripathy@lns.maersk.com
SCP	vaibhav.h.ghag1@lns.maersk.com
NFTP	gurminder.sahota@maersk.com; sunil.kumar.musham@maersk.com b.gandhi@maersk.com
Procurement	laurence.reddy@maersk.com

Existing Landscape

Most of the applications are independently working as on today with their local databases.

To Be State (TBC)

AFLS Charge code creation process

Application Tool called CDC is used to Auto sync Charge codes created in AFLS to Athena. In GCSS a ticket would be raised to manually sync the charge codes.

Key Known Challenges with upstream/ downstream systems

Current Challenges
Approximately two weeks of Timeframe for charge codes to get reflected in multiple applications once created.Surcharges and Contractual charges manually applied for the selected product as compared to get charges automaticallywhen rebuilding there are chances of adding or removing charges which is not in relation to earlier configuration madeTerms and conditions are triggered through configuration and due to delta there is likely hood there is missing complete coverage.when service delivery team executes the service, they need to know what is charge code to be applied and system should auto fetch the same based on product to price linkageToday charge code creation process and product definition process are not in sync - without even defining the service, Charge code requests are getting created on first attemptLack of control on existing Material codes including Inactivation of the codes.Multiple locations for creation/amendments/deactivationInability to control / govern usage of deactivated codes

Current Challenges

Approximately two weeks of Timeframe for charge codes to get reflected in multiple applications once created.Surcharges and Contractual charges manually applied for the selected product as compared to get charges automaticallywhen rebuilding there are chances of adding or removing charges which is not in relation to earlier configuration madeTerms and conditions are triggered through configuration and due to delta there is likely hood there is missing complete coverage.when service delivery team executes the service, they need to know what is charge code to be applied and system should auto fetch the same based on product to price linkageToday charge code creation process and product definition process are not in sync - without even defining the service, Charge code requests are getting created on first attemptLack of control on existing Material codes including Inactivation of the codes.Multiple locations for creation/amendments/deactivationInability to control / govern usage of deactivated codes

Was this page helpful?