.

Geo Informatics 1-2008
article figure 3: geodan movida system overview the operators, as is the case at the bp plant in cherry point. furthermore, communication can even be established with other assets. this offers the option to re-programme devices triggered by their location or the locations of others. as mentioned above it seems reasonable to take advantage of programming the sensor devices directly. especially such high performance devices like the falcom mambo perlocator which unifies gps technology, cellular technology, bluetooth connectivity and motion detection. be used in the expressions. they are filled automatically by movida each time a new location enters the location server. besides common java syntax, specific functions are implemented to enable spatial functions, date functions and other functions that are useful for alert conditions. application api and visualisation movida offers a ready-made client for the visualization of tracked persons and objects. the application api therefore is intended for the integration of the movida platform into a correspondingly enterprising it environment. generally not all movements and positions received are to be visualized as well. “that would be the same as permanently watching the logfile of one’s wlan router,” says schneider. in most cases visualization is required in alert situations. therefore companies should not be interested in visualizing all events in between, but rather try to respect and protect their employee’s location privacy. of location privacy was not present in people’s minds. when location systems track users automatically, they generate an enormous amount of potentially sensitive information. privacy of location is about controlling access to this information. when applying location services in a business context, issues of location privacy are not to be underestimated. at best only the most necessary personal location information should be visualized. even if not visualized, a tremendous amount of data will be stored. these data should be kept only for a critical time-phase, like 24 hours. for analytical purposes a de-personalisation or aggregation should be applied. that should also count for the badges too, as they are better not to be personalised but can have a given categorisation. concerning legal issues emerging from location services most governments are trying to catch up but still lag behind. there is an extensive public discussion about location privacy concerning the installation of cctv cameras, the monitoring of mobile phone activity and car detection. at the moment a strong political drift goes for a maceration to ease location disclosure – partly nurtured by the omnipresent fear of terrorism. however, location services are considered to be very effective when concerned with operational safety. but greater involvement of the workers’ council is necessary to allay their doubts concerning the right of privacy, enabling them to have some influence on ensuring location privacy. commodification of location on the face of it the utilisation of location seems to be another resource which ought to be exploited carefully. it holds enormous value for the optimisation of business processes and safety issues whereat location privacy should not be forgotten and always be treated with care. furthermore the choice of sensors will be not easy in the future and will have a huge impact on the functioning of all location systems. all in all, the potential of these location systems, and especially their ability to combine positioning, rules and communication, seems to be very promising for a big market in the future. florian fischer ffischer@geoinformatics.com is a contributing editor of geoinformatics. for more information on the topics in this article, visit: www.rfidjournal.com/article/articleview/2389/1/1 www.multispectral.com/news/news-121507.html www.falcom.de www.falcom.de/ www.multispectral.com www.multispectral.com www.ubisense.net www.ekahau.com rule definition for alerts events that can be triggered are stored as rules in the movida database. expressions define when, or under which conditions, the events are triggered. these expressions are called alert conditions, because this type of event is generally called an alert in movida. alert conditions are boolean expressions returning true or false. if the value true is returned then the system is triggered to send notifications (alerts) to the specified destinations. if the value false is returned, then nothing will happen. variables such as current (for the current position), previous (for the previous position) and speed can location privacy until recently people did not usually have access to reliable and timely information about the exact location of others. therefore, the concept any of the laptops enters the main building: (within(previous_position,{getzoneid(“main building”)}) == false && within(position,{getzoneid(“main building”) }) == true) && (getdeviceownerparameter(“ltype”) == “laptop”) any of the laptops leaves the first floor: (within(previous_position,{ getzoneid(“first floor”) }) == true && within(position, { getzoneid(“first floor”) }) == false) && (getdeviceownerparameter(“ltype”) == “laptop”) the maintenance date is january 7 2007: getdeviceownerparameter(“maintenance date”) == “20070127t000000” rule definition for triggering events 50 january/february 2008
Powered by fluidbook tm