|
EXCEPTION CRITERIA 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 criteria
define the threshold for variances, beyond which an exception message should be
triggered.
The Exception Criteria 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.
Exception criteria are rules that describe the thresholds for forecast
variance, product activity, and performance history beyond which exceptions
should be triggered.
CPFR® implementations
exchange exception criteria so that their respective exception engines can use
the same rules to evaluate data, and trigger identical exceptions in parallel.
Forecast item exception criteria may be restricted to a single
component of a forecast (for example, a variance in the promotional component
of two sales forecasts), or they can compare totals. The effective dates for an exception describe
a horizon in which a criterion is valid.
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.
|
|
|
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 |
|
|
|
|
|
|
|
|
Use Case
Description
|
|
|
|
Use Case ID
|
UC-1
|
|
Use Case Name
|
Request Exception criteria |
|
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
|
Both trading partners agree on
the exception criteria and are implementing CPFR® |
| Post
conditions
|
Success :
Exception criteria triggers an exception notification for variances beyond
threshold limits.
Failure
: Variances do not trigger an exception notification. |
|
Scenario
|
Begins when the development of a collaborative arrangement and
implementation of CPFR® is done.
Continues with...
1
Both
trading partners have established the buyer and seller exception criteria as
part of CPFR® Step 1 (“Develop
Collaboration Arrangement” includes the identification of buyer and seller
exception criteria. The exception
criteria establish the exception triggers for the exception notification).
2
Both
trading partners are implementing CPFR®
3
Both
trading partners are collecting and evaluating data
4
A variance
exceeding the assigned threshold criteria occurs
5
An
exception is triggered
Ends when... the implementation of the exception criteria against operational, metric
and forecast performance is done.
|
|
Alternative Scenario
|
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None |
|
|
|
|
|
|
Business
Transaction Activity Diagram
|
|
|
Not available
|
|
|
Business
Transaction Sequence Diagram |
|
|
Not available |
|
|
|
|
|
Code Lists |
|
|
TOP
|
|
|
|
|
|
