|
FORECAST BULK DATA 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 Bulk Data for Forecast is a message format.
The Bulk Data for Forecast 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.
Each bulk data message is a uniform series of records of a single
message type. Records criteria include width, order of fields and default
values.
A bulk data description may be provided with every batch file, or a
single description may be used to describe all files of that type exchanged
between a buyer and a seller.
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 |
|
|
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 Bulk Data For Forecast |
|
Use
Case Description
|
Not filled in the
previous BRD |
|
Actors (Goal)
|
Bulk data for forecast is a two-actor system involving
a buyer and a seller |
|
Performance Goals
|
None
|
|
Preconditions
|
Both trading partners engage in CPFR® Step 1. |
| Post
conditions
|
Success : The bulk data for forecast is sent and received
Failure
: The bulk data for forecast can be neither sent
nor received |
| Scenario
|
Begins the step 1 of the CPFR® process
is started
Continues with...
1
Both
trading partners have started CPFR® Step 1
2
Both
trading partners agree on the fixed record width
3
Both
trading partners agree on default values
4
Both
trading partners agree on description rules
5
Both
trading partners create, send and receive a trial message
6
Both
trading partners exchange bulk forecast data Both trading partners have established
the buyer and seller exception criteria
Ends when... the bulk data is exchanged. |
| Alternative Scenario
|
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None |
|
|
|
|
|
|
Business
Transaction Activity Diagram
|
|
|
Not available |
|
|
Business
Transaction Sequence Diagram |
|
|
Not available |
|
|
|
|
|
Code Lists |
|
|
TOP
|
|
|
|
|
