ABNET WCS Architecture

Saga reference architecture: WMS integration, ABNET WCS flow control, and execution through MFC, PLCs, and automation equipment.

From management to physical execution

WMS

Manhattan / SAP

APIs / messages

ABNET WCS · Saga

Routing
Buffer management
Tracking
Exceptions
Priorities
Monitoring

MFC / equipment interfaces

PLC

Conveyors

PLC

Sorters

PLC

AS/RS storage

Logical reference diagram, not a network or safety topology. MFC may be part of WCS or a separate layer. PLCs control equipment; commands and events travel in both directions. Manhattan and SAP are examples of WMS systems: interfaces and versions are defined for each project.

WMS: orders, inventory, and priorities

The WMS determines what needs to happen: tasks, destinations, and business priorities. It manages inventory and processes while WCS coordinates their execution in automation.

APIs and messages: integration contract

Identifiers, fields, validation, commands, and states form the contract between systems. Message receipt does not mean physical task completion. Correlation, duplicate detection, and retry rules must be defined in the integration.

ABNET WCS: flow coordination

Saga connects WMS requirements to operating conditions. The functions below organize flow decisions and supervision; details depend on project configuration and scope.

MFC: execution coordination

Material Flow Control translates flow decisions into interactions with equipment controls. Its separation from WCS depends on the installed architecture; an additional layer is not mandatory.

PLCs and MHE: local control and movement

PLCs execute local device logic. MHE is the physical equipment, such as conveyors, sorters, and AS/RS systems. Interlocks, safety, and motion control remain within the layers responsible for these functions.

Event feedback and reconciliation

Passage events, states, and failures return from automation to WCS. Agreed information is relayed to WMS. After an interruption, the design needs to reconcile pending tasks, logical states, and physical conditions.

WCS layer functions

Routing: Select paths and destinations according to rules and availability.
Buffer management: Coordinate accumulation, occupancy, and release between stages.
Tracking: Associate cartons, tasks, positions, and passage events.
Exceptions: Handle deviations, failures, and situations requiring intervention.
Priorities: Apply priorities to flow sequencing and release.
Monitoring: Provide visibility of operational states, events, and incidents.

Discuss your project architecture Understand WMS × WCS integration

Illustrative specification model. Responsibilities and mechanisms are defined for each project.

Authority matrix: decision ownership and evidence

Start integration with an authority matrix. For each decision, name the component allowed to change it, the required evidence and behavior when information is unavailable. This is a reference division: a separate MFC may own WCS flow functions, provided there are no competing owners.

Authority matrix: decision ownership and evidence
Decision	Reference authority	Evidence and boundary
Business destination and priority	WMS / agreed orchestration	Valid demand and constraints; no permission to override an interlock.
Admission and capacity reservation	WCS/MFC flow coordination	Occupancy plus approaching reservations; one slot cannot be promised twice.
Local movement	Equipment controller	Handshake, mode and interlocks; safety remains in the machine architecture.
Logistics completion	WCS reports; WMS records the business effect	Load identity and delivery at the agreed point, not merely a sent command.
Discrepancy correction	Authorized operational procedure	Operator, reason and evidence; retain the original task and events.

Read the complete technical guide →