|
ITEM
DATA NOTIFICATION v. 2.1
|
|
|
|
|
|
Problem
Statement |
|
|
The
current situation in the upstream supply chain of the CPG industry
is that all manufacturers and suppliers are faced with different
business
processes and data interchanges when they move into more integrated
relationships. Different business processes and approaches create a
barrier to
the scalability of integration efforts whilst also imposing many costs:
the time
and money spent making transactions; the delays caused by the need for
corrections; plus inevitable information gaps and misunderstandings.
Both parties should obtain benefits from integration, among them
reduced inventory and a reduction in re-work and waste.
One example is that suppliers should have better visibility of
forecasted production and can improve their reaction to changes.
A key part of this integration is the
alignment of master data between buyer and seller.
Item Master Data is a set of data, which
describes the specifications and structures of each item involved in
Supply
Chain Processes. Each set of data can uniquely be identified by a
Global Trade
Item Number (GTIN).
The
transaction can be established by either the manufacturer or the
supplier. Only
one party will initiate the transaction. Which of both parties
initiates the
transaction needs to be agreed upon in the Integration Agreement;
changes in
item master data need to be commonly agreed & realised by the
party
initially initiating the transaction, i.e. the message flow will only
be in one
direction in order to ensure data alignment.
Master
data will be aligned each time information changes or new information
is added.
There is no need for a response message during the alignment
of master data between buyer and seller.
|
|
|
The
"Master Data Alignment" building block has three elements |
|
|
- Identifying and clarifying,
between the two parties, the coding for items.
- Agreeing on the attributes to be
shared about each item for example specifications, logistical handling
information, packaging format.
- Ongoing alignment of the item and
attribute data so that suppliers and manufacturers are working off a
common and
current understanding of this important base information. One challenge
facing
all trading relationships is maintaining accuracy and the distribution
of base
item data given the rapid changes to specifications and logistics
information
that can arise.
|
|
|
Item information will be composed of “General
Item information” which is relationship independent and
“Specific Item
information” which is relationship dependent item data. |
|
|
General Item Information |
|
|
General item information allows
the
identification and clarification of general, i.e. relationship
independent item
coding between trading partners, the agreement on the attributes to be
shared
about each item as well as the alignment of item information between
trading
partners. |
|
|
Specific Item Information |
|
|
Specific
item information (relationship dependent) allows the identification and
clarification of relationship specific item coding between trading
partners,
the agreement on the attributes to be shared about each item as well as
the
alignment of item information between trading partners.
It
contains those relationship specific item related parts of the overall
(and
mostly paper based) Integration Agreement, which might change often and
therefore make sense to be exchanged electronically to ensure alignment
between
both parties while limiting manual effort. |
|
|
Objective |
|
|
To
supply the detail design of the (specific) business transaction needed
to meet
the requirements of the referenced BRAD(s).
|
|
|
Audience |
|
|
- CPG Manufacturers
- Material Suppliers
|
|
|
Business
Context
|
|
|
Industry:
CPG
Geopolitical: All
Product: CPG Direct Materials
Process: Align_Item
System
Capabilities: EAN.UCC
Official
Constraints: None
|
|
|
Business
Transaction View
|
|
|
 |
|
|
Business
Transaction Use Case
Diagram |
|
|
|
|
|
Use
Case
Description
|
|
|
| Use
Case ID: |
BCA-1 |
| Use
Case Name: |
|
| Use
Case Description: |
The data interchange for
Item Alignment includes
the item information messages. Item information can be composed of
“General
Item information” which is relationship independent and
“Specific Item
information” which is relationship dependent item data.
Manufacturer and supplier
will commonly agree on item information to be shared and drive the
process of
exchanging these data. While both parties need to agree on item master
data, it is understood that only one party, i.e. manufacturer or
supplier, will
send the item information messages and that the information flow will
be in one
direction only in order to ensure alignment |
| Actors
(Goal): |
Buyer:
to align item information with the seller.
Seller:
to align item information with the buyer.
Sender: to send the item information to the receiver.
Sender could be buyer or seller.
Receiver:
to receive the item information. The receiver could be the buyer or
seller |
| Preconditions:
|
INTEGRATION
AGREEMENT IS IN PLACE
ITEM
DATA ARE ASSEMBLED AND AGREED |
| Postconditions:
|
ITEM DATA IS ALIGNED |
| Scenario:
|
Begins when the
sender generates the item information
Continues
with...
| Step # |
Actor |
Activity Step
|
| 1 |
Sender |
Sends the Item Data
Notification |
| 2 |
Receiver |
Receives the Item Data
Notification |
| 3 |
Receiver |
Integrates item information
into own systems |
Ends
when the receiver has integrated the item information
in own
systems.
|
Alternative
Scenario:
|
N/A
|
Related
Requirements:
|
N/A
|
Related
Rules:
|
N/A
|
|
|
|
Business
Transaction Activity Diagram |
|
|
Not available
|
|
|
|
|
|
Business
Transaction Sequence Diagram |
|
|
Not available |
|
|
Code Lists |
|
|
Test Data |
|
|
Glossary
of Terms |
|
|
|
|
|
TOP
|
|
|
|
|
