BusBudE Secure Travel Notification System

Apr 4, 2016 karen's Blog

Each year nationwide, there are reports of young children being dropped off of school buses in the wrong neighborhoods, unable to find their way home, and widespread reports in the media of children who are inadvertently left on the bus alone, posing a dangerous health risk. Most children live in households where families work, making it difficult for parents to be home to ensure the safe departure and arrival of their children. School notification systems contact parents during the first hours of school if their child has an unreported absence. Parents often are not aware if their children have returned home at the appropriate time until parents discover them missing hours later. The significant lapse in time can mean the difference between life and death. We put our creativity to the test to find a solution for this problem and created BusBudE Secure Travel Notification System.

We are the BusBudE Team, middle school and high school students from South Fayette Township School District near Pittsburgh, Pennsylvania. Each member has their own individual role and duty that helps our team stay organized and efficient. Our team includes: Co-project Managers: Joe Cavanaugh (grade: 11), Parv Shrivastava (grade: 8); Director of Computer Programming: Sam Cohen (grade: 11); Computer Programming Team: Anish Thangavelu (grade: 8), Vinay Pedapati (grade: 9); and Director of Business Marketing: Meghan Banerjee (grade: 12). We are part of the Emerging Innovation Leaders Program led by South Fayettes Director of Technology and Innovation, Aileen Owens. Our goal for BusBudE is to create a system that helps young students board the bus safely and allows parents peace of mind knowing their child is safe.

BusBudE is a product designed to help keep students safe while traveling to and from school on the school bus. Currently we are beta testing our product design. Our plan for the future is to create system for parents to register their young children for this service. Currently during beta testing our children receive a tag and small device attached to their backpack. As children enter the bus they scan their BusBudE tag to the mobile device on the bus. Immediately a text message is sent to the childs parents alerting them as to the date, time, and location that their child enters and leaves the bus. Parents know exactly where their children are when they enter and exit the bus. The BusBude application is designed to increase students safety and decrease parents fears and apprehension.

Technical Aspects

BusBudE uses a variety of technology within a cohesive system to keep children safe. Currently, the major components of BusBudE are near field communication (NFC) tags and a NFC-capable phone. We envision every bus outfitted with a phone that has NFC capabilities. Each participating student will receive a tag with customized information specific to each child and a custom designed tag holder. When the students enter the bus, they will scan their NFC tag to the NFC reader on the phone. Each phone is loaded with the BusBudE application which takes in the students information and puts it into a text that is sent to his or her parents. Here is an example of a text message: Sara is getting off bus 10 at 77 Massachusetts Ave, Cambridge, MA 02139.

We designed the prototype app for BusBudE using App Inventor. The app has a variety of features. The features include an accurate location and time based algorithm that detects whether the student is getting on or off the bus in the morning or the afternoon. With this algorithm, bus drivers do not have to manually select whether a student is getting on or off the bus as we did in an earlier iteration. Additionally, a notification sounds when the phone as read the tag to notify the student if his or her NFC tag has been scanned, a necessary feature that we added after our first beta test.

Featured below is a small snippet of the code that takes the name of the student and phone number from the NFC tag. It shows the BusBudE logo and a counter that increases by 1 every time the student has scanned their tag.

Design Stages

Once we designed the prototype version of the device and programmed the tags and the reader, we decided to beta test the application with a small group of students and their parents. We selected 5 students in 1st and 2nd grade from Bus 10 and ran the first beta test in March 2015.

The test concentrated on specific research questions to help develop the app to meet our user needs. We focused on analyzing the technical facets of the device and the students responses. The questions we focused on included:

• Would the technical aspects of the device work effectively and efficiently?
• Would there be any time restraints or issues scanning and receiving text messages?
• Would the device be easy for the students to use?

We held a parent-student training session with five students and their parents from 1st and 2nd grade to explain exactly what the product was intended to do. After distributing the individual badges, we ran through a practice run with the students to set expectations and explain how to scan their badges through role-playing. During the first beta test the device had the capacity to send a text to the students parent or guardian with a notification to let parents know that their childe had entered or exited the bus. We provided training for the bus driver and with her assistance located the best placement for the device on the bus.

On the morning and afternoon of the beta test, Aileen Owens rode the bus and monitored the students, observing and taking notes. After each alert was received, parents texted back to Aileens cell phone to let her know that they received the alert. She could then see in real time when students scanned and when the text was received. Parents reported that they received the texts and provided enthusiastic and positive feedback. The first beta test was a success.

Some of the lessons we learned from this beta test were:

• Scanning cards was easy for the students and was accomplished quickly without significant delay to the bus schedule.
• The reading device on the bus was positioned right for the elementary school children to scan without difficulty.
• The parents really loved the fact that they were receiving texts that alerted them to the fact that their children were safely riding the bus at the right times.

Potential areas for improvement were also discovered.

• There was no visual cue on the reading device that allowed students to see that their card had been scanned. As a result, some students scanned multiple times since they were not sure if their scan had been completed. As a result, some parents received multiple text messages.
• Another area for improvement was the handling of the reading device on the bus. The Bus driver suggested that the device be switched on at the start of the route and switched off at the end of the route, so that the driver did not have to touch the device at any time during the trip. If the driver were to touch the device anytime in between, it could potentially send repeat messages to parents, and cause confusion.
• The driver also recommended that the text message sends an alert to parents stating the bus number that the students entered. She explained that one of the biggest challenges for elementary students is learning to board the correct bus. There are times that students take a different bus route home from school when traveling to parents living in separate households.

The first beta test presented us with several areas for improvement which we incorporated into the second iteration of the product.

The responses and results of this test were reported to Josh Sheldon, an App Inventor team member from MIT. One of his suggestions was to program the device to include the location of the student when entering and exiting the bus. Josh explained to the team how to use the location sensor feature on the App Inventor program.

The team made this addition to the device, upgraded to a higher data plan, and tested the second iteration of the program through a second beta test. This beta test was also successful. Our team began preparing to expand the device to accommodate more students, and to make adjustments to the badge size and look, with the idea of theoretically scaling-up for implementation for our school transportation department.

Beta Tests

After the original beta test that took place in mid-2015 with children in grades K-2, the BusbudE team took the opportunity to test an alternate use of the design and to consider product flexibility. South Fayette belongs to Digital Promise, League of Innovative Schools, a nationwide organization designed to accelerate innovation in education. The League hosts meetings twice a year in different parts of the country. In October 2015 they chose to host their meeting in Pittsburgh and visit three League schools including South Fayette. Our BusBudE team prepared 70 tags for visitors. Each visitor was assigned to one of four groups and each group followed a different schedule for the day. When visitors entered the bus to travel from downtown Pittsburgh to South Fayette they scanned their tags and their specific schedule, as well as information and web site links about South Fayettes computational thinking and STEAM program, was texted to their phone.

This beta test of the product provided excellent results. We were able to show that BusBudE could be adapted and configured for other uses. From this beta test we were able to move through another iteration of the application and promptly moved back to development for the intended age group in order to complete a larger beta test in early 2016.

The beta test that was completed in March 2016 included 38 students in 1st 5th grade riding Bus 10. This beta test was a user-centered interaction test with a larger population specifically designed for the following reasons. We changed the plastic 3D printing device that holds the NFC tag and needed to discover: (1) were the devices designed appropriately for small hands, (2) could students use the device effectively, (3) would larger numbers of students scanning tags significantly delay or affect the bus schedule, and (4) to discover any additional challenges or obstacles that must be addressed. During this third test, we encountered our first issue with the system. In the morning students scanned when entering the bus but their parents did not receive the text alert. However, the afternoon test worked well. Parents received the text alerts when students entered and exited the bus.

From this test we learned that we need to build a failsafe system into the BusBudE application. We realize that before the phone was attached to the bus it was dropped down several stairs of the bus. The phone must have turned off but because of the way the case was designed there was no way to visually see that the phone was disconnected. The team is working on a re-design to address this issue. In addition, the team is working on a way to design the app so that students can scan without touching the device to make the scanning process faster.

The Future of BusBudE

Currently BusBudE is in its beta stages, thus there are many aspects that need to be altered and adapted before our product can truly be finished. In terms of upgrading our system, we would like to integrate a clear light and sound indication for the students. This would allow them to recognize if their tag scanned and if they are on the correct bus by using a green light and a sound notification for the correct bus and a red light with a sound alert if they are on the wrong bus. We are also looking into the addition of an external display indicating the status of the scanned NFC tag as a solution to this problem. Also, we are currently working to edit our code to enable more features such as precise GPS location notification and to further enhance the reach of the application.

The NFC tags we had purchased for previous beta tests weren't cost effective and were a temporary solution, thus we have started collaborating with an Australian based start-up to lower costs for mass orders and integrate our logo onto each tag. We currently use a phone for our NFC scanner, yet in future iterations we would like to change it to a customized scanner specifically for BusBudE to include increased proximity and reliability.

We have already conducted several beta tests, yet with every revision to BusBudE we would like to hold at least one beta test to observe the effect of each specific change in our product. In the future we hope to include full functionality and use of the application serving every student within the South Fayette School District. From this point, assuming the implementation is successful, we would like to begin to expand to other districts and potentially become an entrepreneurship venture.

Meet the BusBudE Team from South Fayette Township School District

Anish Thangavelu, 8th Grade; Meghan Banerjee, 12th Grade; Vinay Pedapati, 9th Grade; Parv Shrivastava, 8th Grade; Joe Cavanaugh, 11th Grade; Sam Cohen, 11th Grade; Nick Wilke, 11th Grade