Challenge to Transfer IT Power in MA
Andy Updegrove writes "Linda Hamel, the General Counsel of the Massachusetts department that is struggling to establish ODF for state use, has prepared a challenge to those in the State Senate that would strip State CIO Peter Quinn of his power to set IT policy. Her analysis graphically describes why a task force of political appointees has no business telling more than 2000 IT professionals what to do."
While its obviously not the whole story, this move does have all the classic fingerprints of a sourcing effort shooting for savings through leveraged negotiations with vendors. With control of all the
"(1) procurement policies by commonwealth agencies, constitutional offices, and other government entities concerning computer hardware and software, cellular telephones, personal data accessories, and other information technology devices"
the single office in charge of contracting can force standardization and negotate discounted contracts. Combine that with implied savings from standardization of technologies and resulting reduction in support costs and you get a nice presentation at the end of the year that you can show all your bosses showing you saved the state $X million. With that level of spending the $X is going to be a mighty big number.
If its not something like that then somebody better make very sure any contract signed is arms length - the next most obvious rationale would be lining one's pockets.
The last time I was in an IT position as a developer/data analyst at a fortune 100 company, myself and the other memebers of the team kept saying, "Hey ******, things are technilogically bad here, and the IT department agrees, we really need to step things up and make the following 5 changes: ", (then we listed 5 boring, but neccessary changes).
So after that, ****** decided to hire a team of IBM consultants to determine what the real problem was. They promptly had a meeting with us, where we shared our 5 changes that needed to be made, and were told a week later that IBM came up with 5 amazing outside-the-box changes to turn the company around.
A year and a half later, I'm at a different job where I make the decisions, and ****** is in the same position they were before, with more and more money being poured into consultants while the IT professionals remain unheard.
And, just another warning about IT professionals: I had a boss once that refused to allow me to install a Linux-based webserver, and instead poured over $800 into software simply to run IIS. It took a few weeks to get the software in, another week to get it configured, and yet another week to lock it down tight and get the file permissions to run properly. (keep in mind IIS kindly ignores windows file permissions on a fairly random basis, at least from my experience.) Now that that IT Professional has left to do ASP development elsewhere, I spent 3 days learning how to set up a linux webserver and lock it down, and 1 day actually carrying out what I learned. It has thus far cost us nothing, and we have yet to get a virus.
IT professionals are the #1 target it seems for Microsoft donations, so its no wonder most are drooling over Microsoft Office software. Most individuals I've worked with (even the Microsoft Certified Developers) have chosen Open Source solutions this past year because of how much they've developed, and how easy they are to work with. Maybe we need a bureaucratic geek to make the decisions anyway, since the self proclaimed IT Professionals either aren't doing such a hot job, or don't have the power to make these decisions anyway.
One last bit of info: forcing the use of non-proprietary software for developing publically available documents should be federal law by now, IMO, and using proprietary software should be considered obstructing access to the public domain. Why not tear down the wheelchair ramps while we're at it? And if Microsoft is truly non-proprietary in their new XML format, then let's use that too, but don't side with a single vendor when a globally available standard is sitting there, free of charge, easy to implement, waiting to be taken advantage of.
Most for-profit vendors have always been just that, For Profit. Most Open Source solutions and free-domain solutions set forth by not-for-profit organizations have been just that, Not For Profit. If something isn't for profit, and isn't for political gain, then odds are it is strictly being developed for the betterment of society. I guess the honest question now, when confronted with accepting the logically obvious decision, is "Why start now?", to which I say, "To make up for lost times."
"Now the trouble about trying to make yourself stupider than you really are is that you very often succeed." -C.S. Lewis