Details of our proposal

This proposal project is a collaborative effort of Shiho Kawashima, Melissa Mendoza, and Lyneve Quiles.

We propose that the MTA make it possible for cell phones to receive information via text messages.

As of today, cell phones are pretty much useless underground. This presents a variety of problems, which we outlined in our first installment. Having the ability to communicate underground is important, especially during emergencies. While being able to talk using a cell phone is the ideal circumstance, it will face opposition from commuters who prefer that people practice some cell phone courtesy in public spaces. Thus, SMS is a great compromise. It enables communication to take place, but in a more silent (and tolerable) manner.

Commuters will definitely take advantage of this capability, and it is useful for train conductors as well. If a train gets into an accident, if the radio/phone does not work, or if at any time there is no power, the conductor has the ability to text to the MTA information regarding accidents or delays. In doing so, the MTA is able to get information to its commuters immediately.

We propose that the MTA establish code numbers to which commuters can send via text message, to learn about possible train delays or schedule disruptions. There would be different codes for each train line.

Here is a scenario that can take place today: Lyneve is on Fulton Street waiting to board the 4/5 train in order to get to school. She has been waiting for the train for 10 minutes and is getting very impatient. An announcement is made through the intercom, but Lyneve is unable to hear it because of static and commuter chatter. So she continues to wait, not knowing that service has been delayed due to derailment on Bowling Green. As a result, she is late for our class.

Here is the same scenario with the implementation of our plan: Lyneve is on Fulton waiting to board the 4/5 train in order to get to school. She has been waiting for the train for 10 minutes and is getting very impatient. An announcement is made through the intercom, but Lyneve is unable to hear it because of static and because of commuter chatter. Feeling hopeless and cranky, she takes out her cell phone and sends a message that reads “info” to 334 and 335, which are code numbers for the 4 and 5 trains. In a matter of seconds, she gets a text message from both 334 and 335 that reads “Service delayed due to derailment on Bowling Green.” With that, Lyneve rushes out of the station, and takes the bus instead. Due to the great new system of information transfer, she makes it to organizational communication class on time.

This is just one way this system can improve the quality of our daily commute. Imagine waking up on a stormy day. The rain is unrelentless and the streets are flooded. Then imagine being able to text the MTA and find out whether or not the C train is working. One would no longer have to walk through the storm and into a crowded train station only to find that service was halted due to flooded tunnels. Basic inconvenience such as these would be solved instantly through mobile capabilities.

We propose that a number (or code) be established specifically for security/safety reasons. If a commuter witnesses a crime, suspects devious behavior, or is involved in an accident, he or she has the capability of contacting the police/hospital immediately.

In these situations, it is best for people to have the capability of dialing 911 in their cell phone (since more people place emergency calls using cell phones than land lines) and directly tell the operator what is wrong or what happened. Unfortunately, in subways, the best thing a person can do today is to call the conductor or if the emergency is very serious, pull the emergency brake handle. With text messaging, at least commuters have a chance to contact help on their own.

Let’s say that Shiho got on the downtown 6 train. On the way to Spring Street, a commuter faints. Today, a person would have to call the conductor to inform him or her of the situation or wait to get off at the next station, run into the street, and dial 911 to get help. Instead, Shiho takes out her phone and sends the text “commuter faints on 6-Spring” to the code number 911. Having this capability will give EMT the chance to go to the Spring station immediately to help the passenger.

Also, text messaging capabilities can also be used to alert the MTA or commuters of suspected terrorism or any major accidents that might take place. In London, there is a system where people can pay a fee in order to receive information if a terrorist attack ever took place within the area. The MTA can develop a similar system, but of course, it ought to be free. If an emergency, such as a station fire, took place, the MTA should be able to contact commuters as soon as possible, especially those nearby the scene of the accident.

In order for this system to be more efficient, the MTA should develop a short handed language for certain words (like “emergency” or “accident”) so that typing a message would not have to take a such a long time to do. They should distribute this information through mailings, through posters/advertisements, or through posts online so that passengers will know how to properly- and quickly- text a message when an accident occurs.

We propose that the MTA develop a system in which commuters can go online, register their phone number, and determine what information they would like to have sent to them via text messages. The plan calls for giving commuters the ability to customize the information they receive, as to make sure that messages sent to them are specifically about the trains they or their loved ones take.

This is probably one of the more ambitious aspects of our proposal, even more ambitious than having wireless signal installed in the subway tunnels. This is because this aspect of our plan will require a good amount of commuter participation, and since nothing like this has ever been done before (in New York), we are unsure of just how involved the commuters will be.

Basically, in the “Lyneve Stranded on Fulton” scenario, Lyneve was able to take out her phone and send a text message by using a code number in order to receive information about her train. Here, we want the MTA to take it a step further by actually having the ability to send out information via text message to commuters as soon as an accident, derailment, or delay takes place. We believe that this can be done if the MTA creates an online commuter database, where commuters can register and have information sent to them about the train line of their choice.

Here is how it would go: Lyneve, frustrated from the delayed service, goes home and goes online. She decides that instead of texting the MTA to get information about train delays, she would rather have that information texted to her as soon as it happens. So, she finds the MTA Commuter Database Registration page and registers. Lyneve types in her name, her email address, and her mobile number. She presses “enter” and is then directed to a checklist, which included a directory of train lines from which she can choose. She checks the A, 4, 5, and 6 trains because these are the trains that she uses on a daily basis. Lyneve then confirms the selection. She is now part of the commuter database and can customize/update her profile depending on how private she wants it to be. If possible, the MTA can go even further than commuter profiles by enabling commuters to have their own commuter blog. Here, commuters can write down anything MTA related or it could simply be a location where commuters can go and let off some steam.

Since Lyneve is now a registered commuter, she should able to receive information via text messages if at any time one of her trains become delayed or involved in an accident. Therefore, she will be kept up to date regarding the status of her trains wherever she is.

We propose that MTA create a system in which foreign tourists can register their number online so that the text messages they receive are customized into their national language.

Tourists from foreign countries should also be able to receive the same information regarding train delays. However, information in a language they cannot understand is pretty useless so we want the MTA to create a way for tourists to receive text messages in their national language. Like Sunny's Korea Infogate Company, the MTA should strive to make it more convenient for tourists to retrieve information specifically about train service. For this to work, a tourist can basically follow the steps that Lyneve took when registering. Upon their arrival to New York City, a tourist can go online, go the MTA registration page specifically for tourists and register their number. Then, they can check off what language in which the text message they receive is written. This will allow tourists to travel more efficiantly while on vacation, they can now spend time seeing the sights, rather than trying to find their way in a confusing mess of subway lines.

We propose that MTA develop a website where customers can go and post/retrieve information regarding: train delays/problems and neighborhood events specific to the subway stops.

This proposal is also an ambitious plan since it too requires commuter involvement and participation. Here, we propose that the MTA create a website for commuters- who may or may not have registered for the database- to be able to obtain information regarding train delays and neighborhood events. This website can be modeled after internet forums, tag boards, or message boards, so that commuters have the chance to post down messages or information. This site should be organized by having different directories for each train line (1,2,3, A,C,E, N, R, 4, 5,6, ect) and then sub categories such as problems/delays, and different stations/stops (6- 42nd, 6- 51st, 6-59th, ect). That way, one could navigate his or her way to information regarding a specific train line and also a specific station/neighborhood/area.

Since we want to allow commuters to post, we want to model it after wikis, which Rosalyn describes as reliable and an "easier way to exchange ideas," or Eric’s idea of an instant blogger, where a number commuters, not just one person, can post ideas in one blog. These tools are helpful and better suited for our plan because they allow for current information to be displayed and limits the length or cluster that develops tag boards or message boards. By enabling commuters to write and post their own messages, a commuter, like Gage, can go on a specific directory and post about a new bar that is opening up so that other commuters around the area can go for a visit.

Let’s say that Shiho, an unregistered commuter, wants to know if there the 6 train was running behind schedule today. She goes online, finds this website, and clicks on the 6 train directory. She read current information that the MTA posts on the site (unless a commuter beats the MTA to it) regarding a slight delay in service. Shiho browses through the site and reads a post on “6-59th” which is about a major sale in Bloomingdales that is happening this week. Shiho also goes to “6-Bleecker” and reads about an open mike night that will be taking place on Friday in one of the cafes a few blocks away from the station. Shiho thinks this site is fantastic and bookmarks the 6 train directory for future reference. Or, if she wants to, Shiho can add this website to her aggregator, so that she can always check her aggregator of any updates regarding the 6 train.

The London Tube Guru is basically a website that the MTA can use as a model for this plan. In this website, a commuter can click on a station and find points of interests around the area. The information that the Tube Guru provides include: restaurants, bars, cinema, tourist locations, hotels, etc. This kind of information is not only useful for commuters, but for tourists or those new to the area as well. Another site that the MTA can look over is the London's National Rail Enquiries. This website lists the location of places where service may be delayed because of construction, as well as a time table of possible engineer work in the future.

And one last suggestion if we may...

Since commuters will be receiving/sending information via text messages, it is imperative that the cell phones work at all times. Thus, trains and train stations should have outlets that commuters can use to charge cell phones. The plan calls for chargers in main subway stations. In Japan, service carriers provide chargers in the metro. It is free and every body can use this system. When Shiho's brother went took a trip to northern Japan, he forgot to bring his charger. At that time, the weather conditions were so bad that he changed his trip plans. He needed to talk and tell his family to pick up him at the train station, but his cell phone did not have any battery. Finally, he found the free charger in the train station and used it.

This system is not only great for commuters, but for tourists and for people who work and need to be in constant communication with their coworkers at all times. In New York City, such service is nonexistent since there no cell phone charger system, even in big stations like Grand Central, Times Square and Penn station. These three stations are always visited by many tourists and visitors. Since many tourists are here, they have an added need to be able to charge their cell phones to make it less of a problem for them to make contact with family and friends in a strange city.

Possible drawbacks to be discussed in our third and last installment, as well as a final wrap up of our project.