Bartek Szejna, OASIS team Round table, 28/05/2013 HYPERMANAGER SPINNAKER PROJECT

PLAN Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusion 2

PLAN Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusions 3

SPINNAKER PROJECT Transform the current state of the art in RFID-based systems and enable more widespread adoption of the technology, particularly in retail and healthcare sectors Improve the performance and real-time interconnectivity of wireless-sensing systems Throughout the supply chain, from manufacturing, distribution, and retail through to the end customer experience. Lead by TAGSYS 8 research labs 4 industrial entities 4

SPINNAKER PROJECT Partners: INSIDE Secure Legrand High-frequency communication INRIA - OASIS INP Grenoble – LCIS – ORSYS Microelectronics Center of Provence Institut d’électronique et de télécommunications de Rennes François Rabelais University ESEO School University Pierre & Marie Curie Laboratory Acoustics Laboratory of the University of Maine Université Paris-Est Marne-la-Vallée – ESYCOM 5

PLAN Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusions 6

ECONNECTWARE By TagsysRFID New generation for a cloud hosted middleware Gather RFID information, collected by RFID readers deployed on the client sites (factories, warehouses, shops, etc.) Set of advanced management and administrative functions Built using Scalagent JMS Configuration consist of a server and several gateways 7

PLAN Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusions 8

HYPERMANAGER HyperManager in Spinnaker project (abstraction level) 9 ECW HM Other Partners Bare metal, RFID, etc.. Software

HYPERMANAGER Monitor and to act automatically on each element of the architecture 10 Equipments HM Customer ECW Central Gateway HM Site ECW Site Gateway HM Site ECW Site Gateway HM Gateway ECW Gateway HM GW ECW GW HM GW ECW GW HM GW ECW GW HM Supervisor Monitor the behavior of local gateway events Report on the health of the ECW Gateway to the upper layer Monitoring the behavior and state of local gateways Ensuring traceability of local gateways behaviour Handle failure in an automatic manner Handling configuration and reconfiguration Orcheastring firmware and software deployment and updates Offering client oriented facilities Managing software versioning Provide cloud-base hosting for customer’s central servers, as an alternative to local hosting on the customer premises

HYPERMANAGER Component model 11 HM Site HM Gateway HM GW Equipments ECW Central Gateway ECW Site Gateway ECW Site Gateway ECW Gateway ECW GW ECW GW ECW GW HM Customer HM Site HM GW HM GW HM Supervisor

HYPERMANAGER USE CASE 12

PLAN Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusions 13

HYPERMANAGER INDICATORS Different Indicators per level Machine (Cpu, Memory,...) Mediation (components, JMS queues,...) HMI EPCIS errors Accessibility by: JMX DB Native library 14

PLAN Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusions 15

HYPERMANAGER - IMPLEMENTATION Upon ProActive Parallel Suite Indicators state exchange between levels: Pull Push (critical events) 19/42 Indicators implemented (25 available) Automatic event handling – 2 cases Events stored in DB (Hibernate + SQLite) on L1 JNI, Plain SQL 16

HYPERMANAGER - IMPLEMENTATION 17 HM Customer Host with ECW components Site1 RM HM Site GW1GW2 HM GW HM GW GW3 HM GW Site2

PLAN Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusions 18

DEMO Main starting host (Antofagasta) 4 virtual machines 2 per 1 site Critical events simulation on Hypermanager level Temporary solution NX technology 19 JMX HM ECW

PLAN Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusion 20

CONCLUSION & FUTURE WORK Extend a list of implemented indicators GUI improvement Implement other remaining levels Lack of support from Tagsys  21

QUESTIONS 22