Smart Objects and Services

Project Presentation

Name

SmartLight

Group Composition

Enshuo ZOU et Thai Ha NGUYEN

Scenario :

Object Shape :

Name of the contact at Reims

arnaud BILLAUDEL

Sketch of the Object from Reims :

Picture of the Object without instruments and electronics :

i.imgur.com_sygacj2.jpg

Picture of the Object with instruments and electronics outside on the same table (put some circles and arrows on the picture to show where you're going to integrate all of these) :

i.imgur.com_4lbc9zj.jpg

Picture of the finished Object (all is integrated):

i.imgur.com_lkmqkaj.jpg

Demonstration Video :

Youtube SmartLight Video

Hardware specifications :

List :
sensor or actuator reseller link seller reference links to datasheet or technical document
Capteur de lumière de précision 1127 GoTronic 25486 http://www.gotronic.fr/art-capteur-de-lumiere-de-precision-1127-12101.htm
Adaptateur 1101 pour capteurs Sharp GoTronic 25465 http://www.gotronic.fr/art-adaptateur-1101-12080.htm
Capteur de mesure Sharp GP2Y0A021YK GoTronic 24565 http://www.gotronic.fr/art-capteur-de-mesure-sharp-gp2y0a021yk-11539.htm

Specifications and interface of the service on the object

There are two services on the object:

Specifications of the interface of high added value service

There are two high added value services for our project:

 second container

To realize there services, we created a intermediate layer to receive the data sent from the object, and treat these data to get the different states. With the distance data, we can get the states like: the user is present or not. For the brightness data, the states are: bright and not bright. Then we mix the two types of states to get a mixed state, and this is the data that we need to send to the layer of high added value service. Note : (including a figure on the orchestration between services on objects and information systems)  first container on pc

Project Files:

. wcc of the two containers (embedded and on the remote PC) :
Beans added for the embedded container (for the service on the object) ** (DLL and Source code for each of them)
Beans added for the remote PC container (for the high added value service on the PC) ** (DLL and Source code for each of them)
Chesklist to install the embedded service on the object

(N.B. As there is a bug from Wcomp for our embedded service, this step is not necessary for us.)

Chesklist to install the remote service/application on the PC

Results of the relations with Reims (being factual without personal opinion)

The collaboration with Reims learned us:

In result, the prototype was made ​​as commended, except that there are two small remarks:

Prospects :

Possible extensions of the object
Possible extension of the service on the Object
Possible extension of the high added value Service
Possible GUI for data visualization