Equipment Comparison Chart
Open Winbox application to access Mikrotik or you may use a web browser to connect to your Mikrotik. Connect to Mikrotik using it’s IP address or MAC address if you are using Winbox.
To start setting up the hotspot network, click on IP-Hotspot and click on Hotspot Setup under Servers tab. Go through the Hotspot Wizard by selecting the desired interface to run the hotspot network.
Create a gateway for your hotspot network and masquerade the network.
Create a DHCP pool range for your hotspot network.
Select none for SSL Certificate.
Leave the SMTP server address as default 0.0.0.0.
Add Google DNS Servers 188.8.131.52 and 184.108.40.206.
Leave the DNS name empty.
Skip the local hotspot user by clicking next.
Now you have successfully created a hotspot network on your Mikrotik. The next step is to point your hotspot network to RADIUS server which is Kiwire. To do that, first, click on the Server Profiles tab and select the hotspot server profile that you just created. Go to the Login tab and tick only HTTP PAP and HTTPS.
Next, go to RADIUS tab and tick on use RADIUS.
Next, go to User Profiles tab and click on the default profile. Edit the Shared Users box by putting 1000.
Go to Walled Garden, add new Walled Garden at the Dst. Host section, select your hotspot server and allow it on the Action. This setting is for allowing the social login and pre-login campaign videos or URLs.
Type Walled Garden List
|Synchroweb social gate||socialgate.synchroweb.com|
Next, go to Walled Garden IP List and add Kiwire IP address in the Src. Address and Dst. Address and select your hotspot server.
Click on the RADIUS menu and add new RADIUS. Put Kiwire IP address and create a secret. Tick on hotspot for Service.
On the Incoming tab in the RADIUS menu, tick on Accept and use port 3799.
Next, go to System-Identity and set an identity for your Mikrotik. This will be the NAS ID of your Mikrotik.
Open your web browser and type in http://kiwire-ip/admin to access your Kiwire admin panel.
Go to Device-NAS and click add NAS to add your Mikrotik.
Next, we go to Device-Zone to assign which zone we want to assign splash page. We can assign zone based on NAS ID, VLAN ID, IP address, or SSID. Create a new zone by clicking Create Zone. Put a name to it, Link To User and Limit Connected User can be empty. Then enable the Status.
After that, edit the zone by clicking Add.
Finally, you have completed the configuration of both Kiwire and Mikrotik. Next is you need to design a landing page, create user profile and create user and assign the landing page to the zone desired. You may refer to http://doc.synchroweb.com/kiwire-2-0-directory/ for setting up landing page, user profile, users, and other details of Kiwire.
Kiwire can also support dialup pppoe services for Mikrotik as controller, with Mikrotik as PPPOE server is an popular option for fixed fiber or wifi always on internet services for telco or internet service provider .
One of the requirement is to provide bandwidth or rate limit to the subscriber , the default profile by Kiwire is for WISPr ( Wireless ISP ) which use Wispr attribute , however you can use policy-> radius attribute to add PPPOE rate limit attribute to the profile. the step are
The schedule script will enable automatic download of wallgarden list and firewall list into the mikrotik nas on an interval.
version 2.0 [ 2017-02-01 ]
The setting module let your configure and customise the omaya platform to your organisation needs.
The web user module let you add additional administrator or operate to omaya platform. When you access the module, it will list existing administrator or operator exist in the system.
The column data are:
username – the username of the administrator or operator
Email – the email for the user
Company – the company account associated with the users
Created – the date the user is created
Last seen – the last the user login to omaya platform
Role – the role assign to the user
Act – delete or edit the users.
To add new administrator or operator click on the + Add New User button.
Fill in the input box with the required data:
Username – the username given to the new user
Email – the email address for the new users
Password – the password for the new users
Company – the company id associated with the new user
Role – the role assign to the new user , for more information on role refer to role module.
All administrator or operator added to system are govern by the role and privileges assigned. You can fine-tune the role and privileges assigned to per user basis.
To add new role and privileges , please create a role first by click on the + Add New Role fill in the role name and its descriptions click Save to save the role , the newly created role is an empty container which does not have any privileges continue by click on the privileges tab and click on + Add new Privileges button. Select the privileges you allowed the role to have and click Save to save the privileges.
The Venue module let you manage the entire venue you have with sensor installed within your company.
Click on the + Add venue button to add venue. Fill in the venue name with the name of your venue, select the venue type
• Mall – if this venue is part of a mall
• Outlet – if this is outlet within a mall or shop
• Zone – if this venue is a zone, which consist multi sensor.
4.4 Venue Device
Venue devices are list of sensor that is compatible with omaya platform; this can be wireless access point or Wi-Fi sensor. The venue device listing will list the entire sensor associated with your company account. You have option to edit or delete the sensor associated with your company account.
Note: only superadmin can add and assign new sensor to company id. Refer to omaya 2: platform owner guide.
the listing will show the data as
Company – the company id associated with the sensor
Venue – the venue the sensor is installed in
Alias – the alias or name for the sensor
DevTag – the sensor serial no or tag no
Type – the sensor type it could be access point or cloud beacon.
Rssi min – the min RSSI set
Rssi max – the max RSSI set
Dwell – the dwell time setting to constitute a user as engaged
Map Axis – the placement of sensor on the map uploaded
Map – the map id of the map associated with the venue.
The edit venue device screen let you re-assign the sensor to new venue or change the sensor alias, tag or type.
the signal strength slider is use to manipulate dbm of the device , example if -85 dbm to -25 dbm ( lower dbm is nearer to sensor ) , we ignore any device that is more than -85 dbm and user with dbm -25 and bellow are classified as visit type users.
The dwell slider is use to determine how long a user stayed in the venue constitute as engaged users. In a fast food industry we may set the dwell to be 3 minute as the user who stay more than 3 minutes and are nearby to sensor are already a client however in a museum venue we may set the dwell time to be higher as a longer dwell time constitute user interacting with the exhibit.
The venue map module let you upload, manage and sensor placement of sensor onto the map.
The column listing of the venue map
Venue name – the venue name assign to the map
Company – the company id assign to the map
Type – the type of venue
Level – the level for the map within venue
Address – the address of the venue.
Click on the icon to upload your map you may drag and drop the map into the upload box or click choose file button to select the map, please put the scale of their the map scale example 2m:1px this is for rendering of the heat map as accurate as possible .Click save to save the map.
Click on the icon for placement of sensor into the map. Drag and drop the sensor and drop them on the approximate location within the map. In addition, click save button to save.
Omaya have a built in filtering engine that can automatically filter other sensor or Wi-Fi equipment and distinguish between users and permanent devices such as Wi-Fi printer or Wi-Fi CCTV and others wireless enabled equipment. You may enable auto filtering per venue or select “all venue”. Automatic filtering will compute the statistic without data of permanent device to provide an accurate analytics reports that is consist of actual user only.
The API module let you integrate your omaya platform data with other third party software platform, click enable to enable the API and key in your secure API key or click generate to let omaya generate the API key for you. The API key & company id is required by third party software to access the omaya API to collect data from omaya platform. Refer to omaya API document on using the API.
The operation module provide you and operations function of omaya platform
The view devices status provide you the health status of the sensor within your omaya platform. It will show health status as well as the last reported time by the devices.
To view administrator and operator activity on omaya platform use the view web logs function to view the activity perform by the users. You may select date range or by username.
The track user location will locate users by the mac address of the mobile devices the user carry. mac address is an unique serial no that is associated with each mobile device.
The analytics module is your primary reporting screen for your venues.
Benchmark provide a key comparison among all your venues. It will display the average record of total pass by, total visit, total engaged and calculate the conversation rate from total visit to engaged.
The default date range is the last 7 days to select a different date range, use the date range selector to select the date, the selected will be highlighted.
you can further view the average data to get a pulse of the venue crowd data by clicking the weekly view
The weekly heat map view will use colour-coded display and show the highest users crowd density by red and blue for the lowest.
Unique visit is your primary report of the user’s behaviour within your venues, it will do comparison between pass by, visit and engaged users.
To view specific venue, use the drop down venue list as well the date range to view the analytics data.
Click on the bar view to view the graph in bar chat format.
Click on the detail view if you wish to view further detail on the data as daily breakdown view.
To export the data click on the copy / csv / excel and pdf menu.
You may view the unique visit analytics for the day by clicking on view on the selected days, the graph will provide statistic by hourly basis.
You can change the graph to bar chart format by click on the bar icon.
Click on the data view to view the data in table format.
From the daily, you can click on the weekly view icon to see the user’s crowd heat map statistic on from the date selected.
The entry & exit analytics report provide churn rate on users entry, exit and bounce rate for the venue. You can select the venue, date range and reporting interval hourly or daily reports.
For the hourly report, the table report bellow the graph will show entry, exit, bounce rate and the percentage of entry vs exit in hourly view.
For daily report, it will show the data group by dates.
Dwell time analytics provide you analysis of your venue engaged user dwell time; you may select the venue you wish to view interval (daily, weekly or monthly) view and date range using the date range selector.
Click on the detail icon will show the dwell time data of user in table format group by key index such as less than 15 minutes, 15 to 30 minutes, 30 min to 1 hour, 1 hour to 2 hour and more than 8 hours. We opinion the more engaged the users the more likely the user will interact with your venue.
From the table report, you can further zoom into the daily view in a pie chart grouping for ease to view.
Click on the funnel graph to view the funnel of users dwell time in your venue.
2.5 Venue Map
The venue map provide you overlay of crowd density via heat map over your venue floor plan. Depend on the number of sensor deployed you can have a zonal heat map or presence heat map. The presence heat map provide heat map of user density nearby the single sensor while zonal edition uses triangulation between all the sensor and display the density between the sensors., click on the green view icon to view the map.
The map heat map page includes a “playback” function – by pressing the show button, it is possible to see how the client density changes throughout the course of the day. Dates can also be toggled to see client density on a specific day in the past.
The heat maps are calculating using two metrics – (a) the number of devices were detected during the time, and (b) how long those devices dwelled in the area. The colours represent the areas on the map where there is the most “presence.” The intensity is based both on how many devices were detected during the time and on how long those devices dwelled in the area. Areas may be dark red either because there were many devices detected, or because there were a few devices that all stayed in the area for the entire hour.
The loyalty & distributions analytics provide distributions statistic on new user’s vs return users to your venue. You may select the venue and date range for reports. On the main screen, there is three primary tab.
The first tab is new users versus repeat users analysis, which inform you how many new user is detected and how many return users are detected at venue
The second tab is repeat count report, which inform the frequency of the users group by 1, 2, 3 to 5 or more than five visit to the venue.
The third tab will show the return users visit frequency group by 1 ~ 3 days, 3 ~ 1 week, 1 ~ 2 week and more than 3 weeks.
The cross visit report will provide you trend of your users return to and movement across the entire venue you have. You can select the date range and view the user cross visit report.
Click on detail view-to-view movement of user count at each venue and dates.
You may view the hourly report of user movement count from the table listing.
Omaya is a web-based platform, to access omaya platform open your internet browser and go to http://omaya.xyz.com/ to login. If this is onsite edition use the ip assign to omaya onsite.
Default Access for Standalone Omaya Platform
Dashboard provide an overview snapshot of crowd analytics of your venue.
Your dashboard is the first thing you will see when you login to the omaya Portal. It gives you an overview of activity and reports on a weekly basis. The dashboard gives you the following information:
Total pass by – Total no of unique users detect walked by your venue
Total return user – Total users detected return to venue
Total visit by – Total users who is detected near the sensor
New User – Total new users to venue
Average dwell time – Average dwell time for all engaged users.
Pass by vs Visit vs Engaged Graph – a graph of the data overlaps of pass by, visit and engaged statistic.
To reset password, click on the avatar on the top right, click on reset password to access the change password screen
Input your old password and your desire new password twice into the new password, confirm password box, and click Submit to change your password.
This User Guide describes how to configure and utilise omaya 2.0 location based system. Those responsible for managing Omaya System intend this guide for use. Consequently, it assumes a basic working knowledge of local area networking, wireless networking and wireless devices.
Omaya is a location based platform helps you understand how people move around your venue. The paths they take, choke points, entry or exit points and even queue lengths are not only possible but also made easy with it.
We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.
|Bold||Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.|
|Italics||Italic typeface indicates emphasis.|
Omaya uses a common icon to represent a function
|Edit an entry|
|Delete an entry|
|View an entry|
|weekly view of entry|
Omaya administration platform consist of few pane
Navigation pane for navigation menu to access a operation or module within Omaya administration platform.
Main screen: the main display of module and function
if you have large data to compute, a waiting screen will be displayed, please wait until the compute is complete to review your data
There are a few key terminology used by omaya system, please get accustomed and familiar to the term for ease of operating omaya. The condition for the users associated with the correct term can be set by venue device screen.
Users – mobile device with wifi chip detected , each device is assumed to be one user, while the trend of single user with multi device is in trend its only minimal users having more than 1 mobile devices
Pass by – Users detected walk by at venue
Visit – User who is detected nearer to sensor
Engaged – total no of user that dwell at venue more than no of minutes thus is converted from pass by to engaged
Daily loyalty users – users who is detected by system 5 days out of 1 week.
Weekly loyalty users – users who is seen more than 4 days a month
Bounce rate – users who spend less than 5 minutes
Churn – the relative number of user that appear and disappear during a time window
Dwell Time – determined the amount of queuing or the average time spend in zone or outlet
Crowding factor – determined the potential bottlenecks or where extra resources are needed
Dominant direction – the most typical direction of travel through an area by users
New visitor – user who is detected 1st time at venue
Repeat visitor – users who is detected within venue 2nd time the next day onward
Device state – all mobile device emit wifi signal , the frequency of signal emitted are based on the state of the device
|Device state||Probe/emit request interval|
|Asleep ( screen off )||~once per minute|
|Standy (screen on )||10 ~ 15 times per minute|
|Associated with SSID||varies , but higher frequency.|