People counter: Difference between revisions
m nothing |
|||
Line 1: | Line 1: | ||
= '''NIU Bus Ticket System''' = |
|||
{{Multiple issues| |
|||
{{refimprove|date=April 2015}} |
|||
{{original research|date=December 2015}} |
|||
{{weasel|date=December 2015}} |
|||
{{copy edit|date=December 2015}} |
|||
}} |
|||
A '''people counter''' is a device used to measure the number and direction of people traversing a certain passage or entrance, often used at buildings, so that the total number of visitors can be recorded. |
|||
== |
== Concept: == |
||
NIU Bus Ticket system is an application where a student can reserve tickets for his/her travel to different places. A charge will be applied to Student account after successful reservation. Staff approves any bus schedule. He also updates the schedule on weekly basis. |
|||
== Description: == |
|||
===Retail stores=== |
|||
Northern Illinois University decided to arrange bus facility to students and have an application for selling bus tickets. The University observed that many students are struggling to find an option to travel to places like Chicago, Elgin and Rockford etc. The local cab drivers are making good profits taking advantage of the situation. Previously, the problem for University is, it doesn’t have statistics like how many buses required? How many students will be travelling? Etc. With this application, it should be able to have all the statistics and make arrangements accordingly. It allows students to book tickets using Huskie bucks. Looking at the count of students for a particular trip, the manager of the system will have an option to accept or cancel the trip. The system will have a display for all the trips available for a particular week. Students will have an option check the chart. The students can login with their Z-id and request for a particular ride. They receive a confirmation mail once the manager approves the trip. The University decided to have the database cleaned up every week in order to save memory space. Once a student books a ticket, the amount will be deducted from the huskie bucks available. A student will be able to book any number of tickets if there is huskie bucks balance in his account. |
|||
If this system proves successful, Northern Illinois University has the idea to extend it to Universities across United States which are suffering with similar problem. |
|||
'''Conversion Rate''' - The use of people counting systems in the retail environment is used to calculate the [[Conversion (marketing)|conversion]] rate, i.e., the percentage of a store's visitors that makes purchases. This is the key performance indicator of a store's performance and provides greater information than traditional methods, which only take into account sales data. Together, traffic counts and conversion can reveal sales information such as how a store arrived at sales, e.g., if year-over-year sales are down, did fewer people visit the store, or did fewer people buy? |
|||
==Link:== |
|||
'''Marketing Effectiveness''' - Shopping mall marketing professionals rely on visitor statistics to measure their marketing. Often, shopping mall owners measure marketing effectiveness with sales, and also use visitor statistics to scientifically measure marketing effectiveness. Marketing metrics such as CPM (Cost Per Thousand) and SSF (Shoppers per Square Foot) are performance indicators that shopping mall owners monitor to determine rent according to the total number of visitors to the mall or according to the number of visitors to each individual store in the mall. |
|||
http://omisapps.niu.edu/z1747788/BUS(1) |
|||
== Usecase Diagram: == |
|||
'''Staff Planning''' - Accurate visitor counting is also useful in the process of optimizing staff shifts; staff requirements are often directly related to density of visitor traffic and services such as cleaning and maintenance are typically undertaken when traffic is at its lowest. |
|||
http://omisapps.niu.edu/z1747788/Projectuml |
|||
== Functional and Non Functional Requirements: == |
|||
===Shopping Malls=== |
|||
Functional Requirements: |
|||
'''Measure Busy Areas''' - Shopping Centres use people counters to measure the number visitors coming into the Centre. It also assists in measuring the areas of of 'hot spots', where it is often used to justify rental rates. |
|||
1. The NIU Bus Ticket System should allow the student to book any number of tickets using huskie bucks. |
|||
===Museums and libraries=== |
|||
'''Justify fundings''' - Many [[non-profit organisation]]s use visitor counts as evidence when making applications for finance. In cases where tickets are not sold, such as in museums and libraries, counting is either automated, or staff keep a log of how many clients use different services. |
|||
2. The NIU Bus Ticket System should allow the manager to cancel a trip or to approve a trip depending on conditions. 3. The NIU Bus Ticket System should display all the bus routes available along with timings and cost. |
|||
===Stadiums and Concert Halls=== |
|||
'''Crowd management''' - There are often large traffic flows before and after an event. People counters are used to measure the traffic flows of previous events, and the traffic patterns is used to improve traffic flow, particularly the access and egress of patrons. |
|||
4. The NIU Bus Ticket System should clean up the database every week and load fresh data for the upcoming week. |
|||
===Smart Office buildings=== |
|||
'''Optimise energy usage''' - Commercial buildings are using people counters to measure use of different parts of the building at different times. This information can then be used to intelligently optimise the energy usage in the building eg. air conditioning needs etc. |
|||
5. The NIU Bus Ticket System should allow only valid users to login with respective to their roles. |
|||
'''Fire Management''' - In the case of fire, people counters are one of the tools used to approximate the number of people inside the building. |
|||
6. The NIU Bus Ticket System should send a confirmation email to the student upon approval from manager. |
|||
==Business Metrics== |
|||
7. The NIU Bus Ticket System should allow Students to book ticket until specified time in the application and should not allow online tickets booking beyond specified time. |
|||
===Footfall=== |
|||
The number of people coming in and out of the venue. |
|||
8. The NIU Bus Ticket System should allow the students to request for resending confirmation email. |
|||
===Window conversion rate=== |
|||
Window Conversion Rate is the percentage of shoppers who came into the store over the people of people who walk passed the outside of the store. With [[#WiFi counting|WiFi counting]] shops can estimate the number of people walked passed the store. A more accurate method is video counting. While revenue and footfall are important, the number of people who walked pass the store often reflects the true potential of the store location. The Window Conversion Rate often depends on the attractiveness of the shop window design and the effectiveness of marketing campaigns.<ref>{{cite journal|last1=Dillon|first1=Chris|title=Sunder Sandher’s tech game changer|date=30 July 2015|url=http://www.betterretailing.com/sunder-sandhers-tech-game-changer/?utm_content=bufferdbcdd&utm_medium=social&utm_source=twitter_betterRetailing&utm_campaign=buffer}}</ref> |
|||
9. The NIU Bus Ticket System should allow students to check their available account balance. |
|||
===Visit duration=== |
|||
Visit duration is the amount of time visitors stay in the venue. [[#WiFi counting|WiFi counting]] has the ability to track the time when a person carrying a smartphone has entered the venue and when that same person has left the venue. |
|||
10. The NIU Bus Ticket System should not allow students to book tickets if there is no sufficient balance in the account. |
|||
===Returning customers=== |
|||
The number of people came into the store who had visited the store previously. WiFi counting has the ability to remember the Unique WiFi beacon signal ID emitted by shoppers, so if a shopper had previously visited the store, the counter would flag the person as a returning customer. |
|||
11. The NIU Bus Ticket System should display details like number of students requested for particular trip etc. in order to decide whether to approve or cancel a trip. |
|||
===Cross shopping=== |
|||
The number of shoppers who came into the store had previously visited other stores of the same chain. This is available for 3rd generation people counters that have [[#WiFi counting|WiFi counting]] functionalities. |
|||
12. The NIU Bus Ticket System should not charge the student incase if a trip is cancelled. |
|||
==Technologies== |
|||
Many different technologies are used in people counter devices, such as [[infrared]] beams, [[thermal imaging]], [[computer vision]] and [[#WiFi counting|WiFi counting]].<ref>{{citation |title=Manual of traffic engineering studies |page=17 |publisher= |
|||
Institute of Transportation Engineers |author=Paul C. Box, Joseph C. Oppenlander |year=1976 |url=http://books.google.com/books?id=jzhPAAAAMAAJ| accessdate=December 21, 2010}}</ref> |
|||
Non Functional Requirements: |
|||
===1st generation - Infrared beam counters=== |
|||
[[File:First Generation Infrared Beam Counter.jpg|thumb|The simplest form of counter in which a single, horizontal infrared beam across an entrance counts when a person or object passes and breaks its beam]] |
|||
The simplest form of counter is a single, horizontal [[infrared]] beam across an entrance which is typically linked to a small [[Liquid crystal display|LCD]] display unit at the side of the doorway. Such a beam counts a 'tick' when the beam is broken, therefore it is normal to divide the 'ticks' by two to get visitor numbers. Beam Counters usually require a receiver or a reflector mounted opposite the unit with a typical range from {{convert|2.5|m|0}} to {{convert|6|m}}. Despite its limitations, infrared counters are still widely used, primarily due to its low cost and simplicity of installation.{{cn|date=December 2015}} |
|||
1. The system should be available 24/7. |
|||
===2nd generation: Thermal counters=== |
|||
[[Thermography|Thermal imaging]] systems use array sensors which detect heat sources. These systems are typically implemented using embedded technology and are mounted overhead for high accuracy.[[File:Second Generation Thermal Counter.png|thumb|Thermal imaging systems use array sensors which detect heat sources from human body.]] Before the advance of computer technology which allows complex algorithms to perform video counting, thermal counters were the main choice for most businesses.{{cn|date=December 2015}} It can deliver reasonably high accuracy; however it does have its limitations, such as |
|||
i) thermal counters cannot mount on a high ceiling |
|||
ii) can only cover a narrow door entrance |
|||
2. The system shall be user friendly and consistent. |
|||
iii) difficult to verify the accuracy of the counter |
|||
3. The system shall provide attractive graphical interface for the user |
|||
iv) accuracy reduces in places there is slight variations in thermal conditions. |
|||
4. The system mainly focus on customer service |
|||
=== 3rd generation: Video + WiFi counting=== |
|||
5. The system provides secure access to authorized students. |
|||
With the advance of computer technology, complex image processing algorithm can now be used to perform counting using camera imaging. The third generation counters also includes Wifi Counting functionality which collects [[IEEE 802.11#Management Frames|WiFi probe request]] signals from shoppers' smartphones and add a number of important metrics for businesses, especially for the retail industry. Many business are now deploying people counters to help them to gain insights into their businesses <ref>https://www.abiresearch.com/press/people-counting-retail-market-undergoing-3-billion/</ref> |
|||
6. The system can recover in less than an hour time once a breakdown occurs. |
|||
====Video counting==== |
|||
[[Computer vision]] carries out its processes inside an [[Embedded system|embedded device]]. This reduces network bandwidth requirements as only the counting data has to be sent over the network. Robust and adaptive algorithms has been developed to provide excellent counting accuracy for both outdoor and indoor counting using computer vision. Multilayer Background Subtraction, based on colour and texture, is considered{{by whom|date=December 2015}} the most robust algorithm available for varying shadows and lighting conditions.<ref>http://www.idiap.ch/~odobez/human-detection/doc/YaoOdobezCVPR-VS2007.pdf</ref> With the advances in image processing, video count can achieve 90-95% in various lighting environments. The use of artificial intelligence and pattern recognition functions can further enhance its accuracy.{{cn|date=December 2015}} |
|||
7. The system shall automatically trigger the message to the concerned person when a down time occurs. |
|||
====WiFi counting==== |
|||
WiFi Counting uses WiFi receiver to pick up unique WiFi management frames emitted from the smartphones with a range of up to 100 metres. While not all people carry a smartphone, WiFi counting can produce statistically significant metrics due to the large sample size available. Apple iOS8 attempts to randomise MAC address, however it is making little impact on the effectiveness of WiFi counting.<ref>{{cite journal|last1=Technologies|first1=Zebra|title=Analysis of iOS 8 MAC Randomization on Loca tioning|date=2015|url=http://mpact.motorolasolutions.com/documents/iOS8-White-Paper.pdf}}</ref> |
|||
8. The system shall not allow the users to login in parallel at the same time from two different devices. |
|||
==References== |
|||
{{reflist}} |
|||
9. The system automatically connects itself to backup database in case when a data base crash occurs. |
|||
== Task Flow Diagram: == |
|||
http://omisapps.niu.edu/z1747788/projecttaskflow |
|||
== Main Features: == |
|||
# [http://omisapps.niu.edu/z1747788/scheduledisplay Bus Schedule] |
|||
# [http://omisapps.niu.edu/z1747788/Studentlogin Student Account] |
|||
# [http://omisapps.niu.edu/z1747788/StaffLogin Staff Account] |
|||
# [http://omisapps.niu.edu/z1747788/loginforAdmin Admin] |
|||
# [http://omisapps.niu.edu/z1747788/HelpDesk HelpDesk] |
|||
# [http://omisapps.niu.edu/z1747788/Frequent Frequently Asked Questions] |
|||
[[Category:Retailing]] |
[[Category:Retailing]] |
||
[[Category:Applications of computer vision]] |
[[Category:Applications of computer vision]] |
Revision as of 04:24, 6 December 2015
NIU Bus Ticket System
Concept:
NIU Bus Ticket system is an application where a student can reserve tickets for his/her travel to different places. A charge will be applied to Student account after successful reservation. Staff approves any bus schedule. He also updates the schedule on weekly basis.
Description:
Northern Illinois University decided to arrange bus facility to students and have an application for selling bus tickets. The University observed that many students are struggling to find an option to travel to places like Chicago, Elgin and Rockford etc. The local cab drivers are making good profits taking advantage of the situation. Previously, the problem for University is, it doesn’t have statistics like how many buses required? How many students will be travelling? Etc. With this application, it should be able to have all the statistics and make arrangements accordingly. It allows students to book tickets using Huskie bucks. Looking at the count of students for a particular trip, the manager of the system will have an option to accept or cancel the trip. The system will have a display for all the trips available for a particular week. Students will have an option check the chart. The students can login with their Z-id and request for a particular ride. They receive a confirmation mail once the manager approves the trip. The University decided to have the database cleaned up every week in order to save memory space. Once a student books a ticket, the amount will be deducted from the huskie bucks available. A student will be able to book any number of tickets if there is huskie bucks balance in his account.
If this system proves successful, Northern Illinois University has the idea to extend it to Universities across United States which are suffering with similar problem.
Link:
http://omisapps.niu.edu/z1747788/BUS(1)
Usecase Diagram:
http://omisapps.niu.edu/z1747788/Projectuml
Functional and Non Functional Requirements:
Functional Requirements:
1. The NIU Bus Ticket System should allow the student to book any number of tickets using huskie bucks.
2. The NIU Bus Ticket System should allow the manager to cancel a trip or to approve a trip depending on conditions. 3. The NIU Bus Ticket System should display all the bus routes available along with timings and cost.
4. The NIU Bus Ticket System should clean up the database every week and load fresh data for the upcoming week.
5. The NIU Bus Ticket System should allow only valid users to login with respective to their roles.
6. The NIU Bus Ticket System should send a confirmation email to the student upon approval from manager.
7. The NIU Bus Ticket System should allow Students to book ticket until specified time in the application and should not allow online tickets booking beyond specified time.
8. The NIU Bus Ticket System should allow the students to request for resending confirmation email.
9. The NIU Bus Ticket System should allow students to check their available account balance.
10. The NIU Bus Ticket System should not allow students to book tickets if there is no sufficient balance in the account.
11. The NIU Bus Ticket System should display details like number of students requested for particular trip etc. in order to decide whether to approve or cancel a trip.
12. The NIU Bus Ticket System should not charge the student incase if a trip is cancelled.
Non Functional Requirements:
1. The system should be available 24/7.
2. The system shall be user friendly and consistent.
3. The system shall provide attractive graphical interface for the user
4. The system mainly focus on customer service
5. The system provides secure access to authorized students.
6. The system can recover in less than an hour time once a breakdown occurs.
7. The system shall automatically trigger the message to the concerned person when a down time occurs.
8. The system shall not allow the users to login in parallel at the same time from two different devices.
9. The system automatically connects itself to backup database in case when a data base crash occurs.
Task Flow Diagram:
http://omisapps.niu.edu/z1747788/projecttaskflow