FBOpen & Procurement Tools — 18F Demo Day, 9 May 2014

Transcript

1. fbopen iteration 0 Aaron Snow | aaron.snow@gsa.gov
2. Problems in Procurement SoWs and SoOs are hard to write Opportunities are hard to find RFPs 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)
3. What should a business be good at? Why should it be easier?
8. How do we scale to many targeted marketplaces, each filled with relevant opportunities?
9. We can work with this.
10. 1. Thin API* server (nodeJS, expressJS; Apiary docs; api.data.gov) 2. Search-index all the opportunities (Solr, moving to Elasticsearch) 3. Download and index attachments (scripts) 4. Sample/pilot website fbopen pilot: design
11. APIs are how programs (and web services) talk to each other. *What’s an API? In 10 seconds or less.
12. 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>
15. fbopen search server
16. API ?
17. 1,750+ users have run 51,000+ queries top three sources: businessusa.gov (50%), fbopen.gsa.gov (25%), sbhub (8%) so far
18. wins • simpler, faster search • one-stop shopping • more touchpoints, wider exposure • reuse: architecture, code, design, ATO 18f.gsa.gov, notalone.gov, future • feedback and learning
19. pilot website: fbopen.gsa.gov API docs and examples: docs.fbopen.apiary.io all the code: github.com/18f/fbopen @fbopen