How to Integrate Conveyor Controls With Your WMS and WES (A Practical Guide)

INTEGRATION OBJECTIVE

Warehouse Management Systems (WMS) manage inventory, orders, waves, and fulfillment records. Warehouse Execution Systems (WES) coordinate work across automated equipment, labor, and material flow. Conveyor controls execute machine-level functions through PLCs, drives, sensors, scanners, and safety circuits.

Successful system integration assigns each function to the correct control layer:

WMS: Orders, inventory, carton records, locations, and fulfillment status
WES/WCS: Task orchestration, routing, release logic, equipment coordination, and exception handling
PLC CONTROL SYSTEM: Motor control, sensor processing, zone logic, interlocks, accumulation, and local fault response
OPC UA: Structured communication between control equipment and supervisory systems
NETWORK INFRASTRUCTURE: Industrial Ethernet, managed switches, firewalls, VLANs, and secure access

The integration must preserve local machine control while providing accurate equipment status and material-flow data to higher-level systems.

DEFINE THE SYSTEM ARCHITECTURE

Use a layered architecture before selecting protocols, writing PLC code, or configuring WMS interfaces.

WMS LAYER

The WMS remains the system of record for:

Customer orders
Inventory quantities
SKU information
Carton and tote identifiers
Storage locations
Wave and batch releases
Order completion
Inventory transactions

The WMS generally does not control individual conveyor motors or photo-eyes. It sends business-level work to the WES or WCS through REST APIs, database interfaces, message brokers, or other approved enterprise connections.

WES OR WCS LAYER

The WES or Warehouse Control System converts business-level work into equipment-level actions.

Typical functions include:

Releasing cartons to a conveyor line
Assigning destinations
Coordinating sortation
Managing accumulation
Sequencing work
Monitoring equipment availability
Handling blocked routes
Recording conveyor events
Returning completion and exception data to the WMS

This layer prevents the WMS from depending on vendor-specific PLC tags or proprietary machine commands.

PLC AND EQUIPMENT LAYER

The PLC executes the conveyor control logic. Local functions include:

Start and stop logic
Motor and VFD control
Zone accumulation
Photo-eye processing
Jam detection
Divert confirmation
Sensor fault handling
Safety interlocks
Emergency-stop response
Local manual and maintenance modes

Real-time control remains local to the PLC. WMS and WES systems issue supervisory commands and consume status data. They do not replace the PLC safety system or close time-critical control loops through an enterprise network.

USE OPC UA AS THE EQUIPMENT INTERFACE

OPC UA provides a platform-independent communication architecture for industrial control systems. The standard supports structured information models, secure communication, subscriptions, events, and method calls.

The OPC Foundation overview of OPC UA identifies the following capabilities:

Discovery of OPC UA servers
Hierarchical address spaces
Read and write access
Data subscriptions
Event notifications
Method execution
Encryption
Authentication
Certificate-based application identity
Auditing
Client-server and publish-subscribe communication

For conveyor applications, OPC UA can expose equipment information in a format that WES software can browse, monitor, and use without relying on unstructured tag lists.

SELECT SERVER PLACEMENT

Two primary OPC UA deployment patterns apply to conveyor systems.

PLC-BASED SERVER

Use an OPC UA server embedded in a modern PLC or controller.

Applicable conditions:

New conveyor installations
PLCs with native OPC UA support
Sufficient controller resources
Defined security and certificate capabilities
Direct access to equipment states and diagnostics

EDGE GATEWAY SERVER

Use an industrial PC or gateway to aggregate legacy controls.

Applicable conditions:

Existing PLCs without native OPC UA
Multiple controller brands
Retrofit projects
Fieldbus or proprietary protocols
Centralized namespace requirements

The gateway reads approved PLC data, maps it to a consistent OPC UA information model, and provides the WES with a standardized interface.

DESIGN THE OPC UA INFORMATION MODEL

Do not begin with an unstructured export of every available PLC tag. Define the equipment model first.

IDENTIFY ASSETS

Create objects for equipment such as:

Conveyor zones
Motors
Variable frequency drives
Diverters
Merges
Scanners
Photo-eyes
Scales
Print-and-apply stations
Accumulation sections
Sorter lanes
Safety devices

SEPARATE STATUS FROM COMMANDS

Use read-only variables for operating information:

Operating state
Speed feedback
Motor current
Zone occupancy
Photo-eye status
Jam state
Fault code
Run hours
Temperature
Energy data

Use controlled commands or methods for authorized actions:

Start line
Stop line
Reset fault
Set speed
Enable route
Assign destination
Release carton
Confirm maintenance mode

Access rights must distinguish monitoring from control. A reporting client may only read data. A WES client may execute approved methods. A maintenance application may require a separate role.

STANDARDIZE STATES

Use consistent state definitions across equipment:

STOPPED
IDLE
STARTING
RUNNING
BLOCKED
JAMMED
FAULTED
SAFETY-STOPPED
MAINTENANCE
MANUAL

Define the transition rules, timestamps, reset requirements, and responsible system for each state.

MODEL EQUIPMENT CAPABILITIES

Represent conveyor functions as operational capabilities. Examples include:

Transport carton
Accumulate carton
Divert carton
Merge flow
Scan identifier
Weigh carton
Apply label
Confirm destination
Report exception

The WES can use these capabilities to coordinate material flow without embedding device-specific logic in the WMS.

ESTABLISH DATA OWNERSHIP

Define ownership for every important data element before integration testing.

DATA ELEMENT	SYSTEM OF RECORD
Customer order	WMS
Inventory balance	WMS
Carton identity	WMS or WES, based on project definition
Conveyor operating state	PLC
Sensor state	PLC
Equipment fault	PLC
Route assignment	WES
Carton movement event	PLC and WES
Order completion	WES to WMS
Inventory transaction	WMS

Avoid duplicate ownership. The WMS should not independently infer a carton’s physical location when the WES and conveyor controls provide verified movement events.

BUILD THE COMMUNICATION FLOW

A standard carton flow can use the following sequence:

WMS releases orders, cartons, and destinations to the WES.
WES validates available equipment and creates material-flow tasks.
WES sends supervisory commands through OPC UA.
PLC starts the required conveyor zones and applies local interlocks.
Scanner or identification equipment reads the carton identifier.
PLC reports sensor, zone, and equipment events.
WES updates the task and selects the next route.
PLC executes the divert or transport function.
WES receives confirmation of the completed movement.
WES sends completion, exception, or rejection data to the WMS.
WMS updates order and inventory records.

Use event-driven communication for significant transitions. Examples include:

Carton detected
Scan completed
Scan failed
Carton released
Carton diverted
Divert rejected
Chute full
Conveyor blocked
Equipment faulted
Order completed

Include a unique identifier, event type, equipment source, timestamp, sequence number, and processing status in each event.

APPLY SECURITY CONTROLS

OPC UA security depends on configuration and operational governance. Establish the following controls:

Separate OT and enterprise networks
Place PLCs and gateways on controlled industrial VLANs
Use firewalls between WES, WMS, and control networks
Manage OPC UA application certificates
Maintain approved trust lists
Restrict write and method permissions
Disable unused services and endpoints
Record configuration changes
Back up PLC, gateway, and HMI programs
Document certificate expiration dates
Test recovery procedures

Use the VDMA OPC UA implementation guide as a reference for information models, security, migration, and industrial communication planning.

OPC UA provides the communication framework. The project team remains responsible for network design, access policy, account management, and operational security.

TEST THE INTEGRATION IN STAGES

Use a staged commissioning process.

FACTORY ACCEPTANCE TEST

Verify:

PLC sequences
Conveyor zone operation
Safety circuits
Sensor response
Jam detection
Divert confirmation
OPC UA namespace structure
Read and write permissions
Method execution
Event timestamps
Fault recovery

SOFTWARE INTEGRATION TEST

Test WES and WMS transactions without production loads.

Verify:

Order release
Carton creation
Destination assignment
Route selection
Duplicate message handling
Communication loss
Delayed event processing
Invalid carton identifiers
Full destination locations
Equipment unavailable conditions
Order cancellation

SITE ACCEPTANCE TEST

Begin with one conveyor zone, lane, or controlled process. Confirm performance before expanding to the complete system.

Measure:

Command response time
Event delivery time
Scanner transaction time
Carton tracking accuracy
PLC processor utilization
Network utilization
Gateway resource utilization
Recovery time after communication loss
Exception handling accuracy

Safety validation remains separate from business-system testing. WMS or WES communication must not bypass the required machine safety architecture.

SELECT THE RIGHT CONTROL PARTNER

Conveying Controls L.L.C. provides electrical control systems for conveyor and material handling applications. Services include:

Full system concept and design
Procurement and specification support
Machine control wiring
Conveyor control wiring
Panel control wiring
Comprehensive schematic drawings
FLA calculations
PLC-based platforms
HMI-based platforms
Special project requests
End-to-end customer service
Exclusive shipping for order protection

With more than 35 years of experience in conveyor controls and material handling applications, Conveying Controls L.L.C. can support the control-system portion of a broader WMS, WES, or system integration project.

Use SUPPORT for project coordination and technical assistance.

INTEGRATION CHECKLIST

Before deployment, confirm:

WMS, WES, and PLC responsibilities are documented
Data ownership is assigned
Conveyor assets are modeled
Equipment states are standardized
OPC UA server placement is selected
Commands and telemetry are separated
Network zones and firewalls are defined
Certificates and permissions are managed
Carton identifiers are consistent
Events include timestamps and sequence data
Communication-loss behavior is defined
Safety controls operate independently
Factory testing is complete
Site testing is complete
Backups and maintenance procedures are available

CONCLUSION

Effective WMS and WES integration requires defined system boundaries, structured industrial control systems, consistent data ownership, and tested communication services.

Use:

WMS for orders and inventory
WES for orchestration and routing
PLCs for real-time conveyor control
OPC UA for structured equipment communication
Secure networks for controlled system access
Staged testing for commissioning and validation

PLAN. MAP. TEST. INTEGRATE.