Outcomes A $20B telecom leader

Global customer and product codes maintained across three divisions, in one collaborative app

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, supporting product activation, forecasting and demand planning.

3
business divisions on one code set
anonymised engagement
10 GB/day
of data processed
anonymised engagement
$20B
revenue class of the customer
anonymised engagement
3
processes fed: product activation, forecasting, demand planning
anonymised engagement
The situation

Before

Each division kept its own customer and product codes, and every planning and activation process had to reconcile them first.

What was built

The apps

Lima consolidated the global supply chain data and put the code maintenance on it as a collaborative app: a hierarchy per division with the functions that own each part of a code, screens per level, and criteria that route a new or changed code through the owners before it is released to every system that uses it.

Catalogue entries that match the apps in this story.

How it runs

Day to day

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

Results

Each with its evidence

anonymised engagement

One code set

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

anonymised engagement

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

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 first, one per division, 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 processes resemble yours.