Title: DATA ACCURACY
1DATA ACCURACY
- GlaxoSmithKline
- Consumer Healthcare
- Lorraine Learish
2History of Events
- GlaxoSmithKline began our data synchronization
initiative approximately 4 years ago - Created a Cross Functional Team with executive
sponsorship to identify overall requirements. - Worked closely with key customers.
- Identified all of the attributes required
- Mandatory
- Customer Specific
- Created a Database that tracked attributes, what
was available, what was missing and functional
area responsible.
3History of Events
- Gaps Identified
- No method/system to manage ALL GDSN data or
messages - Information that did not live in any system
- Inconsistent GTIN Allocation Rules
- Inconsistent measurement of products
- Lack of clearly defined processes
- No formal training for existing processes
4History of Events
- Closing the Gaps
- Educated all functional areas on GDSN
requirements. - Pursued missing attribute information
- Initiated extensive data cleansing efforts.
- Implemented CPIM solution to create one version
of truth.
5Key Initiatives
- Education
- Constant approach to build awareness.
- Initiated ongoing training for every department
involved in the creation and maintenance of the
master data. - Encouraged each area to create SOPs and enforce
accountability with data accuracy.
6Key Initiatives
- GTIN ALLOCATION
- Set a standardized structure for all GTINs
- Created tools to help decision makers with
understanding the GTIN Rules - Biggest challenge is gaining support for NEW GTIN
for changes in dimension, content count, weight
-/ 20 - Created SOP and SOG outlining the rules
- Trained Marketing Sales associates on
requirements and risk of non-compliance.
7GTIN Allocation
36 Units in a case
24 Units in a case
12 Units in a case
1030766074670C
Retail unit
SKU 074670
0030766074670C
THE SKU IS OUR INVENTORY NUMBER
8GTIN Allocation
Marketing Assumption Goodys change is lt20
9GTIN Allocation
Reality Goodys change is gt20
Width/Depth/Height must be as oriented on the
retail shelf
10Key Initiatives
- Extensive Data Cleansing
- Audited all technical attributes for ALL open
stock items - Technicians were not measuring product as it
appears on the shelf. - Length, Width, Depth transposed.
- Inner Pack quantity and units were
mis-interpreted. - A concise SOP and SOG were written on proper
measurement techniques - Data Synchronization Coordinator confirms
accuracy on all changes prior to communication. - Currently do NOT have a tolerance level set,
strive for 100 accuracy.
11Product Change ExampleMultiple Related Issues
Super Poligrip Extra Care 2.2 oz (05876n)
1. W/D/H orientation not consistent
Technical Information Form (05876A)
System Header Item 05876
System Header Item 05876A
12Product Change ExampleMultiple Related Issues
Super Poligrip Extra Care 2.2 oz (05876n)
2. System width is not true shelf width
Technical Information Form (05876A)
System Header Item 05876
System Header Item 05876A
13Product Change ExampleMultiple Related Issues
Super Poligrip Extra Care 2.2 oz (05876n)
3. Absolute values change (gt ¼)
Technical Information Form (05876A)
6.534 vrs 6.850
System Header Item 05876
System Header Item 05876A
Some retailers are currently checking supplier
data for gt ¼ variances
14Product Change ExampleMultiple Related Issues
Super Poligrip Extra Care 2.2 oz (05876n)
4. Appears that new DCS values are either
estimates or grossly rounded
Technical Information Form (05876A)
System Header Item 05876
System Header Item 05876A
15Key Initiatives
- CPIM
- Consolidates GSK Data
- Validates data against GDSN requirements.
- Entry Point for data with no home
- Manages Complex Customer-Item Relationship
- Manages Synchronization of messages with Data
Pools and Customers - Insulates GSK from Changing Data Sync. Landscape
16Lessons Learned
- Manual cleansing of key attributes should be
performed prior to systematic synchronization,
especially on GTINs. - Both companies need to stay consistently engaged
during implementation phase. - Critical to implement consistent measurement
standards, focus on data QUALITY not quantity.
17Lessons Learned
- Conversion to 14 digit case/UPC is critical for
effective synchronization. - Retail UPCs can tie to multiple Case GTINs.
- Our strategy is to convert retailers to 14 digit
case ordering. - Compliance with GDSN standards is critical.
Validation rules will prevent synchronization on
changes. -
18Lessons Learned
- Determining best timing to communicate effective
dates and understanding how retailers will manage
within their systems. - As new attributes are added to the data model all
synced customers will receive a change
notification. Suppliers should notify retailers
when a large change is occurring to discuss
timing and best approach. - -- i.e. conversion from UDEX to GPC