The warehouse management monitor provides you with the following options:
Invocation of information on the system status, pending tasks, and the current occupancy of communication points and resources
Evaluation and tracking of shipments and telegram traffic
Starting and stopping the communication channels
Targeted intervention in the event of malfunctions
You have defined the storage type role H Material Flow Control
or J Automatic Warehouse (Driven by MFS)
. For more information, see the Implementation Guide (IMG) for EWM
under .
The selection of the MFS-relevant HUs and the MFS-relevant warehouse tasks is based on the storage type role of the affected storage types. You define these storage types in Customizing for EWM.
You can track the following objects in the warehouse management monitor:
Communication channel
The communication channels will have been started. In the warehouse management monitor, you can stop or restart individual connections.
Communication point
You can display a list of the communication points with their current status. Various sort and selection options are available (for example, you can display malfunctioning communication points). You can also lock communication points.
Telegram
You can display logs of PLC telegrams received and sent. Here, too, you have various select options such as by time of transmission. This overview is an important analysis instrument in the case of malfunctions. From here, you can branch directly to the affected warehouse tasks.
Warehouse task
You can call up a list of the current warehouse tasks and a warehouse task history. In the case of malfunctions, you can cancel or manually confirm warehouse tasks and you can branch directly to the associated telegrams and to the creation log for the warehouse task.
Handling units (HUs)
You can display a list of the HUs currently located within the automatic storage retrieval system. You see their current location, the status of the associated warehouse tasks, and the related telegrams sent. Furthermore, you can divert HUs in the case of errors.
Conveyor segment, conveyor segment group
You can display an overview of the status of the conveyor segments or segment groups. You can also manually lock individual segments or entire segment groups.
Resource
You can call up a status overview or manually lock the resource.
Telegram buffer
Telegrams received that could not be processed remain in the inbound buffer with error flags. Where appropriate, you can manually correct them and flag them for posting.
Telegrams due to be transmitted or which have been transmitted but not yet acknowledged by the PLC are visible in the outbound buffer.
The two buffers should always be empty.
From the warehouse management monitor, you can carry out the following activities for each node:
Node |
Activities |
|
Start or stop communication channel. Reset run number for received or sent telegrams. |
|
Define exception, query status, trigger processing. |
|
Send repeat telegram, simulate telegram. |
|
Simulate warehouse task, display warehouse task log, split off from warehouse task, assign warehouse task, revoke warehouse task assignment, confirm in foreground, confirm in background, reprint warehouse task, cancel warehouse task, define exception. |
|
Set MFS error; trigger processing. |
|
Define exception |
|
Define exception |
|
Define exception, query status, trigger processing. |
|
Process or delete telegram. |
Using MFS for case conveyor systems, the activity ‘trigger processing’ for communication points and HUs is not needed and is disregarded by the system.