|
EXCEPTION NOTIFICATION v. 2.0.2 |
|
|
|
|
|
Problem
Statement |
|
|
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 exception notification is an indication of a variance from trading partner
guidelines for changes in a forecast, differences between partner forecasts, or
key performance metrics (forecast error, overstock, etc.).
The Exception Notification 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, class 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.
There are several types of exceptions, but all types describe a
variance of a data item from an expected value during a particular time interval. There are:
- Operational Exceptions to alert users to
a variance from expected product activity data values, such as a surge in
emergency orders, an overstock condition, or reduced shipment levels
- Metric Exceptions to identify
variances in key performance metrics such as forecast accuracy and fill rate
from their expected values in a particular time period.
- Forecast Data Item Exceptions. There are two kinds within this type.
|
|
|
- Forecast Accuracy Exceptions to compare a
forecasted item with the actual value observed.
(Example: a sales forecast would be compared to
point-of-sale data for the same period, and an exception is triggered if the
numbers vary by more than the forecast item exception criterion threshold).
- Forecast Comparison
Exceptions to compare two forecast streams.
(Examples: either the buyer’s
forecast to the seller’s or two generations of a forecast produced by the same
trading partner).
|
|
|
CPFR® is the registered trademark
of VICS, the Voluntary Interindustry Commerce Standards Association |
|
|
Objective |
|
|
The objective of this BRD 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 notify a
trading partner when a buyer or seller exception has been triggered
|
|
|
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
|
|
|
Business
Transaction View
|
|
|
Business
Transaction Use Case
Diagram |
|
|
Not available
|
|
|
|
|
|
Use Case
Description
|
|
|
|
Use Case ID
|
UC-1
|
|
Use Case Name
|
Request Exception Notification |
|
Use
Case Description
|
Not filled in the
previous BRD |
|
Actors (Goal)
|
Exception Notification is a two-actor system involving
a buyer and a seller. |
|
Performance Goals
|
None
|
|
Preconditions
|
CPFR® Steps 1 through 6 have been
completed |
| Post
conditions
|
Success :
Exception Notification is received by the other trading
partner
Failure
: A variance occurred and was not triggered resulting in the trading partner
not being notified of an exception
|
|
Scenario
|
Begins when there is a variance of a data
item from an expected value during a particular time interval. The variance is triggered by agreed upon
buyer and seller exception criteria
Continues with...
1
Both
trading partners have established the buyer and seller exception criteria
2
CPFR® is being practiced and data collected
3
A variance
exceeding the exception criteria occurs
4
The
variance to operational, metric or forecast items is identified
5
An
exception notification is sent to the other trading partner
Ends when... the message is transmitted
|
|
Alternative Scenario
|
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None |
|
|
|
|
|
|
Business
Transaction Activity Diagram
|
|
|
Not available
|
|
|
Business
Transaction Sequence Diagram |
|
|
Not available |
|
|
|
|
|
Code Lists |
|
|
TOP
|
|
|
|
|
