Open Dialogue on Improving How to Do Business with the Federal Government 2. Procurement Rules and Practices

For all the contracts we had bid on, we were required to submit the proposals and revisions in multiple paper copies. This mandate delays the communication between us and the contracting agencies and it consumes a lot of paper. An electronic submission system can streamline this into a much more efficient and environmentally friendly process.

Many RFPs with an IT component require that the government own the code. This means a "build it" approach for ALL of these vs. buy it. Ok, Healthcare.gov has been discussed endlessly but this is still a good example. There was zero reason to build from ground up other than that I assume the procurement required ownership. Many modules could have been purchased from other vendors for this and MANY other procurements. ...more »

The most ironic display of waste in the federal acquisition system is multiple websites referencing the FAR. There needs to be one, and just one, government-run website referencing the FAR with all the benefits of the other sites.

Acquisition.gov/far can do the job of http://farsite.hill.af.mil/vffara.htm in addition to other FAR sites out there.

Poor requirements or a willingness to change requirements on the fly continues to waste taxpayers' money in IT projects. Surety bonds are used to guaranty performance of federal construction projects and should be used for IT projects. Although it is seen as a way to hold the contractor accountable, it can and should be used to hold the buyer accountable. Senior officials should require bonds and use them as a method ...more »