Outcomes A $20B telecom leader

Global customer and product codes maintained across three divisions, as one golden set

A telecom leader with three main business divisions and supply chain data spread across many systems maintains its global customer and product codes on Lima, feeding product activation, forecasting and demand planning.

SOURCESGOLDEN RECORDFEEDSDivision A systemsDivision B systemsDivision C systemsProduct activationForecastingDemand planningCustomer and product codesOne golden set
One code set
Three divisions maintain one golden set of customer and product codes.
anonymised engagement
3 processes fed
Product activation, forecasting and demand planning read the released codes.
anonymised engagement
10 GB a day
The estate processes 10 GB of data a day.
anonymised engagement
01
The situation

Before

Each division kept its own customer and product codes, and every planning and activation process reconciled them first. A new product code reached the three systems on three dates.

02
What was built

The domains

Lima consolidated the supply chain data of the three divisions and published one golden customer set and one golden product set, each with a versioned hierarchy per division and a crosswalk to every system's local code. A collaborative SmartApp routes a new or changed code through the owners before release.

03
How it runs

Day to day

A request for a new product code opens at the requesting division, passes the duplicate check against every division's codes, fills its views function by function, and is released to the systems through their interfaces. Forecasting and demand planning read the released codes the same day.

Domains in this storyCatalogue entries that match the domains in this story.
Results

Each with its evidence

anonymised engagement

One code set

Three divisions maintain one golden set of customer and product codes.

anonymised engagement

3 processes fed

Product activation, forecasting and demand planning read the released codes.

anonymised engagement

10 GB a day

The estate processes 10 GB of data a day.

anonymised engagement
In the customer's words

Slot 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.

named reference · pending approval

What we would do the same today

Model the hierarchy per division first and let the duplicate check run on live codes from all three before any screen is drawn.

Ask for a reference conversation

Under NDA, with the account owner's approval, we arrange a conversation with a customer whose domains and systems resemble yours.

See your first domain built on your data

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.