Warehouse Control System

A warehouse control system is the real-time layer between your WMS and the equipment on the floor. The WMS sends order data and routing instructions to the WCS, which drives the motors, diverts, scanners, and sortation logic as product moves. Done right, every package is tracked from receiving through shipping without manual routing. Done wrong, packages stall at diverts and misroute on warehouse conveyor systems.

What the WMS Owns and What the WCS Owns

The split matters because the two systems run on different clocks. A WMS works in transactions. A WCS works in the milliseconds between a barcode read and a divert firing, and it coordinates each zone based on its own sensor plus handshake signals from the zones upstream and downstream, which is the job of conveyor controls.

Where Sortation Decisions Actually Get Made

Research on automated warehouse sorting lays out the sequence: product moves on an accumulation belt to an induction station, a recognition station scans the barcode to identify each item, and the sorter discharges it to the packing lane assigned to that order.

Lane assignment and release sequencing are software decisions, not mechanical ones. The same sorter hits very different throughput depending on how orders are sequenced into it, which is why WMS to WCS integration is a throughput project, not just a data project.

Network Architecture at the OT Boundary

Connecting business software to floor controls crosses the IT to OT boundary, and NIST SP 800-82 Revision 3 gives specific architecture guidance. Organizations should segment IT and OT devices using a recognized model such as the Purdue model or ISA-95 levels (IEC 62264), and should consider a DMZ as the enforcement boundary between segments.

Adjacent levels only. Firewall rules should permit connections only between adjacent levels or zones. In a Purdue architecture, Level 4 devices should be prevented from communicating directly with Level 2, 1, or 0 devices.

Outbound rules as strict as inbound. Unmanaged outbound connections from lower zones carry significant risk.

All enterprise traffic through the DMZ. Communications between the enterprise level and the operations management level should pass through services in the DMZ, and those services have to be monitored.

Least functionality on controllers. Web servers or SSH servers present in newer PLCs and HMIs should be disabled when unused, along with the associated ports.

Failure Modes at the Interface

Data stuck on the floor. PLCs run the machines but tell the WMS nothing, counts get retyped, reports lag a day, and nobody trusts the numbers.

Code nobody can read. The integrator leaves, comments are blank, and maintenance cannot clear a fault without calling someone who no longer works there.

Routing that degrades quietly. Misroutes at sortation and stalls at diverts show up as labor, not as alarms.

What Working Integration Looks Like

Faults appear on the HMI and get cleared in minutes without opening the PLC. Every panel matches its drawing, every PLC has a backup, and the WMS knows what the floor is doing without anyone retyping a number. When a line is added the following year, the new code reads like the old code.

Diagnostics are part of the control design, not an add-on. Good conveyor control systems surface zone faults and jams for fast troubleshooting.

Platforms and Interfaces HOJ Supports

HOJ builds new systems on Beckhoff industrial PCs and works in Allen-Bradley, Siemens, and mixed floors, with Ignition HMIs that run across brands. Floor data flows to the WMS and ERP automatically. On the software side, HOJ integrates with WMS, SAP, ERP, and platforms including Oracle and NetSuite, including the software layer behind automated storage and retrieval systems.

How the Integration Gets Delivered

Scoping starts with what is running today, what is failing, and where throughput needs to go. The engineered proposal includes drawings, a hardware list, a platform recommendation, and a fixed schedule. HOJ's PLC and controls integration team then builds the panel, writes the code, installs, runs FAT and SAT, trains the team, and hands over commented code and drawings.

Most of a typical eight to sixteen week line integration is planning, with floor execution kept short. HOJ has completed multiple changeovers in a couple of days.