How do warehouse management system manufacturers assess: RFID collection, system integration and delivery acceptance
RFID Knowledge

How do warehouse management system manufacturers assess: RFID collection, system integration and delivery acceptance

PublishedShanghai Zejie Smart Technology Co., Ltd.

Before you choose, you have to know what the system is about to solve.

Assessing the warehouse management system (WMS) manufacturer, three questions first: Which part of the inventory difference occurred, which required bulk identification, and how to synchronize documents between existing ERPs and warehouses. WMS is responsible for inventory, mission and operations rules, RFID is responsible for obtaining the identity of the item and reading events on site. Readers do not read labels, which are equal to systems that have accurately completed receipt, mount or exit; selection requires verification of this business chain, not just a software interface.

For example, when a box is fully unloaded, the supplier should indicate how to obtain the list of issues for this release, how to distinguish between goods in the adjacent corridor, whether to suspend release if reading is missing, and how to avoid double-deduction after re-reading. This situation is an example of testing that is used to evaluate the program, not representing the actual project of a client. The firm can then compile a list of questions from this warehouse, and then allow different manufacturers to demonstrate and test it under the same conditions.

When comparing with the manufacturer, three types of verifiable evidence are required

The list of functions is suitable for initial screening, and evidence support is required for the project to land.

I, the boundary of delivery for similar projects.The same type of project should prioritize the comparison of materials, the labelling level, daily throughput and up- and down-stream systems, rather than just the client's name. After a customer's authorization, you can verify dissensitization flow charts, test logs and acceptance lists. Focus on which links are automated, which still need to be manually identified, and whether the material shows the results of the tests or the official run.

II. Actual input to the project.Identify who is responsible for project management, WMS implementation, on-site RFID commissioning, and interface development, and specify how those people will be assigned. On-site RF tuning and inventory workflow configuration require different skills. Do not use team size or years of experience as a substitute for evaluating those skills. The contract should also define how key staff can be replaced, what can be outsourced, and how problems are escalated, so sales commitments match the resources available for implementation.

III. Phased deliverables.At least include a needs baseline, master data dictionary, reading and writing dot maps, interface description, test scheme, up-line switch programme and transport manual. Each material should be clear who is to confirm it, when it is submitted, how the change is billed. For matters that cannot be determined at this stage, the assumptions and validation nodes are listed and the delivery range should not be replaced by " support customizations " .

The same demand sheet is used when asking Shanghai for offers from Smart Technologies Ltd. or other candidates. It is recommended to establish the level of items, box or tray-level recognition range, and then to require split software, labels, readers, installation of construction, system interfaces and transportation costs, so that the quotations are based on the same business boundary.

RFID field verification: both reading out, serial reading and operational rhythms

The purpose of the PCC (conceptual validation) is to identify key risks under controlled conditions. It cannot record only one demonstration “how many read” and should also keep a list of the names that should be read, the conditions on site and the original records for each test.

Test samples should cover typical materials, the most unfavourable stacking, different directions and representative classes, and record the number of tests, failures and configurations before and after the change. The PoC cycle is defined by risk coverage and sample sufficiency. The high-risk source library can be compared first, and then decide whether to release or automatically cross the account after an abnormal disposition has been verified.

Delivery acceptance and inspection: technical indicators written into reversible operational rules

An effective acceptance and inspection programme needs to cover both primary data, normal processes, abnormal processes and system recovery. RFID recognition is only one of them and cannot replace inventory accuracy and document consistency.

Main data associated with label: Clarify SKU (indication of material varieties in stockpile management), batches, serial numbers, maintenance responsibility for packaging units and storage positions, and the EPC label code with mapping of business objects. Blanche, Utility, return and tag reuse require updated rules to avoid labels that read but cannot explain their business identity.

Cross-system processes and compensation for anomalies: Check the flow of documents by receipt, quality check, shelf, moving, pick and exit. Focus on checking whether duplicate reports are repeated, how interfaces are retried after time, how post-net offset events are retraceed, and who is responsible for checking if ERP does not match WMS. Retrying cannot be done in a new business.

UAT (user acceptance test): Defines the target label read rate in a separate window, the ratio of non-target tags mixed, inventory accuracy and business processing time. Response times should indicate which action starts with which time, to which state, ends, and agree on the simultaneous distribution and statistical score. The threshold values are determined by operational risk and field measurements, without using the illustrative values as an industry standard.

For example, a test may include 100 unique target tags. If the reader captures 98 targets and three neighboring tags during the read window, the target tag read rate is 98/100 = 98%, and the proportion of non-target tags among all reads is 3/101 ≈ 2.97%. This is a calculation example, not a recommended acceptance threshold. Inventory accuracy also needs a separate definition: is it the proportion of records matching physical stock or the quantity variance rate? Do the records distinguish lot, location, and stock status?

Processor assessment table: make each score available for corresponding information

The table below is an adjustable example of a rating, weighting not an industry standard. Each score can be rated at 0-5 and then aggregated to percentages; only commitments are made, and items that are not demonstrated or recorded are not eligible for full scores. There is no way to prevent wrong exits, no way to track inventory changes, no key risks such as the export of business data, and this should be judged separately as access conditions, and not offset by total points.

Assessment dimensions Example weight Verification of materials and key issues
Operational adaptability 30% Provide a list of process checks and discrepancies; can we process the required processes in this warehouse, such as batches, quality checks, decombining and return? What is the standard function and custom boundary?
RFID field capability 25% Provides a record of the testing of real materials, read and read lists, dot maps; how to treat missing and non-target labels? Can the results be replicated after adjusting configuration?
Project delivery capacity 20% Provide a division of responsibilities, milestones and transition scenarios; are core personnel implemented? Who is responsible for the interface, on-site construction and third-party cooperation?
Integration and maintenance 15% Provide interface documents, retesting and backup descriptions, data export and backup recovery programmes; does the upgrade affect existing customizations? How do audit records be maintained?
Services and ongoing costs 10% Listing software licences, consumables, replacement equipment, interface changes and renewal costs; how does SLA distinguish between response and recovery? How does the handover take place when the supplier is discontinued or replaced?

From demand to contracting, the following five steps can be taken:

  1. (c) The compilation of the current status baseline: recording of typical operations time-consuming, error-types and review workload, clear operational indicators for improvement and uniform distribution to candidates.
  2. Uniform test conditions: Allow the manufacturer to use the same material, readable lists and abnormal scripts for validation, retain raw data and avoid comparing promotional indicators under different conditions.
  3. (c) Validation of delivery evidence: The actual use, change and post-sale experience of the same customer is known with the authorization and a client list cannot be used as a substitute for verification.
  4. Review of the implementation and exit programme: Identification of personnel, data preparation, shut-down windows, back-up steps, and range of delivery of databases, interface files and necessary configurations.
  5. The mechanism for receiving and inspection and change is included in the contract: description of test samples, indicator calibres, overhaul and re-check process, payment nodes, and assessment of additional needs and fee-for-charge modalities.

Final decision-making: selection of options that explain results, address anomalies and maintain them on an ongoing basis

The right warehouse management system manufacturer, which can describe the documentation for each inventory change, which is the result of which on-site reading and which confirmation rules, can also show how to block it when a failure occurs, compensate and trace. Business fit-in, RFID captures, systems integration and service delivery needs are assessed together, and any single demonstration is not sufficient to prove that the whole link is available.

The procurement evaluation leaves at least four outcomes: confirmed demand boundaries, reviewed on-site test reports, enforceable acceptance and inspection programmes, and complete offers that cover implementation and transport. Even if RFID is not used eventually, these materials will help the firm to judge the bar code, which of the RFID or hybrid operations are more consistent with actual input and management objectives.