Data Cleansing and Internal Synchronization

1
Data Cleansing and Internal Synchronization

• Henry C. Co
• Technology and Operations Management,
• California Polytechnic and State University

Source EXTOL, UCCnet One Version of Truth,
http//hosteddocs.ittoolbox.com/JO021805.pdf
2
GDSN

• See video on Global Data Synchronization Network

3
GDSN

• UCCnet standards for trading partners to exchange
  information on
• Product data
• Business location
• Pricing
• Others
• Purpose One Version of Truth (OVoT) for
  fundamental trade information
• Benefits reduced shipping errors, returns,
  charge-backs, out-of-stock conditions, error
  corrections, and other problems that costs time
  and money and erode margin.

0.1 of revenue saved by data synchronization
2-3 saved with CPFR.
A.T. Kearney
4
GDSN Business Flow
5

• GDSN
• Enables suppliers to REGISTER trade items,
  PUBLISH detailed information about items they
  sell, WITHDRAW obsolete items, RETRIEVE
  confirmations and notifications from trading
  partners.
• Enables buyers to SUBSCRIBE to items of interest,
  REQUEST for trade item publications, and RESPOND
  to supplier publications.

6
Enables suppliers to REGISTER trade items,
PUBLISH detailed information about items they
sell, WITHDRAW obsolete items, RETRIEVE
confirmations and notifications from trading
partners. Enables buyers to SUBSCRIBE to items
of interest, REQUEST for trade item publications,
and RESPOND to supplier publications.
7
Building Blocks

• Common Data Standards
• Standards for Information Representation
• GDSN
• AS2 Communication Standard

8
Building Blocks

• Common Data Standards GTIN, GLN, etc. defined
  by the GSMP of GS1 (formerly EAN/UCC)
• Standards for Information Representation
  EAN.UCC XML message standard for sending and
  receiving XML messages across the Internet-based
  GDSN
• GDSN (GDS Registry and data pools) for companies
  to register, publish, query and perform other
  operations on trade items.
• AS2 Communication Standard provides transport
  services to send messages into and across the
  GDSN.

9
Data Synchronization
10
(No Transcript)
11
How?

• Data Cleansing
• Internal Synchronization

12
Data Cleansing

• Verify and Augment source data
• Verify with recorded information by physically
  measuring dimension, weight, packaging and other
  item attributes
• Augment data not generated/maintained by the
  back-office systems (ERP, WMS, CRM etc.).
• Validate source data to conform to EAN.UCC XMS
  and GSMP standards for synchronization.
• Reconcile source data
• Source data must be internally consistent across
  engineering, manufacturing, sales and
  distribution.
• e.g., data describing a new engineering change or
  a packaging change must be reflected in the
  description of a currently sold product.

13
Internal Data Synchronization

• COMPLETE, ACCURATE data that is CONSISTENT across
  enterprise application systems (the back-office
  systems that created the source data).
• Data created by engineering, manufacturing,
  packing, warehouse management, marketing, sales,
  order management, shipping, etc.
• ENSURE that data in ERP, WMS, CRM and other
  applications are CONSISTENT before attempting to
  do external data synchronization.

14
Internal Synchronization

• See Figure in next slide.
• Back-office systems generate data
• Data is extracted, transformed, consolidated and
  loaded onto a local trade item catalog
• Customers responses are integrated onto the
  local trade item catalog
• Use internally synchronized data in
  e-collaborations processes (EDI, VMI, CPFR,
  Outsourcing, Private labeling).

15
(No Transcript)
16
Local Trade Item Catalog

• Consolidation
• Augmentation
• Validation
• Isolation
• Workflow Management

17
(No Transcript)
18

• Data consolidation Source data exists in
  different back-office systems. The local catalog
  consolidates these data into a single location,
  thus ensuring OVoT.
• Data augmentation The local catalog provides a
  place to put data needed for e-collaboration but
  not generated/maintained by the back-office
  systems.

19

• Data Validation Back-office systems may not
  comply with EAN.UCC XML and GSMP standards for
  synchronization. The local catalog enforces data
  validity by implementing a schema that enforces
  synchronization specific domain integrity and
  referential integrity rules.
• Data Isolation
• Data not needed for e-collaboration (private and
  confidential data) are not in the local catalog.
• Data not ready for synchronization are not in the
  local catalog (thus preventing inconsistencies).

20

• Workflow Management
• Back-end application systems maintain redundant
  trade item attributes.
• e.g., core product metrics may be maintained in a
  manufacturing system, packaging data in a
  warehouse management or distribution system,
  pricing data in a CRM system.
• It is necessary to reconcile copies of trade item
  data that are maintained in many places.
• Local catalog provides a place to store
• Data specifically for global data
  synchronization.
• Synchronization status and history information
  for each trade item.

21
(No Transcript)