Forecast

What is the "Forecast" module

The Forecast module is an extension of KanbanBOX that allows you to:

• import production or procurement forecast data into KanbanBOX (i.e. forecasts generated by external software) based on historical data, market trends and predictive analyses;
• share forecasts with suppliers;
• perform maintenance on the kanban loops based on the imported forecast data.

The Forecast module can be activated via in-app purchase by following this path: Reports > Forecast.

How to use the "Forecast" module

To make the most of the Forecast module, follow these steps:

1. Import forecast data into KanbanBOX
2. View imported forecast data
3. Share forecast data with suppliers
4. Perform the maintenance on the kanban loops from forecast data

Import forecast data into KanbanBOX

It is possible to import forecast data into KanbanBOX via:

• Import with Excel
• POST /Forecast API

For the initial setup, it is recommended to import forecasts with Excel.

Forecast data can also be imported for kanban loops that are not yet present in KanbanBOX: it is sufficient that the component, supplier and customer are correctly entered in the master data section. In addition, there must be an active link with the external partner's (supplier or customer) KanbanBOX license.

View imported forecast data

Procedure

1. Go to Reports
2. Click on Forecast as owner.

Time interval statuses

In the Forecast as owner table, the time buckets will have one of the following statuses:

• Past if the time interval has already passed.
• Current if the time interval is the present one.
• Future if the time interval is upcoming.
• Expired if the time interval refers to an expired revision.

By default, the Forecast as owner table will show the last imported revision for a scenario with time intervals filtered by Current and Future status.

Expired revisions

If a revision is replaced by a more recent one, all time intervals of the old revision will become Expired, because they belong to an outdated revision.

When a new revision is imported, the previous revision is automatically deactivated and a expiration date is recorded. Previous revisions are not deleted or overwritten but are hidden by the filter on the time interval status.

Export

The Forecast as owner table can be exported to Excel by clicking Export components to Excel.

Share forecast data with suppliers

In the Forecast as supplier table, the supplier involved in the imported forecasts can confirm or modify the expected quantity for each forecast by clicking the Add quantity confirmation icon.

The quantity confirmed by the supplier is recorded under the Confirmed Quantity column.

By default, the Forecast as supplier table will display the last imported revision for a given scenario with time intervals filtered by Current and Future status.

Maintenance from forecast

The "Forecast" module allows you to perform the maintenance on your kanban loops based on the forecast data entered in KanbanBOX.

Procedure:

1. Click on Kanbans > Kanban maintenance > Maintenance from forecast
2. The table shows the Maximum daily consumption from KanbanBOX and the Maximum consumption per day from forecast together to compare them.
3. In the table is shown the KanbanBOX suggested adjustments, based on forecast data.

4. Using the commands in the Operations column it is possible to carry out loop maintenance operations, including:

   • : click here to recalculate the suggested adjustment based on the forecast data;

   • : with each click, the number of cards present in the loop increases by 1;

   • : with each click, the number of cards in the loop decreases by 1;

   • : click here to automatically resize the loop according to KanbanBOX suggestion;

   • : link to the statistics page (read Kanban statistics and maintenance);

   • : to access the Edit kanban loop page.

When does the automatic recalculation of forecast-suggested adjustments occur?

The automatic recalculation of forecast-suggested adjustments happens: - for all loops with an associated forecast, after new forecast data is uploaded; - for a single loop, after one of its cards is consumed; - once a day, if none of the above conditions are met.