| EVENT v. 2.0.2 |
|
|
Business Opportunity and Business Needs
|
Collaborative Planning Forecasting and Replenishment (CPFR®) is a well documented nine step process developed
and maintained by the Voluntary Interindustry Commerce Standards Association
(VICS) for use by trading partners.
In the CPFR® process an event is a
description of a promotion, inventory policy change, or other planned events,
along with its expected and actual impacts on the supply chain. Both the buyer and seller prepare, review and
collaborate on their planned events during the creation of the sales forecasts.
The Event Business Requirements Document is the output of the VICS CPFR®, GCI, the Plan BRG (Business Requirements Group)
and EAN ECEG (Electronic Commerce Expert Group). It is the responsibility of
the BRG’s to provide the business requirements for the process of the creation
and maintenance of the business and data models. The BRG’s develop and maintain
business process models and supporting use case diagrams, logic diagrams and
data requirements for a specific business function in a global electronic
commerce environment. The BRG’s review and resolve change requests. The BRG’s
provide guidance for the technical application of new business processes and
changes to existing business processes. Currently, BRG’s exist for the following
business processes: Align Data, Plan, Order, Despatch, Pay, After Sales
Services, Asset Management, Manufacturing and Point Of Service. EAN (ECEG) covers similar functionality,
through a pool of experts that liaises with the local users, ensuring the
effective gathering of the business requirements from its network of national
Member Organisations world-wide.
Event messages describe discrete events that affect supply or
demand. For example, a sale on an item increases
demand. Events are not restricted to
promotions; they may include weather-related activity, or inventory policy
changes.
Events are important in CPFR® because they are
typically responsible for the greatest volatility in a forecast. When events are properly correlated to the
base forecast for an item, forecast accuracy improves.
CPFR® is the registered trademark of VICS, the Voluntary
Interindustry Commerce Standards Association
|
|
Objective
|
The purpose of this Business Requirements Document is to document a
process-to-data approach. The Unified Modeling Language (UML) is used for
notation. Processes are clearly understood because of the use of formal
modeling with the UML models. Agreed to models permit the application of the
data elements to support the processes. The biggest benefit of this
process-to-data approach is the alignment of the model to fit the business
need.
The objective is to collaborate on
both the buyer’s and seller’s event planning to improve the accuracy of the
forecast.
|
| Audience |
The
audience for this document is anyone involved in collaborative planning,
forecasting and replenishment.
To better understand this business requirements document the
audience should become familiar with the VICS CPFR® Process, the VICS CPFR® XML Messaging
Model, June 13, 2001 and VICS Collaborative Planning Forecasting and
Replenishment (CPFR®), Global Commerce Initiative
Recommendation, June 30, 2001 as these documents provide the basis and context
of the business requirements.
|
| Business
Context |
Industry:
All
Geopolitical:
All
Product:
All
Process: Plan
System
Capabilities:
EAN.UCC
Official
Constraints: None |
|
| Player and Roles |
| Both trading partners, the buyer and the seller,
collaborate on the events. |
|
|
| Business Transaction View |
|
Business Transaction Use Case Diagram
|
| Not available |
|
Use Case ID
|
UC-1
|
|
Use Case Name
|
Request Event
|
|
Use
Case Description
|
Not filled in the previous BRD
|
|
Actors (Goal)
|
Event is a two-actor system involving a buyer and a seller.
|
|
Performance Goals
|
Goals related to
technical requirements
None
|
|
Preconditions
|
Both trading partners complete CPFR Steps 1 and 2.
|
|
Post
conditions
|
Success: An event is planned, exchanged and
agreed upon before the development of a forecast.
Failure: An event is not created before the
forecast.
|
|
Scenario
|
Begins when the completion of CPFR Step 2 is finished .
Continues with...
1
Both trading partners have established the
buyer and seller exception criteria as part of CPFR Step 1
2
Both trading partners have completed CPFR Step 2
3
Both trading partners identify and describe
their events
4
Both trading partners collaborate on their
events
5
Event items and planned impacts are identified
6
Events are assigned a category code, type code
and status
Ends when... the creation of a new event, the revising of an
event, or the cancellation of an event is done |
|
Alternative Scenario
|
There are no alternative scenarios.
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None
|
|
|
| Code Lists |
|
TOP
|
|
|
