To folks new to government, one of the most surprising differences between our work and work in the private sector are the barriers in accessing commercially available software, and commercially available Software-as-a-Service (SaaS) in particular. There are good reasons for these barriers: the government places premiums on considerations such as security, privacy, accessibility, license management, and competition. It takes great care to work within those considerations while also providing digital teams with great tools to get work done.
V. David Zvenyach
18F is an open-source team. We currently have hundreds of publicly available repositories, with dozens under active development. We’ve had numerous contributions from colleagues within government, and contributions from members of the public. But in the next few weeks, we are going to run an experiment: we want to contract for contributions. And we want to do it the 18F way. What’s the experiment? Specifically, we’re going to use our “micro-purchase” authority.
In January, 18F Consulting announced a new kind of process for vendors to compete for software acquisition contracts. The Agile Blanket Purchase Agreement (BPA) process would be open to existing vendors on Schedule 70, and require vendors to submit a working prototype based on a public dataset—and then show their work in a publicly available git repository. A number of decision factors led to the request for information (RFI) and then the request for quotation (RFQ).