Members:

Alan Buabuchachart
| alan2234637 at hotmail com |
| Computer Science |
2014
Evan Ponchick
| eponch at umd edu |
| Operations Management |
2012
Frankie Abralind
| fabralind at gmail com |
| MBA |
2012
Gary "Cubby" Brendle
| gbrendle at umd edu |
| Computer Science |
2014

Faculty Advisor:

Massimiliano Albanese
| albanese at umiacs umd edu |

Proposal:

On a campus this large, members of the Maryland community need a single, centralized way to quickly report broken things and support a clean campus. And “Tell the Terp” can provide this service!

In any community in general, many things break and need maintenance. The job of finding these things is often left up to members of the community. Maintenance workers simply cannot find every issue. At Maryland there are some systems in place, but they are fragmented and not everyone knows about them. Most people will not bother if it is too difficult for them to find out who to contact for a specific building or place on campus. Following are some examples.

The bolt in your door room is loose. It is now taking you and your roommate over five minutes to open the lock. On a phone call to 4WORK you describe the situation and an employee comes by the next day. He inspects the door and does not have the proper equipment. Much time would have been saved if only you could send a picture into 4WORK attached to your request or phone call so the maintenance help could be better prepared.

In another instance, there is a trash overflow in Glenn Martin Hall and you happened to come across it. Instead of walking by and being unable to do anything about it, you can "Tell the Terp" to quickly report the problem and be happy knowing that you helped the fellow Terps.

The above situations illustrate that a simple picture with geolocation data and maybe a small amount of text can notify the appropriate personnel to the problem with very little effort by students, faculty, and staff of Maryland. Our proposed “Tell the Terp” application is a simple mobile reporting system for students, faculty, and staff to use to report anything that needs attention.

The app will have a simple interface that allows the user to quickly take a picture and tag it with a description. The app then automatically calculates the position of the user and decides which person to send the report to. For example, the user won’t have to say that there is a broken desk in Van Munching Hall, instead he/she can simply say “broken.” With the visual aid of an image, maintenance in Van Munching Hall will realize right away what is it that that user is referring to. The system ensures that the report is sent to Van Munching Hall and not on Glenn Martin Hall. The technical implications that come with this consist of obtaining exact locations of all campus Wi-Fi access points and using this information to accurately determine the position of a user, distinguishing between reports from within a building and reports near it, and filtering out spam.

On the client-side (users) it is an app on the iPhone platform. Meanwhile, on the server-side (maintenance people), it will be on the web platform. On the web platform, the tagged images sent from the users’ iPhones will be displayed and updated live. The web will also allow a public access. In other words, people can view which problems exist on campus and which are fixed. This will promote the success of the app and the quality of campus maintenance.