Skip to main content

TransLink rolling out Fare Gates

Translink will be rolling out new Fare Gates which automate the process of validating tickets. This a great initiative. In the article, it denotes that having this system in place will generate $4 million dollars annually. Let's be honest though -- $4 million at SkyTrain's scale (500,000 daily users) is chump change -- There's more tha. At best case, let's say 50% of the people in daily usage are 3-zone and out of the 50% we have 10% that are not paying for 3-zone bus passes and end up paying twice a day at $5 a ticket (2 ways).

250,000 * 0.9 * $7.55 ($151/20 work days assumption) = $1,698,750
250,000 * 0.1 * $10 = $250,000
Total = ~$2million revenue per day based on 3-zone daily users (best case scenario). These super rough numbers don't even count 1-zone and 2-zone. Based from experience on using the SkyTrain every work day even sometimes on weekends for the last 7 years -- There's no shortage of people coming from Surrey. I actually think most customers are from Surrey based on how packed it is during rush hour (7am to 9am and 4pm to 7pm).

Taking this even farther, I don't believe the goal for Fare Gates is to make the customer's transportation experience better -- it isn't to make their lives more easier, safer, or more comfortable. It is to ensure they can implement more automation and reduce the man-power (guards) required to keep the operation going. This is just what needs to happen to run at their scale. So the question I have is will reducing the number of guards at each station make customers feel more safe? I doubt that.

Let's think for a second and say TransLink lays off 1,000 guards. Let's also assume that each guard is about $100,000 per year (base salary, vacation, health insurance, sick days, etc). That's $100,000,000 in savings with a $20,000,000 investment in automation (FareGates). Furthermore, I'd like to describe my perspective as a daily user.

The fundamental problems (as a daily user of SkyTrain) are scale and safety. People think of TransLink as a fantastic way of getting between Surrey and Downtown Vancouver. It is; however, it comes with its own set of problems. Those problems include drug addicts / violent drunks causing problems on the train, civil disputes randomly starting, and gradual rising costs of monthly transportation passes.

I fully understand that when running a business, the most expensive resource in staying alive is the people. People are expensive. Moving forward, automation is the key to saving operational costs -- but I think that TransLink will need to be more vigilant than ever to ensure the safety of their customers and the scalability of the system as a whole. There are far too many people using SkyTrain during rush hour and customers need a way to feel safe and comfortable without costing an arm and a leg on monthly transportation passes.
Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.

Cheers,
Jaime

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:



Now, whenever you make a commit, it should show up like this in the log:



Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this



Want more emojis? check out the Emoji Mardown Cheatsheet!

NodeJS Hack Session: MMO Pokemon with NodeJS/WebSockets

The primary focus of this proof of concept is to determine how easy it is to build real-time web applications for all iPad, iPhone, droids, Safari, Chrome users on top of NodeJS (non-blocking event driven server side Javascript platform). The proof of concept was built within 6-8 hours including the following:

Uses Express framework for server side Javascript development (inspired by Rails / Sinatra / Django)Uses EJS for templating language (much like Django templates and symfony) -- allows partials and passing parameters into partials like symfony PHPReal-time chat using WebSocketsArena Queueing System for real-time competitive matchplay using WebSocketsHTML5 AudioCSS3 transitions for all hand cards, tappable cards, transparent panels, rounded corners, drop shadowsFallbacks for Firefox, IEFirefox/IE will fall back to Flash socketIE will fall back to XHR long poll if the user doesn't have Flash installedNoSQL CouchDB for fetching users and soon cards, achievements, friend associat…