Before
Allocation ran on extracts whose site and product codes differed per region; a re-organisation of the sales regions took a quarter to reach the allocation logic.
A telecom company runs a global supply chain data hub for allocation planning and demand prioritisation on Lima; the sites, products and customer hierarchies the allocation uses are golden records with versions.
Allocation ran on extracts whose site and product codes differed per region; a re-organisation of the sales regions took a quarter to reach the allocation logic.
Golden sites with their codes per system, golden products with the planning hierarchy, golden customers in a versioned sales hierarchy; allocation weights kept as master data on the hierarchy nodes; the pivot with data entry for allocation targets.
Planners enter allocation targets at a region and the platform disaggregates by the weights; a reorganisation is a hierarchy version with an effective date.
anonymised engagement
one hub for allocation planning.
anonymised engagementsales hierarchy changes as versions with dates.
anonymised engagementallocation keys governed as master data.
anonymised engagementSlot for the customer's own words: supplied and approved by the reference contact before publication. The story above is written in Lima's voice from the engagement material; the customer's feedback goes here in theirs.
Put the allocation weights on the hierarchy as versioned attributes on day one, so the entry grid and the audit trail cover them.
Under NDA, with the account owner's approval, we arrange a conversation with a customer whose domains and systems resemble yours.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.