|
PRODUCT ACTIVITY 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, product activity
is one type of historical data that a pair of CPFR® trading partners (a buyer and a seller)
can share. Product Activity represents movement of a product through a
location.
Product activity,
historical product movement through a location, is always expressed in terms of
the base unit of measure for the item, so no unit of measure is specified. Types of product activity include sales
(which may also be interpreted as manufacturing consumption or warehouse
withdrawals, depending upon the type of buyer/seller relationship), orders,
canceled orders, emergency orders, receipts, shipments and on-hand
inventory. Product activity reports are
collections of product activity items that indicate the quantities of product
movement during the specified time intervals.
|
|
|
Objective |
|
|
To supply the detail design
of the Forecasts 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.
Product Activity is used for operational 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
|
Product Activity |
|
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)
|
Product Activity 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
Continues with...
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Buyer, Seller
|
Establishes exception criteria
|
|
2
|
Buyer, Seller
|
Establish 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
|
|
|
|
|
