Create one forecast view in PowerBI
Budget: $30 – $250 USD
What:
The customer needs a sales history of the last 12 months, and at the same time, the sales forecast for the products within the hierarchy.
How:
A data visualization that allows the user to obtain the forecast, from various hierarchical levels, to the lowest level (SKU).
The database already contains the sales history at all levels of granularity. We just want the user to be able to navigate those levels with filters included in the view.
Characteristics:
1. Various hierarchical levels
a. Enterprise
b. Branch/Cost Center
c. March
d. Category / Subcategory / Family
e. SKU
2. Select the algorithm type (if available)
3. Possibility to "edit" the data that will be used for the forecast.
Note: Historical data may have variations that are not useful/necessary for forecasting. Therefore, the user should have the possibility to edit the data of certain months in such a way that they affect the behavior of the forecast.
Visualization:
1. Visualization at the graphical and tabular level (data)
2. Option to export the data to Excel
The requirements above can be achieved with the line chart, using the included forecast analytics.
We are open to using this, and/or other alternatives if those are backed up with strong arguments (technical & economic).
The customer needs a sales history of the last 12 months, and at the same time, the sales forecast for the products within the hierarchy.
How:
A data visualization that allows the user to obtain the forecast, from various hierarchical levels, to the lowest level (SKU).
The database already contains the sales history at all levels of granularity. We just want the user to be able to navigate those levels with filters included in the view.
Characteristics:
1. Various hierarchical levels
a. Enterprise
b. Branch/Cost Center
c. March
d. Category / Subcategory / Family
e. SKU
2. Select the algorithm type (if available)
3. Possibility to "edit" the data that will be used for the forecast.
Note: Historical data may have variations that are not useful/necessary for forecasting. Therefore, the user should have the possibility to edit the data of certain months in such a way that they affect the behavior of the forecast.
Visualization:
1. Visualization at the graphical and tabular level (data)
2. Option to export the data to Excel
The requirements above can be achieved with the line chart, using the included forecast analytics.
We are open to using this, and/or other alternatives if those are backed up with strong arguments (technical & economic).