|
PERFORMANCE HISTORY 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, performance history is one type of historical data
that a pair of CPFR®
trading partners (a buyer and a seller) can share. Performance History
represents a collection of values gathered for key performance metrics in the
trading partner relationship.
Performance history captures key supply chain metrics. These metrics can include forecast accuracy,
in-stock percentage, fill rate, days of supply, or on-time delivery
percentage. Because many of these
measures are ratios, they require a unit of measure to be meaningful.
|
|
|
Objective |
|
|
To supply the detail design
of the Performance History business transaction needed to meet the requirements of the
referenced BRAD(s).
|
|
|
Audience |
|
|
The audience for this document is anyone
involved in collaborative planning, forecasting and replenishment.
|
|
|
Business
Context
|
|
|
Industry: All
Geopolitical: All
Product: All
Process: Plan
System
Capabilities: EAN.UCC
Official
Constraints: None
|
|
|
Business
Transaction View
|
|
|
Exception criteria are rules that describe the
thresholds for forecast variance, product activity, and performance history
beyond which exceptions to sales forecasts and order forecasts are noted and
resolved between a pair of trading partners.
Performance History is used for metric exceptions.
The collaboration for these exceptions and resolution to
exceptions occurs between a pair of trading partners for a single location.
|
|
|
|
|
|
Use Case
Description
|
|
|
|
Use Case ID
|
UC-1
|
|
Use Case Name
|
Performance History |
|
Use
Case Description
|
The objective is
for a pair of trading partners to elaborate upon operational conditions and key
metrics that would identify exceptions to sales and order forecasts. |
|
Actors (Goal)
|
Performance History is a two-actor system involving a
collaborative effort between a buyer and a seller for a single location. The lead actor in the collaboration depends upon
the scenario most appropriate to the trading partner’s business situation. |
|
Performance Goals
|
None
|
|
Preconditions
|
A collaboration agreement and
joint business plan must be in place and a forecast is prepared and received by
the trading partners. |
| Post
conditions
|
Success : Exceptions, when identified,
are noted and
resolved.
Failure
: Operational
activities and key metrics identifying exceptions to forecasts are not
identified and resolved. |
| Scenario
|
Begins with the receipt a forecast by one of the Actors.
Continues with...
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Buyer, Seller
|
Establishes exception criteria
|
|
2
|
Buyer, Seller
|
Establishes the value limits set by
the exception criteria
|
|
3
|
Buyer, Seller
|
Upon receipt of a forecast (sales or
order), the appropriate trading partner retrieves exception criteria data
|
|
4
|
Buyer, Seller
|
If forecast is within the value
limits, no exception occurs or If forecast is outside the value limits, an
exception is identified and processed
|
Ends with
the resolution of exceptions |
| Alternative Scenario
|
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None |
|
|
|
|
|
|
|
|
|
Business
Transaction Activity Diagram
|
|
|
Not available
|
|
|
Business
Transaction Sequence Diagram |
|
|
Not available |
|
|
|
|
|
Code Lists |
|
|
TOP
|
|
|
|
|
