Get to know RFID.
Properly understanding RFID is not about remembering all the advantages, but about knowing under what conditions it may fail and how to judge when it fails.
A proper understanding means the uncertainty of accepting technology.
Read the label as an observation, and there may be several reasons for not reading.
The system needs to allow for an unknown and pending review status, and should not force the designation of a certain location for each item for the sake of the full screen.
The right-to-know technology also includes knowing that it can't prove anything. It doesn't read that it may come from a mask, from a failure or from the absence of the object, and it does not necessarily mean that the transfer is complete. Separated from business judgement, it allows people to know when they believe in the system and when additional evidence is required.
Identity, gathering events and operational facts to be separated
The RFID link involves at least labels, readers, antennas and operating systems. The tag returns the logo for the search of objects, which results in a wireless observation, which is then interpreted by the business software according to location, time and documentation.
Why the number of times read does not represent the quality of information
One label stays in the reading area, which can generate many repetitions of observations; the other is always blocked and may not have any record. The original number increases, without representing a more complete object cover. The software needs to combine observations with mission-generated events and distinguish between non-observed objects that are not observed. If the binding relationship is wrong, even if wireless communication is fully normal, it stabilizes the wrong output. The quality of the system should therefore at least take into account the three layers of the chain, identity and event, so that one layer cannot be endorsed by another.
Re-examine the programme from an exception
When the target is not read, the interface only shows " missing " . Users may mistakenly believe that it has been proved lost. A more accurate state should include unobserved, pending review and confirmed anomalies. Recognizing that unknown is not a system retreat but rather avoid packaging in to a definitive conclusion of insufficient evidence.
Put your judgment in the real situation.
The test set is supplemented by a mask, mistaste and missing data, the system is checked for honesty in expressing uncertainty and review is referred to the appropriate person.
It is recommended to write how the object identifiers are allocated, who binds and how the labels are used to continue history, and then design a collection point.
Let's look at the input and the results.
| Observation dimensions | Evidence to be retained |
|---|---|
| Object Identity | Is the coding tied to the object? |
| Collection of evidence | Keep reading points, times and original results |
| Closed business circle | Whether anomalies can be reviewed, corrected and traced |
| This is the key trade-off. | Is a system that always shows answers more reliable than a system that can justify insufficient evidence? |
It's worth asking.
Is a system that always shows answers more reliable than a system that can justify insufficient evidence?

Ms. Lei
Mr. Pang