Voters News Service: What Went Wrong
ddtstudio writes "Baseline Magazine has a pretty good recounting of how even the national TV networks can have a computer network go wrong -- in this case the night of the last U.S. election. From the article: "VNS had been trying to rewrite and retool the system for years. This was just the most recent attempt and it failed miserably."
Oracle, IBM, BEA Systems -- all crashed."
The systems in question were mainframe computers running IBM's Operating System 390.
Not that i'm a linux fanatic, just wanted you to get your facts straight.
... and one page version of article.
Quote from article: "Also, the networks would be unable to give the type of detailed explanations as to why voters voted the way they did this time around. For example, according to TV network analysts working the election, the networks wouldn't be able to tell viewers why particular demographic groups voted for specific candidates nor the issues that they considered most or least important when voting. "
:)
:)
So, what this means is that people were able to go late to the polls, and cast a vote free from the influence of network prognostication. They were able to cast a vote that they thought was right, free from the spectre of "throwing a vote" as the election had already been "called" by *INSERT NETWORK NAME HERE*. Boo Hoo to the networks. Wow...why the hell is this a bad thing???
Up until the 1960's, most US citizens were able to vote just fine, all by themselves, without the need for knowing why *INSERT DEMOGRAPHIC HERE* people voted for *INSERT CANDIDATE NAME HERE*. Why does it need to be different today? There's already enough blather on TV, if we could eliminate it from just one night every 4 years....oh man, that'd be sweet!
Of course, I won't know because I'll be watching something that is entertaining, rather than a farce, on my TiVo!!!
All members, including 19 newspapers, shared in the management of the company and oversaw its $33 million operating budget for the current four-year election cycle.
Could the failure of VNS be the fault of having far too many PHB's droning on about mission statements and TPS reports?
"Alcohol, Tobacco, & Firearms" should be a convenience store, not a government agency.
Well, no where in the article is it mentioned that there was a problem with IBM and Oracle. It just says that there were delays in transferring data. So I don't know why Oracle and IBM were named in the original post.
What's under yellowstone?
From article:
Now, it does not mention what OS they were running WebLogic on in the article, but it was definately not OS/390.
Forget the whales - save the babies.
Java, Oracle, DB2, BEA - nope, those were symptoms of a deeper failure...
From the article:
Back up to Election Day, Nov. 5. The balance of power in Congress was up for grabs. Yet by 10 a.m., the TV networks confirmed what they had feared for months: They couldn't derive any meaningful exit-polling data from a system they had just spent between $10 million and $15 million to overhaul.
That's 2002.
Who wants to start an open source project to replace this failed service. We'll use Linux, MySQL, Perl, PHP and Apache. Any takers?
Karma: The shiznight, mostly because I am the Drizzle.
OK Folks,
I'm one of the lead programmers of one of the members
We KNEW this was going to happen a LONG time before November. At the end of the article, they talk about "set a deadline 2 months ahead of the real deadline"
Guess what? They did!!! They were supposed to be ready for the NJ Primary, which was before the summer - they missed it, BIG TIME - That's when the alarm bells went into overdrive for me
I understand (This up in the levels above me) that the steering committee didn't realize that the technical committee was saying "We've got a BIG problem"
Another warning sign was when their test data generator that they sent us in the spring generated XML that didn't match their own XSDs - and that was with all the fields declared as cdata - the field names didn't match
The first test, which was supposed to be months ahead, came weeks ahead, and even the most basic message (just a heartbeat) didn't work. That's they day I knew it was doomed for sure. Our prime efforts switched to our backup data source at that time. THAT worked fine. I had a boring election night, watching VNS crash, and laughing
One stipulation: That the new system use more flexible and current programming languages--Java and the Extensible Markup Language-- rather than OS 390 to gather, compute and deliver data to the media outlets.
That sounds great. People who have no idea how to accomplish the goal telling the people tasked with doing it, how it should be done. I can't believe it failed. They should have laid out what they wanted to acheive and left the rest up to the designers on how to meet those goals...
Also, some interesting older information on the VNS can be found a the Votescam website. Although they seem to have a few extreme views, along with some wild conspiracy theories..
-- -- Warning. Do not stare directly at the sun.
"Oracle, IBM, BEA Systems -- all crashed!"
Doesn't that sound like a line from a bad disaster movie?
DIE HARD IV: DIE HARDWARE.
As someone who finally bailed out of an extremely poorly run company (WebMD) burdened with dumb management, it's easy to see the echoes.
The list on the last page of the article is nearly perfect, with one small addition:
6) Listen to your employees!! You hired them because you thought they were good at what they do. Why would you ignore their input into the process now?
Nothing in this article is the "fault" of the technology (Oracle, Java, IBM, Linux, or anything) itself any more than it's the fault of a head of cabbage.
It's just poor management.
One stipulation: That the new system use more flexible and current programming languages--Java and the Extensible Markup Language-- rather than OS 390 to gather, compute and deliver data to the media outlets.
Ah, yes. The programming language OS 390. Are there any O'Reilly books on that subject?
"I'd rather have a full bottle in front of me than a full frontal lobotomy"
the TV networks confirmed what they had feared for months: They couldn't derive any meaningful exit-polling data from a system they had just spent between $10 million and $15 million to overhaul.
.
Projecting winners and losers in various races would take several hours longer than in the past.
(sarcasm)
Y'know, it is truly a sad day when you can no longer count on the media to tell you what might happen and instead have to settle for what did
(/sarcasm)
To-do List: Receive telemarketing call during a tornado warning. Check.
Or make sure you know what kind of better hardware you could buy, if needed.
When developing a system you should try to overload it so you can recognize what a failure state looks like. This may give your engineers valuable insight.
What is the resource that gets exhausted first? What is the system's behavior when it is completely overloaded? Does it just stop functioning, or does it lose data? Or maybe generate bad data?
These things could be nice to know, and may suggest quick improvements so that, if 6 years later the customer puts in 20 times as much usage as was originally budgeted, the failure isn't completely embarrassing.
The "this" in question, the Voters News Service, is funded by news networks and newspapers, not the government. They use it so that they can provide as up to the minute information on voting results as possible, and so that they can provide in depth analysis of voter behavior.
I suggest volunteering to work at the polls, or to be a monitor of the polls. You're free to watch the entire process yourself. In hotly contested races, the various parties will send people down to monitor things themselves.
If you are absolutely convinced that the system is fraudulent, what are you doing about it? Might I suggest:
Your claim that our election system is rigged is extremely serious. If you seriously believe it, don't you owe it to yourself and your country to fight back?
Search 2010 Gen Con events