Wms Warehousing Management System presentation, WCS and RFID hardware synergetic architecture resolution
RFID Knowledge

Wms Warehousing Management System presentation, WCS and RFID hardware synergetic architecture resolution

PublishedShanghai Zejie Smart Technology Co., Ltd.

Introducing the WMS warehouse management system, if only the WMS were compared to the "brain," the WCS were compared to the "hands and feet" and the RFID was easily missing the most important issue in implementation: who is entitled to confirm receipt after a tray has been read? The equipment received removal assignments, can stock be moved to target storage immediately? When the network is disrupted, the goods have moved and how will the account be restored? Understand this architecture, it should be unset along a single line of business, "identify, make decisions, execute, confirm" four things, not simply string three product names.

I. Clearing up responsibilities: System names cannot replace interface boundaries

In the structure discussed here, WMS is responsible for the rules of storage operations and inventory confirmation, while WCS is responsible for the implementation coordination of automated operations, and RFID collects layers provide evidence of target identification. The functional cross-cutting of the actual product: some WMS self-contained equipment access modules, others have already been part of a local task schedule, so solicitation and design should be assigned to each function and cannot be extrapolated by system abbreviations alone.

Level Questions to answer There's no way to draw conclusions.
WMS Business Level Availability of goods, target storage allowed, when receipt and dispatch confirmed or moved The interface request cannot be considered as having been physically moved directly
WCS Executive Coordination Level Tasks that need to be carried out, how equipment is handed over and which tasks are to be held up “Deliverable conditions are met” cannot be replaced by “Equipment received”
Device Control Layer Whether the actions of the transport, lift or other institutions and the conditions for the chain are met No security stoppage or personal protection responsibilities could be relied on for common business interfaces
RFID Collection and Event Management Level Which label is read in what reading area, when, which object and task are relevant A first reading cannot independently prove the quantity, movement or final storage of the goods

Manual warehouses can use WMS bar code or RFID handheld terminals, and do not necessarily require a stand-alone WCS; automation equipment can also combine bar codes, and photoensor and device location feedback is not impossible without RFID. The introduction of RFID should have clear business reasons, such as reducing manual scanning of whole-to-place connections, or identifying revolving loads, rather than a set of structures.

II. Distinguishing between “read” and “completed” by a tray-mounted task

The following is an example of a process design, not a client project.Tray P001 is in the pick-up hold and plans to be mounted to ZA-02-03. P001 is an internal load number that cannot be directly coded as a standard EPC example. The system has created a map of the tray tags and the identity of the carrier, and has kept this loaded shipment, batch and quantity; if only the tray is marked, the details of the goods that are checked after reading the tray are from the loading relationship, not the result of this case-by-case identification.

  1. Checking identity:The RFID collects labels, the event layer confirms that the label is valid, the reading area is currently working and is associated with the tray in operation. Unknown tags or adjacent areas read in a series of boxes, which do not directly create receipt records.
  2. Development of operational tasks:WMS checks receipt, quality and stock status, verify target storage capacity and storage rules, generate upscaling tasks and reserve targeted resources as agreed.
  3. To receive and execute:WCS confirms the acceptability of the mission, arranges for transport and transfer of equipment. Returning “received” only means that the mission is in the performance area and that the tray should not be recorded directly as being mounted at this time.
  4. Feedback completes evidence:When the device is completed, the object, actual destination, and result and anomaly. Without a library RFID reading point, complete evidence can be derived from a verified equipment status and contact signal, it should not create a "full-range radio frequency position".
  5. Identification of stockpiles:WMS verification missions remain valid, the target is consistent with destination and the corresponding completion events have not been addressed, confirming the location of the inventory and releasing the resources reserved.

The inventory can be displayed as “moved bank” during execution, while maintaining the departure location, planned destination and recently confirmed position. What stocks are allocated to new orders requires clear business rules. Covering the “last read place” directly into “account space”, may result in duplicate distribution of goods on the delivery line.

The interface will be designed for the status machine and then HTTP or message queue.

A commingled protocol should at least define the task number, object number, end point, priority, task version, message number, time, state and error code. The external interface also requires a default, time out, retry, retention period and query mode. HTTP response successfully, message into queue, device acceptance command, physical action end, WMS confirmation inventory is confirmed at different levels, cannot be merged into an ambiguous "success."

You can classify a mission as receiving, accepted, in the process of implementation, completed, failed, cancelled pending confirmation and cancelled, and agree to allow a state move. This is an example of design that allows the project to adjust its status name, but not to omit the intermediate status of "the request for cancellation has not yet been effected". Once the WMS has been cancelled, the device may have reached a transfer that cannot be immediately suspended; until the WCS confirms the cancellation or physical completion, WMS cannot release all resources directly and send conflicting new assignments.

The same operational identifier should be used to re-test the same job, so that the duplicate of the same version returns the result, rather than creating a second task. The event is also processed in terms of thorium; but the other legal transfer library must be performed on the next day with the same tray, and it cannot be permanently weighed by the same tray number. For an unsequenced event, the task version and status conditions should be checked, and the late "in-progress" should not cover completed status.

IV. HOW THE RFID READING QUIET IS Credible OPERATIONAL

It is advisable to keep original label values, reader and antennas, read time, read area and context of the task, and then generate a candidate event for your business. The number of readings does not equal to the number of articles, and the same tag stays on the side of the channel may be reported repeatedly. The event layer can aggregate reading numbers in the operating window, but whether the goods are passed and allowed into the library still needs to be determined by a trigger signal, operational status and validated field rules.

RSSI cannot directly replace the space of the library. Antenna direction, label location, cargo material and on-site reflection affect the reading area; power enhancement may be added to target labels or can lead to neighbourhood labels. The antenna selection should combine coverage areas, labels are directed towards applications, etc. The field test is conducted while preparing the target goods and uncounted neighbourhood goods, rather than just displaying " how far can read as far as possible." [1]

Distinguish two kinds of protocols when connecting equipment: the air interface between tag and reader, and the interface through which the reader uploads data and receives configuration. Gen2 handles over-the-air communication in passive UHF systems, for example. LLRP, vendor REST interfaces, and SDKs connect readers to applications. Supporting a tag protocol does not mean a device can connect directly to the existing WMS receiving and inventory interfaces.[2][3]

When cross-systems are required, reference can be made to the incident expression of GS1 EPCIS, to the object, time, location and operational context.[4] Reference to this semantic will help parties interpret the same record, but does not imply that all project in a warehouse must purchase an additional EPCIS platform.

The hardest thing to recover after the netting is "the goods moved but lost"

P001 is assumed to be in target position, and WMS has not received completion notification. This time, a complete removal order can be reissued, the task will fail or the repository may be released by mistake. The recovery process should first search for the end-state of the execution end by task number, then check the device or handover record. If it can be confirmed that it was completed, attach the same completed event; if it remains unconfirmable, enter the controlled manual verification, no actual location can automatically be presumed from the excess.

Interface design uses local durability, records to be sent, confirmation and retesting, and regular business reconciliation mechanisms. Reconciliation should check mission end-state, tray location, consistency of inventory changes and resource retention, rather than only a total of the amounts in the database. How long is the equipment ' s end-of-the-life record kept, how long will it take for the system to recover, what type of data to allow to be lost, and also agreed before acceptance.

When an unidentified, failed handover or conflict of destination is detected, you shall wait for the equipment to be designed to enter, quarantine or other secure and controllable state. People's protection, stop and locking are subject to appropriate security design guarantees, and normal WMS, WCS business messages cannot replace these mechanisms. The software shows "taught-out" -- not a permit for people to access the dangerous area of the equipment themselves.

VI. ACCOUNT AND AUDIT NOT JUST RESIDED THE STRATEGIC,

When assessing response time, the delay in collection, delays in receiving equipment, delays in physical handling and delays in inventory confirmation, indicate starting point and load conditions. Write a millisecond response to an interface into a whole library, which is not of reference value for design and procurement.

VII. Order of implementation: complete and expanded business chain

The pilot can first select a switchpoint, a label adhesion and a complete library path, complete identity binding, task execution, abnormal processing and inventory reconciliation. Only normal and faulty processes explain clearly are they suitable for increasing the channel, equipment or type of goods. The procurement judgement should also look at the business metametry, the error cost, the complexity of managing the particle size and automated interface, rather than the daily order.

The delivery should contain a job matrix, object and library dictionary, task profile, interface and error code, read-area test logs, fail-recovery manual and acceptance evidence. The structure is reliable, ultimately reflected in the condition of a tray, why the system judge this, and who recovers after an anomaly has clear answers.

Technical information and illustrative notes

This document has a task number, state name, acceptance scripts and processes that are designed to be illustrative of the client case, equipment performance or product boundaries of all manufacturers. Technical information: [1] Impinj "Choosing the Right RIAN RFID Reader Antenna for Your Solution " ;[2] GS1 "EPC UHF Gen2 Air Interface Protocol " , used to distinguish between labeled aerial communications; [3] Impinj, RIAN RFID Reader IoT Dévice Interface for Assistance Development, used to understand the equipment side interface with LLRP;[4] GS1 What is Electronic Production Code Standards? (EPCIS) for the description of business event syntax. The reference criteria cannot be a substitute for project interface engagement and on-site validation.