Difference between revisions of "Forecast Management"

From ADempiere ERP Wiki
Jump to navigationJump to search
m
 
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Status  ==
== Status  ==


Ready for Production use
In production use


== Contributors  ==
== Contributors  ==
Line 14: Line 14:


== Purpose  ==
== Purpose  ==
[http://docs.google.com/document/d/1T1dh2JyncjCMqwlUqnIHEla9tywwHLEqBa2mw1gttEc/pub Forecast Sales Management User Guide]
== References  ==
== References  ==
[http://www.stevengould.org/software/openforecast/index.shtml Open Forecast]
[http://www.stevengould.org/software/openforecast/index.shtml Open Forecast]
[http://en.wikipedia.org/wiki/Demand_forecasting Demand forecasting]
[http://en.wikipedia.org/wiki/Demand_forecasting Demand forecasting]
[http://en.wikipedia.org/wiki/Forecasting Forecasting]
[http://en.wikipedia.org/wiki/Forecasting Forecasting]
[http://www.businessdictionary.com/definition/sales-forecast.html  business dictionary definition]
 
[http://www.businessdictionary.com/definition/sales-forecast.html  Business Dictionary Definition]


== Design Considerations  ==
== Design Considerations  ==
===Assumptions===
===Assumptions===
===Dependencies===
===Dependencies===
*The supported methods for calculating the forecast are based on the  [http://www.stevengould.org/software/openforecast/sample.html library open forecast]
===Constraints===
===Constraints===
*Is requires having a historic sales by product  at least a year to be imported.
== Glossary ==  
== Glossary ==  
==Functional Requirements==
==Functional Requirements==
== Functional team  ==
*Volunteers for analyzing:
** [[User:mar_cal_westf|Mario Calderon]] 11:00, 16 June 2013 (UTC) - Functional Review
===Result of review by Mario Calderon, June 16th, 2013===
*Analyzing document ( https://docs.google.com/a/e-evolution.com/document/d/1T1dh2JyncjCMqwlUqnIHEla9tywwHLEqBa2mw1gttEc/pub )
*Goal of module: to create forecasts that will be considered during execution of MRP. The forecasts can be generated based on different rules and the results can be simulated before being brought into the forecast table.
*Definition of forecast calendar and forecast periods
**Automatically, weekwise
*Generation of sales history, based on different parameters
*Possibility of importing sales history, created on csv files
**Import sales history: works (from file into table ''C_SalesHistory''
*Definition of forecast rules in Application Dictionary
**Double Exponential Smoothing
**Simple Exponential Smoothing
**Triple Exponential Smoothing
**Polynomial Regression
**Regression
**Naive Forecasting
**Multiple Linear Regression
**Best Forecast Model
**Moving Average
*Forecast definition
**Lines for different concepts: products, product categories, business partners
**Factors definable (alpha, beta, gamma)
**Sequence definable
*Forecast calculation
**''Forecast run'' is calculated based on parameters and sales history
**Forecast calculation is possible to run repeatedly
**Parameters for calculation
***Forecast definition
***Forecast rule
***Calendar
***Source and target warehouse
***Base and target period
*Forecast run result
**Is a Smart Browser
**Two filter fields with same name (Period definition): is not clearly explained what they are for; this makes the filtering difficult.
**Zoom doesn't work
**Export works
*Process ''Calculate forecast''
**not to confound with ''Forecast calculation''
**This calculates the real forecast, based on Forecast run
**Different parameters selectable (action, load type)
**It is possible to do simulations for different scenarios and do the forecast for the most suitable/acceptable
*If the company has an own Forecast application, the forecast can be imported directly from a csv file
*'''Conclusion: accepted'''
===User roles & profiles===
===User roles & profiles===
* Sales Manager
* Product Manager
* Marketing Manager
===Business process definition===
===Business process definition===
===User stories===
===User stories===
===Functional requirements based on business processes===
===Functional requirements based on business processes===
====User Interface Mockups====
====User Interface Mockups====
[http://www.adempiere.com/Forecast_Management#Purpose  Screenshot]
== Acceptance criteria  ==
== Acceptance criteria  ==
== QA and test cases ==
== QA and test cases ==
== Development infrastructure  ==
== Development infrastructure  ==
*[http://sourceforge.net/p/adempiere/code/ci/feature/ADEMPIERE-98-Forecast-Management/~/tree/ The feature has been integrated into Adempiere Repository]
*branch: feature/ADEMPIERE-98-Forecast-Management
*JIRA-URL: https://adempiere.atlassian.net/browse/ADEMPIERE-98
== Technical Requirements ==
== Technical Requirements ==
== Technical team  ==
*Volunteers for analyzing: [[User:Kthiemann|Kthiemann]] 14:41, 24 June 2013 (UTC)
*Result of analysis:
== Data Requirements ==
== Data Requirements ==
==Non-Functional Requirements==
==Non-Functional Requirements==
==Open Discussion Items==
==Open Discussion Items==
==Closed Discussion Items==
==Closed Discussion Items==

Latest revision as of 14:34, 5 March 2015

Status[edit]

In production use

Contributors[edit]

e-Evolution

Overview[edit]

This functionality allows an estimate of future sales of physical units and / or monetary of the products or services over a period of time, using quantitative and statistical methods based on historical data and market statistics.

The projected quantities and sales amounts are used for decision making, pricing, cash flow, estimated future demand, calculating master production schedule, supply plan and future capacity requirements.

Purpose[edit]

Forecast Sales Management User Guide

References[edit]

Open Forecast

Demand forecasting

Forecasting

Business Dictionary Definition

Design Considerations[edit]

Assumptions[edit]

Dependencies[edit]

Constraints[edit]

  • Is requires having a historic sales by product at least a year to be imported.

Glossary[edit]

Functional Requirements[edit]

Functional team[edit]

  • Volunteers for analyzing:

Result of review by Mario Calderon, June 16th, 2013[edit]

  • Analyzing document ( https://docs.google.com/a/e-evolution.com/document/d/1T1dh2JyncjCMqwlUqnIHEla9tywwHLEqBa2mw1gttEc/pub )
  • Goal of module: to create forecasts that will be considered during execution of MRP. The forecasts can be generated based on different rules and the results can be simulated before being brought into the forecast table.
  • Definition of forecast calendar and forecast periods
    • Automatically, weekwise
  • Generation of sales history, based on different parameters
  • Possibility of importing sales history, created on csv files
    • Import sales history: works (from file into table C_SalesHistory
  • Definition of forecast rules in Application Dictionary
    • Double Exponential Smoothing
    • Simple Exponential Smoothing
    • Triple Exponential Smoothing
    • Polynomial Regression
    • Regression
    • Naive Forecasting
    • Multiple Linear Regression
    • Best Forecast Model
    • Moving Average
  • Forecast definition
    • Lines for different concepts: products, product categories, business partners
    • Factors definable (alpha, beta, gamma)
    • Sequence definable
  • Forecast calculation
    • Forecast run is calculated based on parameters and sales history
    • Forecast calculation is possible to run repeatedly
    • Parameters for calculation
      • Forecast definition
      • Forecast rule
      • Calendar
      • Source and target warehouse
      • Base and target period
  • Forecast run result
    • Is a Smart Browser
    • Two filter fields with same name (Period definition): is not clearly explained what they are for; this makes the filtering difficult.
    • Zoom doesn't work
    • Export works
  • Process Calculate forecast
    • not to confound with Forecast calculation
    • This calculates the real forecast, based on Forecast run
    • Different parameters selectable (action, load type)
    • It is possible to do simulations for different scenarios and do the forecast for the most suitable/acceptable
  • If the company has an own Forecast application, the forecast can be imported directly from a csv file
  • Conclusion: accepted

User roles & profiles[edit]

  • Sales Manager
  • Product Manager
  • Marketing Manager

Business process definition[edit]

User stories[edit]

Functional requirements based on business processes[edit]

User Interface Mockups[edit]

Screenshot

Acceptance criteria[edit]

QA and test cases[edit]

Development infrastructure[edit]

Technical Requirements[edit]

Technical team[edit]

  • Volunteers for analyzing: Kthiemann 14:41, 24 June 2013 (UTC)
  • Result of analysis:

Data Requirements[edit]

Non-Functional Requirements[edit]

Open Discussion Items[edit]

Closed Discussion Items[edit]