CSL CS101-2 EPC CLASS 1 GEN 2 RFID HANDHELD READER
USER'S MANUAL, VERSION 1.0
Copyright © Convergence Systems Limited, All Rights Reserved
187
11.2.2 Integration Process
11.2.2.1 Use Cases and Requirements Gathering
Before starting the development process, system integrators should fully understand the
requirements from customer, such as the throughput requirement, latency requirement,
bandwidth requirement. etc, that are specific to the reader. Besides, they could document the
use cases which will help in decision making later on in the development process.
11.2.2.2 Draft Solution and In-House Testing
Once the requirements are gathered and use cases are defined, system integrators can develop a
draft solution. Draft solution means that it is subjected to final adjustment or tuning after pilot
testing. In-house testing allows system integrators to test the feasibility of the solution before
deploying to customer’s site.
11.2.2.3 API Programming
The API Programming process here is different from the one in Familiarization Process. In
Familiarization Process, system integrators should familiar with the configurations and
functioning modes of the reader by using the API. In System Integration Process, they should
determine and focus on the configurations and functioning modes to be used in the solution to
fulfill user requirements.
11.2.2.4 Pilot Testing
RFID system is greatly affected by environmental factors. For example, background RF noise
and metallic object around may affect the read range of antenna dramatically. The same RFID
system may function well in the system integrator’s own office but fail in end-customer’s site.
Therefore system integrators should conduct on-site pilot testing.
During the on-site pilot testing, system integrators should tackle the site-specific problems that
affect the RFID system. For example, if there is metallic object around, position of the antenna
