San Francisco releases new software evaluation policy
COIT Software Evaluation Policy
Under the provisions of the City and County San Francisco Administrative Code, information resources are the strategic assets of the City and County of San Francisco that will be managed at the direction of the Committee on Information Technology (COIT). The COIT Software Evaluation Policy will require a standard, rigorous evaluation of the operational benefits and total cost of ownership of new software. The Software Evaluation Policy will require departments to consider open source alternatives, when available, on an equal basis to commercial software, as these may reduce cost and speed the time needed to bring software applications to production. (Open source software means that the underlying source code is not copyrighted and therefore available free of charge to read, modify, and build upon.) This policy is part of the Cityâ€™s â€œOpen SFâ€ project which is intended to engage our constituents in developing creative solutions to our shared challenges.
The purpose of the COIT Software Evaluation policy is to ensure that all departments thoroughly and fairly evaluate software alternatives, including open source prior to acquiring new software. New software means an additional software system or a complete replacement of an existing system, rather than an upgrade or modification to an existing system. COIT believes that a rigorous evaluation process will help departments make software choices that meet operational requirements, reduce costs, and possibly speed the time to bring software applications into production. The intent is that this process occur concurrent with existing procurement process and not add additional time to the procurement process.
The Software Evaluation Method or equivalent method must be used for all new software purchases over $100,000. COIT directs that the Software Evaluation Method or equivalent method be used for all new software purchases, including non-application software, such as databases, operating systems, web application servers. The Software Evaluation Method shall be available on the COIT website and will be developed and maintained by the Cityâ€™s Chief Information Officer.
Departments are responsible for completing the Software Evaluation Method or equivalent method at two possible junctures:
1. In cases where requirements have been established, but no software solution identified, the Software Evaluation Method or equivalent must be part of the evaluation of responses to a Request for Proposal or similar procurement vehicle; or
2. In cases where a software solution has been identified, the Software Evaluation Method must be applied prior to commencing a request for bids through the Technology Store or similar procurement vehicle.
The CIO will reject purchases that do not document that they have followed the COIT Software Evaluation Method or equivalent process.
The CIO will determine whether a department has made a good faith effort to consider open source software alternatives, and may reject purchases that do not.
The Performance and Planning and Budget Subcommittees will review each Software Evaluation as part of its oversight of IT projects.
New enterprise agreements for existing software used by the City are not considered a new software acquisition.
Exceptions to this standard can be granted by COIT upon request by department.
Approved by Resources Subcommittee: January 6, 2010
Approved by COIT: January 21, 2010
Effective Date: February 1, 2010
Every day I get to engage with entrepreneurs, public sector innovators and journalists on re-imagining and re-energizing how government works, what it means to be “civic,” and this year has been an incredible one for many friends and colleagues.
I’m always inspired talking and working with entrepreneurs trying to solve big civic problems, especially those who realize much of the challenge lies within modernizing and empowering internal government operations, so it was great to finally meet with Govtech Fund Founder and Managing Partner Ron Bouganim this week.
The 18F Delivery team released a “Partnership Playbook” that aims to help federal agencies understand what to expect when working with 18F, and the gem within is play number two, “We work with an empowered product owner.”
Citizens simply glaze over when they are confronted by a sea of large numbers with many zeros. These figures need to be relatable to the person reading the data. Otherwise, open data is just more data that dies on the vine.
The U.S. Department of Veterans Affairs released a beta version of Vets.gov, and it’s the future of federal government digital development.
The Welsh Government released a report of its findings on how local government in Wales can better leverage digital technologies and realize significant savings while still providing quality, scalable citizen services.
A California bipartisan oversight committee, the Little Hoover Commission, has issued recommendations on how the state can bring a more customer-centric government to residents and visitors.
Seneca Systems CEO Chris Maddox shares the inspiration behind the new constituent relationship management system, Romulus.
“No ugly, old IT” jumped out at me when I first reviewed DataSF’s strategic plan, “Data in San Francisco: Meeting supply, spurring demand,” and it still sticks, mostly because someone inside government was so bold as to make this a priority and openly communicate it and also because this should be a mantra for everyone building civic technology.
Enabling internal government tech shops to quickly stand up applications in a secure testing environment is fundamental to quick prototyping, and 18F’s new Cloud.gov is a major step in realizing ultimate IT flexibility.