Re: UBL Documents for Collaborative Planning, Forecasting and Replenishment...

[Tim McGrath <tim.mcgrath@documentengineeringservices.com>]

As part of the requirements for UBL 2.1 we have received a request from 
the iSURF project  (a EU Framework 7 project) for Collaborative 
Planning, Forecasting, and Replenishment (CPFR) documents. 

The UBL TC has requested that the PSC take these requirements into 
account as part of the modelling for UBL 2.1.  Can you please liaise 
directly with Asuman and Yildiray on further details and keep them 
advised of progress.

The relevant documents (including the draft spreadsheets) have been 
posted to the UBL site at:

http://www.oasis-open.org/apps/org/workgroup/ubl/download.php/28512/eChallenges2008iSURFv2.pdf
http://www.oasis-open.org/apps/org/workgroup/ubl/download.php/28511/UBL-Forecast.Draft.zip
http://www.oasis-open.org/apps/org/workgroup/ubl/download.php/28510/HowToObtainForecast.doc


iSURF also has a Web site at:
http://www.srdc.com.tr/isurf/

Below is the information provided by the project team leaders.

Prof. Dr. Asuman Dogac wrote:
> Dear Jon,
>
> The documents we need for Collaborative Planning, Forecasting, and 
> Replenishment (CPFR) are as follows:
>
> 1. Forecast: projected demand for an item sourced at a seller location 
> and consumed at a
> buyer location
> 2. Forecast revision: a set of proposed changes to a forecast, as the 
> result of, for example,
> promotional activity, weather, distribution or transportation issues, 
> or replanning
> 3. Product activity: actual product movement observed, which may 
> include on-hand
> quantities, distribution center (DC) withdrawals, or Point-of-Sale (POS)
> 4. Performance history: a collection of values gathered for key 
> performance metrics in the
> trading partner relationship, such as forecast error, sales growth, or 
> the number of
> emergency orders
> 5. Exception notification: indication of a variance from trading 
> partner guidelines for changes
> in a forecast, differences between partner forecasts, or key 
> performance metrics (e.g.,
> forecast error, overstock)
> 6. Exception criteria: definition of the threshold for variances 
> beyond which an exception
> message should be triggered
> 7. Item location profile: parameters to guide the collaborative 
> replenishment process for an
> item sourced at a seller location and consumed at a buyer location
> 8. Event: description of a promotion, inventory policy change, or 
> other planned event, along
> with its expected and actual impacts on the supply chain
> 9. Item information request: one trading partner’s request to the 
> other to send product
> activity, forecast, or performance data, when the partner does not 
> automatically send
> data
>
> The process we apply is described in the enclosed document.
> Additionally, we include our trial to generate a "Forecast" document
> in the attached zip file.
>
> We look forward to hearing your comments.
>
> All the best,
>
> Yildiray&Asuman
>
>>
>>
>>   
>
>
begin:vcard
fn:Tim McGrath
n:McGrath;Tim
org:Document Engineering Services Ltd.
email;internet:tim.mcgrath@documentengineeringservices.com
title:Managing Director
tel;work:+61 438352228
tel;cell:+61 438 352228
url:www.documentengineeringservices.com
version:2.1
end:vcard