LFS MFC

What is LFS MFC?

LFS MFC stands for Material Flow Control in the context of the LFS warehouse management system. The module handles the control of physical material flow in automated warehouse and picking systems. It receives orders from the WMS layer, translates them into specific transport commands and forwards them to the machine level – typically via interfaces to programmable logic controllers (PLCs). In doing so, the MFC manages routing decisions, prioritization and congestion control in real time.

How does LFS MFC work in practice?

In an automated facility – such as an automated small-parts warehouse (AS/RS) with connected conveyor technology – the MFC forms the middle control layer between the WMS above and the PLCs below. Specifically, it handles the following tasks:

• Receiving transport orders from the WMS (e.g. retrieval, storage, relocation)
• Calculating optimal routes through the conveyor system, taking into account occupancy, capacity and priorities
• Communicating with PLC units to activate diverters, lifts, conveyor belts and sorters
• Reporting status back to the WMS or control center (acknowledgements, error messages, fault signals)
• Managing fault scenarios and defined recovery procedures

The MFC operates event-driven and must handle latencies in the millisecond range to prevent material flow from stalling. At the same time, it must be stable enough to handle system faults in isolation without interrupting overall throughput.

What matters when selecting and integrating the system?

Several points are critical when introducing or expanding an LFS MFC. First, all system components to be connected – conveyor lines, stacker cranes, sorters, airlocks – must be fully accounted for in the interface concept. Responsibilities between the WMS vendor, MFC layer and system supplier should be clearly defined contractually, as errors in the grey area between these layers are difficult to attribute during operations.

Redundancy and high availability are solved differently depending on the vendor and project – whether as hot standby, cold standby or with limited emergency operation. This should be explicitly defined in the requirements catalog. Likewise, monitoring interfaces to the control center and defined SLAs for restart times after faults are important criteria. Dead times and latencies between WMS order and physical execution should be verified by measurement during the acceptance process (FAT/SAT).