Professional Documents
Culture Documents
Location Determination
using the
Trapeze LA200
1
Abstract
The ability to track and check the location of people or equipment in real time
has a number of application areas such as child safety, prisoner tracking and
supply chain to name but a few. Wi-Fi location determination is a technology
that has been developed in recent years, that utilises existing Wi-Fi equipment
such as those installed in personal computers, personal data assistant’s
(PDA) and mobile phones. The technology uses modulated Wi-Fi
transmission signals to detect the presence of a device, which does not
necessarily have to be connected to the network in question, just visible to it,
the system is then able to determine the position of the device based on the
signals received from the various Access Points (AP).
2
Acknowledgements
I would like to thank my project supervisor, Dr. Kevin Curran for highlighting
the availability of the Trapeze LA200 equipment and the subsequent idea of
utilising it in my work and in this project, his assistance and understanding of
my situation that enabled me to complete the report.
I would also give a special word of thanks to Eoghan Furey, a current PHD
student who was a fellow part-time student, for his advice and guidance in the
location awareness arena, not forgetting the other part time students namely
Jason McDevitt, Gerald Galway and Francis Doherty for their help and
encouragement over the last five years.
I also wish to acknowledge Stelios Haji-Ioannou and Michael O’Leary for low
cost airlines; these have enabled me to travel from my new home in Geneva
to complete the last year of the course.
I wish to thank my wife, family and friends for their support and prayers over
the years.
And finally you, who ever you are, for taking the time to read this report.
3
Declaration
“I hereby declare that for a period of two years following the date, on which
the dissertation is deposited in the Library of the University of Ulster, the
dissertation shall remain confidential with access or copying prohibited.
Following the expiry of this period, I permit the Librarian of the University of
Ulster to allow the dissertation to be copied in whole or in part without
reference to me on the understanding that such authority applies to the
provision of single copies made for study purposes or for inclusion within the
stock of another library. This restriction does not apply to the copying or
publication of the title and abstract of the dissertation.
4
List of Acronyms
AP Access Point
API Application Programming Interface
BBC British Broadcasting Corporation
DGPS Differential Global Positioning System
EPE Ekahau Positioning Engine
ESS Ekahau Site Survey
FM Frequency Modulation
GNSS Global Navigation Satellite System
GPS Global positioning system
GSM Global System for Mobile Communications
GUI Graphical User Interface
HCI Human Computer Interaction
IEEE Institute of Electrical and Electronics Engineers
IR Infrared
MAC Media Access Control
PDA Personal Digital Assistant
PPS Precise Positioning Service
RADAR Radio Detection and Ranging
RF Radio Frequency
RFID Radio Frequency Identification
RSSI Received Signal Strength Indication
RTLS Real Time Location System
SPS Standard Positioning Service
TDOA Time Difference of Arrival
VoWi-Fi Voice over Wi-Fi
WLAN Wireless Local Area Network
WPAN Wireless Personal Area Network
WYSIWYG What You See Is What You Get
XML Extensible Mark-up Language
5
6
Table of Contents
Acknowledgements
3
Declaration.....................................................................................................................4
List of Acronyms...........................................................................................................5
Table of Contents...........................................................................................................7
List of Figures .............................................................................................................11
List of Tables...............................................................................................................13
1 Introduction...............................................................................................................14
1.1 Aims & Objectives...........................................................................................15
2 Location Determination Technologies......................................................................17
2.2 Mobile Cellular Systems..................................................................................17
Optical Vision........................................................................................................18
2.6 Rosum..............................................................................................................20
2.7 Skyhook hybrid positioning system (XPS)......................................................20
2.8 Ultrasonic Location Determination..................................................................21
2.9 Infrared Location Determination.....................................................................21
2.10 Bluetooth Location Determination................................................................22
2.11 Inertia tracking...............................................................................................22
2.12 RFID Location Determination.......................................................................22
2.13 Wi-Fi..............................................................................................................23
2.14 Wi-Fi Fingerprinting......................................................................................23
2.15 Location Determination Applications ...........................................................24
2.15.1 Mapoint ......................................................................................................24
2.15.2 Dodgeball....................................................................................................24
2.15.3 Friend finder ...............................................................................................24
2.16 Potential applications of Wi-Fi Location Determination...............................24
2.16.1 Prisoner Monitoring....................................................................................25
2.16.2 Child Safety................................................................................................25
2.16.3 Indoor gaming.............................................................................................25
2.16.4 Supply Chain...............................................................................................25
2.16.5 Security.......................................................................................................25
7
2.16.6 Healthcare...................................................................................................25
2.16.7 Location Based Access..............................................................................26
27
3.1 Microsoft Research Group RightSPOT...........................................................27
3.2 Microsoft Research Group RADAR system....................................................28
3.3 Trapeze LA200 ...............................................................................................28
3.4 Place Lab software ..........................................................................................28
3.5 AeroScout Wi-Fi RFID ...................................................................................29
3.6 Ekahau RTLS...................................................................................................30
4 Trapeze LA200 Wi-Fi Location Determination......................................................32
4.1 LA200 major components................................................................................33
4.1.1 The Trapeze Dashboard................................................................................33
4.1.2 The Trapeze Webpage Dashboard................................................................35
4.2 Limitations of the Trapeze LA200 ..................................................................39
4.3 Advantages of the Trapeze LA200 .................................................................39
5 Lean Six Sigma - Work Study .................................................................................40
5.1 Aeroscout and IMEC Technologies................................................................41
5.2 Ekahau and Polycom.......................................................................................41
5.3 Ekahau & Rautakesko .....................................................................................41
5.4 Aeroscout and Mine Site Technologies..........................................................42
5.5 Product flow analysis.......................................................................................42
6 Requirements Specification and Analysis................................................................45
6.1 Problem Specification .....................................................................................45
6.2 Objectives of System ......................................................................................45
6.3 Design Methodology........................................................................................46
6.3.1 Waterfall Methodology.................................................................................46
6.3.2 Evolutionary development............................................................................47
6.4 Requirements Specification.............................................................................48
6.4.1 Functional Requirements .............................................................................48
6.4.1.1 User ...........................................................................................................48
6.4.1.2 System........................................................................................................48
6.4.2 Non-Functional Requirements .....................................................................48
6.4.3 Hardware Requirements ...............................................................................49
6.4.4 Software Requirements.................................................................................49
8
6.4.5 Development Languages ..............................................................................50
7 Design Phase.........................................................................................................51
Stages of the System..............................................................................................54
7.6.1 User Use Case Diagram..............................................................................54
7.6.2 User Use-Case Diagram Descriptions........................................................54
7.6.3 System Use Case Diagram .......................................................................55
7.7 Class Diagram..................................................................................................55
7.8 Activity Diagram.............................................................................................56
7.9 Sequence Diagram...........................................................................................56
8 Implementation.....................................................................................................58
8.1 Equipment Connection.....................................................................................58
8.2 Program GUI....................................................................................................58
8.4 LA200 Database...............................................................................................63
9 Testing....................................................................................................................64
9.1 Unit Testing.....................................................................................................64
9.1.1 Splash Screen & Login ................................................................................64
9.1.1 LA200 System and network..........................................................................65
9.1.2 GUI to API component.................................................................................65
9.1.3 API to the LA200 & LA200 Database component.......................................66
9.1.4 GUI to local replica database component....................................................66
9.1.5 Reporting and Graphing Component............................................................67
9.2 Integration Testing...........................................................................................67
9.3 Performance Testing........................................................................................68
10 Evaluation...............................................................................................................69
10.1 Database Component.....................................................................................69
10.2 Graphics.........................................................................................................70
10.3 Calibration......................................................................................................70
10.4 Issues during development.............................................................................70
10.4.1 API issues....................................................................................................70
10.4.2 Setup effort..................................................................................................71
10.4.3 TAG testing.................................................................................................71
10.4.4 Stationary - Additional records...................................................................71
10.4.5 Reporting of wrong location ......................................................................71
10.4.6 WLAN coverage / Inactive result ..............................................................72
9
10.5 Future Work...................................................................................................72
11 Conclusion..............................................................................................................74
References....................................................................................................................75
Appendix A – LA200 database schema.......................................................................77
10
List of Figures
Figure 1: How location is determined from satellites .................................................19
Figure 2: ZigBee Mesh Structure Network..................................................................20
Figure 3: Rosum System Architecture ........................................................................20
Figure 4: Trolley Scan RFID-Radar System ...............................................................23
Figure 5: Wireless base systems and their location range resolution .........................27
Figure 6: Key components in the Place Lab architecture ...........................................29
Figure 7: AeroScout Active RFID tag.........................................................................30
Figure 8: Ekahau Tag...................................................................................................31
Figure 9: Trapeze LA200 Appliance ..........................................................................32
Figure 10: Trapeze Dashboard for the LA200 ............................................................33
Figure 11: Trapeze LA200 Connection Details Form.................................................34
Figure 12: Trapeze Dashboard Device List Screen Appliance....................................34
Figure 13: Trapeze Dashboard Layout Locales ..........................................................35
Figure 14: Trapeze Dashboard fingerprint locations ..................................................35
Figure 15: Trapeze Web Dashboard login screen........................................................36
Figure 16: Trapeze Web Dashboard Summary screen ...............................................36
Figure 17: Trapeze Web Dashboard Device List screen.............................................37
Figure 18: Trapeze Web Dashboard Monitor screen...................................................37
Figure 19: Trapeze Web Dashboard Monitor Screen..................................................38
Figure 20: Trapeze Web Dashboard Fingerprint screen..............................................38
Figure 21 A heat map from the Ekahau / Rautakesko system.....................................42
Figure 22: Lean Six Sigma Point to Point Diagram....................................................43
Figure 23: Point to Point after improvements..............................................................44
Figure 24: Traditional Waterfall Methodology ...........................................................46
Figure 25: Evolutionary Development Model.............................................................47
Figure 26: Trapeze System Concept............................................................................53
Figure 27: Overview of the System.............................................................................53
Figure 28: User Use Case Diagram............................................................................54
Figure 29: System Use Case Diagram.........................................................................55
Figure 30: Class Diagram............................................................................................56
Figure 31: Display report for selected user..................................................................56
11
Figure 32: High-Level Sequence Diagram for the system...........................................57
Figure 33: Trapeze Web Dashboard Summary screen................................................58
Figure 34: The application splash screen.....................................................................59
Figure 35: The login screen.........................................................................................59
Figure 36: The main GUI screen.................................................................................60
Figure 37: Connect LA200 online database.................................................................61
Figure 38: Connect to local replica..............................................................................61
Figure 39: MAC address selection..............................................................................61
Figure 40: Graph of places visited...............................................................................62
Figure 41: Graph of routes taken.................................................................................62
Figure 42: Successful login confirmation....................................................................64
Figure 43: Unsuccessful login.....................................................................................64
Figure 44: LA200 API connection error......................................................................65
Figure 45: Successful connection to LA200 database.................................................66
Figure 46: Successful connection to local replica........................................................66
Figure 47: Unsuccessful connection to local replica...................................................66
12
List of Tables
Table 1: LA200 Tracking performance ......................................................................33
Table 2: Trapeze LA200 Dashboard hardware requirements......................................51
Table 3: Summary of Main Screen Components Shown in Figure 36........................60
Table 4: Integration Testing.........................................................................................67
Table 5: Evaluation against User Functional Requirements........................................69
Table 6: Evaluation against System Functional Requirements....................................69
13
1 Introduction
With the development of GPS, high speed Wi-Fi and mobile computing there
has been a growth in the areas of location determination and supplying an
individual and others with current location information relevant to the
individual or a piece of equipment current location. Location determination can
also be used to track social patterns for example finding out who interacts with
whom, how often and for how long. Location determination and the current
and historical movement of people and equipment is a useful tool for example
when looking to develop more efficient work practices by removing wasted
time or movements. A current highly promoted example into equipment
movements is being carried out by the British Broadcasting Corporation
(BBC). They are carrying out an experiment on tracking the movement of a
shipping container by attaching a Global Positioning System (GPS) receiver to
a single shipping container and are following the containers movement around
the world for a year.1
Trapeze Networks quote a ninety five percent accuracy rate to less than three
meters for their LA200 system for indoor Wi-Fi location determination which,
when compared to other location determination technologies is quite good
when you consider other technologies such as Global Positioning System
(GPS) technology, which simply does not work indoors as it requires a direct
line of sight to the satellites, and mobile phone positioning systems that have
an accuracy of around one hundred meters, Radio Frequency Identification
1
http://news.bbc.co.uk/2/hi/in_depth/business/2008/the_box/default.stm
14
(RFID) can offer better accuracy as long as the item or person being tracked
is very close to the sensor.
Chapter five discusses the relationship between the Lean methodology and
Six Sigma Methodologies to this project and gives some examples.
15
Chapter seven describes the design phase of the project and in particular
discusses the hardware and software components in detail, the design
constraints, HCI guidelines and system architecture.
Chapter eight describes the implementation of the system and the different
components within the system.
Chapter nine describes the testing methodologies and the testing phase of the
project.
Chapter ten is a critical evaluation of the project against the requirements laid
out in chapter six and finally the opportunities for future work in this arena.
Chapter eleven is the conclusion which gives a review of the project and
information contained within this report.
16
2 Location Determination Technologies
Every location determination technology has its advantages and
disadvantages in a number of areas namely; if they are designed to operate
inside or outside, how they determine their position internally or via a network
connection, their cost, their susceptibility to interference and their location
determination accuracy.
2
http://www.answers.com/topic/radar
3
http://science.howstuffworks.com/radar.htm
4
http://www.locatemobiles.com
17
Optical Vision
Computer visual techniques can be used in location determination systems.
A desktop augmented reality system using optical markers was reviewed by
Kato et al (2000). It used the desktop area as they envisaged it as system for
virtual face to face meetings that would be held around a table. The computer
would then use the special markers to track the meeting attendees in a virtual
manner. Alternatively the optical markers could be used to track movement
and ultimately location in a motion capture system (Benford, 2005).
5
http://electronics.howstuffworks.com/gps1.htm
18
does have some limitations namely receivers must be in ‘line of sight’ with the
satellites which means they cannot work indoors or near tall buildings which
block or reflect the signal, a phenomenon known as ‘urban canyon effect’.
Figure 1 shows how a location is determined from satellites orbiting the earth.
2.5 ZigBee
ZigBee is a name given to the IEEE 802.15.4 standard. The term is derived
from the erratic flight patterns that bees make while they are collecting pollen
from flowers, and is similar to the numerous connections between all the
devices in a totally wireless network. ZigBee is aligned to connectivity
between small packet devices, its ‘bigger brother’ in the Wireless Personal
Area Networks (WPAN) arena, Bluetooth, is aligned to the connectivity
between large packet devices such laptops, cellular mobile phones and
headsets.7
In a ZigBee mesh structure network, as shown in Figure 2, a mobile nodes
location can be triangulated by using Received Signal Strength Indication,
(RSSI), to an accuracy of five meters from three or more adjacent static nodes
(Cambridge Consultants, 2006).
6
http://encarta.msn.com/encyclopedia_761579727_2/Global_Positioning_System.html
7
http://www.wisegeek.com/what-is-zigbee.htm
19
Figure 2: ZigBee Mesh Structure Network
2.6 Rosum
Rosum uses commercial digital, analogue and mobile television signals for
location determination. Its advantage over other systems is that it is a hybrid
system that combines the benefits of GPS with television transmitter signals
to determine location. When the GPS component cannot determine the
location accurately typically in an urban area or inside a building the location
can be derived from television transmitter signals which can penetrate a
building.8 Figure 3 shows the Rosum system architecture.
8
http://www.rosum.com/rosum_technology.html
9
http--www.rosum.com-images-architecture.jpg
20
access points to calculate the position of a mobile device. Based on the
required accuracy of the location determination and in an effort to reduce
power usage the system disables or enables input from the various
information sources. GPS and mobile cellular system location determination
are calculated using the methods discussed in earlier sections of this report.
21
2.10 Bluetooth Location Determination
12
A Bluetooth system like Tadly’s Topaz System is made up of three major
components namely the positioning server, the access points and the tags.
The tags can be either special Topaz System Bluetooth tags or any Bluetooth
equipped device such as a mobile phone. The system can provide with ninety
five percent reliability an accuracy of around two meters. It can detect a
Bluetooth tag by several methods namely, using RSSI to triangulate the
location, putting an access point in every room and the nearest AP to the tag
indicates its location. They also offer for a highly compartmented area the
use of a hybrid Bluetooth-IR system.
22
(rfid-radar.com, 2007). To improve accuracy ‘chokepoints’ may be used, these
are additional readers and antenna that are installed at entry and exit points,
they are used to detect when a tag enters or leaves a particular area.
Antenna array
Reader
Tags
2.13 Wi-Fi
Wi-Fi is the generic name given to any of the 802.11 group of specifications
for the wireless local area network (WLAN) interface developed by the
Institute of Electrical and Electronic Engineers (IEEE). With the increasing
number of hotspots, public access points, high speed internet access and the
ability to easily set up a network without the need for any cabling has led to
the take off in popularity of WLAN’s
23
device is taken to a location and the system determines the probable location
based on the fingerprints. The greater number of fingerprints taken will
improve the accuracy of the location determination.
2.15.1 Mapoint
Mappoint.com is an example of an application for users who do not disclose
their position to anyone else; it displays the user’s position on a map and
nearby points of interest.
2.15.2 Dodgeball
www.dodgeball.com is an example of an application for users who wish to
display their position to a select group; it is used by mobile phone users and
works by users telling www.dodgeball.com who their friends are, then when a
user is out and about they sent a text message to Dodgeball with their
location, Dodgeball then send a text message to all their friends and reports
back if there are any of their friends in the vicinity.
24
The use of Wi-Fi location determination technology could be utilised in a
number of applications namely:
2.16.5 Security
For example, if valuable equipment is no longer detected in its normal area
this action could activate an alarm for the security staff and then allow them to
track and find it while it is still within the range of the WLAN.
2.16.6 Healthcare
25
For example in a hospital environment patients could wear wristband tags that
allow them to be tracked throughout the hospital. If a patient tries to leave
without being discharged, nurses are alerted to the situation and are able to
get them and return them to their ward. This would be particularly useful for
patients suffering from dementia or Alzheimer’s disease. Additionally it could
be advantageous if important staff may wear tags that would allow,
particularly in an emergency situation their location to be quickly identified.
26
3 Wi-Fi Location Determination Technologies
A number of different systems have previously used WLAN access points as
beacons from which to estimate location. Numerous other indoor location
systems have been developed that make use of the sensory technologies
discussed earlier but the major drawback with these is that they all require the
installation of specialised hardware in the environment to be maintained. The
high costs of these technologies are also prohibitive making them unsuitable
for personal or social applications that are to be used in people’s daily lives.
They do however offer very high accuracy levels and are therefore used by
many commercial organisations.
27
Microsoft research group developed an algorithm, that they called
RightSPOT, which used a ranking system of the available Frequency
Modulation (FM) radio stations rather than their relative signal strengths to
determine location. With eight radio stations they were able to get an
accuracy rate of approximately eighty percent (Krumn et al, 2003).
28
accuracy for the system is around twenty meters. Figure 6 shows the main
components, (LAMARCA et al., 2005).
14
http://www.placelab.org/publications/pubs/pervasive-placelab-2005-final.pdf
15
http://www.aeroscout.com/leadcapture/files/AeroScout+System+Data+Sheet_0.pdf
29
Figure 7: AeroScout Active RFID tag
16
http://www.rfidjournal.com/article/articleview/2050/1/1/
17
http://www.ekahau.com/?id=4510
30
The EPE uses software based algorithms to calculate the position of a tag.
However before the EPE can determine the location work it needs the site
survey calibration information from the ESS. The ESS collects the information
on the coverage and RSSI of each AP in the network across the area to be
covered. The ESS gathers the calibration information by a person carrying
18
the system and walking around the area to be covered. Ekahau have also
developed Wi-Fi tags an example of which is shown in Figure 8.
18
http://www.ekahau.com/?id=4130
19
http://www.ekahau.com/?id=4220
31
4 Trapeze LA200 Wi-Fi Location Determination
The LA200 unit was developed originally by Newbury Networks, who in
December 2008, were bought over By Trapeze Networks. Trapeze then in
turn rebranded the unit as the Trapeze Networks Location Appliance LA200.
However prior to this Newbury Networks strategic business partners had
rebranded the unit under several different names namely the Meru Networks
Meru E(z)RF Location Manager, the Nortel Networks Nortel WLE2340 and
now the Trapeze Networks Trapeze LA200.20 The unit will only be referred to
as the LA200 in this report. A picture of the actual unit is shown in Figure 9.
21
Figure 9: Trapeze LA200 Appliance
The Trapeze Networks Location Appliance LA200 provides the ability in real
time to quickly and accurately locate and track assets, people or practically
anything that has a or is attached to a Wi-Fi transmitter over an existing Wi-Fi
network. The LA200 can offer location determination for up to two thousand
Wi-Fi devices over a WLAN. It also provides the capability to run custom or
enterprise applications that require the ability to provide location sensitive
content or security and track assets. To ensure compatibility the LA200 is fully
Wi-Fi compliant this allows the system to use the active Wi-Fi tags from other
companies such as, AeroScout, Ekahau, Newbury Networks and Pango.
20
http://www.newburynetworks.com/company-about.htm
21
http://www.mobiledataforce.com/Products/pointsyncRFID_Overview.stm
32
Accuracy at 10 meters 99%
Accuracy at 5 meters 97%
Accuracy at 3 meters 95%
Average seek time 30 sec
Fastest seek time 10 sec
Number of devices tracked 2000
22
Source la200 datasheet
33
Figure 11: Trapeze LA200 Connection Details Form
After the Dashboard connects to the LA200 Appliance a ‘Device List Screen’
appears, it shows a summary of each device visible to the LA200. Options are
available to view devices by server, locale or network. Figure 12 shows a
typical device list view on the Dashboard.
An image file containing a scaled plan of a building can be imported into the
system and different locales added by the user. For example from the
University of Ulster System the light blue area in Figure 13 represents the ‘MG
Floor2 Staff2’ locale, which contains a number of smaller offices.
34
Figure 13: Trapeze Dashboard Layout Locales
After the locales have been identified the actual physical of the fingerprints an
AP’s are added. The points where fingerprints have been taken are
represented by a green flag as shown in Figure 14 the example is from the
University of Ulster System at the Magee Campus.
The LA200 system also comes with a web based dashboard interface to
access the system; it provides similar functionality to the dedicated
Dashboard application, however it does not have the capability to display the
live maps only a data table of the information. The next section will describe
the main web interface screens from the University of Ulster LA200 system at
the Magee Campus. Figure 15 shows the web based Dashboard login screen.
35
Figure 15: Trapeze Web Dashboard login screen
Figure 16 shows the web based Dashboard summary screen that displays summary
information on the system, network and devices visible to the network.
The web based Dashboard device list screen that displays information on all the
devices visible to the network is shown in Figure 17.
36
Figure 17: Trapeze Web Dashboard Device List screen
Using the web based Dashboard monitor screen as shown in Figure 18 the
user can then enter a particular MAC address and date range for any given
time period in the last thirty days and the system will display the location of
that tag for the given date range as shown in the example in Figure 19.
37
Figure 19: Trapeze Web Dashboard Monitor Screen
The system will also display the fingerprint information it holds for a particular
fingerprint point. For example in Figure 14 fingerprint ‘mp24’ is shown in the
graphic. From the web based Dashboard fingerprint screen Figure 20 shows
the detail of the ‘mp24’ fingerprint location in a graphical representation using
green and purple bars.
38
4.2 Limitations of the Trapeze LA200
While the LA200 has many advantages it does have certain limitations, issues
and costs. These include:
• Requires the purchase of the LA200 system box for the network which
at current prices, is around fifteen thousand US dollars.
• There are range limitations due to the penetration of Wi-Fi signals,
through solid objects such as building walls;
• While not purely a LA200 issue there are privacy issues, namely the
ability to track individuals without their consent.
• While the system is fully compatible with Wi-Fi and can use the Wi-Fi
signals from laptops, PDA’s etc any piece of equipment or person to be
tracked requires a Wi-Fi tag and these cost around fifty pounds each
which if you wanted to give one to every student on a campus or
employee in a business could end up quite expensive.
23
http://www.trapezenetworks.com/file.cfm?content=443&pageId=84&tagId=111
39
5 Lean Six Sigma - Work Study
Lean Six Sigma is the collective term given to the parsing of the Lean
Methodology and the Six Sigma methodology. The term Lean is used to
describe process of reviewing work methods to improve standards, increase
productivity and make better use of resources. It involves reviewing the
activity and removing the waste in the process by removing unnecessary or
non value adding work. Arranging or adding equipment to make the activity
easier or take less time to complete. The Six Sigma term is used to describe
the process of applying statistical analysis on data to devise solutions that will
reduce the causes of variation and defects.
It could be envisaged that Wi-Fi location technology will have little impact on
the design of the product or the type of materials used however it could have
a significant impact on improving the manufacturing processes, human
intervention reasons and work practices. By analysing the movements and
non-movements of people, equipment, raw materials and finished product in
the manufacturing process, it could be possible to discover the actual sources
of waste.
40
action include those working at a slower pace, due to their capability, training
or other issues. Some recent examples of the use of where Wi-Fi and Lean
Six Sigma methodologies have been used together include.
24
http://www.sixthsigma.com/2009/02/flexible-e-kanban-manufacturing.htm
25
http://www.aeroscout.com/content/news-and-events/press-releases/thermoking-170209/thermo-king-
improves-manufacturing-operatio
26
http://www.wi-fiplanet.com/news/article.php/3707806
41
and adjust their product arrangements accordingly. Figure 21 shows a heat-
map produced by the system. 27
42
In the real work a person or product is followed by an auditor who literally will
attach them selves to that person or object and follow and record their every
movement or lack of movement and record all the information on a various
data collection sheets. One such sheet is the point to point diagram shown in
Figure 22. The circles represent doing a task and the lines represent
movement from one area to another.
In Figure 22 it is quite apparent that there is a lot of wasted time for the
person moving between the bench area and the oven area because these two
pieces of equipment are far apart and the waste comes from the fact they are
used quite a lot. It would be better if the equipment was rearranged so that
these two pieces of equipment were much closer together and some of the
steps consolidated.
AREA NAME: BEFORE - Carrier Assembly - Ball Bearings PREPARED BY:
SUPERVISOR: DATE:
NOTE: Depict rough scale of equipment layout; and, draw a point to point diagram of the complete product flow
40
35
OVEN
33
31
Bench
Tool
21
23 Box 26
22 8
24 Trash
Press 19 14 2 4 9 6 10
39 30 18
13 12 16 20 34 38
44
42 32
28 Part 15
Vice 41
Box 17
36
43
29 25 3 1 5 7
37 27
11
Parts Rack
Figure 23 shows the same process as Figure 22 after the product flow
analysis component of the Lean methodology has been applied. In this
instance some steps have been consolidated, reduced from forty two to
twenty eight.
Broach
Oven
Press
Press
1 2 3 26 27 28
9 11 14 17 20 23
4 5 6
10 12 1543 18 21 24
7 8
13 16 19 22 25
Figure 23: Point to Point after improvements
44
6 Requirements Specification and Analysis
This chapter will specify the problem; list the system objectives, the chosen
design methodology, specification of the functional, non-functional, software
and hardware requirements.
45
to provide analysis charts on the movements this will be done by extracting
the data from the LA200 database using the LA200 Application Programming
Interface (API) using code written in Perl, Ruby or Python. The data will then
be imported into Microsoft Excel for analysis and charting and then imported
into the GUI for use by the user. The application will run on any Windows XP
operating system, with service pack two or later installed. The user interface
will contain number of selectable options that will access the data from the
LA200 database and present the data in a graphical form to the black belt or a
lean practitioner.
29
http://www.maxwideman.com/papers/plc-models/1990s.htm
46
the waterfall methodology is typically intended for large projects which this
project is clearly not and more importantly the methodology does not have the
ability to easily handle major change or upgrades late in the process which
are envisaged in this system.
47
6.4 Requirements Specification
The requirements for this project are split into two distinct areas: functional
requirements and non-functional requirements. The software and hardware
requirements are also listed in order that the full functionality can be
successfully implemented.
6.4.1.1 User
After starting the program, the user should be able to:
• Quit the program;
• Access the menu screen;
• Select the data that they require from the database;
• Report the data in a format that they desire;
• Export the data to Microsoft Excel – if desired;
• Graph the data on the GUI;
• View the software help at any time;
6.4.1.2 System
The LA200 provides and stores all the location data.
The system should:
• Have a permanent network and intranet connection;
• Have access to the LA200 and Dashboard;
• Have fully working GUI for the user;
• Run on any recent computer using Windows XP SP2 operating system;
• Access the location data provided by the LA200 system;
48
• Accessibility – The software should be easy to use with little training or
experience.
• Time Constraint – See project Gantt chart attachment A and the
required project completion date is 28th April 2009;
• Reliability – The system work all the time and provide a means to
handle errors with little or no input from the user. The data provided by
the system should be validated and verified were possible;
• Performance – The system should be able to carry out each task
requested by the user as quickly as possible;
• Extensibility – The system should be developed with future upgrades
and additional functionality being added at a later date;
• Maintainability – The program coding should be well documented and
laid out particularly to facilitate future upgrades and additional
functionality being added at a later date;
• Scalability – The system should be able to provide data for the current
maximum number of tags presently two thousand for a period of thirty
days in what ever format the user decides;
• Efficiency – The system should operate with the minimum adequate
resource levels to that ensure it performs at a level acceptable to the
user;
• HCI standards must be adhered to.
49
• Latest version of the Java Runtime Environment (JRE)
• Trapeze Networks Dashboard
• Trapeze Networks webpage
• Perl, Ruby, Python or Soap programming systems (as required)
• Visual Studio 2005
• Microsoft Excel 2003
• Custom made application
50
7 Design Phase
This chapter will discuss the detail of each component in the design phase of
the project.
51
tags position to a room or locale level each of which should have the
recommended number of fingerprints carried out.
52
Trapeze Custom
Dashboard App. Made
Positioning model Creation,
Maintenance and analysis Application
Trapeze LA200
802.11a/b/g Positioning Server
& Database
Wi-Fi network
Trapeze
API
Clients
Trapeze Web
Dashboard
To LA200
WI-Fi
Access Point
Network
Person with
Tag or Wi-Fi
source LA200
API
LA200
On-Screen Database
Display
of new
application
53
Stages of the System
This section will show the use case diagrams showing different user activities
and the system functionality.
Start Location
Awareness Application
Remove Person
Start Graphing User
tag from List
«extends»
«uses»
Select User To
Graph
«extends»
User
Add Person /
Display / to List
Print
Reports / Graphs
Figure 28: User Use Case Diagram
View Help
7.6.2 User Use-Case Diagram Descriptions
Use Case Name Start Location awareness Application
Exit Application
Primary Actor User
Data None
Description The user starts the application.
Preconditions None
Post Conditions The application loads.
54
There is at least one record for the appropriate tag.
Post Conditions The appropriate report is displayed.
Interface with
«uses» LA -200 API Software
Start Location
Awareness Application «uses»
Connect to LA -200
Database
Remove Per
Start Graphing User
tag from L
«extends»
«uses»
Select User To
Graph
«extends»
System
Add Perso
to L
Show
Reports / Graphs «uses»
Print Graphs
«uses» «uses»
Figure 29: System Use Case Diagram
Exit Application
Get graphs
from Excel
Show Help Screen Pass values
to Excel
55
MainForm LA200 Database
-port : SerialPort
-TotalRange : double
+MainForm()
+MainForm_Load()
+connectLA200() 1
1
+disconnectLA 200()
+sendUserToExcel(in message : string)
+selectUser ()
+RemoveUser()
+refreshData()
+displayGraph()
Figure 30: Class Diagram
+printGraph()
+mainForm_Quit ()
+helpScreen()
7.8 Activity Diagram
Figure 31 showing and activity diagram to show the process of selecting the
user MAC address to display.
Select user
Mac address
[ MAC Exists ]
[ No Wi-Fi
[ error records ]
message ]
[ Wi-Fi
Records ]
Display
Report
Figure 31: Display report for selected user
56
Location Awareness API LA200
Application Interface Database
All_ta
btn_selectUserClick ()
getSelectedUserData()
queryResult
57
8 Implementation
This chapter describes the functionality of the system and the implementation
stage of the project.
58
Figure 34: The application splash screen
As the prototype has the ability to track people this creates a “big brother”
issue and therefore would benefit from some sort of security system that
would have a username and password to gain access and restrict report to a
few “test” or special tags and the users own MAC address Therefore so it was
decided to add this feature to the scope, iterative and incremental approach
allows this unlike the waterfall methodology.
59
4
60
From the main GUI the use then can elect to connect to the online database
in the LA200 as shown in Figure 37 or use a local replica copy of the
database stored on the machine as shown in Figure 38.
To begin the user selects a MAC address from the dropdown list. The
dropdown list, as shown in Figure 39, this has all the MAC addresses that are
available to provide a report for the user.
After selecting the desired MAC address the user can then select from the
options to export the information to Excel or to display the graphs and reports
on the screen. Examples of the graphs are shown in Figures 40 and 41
61
Figure 40: Graph of places visited
62
8.4 LA200 Database
The GUI utilises the database within the Trapeze LA200 device to access the
data a Trapeze supplied API is available as a data access layer to enable
simple read only data retrieval from the LA200 database. The LA200
database is quite complex and outside the remit of this project, however in the
Appendix A, a full list tables, their showing configuration and fields has been
provided.
63
9 Testing
This chapter describes the testing section of the project. This is important part
of the process as it ensures that the system performs satisfactorily and meets
all the users’ requirements as laid down in the requirements specification in
chapter six.
64
9.1.1 LA200 System and network
The Trapeze LA200 equipment is central to the whole project and the
information it gives is only as good as the configuration and setup work done
when the system is installed. After the system has been set up to the
manufactures recommendations, this is an enormous task outside the remit of
this report. Testing of the setup can actually be done with one person using a
Wi-Fi enabled laptop connected to the network and running the Trapeze
Dashboard software, then as they walk around they can see themselves on
the Dashboard display and verify that all is correct with the configuration, if
errors are found then addition calibrations will have to be carried out in the
area.
30
Trapeze LA200 Deployment Guide Version 6.0
65
9.1.3 API to the LA200 & LA200 Database component
Having received the MAC address the API must now select all the rows of
data history relevant to that MAC address, and then pass these rows back to
the GUI. Unfortunately this is also failed as per section 9.1.2. However if the
system had worked correctly then the user would get a confirmation message
as shown in figure 45.
66
9.1.5 Reporting and Graphing Component
Having received the rows of data the system need to pass them into Microsoft
Excel where they can be manipulated into graphs and displayed for the user.
Figures 40 and 41 shown earlier in the report display typical results.
Predicted
N Test Case Actual Result P/F
Result
The GUI starts
up, the splash
screen is
displayed then
The splash, then
the login in
login then main
1 The GUI starts up screen is Pass
screen is
displayed after
displayed.
correct login
details entered
the main GUI is
displayed
The three test MAC addresses
The 3 tags are The 3 tags are
2 from the Ekahau tags are available Pass
there there
in the dropdown list to select.
The selected tag is passed to the
The data is API component
API and the appropriate data is
available for failed only able Partial
3 selected from the LA200 database,
graphing and to use local Pass
and passed back to the GUI for
reporting replica
reporting.
The GUI displays the report and The correct data Graphs are
4 Pass
graph and graph is shown displayed
67
9.3 Performance Testing
In this section the systems performance against the non-functional
requirements listed in the requirements analysis subsection, 6.4.2, are
checked.
• Accessibility – The software is easy to use even with little or no training
or experience. Only a few mouse clicks are required.
• Time Constraint – Project completed in time for required closing date of
28th April 2009;
• Reliability – Coding has been completed to handle errors and the data
provided by the system should be validated and verified were possible;
• Performance – The system can quickly carry out each task requested
by the user.
• Extensibility – The system was developed using the evolutionary model
and is well suited for adding upgrades and additional functionality at a
later date.
• Maintainability – The program coding is clear, structured and with
comments and documentation.
• Scalability – The system can provide data for the current LA200 limit of
a maximum number of two thousand tags for a period of thirty days in
what ever format the user decides;
• Efficiency – The system does not use an exorbitant amount of memory
or CPU.
• HCI guidelines have been followed.
68
10 Evaluation
The evaluation stage is a very important phase in a project as it reviews the
success of the final product against the desired outcomes that were specified
in the requirements section. This chapter checks the prototype system
developed in this project against the functional requirements from Chapter 6
and determines if the required functionality is present and acceptable.
Table 6 lists the system function requirements, and whether each requirement
was satisfied.
Requirement Satisfied?
Run on any desktop / laptop computer with Windows XP SP2 Yes
operating system;
Have a fully working GUI for the user Partial
Have access to the LA200 Fail
Have a permanent network and intranet connection Yes
Access the location data provided by the LA200 system Fail
Table 6: Evaluation against System Functional Requirements
69
an XML extract was used as an interim measure, due to the time constraints
of the project.
10.2 Graphics
It was decided not to add graphics to the system showing the location of Wi-Fi
devices as this functionality is already available on the LA200 dashboard also
this project is working on developing a just prototype system and due to the
time constraints, and limitations in the graphics capability of the Visual
Basic .NET Framework it was decided that this level of functionality was too
complex and outside this projects scope.
10.3 Calibration
Calibration was performed during the implementation of the LA200 system
and again by the Trapeze engineers in February 2009, however they
concentrated on a relatively small area, namely a single floor in a building in
comparison to the total area under Wi-Fi coverage at the University of Ulster
at Magee Campus.
To improve the accuracy you could give the floor plans for all the buildings in
the campus to the Trapeze engineers and let the choose the locations for all
the access points which could potentially mean moving every access point as
historically they were located in the centre of a room, however moving access
points is not really a cost effective option, it would be easier to add more
fingerprints this would give additional clarity especially if it was done at both
sides of every entrance and exit point.
70
To connect to the LA200 with out being an expert in the designated API
languages of Soap and Perl proved to be very difficult and time consuming
task for the author with no success at the end. Emails were sent to vendor for
help with getting data using the API with little success. Upon review for this
project and doing the data analysis live data directly from the LA200 database
is functionality that was more a nice to have than a necessity especially when
an almost live database could be extracted from database.
71
reporting correctly. Investigation showed that the user had moved to a slight
different location at their desk. As this was the test case and was being
monitored it resulted in the manual correction of records namely having to
rename the records from MS129 to MS130. This would not be acceptable or
sustainable as generally through out the test required a lot of manual effort to
“clean up the data”. to use the data to carry out significant statistical analysis.
If this had not been done then there would have been a lot of false
interpretations made.
However while this was envisaged as a niche market for use by those looking
to analyse movement of people, equipment, product or inventory such as
Lean Practitioners or Six Sigma Black belts then there is a lot of scope to
improve the system and utilise the full capabilities of the information that the
LA200 can prove, especially if the system could provide heat maps Figure 21
and point to point diagrams Figure 22.
Any work to improve or rearrange & improve the configuration of the wireless
network would be a big advantage to the calibration of the LA200 which would
provide greater accuracy
72
To utilise the information in the LA200 database fully is quite a complex task
and requires an in depth knowledge of Perl, Ruby and Soap scripting
language so to allow the system to be modified to extract live data into an
algorithm that would plot “point to point” diagrams on a map showing the
historical movements of people and equipment.
73
11 Conclusion
While a number of the more familiar location determination technologies have
limitations when it comes to working inside buildings, at a small area level of
resolution, fairly high accuracy rate without the need for substantial capital
investment the recent advancements with the Trapeze LA200 WLAN location
awareness system have allowed Wi-Fi technology to provide accurate live
and historical positional information. This project aimed to investigate the use
of the LA200 to provide information for an application for use by Lean
Practitioners or Six Sigma Black Belts to monitor the movements of people,
equipment, products or inventory in an area that was covered by a WLAN and
produce reports and graphs for them to use.
Initial requirements set out during analysis phase called for a GUI program,
created with Visual Studio 2005 that would interface with the LA200 database
and API and provide location data for the user’s selected MAC address. The
GUI program would then take the information and produce charts and a report
on the movements.
The specifics of the programs were defined in the design section, these
included diagrams showing the functionality of components, along with
software, hardware and HCI requirements. The design information was then
taken implemented into an application created to meet these requirements.
Before being released for general use and to validate and verify that
everything was as it should be testing was carried out in various forms namely
unit tests, functional tests, integration tests and performance tests. To
conclude, this project has been successful in delivering a prototype that can
use the information from the Trapeze LA200 system to monitor, chart and
report the movements of Wi-Fi tags around an area. However, it has also
shown that accuracy is not perfect and to achieve a high level may require
additional capital expenditure to purchase additional access points not
forgetting the setup time required to accurately verify the calibrations.
74
References
BROWN, B., MacCOLL, I., CHALMERS, M., GALANI, A., RANDELL, C.,
STEED, A. (2003). ‘Lessons from the Lighthouse: Collaboration in a shared
mixed reality system’. In: Cockton, G., Korhonen, P. 2003. CHI '03:
Proceedings of the conference on human factors in computing systems. New
York, NY: ACM Press, pp. 577-584. [Available Online at:
http://www.equator.ac.uk/var/uploads/Brown&MacColl2003.pdf]
75
KRUMM, J., CERMAK, G. & HORVITZ, E. (2003) ‘RightSPOT: A Novel Sense
of Location for a Smart Personal Object’, Paper presented at the UbiComp
2003. [Available Online at:
http://research.microsoft.com/~jckrumm/Publications%202003/rightSPOT
%20publish.pdf]
Myerson, J. (2006), RFID In the Supply Chain, CRC Press, ISBN 0849330181
RANDELL, C., MULLER, H. (2001). ‘Low Cost Indoor Positioning System’. In:
ABOWD, G. (Ed). 2001. UbiComp '01: Proceedings of the 3rd international
conference on Ubiquitous Computing. Springer-Verlag, pp. 42-48. [Available
Online at: http://www.cs.bris.ac.uk/Publications/Papers/1000573.pdf]
76
Appendix A – LA200 database schema
77
CONDITIONS ENDTIME FALSE FALSE TIMESTAMP 26,6
CONDITIONS ACKTIME FALSE FALSE TIMESTAMP 26,6
CONDITIONS ALERTID FALSE FALSE VARCHAR 256
CONDITIONS VARIANTID FALSE FALSE VARCHAR 256
CONDITIONS CONFIGID FALSE FALSE VARCHAR 256
CONDITIONS ALERTNAME FALSE FALSE VARCHAR 256
CONDITIONS PRIORITY FALSE FALSE VARCHAR 256
CONDITIONS HIGHLOW FALSE TRUE SMALLINT 5
CONDITIONS CONDITIONCODE FALSE TRUE INTEGER 10
CONDITIONS PRIMARIES FALSE FALSE LONGVARCHAR 32700
CONDITIONS SECONDARIES FALSE FALSE LONGVARCHAR 32700
CONDITIONS TERTIARIES FALSE FALSE LONGVARCHAR 32700
CONDITIONS KEYWORDS FALSE FALSE LONGVARCHAR 32700
DATATAPS DATATAPID TRUE TRUE VARCHAR 256
DATATAPS NAME FALSE FALSE VARCHAR 256
DATATAPS OBSERVERNAME FALSE FALSE VARCHAR 256
DATATAPS DESCRIPTION FALSE FALSE VARCHAR 256
DATATAPS PROFILEID FALSE FALSE VARCHAR 256
DATATAPS ADDRESS FALSE FALSE VARCHAR 256
DATATAPS ENABLED FALSE TRUE SMALLINT 5
DATATAPS DEFAULTUSED FALSE TRUE SMALLINT 5
DATATAPS PASSWORD FALSE FALSE VARCHAR 256
DATATAPS SERVICE FALSE FALSE VARCHAR 256
DATATAPS CHANNELS FALSE FALSE VARCHAR 256
DEVICES DEVICE_ID TRUE TRUE VARCHAR 256
DEVICES LOCATION FALSE FALSE VARCHAR 256
DEVICES TYPE FALSE TRUE INTEGER 10
DEVICES ACTIVITY FALSE FALSE INTEGER 10
DEVICES DEVICEADDRESS FALSE TRUE VARCHAR 250
DEVICES INETADDRESS FALSE FALSE VARCHAR 256
DEVICES LASTSEEN FALSE TRUE BIGINT 19
DEVICES DEVICELABEL FALSE FALSE VARCHAR 256
DEVICES CHANNEL FALSE TRUE INTEGER 10
DEVICES SSID FALSE FALSE VARCHAR 256
DEVICES ENCRYPTION FALSE FALSE VARCHAR 256
DEVICES RXADDRESS FALSE FALSE VARCHAR 256
DEVICES DEVICEUSER FALSE FALSE VARCHAR 256
DEVICES ACCESSSTATUS FALSE FALSE VARCHAR 256
DEVICES SPOOFSTATUS FALSE FALSE VARCHAR 256
DEVICES LASTMOVE FALSE TRUE BIGINT 19
DEVICES SIGNATURE FALSE FALSE VARCHAR 256
GEOMETRY UNIQUEID TRUE TRUE BIGINT 19
GEOMETRY NAME FALSE FALSE VARCHAR 255
GEOMETRY SCALE FALSE TRUE DOUBLE 52
GEOMETRY BACKGROUND FALSE FALSE VARCHAR 255
GEOMETRY ORIGIN_UNIQUEID FALSE FALSE BIGINT 19
78
GEOMETRY_AREAS GEOMETRY_UNIQUEID TRUE TRUE BIGINT 19
GEOMETRY_AREAS AREAS_UNIQUEID FALSE TRUE BIGINT 19
GEOMETRY_AREAS AREA_IDX TRUE TRUE INTEGER 10
GEOMETRY_POSITIONS GEOMETRY_UNIQUEID TRUE TRUE BIGINT 19
GEOMETRY_POSITIONS POSITIONS_UNIQUEID FALSE TRUE BIGINT 19
GEOMETRY_POSITIONS POS_IDX TRUE TRUE INTEGER 10
GROUPS GROUP_ID TRUE TRUE VARCHAR 256
GROUPS NAME FALSE FALSE VARCHAR 256
GROUPS TYPE FALSE FALSE VARCHAR 256
HIBERNATE_UNIQUE_KEY NEXT_HI FALSE FALSE INTEGER 10
HISTORYCONDITIONMAPPING HISTORYID FALSE TRUE VARCHAR 256
HISTORYCONDITIONMAPPING CONDITIONID FALSE TRUE VARCHAR 256
JMS_MESSAGES MESSAGEID TRUE TRUE INTEGER 10
JMS_MESSAGES DESTINATION TRUE TRUE VARCHAR 255
JMS_MESSAGES TXID FALSE FALSE INTEGER 10
JMS_MESSAGES TXOP FALSE FALSE CHAR 1
JMS_MESSAGES MESSAGEBLOB FALSE FALSE BLOB 1073741824
JMS_ROLES ROLEID TRUE TRUE VARCHAR 32
JMS_ROLES USERID TRUE TRUE VARCHAR 32
JMS_SUBSCRIPTIONS CLIENTID TRUE TRUE VARCHAR 128
JMS_SUBSCRIPTIONS SUBNAME TRUE TRUE VARCHAR 128
JMS_SUBSCRIPTIONS TOPIC FALSE TRUE VARCHAR 255
JMS_SUBSCRIPTIONS SELECTOR FALSE FALSE VARCHAR 255
JMS_TRANSACTIONS TXID TRUE TRUE INTEGER 10
JMS_USERS USERID TRUE TRUE VARCHAR 32
JMS_USERS PASSWD FALSE TRUE VARCHAR 32
JMS_USERS CLIENTID FALSE FALSE VARCHAR 128
LAYOUTS LAYOUTID TRUE TRUE VARCHAR 256
LAYOUTS PROFILEID FALSE FALSE VARCHAR 256
LAYOUTS USERID FALSE FALSE VARCHAR 256
LAYOUTS GROUPID FALSE FALSE VARCHAR 256
LAYOUTS PERMISSIONS FALSE TRUE INTEGER 10
LAYOUTS LAYOUTNAME FALSE FALSE VARCHAR 256
LAYOUTS LAYOUTDATA FALSE FALSE BLOB 2147483647
LICENSE ID TRUE TRUE BIGINT 19
LICENSE LICENSEKEY FALSE FALSE VARCHAR 255
LICENSE ACTIVATIONDATE FALSE FALSE DATE 10
LINKAGES LINKID TRUE TRUE VARCHAR 256
LINKAGES SOURCESTRING FALSE FALSE VARCHAR 256
LINKAGES LINKVALUE FALSE TRUE DOUBLE 52
LINKAGES LINKTYPE FALSE FALSE VARCHAR 256
LOCALES LOCATIONID TRUE TRUE VARCHAR 256
LOCALES LOCATIONNAME FALSE FALSE VARCHAR 256
LOCALES LOCATIONDESCRIPTION FALSE FALSE VARCHAR 256
LOCALES PROFILEID FALSE FALSE VARCHAR 256
LOCALES ZONEID FALSE FALSE VARCHAR 256
79
LOGACTIVITIES UUID TRUE TRUE VARCHAR 256
LOGACTIVITIES HISTORYID FALSE FALSE VARCHAR 256
LOGACTIVITIES STARTTIME FALSE FALSE TIMESTAMP 26,6
LOGACTIVITIES ENDTIME FALSE FALSE TIMESTAMP 26,6
LOGACTIVITIES ACTIVITY FALSE FALSE VARCHAR 256
LOGASSOCIATIONS UUID TRUE TRUE VARCHAR 256
LOGASSOCIATIONS STARTTIME FALSE FALSE TIMESTAMP 26,6
LOGASSOCIATIONS ENDTIME FALSE FALSE TIMESTAMP 26,6
LOGASSOCIATIONS APHISTORYID FALSE FALSE VARCHAR 256
LOGASSOCIATIONS CLIENTHISTORYID FALSE FALSE VARCHAR 256
LOGHISTORIES UUID TRUE TRUE VARCHAR 256
LOGHISTORIES ENTITYID FALSE FALSE VARCHAR 256
LOGHISTORIES TYPE FALSE FALSE VARCHAR 256
LOGHISTORIES MACADDRESS FALSE FALSE VARCHAR 256
LOGIPADDRESSES UUID TRUE TRUE VARCHAR 256
LOGIPADDRESSES STARTTIME FALSE FALSE TIMESTAMP 26,6
LOGIPADDRESSES ENDTIME FALSE FALSE TIMESTAMP 26,6
LOGIPADDRESSES IPADDRESS FALSE FALSE VARCHAR 256
LOGIPADDRESSES HISTORYID FALSE FALSE VARCHAR 256
LOGLABELS UUID TRUE TRUE VARCHAR 256
LOGLABELS STARTTIME FALSE FALSE TIMESTAMP 26,6
LOGLABELS ENDTIME FALSE FALSE TIMESTAMP 26,6
LOGLABELS LABEL FALSE FALSE VARCHAR 256
LOGLABELS HISTORYID FALSE FALSE VARCHAR 256
LOGLOCATIONS UUID TRUE TRUE VARCHAR 256
LOGLOCATIONS HISTORYID FALSE FALSE VARCHAR 256
LOGLOCATIONS STARTTIME FALSE FALSE TIMESTAMP 26,6
LOGLOCATIONS ENDTIME FALSE FALSE TIMESTAMP 26,6
LOGLOCATIONS LOCATIONID FALSE FALSE VARCHAR 256
LOGLOCATIONS LOCATIONNAME FALSE FALSE VARCHAR 256
LOGPOPULATIONS UUID TRUE TRUE VARCHAR 256
LOGPOPULATIONS HISTORYID FALSE FALSE VARCHAR 256
LOGPOPULATIONS STARTTIME FALSE FALSE TIMESTAMP 26,6
LOGPOPULATIONS ENDTIME FALSE FALSE TIMESTAMP 26,6
LOGPOPULATIONS ACTIVITY FALSE TRUE INTEGER 10
LOGPOPULATIONS ACTIVE_APS FALSE TRUE INTEGER 10
LOGPOPULATIONS ACTIVE_STATIONS FALSE TRUE INTEGER 10
LOGPOPULATIONS ACTIVE_ADHOCS FALSE TRUE INTEGER 10
LOGSSIDS UUID TRUE TRUE VARCHAR 256
LOGSSIDS STARTTIME FALSE FALSE TIMESTAMP 26,6
LOGSSIDS ENDTIME FALSE FALSE TIMESTAMP 26,6
LOGSSIDS SSID FALSE FALSE VARCHAR 256
LOGSSIDS HISTORYID FALSE FALSE VARCHAR 256
LOGTYPES UUID TRUE TRUE VARCHAR 256
LOGTYPES STARTTIME FALSE FALSE TIMESTAMP 26,6
LOGTYPES ENDTIME FALSE FALSE TIMESTAMP 26,6
80
LOGTYPES DEVICETYPE FALSE FALSE VARCHAR 256
LOGTYPES HISTORYID FALSE FALSE VARCHAR 256
POSITIONS UNIQUEID TRUE TRUE BIGINT 19
POSITIONS ELEMENTNAME FALSE FALSE VARCHAR 255
POSITIONS ELEMENTTYPE FALSE FALSE INTEGER 10
POSITIONS X FALSE TRUE DOUBLE 52
POSITIONS Y FALSE TRUE DOUBLE 52
PRINCIPAL_GROUP_MAPPING PRINCIPAL_ID_FK FALSE TRUE VARCHAR 256
PRINCIPAL_GROUP_MAPPING GROUP_ID_FK FALSE TRUE VARCHAR 256
PRINCIPALS PRINCIPAL_ID TRUE TRUE VARCHAR 256
PRINCIPALS NAME FALSE FALSE VARCHAR 256
PRINCIPALS TYPE FALSE FALSE VARCHAR 256
PROFILES PROFILEID TRUE TRUE VARCHAR 256
PROFILES PROFILENAME FALSE FALSE VARCHAR 256
PROFILES PROFILEDESCRIPTION FALSE FALSE VARCHAR 256
PROFILES PROFILEACTIVE FALSE TRUE SMALLINT 5
PROPERTIES ENTITY FALSE TRUE VARCHAR 256
PROPERTIES RELATEDENTITY FALSE TRUE VARCHAR 256
PROPERTYSET PROPERTY_SET_ID TRUE TRUE VARCHAR 256
PROPERTYSET ENTITYID FALSE FALSE VARCHAR 256
PROPERTYSET TYPE FALSE FALSE VARCHAR 256
PROPERTYSET PROPERTYKEY FALSE FALSE VARCHAR 256
PROPERTYSET DATASTRING FALSE FALSE VARCHAR 256
PROPERTYSET DATABOOL FALSE FALSE SMALLINT 5
RELATIONS RELATEDENTITY FALSE TRUE VARCHAR 256
RELATIONS ENTITY FALSE TRUE VARCHAR 256
SAMPLEDATA SOURCESTRING FALSE FALSE VARCHAR 256
SAMPLEDATA SAMPLEVALUE FALSE TRUE DOUBLE 52
SAMPLEDATA SAMPLEDATAID TRUE TRUE VARCHAR 256
SAMPLEDATA SAMPLEID FALSE FALSE VARCHAR 256
SAMPLES SAMPLENUMBER FALSE TRUE INTEGER 10
SAMPLES SAMPLEID TRUE TRUE VARCHAR 256
SAMPLES SIGNATUREID FALSE FALSE VARCHAR 256
SCHEDULETASKS UUID TRUE TRUE VARCHAR 256
SCHEDULETASKS IDENTIFIER FALSE FALSE VARCHAR 256
SCHEDULETASKS PROPERTIES FALSE FALSE BLOB 2147483647
SCHEDULETASKS CALLBACKVALUE FALSE FALSE VARCHAR 256
SCHEDULETASKS TIMESPEC FALSE TRUE BIGINT 19
SIGNATURES SIGNATUREID TRUE TRUE VARCHAR 256
SIGNATURES SIGNATURENAME FALSE FALSE VARCHAR 256
SIGNATURES SIGNATUREDESCRIPTION FALSE FALSE VARCHAR 256
SIGNATURES SIGNATURETYPE FALSE FALSE VARCHAR 256
SIGNATURES PROFILEID FALSE FALSE VARCHAR 256
SIGTRANSLATION LOCATION FALSE TRUE VARCHAR 256
SIGTRANSLATION SIGNATURE FALSE TRUE VARCHAR 256
SNIPERS SNIPERID TRUE TRUE VARCHAR 256
81
SNIPERS NAME FALSE FALSE VARCHAR 256
SNIPERS DESCRIPTION FALSE FALSE VARCHAR 256
SNIPERS PROFILEID FALSE FALSE VARCHAR 256
SNIPERS ADDRESS FALSE FALSE VARCHAR 256
SNIPERS ENABLED FALSE TRUE SMALLINT 5
SNIPERS DEFAULTUSED FALSE TRUE SMALLINT 5
SNIPERS PASSWORD FALSE FALSE VARCHAR 256
SNIPERS SERVICE FALSE FALSE VARCHAR 256
TIMERS TIMERID TRUE TRUE VARCHAR 80
TIMERS TARGETID TRUE TRUE VARCHAR 250
TIMERS INITIALDATE FALSE TRUE TIMESTAMP 26,6
TIMERS TIMERINTERVAL FALSE FALSE BIGINT 19
TIMERS INSTANCEPK FALSE FALSE BLOB 2147483647
TIMERS INFO FALSE FALSE BLOB 2147483647
VERSION61 UNIQUEID TRUE TRUE BIGINT 19
VERSION61 INFO TRUE TRUE VARCHAR 256
VIEWS VIEWID TRUE TRUE VARCHAR 256
VIEWS PROFILEID FALSE FALSE VARCHAR 256
VIEWS USERID FALSE FALSE VARCHAR 256
VIEWS GROUPID FALSE FALSE VARCHAR 256
VIEWS PERMISSIONS FALSE TRUE INTEGER 10
VIEWS VIEWNAME FALSE FALSE VARCHAR 256
VIEWS LAYOUTNAME FALSE FALSE VARCHAR 256
VIEWS VIEWDATA FALSE FALSE BLOB 2147483647
WORKSPACE_APS AP_ID TRUE TRUE VARCHAR 256
WORKSPACE_APS DEVICEADDRESS FALSE FALSE VARCHAR 256
WORKSPACE_APS INETADDRESS FALSE FALSE VARCHAR 256
WORKSPACE_APS APNAME FALSE FALSE VARCHAR 256
WORKSPACE_APS APMODEL FALSE FALSE VARCHAR 256
WORKSPACE_APS APTYPE FALSE FALSE VARCHAR 256
WORKSPACE_APS APCOMMUNITY FALSE FALSE VARCHAR 256
WORKSPACE_APS POLICY_ID FALSE FALSE VARCHAR 256
WORKSPACE_POLICIES POLICY_ID TRUE TRUE VARCHAR 256
WORKSPACE_POLICIES POLICYNAME FALSE FALSE VARCHAR 256
WORKSPACE_POLICIES SECRET FALSE FALSE VARCHAR 256
ZONES ZONEID TRUE TRUE VARCHAR 256
ZONES ZONENAME FALSE FALSE VARCHAR 256
ZONES DESCRIPTION FALSE FALSE VARCHAR 256
ZONES PROFILEID FALSE FALSE VARCHAR 256
82