Report

What are Reports?

The Report module provides access to all lists and reports that track the history of key activities.

History - Moves

The History - Moves report records all status changes applied to kanban and extra cards within a defined time range. By default, the table is filtered by setting the Last status change date to today. These default settings may be modified to extend the time range considered.

The table shows changes made to kanban and extra cards by both license users and users operating under a partner license (Last edit user).

This report provides visibility into the Source that performed tha status change.

The Source includes:

Type	Description
Automatic	These are intermediate and optional status changes, performed automatically by the system.
Board	Status changes are performed through the browser, using widgets or directly from the board.
API	Status changes are performed through integration with the management system.
Android, iOS, …	Status changes are performed using the app.
Documents	Status changes (In transit/Full) are performed through the Documents module.
RFID	Status changes are performed using RFID technology.
Inventory count	Status changes are performed during the inventory count.

Among the data available in this table, the Date of emptying field may be relevant to display. This field is not included in the default set of columns; however, it can be added to the table, along with other available fields, by clicking the Customize table fields icon.

History - Worklists

The History - Worklists report provides an overview of all cards included in worklists created by users, enabling the identification of both the cards included in a given worklist and the worklist to which a specific card belongs. The report is structured into two distinct tables: - Active worklists: lists all cards currently on the kanban board that belong to a worklist. A worklist is considered active if at least one of its cards is still present on the kanban board. Each license has visibility on the worklists created within its own license, as well as on those created by partners that include shared kanban loops. - Worklist history: lists all cards associated with active and inactive worklists (cards that are no longer present on the board) for which the license has visibility.

By default, tables are filtered by Creation time and display worklists created in the last month. Users can modify this filter to expand or narrow the selected time range.

Both tables can be filtered using additional fields, and the displayed data can be exported by clicking the Export data to Excel icon.

History - Card Events

The History - Card Events report tracks all actions performed by license users on kanban, extra cards, and worklists. Actions performed by users of linked licenses (both suppliers or customers) are not included.

For each action, the table shows the initial state (Initial Status and Scanned String), the final state (Occurred event and Final String), and the action that triggered the transition from one to the other (Triggering action).

The table also shows the Result of the operation and the Message to the user.

The following actions are tracked:

• Card status changes;
• Card blocking and unblocking;
• Card quantity changes, which are reported in the Message to the user column;
• Flagging a card as urgent;
• Flagging a card as out of stock;
• Workflow execution.

This report provides visibility into the Source that performed tha status change.

The Source includes:

Type	Description
Automatic	These are intermediate and optional status changes, performed automatically by the system.
Board	Status changes are performed through the browser, using widgets or directly from the board.
API	Status changes are performed through integration with the management system.
Android, iOS, …	Status changes are performed using the app.
Documents	Status changes (In transit/Full) are performed through the Documents module.
RFID	Status changes are performed using RFID technology.
Inventory count	Status changes are performed during the inventory count.

By default, the table is filtered to display only card events with a successful outcome (non-empty Occurred event) and referring to the current date. As a result, events that ended with an error are not shown by default but they can be displayed by adjusting the table filters.

History - Kanban statuses

The History - Kanban statuses report provides an overview of all kanban loops, showing the status of cards, the number of existing orders, expressed as the number of released cards by quantity, and the number of extra cards.

The table displays data in real time and is continously updated.

For each kanban loop, detailed statistics can be accessed by clicking the Kanban loop statistics icon.

Here, a set of essential charts presented:

• Historical kanban available in supermarket;
• Historical consumption;
• Average delivery lead time;
• Value of stock;
• Inventory turns on a yearly basis;
• Out of stock.

For each chart, it is possible to set the time range to be analyzed and export the data to an Excel spreadsheet by clicking the Export data to Excel icon.

History - FIFO Report

The History - FIFO issues report shows, for each kanban card currently present on the board, how many times the card has been overtaken by other cards belonging to the same loop. The report is automatically updated after each status change.

For each kanban card, the table displays the following information:

• Overtaking cards no.: it represents how many times the card, in the status in which it is set, has been overtaken by other kanban cards belonging to the same loop, that is how many times other cards of the same loop were set in the same status successively to the concerned card, and already set in a subsequent status;
• % overtaking: it represents the percentage of overtakes that the kanban card had. The percentage is calculated as the number of overtakes divided by the number of cards.
  The critical percentage is represented by 100%: when the percentage of overtaking is equal or higher than this value, the kanban card has been overtaken by all the other kanban cards of the same loop.
  The higher this percentage, the higher the attention to be paid to the kanban card, so we suggest to order the table by descending % overtaking.

Main causes of an high number of overtakes

An high number of overtakes can have one of these causes:

• the kanban card container physically exists but is not present in the warehouse, consequently it has been lost.
  In this case, if you cannot find the container, you should set the kanban card quantity to zero and release the card.
• the kanban card container has been consumed but the kanban card was not released. The loop is running with one card in less. A comparison between the KanbanBOX stock and the ERP stock can reveal a KanbanBOX stock higher than the ERP stock. In this case, you should release the card.

For each card it is possible to access the history of the kanban loop to which the card belongs, clicking on the icon Kanban loop status, in the Operations column.

History - Comment History

The History - Comment History report provides a comprehensive record of all comments entered on kanban cards, together with the corresponding Insert Date and the Comment Author.

The table includes only comments added by license users; comments entered by users with passive licenses are not tracked.

This table also allows you to view comments associated with kanban cards that are no longer present on the board.

By default, the table is filtered by setting the Insert date to today. These default settings may be modified to extend the time range considered.