|
RETAIL EVENT v. 2.0.2 |
|
|
|
|
|
Problem
Statement |
|
|
The Retail Event Message Business Requirements
Document defines the business need, lifecycle,
structure and content of messages that communicate information about retail
events (such as promotions, product introductions, community or environmental
events) that affect supply or demand. These messages are intended to replace
the existing EAN.UCC XML Event message
Promotions and other retail events
have a major impact on sales volume in the retail channel, at times generating
many months’ worth of sales for a product in a single week. Such major swings
in demand can result in out-of-stock situations, high logistics costs, and
large amounts of excess inventory if they are not planned and executed well.
Understandably, retail events are
also a major focus of retailer/manufacturer collaboration initiatives such as
Collaborative Planning, Forecasting and Replenishment (CPFR®). To be successful, both
parties need a clear view of upcoming events, with agreed timing, terms and
volume estimates. They also need to be alerted to any changes in promotion plans
or product availability as quickly as possible
CPFR® is a Registered Trademark of the Voluntary Interindustry
Commerce Standards (VICS) Association.
|
|
|
Objective |
|
|
To supply the detail design
of the Forecasts business transaction needed to meet the requirements of the
referenced BRAD(s).
|
|
|
Audience |
|
|
The audience of this standard is any
participant in the global supply chain. This includes retailers, manufacturers,
service providers, and other third parties.
|
|
|
Business
Context
|
|
|
Industry: All
Geopolitical: All
Product: All
Process: Plan
System
Capabilities: EAN.UCC
Official
Constraints: None
|
|
|
Business
Transaction View
|
|
|
Figure 1 Business
Transaction Use Case
Diagram |
|
|
|
|
|
|
|
|
Use Case
Description
|
|
|
|
Use Case ID
|
UC-1
|
|
Use Case Name
|
Negotiation |
|
Use
Case Description
|
This Use Case describes the processes of negotiation
within the promotional event lifecycle. |
|
Actors (Goal)
|
Manufacturer or Retailer acts as the originator of the promotion event.
The
respondent acts as the recipient of the promotional event. |
|
Performance Goals
|
None
|
|
Preconditions
|
Trading partner wishes to engage in some sort of
promotional event. |
| Post
conditions
|
Success : The originator of the event may modify and resubmit a
proposed event or it will not take place
Failure
: Rejection of proposal |
| Scenario
|
Begins
Continues with...
|
Step
#
|
Actor
|
Activity
Step
|
|
1
|
Retailer, Manufacturer |
Makes the business case for the event – items and
expected results |
|
2
|
Retailer, Manufacturer |
The other party either accepts the proposal or rejects
it |
|
3
|
Retailer, Manufacturer |
The originator of the event may modify and resubmit a
proposed event, subject to rules established for the trading relationship. |
Ends when... a sales forecast is initially generated by one trading
partner, communicated to the other trading partner and then used as a baseline
for the creation of an order forecast. |
| Alternative Scenario
|
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None |
|
|
|
|
|
|
Figure 2 Activity Diagram Negotiation phase of
Event
|
|
|
 |
|
|
|
|
|
|
Use Case ID
|
UC-2
|
|
Use Case Name
|
Planning |
|
Use
Case Description
|
This Use Case describes the trading partners
identifying which products and locations are to be included in the promotion,
and decide what specific price points, advertisements, displays, and other promotional
activities will be included in the event. The parties also estimate what
consumer demand will be, and what order quantities and timing will be required
to keep the affected products in stock. This phase may overlap with
negotiation. |
|
Actors (Goal)
|
Manufacturer or Retailer acts as the originator of the promotion event.
The
respondent acts as the recipient of the promotional event |
|
Performance Goals
|
None |
|
Preconditions
|
Trading partner wishes to engage in some sort of
promotional event. |
|
Post conditions
|
Successful: Both parties accept the event or promotion
Unsuccessful: Rejection or cancellation of a proposal.
|
|
Scenario
|
Begins
Continues
with…
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Retailer, Manufacturer |
Either the retailer or the manufacturer makes the
business case for the event – proposing items and expected results. |
|
2
|
Retailer, Manufacturer |
The other party either accepts the proposal or rejects
it. |
|
3
|
Retailer, Manufacturer |
The originator of the event may modify and resubmit a
proposed event, subject to rules established for the trading relationship. |
Ends when
|
|
Alternative Scenario
|
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None
|
|
|
|
|
|
|
Figure 3 Activity Diagram Planning phase of Event
|
|
|
 |
|
|
|
|
|
|
Use Case ID
|
UC-3
|
|
Use Case Name
|
Execution
|
|
Use
Case Description
|
This Use Case describes any displays, ad materials or incremental
product quantities are staged and presented to consumers.
|
|
Actors (Goal)
|
Manufacturer or Retailer acts as the originator of the promotion or
event.
The respondent acts as the recipient of the promotional event
|
|
Performance Goals
|
|
|
Preconditions
|
Trading partner wishes to engage in some sort of promotional event.
|
|
Post conditions
|
Successful: The originator of the event may modify and resubmit a
proposed event or it will not take place.
Unsuccessful: Rejection of proposal.
|
|
Scenario
|
Begins when...
Continues with...
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Retailer, Manufacturer
|
Either the retailer or
the manufacturer makes the business case for the event including specific advertising
tactics
|
|
2
|
Retailer, Manufacturer
|
The other party either
accepts the proposal or rejects it.
|
|
3
|
Retailer, Manufacturer
|
The originator of the
event may modify and resubmit a proposed event, subject to rules
established for the trading relationship.
|
Ends when...
|
|
Alternative Scenario
|
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None
|
|
|
|
|
|
|
|
Use Case ID
|
UC-4
|
|
Use Case Name
|
Post-event analysis
|
|
Use
Case Description
|
This Use Case describes both the manufacturer and the retailer
evaluating the effectiveness of the promotion in meeting the objectives set
out at the beginning of the process. Analysis of sales and delivery
performance is used to develop more effective future promotional events
|
|
Actors (Goal)
|
Manufacturer and Retailer
|
|
Performance Goals
|
|
|
Preconditions
|
Trading partner wishes to report the results of an event. Example: Snow Storm.
|
|
Post conditions
|
Successful: The recipient of the data successfully receives the
transaction.
Unsuccessful: The recipient of the data does not receive the transaction.
|
|
Scenario
|
Begins when...
Continues with...
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Retailer, Manufacturer
|
Either the retailer or
the manufacturer transmits the results of an event.
|
|
2
|
Retailer, Manufacturer
|
The other party receives
the data.
|
|
3
|
|
|
Ends when...
|
|
Alternative Scenario
|
None |
|
Related Requirements
|
None |
|
Related Rules
|
None |
|
|
|
|
|
|
Business
Transaction Sequence Diagram |
|
|
Not available |
|
|
|
|
|
Code Lists |
|
|
Implementation Considerations |
|
|
TOP
|
|
|
|
|
