In the event-driven KANBAN procedure, you can also use all the functions available in the

KANBAN module.
You must maintain separate control cycles for event-driven KANBAN.
In this procedure, a kanban is only created when required. That is, kanban creation is triggered
by a certain event. The system creates a kanban for every requested material quantity, which is
subsequently deleted on replenishment.
The event-driven kanban is created using a separate function. The quantity to be replenished is
defined directly in this function. In the control cycle, you can define the following restrictions for
the definition of the kanban:
You can enter a rounding quantity to round up the required quantity.
Reaching or exceeding the trigger quantity:
The procedure here is similar to the two procedures described above. However, the
difference here is that the kanban is set to EMPTY when the remaining quantity in the
kanban reaches or exceeds the trigger quantity. In this process, the parts are withdrawn
with the quantity signal. In this case, you must maintain the trigger quantity as well as the
logic in the control cycle. This process is particularly useful for parts that are not used on
a regular basis. Therefore, you can procure parts with KANBAN without having to keep
several containers in stock. However, a PDC system is required for this procedure.
4. Event-Driven KANBAN:
In event-driven KANBAN, material provision is not based on a predefined number of kanbans or
a predefined kanban quantity. Instead, it is based on actual material consumption. The material is
not continually provided and replenished at a supply area. It is only replenished when specifically
requested. In this procedure, the advantages of the KANBAN module are used to make the
material replenishment process even more simple.
In the one-card KANBAN procedure, you can also use all the functions available in the KANBAN
module.
Before you can use this procedure, you must select one of the processes in the field, Trigger
replenishment when maintaining the control cycle.
Triggering replenishment at status IN USE:
After the first container is reported full, the system proceeds as follows: The second
kanban is set to the status WAIT. If a new kanban is requested, the system sets the full
kanban to the status IN USE. With this status change the kanban with status WAIT is
automatically changed to status EMPTY and thus replenishment is triggered. When this
new kanban is delivered, it receives the status FULL. As soon as the kanban from which
material is still being withdrawn is set to EMPTY, the system automatically sets it to status
WAIT and the process is repeated.
This procedure is illustrated in the following graphic:
Triggering replenishment at status WAIT:
After the first container is reported full, the system proceeds as follows: When a new
kanban is requested, the full kanban is set to status EMPTY. With this status change the
kanban with status WAIT is automatically changed to status EMPTY and thus
replenishment is triggered. The kanban from which material is still being withdrawn
receives the status WAIT. When the new kanban is delivered, it receives the status FULL
and the process is repeated. As opposed to the logic with the status IN USE, you do not
have to work with an additional status here. On the other hand, you have no possibility in
the system of seeing whether a container is currently being emptied.