fbopen

iteration 0

Alison Rowland | alison.rowland@gsa.gov

Federal Procurement:

Why Care?

Source: USASpending.gov, totals are Grants + Contracts

FY 2012 $1.05T

2013 $ 975B

2014 $ 580B (so far)

Problems in Procurement

SoWs and SoOs are hard to write

Opportunities are hard to findRFPs are hard to understand

Bidding is onerous for vendors

The selection process is onerous for KOs

Awards can seem rigged against SMBs

Registering to get paid is hard (SAM)

core competency

>

finding and winning bids

Why should it be easier?

We can work with this.

1. Index all the opportunitiesSolr, soon Elasticsearch

2. Download and index attachments

3. Thin API serverNode.js/expressJS/api.data.gov

4. Lightweight web interfaceHTML/CSS/JS/Backbone

fbopen pilot: design

bids.state.gov

fbopen

search

server

(Elasticsearch)

fbopen

API

server

(nodejs)

api

.data

.gov

fbopen

web

server

● SSL by default

● 100% open-source

● component architecture reused for

18f.gsa.gov, notalone.gov, future?

1

2

FedBizOpps data

<obligatory tech architecture slide>

grants.gov

FBOpen

search

index

API ?

wins

● simpler, faster search

● one-stop shopping

● more touchpoints, wider exposure

● reuse: architecture, code, design, ATO18f.gsa.gov, notalone.gov, future

● feedback and learning

fbopen.gsa.gov

docs: 18f.github.io/fbopen

code: github.com/18f/fbopen

@fbopen