The Five Biggest Lies About Highway Tolls

Like it or not, get ready to pay tolls on our Interstates and Parkways.  Transportation officials in Hartford say there’s just no other way to raise badly needed money for over-due infrastructure repairs.  Tolls may not be popular, but neither are collapsing bridges.

In the last decade’s debate on highway tolling, here are the five biggest lies that opponents have used to stall the return of highway tolls:

1)    The Federal Government Won’t Let Us:  Also known as “We’ll have to return millions in federal funding”.  Not true, as US DOT officials told us at a SWRPA-sponsored meeting in Westport years ago.  The federal government regularly allows tolls to be used as traffic mitigation and revenue raising tools.

2)    Our Highways Should Be Free:  So should ice cream and donuts.  Nothing is free, including the cost of repairing I-95 and removing snow from the Merritt.  Gasoline taxes come nowhere near to raising the needed revenue. Driving is a privilege, not a right. It should come with a cost.

3)    Tolls Will Slow Traffic:  It’s not 1965 anymore.  Tolling doesn’t require highway-wide barriers with booths and gates.  Just look at the NJ Turnpike or Garden State Parkway, where barrier-free tolls using EZPass allow you to pay at 55 mph.

4)    Tollbooths Cause Accidents:   See #3 above.  This happened once, 29 years ago, in Milford, and was used as an excuse to end tolling in the state.  If toll barriers are unsafe, why don’t fiery truck crashes happen daily at the hundreds of other toll barriers around the US?

5)    Highway Tolls Will Divert Traffic to Local Roads:    This may be true, for about the first week.  If people would rather drive for free on the Boston Post Road than pay 50 cents to save an hour by taking I-95, let ‘em.  Few drivers are that cheap, or stupid.

Trust me, I know about tolls and toll booths. I spent three summers in college working as a toll collector on the Tappan Zee Bridge.  The toll was only 50 cents to cross the mighty Hudson, but people still didn’t like paying it.  (Today the toll is $5).

Connecticut pioneered toll roads as early as the late 18^th century.  But today our state is facing billions in over-due bridge and highway repairs.  And federal aid for transportation may be cut from $469 million to $301 million. So why are we in this current mess?  Who’s to blame?  Us! 

We’re the ones that stupidly pushed CT lawmakers to cut the gas tax 14 cents a gallon in 1997.  And we’re the ones making it political suicide for legislators today to say they support tolls, even though they know tolls are inevitable.

Pick your poison:  “free” driving on pothole-filled highways with collapsing bridges… or pay a few bucks for a safe, speedy ride.   I vote for the tolls.

Where oh where have I been and why oh why would you care?

You may have noticed that I haven’t updated this blog in a long time, nor have I been feeding my obsessive need to be on OTN/Network54.  And you likely didn’t care, but I’ll tell you where I’ve been regardless.  :)

I and 12 other happy souls have been writing a book for the last six months.  No, not a book about coffee, or obscure French cars, or my imaginary service in the RAF (my callsign, if I had one, is Biggles 1 and in my imagination I fly this).  Instead, we have written something that I think is going to set the Essbase world on its collective ear – the first advanced topic Essbase book:  Developing Essbase Applications: Advanced Techniques for Finance and IT Professionals.  

No, you can’t buy it, yet, as it just went to the publisher as a first draft.  I hope it will be available by KScope12 but it will likely be available by Oracle OpenWorld.  We’ll see – this is the first book I’ve ever written and I have no real yardstick to compare times, effort, etc. against.  Yes, it has been quite the learning experience.

Again, who cares?  Why would I read this book?

You’ll read Developing Essbase Applications because:

• That advanced topic orientation I talked about.  For the time being, you’ll simply have to trust me on this, but I am quite confident that you will find this book interesting.  Nope, I take that back, you will find this book revelatory, revolutionary, and amazing.  Hype, right?  I don’t think so – there is content in this book that exists nowhere else.  Some of it will blow your mind – really.  We’ve peer reviewed this beast and have received very positive feedback.  We’ve also gotten back the comments, “Wow, that’s really hard/amazing.  How did you guys figure that out?  I thought I knew Essbase and I didn’t know that.”  This is not a beginner’s book.  I’m not even sure it’s a midlevel developer’s book.  There’s Good Stuff inside the covers.
• A good practices approach.  We’ve seen bad Essbase implementations.  We’ve (long, long ago) even been responsible for bad Essbase implementations.  The lessons from those bad systems were absorbed and the bad practices assiduously avoided.  Instead, we show you nothing but the right way to do Essbase.  Our internal motto during the writing of this book was, “We love Essbase and hate to see it done wrong.”
• We do more than just tell you how to do something, we tell you why.  It’s like having a team of seasoned consultants in a book and they’re 100% dedicated to knowledge transfer.  More than a few people in on the secret have said, “Are you telling the world too much?”  If there was a finite amount of Essbase knowledge out there, then yes, maybe I’d be worried about writing ourselves out of a job.  Happily, Essbase is alive, well, and growing.  Making you grow is Developing Essbase Applications mission.

I am ever so slightly interested.  So what’s in it?

Developing Essbase Applications covers every area of advanced Essbase practice there is:

• Essbase infrastructure
• Data quality
• Essbase Studio
• BSO in depth
• BSO to ASO conversions
• Designing ASO for performance
• Practical MDX
• Essbase Java API
• Automating with Groovy
• Advanced Smart View
• Implementing and administering Essbase

Who wrote the book?

An excellent question and oh how I do love writing these leading questions.  See if you recognize any names:  Dave Anderson, Joe Aultman, John Booth, Gary Crisci, Natalie Delemar, Dave Farnsworth, Cameron Lackpour, Michael Nader, Dan Pressman, Robb Salzmann, Tim Tow, and Angela Wilcox.  Jake Turrell edited.  Many more people contributed with their edits, comments, and ideas.  This was the group project to end all group projects and I am obliged to each and every one of you.

So you’re just one of 12.  What’s the big deal?

I was the editor in chief of this project.  What does that entail?  An editor in chief, at least within the context of this book:

• Lands the publishing contract.  The Oracle ACE program helps.  No, this is not an endorsement of the book by the ACE program.  Oracle wants ACEs to write and they provide the all-important introduction to publishers.  
• Handles all of the legal issues.  I now know more about copyright than I ever wanted to.
• Project manages the writing.  I  will freely admit that project managing this large a group of what are essentially volunteers (yes, we are getting royalties, but split that 13 ways and figure the number of hours and it’s pretty close to volunteerism) was challenging, to say the least.
• Helps edit each and every one of the chapters along with Natalie Delemar, Dan Pressman, Angie Wilcox, and Jake Turrell.
• Writes a fairly awesome (ahem) chapter on data quality.
• Lives, breathes, eats, sleeps, and anything else you can think of nothing, but nothing, but this book for the last two months.  

The writing process has been exhilarating and exhausting.  I’m happy to have done it and equally happy that it is finally over.  I need to go find billable work.

So what’s next?

I and my fellow coconspirators will keep you up to date with more information about Developing Essbase Applications as it gets closer to actual publication.  Like I wrote, we aren’t exactly doing this for money.  We wrote it to drive the art of practicing Essbase further, much further.  So think of the drip, drip, drip of news about this book as a service, not a marketing campaign.  ;)

We’re tremendously proud of what we’ve written and think you will find it tremendously valuable.

Congress to Commuters: "Drop Dead"

Back in 1975 when New York City was teetering on the brink of bankruptcy, then- President Ford declined to offer help and the NY Daily News’ headline screamed “Ford to City: Drop Dead”.

Well, last month the US Congress said about the same thing to us users of mass transit.  In their quagmire of inaction, bickering and partisanship, they let expire an important tax benefit to commuters:  whether you drove or took mass transit, you used to be able to spend up to $230 a month in pre-tax dollars to fund your commute.  But by not acting to extend the law, that benefit dropped to $125 a month for riders of mass transit but increased to $240 a month for drivers’ parking expenses.

What?  Commuters who ride the train / bus /subway get screwed but drivers get a benefits hike?  Yes, friends, it’s all true and you have Congress to thank.

This isn’t a red-state / blue-state issue.  I see it as a “gray state” victory, the gray states being those paved with asphalt that have scorned mass transit.  Meanwhile, big city riders of the rails get penalized.

There’s something egalitarianabout mass transit… millionaires riding in the same smelly Metro-North cars as blue collar workers.  People of color actually mingling with white folks!  It’s like we’re all in this together, sharing space, giving up our individual liberties (smoking, singing, traveling exactly when we want) for the greater good (less highway congestion, air pollution, saving money).

People in the gray states don’t understand that.  Theirs is a culture of selfishness:  my car, my space, my right to travel where I want and when, to heck with you.  Oh yeah, and the right to have free parking (or at least subsidized, as under this bill).

Connecticut commuters welcomed the New Year with a 5.25% fare hike on Metro-North (with similar fare hikes to come the next two years), thanks to the Malloyadministration seeing rail riders as an easy target for “revenue enhancement”.  So losing this federal tax benefit is just adding insult to injury.

The Federal government doesn’t do much in terms of our commuter rail.  They didn’t pay a penny for the new M8 cars.  They don’t set the fares, determine the station parking rules or set the timetable.  All of those are state functions.  (Sure, the feds did kick some Tiger III grant money to Stamford for station work, but aside from that, nada.)

That’s why Senators Blumenthal and Lieberman are trying to restore this federal taxbenefit, the one thing they can do to help us commuters.  They’ve been flooded with angry letters.  Their bill (S-1034) has 10 co-sponsors but so far hasn’t won support from their colleagues who matter, Senate Finance Committee Chairman Max Baucus (D-Mont.) and Ranking Member Orrin Hatch (R-Utah).  Not a lot of commuter rail in Montana and Utah, eh?

Time will tell if Congress can fix this mess.  I’m not optimistic, despite the best efforts of our Connecticut delegation.

For more information  on what you can do, visit this website.