Slashdot Mirror
The Open Source Dilemma for Governments
Sam Hiser writes "Tom Adelstein, open source consultant and Member of the Open Government Interoperability Project ("OGIP") working group, offers another incisive article in which he discusses the costs in the terms of lives and dollars when local governments do not deploy open standards-based software for data sharing. Asks Adelstein, 'Can local governments afford to create redundant applications to meet new Federal standards for first responder alerts, emergency services, law enforcement, broadcasters?' He posits that Open Source collaborative initiatives may provide the only solution for the US if the people want to create a safer environment."
...is a big supporter of this sort of thing. Check them out here. The OSSI is chaired by John Weathersby, who seems to have a good handle on how to communicate effectively via standards, reports, certifications, and so on with folks in the U.S. government.
The Army reading list
If we want secure software, it has to be open source.. Granted, at the start the code quality of open source stuff is around equal to closed source stuff but the resources available to check code that is public are far larger than any closed source firm can muster.
Simon.
I don't care if the US Senate or House chooses to use MS Office or vi or whatever - as long as the documents they produce are of an open format (text, rtf, XML, whatever), and can be read by us Citizens (and others, why not?) wihtout needing to have a particular piece of software. Same can be said of exchanging data between various levels, types, and branches of government.
Don't blame me, I voted for Kodos
The Open Source Dilemma for Governments
by Tom Adelstein
January 04, 2004
If someone told you a hole existed in the competitive landscape for a large and highly addressable US market segment you would call them a niche miner. If I told you the cream of that niche totaled $56 billion and could be addressed in a three to five year time frame you might wonder how you missed it. Don't feel bad, it seems that the major computer companies have missed it too.
In a nutshell, the local government software market has not drawn large software firms. Also, independent software vendors (ISV's) have failed to adequately satisfy this market's needs as they lack the resources to serve the large geographical base. People have viewed this market as fragmented, requiring too much one-off customization with long sales cycles. Since the tragedy of September 11, 2001 those barriers and the poor economics of serving this sector have changed. You might call this a new opportunity.
What's At-Stake
Local governments must upgrade their computer infrastructures. That means additional taxes, levies and bond issues lie ahead. They could ignore their ailing systems and that means putting people's lives at risk. If the American public understood this problem one might see some intense interest at town hall meetings. If mayors and city councils really understood this problem they might panic. Perhaps some of us also wonder how much frustration US agency and department personnel feel as they hurry to make a bigger impact in a faster time frame and run into muck of local government.
An example of the problem local governments face exists on the website of the US Department of Justice - Office of Justice Programs, under the Global Justice Data Model http://it.ojp.gov/topic.jsp?topic_id=43. On that page, the authors write:
Approximately 16,000 justice and public safety-related data elements were collected from various local and state government sources. These were analyzed and reduced to around 2,000 unique data elements that were then incorporated into about 300 data objects or reusable components. These components have inherent qualities enabling access from multiple sources and reuse in multiple applications. In addition, the standardization of the core components resulted in significant potential for increased interoperability among and between justice and public safety information systems.
Many of those 16,000 fields contain the same type of information with a different naming scheme. For example, some databases use the field " name_first" and others use "first_name". Then you might find "firstname" or "givenname" or "given_name".
As you go through the local government databases, you find a myriad of schemes for everything from last_name to zip_code. Obvious, the nation's information stores contain massive redundancies. These redundancies make it difficult to share data and provide alerts.
So, add all the separate naming schemes of local government databases together and you get 16,000 variations. Create a standard and it goes down to 2,000. Put those into categories of reusable components and you wind up with 300 database elements. That's why they call it a standard. It allows disparate systems to work together. It starts to open the window of a manageable task when the interoperable elements number 300 instead of 16,000.
Non-Compliance Problems and Their Costs to You and Me
Recently, I received two requests to assist a local government and a university in the same area of deploying justice databases. The requests involved implementing a new, comprehensive application to provide services and a tracking system using a web-enabled database-driven application. The requirements of the applications seemed simple and with the use of the Global Justice Data Model, I estimated delivery within 90 days. In both instances, the people controlling those projects dismissed implementation of the standards-based model.
What should one do when government entitie
For pure niche apps (patrol car suspect lookups, etc), I would posit that small commercial companies are in the best possible position to provide support and apps, not the FOSS world - after all, where does your teenage A-Patchy Webserver hacker get his hands on the specialty hardware used in patrol cars?
by the UK goverment that they might "look-in" to open source software themselves simply because they know it scares Microsoft, like Germany, who got massive discounts.
/. stories on goverments considering OSS and then stories a few months later about them receiving massive discounts.
A goverment just has to say it's thinking about it to get Microsoft scared and giving out vouchers left right and centre.
Expect to see alot more
--- any post that takes longer than 20 seconds to write, isn't worth writing
Can local governments afford to create redundant applications to meet new Federal standards for first responder alerts, emergency services, law enforcement, broadcasters
No! With or without open source, we can't afford such nonsense.
This is another clear example of the overgrowth of the role of the federal government. They're going to run our local governments deeper into debt with these ridiculous unfunded mandates that may be wildly inappropriate for a given locality. The constitution clearly states the roles of the federal government and leaves the rest to the states and localities. This along with over-regulation of personal lifestyles that's going to come with public healthcare, are the biggest disasters on the horizon.
1)"Free" is not a good motivator - coming in under budget is not a motivator if they want budget they need to spend budget
2) it's too complex for SLG admins, it's not as easy to pass an open source torch on to your new team mate or underling.
what will motivate Open Sopurce Adoption?
those 400k novell seats and their admins that still run win9x and office 97 need an upgrade very badly. If Novell/SUSe and Ximian can pull off a compelling solution then you will see huga adoptions -- not these onsie twosie deals.
Mod me down if you like but this is a strong emerging market.
Sorry you need to update your version of Microsoft Office to 2003sp3 in order to report a child missing.
When timing is critical a commercial solution can fall flat on it's face.
As seen on Wired: Get a free desktop PC
Open source software plays a big role in many projects where I work, and our clients tend to be gov/mil related. While not all open source software is "good", you can't lump it all together and say it's "trash".
Comment removed based on user account deletion
The issues that this article brings up are similar regardless of whether commercial software or opensource software is used.
This article is really talking about standardization and consistency across government organizations -- a huge job.
Imaging thousands of individual offices who have operated in a certain way for a hundred years. Imagine all of the paperwork, homemade spreadsheets, interoffice memos that spawn secondary spreadsheets, etc. This unfortunately is how the US government works.
Now imagine someone coming in and promoting replacing whatever random assortment of tools is in use with opensource tools. This means retraining. This means new hardware. This means *A CHANGE*. Uh oh.
Is this the right long-term thing to do? Yes!!
Is this going to be easy? NO!
In order for this to be successful, it will have to have very important people behind it pushing it from the top down and funding the proper resources (hardware and people) where necessary to bring the government into the 21st century.
I for one, certainly hope it can be done, and it would be great for the US and the rest of the world (except Microsoft) if it can be done with opensource software.
There are much worse ways that software can fail. One of the worst is software that looks like it's working, but in fact is not displaying new / updated items -- this leaves the warfighter with the false impression of situational awareness. Another popular failure is software that has time-consuming processing steps that don't have adequate progress indicators -- this leaves the warfighter wondering 'Is it done yet?' when it hangs or fails.
At least with a blue screen or core dump, you know you've got a problem, and you can restart / reboot to resume, with a well known startup time.
We call it art because we have names for the things we understand.
The original Internet and Open Source standards came out of public monies mostly granted to university research departments by the Department of Defense. Who paid for those efforts? Why must the public have to pay for those technologies once again because companies like Microsoft adopt them and then resell them as proprietary software?
What the hell is he talking about? In the previous paragraph he writes:
If the Internet failed to follow accepted standards, it simply would not work
So the Internet works because it "follows standards", and we know MSIE (price: free) has the largest share of the browser market. So MS hasn't broken the Internet. Can someone give an example of what he's talking about? And don't tell me Kerberos because it's not the example you're looking for (MS did not co-opt it - MS extended Kerberos in accordance with the spec).
He started out reasonable and then got shrill. He throws out statements like, "Seventy-five percent of the municipalities and schools in the United States cannot afford proprietary software" So...that means 75% of the municipalities are either a) running OSS, b) using pen and paper, or c) pirating all their software. A source reference would have been nice.
Oh no...he has recommendations too:
the states should require the use of Open Standards and Open Source Software when applicable
When applicable? So, who decides when the software "applies"? Availability? Cost? (cost of development for a custom solution vs cost of COTS software) Everyone knows offshore development is cheaper - since he beats the fiscal drum so loudly does he also advocate sending any custom programming jobs overseas? He did have one good idea:
If we can pay for software one time and share it with all government entities, we empower Americans to participate in the security of the homeland.
Solution: site licenses for America!
Excellent, the first poster so far that appears to have RTFA.
The crux is standardization, or, for you DBAs out there, normalization across applications instead of databases.
One of the examples he gives talks about differing field names (last_name versus surname, for example). Well, sorry, but that has nothing to do with whether you're using SQL Server or MySQL and everything to do with standardizing architecture.
But how does one do that across an entity as large as a government? How do you tell programmers they must use only these field names? And how much will it cost to rename fields in existing applications, and ensure all the links, dependencies, etc., are rectified as well? It's not really anything to do with the platform; at the least, it doesn't have anything like the impact the author suggests.
An important issue, as the author says, is that for many applications (such as SAP and JD Edwards), no open source equivalents exist. This is a big problem for purchasers, because it makes them wonder how long open source will take to give them the applications they need (or if they'll ever come). They may have to pay big bucks for that other software, but it integrates with their existing applications and it's a known quantity. Never underestimate the power of familiarity.
And, although I hate to be a grammar nazi, the author might just find himself being taken more seriously if he learns how to use words properly.
the problem lies not government "per se" but with the management thereof.
The same government that you are railing about is the reason nobody's dying in low speed head-on crashes from getting a steering column rammed through their chest.
The car companies were quoting "market forces" and "nobody will want to pay for collapsible steering columns," and people were pinned to their seats like butterflies to cardboard. Sound familiar? Its the justification of every elite to anything that's going to cut into sl/easy profit.
Management of government by objectives without citizen input into what the objectives are is disastrous.
Remember Clinton's medical plan fiasco that was thrown out, not by elected representatives like the congress, but by HMO lobby groups posing as experts, as being unmanagable.
You didn't get to register so much as a peep for or against or make a suggestion. It was managed right out of your hands.
People are dying because their only sin is being temporarily broke from the last scrape with the health care system.
MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
The costs of development would be borne once (quite likely whatever software they'd need has already been done by some community or other,) and used as is and/or modified under the GPL, and copied into the pool.
Some existing body, like the GAO, could administer the pool and send CDs to any community, state or federal department that would require the software.
MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
If someone wants the government to use their software then their software must be capable of saving to the government standard GPL format.
Government documents will always be accessible.
Goverments will be free to switch software and not worry about format incompatibility.
They can choose to use the best software for their formats...free(dom) software or proprietary.
The playing field will be leveled. No document lock. A software package will compete on its pricing and merits.
Chances are all of these benefits will transfer to the private sector as the sheer volume of government documentation will force the inclusion of government standard gpl formats into software made for the private sector.
As a bonus the GPL will get a shot in the arm as far as legitimacy go.
The government formats will also spread and be improved being GPL as anyone will be free to use or change it.
If the government sees a nice modification they can make it the standard.
Steve