An 自動倉庫・搬送システム only creates value when the right software tells the right machine to move the right pallet at the right moment. Buyers often spend months comparing shuttle speed, rack layout, and crane cycles, then discover that the real project risk sits in the integration layer between the warehouse management system, the warehouse control system, and the automation hardware. This guide explains what each system does, where integration breaks, what architecture choices matter, and what to put in a supplier evaluation checklist before you sign.
What ASRS, WMS, and WCS Each Control
An ASRS is not a single brain. It is a stack of control layers, and each layer makes different decisions at different speeds.
| Control layer | Typical system | Primary responsibility | Integration data |
|---|---|---|---|
| Business/planning | WMS | Orders, inventory, slots, replenishment, labor priorities | SKU master, order wave, putaway rule, inventory status |
| Execution/orchestration | WES/WCS | Task assignment, equipment routing, traffic, exception handling | Transport order, destination, priority, release triggers |
| Equipment control | ASRS controls + RCS | Robot dispatch, motion control, sensor events, safety | Position, status, load presence, fault codes |
The WMS is the planning brain. It decides what should move and why. A warehouse control system decides how a group of machines should execute that movement. The ASRS and its robot control system execute the physical pallet movement. The closest formal model for this separation is the enterprise-control integration hierarchy defined in ISA-95, which divides business planning, operations management, and real-time equipment control into distinct activity domains [1].
This distinction matters because each layer has a different failure mode. A WMS error usually affects data or planning. A WCS error blocks material flow. An ASRS fault stops physical movement. A buyer must therefore evaluate integration quality, not only the features of each individual package.
Why Integration Is Where Automation Projects Stall
Industry research consistently places software integration, data quality, and workforce readiness among the top risks in automation adoption [2]. The reason is straightforward: an ASRS can only execute what the upstream systems describe cleanly. If the WMS uses a different pallet master, a different unit of measure, or a different location hierarchy than the WCS expects, the project needs expensive custom mapping.
The most common failure points include duplicate or conflicting master data, missing exception workflows, unclear ownership of task cancellation, inconsistent barcode or RFID rules, and custom interface code that becomes unsupported after go-live. These are not dramatic failures. They appear as small delays, manual overrides, and falling throughput after launch.
Most integration failures trace back to software boundaries, not robot hardware.
Integration Architectures: From Interfaces to Unified Platforms
There are three common ways to connect ASRS equipment to warehouse software.
Model A: WMS to WCS with direct equipment control. The WMS releases orders to a WCS, and the WCS directly manages conveyors, shuttles, lifts, and stacker cranes. This works for focused projects but can become brittle when new equipment or workflows are added later.
Model B: WMS to WES to WCS/RCS. A warehouse execution system inserts an orchestration layer between planning and equipment control. This is useful in high-volume, multi-process operations where order release must be optimized across picking, replenishment, and inbound tasks.
Model C: Unified WMS/WES/WCS/RCS platform. One software suite manages planning, execution, equipment control, and robot control. Fewer interfaces mean less data translation and fewer support boundaries. Zikoo’s PTPスマート倉庫ソフトウェアcURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits 四方向シャトル cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
| Area | 確認すべきポイント |
|---|---|
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| シミュレーション | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| 拡張性 | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
よくある質問
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
What interface standards should we require in an RFP?
Require at least these deliverables: an interface control document, message sequence diagrams for inbound, outbound, replenishment, and exception flows, a defined data model, a simulation or emulation plan, and a service-level response for interface issues. You do not need to mandate a specific protocol as long as the supplier defines versioned, testable, and supportable interfaces.
How long should integration testing take?
The duration depends on the number of systems and the quality of the master data. A focused single-vendor ASRS integration may require several weeks of testing. A multi-vendor project with ERP, WMS, WCS, and automation equipment can take months. Only accept a go-live date after interface testing, functional testing, and a full-volume rehearsal are complete.
What happens to operations during system integration?
A phased or brownfield transition can keep parts of the warehouse operating while the new ASRS is installed and tested. The supplier should explain how existing inventory will be moved, how system cutover will run, and what manual procedures will cover the period when the old and new systems operate in parallel.
参考文献
[1] ANSI/ISA-95.00.01-2018, Enterprise-Control System Integration — Part 1: Models and Terminology, ISA.
[2] MHI Annual Industry Report 2024, The Collaborative Supply Chain: Tech Investment and Workforce Transformation, MHI/Deloitte.
[3] EN 528:2008, Rail dependent storage and retrieval equipment — Safety requirements, CEN.
[4] ISO 3691-4:2020, Industrial trucks — Safety requirements and verification — Part 4: Driverless industrial trucks and their systems, ISO.
興味があれば、これらの関連記事もご覧ください：
六方向シャトルが倉庫のアップグレードを推進し、インテリジェントな自動3D倉庫を構築
スタッカークレーン対フォーウェイシャトル：あなたのASRS倉庫に最適なのはどちら？
Six-Way Shuttle：高密度ストレージ向けのデュアルエンジンソリューション
