[vox-announce] Comments to CPR supporting Open Source needed! (deadline: 30 Sep.)

Henry House hajhouse at houseag.com
Tue Sep 28 09:24:46 PDT 2004


If you want to see open-source software in our State government, I
urge you to express your support in written form and submit it to the
California Performance Review. Submission instructions are here:

<http://cpr.ca.gov/feedback>

You are free to base your letter on LUGOD's letter, which you can see in our
CPR meeting report here:

<http://lists.lugod.org/pipermail/vox-outreach/2004-September/001048.html>

BACKGROUND

The CPR report contains a subsection recommending that state agencies use
open-source software where feasible in new projects and new contracts. It
reads in part:

   Each year the State of California spends millions of dollars on software,
   software maintenance and renewal. Many private and governmental
   organizations are turning to open source software as a cost-effective
   alternative to closed source software. The state should more extensively
   consider use of open source software, which can in many cases provide the
   same functionality as closed source software at a much lower total cost of
   ownership.

	[...]


    A. For potential immediate savings, departments should take an inventory
       of software purchases and software renewals in the Fiscal Year
       2004-2005 and implement open source alternatives where feasible.

    A. Incorporate open source software as a viable alternative to any
       software procurement.

   Today, when state agencies purchase software solutions they are required
   to look at best value, and often go through a formal procurement process
   wherein vendors submit proposals. Since open source code solutions do not
   fit the traditional procurement model in that there is not usually a
   vendor promoting and proposing the product, it is recommended that state
   departments actively research and evaluate open source code alternatives
   prior to considering use of the traditional procurement model for
   software.

	[...]

   Fiscal Impact
   
   The recommendation to inventory software purchases and software renewals in FY
   2004-2005 and implement open source alternatives where feasible should have no
   immediate fiscal impact. Agencies participating in this review could fund any
   minor cost from their existing budgets.
   
   The fiscal implications for the use of open source software can vary widely
   depending how deep an organization is willing to use these technology solutions
   and whether they are used at the desktop, server or other installs. Savings
   could range from several hundred thousand dollars to millions. As listed above,
   FTB realized savings of more than $300,000 on one software installation. The
   Department of Transportation realized nearly $300,000 in savings on one
   application. Also, as software licensing and application development costs
   continue to increase, organizations are looking at creative ways in which to
   manage those costs. Looking to the open source community for applications that
   serve the same function as closed source solutions may cause vendors to be more
   flexible with pricing and licensing structures. Because these savings will
   depend on individual agency actions, however, the savings resulting from this
   recommendation cannot be estimated.



http://report.cpr.ca.gov/cprrpt/issrec/stops/it/so10.htm

--
Henry House
Please don't send me HTML mail! My mail system will reject it.
The unintelligible text that may follow is a digital signature.
See <http://hajhouse.org/pgp> to find out how to use it.
My OpenPGP key: <http://hajhouse.org/hajhouse.asc>.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://ns1.livepenguin.com/pipermail/vox-announce/attachments/20040928/770440cf/attachment.bin


More information about the vox-announce mailing list