Wednesday, December 28, 2011

Metro-North's "Passenger Pledge"


Never let a crisis go to waste.  With that philosophy, the CT Rail Commuter Council has turned last July’s stranding of a train full of desperate passengers into something which will benefit every rider of Metro-North:  “The Passenger Pledge”.

That incident, on the hottest day of the year, showed several failures on the part of the railroad… poor communications, lack of coordination with first responders and the need for better training of conductors.  While the railroad has taken the first tentative steps to remedy those problems, The Commuter Council wanted to go further.

At the suggestion of State Senator Toni Boucher, in August the Council drafted a “Passenger Bill of Rights” enumerating what passengers should expect in exchange for a ticket.  Some of those “rights” seemed pretty obvious… heat in the winter, AC in the summer, lighting and clean restrooms.  We even dared to suggest that every passenger should get a seat, a concept quickly rejected by the railroad.

CDOT (which hires Metro-North to run our trains) also rejected our call for refunds or credits for weekly and monthly pass holders when service was cancelled and alternative busing was not provided.  Impossible, said the state!  We’ll see.

But over five months of negotiations with Metro-North and CDOT, we did hammer out an important, precedent-setting document, merging our “Bill of Rights” with what Metro-North called a “Passenger Pledge”.

Among the promises from the railroad… timely communications when service is disrupted… moving stranded trains to stations so passengers can get off… maximizing available seating by equipment scheduling and conductor enforcement of one-passenger, one-seat rules…  railroad employees should be courteous and display name badges when on duty… and cars will be kept clean and safe.

These service pledges will be posted at stations and on trains for all to see, quite a concession from a railroad that has never before committed in writing to such standards.
Some on the Commuter Council were disappointed that we didn’t get all that we’d sought, but most felt that a compromise document that was 90% of our ideal is a major victory.  (I wish members of Congress could similarly compromise!)

The “Passenger Pledge” isn’t perfect.  And it doesn’t guarantee that there won’t be slip-ups.  But now we all know what the standards are and if they’re not achieved, we can discuss what the penalties should be.  (You can see the full Pledge on our website:  www.trainweb.org/ct)
So let’s greet 2012 with optimism.  The fares may have gone up and we only have a few more new M8 cars in service.  Winter will probably bring service cuts.   But we finally, for the first time in the 25+ year history of Metro-North, have a written pledge of customer service.

Wednesday, December 21, 2011

Finally found the fastest way to do chrissy shopping, give yourself 30min and limit yourself to one street of shops in town!! In tassie this makes life even easier because our streets are so short!!



Anyway within my allotted time frame managed to find an ice cream maker, board shorts, face and cream, beach towel, gym cloaths and polo shirts, the best part had most of them gift wrapped thanks to gold coin donations for charities, great initiative.



Time for a massage to recover from the mornings TT session and my 30min of shopping madness!!



Cjw

Sent from my BlackBerry® wireless device

Saturday, December 17, 2011

Stupid Programming Tricks #9

Keeping it G-Rated

I have a focus problem – no, that’s not the part that is G-Rated.  My focus problem is that I jump around so many technologies I sometimes tie myself into knots trying to figure what should be, and maybe are, simple things.  No, that’s not bragging, more like an expression of frustration.  But it’s all fun, right?  Right?  My hat is off to those who find this stuff easy, ‘cause that for sure ain’t yr. obdnt. srvnt.

So with the warning to myself to keep both the whinging and the cursing to a minimum, let us proceed with an ODI Stupid Trick.

Going faster miles an hour    

Oh dear, that version is NSFW.  But you have to give the Pistols artistic license.  And it’s a fairly good comment on how much this issue frosted my cookies.

So I am working on my Essbase Special Project using ODI 11.1.1.5 and all is going swimmingly, sort of.  I’m even doing it all in the Cloud.  So what?

I had a Procedure that logs process status to a table (too many steps for emails).  I wanted one of the fields to be appname.dbname with those values passed by #VAR_AppName and #VAR_DbName.  I had these defined as Alphanumeric variables, No History, with a default value initially of ASOSamp and Sample; I subsequently set these to blank because I wanted to assign them via a Load Plan.  In any case, these were set to Declare Variables in my Package and off I went.

The problem
Except that some of the Procedures that used these variables didn't change their value.  Odd.  I deleted the variables from the Package and readded them and regenerated the Scenario(s).  Nope, still stuck, actually, no, only one of them.  Huh?

The Stupid ODI Trick, and yes, it was just luck that I found it
After a lot of experimentation which I believe included scratching my head and rubbing my belly while typing (that's hard to  do with one’s nose but I managed it), I was just about ready to delete the silly things (this would  NOT have been a trivial exercise as they are used through the Project) when I came across this (unanswered) post on OTN’s ODI forum by Steve Truesdale:
https://forums.oracle.com/forums/thread.jspa?messageID=9973095&#9973095
Which then led me to these two (instructive) links:
http://public.sttruesdale.fastmail.fm/ODI%20Variables%20-%20with%20History%20-%20Prompt%20at%20Runtime.png
http://public.sttruesdale.fastmail.fm/ODI%20Variables%20-%20No%20History.png

Simple, right?  :)  Just like everything else in ODI.
Nuke the entire site from orbit, it’s the only way to be sure
Channeling my inner Ripley, looking at the diagrams made me think -- I can't get that !@#$ing variable (whoops, so much for the G-rating) to change its value -- what if I changed its type from Alphanumeric to Numeric or Date or Text?  One of those ought to be an illegal type conversion and make the value GO AWAY. 

And so it was.

Sigh. 

At least the variables value now in the Load Plan, just the way they ought to.  That was NOT intuitive, but at least it worked.


Quiet Cars Finally Arrive On Metro-North In Connecticut


More than ten years ago the CT Rail Commuter Council first proposed the idea of Quiet Cars on Metro-North.  They seemed to work just fine on Amtrak, first introduced in 2001 at the request of passengers. And other commuter lines across the US had also adopted the idea, usually to great acclaim.
For the most part, the rules are self-enforced by passengers.  Those whose phones start ringing are quickly reminded they are in the wrong car and they usually move.  There have been exceptions, including a celebrated case last spring on Amtrak when a woman was arrested for yacking for 16 hours on her cell phone and refusing to move from the Quiet Car.
But over the years Metro-North refused even a small trial.  The idea was summarily rejected by management as unworkable.  Conductors didn’t have time to police the “library like” requirements, they said (though they seemed to have no trouble enforcing no smoking, no feet on seats and other rules).  And passengers wouldn’t abide by the rules anyway.
Oh what a difference a half-decade can make.
Last fall the railroad finally decided to rollout a pilot program on a handful of trains on all three lines, the Hudson, Harlem and New Haven.  But the proposed test in Connecticut, involving only Danbury branch trains, was clearly flawed and was, to their credit, rejected by the CDOT.
Much to the railroad’s surprise, the Hudson and Harlem train trials (involving 32 peak trains) were a big success.  A November survey of 4388 riders in both “quiet” and regular cars, showed 90% customer satisfaction.  And 82% of respondents thought the program should be expanded to all AM and PM peak trains.
Best of all, the railroad admits there were “no significant operational issues”.  Wow.  Treat passengers like adults and they’ll act that way… even on the LIRR where another trial is underway.
The railroad promoted the program heavily (the survey showed 90% awareness) and rather than being confrontational with those violating the quiet rules, conductors just handed the offenders discreet cards explaining the program’s rules.
Those that wanted to use cell phones could still do so, either quietly at their seats or by moving to the vestibules for longer calls.  Groups traveling to the city who wanted to talk could also do so without the withering stares of those affected by their chatter.
Best of all, those seeking a little peace (and maybe a nap) could find the quiet car and be assured of, well, quiet.
Now the Quiet Car program is finally coming to Connecticut.  Starting January 9th, 18 AM and PM peak New Haven line trains (designated with a big Q on the timetable) will be testing the concept.  And Metro-North says if the tests go as well here as in New York, the Quiet Car plan could roll out system wide in peak hours on all trains come April 2012!
The railroad was wrong.  The people were right.  This is certainly cause for (quiet) celebration.

Wednesday, December 7, 2011

Two (no three) tips from Oracle Support

Introduction or who am I, anyway?

I like things that come in threes.  Perhaps my OTN handle should be “RD” instead of “CL”.

By the way, Rene Descartes had three dreams that drove him to pursue science.  FWIW, I had dreams (all too real) of working in a mainframe Adabas shop (that was subsequently off-shored) forever – I ran to the tender embrace of OLAP just as fast as I could.  I wasn’t always an idiot as a recent college graduate – just mostly.  As for what I am now I leave it for you to decide.  Good grief, what a digression that was.  Okay, the rest of this post is actually useful stuff.

Information Center

Would you like to have all of your EPM (and related BI) Support goodness wrapped into one package so you didn’t have to chase hither and yon, looking for specific articles?  How about a single location that’s even more consolidated than the Master Note Indexes and Oracle Advisors? What, you like searching through Support?  Uh-huh, you were only joshing me.  

There is now one single place to get:

And there’s more than the above, a lot more.  I think I could easily spend a month (or maybe more like a quarter) exploring all of the goodies on this page.

Pretty nifty, eh?  And how do you find this treasure trove, that is, by the by, updated every quarter?

Go right here to find out more:     
EPM and BI Support Newsletter Current Edition - Volume 2 : December 2011 (Doc ID 1347131.1)

ODI is left out, but there’s still great stuff for it

I’m working on a Special Project using ODI right now and it has been an interesting experience.  I’m pretty sure productivity in ODI = being beaten down by the product’s obtuseness, arbitrary nature, and just plain weirdness and then getting built back up by its awesomeness.  I guess it’s sort of like the Army’s BCT except we ODI developers don’t run around to a cadence march or yell Hooah!  I digress yet again. Regardless, ODI really is very powerful but anyone who doesn’t use it as part of his "normal" (can normal be used with me?) job can use all the help available.

ODI isn’t part of the EPM and BI newsletter, but here are three articles for you to obsess about.  What, you don’t do that when I post this stuff?  For shame.

There is a lot of good information in these notes – I wish I had known about them before I began my Journey of Pain that is ODI 11.1.1.5.

HTML rules, Flash, not so much

Oracle Support has this whiz-bang, super-duper web site full of all kinds of nifty interface functionality.  This is good.

If you are on a slow PC or a slow internet connection, it is S-L-O-W.  This is bad.  Do it on a laptop tethered to your mobile phone as an internet gateway and it is beyond slow.  Pouring molasses on a cold New England’s winter morn comes time mind as a barely-adequate analogy.

There is another way to get into Oracle Support’s web page and if you clicked on the above link, you’ve already experienced it – it is https://supporthtml.oracle.com.  All of the same great content, 100x (it is possible I am employing hyperbole to make the point, but it is fast) the UI speed.  What’s not to like?

And that’s it, for now

Yet again, Oracle Support does their very best to make our lives a little bit easier.  I for one am thrilled that this kind of consolidated information is making its way to us.  These products are complicated sophisticated and poor old implementation consultants like me need all the help they can get.  

I don’t know who in Support is responsible for supporthtml.oracle.com, but whoever that is – thanks, you are a life saver.

Monday, December 5, 2011

Winter on Metro-North


It may not officially start until December 21st, but winter is already on the minds of Metro-North and its 125,000 daily commuters.  We all remember what happened last year with bad storms, train breakdowns and a month of reduced service (fewer trains and fewer cars).
Well, though I can’t forecast the weather I can safely predict another tough winter for the railroad and its passengers.
I honestly believe that Metro-North wants to run an all-weather railroad and does all it can to prep our aging fleet of 40-year-old cars.  But the old cars’ poor design probably means that more break-downs are inevitable.
We don’t have enough diesel train sets to come anywhere close to being able to offer full service if the old MU (electric) cars freeze up again.  And we’ve only received 56 of the 405 new M8 cars ordered years ago, so those few train sets will be of little help if our 300+ older cars can’t run.
And the M8’s we do have on hand have yet to be run in nasty winter weather, so fingers-crossed when they’re sent out in their first blizzard.
So what’s Metro-North’s plan for the months ahead?  In a nutshell, lower your expectations and hopefully exceed their few promises.
Rather than try to run in bad weather, Metro-North is warning ridersnot to expect full service when the snows come.  I think this move is wise, if unfortunate, given the realities of our ancient fleet.
It really makes no sense to run the old MU cars if we all know they may freeze up mid-run, stranding passengers in dangerous conditions.  Though the railroad has done all it can engineering-wise to fix them, the cars were poorly designed and still ingest snow into their electronics bays where it melts, short-circuits the train’s electronics, then refreezes into a giant block of ice.
So expect reduced or potentially cancelled train service if the weather is bad.  Make your plans now to stay with a friend or relative if you’re trapped in the city, or work from home if the morning trains don’t run.
When the forecast looks bad, check for updates on the MTA website, Clever Commute and through local media.  (The CT Rail Commuter Council tweets the latest @CTRailCommuters on Twitter.)
There will probably be better rail service than the railroad is warning, but it will be nowhere close to the full service we enjoy in good weather.  What trains that do run will be packed and will probably be late.
By this time next year we should have a hundred additional shiny new M8 cars, which have been designed to withstand the worst Mother Nature can dish out.  If they live up to expectations, this winter may be the last where we have to worry about winter train service.

Popular Posts