Archive for MTA Technology
I’ve been sitting on a bunch of open tabs for a little while and thought it would be a good idea to get around to sharing these. These are stories I found interesting or newsworthy but just haven’t had an opportunity to post here.
I’ve talked a bit about the MTA’s new green fee and the money realized from unused MetroCards, and a recent piece in The Times put those dollars into context. Throughout the first decade of the 21st century, the MTA collected half a billion dollars from unused fares. Since straphangers have to pre-pay for MetroCards, dollars that are left on the cards long after their expiration dates remain with the MTA, and on an annual basis, the money is a small, but important, part of the agency’s annual budget.
Unused fares isn’t something that’s come about because of the MetroCard era. Back in the day, New Yorkers would buy tokens and never use them. They would get lost, get forgotten, get overlooked, and the MTA could collect those fares. But today with uneven bonuses that make the math of a free fare more difficult, more dollars are left on cards that expire, and the $1 fee for new MetroCards means revenue as well.
As the MTA phases out the MetroCard — the topic of my March 19 Problem Solvers session — these unused fares may diminish a bit. The next system may well be a pay-as-you-go set-up that doesn’t focus around any proprietary fare collection system. While the MTA will lose the money from unused fares, it will also drastically reduce the amount it has to spend to collect fares. That’s a win for the customers, and a win for the transit agency as well.
As New York City subways go, the 3 train runs an odd route. It stretches deep into Brooklyn but then stops short of anything in Manhattan. It terminates at 148th St. near the Lenox Yard and goes no further north. In a piece at Welcome2TheBronx, Richard Garey argues for extending the train to the Bronx. With the need for some cross-Bronx subway service and the incoming soccer facility near Yankee Stadium, the time may be right to look at some subway extension options.
Garey’s post focuses on the 3 train as a way to serve neighborhoods that once enjoyed streetcar service and now don’t, but I think he has the routing wrong. The 3 shouldn’t end up as another north-south route in the Bronx but could instead cut across the borough, serving areas that don’t have good cross-Bronx transit options while boosting subway service. It is, after all, a fast ride downtown on the IRT express. Without a massive infusion of cash, we’re just dreaming, but it’s an intriguing proposition after all.
Unhappiness at 149th Street
For years, I’ve been using the 149th Street-Grand Concourse subway stop as a transfer point on the way to Yankee Stadium, and for years, it has been one disgusting station. The walls were marred by leaking pipes, and on the way home from a World Series game in 2001, my sister and I saw squirrel-sized rats on the uptown 2/5 platform. It was very, very unpleasant.
Recently, the station underwent a renovation, but a few area residents are unhappy. One transit buff took a video tour of the station post-renovation and discovered some subpar work. Meanwhile, another group of residents wants to restore elevator service that was shuttered 40 years ago. As best as I can tell, the elevator in question went from the 2/5 platform to street level. The MTA has no money, and protestors hope Mayor de Blasio can help out. I wouldn’t hold me breath.
Thanks to an infusion of funds from Council member Vincent Ignizio, four stations along the Staten Island Railway — Great Kills, Eltingville, Annadale and Huguenot — now have countdown clocks. The work is part of a $675,000 initiative funded by Ignizio’s office that will eventually include a Subway Time component that will add these SIR stations to the MTA’s tracking app. For now, the information is available on the St. George-bound side, but Tottenville-bound service will have its time in the sun as well. If you pay for it, it will come.
L train riders, rejoice: The MTA’s real-time subway tracking app and developer feeds have been updated today with location information for the BMT Canarsie line. The update was originally due by the end of 2013, but missing a deadline by two weeks seems minor in the grand scheme of things. With the latest update to the MTA’s own iOS app and the web-based interface as well as the open-data feeds for third-party developers, L train riders can find out how long — or short — their waits will be before heading underground.
For the MTA, this is the first upgrade to the Subway Time app, and while the design or scrolling experience haven’t improved, the data available now includes arrival time estimates for eight of the city’s subway routes. Unfortunately, it’s also likely to be the last update for a few years. The CBTC signal project currently underway on the 7 line is expected to wrap in 2016, and the Flushing line could be added thereafter. The MTA is still eying a three- to five-year rollout of some sort of digital tracking system on the remainder of the lettered lines, but it’s unclear if the agency can meet that deadline.
In any event, today’s upgrade is a welcome one, even if it underscores the time we’ll have to wait for information on the rest of the system’s trains at the same time.
The target date to wrap the MTA’s installation of communications-based train control along Flushing Line has been delayed six months until mid-2017, the agency said in documents released this weekend. As part of the update to the Capital Program Oversight Committee, the MTA noted that the $550 million project remains on budget, but due, in part, to complications from Sandy, the project’s substantial completion date has been pushed back from the fourth quarter of 2016 to the second quarter of 2017.
According to the documents, two issues could further impact this date. The first concerned the availability of test tracks for the CBTC-enabled R188s. These cars were due to be tested on the Rockaway Test Track, but this stretch of railbed was damaged during Sandy. The delay in repairing the test track has pushed back the date for final delivery of the R188s from February 2016 to August 2016.
Second, the MTA fingers “G.O. Availability” as a concern. As CBTC work means many weekends without 7 train service into and out of Queens, the agency has been working with community leaders along the Flushing Line to better plan outages. As the Board materials say, though, “if track outages for this project are delayed/denied, the project’s milestones will be delayed.” In other words, if the MTA can’t schedule G.O.’s, it can’t perform the work on time. I’ll continue to follow this story, but for now, the expected completion date is slipping.
Amidst much anticipation, Manhattan now has real-time bus tracking as the MTA unveiled BusTime for the County of New York. At around midnight this morning, BusTime — the MTA’s in-house-built, distance-based system — went live on nearly all Manhattan bus routes. The system is available on the web right here, and already, bus bunching is on display for all to see.
In announcing the new technology, a variety of MTA officials made their perfunctory statements. “MTA Bus Time is a game changer and a service that greatly enhances our customers’ experience with bus travel,” MTA Chairman and CEO Thomas F. Prendergast said. “MTA Bus Time has turned your phone into a tool that tells you when to start walking to the bus stop so you can get there right when the bus does. Meet your bus, don’t wait for it.”
Those riders who can now meet their buses — or opt to walk — instead of waiting include those who use the following routes: M1, M2, M3, M4, M5, M7, M8, M9, M10, M11, M14A, M14D, M15, M15 SBS, M20, M21, M22, M23, M31, M35, M42, M50, M57, M60, M66, M72, M79, M86, M101, M102, M103, M104, M106, and M116. The M34 and M34A were already a part of BusTime, and Brooklyn- and Queens-based routes that enter Manhattan will be added as BusTime comes to those boroughs and depots within in the next six months. The MTA estimates that 93 percent of all Manhattan bus riders can now track their routes.
To bring this borough’s iteration of BusTime online, the agency’s small in-house staff had to code in 1800 bus stops while adding GPS hardware to the buses that operate in the city. Since 2012, the MTA has installed this technology on 2852 buses. Conveniently, the MTA also provided a list of apps already accessing the BusTime API. Those include, for iOS All Aboard NYC; All Schedules Free; Bing Mobile; Bus New York City; Google Maps for Mobile; In Time Staten Island; Ride On Time NYC; Roadify; and Transit Times. For Android, Bus Tracker Pro – MTA NY and Sched NYC feature real-time bus information.
As with the previous boroughs, Manhattan’s BusTime is based on distance rather than time. Since travel times are variable and far more costly to get right, the MTA has gone with a distance-based approach that allows riders to estimate potential wait times. It’s not perfect, but any regular rider should pick up on the idiosyncrasies within a handful of uses.
Meanwhile, through the web interface, you can see bus bunching in action. Earlier today, a variety of north-south lines had two, three or even four buses all within 10 blocks of each other with big gaps in service. Jason Rabinowitz at NYC Aviation noted the problem with the M60 and service across 125th St., a particular sore spot after a vocal minority temporarily squashed bus improvements for the congested corridor.
With a wealth of location data now available, hopefully, the MTA can begin to attack the problem of bunching head on. For everyone else, now you know where your bus is and that hopeless stare down an avenue can become a thing of the past.
Citymapper, a iOS app that uses real-time transit information and up-to-date service advisories to provide its users with a wealth of travel information within the five boroughs, won a $20,000 prize in the MTA and AT&T’s 2013 App Quest contest, the agency announced today. The app comes with a web component and can even tell users how many calories they’ve burned on a trip throughout the city. It’s not quite transformational or quirky, but it works.
This year’s App Quest launched in May and featured 49 submissions. My personal favorite in terms of creativity was an Android app called MetroNap that uses motion sensors to wake up the user when he or she reaches a destination. It did not walk away with a prize though from the panel of nine members of the city’s burgeoning tech and V.C. industry.
In addition to Citymapper, five other apps walked away with cash prizes. Subculture.FM allows uses to get more information on the artists who participate in the Music Under New York program; Transit App, my current go-to for train arrival times and trip instructions, took home $5000. Accessway, an accessibility app for visually impaired riders, and Bus NYC, which taps into the BusTime API, garnered honorable mentions, and Moovit, yet another mapping app, was the winner of the popular vote.
“The app developers who competed in this challenge have shown that they have the know-how, the enthusiasm, and the energy to do great things with the open data we and others provide,” Thomas Prendergast, MTA Chairman and CEO, said. “And we are glad that so many in the tech community have put their efforts into helping the MTA, and, more importantly, our customers. That’s why we are going to continue to expand the amount of open data we provide.”
Once again, the MTA, with a fiscal assist from AT&T, decided to outsource app programming to the benefit of the riders, and we have a new series of apps to use, enjoy and, sometimes, delete. Check out all of the submissions right here.
Apologies for the short post tonight. I have an early morning meeting on Wednesday, but I’ll be back with a new edition of the podcast, among others, later on this morning.
When the MTA dismissed an arbitrator who has often sided with the TWU in resolving disputes, an old issue reared its head. In discussing Richard Adelman’s past rulings, I noted that he had stopped one-person train operation on the L train back in 2005. It was but one story in the MTA’s never-ending saga to see through some form of OPTO in the New York City subway system.
As is often the case when OPTO comes out, a debate over its future arose in the comments. I’ve long believed that OPTO is a necessity in some form or another if the MTA is to realize significant cost savings on the labor front. Although the initial capital costs at readying the system for OPTO may be challenging, the year over year savings would more than justify the initial outlay. The trick in implementing such a system would be in identifying the proper form. Does OPTO make sense on the Lexington Ave. trains at rush hour? Does it make sense on the Brighton Line during the weekend? The answer may not be the same to both questions.
The opponents of OPTO — union workers who stand to lose their jobs — are strong though, and they’ve run the table on this argument for years. On the one hand, OPTO is a tough sell from the MTA. They’re basically telling everyone that there will be fewer employees on train cars, and the psychology of such a stick without a corresponding carrot is a tough one to swallow. On the other, those who oppose OPTO have made their case and stick to it.
Essentially, the opposition breaks down as follows:
- New York City’s subway system is older than other systems that use OPTO, and its platforms are too curvy. It’s trains are longer; it wasn’t built for OPTO.
- It’s not safe for passengers and leads to delays. Imagine how long it would a T.O./conductor to walk from the first car to the last in the event of a problem.
- It’s not safe for the T.O./Conductor and puts too much stress on them.
The first argument is New York exceptionalism at its finest. If it wasn’t invented in New York, then we can’t have it, and clearly, we’ll never be able to have it. It’s also the weakest of the arguments. There are automated lines in the Paris Metro and OPTO in place in similar systems to ours. It’s simply a matter of will and ingenuity, and it wouldn’t even take much to see it through. New York is exceptional in some ways but not in this regard.
The other two are legitimate concerns that prevent the public from getting behind OPTO, and this is where implementation would have to be done delicately and properly. An in-car intercom system would have to be developed; better security responses would have to be created. Again, it’s a challenge, but it’s not insurmountable. Meanwhile, moving conductors out of the train cars would allow the MTA to place some on platforms for crowd control purposes or others in stations as agents. Not all would have to be dismissed.
In this safety argument lies the delicate balancing act the MTA needs to execute to see through OPTO. It’s not right for every train line at every moment in time. It likely wouldn’t be a smart move for peak-hour trains along the most crowded of routes but certainly could be effective nearly everywhere on the weekends. It wouldn’t have to lead to more delays or more problems and could help the MTA free up operating money for other purposes.
Ultimately, this is hardly a scientific study on the costs and benefits for OPTO. I’m almost thinking off the cuff here, but it’s a conversation worth revisiting. Ultimately, the MTA should be working toward automation where possible, and OPTO is a good first step. If anything, it can cut down on unnecessary labor costs. But we’re stuck in this rut. It didn’t happen first in New York City so it can’t happen here.
We learned yesterday of new audio announcements concerning train arrival information for a handful of stations in Astoria, and today, I have more information concerning the tracking technology. While the project is mostly a one-off implemented at the request of Astoria’s Assembly representatives, it’s a bit more useful than I first thought.
Notably, the countdown is in minutes — not stations — with audio announcements beginning when the next two trains are within six minutes of the station. The announcements arrive every two minutes with the latest on moving trains and are also audible in the station vestibules. For cold weather days, this will come in handy. There are no plans to incorporate this type of information into a visible countdown clock, but the MTA says it is moving ahead with an effort to bring clocks to the B Division — all lettered subway lines — within three to five years.
So what’s the plan then? According to an MTA spokesman, the agency aims to “get to where we are in the A Division in terms of the same level and type of information,” but the Astoria treatment is independent of that effort. (In Astoria, the announcements are tied into prior signal upgrades.) For now, the MTA is focusing on capturing train arrival information through dispatch and schedule information, and eventually, this data will be made public. The second step involves developing a viable countdown clock implementation. With 132 more stations, nearly 80 more route miles and over 104 more peak trains in service (317 vs. 203), the B Division is much larger than the A Division. We’ve waited this long; what’s another five years?
Over the past few years, I’ve wholeheartedly embraced the MTA’s countdown clocks. Despite a seemingly interminable wait for technology that leading international subways have enjoyed for years, Transit finally figured out how to introduce a modern technology into its 100-year-old system, and now we never have to guess when the next 1, 2, 3, 4, 5, 6 or L train is coming. But what of the rest?
While the lettered lines are still years away from a countdown clock solution, one sliver of Queens is getting something resembling next train information today. As the Daily News first reported, five stations along the BMT Astoria Line — 39th Ave., 36th Ave., Broadway, 30th Ave. and Astoria Blvd. — will soon enjoy the MTA’s next-train announcements. These are audio messages broadcast into each station that proclaims a train one or two stations away. Decidedly low-tech, they allow passengers some measure of relief, but I’ve never been too convinced of their utility.
The system that will go live today in Astoria is the one in place at a few other stations. The BMT platform formerly known as Pacific St. has these announcements, and the IND level at Columbus Circle enjoys this system too. It’s not the most useful though. As Donohue notes, the audio announcements will not specify whether the next train is an N or Q, and it’s unclear how much advanced warning these systems give. As Queens riders note, it’s better than nothing.
My problem with this system is the lack of information. As opposed to offering something useful, the MTA here is providing a service that doesn’t deliver the key information. What train is arriving is equally as important, if not more so, than when that train is arriving. At Pacific St., the announcements simply talk of an arriving local or an express train one station away. That’s fine if you don’t care what train you’re taking, but except for Herald Square-bound passengers, everyone else wants to know if the next train is a D or an N. Columbus Circle suffers from the same problem. I want to know if a C or B is next because I need one and have no use for the other.
In Astoria, that problem is mitigated a bit. Most riders who board in Astoria don’t care if an N or a Q is next. Few of them are heading to the reaches of Brooklyn far from Queens where the N and Q diverge. It will be a relief for riders whose only way of trying to guess where the next train is involves peering down the elevated tracks. Still, these announcements can end up as noise pollution if they’re warning only of trains one or two (visible) stations away.
Meanwhile, according to the MTA, a countdown clock solution for the IND and BMT subway lines is still three to five years away. That’s a long time to wait, and I’m glad my nearest subway lines have countdown clocks. From the Subway Time API functionality to the in-system clocks, this technology has made waiting more tolerable and trip-planning easier. When these — and not just audio announcements — are available system-wide, the age-old New York complaint involving endlessly waiting for the subway may just go up in smoke. For now, though, the next Manhattan-bound train will be two stations away.
For those jonesing for transit directions on Apple’s iOS platform and not too keen on Google’s full-featured stand-alone Maps app, Samuel Vermette’s Transit app, now available for free, can help full the void. With the 2.0 release out this week, the app features real-time data, offline access and travel packs for those who venture outside the cozy confines of New York. It also comes with a context-aware feature that remembers recent travel routes.
Vermette approached me a few weeks ago after I ran my thoughts on the ideal transit app, and his latest release covers my initial request for real-time tracking better than any I’ve seen. It pulls countdown clock data from the MTA’s subway API and bus tracking from the BusTime API. He informs me that they plan to add above-ground entrance location data and real-time service changes in future releases.
For the past few weeks, I’ve been using the beta version of the app, and the 2.0.1 release is now far more stable. What I like about this app is that it works. It’s intuitive to use, very graphical and definitely worth a spin. An Android version is in the works as well.
A thought experiment, if you will, based on the following question: What elements would the ideal transit map contain?
Over the past few years, the MTA has embraced, with varying degrees of success, a mantra of open data. It began with Jay Walder and has continued since his tenure as the MTA has released a whole bunch of information to the public. Some of it, such as turnstile data, helps us visualize ridership patterns while others — BusTime and SubwayTime APIs — help riders track buses and trains in real time. Even as a report from the Permanent Citizens Advisory Committee to the MTA rightly criticized the agency for shuffling its feet on issues such as searchable board PDFs and the like, the MTA has improved in leaps and bounds since early 2009 on open data.
Still, transit apps are rather limited right now, and the MTA, not the best at designing things, has tried to encourage private developers to pick up the slack. This past weekend, the agency along with AT&T hosted a hack-a-thon. It’s part of a long-term effort to reward app makers using MTA data, and as this weekend’s winners walked away with a concept and few thousand bucks, the summer’s winners could earn as much as $40,000 when the dust settles. That’s not chump change for a transit app.
As a sponsor for Capital New York, AT&T filed a puff piece from the hackathon if you want a sanitized version of the experience. Meanwhile, a few developers took home smaller prizes this weekend. Earning $5000 were the creators of Subculture.FM, a web-based app that allows straphangers to identify their favorite subway musicians, find them in the system and buy songs via a QR code. A real-time tracking app called MTA Sheriff took home $3000. It allows riders to submit reports on subway conditions. The third place winners were Accessway, an app that assists visually- or mobility-impaired riders in navigating the subway.
Of that group, the third place winner likely has the most utility. It serves a legitimate, non-frivolous purpose and is seemingly missing from the marketplace right now. Disabled passengers have a tough time getting around the system as it is, and the MTA doesn’t go out of its way to aggregate its accessibility information in an easy-to-find and easy-to-digest format. Still, it’s potential reach is limited by the number of users who need the information.
To me, it seems as though app developers are spinning their wheels a bit. An app about Arts for Transit performers, while kitschy, is hardly going to improve or impact my commute, and that’s what I want from a transit-based app. I need something with information that helps me make decisions and streamlines my ride.
That said, I see the best transit app as offering up the following:
- Real-time train tracking. Admittedly, this is limited by the fact that the B division has no countdown clocks. Add the BusTime API, and this theoretical app is even better.
- Above-ground entrance locations. I can never remember where the nearest Wall St. and Fulton St. entrances are. Show me staircase location as the MTA’s neighborhood maps do, and add Exit Strategy’s staircase location as well.
- Point-to-point directions that incorporate up-to-date service changes.
As far as I’m concerned, anything more is just window dressing. But that’s just my personal preference, and it’s a bit utilitarian. So what do you think? What goes into your ideal transit app? Maybe I’m missing something, but maybe, in an age of ever more complicated devices and apps, we’re just overthinking it.