PFEP > Kanban Reports

Time values used in these reports take into account the work schedule (see Tools: Preferences - PFEP and Work Schedule Maintenance). The reports exclude any scheduled breaks and down days.

1.Kanban Transaction Log

Shows all kanban scans made within the specified date range.

This report can be filtered by Part ID(s), Location ID(s) or kanban card ID(s).

2.Kanban Transaction Duration

Shows Kanban transactions for transaction types Requested, Delivered, Released and Hold. Shows time to complete each transaction. Alerts users to status of times using stoplight images and color-coding.

This report can be filtered by Part ID(s), Location ID(s) or kanban card ID(s), and date, and transaction type, and duration value (stoplight color).

3.Kanban Transaction Count

Returns the number of transactions in the log for the selected transaction types (Requested, Delivered, Released, Hold). These values are sorted by stoplight color.

This report can be filtered by Date and by Part ID(s), Location ID(s) or kanban card ID(s).

4.Kanban Cycle Summary

Shows summary statistics for a given Kanban ID. This report can be filtered by Part ID(s), Location ID(s) or kanban card ID(s), as well as by date, and by stoplight values for both cycle and idle time.

•Cycles: The number of times this kanban has cycled in the selected period. A cycle is defined as a container being requested and then being delivered.

•Avg. Replenishment Time: The mean time required for this kanban to go from ‘Requested’ to ‘Delivered’. Color-coded by stoplight value.

•Max Replenishment Time: The longest recorded time between requesting that the kanban be filled, and the kanban being delivered. Color-coded by stoplight value.

•Min Replenishment Time: The shortest recorded time between requesting that the kanban be filled, and the kanban being delivered. Color-coded by stoplight value.

•Standard Dev. of Replenishment Time: The standard deviation of all cycles (time between requesting that the kanban be filled, and the kanban being delivered).

•Average Idle Time: Mean of time between the delivery of the kanban ID to until the next time that kanban ID is requested.

•Max Idle time: The longest time between a delivery and subsequent request for the given kanban ID. Color-coded by stoplight value.

•Min Idle time: The shortest time between a delivery and subsequent request for a given kanban ID. Color-coded by stoplight value.

•Std Deviation Idle Time: The standard deviation of the time between a delivery and subsequent request for the given kanban ID. Color-coded by stoplight value.

•Alert Column: Flags Kanban card according to worst stoplight value found for type of time.

5.Kanban Issues

A. Kanban Issues, by Location

Shows any Part IDs at a given location for which no kanban cards are idle. These are cases where all of the kanbans for that part and location have been ‘Requested’, but none have yet been ‘Delivered’. Kanbans in this report could also be in the "Hold" or "Released" status if there was an issue with the request.

B. Kanban Issues, by Kanban ID

Shows any Kanban ID that has been requested but not yet delivered. Any Kanban ID that is in the "Requested," "Hold," or "Released" status will appear in this report. This report does not take into account whether or not other Kanban cards for the same part are active or not.

6.Part Kitting Transaction Log

Shows all kitting scans made within the specified date range. There will be a row entry for each part in the kit.

This report can be filtered by Part ID(s) or Location ID(s).