RFID-ROI-SME ICT-PSP No. 250438 RFID-ROI-SME … deliverables/RFID-ROI-SME-D3.1-v2.0.pdf ·...

RFID-ROI-SME – ICT-PSP No. 250438

PROPRIETARY RIGHTS STATEMENT This document contains information, which is proprietary to the RFID-ROI-SME Consortium. Neither

this document nor the information contained herein shall be used, duplicated or communicated by any means to any third party, in whole or in parts, except with prior written consent of the consortium

RFID-ROI-SME DELIVERABLE

D3.1

“Hardware Specifications

and Configuration”

Project Acronym RFID-ROI-SME

Grant Agreement No. 250438

Project Title Pilot RFID Deployments and ROI Studies for SME using Open Source Middleware and Tools

Deliverable Reference Number

RFID-ROI-SME-WP3-D3.1

Deliverable Title Hardware Specifications and Configuration

Revision Number V2.0

Deliverable Editor(s) SENSAP (Panos Dimitropoulos, Nikos Zarokostas)

Authors / Contributors CABLECOM, SERO, BKS, RFID-SPE, ALU

Project co-funded by the European Commission within the ICT Policy

Support Programme

Dissemination Level

PU Public

Statement of originality:

This deliverable contains original unpublished work except where clearly indicated otherwise. Acknowledgement of previously published material

and of the work of others has been made through appropriate citation, quotation or both.




Revision History

Rev. Author(s) Organization(s) Date Changes

V0.01 N. Zarokostas, P.

Dimitropoulos SENSAP

14/06/

10 Table of Contents

V0.02

N. Zarokostas, P.

Dimitropoulos,

Rita Westergaard

SENSAP, SATA,

RFID-SPE

30/06/

10

Addition of SATA and RFID-SPE

Contributions


Dimitropoulos SENSAP, BKS

05/07/

10

Addition of BKS Contribution,

Addition of the introduction

V0.04 P. Monari RETE, BRIDGE 16/07/

2010

Incorporation of Hardware for the

BRIDGE and RETE pilots

V0.05 P. Dimitropoulos SENSAP 21/07/

2010

Addition of Bill-of-Materials for

KOSKINDIS and STAFF pilots

V0.06 S.Bains SERO 22/07/

2010

Addition of Security Systems pilot

hardware

V0.07

N. Zarokostas, P.

Dimitropoulos, P.

Bozhkova

SENSAP, Balkan 26/07/

2010

Update of the BALKAN

Contribution, Fine-Tuning of the

Document


Dimitropoulos SENSAP

13/08/

2010 Proof-Reading and Corrections


Dimitropoulos SENSAP, ALU

26/08/

2010

Integration of contribution from

ALU group


Dimitropoulos SENSAP, BALKAN

27/08/

2010

Integration of revised contribution

from BALKAN


Dimitropoulos SENSAP, STAFF

30/08/

2010

Incorporation of comments from

quality control (by STAFF)

V0.12

N. Zarokostas, P.

Dimitropoulos,

Paola Monari,

Rita Westergaard

SENSAP, STAFF 09/09/

2010

Incorporation of comments from

quality control (by SERO)

V0.13

N. Zarokostas, P.

Dimitropoulos,

Paola Monari

SENSAP 06/12/

2010

Inclusion of diagrams requested

from the reviewers during the first

EC review of the project

V2.0 08/12/

2010 Second Submission




From ANNEX I to the review report – Assessment of deliverables

No. Title Status Comment

3.1 Hardware Specifications &

Configuration

Approved

subject to revisions

Revisions concern including a

Configuration diagram for (i) the automated document tracking pilot project (ii) intelligent manufacturing

project (iii) the inter-enterprise apparel logistics and (iv) the security systems

pilot.

Revisions made:

Inclusion of the following figures:

Figure 3: RETE pilot physical configuration

Figure 6: Physical Configuration of the AutoID Printer at

KOSKINIDIS

Figure 7: Physical configuration of the mobile readers of the

KOSKINIDIS solution

Figure 9: Physical configuration of the hardware comprising the STAFF pilot (retail part)

Figure 10- High-Level physical configuration of the hardware equipment for the Security systems pilot

Review and update of the STAFF equipment, in terms of missing (in the previous version) fixed readers.




Abstract

The purpose of this deliverable is to describe the hardware requirements

for each one of the eight pilots that are organized and deployed in the scope of the RFID-ROI-SME project. Hardware requirements are mainly illustrated in terms of RFID/AutoID equipment, but also in terms of

auxiliary hardware devices required (such as sensors, actuators and networking devices). In several cases/pilots, hints for the configuration of

RFID hardware are provided, in terms of protocols, standards and other configuration options. The equipment listed in this deliverable will provide the Bill-of-Materials required by SME end-users in order to proceed with

the related equipment procurement processes. At the same, the specification of the required hardware signals an important step in the

pilots deployment process, given that it is a key prerequisite for on-site deployment and testing of the hardware.

RFID-ROI-SME: Pilot RFID Deployments and ROI Studies for SME using Open Source Middleware and Tools

WP3- RFID Systems and Solutions Technical Specification Deliverable D3.1: “Hardware Specifications and Configuration”

5/45

Table of ContentsRevision History ............................................................................... 2 Abstract .......................................................................................... 4 Table of Contents ............................................................................. 5 List of Figures .................................................................................. 7 List of Tables ................................................................................... 8 Executive Summary .......................................................................... 9 1. Introduction ............................................................................. 10 2. Cable trading logistics Pilots ....................................................... 13

2.1 Hardware Specifications ........................................................ 13 2.1.1 RFID/AutoID Devices .................................................... 13 2.1.2 Networking Equipment .................................................. 14 2.1.3 Computing Equipment ................................................... 14

2.2 Hardware Configuration ........................................................ 14 2.2.1 Protocol /Interface to AutoID Devices .............................. 15 2.2.2 Physical interface .......................................................... 15 2.2.3 Networking Configuration .............................................. 16 2.2.4 Computational Devices Configuration .............................. 16

3. Pilot on electronic tickets for VIP guests ...................................... 17 3.1 Hardware Specifications ........................................................ 17

3.1.1 RFID/AutoID Devices .................................................... 17 3.1.2 Networking Equipment .................................................. 17 3.1.3 Computing Equipment ................................................... 17

3.2 Hardware Configuration ........................................................ 17 3.2.1 Protocol /Interface to AutoID Devices .............................. 18 3.2.2 Physical interfaces and Networks .................................... 18 3.2.3 Computational Devices Configuration .............................. 19

4. Pilot on automated document tracking ........................................ 20 4.1 Hardware Specifications ........................................................ 20

4.1.1 RFID/AutoID Devices .................................................... 21 4.1.2 Sensors and Actuator .................................................... 22 4.1.3 Networking Equipment .................................................. 22 4.1.4 Computing Equipment ................................................... 22

4.2 Hardware Configuration ........................................................ 22 4.2.1 Protocol /Interface to AutoID Devices .............................. 22 4.2.2 Physical interface .......................................................... 22 4.2.3 Networking Configuration .............................................. 22 4.2.4 Computational Devices Configuration .............................. 23

5. Pilot on safety on building working sites ...................................... 24 5.1 Hardware Specifications ........................................................ 24


5.2 Hardware Configuration ........................................................ 27 5.2.1 Protocol /Interface to AutoID Devices .............................. 27 5.2.2 Physical interface .......................................................... 27 5.2.3 Sensor/Actuators Interfaces ........................................... 28



6/45

5.2.4 Networking Configuration .............................................. 28 5.2.5 Computational Devices Configuration .............................. 28

6. Pilot on intelligent manufacturing for the paper industry ................ 29 6.1 Hardware Specifications ........................................................ 29

6.1.1 RFID/AutoID Devices and Computing Equipment .............. 29 6.1.2 Networking Equipment .................................................. 31

6.2 Hardware Configuration ........................................................ 31 6.2.1 Protocol /Interface to AutoID Devices .............................. 31

7. Pilot on plastic film industry ....................................................... 32 7.1 Hardware Specifications ........................................................ 32


7.2 Hardware Configuration ........................................................ 35 7.2.1 Protocol /Interface to AutoID Devices .............................. 35 7.2.2 Physical interface .......................................................... 35 7.2.3 Sensor/Actuators Interfaces ........................................... 35 7.2.4 Networking Configuration .............................................. 36 7.2.5 Computational Devices Configuration .............................. 36

8. Pilot on inter-enterprise apparel logistics ..................................... 37 8.1 Hardware Specifications ........................................................ 37

8.1.1 RFID/AutoID Devices and Computing Equipment .............. 37 8.1.2 Sensors and Actuators .................................................. 39 8.1.3 Equipment deployed/available at the STAFF central warehouse ............................................................................... 40


9. Pilot on security systems ........................................................... 43 9.1 Hardware Specifications ........................................................ 43

9.1.1 RFID/AutoID Devices .................................................... 43 9.1.2 Sensors and Actuators .................................................. 44 9.1.3 Networking Equipment .................................................. 44 9.1.4 Computing Equipment ................................................... 44


10. Conclusions ......................................................................... 45



7/45

List of Figures Figure 1: High-Level physical configuration of the hardware equipment for

the CABLECOM pilot ........................................................................ 15 Figure 2: Logical Architecture of the Ticketing Pilot ............................. 18 Figure 3: RETE pilot physical configuration ......................................... 21 Figure 4: Basic Configuration of the BRIDGE pilot hardware devices ...... 25 Figure 5: Ethernet Networking between the devices of the Pilot ............ 28 Figure 6: Physical Configuration of the AutoID Printer at KOSKINIDIS ... 30 Figure 7: Physical configuration of the mobile readers of the KOSKINIDIS solution ......................................................................................... 30 Figure 8: Physical Configuration of the hardware of the PICDA pilot ...... 35 Figure 9: Physical configuration of the hardware comprising the STAFF

pilot (retail part) ............................................................................ 39 Figure 10- High-Level physical configuration of the hardware equipment

for the Security systems pilot ........................................................... 43



8/45

List of Tables Table 1: Default Configuration of the selected hardware for the CABLECOM

pilot .............................................................................................. 15 Table 2: RFID and computing equipment to be purchased and used in the scope of the KOSKINIDIS pilot ......................................................... 30 Table 3: RFID and computing equipment to be purchased and used in the scope of the STAFF pilot .................................................................. 38 Table 4: Bill-of-Materials (BOM) for the equipment at the STAFF central warehouse ..................................................................................... 42



9/45

Executive Summary The main objective of the RFID-ROI-SME project is to organize, integrate,

deploy and evaluate eight RFID/AutoID technology pilots spanning different sectors, business cases and geographical locations. The hardware that will support these pilots is among the most critical components of the

pilot deployment. As a result, hardware selection is a cornerstone task for the pilots and an important task in the project’s workplan. Furthermore,

the way this hardware is configured is also important for a successful deployment.

The present deliverable presents the hardware specification and

configuration for each one of the eight RFID-ROI-SME pilots. The equipment specifications are (for each one of the pilots) organized in the

following categories:

o RFID/AutoID Devices.

o Sensors and Actuators.

o Networking Equipment.

o Computing Equipment.

Note that some pilot sites possess legacy equipment that obviates the need for purchasing equipment in one or more of the above categories. In

this case, a brief reference to the equipment to be used is made, rather than a detailed specification. Moreover, some pilots do not require additional sensing and/or actuating equipment, which obviates the need

for the specifications in the respective category.

In addition to equipment specification, the deliverable reports on the main

configuration options to be applied in each pilot in terms of supported protocols, interfaces, as well as configuration parameters for RFID, computing and networking devices. These options provide a starting point

for the hardware installation and testing activities. Nevertheless, it is likely that these options will be fine tuned during the actual pilot deployment

and operation.

In the scope of the deliverable each pilot site representative has provided a Bill-of-Materials concerning the equipment of the pilot. In most of the

pilots this Bill-of-Materials includes the hardware that will be ultimately used in the pilot, as well as in the possible operative system at the end of

the project. However, some sites (such as KOSKINIDIS, RETE, BRIDGE and STAFF) are likely (in subsequent phases of the project) to replace specific equipment unit with other (functionally equivalent) devices. Such

replacement may occur as a result of the on-site equipment tests, or even (at later stages) based on feedback from the actual use of the system. It

is also noteworthy that some sites have (at this stage) reported on alternative configuration options, with a view to finalizing them in subsequent stages of the project.

Overall the present deliverable will serve as a practical reference guide for the procurement processes at the various sites, while at the same time

provide insights for the successful hardware configuration.



10/45

1. Introduction The main objective of RFID-ROI-SME is to organize, deploy and evaluate

eight RFID technology pilots across six European countries and different application domains. One of the main elements of the pilot deployment concerns the selection and configuration of the hardware of the pilots. In

particular, each pilot deployment comprises a number of hardware devices including RFID readers, sensors, actuators, computing equipment,

networking equipment and more. Furthermore, these hardware devices feature different configurations, according to the functional requirements of each pilot.

The purpose of this deliverable is to describe the hardware specifications

and associated hardware configurations of the various RFID pilots. The description of the specifications is performed separately for each individual

pilot. The hardware requirements outlined in this document will be then used to structure bill-of-materials (BOM) for each pilot. Based on this BOM the various will order the hardware to be used in the pilot. As a result, the

present document will serve as a basis for acquiring the hardware required for each one of the pilots. To this end, each of the pilot sites will

proceed with the related procurement processes, which constitute a distinct and important step in all the pilot projects’ plans. The procurement processes will be mainly carried out by the end-users, given

that end-users will own the hardware beyond the end of the project. However, not all the hardware devices will be charged to the RFID-ROI-

SME project, since end-users and solution providers are likely to leverage legacy equipment and devices.

In addition to boosting the procurement processes, the present document will provide a basis for configuring the hardware in the scope of each pilot

deployment. In particular, the deliverable will provide a set of baseline parameters for the hardware deployment, which will be further processed and elaborated during the pilot deployment. The configuration of the pilot

hardware includes also the specification of the device protocols and capabilities to be used during the pilots.

In terms of the hardware specifications description methodology, the deliverable reports the requirements at a per pilot basis. For each pilot the

specifications are structured based on the following categories: RFID (Radio Frequency IDentification) /AutoID (Automatic

Identification) Devices: This category refers to the AutoID equipment to be used in each pilot including readers, printers, scanners and antennas. The deliverable reports the use of each

required device in the scope of the pilot. Note that RFID devices (such as RFID interrogators) are among the most prominent and

indispensible hardware elements of the pilots. Sensors and Actuators: This category refers to the sensors and

actuators to be used in the pilot including temperature sensors,

cameras, conveyor belts, photo-eye reflectors and stack lights.



11/45

Additional sensors are frequently required in order to implement

ubiquitous added value sensing features, which usually involve fusion of the RFID tag data streams with the sensor data. A prominent example is the BRIDGE pilots, where RFID data are fused with camera

data. Likewise, actuators are needed in order to appropriate blend RFID in existing business processes. For example conveyor belts are

among the most common actuators used to support logistics processes, such as receiving and shipping products. It should be however noted that some of the pilots do not have any special needs

for additional sensing and actuating equipment. Networking Equipment: Refers to the equipment that lays out the

basic networking infrastructure of the pilot. This includes switches, routers, wireless bridges and port converters. Note however that several pilots are likely to rely on legacy networking equipment, rather

than purchasing new networking devices exclusively for the purposes of the pilot.

Computing Equipment: This category refers to the computing devices to be used, including dedicated servers, storage servers, desktops, laptops, thin clients and mobile terminals. These computing

devices will serve as the hosts that will receive and possess the RFID data streams for the RFID readers.

In terms of hardware configuration, the deliverables illustrates

configurations on the basis of the following classification: Protocols and interfaces to AutoID Devices: This category refers

to the means of communication with the AutoID device(s) including

message bindings (e.g., based on EPC-LLRP and ISO protocols), as well as transport binding (e.g., based on the HTTP and TCP protocols).

Physical interfaces: This category refers to the physical interface(s) to the AutoID devices, such as Ethernet, RS232, USB and Bluetooth.

Sensor and actuators interfaces: This category illustrates the

means of interconnection between sensors/actuators and related AutoID or computational equipment used on the pilot.

Networking Configuration: The respective configuration lists any pertinent details of the networking configurations to be used.

Computational Devices Configuration: Refers to configuration

details of the computational devices, in terms for example of the operating system and RAM memory configuration used.

Note however that for several solutions the above configuration options have not been determined yet, since they are part of later stages of the solution design. Furthermore, they also depend on other technical

parameters such as selection and configuration of the middleware. Hence, in various pilot descriptions the above-listed hardware configurations are

not reported. The above classifications provide a common basis for the description of

hardware specifications and configurations. However, there are not exhaustive. Specific pilots provide additional requirements not directly

associated with the above categories. Furthermore, not all pilots have requirements and/or configurations falling in the above categories. For



12/45

example, some of the RFID-ROI-SME pilots do not have requirements for

additional sensors and actuators. It is also noteworthy that some solution providers (e.g., SATA) are

currently deploying and testing on-site alternative configurations. For these cases the deliverable reports both alternative options, with a note

that the final selection is still pending. Also, as a short disclaimer, we must emphasize that the present deliverable is confined to the description of the hardware, without delving into details about objectives of each pilot

and the business processes entailed in the pilot deployment. A thorough description of the pilots (in terms of objectives, goals, business processes

and key performance indicators) are provided in other deliverables of the project.

The deliverable is structure as follows: Section 2 following this introductory paragraph lists hardware requirements and related

configuration options for the cable trading logistics pilot in Bulgaria. Likewise, Section 3 illustrates hardware specifications for the RFID pilot on electronic ticketing to be organized in Denmark. Section 4 describes

hardware specifications for the document archiving pilot in Italy. Section 5 focuses on the hardware specifications of the workers’ safety pilot, while

section 6 elaborates on the hardware specifications of the intelligent manufacturing and control pilot in Greece. Section 7 illustrates the

hardware to be used and configured in the logistics pilot for the plastic film industry in Spain. Section 8 is devoted to the hardware specifications of the apparel logistics and retail pilot of the project, while section 9

reports the hardware specifications of the security systems pilot in UK. Finally, section 10 concludes the deliverable.



13/45

2. Cable trading logistics Pilots Targeted process in Cablecommerce pilot project aims at facilitating the

logistics and warehousing of drums of cables and other (smaller) inventory items at two of the trading bases of the company. The idea is all drums of cables to be tagged with RFID tags, while the smaller items to

be labelled with bar-code prints.

2.1 Hardware Specifications

2.1.1 RFID/AutoID Devices

In the scope of the CABLECOM pilot, a number of different RFID products

were evaluated in terms of feasibility to support the envisaged pilot requirements in the target cables environment. The main objectives of the respective feasibility analysis are to ensure that the hardware can

meet the reading requirements imposed by the pilot’s heavy industrial outdoor environment. Specifically, the following products were explored:

LF (125 kHz) LF-AH1-G2-USB MPEC HF (13.56 MHz)

RFID MODULE HF 7527 HF-AM1-G2 USB MPEC UHF (868 MHz)

RFID MODULE UHF-868 LINEAR ANT G1/G2 XMOD MPEC The three different frequency spectrums were tested and observed close

to various types of cable products. Read distances and proximity influences were measured. Numbers of RFID tags (LF, HF and UHF) were

tested to exercise various opportunities of fastening to various warehouse items on the field.

On the basis of the tests carried, the most suitable solution was chosen as follows:

RFID tags with following features –passive tag, HF (13.56 MHz) technology, Read only, ISO 14443, Mifare, ISO 15693

Integrated reader (antenna, reader and software) HF-AM1-G2 or

HF-T2-G2 for hand held (mobile) computer Workabout pro (PSION TEKLOGIX).

At the time of finalizing this deliverable (August 2010) it is still discussed whether printers (Zebra) should be (additionally) included in the hardware configuration.

The envisaged vendor for the above RFID hardware is PSION

(www.psionteklogix.com).

http://www.psionteklogix.com/



14/45

2.1.2 Networking Equipment

Wireless gateway and access points, antenna, accessories and fittings will be used to provide wireless communications coverage of the work zones

on site. At the test stage, industrial design equipment was applied to explore radio propagation, data rates, time delay around outdoor and indoor environment full of cable coils and rolls.

The selected 9160 G2 is a dual radio, 2.4 and 5 Ghz multi-band access point supporting 802.11a/b/g radio standards enabling a mix and match

of 802.11 technologies. The 9160 also supports Wireless Distribution System (WDS) allowing for a completely wireless infrastructure.

After the site survey additional access ports were considered to provide better coverage of the most important zones and a level of redundancy to

guarantee continuous operation.

2.1.3 Computing Equipment

A server integrated to the existing customer’s network will be used to host an intermediate data base and mobile operations application server.

All the field and RFID related operations will be served by mobile applications running on hand held computers.

2.2 Hardware Configuration Hand held computers will be equipped with both RFID scanner and bar

code scanner in order to provide combined facility of reading and automatically identifying tagged product flows. Wi-Fi modules are also installed to provide wireless communication of the mobile clients.

The hardware configuration (as defined by the vendor) set up for the pilot

stage is:

Option Set 0 WORKABOUTPRO

HANDHELD TERMINAL

Unreleased Options 76307

Authorization Code is Valid no Invalid Number

Confirm Authorization Validity no Options not allowed

Entry Status 4 Normal Production

Country of Use BG (For use in Bulgaria)

Price Book GBL Global Price List

RoHS Compliance 1 Compliant

Configuration 9 7527C-G2 (WORKABOUT PRO C)

Assembly (Second Ops) 1 Yes

Internal Scanner 4 1D Imager Pod

CF Slot 23 RA2041 802.11b/g

Authorization Number 76307

Authorization Code is Valid yes Valid Number

Confirm Authorization Validity yes Author and Validity Confirmed

Expansion Slot 0 none

GSM Antenna Location 0 Not applicable

Speech Language 0 None



15/45

Endcap Expansion 4 ACG LF-AH1-G2-USB MPEC

Sim Card 0 None

Operating System 4 WINCE 5.0

Language Support 0 English

Emulation 1 0 None

Emulation 2 0 None

Pistol Grip Handle 1 Pistol Grip

Battery Pack Type 3 Super High Cap (4400 mAh)

Battery Door 3 Super High Cap

Battery Door Latch 1 Standard Latch

Screen Protector 1 Screen Protector Installed Table 1: Default Configuration of the selected hardware for the

CABLECOM pilot

The following figure depicts the physical configuration of computing systems and RFID devices.

Figure 1: High-Level physical configuration of the hardware equipment

for the CABLECOM pilot

2.2.1 Protocol /Interface to AutoID Devices

The following standards and protocols will be used for the interfacing to RFID/AutoID devices:

High Frequency RFID Standards: Multi-protocol reader ISO14443;

ISO14443-B-SR176; ISO14443-B-SRIX4K; MiFareStandart; MiFareUltraLight; MiFareDESFIRE and ISO 15693-PHILIPS;

2.2.2 Physical interface

The physical interfaces used at this stage are RS232 and USB.



16/45

2.2.3 Networking Configuration

The networking configuration for the CABLECOM pilot will be built following the on-site hardware deployment and testing and based on the

already existing local network. In total, it is envisaged to have 8 (eight) access points for reaching optimal network coverage – 6 (six) for the trading base in Burgas and 2 (two) for Sofia.

2.2.4 Computational Devices Configuration

The Server environment will comprise MS SQL Express, MS Server, .NET 3.5; 2 to 4 GB RAM; The Mobile environment will comprise WS Windows CE 5.0. .NET compact

framework 2.5, as well as PXA270 520 MHz, 32 bit RISC CPU with 256 MB Flash, 128 MB RAM.



17/45

3. Pilot on electronic tickets for VIP guests



The following RFID devices will be deployed for this pilot: Desktop reader, Mifare with USB Model RDM530C

http://www.datarfid.com/doce/Product/pic_142.html Any PDA (Personal Digital Assistant), with integrated Mifare reader

and windows mobile or Android OS (Operating System)1.

No sensor and actuators devices will be involved in the pilot.


The readers in the office / booking will use USB for a PC in an Ethernet and TCP/IP environment. The PDA will use the 3G or 4G mobile technology.


The following computing features will be used: Win XP or Win 7 PC with USB.

Server, MS small business server 2008. PDA as specified under RFID-devices.

A cloud computing model will be pursued, which will obviate the need to

purchase a server. Hence, the solution will run on a shared server (running within a provider), which will host the required MS SQL 2008 R2

database.

3.2 Hardware Configuration Figure 2 depicts the logical architecture of the electronic ticketing pilot.

The architecture illustrates the main networking protocols and physical interfaces that will be used, as illustrated in the following paragraphs.

1 RFID-SPE as already developed a first version of the applications for Android OS

and MS SQL 2008 express R2 database



18/45

Figure 2: Logical Architecture of the Ticketing Pilot


ISO 1443 /Mifare will be employed to ensure that the system can

integrated into other systems like ticked and payment, transport and access control used on hotels and buses etc.

3.2.2 Physical interfaces and Networks

In terms of physical interfaces the pilot system will rely on: Desktop readers , mifare, USB

PDA with integrated reader. Note that Bluetooth can be used as an alternative interface for the wireless/mobile communication with the reader.

TCP/IP and mobile networks will be used, as shown in the logical

architecture. The communication between the back-end servers/systems and the readers will be based on TCP/IP, while wireless networks will facilitate networked communications with the wireless devices.



19/45


The following computing devices will be used: PC for booking, existing office clients, Win XP or better

PDA Win CE 6.0 or better, or Android 2.0 or better, disk min. 4GB, 512MB RAM, pocket format, colour display, 3.2” display.



20/45

4. Pilot on automated document tracking The target process is Tax Assessment, one of the most important services

provided by RETE, which now allocates most of the RETE resources for 3 months per year. In fact 90% of the companies associated to CNA (Confederazione Nazionale dell'Artigianato e della Piccola e Media Impresa

i.e. the National confederation of craftsmen and SMEs)2 generate 2 to 4 declarations (for the company, for the partners, for some family

members).

Every year each customer brings document (in original) relevant to its tax assessment from January to May. Documents at RETE are stored into

folders. A folder in a given branch office can stay in a cabinet or into a box on the floor or lay on a desk. A folder can be moved from a branch office

to another one, to undergo specific treatments or to balance office workloads.

The work assumption is that all the relevant folders are tagged and all the relevant places are tagged (desks, cabinets, boxes, offices). We do not assume in this pilot that employees are tagged, as this would raise privacy

issues without generating significant value for the processes.

The number of folders to tag is in the order of tens of thousands. All the

information related to the folder status and contents, dynamically updated by different operations and different employees, are stored in a distributed web application and coupled to the physical folder via its tag.

4.1 Hardware Specifications The main hardware requirement refers to the use of handheld antennas,

without installing fixed antennas in the RETE offices (see

Figure 3).

Another important requirement is the possibility to read simultaneously

about 30 tags associated to folders put into the same box, so as to make an inventory of the box contents in a fast and reliable manner.

For this reason two RFID systems have been evaluated:

UHF system, with a handheld antenna connected via cable to a

reader connected to a net-book via a USB port (no need of further cables for electric powers).

HF (ISO 18000 – 3 mode 2) system, with a handheld antenna

connected via cable to a reader connected via USB to a net-book and via cable to an electric power plug.

We are taking the final decision, very likely we will choose option 1 because of its limited cost, standardisation and usability. The decision will be based on ongoing on-site tests.

2 CNA is an entrepreneurial association, and RETE is a company owned by CNA providing

services to CNA members. The RFID staff is installed at CNA branches under the responsibility and the management of RETE



21/45

Web access

Web application

Client application

Figure 3: RETE pilot physical configuration


UHF system

The following FEIG technology can be used for the UHF solution3:

Tag UHF EPC G2 DogBone Paper Label NXP, 97x27mm, 240 bits (0,349 Euro price per unit)

UHF Short Range Reader ID ISC.MRU80-M2-U. (605,00 Euro) for 2 ext/ant.

UHF Antenna Cable ID ISC.ANT.C4-A (4 meters)

UHF Antenna ID ISC.ANT.U160/160-EU ANT.U10108. RFID OEM PCB Near Field Inductive

UHF Antenna ID ISC.SDK.WIN

SDK Libraries for Windows

The RedWave Short Range Reader UHF USB is EPC Class 1 Gen 2 – ISO

18000-6C and supports 2 external multiplexed UHF antennas. It is a small size & low cost Short Range UHF Controller, with Read Range up to 200

cm (depending on tag & antenna gain), power supply is via USB (5 Volt) and adopts the same protocol of all FEIG controllers (HF & UHF).

HF mode 2 system

The HF solution consists of the following equipment4:

Tag PJM Stack

Reader MARS-2 (Multiple antenna reader system) for two antennas compliant with IEC/ISO 18000-3 mode2, reading up to 150 tags per

second even if tightly stacked, overlapped or touching. Both Ethernet and USB interfaces.

3 Proposed by Softwork (www.rf-id.it) retailer 4 Suggested by mode2 (www.mode2.it), an Italian reseller of Magellan technology



22/45

Antenna 031-70-017-ASY Single axis, round, 60 mm inner antenna

coil diameter, 85 mm overall diameter compliant with IEC/ISO 18000-3 mode2

4.1.2 Sensors and Actuator

No further sensor or actuators are envisaged for this pilot.


The reader + antenna system is connected (in both options) to a PC, note-book or net-book, so as make the user checking at a glance the read tags. This computer is connected to the office LAN, so as to make the

results of the reading operations available to the web application which supports folder management.


Each office is provided with one RFID system (reader + handheld antenna + net-book).

Each RETE office is also connected to centralised servers at the CNA Milano headquarters via VPN/xDSL. These servers host the accounting

system, used by all the RETE offices, and will host the web application for folder management.

4.2 Hardware Configuration


The RFID reader is based on the ISO 18000-6 standard or (with lower probability) on the ISO 18000-3 mode2 standard.


The RFID reader is equipped with USB physical interfaces, used to communicate with the net-book. The reader uses a SMA connector to the handheld antenna.


The application that we are developing is a distributed application

composed by 3 different modules (central repository, web-gui, client-gui).

The main features offered by the application suite are: Access and modify the status of a virtual folder (a virtual

representation of a physical folder).



23/45

Move the folder in and out from a box, and between branches

Notify RETE client about missing documents into the folder The central repository module, deployed on the server, is used to access

and retrieve the information stored into the database. This information contains details about the status of each virtual folder. The central module

is also used to schedule the notifications. The server must be connected to the Internet to use external services used for notifications (sms and email gateway services). This module also exposes web-services for accessing

and modifying the repository.

The web-application module, used by operators working at their own desks, is hosted on the same server and will be used for modifying the status and the content of a virtual folder.

The moving operations of the folder are made available using the client-

gui module. This application is deployed into net-book/note-book and it is able to drive the RFID reader connected. The notebook is connected to the Wi-Fi lan of the office in order to perform the web-service access to the

software central repository.


Two main types of computational devices, net-book/note-book and central

repository server are used, as described previously.



24/45

5. Pilot on safety on building working sites

Two possible operational scenarios have been currently identified for the pilot deployment at BRIDGE129:

Scenario #1 - RFID system integrated with infrared sensors (no

integration with camera)

One or more antennas are placed at each building yard access, linked to

one RFID reader. The reader is able to capture and identify each tag entering the yard access. Then, every entity provided with a tag, humans as well as operating machines, can be univocally identified.

This scenario foresees the use of the reader/antenna system integrated with a system to detect the presence of individuals or operating machines

based on an infra-red device. This infra-red device will be integrated with a viewer placed in the control room. Whenever the infra-red sensor,

placed at the building yard access, captures the presence of an item, a signal is issued to the control room, so as to rise the attention of the operator which is responsible of comparing the number of identified tags

with the number of visible items.

Scenario #2 - RFID system integrated with infrared sensors and

cameras

Scenario #2 presents the same integration between the RFID technology and the infra-red sensor presented in Scenario #1, and as additional

feature it exploits a simple artificial vision system able to count the number of items, i.e. individuals or operating machines and trucks,

entering or exiting the construction working site access.

In this case the human operator maintains a general responsibility of scene control, but the check between the number of detected tag and the

number of identified images is automated.

5.1 Hardware Specifications The selected hardware solution is suited to support both Scenario #1 and #2. In order to minimise the impact of the monitoring system in the

working area, we hypothesise the use of a “smart pole” on which the following devices are mounted:

the infra-red sensor.

2 Rfid antennas installed at different heights (Rfid Antenna 1 & 2)

the camera (Network Camera)

one plastic box (Box) including an ethernet switch, the Rfid reader, the Arduino kit and the electrical connectors for the different system

components.

The smart pole is installed near to the building yard access to monitor. For the correct system work it is necessary to connect the box to the electric

system and the LAN/internet network with an Ethernet cable.



25/45

Figure 4: Basic Configuration of the BRIDGE pilot hardware devices

The combined use of two antennas allows one to extend the RFID reading

area, allowing to detect also tag positioned few meters from the round, particularly those applied to trucks and operating machines.

The selected solution supports Scenario #2 and can be made more

automated by applying an artificial vision system able to count persons/machines crossing the access, so as to implement Scenario #3.


A possible solution5 entails the use of a development kit suited to

experiment in real life conditions the considered operational scenarios. The kit includes some tags.

Kit Rfid Uhf Active with 1 antenna Cod. KA-B02 - RFID Active Beacon Fixed Developer Kit Euro 1.300,00 + VAT

5 Suggested by Softwork (www.rf-id.it) retailer

http://www.rf-id.it/



26/45

Additional antenna: Euro 100, 00 + VAT Active tag (Lf+Uhf) (circa): Euro 32,00 + VAT

The RFID Active Beacon Technology i-PORT M B-2/EU kit includes the following components:

1 X Reader Device i-PORT MB-2\EU -ETH. Fixed Long Range

Reader. With Ethernet host interface, additional RS422 Interface to connect up to 8 additional i-PORT MB Readers, 868 MHz; 2 SMA

antenna connector. (Antenna not included). (Cod. 401662)

1 X ID NET.24V-B Power Supply Unit with European Plug Cable

to pro-vide power for i-PORT MQ. (Cod. WT2557-2558)

1 X ANT.U160/160-EU Antenna UHF. Circular polarized Panel Antenna (CPP868) for operating frequencies in the UHF ranges 865-

870 MHz (EU Region). Directivity: 90°. Gain: 4,0 dBic @ 866 MHz. Antenna connection SMA socket (50 Ohm). Size (WxHxD):

162x162x16 mm. (Cod. 9916-868-16)

2 X Tag i-B2 S/EU - (up to 100m with fixed readers, Broadcast Tag, 9 Bytes Memory, 868 MHz) Read range up to 100 m in free air.

Repetition rate: 0,5 to 60 sec. (in steps of 0,5 sec.). Transmit power < 1 mW. – Industrial housing. (Cod. 285571)

1 X Tag i-B2 P/EU - (up to 100m with fixed readers, Broadcast Tag, 9 Bytes Memory, 868 MHz) Read range up to 100 m in free air. Repetition rate: 0,5 to 60 sec. (in steps of 0,5 sec.). Transmit power <

1 mW. – Credit Card Format (personal Tag), 1 slot for fastening. (Cod. 304563)

1 X Tag i-B2 W /EU - Wristband housing. Read range up to 30 m in free air. Repetition rate: 0,5 to 60 sec. (in steps of 0,5 sec.). Transmit power < 1 mW. Dimensions: 43×38.5×14.5 mm. Casing

Plastics. Mass 40 g. Pro-tection class IP 65. (Cod. 405464)

1 X Tag i-B2 CC/EU - Credit card holder format. Read range up

to 100 m in free air. Repetition rate: 0,5 to 60 sec. (in steps of 0,5 sec.). Transmit power < 1 mW. Dimensions: 104.50×58.40×12 mm. Casing Plastics. Mass 41 g. Protection class IP 65. (Cod. 353870)

1 X Micro Tag i-B2 M/EU - Micro Personal Tag, Oval, 1 mounting holes. Read range up to 50 m in free air. Repetition rate: 0,5 to 60

sec. (in steps of 0,5 sec.). Transmit power < 1 mW. Dimensions: 56x30x12 mm. Casing Plastics. Mass 19 g. Protection class IP 65. (Cod. 341665)

SDK libraries for MS Window

Coaxial cables to connect the two antennas.

The active Rfid kit (KA-B02) includes 6 tags of different kinds. For the BRIDGE pilot case two kinds of tag are useful:

i-B2 S/EU Tag industrial case, to apply on operatine machines

and trucks.



27/45

i-B2 P/EU Tag personal tag, which is similar to a credit card and

can be used to tag authorised personnel.


Infrared sensor

The Infra-red sensor provides a Normally Closed output circuit that commutes its state whenever it senses a person.

Camera

The camera is a common off the shelf IP camera already used by BRIDGE

for the current surveillance environment.


The switch is connected to the RFID reader, the camera and the LAN interface of the Arduino kit.

The box can be provided with a forced ventilation so as to avoid superheating of the internal devices.

The connections between box and camera will be realised by waterproof

corrugated sheathings for cable protection. Similar sheathings are used to connect antennas and box, which includes the reader.

All this equipment is obtained through the normal purchasing channels of BRIDGE.


The computing equipment is that already used for the existing video-surveillance application (i.e. legacy equipment). In particular, the

application will run on an industrial PC put into a box together with the infra-red sensor and the RFID reader, and the box in turn is mounted on

the smart pole. The PC model is depicted in: http://www.nexcom.com/ProductModel.aspx?id=e2afe319-c87e-4392-af9a-36c03be18876.



The RFID reader is based on the ISO 18000-7 standard.


The RFID reader is equipped with USB and Ethernet physical interfaces.

The Ethernet physical interface is used to connect the reader to the Ethernet switch. The reader uses a SMA connector to the antenna.

The Arduino kit with Ethernet shield is equipped with USB and Ethernet interface. The USB interface is used to program the board. Ethernet is

http://www.nexcom.com/ProductModel.aspx?id=e2afe319-c87e-4392-af9a-36c03be18876

http://www.nexcom.com/ProductModel.aspx?id=e2afe319-c87e-4392-af9a-36c03be18876



28/45

used to communicate with the computational device. The Arduino kit also

provides a digital input interface. The camera and the video surveillance server use their internal Ethernet

interface.

5.2.3 Sensor/Actuators Interfaces

The digital input interface provided by the Arduino kit, is used to acquire the signal from the infra-red sensor. The program deployed to Arduino

board listens for a telnet connection on which writes the infra-red sensor status.


The following picture depicts all the used devices (Rfid reader, network camera, arduino, surveillance server) interconnected to the Ethernet switch.

Figure 5: Ethernet Networking between the devices of the Pilot


The existing video-surveillance application is composed by two main

modules: DBMS server and GUI. Both modules are hosted on the same hardware (personal computer)

interconnected using the Ethernet interfaces. The application that we are developing, integrating the view of the captured tags into the camera scene, is hosted on the server used for the existing application.



29/45

6. Pilot on intelligent manufacturing for the

paper industry


6.1.1 RFID/AutoID Devices and Computing

Equipment

The KOSKINIDIS pilot deployment will make use of four mobile readers

and one fixed readers. The Bill-of-Materials (in terms of both RFID equipment and computing devices) is depicted in the following table:

Hardware Component(s)

Description Use in the pilot

Intermec CK31 Mobile Terminal

(4 Pieces)

This is a mobile RFID reader & Barcode scanner,

supporting/featuring ISO18000-6C, EPC UHF Class 1 Gen 2, WIN

MOBILE 6.0, USB, WiFi (802.11 b/g), ΙΡ65, Recharger/Communication base

(USB, SERIAL, ETHERNET), and Adapter.

Mobile readers will be used in many

logistics (i.e., receiving, shipping,

inventory) and manufacturing processes (i.e.,

associated production processes with used

resource assets) of the pilot.

Intermec PM4i This is a high speed RFID / Barcode printer supporting: EPC CL1G2 / ISO180006C, EAN128,

THERMAL TRANSFER, 203 dpi, RS232, PARALLEL, USB, 10/100

Base-T Ethernet.

This is the RFID printer that KOSKINIDIS will use

for printing physical RFID and barcode

labels

SUN Ultra 27

Workstation

Workstation SUN Ultra 27: 1 x

Intel Core2 Quad Extreme Q9650 3.0 GHz, 1333 MHz FSB, 8GB RAM (1GB x 8, 667MHz,

ECC, DDR2), 1 x 250GB HDD (7,3k, SATA 3.0 Gbs) - RAID1, 1

x 1GbE , 4 x PCIe, 6 x USB 2.0, 1 x DVD+/-RW, 1 x NVIDIA FX370 Graphics Accelerator, 1 x

SUN TFT 19" Color, 1 x Keyboard, 1 x Optical Mouse,

Desktop Chassis, SOLARIS 10.

This is the server that

will host the middleware of the solution

ELO 1715L

Touch Screen

ELO Touch Monitor 1715L, 17" These touch screens

will be used as user



30/45

(4 pieces) interfaces for the

production and logistics employees of

the KOSKINIDIS company.

Table 2: RFID and computing equipment to be purchased and used in the

scope of the KOSKINIDIS pilot

Figure 6 depicts the fact that the AutoID printer will be configured through the middleware of the solution (i.e. the S-BOX middleware described in

deliverable D3.2 of the project). The middleware will be hosted in the Sun Ultra 27 server, which the touch screens will be used as a user

interface/device.

Figure 6: Physical Configuration of the AutoID Printer at KOSKINIDIS

M

Tagged Items (Materials, Machines,

Tools)

WiFi WiFi

RF RF

Process I

Process II

Process N S-Box Platform

(Sun Ultra 27)Intermec CK31 Mobile

Terminal

ELO 1715L Touch

Screen

TCP/IP

Figure 7: Physical configuration of the mobile readers of the KOSKINIDIS solution



31/45

Likewise Figure 7 illustrates the use of the mobile readers within the pilot, which will be also be configured and driven by the software/middleware (i.e. S-BOX suite) of the solution. It should be noted that the mobile

readers will feature a wireless (WiFi) connection to the middleware server. Note that the touch screens will be again used as the management and

control interface of the middleware server. Note that WiFi hotspots / access points are readily available in the company and will not be purchased as part of the project.

The pilot deployment does not entail addition sensors & actuators (such as

conveyor belts, photo-eye reflectors, stack lights, etc.).


The pilot will leverage the KOSKINIDIS company LAN (Local Area

Network), which includes both wireline and wireless connectivity services.



Communication with RFID readers of the solution will be based on the EPC LLRP protocol (in terms of message binding) and TCP/HTTP protocol

(in terms of transport binding).



32/45

7. Pilot on plastic film industry

In our project, every hand pallet truck is equipped with an RFID receiver (a reader and an antenna), and an industrial computer with an application connected via Wi-Fi with the ERP database.

In this context the new hardware needed for this pilot is:

- RFID receivers installed on pallet trucks - Industrial computers installed on pallet trucks

- Tags RFID - Handheld RFID reader

- RFID printer

The rest of hardware involved in the project is now available from the factory customer (Database servers, personal computers, TCP/IP network and wireless infrastructure).



Tags

Different types of RFID tags should be selected to suit different situations:

Tags buried in the floor of the warehouse. Tags attached to metal surfaces. Tags attached to by-products and pallets.

There are different scenarios involving different requirements and entail

different risks, this task includes the work to select the appropriate types of RFID tags.

To satisfy these requirements we will evaluate different types of tags: RFID adhesive label, 860-960 MHz, 76x76 mm

RFID adhesive label, 860-960 MHz, 97x76 mm Blue Tag, Gen2 (ISO 18000-6C), 868-915 MHz, 126x24mm Blue Tag on-Metal, Gen2 (ISO 18000-6C), 868-915 MHz,

126x24mm

Handheld RFID readers Handheld RFID readers will be needed for the personal computers

installed on the warehouse to allow RFID readings from ERP system.



33/45

NPH Pocket BT-UHF, Bluetooth handheld RFID reader and

lightweight medium range UHF (862 - 955 MHz), ISO 18000-6A, ISO 18000-6B, ISO 18000-6C, EPC Class 0, EPC Class 1 (GEN2), Bluetooth Clase 2, USB.

RFID Receivers

Every hand pallet truck is equipped with an RFID receiver (a reader and an antenna) to identify the by-products that the pallet truck is loading or

downloading and where. To do this it must be able to read RFID tags of by-products and RFID tags that identify positions in a warehouse. We will evaluate these two alternatives:

NPR EasyTag Lite250 Reader with integrated antenna.

UHF RFID reader RS485 Up to 4 meters distance for reading.

EPC Class1 Gen 2 (ISO 18000-06C) standards 865-868 Mhz

NPR EasyTag Lite 120 Reader with integrated antenna. UHF RFID reader RS485

Bluetooth Class 1 interface. Up to 1,5 meters distance for reading.

EPC Class1 Gen 2 (ISO 18000-06C) standards 865-868 Mhz

Industrial computer

Every hand pallet truck is equipped with an industrial computer to manage the RFID readings captured by the RFID receiver. We are working with

this model:

CMC-3000 Mobile Computer

IP54 dust and water resistance



34/45

2 wireless communication options:802.11b/g, Bluetooth Class II

Intel XScale (PXA255 400MHz) Memory: ROM 64MB Flash, RAM 128 MB 8.4” TFT LCD 800x600 touch-sensitive panel; 64k colours.

RFID printer

RFID printer will be needed for the personal computers installed on the warehouse to allow printing new RFID tags from ERP application. We have

selected and tested the next printer:

Zebra RZ400

RS232, IEEE 1284, USB 2.0 UHF codification

EPC Gen 2 (ISO 18000-06C) standards 16 MB DRAM, 8 MB flash


No such devices will be used in the project


Industrial computer installed on the pallet truck must be connected with

the RFID reader by Bluetooth and it will use a wireless network in the warehouse.


At PICDA factory already has the infrastructure necessary to run the ERP

system and other applications, this equipment consists of:

Servers with Microsoft Windows Server 2003 and Microsoft SQL Server

2000 to manage the ERP database. Personal computers with Windows XP or Windows 7 to run the desktop

client application of the ERP system. And finally for the new hardware for this pilot, we will need

Windows CE for install on industrial computers



35/45

And perhaps Windows 7 or Windows XP for a new personals

computers in a warehouse if is needed.


ERP Client PC

ERP Client PC

Erp Client PC

SQL Server

ERP Client PC

Wireless

acces point

TC

P/IP

RFID

printer

TCP/IP

Handled

RFID reader

Bluetooth

TCP/IP

TCP/IP

RFID Reader

Industrial

computer

Bluetooth

Warehouse

Figure 8: Physical Configuration of the hardware of the PICDA

pilot


The RFID reader is based on the ISO 18000-6 C standard.


Bluetooth to connect Industrial computer to the RFID reader.

Bluetooth to connect ERP client PC to the Hand RFID reader. Ethernet to connect computers to the local network.

Wireless Ethernet to connect computers in a warehouse to local network.

7.2.3 Sensor/Actuators Interfaces

No such devices will be used in the project.



36/45


At PICDA factory already has a network infrastructure based on TCP/IP with wireless support on the warehouse, TCP/IP technology will be used for this pilot.


The following computing devices will be used: PC for ERP client users.

Industrial computer with Windows CE for pallet truck operators.



37/45

8. Pilot on inter-enterprise apparel logistics

8.1 Hardware Specifications The STAFF inter-enterprise pilot will build over the existing pilot

deployment at the STAFF central warehouse. Hence, in addition to presenting the equipment to be purchased for the pilot, following

paragraphs list also the equipment deployed/used at the STAFF warehouse (which in essence) will be also used in the extended pilot.

8.1.1 RFID/AutoID Devices and Computing

Equipment

The RFID and computing devices to be used in the pilot are listed in the

following table:

Hardware Component(s)


PRINTRONIX SL4M RFID Printer

High Speed RFID/barcode printer Printronix SL4M with the following specifications: EPC

CL1G2 / ISO180006C, EAN128, THERMAL TRANSFER, 203 dpi,

RS232, PARALLEL, USB, 10/100 Base-T Ethernet.

Printer enabling printing of physical RFID labels. Will be

chiefly used for handling/replacing

labels and RFID loyalty cards

CSL CS101 Mobile Terminal (2 pieces)

RFID reader & Barcode scanner, with the following specifications CS101, 197 x122 x 223 mm3,

1.2 kg, Reading Speed 150 Tags/sec 7m (Passive Tags),

ISO18000-6C, EPC UHF Class 1 Gen 2, WIN MOBILE 6.0, USB, WiFi (802.11 b/g), ΙΡ65,

Recharger & Communication base (USB, SERIAL,

ETHERNET), Power Supply Adapter.

Mobile readers to be used for inventory within the retail store

SUN Ray 2 Thin Client

Terminals adopting the Ultra - Thin Client SUN Ray 2 architecture. Specifications: 2 x

USB 2.0, 1 x Serial, 1 x SIM Card, 17" SUN TFT Colour,

Keyboard, Mouse, SUN VDI v3.0 Software

Terminals used by the employees of the STAFF warehouse in

order to monitor and control the RFID

deployment.

SUN Ultra 27 Workstation

Workstation SUN Ultra 27: 1 x Intel Core2 Quad Extreme Q9650 3.0 GHz, 1333 MHz FSB,

The computing server that will host the middleware of the



38/45

8GB RAM (1GB x 8, 667MHz,

ECC, DDR2), 1 x 250GB HDD (7,3k, SATA 3.0 Gbs) - RAID1,

1 x 1GbE , 4 x PCIe, 6 x USB 2.0, 1 x DVD+/-RW, 1 x NVIDIA FX370 Graphics Accelerator, 1 x

SUN TFT 19" Color, 1 x Keyboard, 1 x Optical Mouse,

Desktop Chassis, SOLARIS 10.

solution

ELO 1715L

Touch Screen (4 pieces)

ELO Touch Monitor 1715L, 17" Touch Screens to be

used as interactive displays in the retail shop

RFID Reader IMPINJ

Speedway (3 pieces)

UHF reader (UHF Gen. 2) with the following technical

characteristics Tag-to-Reader Data Rate:

640kbps Air Interface Protocols: EPC

Class 1 Generation 2 /

ISO18000-6C Interface: EPC LLRP v1.0

865MHz – 956MHz Antennas: 4 x with TNC

connectors

Power: 30dBm adjustable per 1dBm ( ETSI 302208

compliant) Connectivity: RS232,

ETHERNET

Network Services: TCP and HTTP services.

These three fixed readers will be used

at the read points of the intelligent POS

and the two smart mirror (one for the e-salesman service)

Table 3: RFID and computing equipment to be purchased and used in the

scope of the STAFF pilot



39/45

LAN

Switch

Management Console

(for S-Box)

SUN Ray 2 Thin Client

S-Box Platform

(Sun Ultra 27)

ELO 1715L Touch

Screen

(E-Sales Man)

STAFF Shop

ERP

(legacy)

IMPINJ Speedway

(Smart POS)

RFID/AutoID Printer

(Smart POS)

Internet

STAFF E-Shop

Intermec CK31 Mobile

Terminal

WiFi

ELO 1715L Touch Screen

(Smart Mirror)

IMPINJ

Speedway

IMPINJ

Speedway

Figure 9: Physical configuration of the hardware comprising the STAFF

pilot (retail part)

Figure 9 illustrates the LAN-based connectivity of the hardware devices entailed in the retail part of the STAFF pilot. As a shown in the figure, a

number of fixed RFID readers (already possessed by SENSAP) are connected to a switch in order to support reading of items pertaining to

the various retail services of the pilot (such as the smart point-of-sale (POS), the smart mirror and the display for automated electronic sales). The LAN networked connects also the middleware server (hosting the S-

BOX suite as described in D3.2), as well as the RFID/AutoID printer that will be used to print tags for the loyalty cards. Note that mobile readers

used for inventory purposes (at the retail store warehouse) are connected to the S-BOX platform through wireless connectivity (similar to the KOSKINIDIS pilot). Note that the RFID pilot system entails also

interactions with the ERP of the STAFF shop, as well as the e-shop of the company, in order to offer the e-shop in a shop experience. For the details

of these functionalities, readers can access deliverable D2.1 of the project.

8.1.2 Sensors and Actuators

No additional sensors and actuators will be purchased for the pilot.



40/45

8.1.3 Equipment deployed/available at the STAFF

central warehouse

The following table lists the equipment deployed/used as part of the RFID deployment at the STAFF central warehouse. The table is part of Deliverable D6.2 of the ASPIRE FP7 project6.

Hardware

Component(s) / Consumable

Tags


Tunel Portal - 8m3

This is a Tunel Portal from aluminium and Plexi-Glass. A

SUN Ray machine, an RFID Reader, four Far - Field RFID

Antennas, and another four 4 x Near - Field RFID Antennas

(max) can be put on this portal. The portal includes also coaxial cables with a length of

six meters.

The portal is used to support the receiving

and shipping processes/use cases of

the pilot, where batch reading of packaged

tagged products occurs are packages pass through the portal.

Tunel Portal

Conveyor - 8m

This is an automatic conveyor

belt (8m) with a remote control.

Used to facilitate

packages (e.g., containers) to

move/flow through the portal

Tunel Portal Actuators (two sets)

A Tunel Portal actuator set includes two optical switches, one LED and one Peeble II

Controller for the IMPINJ Speedway RFID Reader.

Support actuating functionalities associated with the use

of the portal (e.g., indications about the

packages, the status of the processes etc.)

SUN Ultra 24 Workstation

SUN Microsystems workstation with the following characteristics: Workstation

SUN Ultra 24: 1 x Intel Core2 Quad Extreme Q9650 3.0 GHz,

1333 MHz FSB, 8GB RAM (1GB x 8, 667MHz, ECC, DDR2), 1 x 250GB HDD (7,3k, SATA 3.0

Gbs) - RAID1, 1 x 1GbE , 4 x PCIe, 6 x USB 2.0, 1 x DVD+/-

RW, 1 x NVIDIA FX370 Graphics Accelerator, 1 x SUN TFT 19" Colour, 1 x Keyboard,

1 x Optical Mouse, Desktop Chassis, SOLARIS 10

This workstation host the RFID middleware of the solution (based on

a JavaEE environment)

6 http://www.fp7-aspire.eu

http://www.fp7-aspire.eu/



41/45

CISCO SD2008

Switch

The switch has the following

specifications: Switch CISCO SR2024C, 8 x 10/100/1000

GbE RJ45, Desktop Chassis

Networking device

used to support the networking

communications of the solution

SUN Ray 2 Thin Client (two pieces)

Terminals adopting the Ultra - Thin Client SUN Ray 2 architecture. Specifications: 2

x USB 2.0, 1 x Serial, 1 x SIM Card, 17" SUN TFT Colour,

Keyboard, Mouse, SUN VDI v3.0 Software

Terminals used by the employees of the STAFF warehouse in

order to monitor and control the RFID

deployment.

IMPINJ Speedway Reader (two

pieces)

The IMPINJ Speedway RFID GEN 2 RFID Reader supporting the pilot solution. The

specifications of the reader include: EPC CL1G2,

LLRPv1.0.1, 865 MHz - 956 MHz, 4 x Mono-Static Antennas (Reverse gender

TNC), Near & Far Field, RF +32.5 dBm, Sensitivity -80

dBm, 10/100 Base-T Ethernet, 1 x RS-232, DHCP, HTTP, Telnet, SSH, SNMP, mDNS,

DNS-SD.

It is used to support reading of tags during the RFID-enabled

business processes. The reader supports

the LLRP protocol and interfaces to the RFID solution via the

AspireRfid LLRP HAL.

IMPINJ

Brickyard Antenna (two

pieces)

RFID Reader Antenna, IMPINJ

Brickyard CS-777, 865MHz – 956MHz

UHF antenna attached

to the IMPINJ RFID reader.

IMPINJ

Guardwall Antenna (two pieces)

RFID Reader Antenna, IMPINJ

Guardwall

RFID antenna attached


MTI ΜΤ242017 Antenna (two

pieces)

Far-Field RFID Reader Antenna MTI-Wireless MT-242017/NRH:

Mono-Static, 865MHz – 956MHz, 10 Dbic min, VSWR

1.3:1

RFID antenna attached to the IMPINJ RFID

reader.

MTI ΜΤ242032

Antenna (two pieces)

10 dbic RFID antenna attached


PRINTRONIX SL4M RFID Printer

High Speed RFID/barcode printer Printronix SL4M with the following specifications:

EPC CL1G2 / ISO180006C, EAN128, THERMAL TRANSFER,

203 dpi, RS232, PARALLEL, USB, 10/100 Base-T Ethernet.

RFID printer used for printing physically RFID and barcode

labels



42/45

INTERMEC

IP30A Mobile Terminal (two

pieces)

INTERMEC Mobile RFID

Readers

Used for Mobile

Scanning (e.g., during pick & pack and

inventory processes)

Satellite Label RFID Label, IMPINJ Satellite,

Monza 3 Chip (96bit R/W), EPC CL1G2, 1.34" x 2.13", TT Paper, Far & Near Field

Operations

RFID Tags used during

the STAFF pilot (for item level tagging of the apparel products)7

Table 4: Bill-of-Materials (BOM) for the equipment at the STAFF central

warehouse



The EPC family of standards (notably the EPC LLRP protocol) will be used for interfacing to RFID devices.

7 More details on the selected/used tags and labels are provided in deliverable 4.1

of the project



43/45

9. Pilot on security systems

9.1 Hardware Specifications The main items of hardware for this pilot consist of a Nokia NFC enabled phone and NFC enabled tags.

TAG

Internet

Internet

NFC Phone

NFC TAGS

HP Servers

Web Browsers

Web Browsers

Figure 10- High-Level physical configuration of the hardware equipment for the

Security systems pilot


The RFID enabled device if the Nokia 6216 NFC phone. It has the following features.

Operating frequency Quad-band GSM 850/900/1800/1900, WCDMA 850/2100 Flight mode

Data network

CSD GPRS Class B, Multi slot class 10

EDGE Class B, Multi slot class 10 WCDMA 850/2100 TCP/IP support

Capability to serve as data modem Support for MS Outlook synchronisation of contacts, calendar and

notes Local connectivity and synchronisation

Near Field Communication (NFC)- Touch with compatible phones to share, explore, travel, pay and pair - Reading, writing and sharing

capabilities Bluetooth version 2.0 2.5 mm Nokia AV connector



44/45

Support for PC synchronisation with Nokia PC Suite

Support for local and remote SyncML synchronisation

9.1.2 Sensors and Actuators

The sensors to be used in the pilot are based inside the NFC phone. No actuators are foreseen.


The networks of the pilot are based around using the mobile operator networks using connection features such as Quad-band GSM 850/900/1800/1900, WCDMA 850/2100.


For the server side infrastructure (hosting the RFID/NFC applications) the

following components will be used: HP ProLiant - DL380 G6 - 12 GB RAM - 2.8 GHz, 20 GB RAM Microsoft SQL Server with 20 GB Storage

Microsoft .NET Framework



The NFC device will communicate over the mobile network using a HTTP

protocol to reach the host server located under the URL at www.serosolutions.co.uk (i.e. the solution provider for this pilot).

http://www.serosolutions.co.uk/



45/45

10. Conclusions This deliverable has described the hardware infrastructure that will

support the eight pilots of the RFID-ROI-SME. Hardware selection is indeed a critical step in each pilot organization, since it affects the functionality of the solution, the technological longevity of each pilot, as

well as the total cost of ownership. Hence, the completion of the present deliverable has a number of positive implications for the project and the

partners, in particular: It signals the completion of the critical element of the solution design,

which is a prerequisite for other technical tasks, such as middleware

and software specification and deployment. It enables the consortium partners (notably end-users) to proceed with

the necessary procurements in terms of purchasing equipment. It engaged (early on) both solution providers and end-users in the

process of elaborating on the technical aspects of the solution, as well as on parameters affecting the solutions cost.

It will allow the timely procurement and testing of the equipment, well

in advance of the pilot commencement. Note however that several pilot sites have reported multiple/alternative

options associated with the testing of the pilots. Overall, we can conclude that this deliverable provides evidence that the

pilot projects are on the right track, at least as far as the selection, procurement and configuration of the hardware is concerned.

RFID-ROI-SME ICT-PSP No. 250438 RFID-ROI-SME … deliverables/RFID-ROI-SME-D3.1-v2.0.pdf ·...

Documents

Transcript of RFID-ROI-SME ICT-PSP No. 250438 RFID-ROI-SME … deliverables/RFID-ROI-SME-D3.1-v2.0.pdf ·...