Vehicle Tracking and Capacity System

Vehicle Tracking and Capacity System Project Sponsor: Dr. Joseph A. Morgan Faculty Advisor: Dr. Jay Porter October 15 th, 2007 Edited by: Signed:

Table of Contents Introduction... 3 Project Design... 3 Problem Statement... 3 Functional Requirements... 3 On board Device... 3 Back end Device... 4 Conceptual Design... 4 On board Device... 4 Back end Device... 5 Functional Design... 5 Work Plan... 7 Milestones... 8 Deliverables... 9 Resources... 11 Marketing Analysis... 11 The Target Market... 11 Environmental Analysis... 12 Competitive Forces... 12 Economic Forces... 12 Political and Legal Forces... 12 Technological Forces... 12 SWOT Analysis... 12 Team Qualifications... 13

Introduction You are waiting at a stop for a bus that is 20 minutes late. The rain is pouring down and while your umbrella is keeping your head dry, it is doing nothing for the rest of your clothing. Suddenly, the bus passes you without stopping; it has already reached maximum capacity. Next imagine that it is 3:45pm and you are the parent of a five year old who did not get off the school bus. Did she get off at the wrong stop? Did she ever get on? Now imagine that there is a public transit tracking system that can give you information that would have prevented either situation from ever being an issue. This system not only allows you to check the location and capacity of your bus, it also notifies you when the bus is nearing your stop in addition to allowing transit authorities to verify when and where individual passengers entered and exited. According to The American Public Transportation Association there are over 83,000 public transit vehicles i and 440,000 public school buses in operation ii. Due to this massive and increasing use of public transit the government has become actively involved in ensuring public transit safety. In 2006 the Department of Homeland Security announced that it would allocate $150 million for the year to transit security research iii. Legislature has approved an additional $3.4 billion over the next four years iv. It is for this purpose that VL Technologies has created VTraC, the Vehicle Tracking and Capacity System. This system is being modeled based on the specifications necessary to enable use by the Texas A&M University transit system. Project Design Problem Statement The purpose of the VTraC system is to provide increased safety and convenience for commuters using public transit by implementing vehicle tracking, passenger identification and capacity monitoring. Functional Requirements The functional requirements listed below are the bare minimum specifications for the VTraC System. These requirements are divided into two categories, the on board device located on the bus and the back end device that consists of the database and support software. On board Device System Power Must operate utilizing conditioned vehicle power of either 12V or 24V. GPS Unit Must receive location data from GPS satellites. RFID Unit Must count and identify passengers. Page 3 of 14

Cellular Transceiver Must transmit position and passenger information via cellular communications. As a whole, the on board system must allow for user friendly installation and be entirely automated, requiring no action from the driver. Lastly, installed units must be unobtrusive to vehicle occupants. Back end Device VTraC Software Must receive vehicle location and passenger information from on board unit and then transmit that data to system database. Database Must be scalable to allow for multiple vehicles to report data. The database must also provide a simple privileged user interface for access to passenger identification and vehicle location. Web Presence Must be able to display multiple vehicle locations via webpage. Website must also allow users to subscribe to arrival alert feature. Conceptual Design On board Device The on board device is a physical black box unit to be installed on the bus. This unit will receive location information via a GPS system while RFID sensors collect passenger count and identification information (see Figure 1.) These two pieces of information will then be combined and transmitted, via cellular network, to the back end system. Figure 1 Conceptual Diagram: On board Device Page 4 of 14

Back end Device Once Location, Capacity, and Passenger ID information is received by the back end system it will be stored into a database (see Figure 2.) In addition to storing data, privileged Fleet Management users will have access to this database in order to retrieve the location and passenger identification information. The database will also be used to disseminate the data to commuters using the VTraC User Website. This site will display the current location of all VTraC equipped vehicles as well as display a meter representing the vehicle s remaining passenger capacity. Through this site, users may also subscribe to the Arrival Alert System which allows them to receive text messages with estimated arrival times for a particular route to a specific stop. Figure 2 Conceptual Diagram: VTraC Support System Functional Design On board Device Texas A&M University buses have a dual voltage system on board, a 24V system used for ignition and a 12V system used to operate electronics such as the radio and lights. VTraC will utilize this pre existing electrical system to provide power to the on board device. The power will be conditioned and reduced to between 3.3V and 5V as determined by the requirements of the VTraC device. The unit will be connected through a switched power source to ensure it does not create a power draw that might drain the battery while the vehicle is turned off. The processor must be connected to all the peripheral devices in order to pass information. The diagram (see Figure 3) shows RS 232 serial connections between every module and the processor although this may change as research progresses and decisions are made on specific components. The microcontroller will be programmed to regularly query the GPS unit for current location information. In Page 5 of 14

the event that the bus is in motion, this location information will be sent via cellular network to the back end for update. A different subroutine will be triggered when the door is opened that will initialize and receive data from the RFID reader. The reader will capture passenger ID s and forward them to the processor for temporary storage. Once the doors close again, the processor will combine the latest passenger information with location information and transmit it to the back end at which point the system will resume sending regular location updates. As shown in the block diagram in Figure 3, the cellular module defined is shown as a transceiver and not a transmitter. Although the present needs of the system require simple transmission, the ability of the on board unit to receive information may be useful or necessary in the future for things such as firmware updates. VTraC Support Software The back end of the VTraC System, referred to as the VTraC Support software, will receive information from the on board device in the form of a standard format e mail. This e mail will contain the most recent GPS coordinates as well as the last passenger count and identifications retrieved from the RFID sensors. Once received the data from the e mail will be passed into the database. Database The next phase of data processing takes place at the system database. This database will be the central location for all information used by the VTraC System. Given that the product should be scalable to accommodate different fleet sizes and routes, the database will be expandable to support any and all of the multiple buses, routes and passengers. Another requirement for the database is that it allow access to data by both the VTraC web front and the transit side user interface. Because of the need for commuter privacy only the transit authorities will have the option of accessing passenger identification information. Lastly the database must also allow subscribers to register for the Arrival Alert feature. This requires that they have the ability to upload a cell phone number, desired bus stop, route and designated arrival time. User Interfaces The Database will have two functional interfaces. The first will be for the use of transit authorities and the second for passengers/subscribers. As specified above, the transit authority interface will enable the retrieval of reports on location and passenger RFID information. The web front will allow users to view the bus location on a route map overlay and allow them to sign up for the VTraC Arrival Alert using subscriber phone number, service provider, bus route and stop. With this information VTraC will be able to send a text message alerting the subscriber to the upcoming arrival of a bus. Page 6 of 14

Figure 3 Functional Block Diagram Work Plan In order to effectively manage the progression of the VTraC System the following work plan has been defined (see Figure 4.) This project has been divided into seven phases; Research, Design and Development, Procurement, Implementation, Testing, Documentation and finally Closure. Figure 4 VTraC Work Plan The Research and the Design and Development phases will be broken down between the on board device and the VTraC Support Software. For the on board unit research must take place in the areas of GPS receivers, RFID technology, cellular transceivers and the microcontroller necessary to process the data. Research must also be done to understand the requirements and principles behind the databases, Page 7 of 14

e mail processing and web design that must be implemented in the VTraC Support Software. Once research is complete, design and development of the on board PCB, website, database and the embedded programming will begin. At the conclusion of design, the Procurement and Implementation phases commence. These phases are broken down into hardware and software. The hardware that will need to be implemented includes the following: GPS receiver, cellular transceiver, RFID tags and module, microcontrollers and server. The software needed includes: database, embedded programming and web design software. The Testing phase will consist of three parts. The first part will be the component verification where the individual parts of the system will be tested. The next part will be the integrated testing where testing of networked components takes place. The scope of these integration tests will increase until the full system is assembled at which point the final Fully System testing will take place. In this phase the system will be put through a barrage of tests attempting to find weak points and repair as needed. Phase 6.0 consists of documentation of the Schematics, PCB Layout, Software, Testing, and Final documentation. Documentation will take place over every facet of this project to ensure that no mistakes are repeated and to ensure that it is possible to replicate the design. The Closure phase of the project will consist of three parts: the presentation and demonstration of the working prototype, the final approval from the Academic Advisor and Project Sponsor and lastly the determination of any/all E4 opportunities. It is through following this work plan that the successful completion of this project will be possible. Milestones In order to best determine the progress of the VTraC System, significant milestones have been defined. These milestones are as follows: Completion and Approval of the Research Research is a significant requirement for this system given that it will provide the knowledge base necessary for a working prototype. The research will include finding the best components for the project at the most reasonable price for each. Research will also include finding the best software for the project, as well as finding the best hardware and software integration package. The completion and approval of research for this project marks the launch point for the rest of the system. It is at this point that procurement and construction can truly begin. Completion and Approval of the Hardware Design The completion and approval of the hardware design will include a full schematic layout of all hardware components. Necessary hardware for the project includes the printed circuit board design of the onboard device and the components in the RFID sensor network. Completion of this phase signifies that the on board portion of the system is essentially complete. Page 8 of 14

Completion and Approval of Database Design The completion of the database design will mark the creation of a scalable system that will be loaded onto the transit server. The database will have an easy to use interface that transit authorities can utilize to find bus location and passenger identification information. The completion and approval of the database design designates that a major portion of the back end system is complete. Completion and Approval of User Interface The user interface accesses the previously completed database and uses that resource to display location and capacity information. The user interface will also will users to subscribe to text messaging alerts. Completion and approval of the user interface will be the last significant design need of the backend system. Completion and Approval of Hardware and Software Integration The completion of hardware and software integration is a significant milestone. It is at this point that a preliminary working version of the VTraC product will be available. Completion and Approval of VTraC Prototype A prototype of the VTraC project will be assembled to demonstrate the functionality of the system. The completion of this phase is an important milestone because it is at this point that all design, procurement and system implementation will be complete. Completion and Approval of Documentation The last milestone of the project is the completion and approval of the final documentation. Documentation for the VTraC system will include a full schematic, an installation guide, a user s manual, a troubleshooting guide, and all test results. Deliverables The project deliverables include documentation, technical installation guides, schematics, and other items that have significant value to the customer. In the case of the VTraC system the stakeholders include Dr. Joseph Morgan, the project sponsor, and Dr. Jay Porter, the project advisor. The following deliverables will act as tools for Drs. Morgan and Porter to mark the progression of the VTraC project: Figure 5 VTraC Deliverable Schedule Page 9 of 14

Functional Block Diagram The functional block diagram is a visual representation of the system requirements for the VTraC project. This includes all known data concerning the system s hardware, support software, physical medium and protocols. Hierarchy/Flow Chart The hierarchy/flow chart will be used as a supplement to the software code. It will demonstrate the logical flow of coding for both the on board and back end sections of the VTraC system. Pseudo Code This deliverable will demonstrate the conceptual flow of the software code necessary to program the back end of the VTraC system as well as the on board processor and modules. Initial Systems Schematic This schematic will demonstrate the preliminary hardware design for the on board portion of the VTraC system. System Parts Listing The system parts listing is a depiction of components to be used in the VTraC system. This will include all pertinent specifications as well as pricing information. Initial PCB Layout The first PCB layout is a schematic used to give the customer an understanding of the hardware circuit envisioned for the on board unit. Initial Database Code This deliverable is the preliminary software coding for the back end of the system. Initial database code will include integration software for the web interface as well as the coding for the database itself. Initial User Interface Code This deliverable will demonstrate the software coding for the online interface. This is the code that must display route information to users as well as allow subscribers to sign up for message alerts. Systems Testing Report This document will outline the testing procedures used to verify functionality of the project to date, as well as the results of all tests conducted. Final System Schematic This document marks the beginning of the final phase of the project. After all testing and revisions have been made to the system the final schematic will depict the definitive layout. Final PB Board Layout This will be the final copy of the PC board layout after all design and testing has been conducted. Final User Interface Code This will be the final version of the web support software that will allow users to logon to the server and signup for alerts and view route information. Cost Analysis The cost analysis will be a financial breakdown of the parts listing, labor hours, laboratory fees, etc. required to recreate the VTraC prototype. Page 10 of 14

Final Documentation The last deliverable will be a compilation of documents including all necessary user manuals, setup instructions, and troubleshooting guides for the VTraC system. Resources Below is a preliminary listing of resources that would be required to recreate the VTraC prototype: Item Cost ($) RFID Reader Module 165 RFID Tags 20 Microcontroller Dev Board 250 GPS Module Dev Board 300 Software 200 Printed Circuit Boards 480 Components 100 Server 1200 14 weeks of Lab Access/Facilities 4500 Labor 4 Engineering ($30/Hr. x 25Hrs/Wk. x 16Wks.) 48,000 Estimated Total 55,215 Marketing Analysis The Target Market The VTraC technology is aimed at addressing four areas with the potential of huge benefits. They are wait time, capacity, safety and asset tracking, and passenger identification. Nobody likes to wait; today s culture is all about right now, and through the VTraC technology riders will not have to wait outside or deal with inclement weather any longer than necessary. They will also be able to find out how full the bus is. If it is too full then they will know to either wait for the next bus or find other means of transportation. Transit authorities will also now be able to tell where every vehicle in their fleet is and if any of those vehicles deviate from their assigned routes. Passenger identification technology will also help in notifying families should there be an accident or any other incident involving a transit vehicle. Also, parents will know whether or not their children have gotten onto the bus or not. All these benefits together will greatly decrease frustration and increase confidence in the reliability and safety of the public transportation system. Page 11 of 14

Environmental Analysis Competitive Forces The idea of tracking a fleet of vehicles is nothing new. Law enforcement has been doing this for years, keeping an updated map of where all squad cars are at any given time. Tracking a fleet with the customer, in this case the bus rider or their parents, in mind is not in implementation. Because this service is not currently provided, there will be no immediate competition from other companies. Economic Forces The Department of Homeland Security allocated $150 million last year and Legislature has approved $3.4 billion over the next four years for the advancement of transit security. With an increase in the use of public transit, the government has recognized the need to increase passenger security. The VTraC technology developed by VL Technologies will provide a relatively inexpensive way to help increase security as well as increase customer satisfaction with public transit. Also, with such a large increase in government spending in public transit, VL Technologies hopes that that money will help subsidize this technology once it is operational. Political and Legal Forces At this time there are no political or legal objections to this type of technology. In implementation, however, VL Technologies will have the responsibility of not divulging too much personal information. With privacy such a high concern, steps will be taken to ensure that privacy remains a priority. For example, if this system were implemented on a elementary school bus, only authorized school officials and the parents of the child would be able to know if their child is on the bus or not. Also, exact numbers of how many people are riding the bus would not be made public, only an approximate rating of occupancy. Technological Forces The technology involved in the VTraC product is not novel. The base components of the technology have been available for some time. However, the combination of technologies, coupled with innovative software will create a novel technology. SWOT Analysis Strengths VTraC is a novel technology Will increase customer satisfaction with public transport Will increase transit security by giving transit authorities access to passenger lists, and vehicle locations Weaknesses The system utilizes cell phone networks, which can be prone to having service outages, or busy networks (example: College Station during a home football game weekend) Page 12 of 14

Opportunities Could be expanded beyond public transportation for use in school districts. Availability of funds from the Department of Homeland Security Threats Privacy concerns must be addressed Technologies imitating the success of VTraC Team Qualifications VL Technologies consists of a diverse and uniquely qualified set of individuals. The team composition is as follows: Figure 6 Team Composition Diagram Catherine Grace Christensen Team Manager Responsibilities: GPS system and Documentation Senior Telecommunications Engineering Major at Texas A&M University and has a 3.56 GPA Associates in Applied Science Telecommunications with 4.0 GPA Has held leadership positions in over 10 different groups, organizations and/or corporations Two years of experience operating GPS based equipment for Texas A&M University Extensive experience in circuit design, testing and implementation of hardware and software Page 13 of 14

Jeremy Brandt Telecommunications Engineer Responsibilities: Cellular and RFID systems Senior Telecommunications Engineering Major at Texas A&M University Army Veteran with 5 years experience in Telecommunications field Configured, aligned and operated technical control equipment and associated devices Awarded two Army Commendation Medals and one Army Achievement Medal for outstanding professional and technical proficiency Jason Tomlinson Systems Engineer Responsibilities: Database Design and Web Fronts Senior Electronics Engineering Major at Texas A&M University 5 years Navy Experience as a Communications Electronics Technician High level of expertise in communications ranging from receive only GPS to satellite communications Excellent training and experience in troubleshooting on complex electronic systems Awarded Navy and Marine Corps Achievement Medal and earned Submarine Silver Dolphins Ricky Goldsmith Test/Quality Engineer Responsibilities: VTraC Software and Systems Testing Senior Electronics Engineering Major at Texas A&M University Associate of Science at Northeast Texas Community College 8 years experience as an electrician Held management positions and maintained computer hardware and network for 2 years at Brazos Valley Food Bank Managed construction projects for Texas Sterling Construction Vincent Upperman Marketing Specialist Responsibilities: VTraC finance and marketing data Junior Finance Major at Texas A&M University Interned in the Office of Technology Commercialization at Texas A&M University Worked at to determine economic viability of creating a startup company built on a service created by TAES scientists i Passenger Bus Statistics http://www.apta.com/research/stats/vehicles/vehact.cfm ii School Bus Statistics http://www.bts.gov/publications/transportation_statistics_annual_report/ 1999/chapter4/chap4.htm iii Transit Security Grant https://www.apta.com/government_affairs/dhs_grants/ iv Allocation of funds by legislature: http://www.apta.com/government_affairs/washrep/2007aug09.cfm Page 14 of 14