(Byline: Mary Davie, Government-wide IT Category Manager)
I recently met with more than 50 representatives from the top IT services companies and talked about the good and the bad in federal acquisition. Some of the discussion was surprising … some not so much. The key takeaways include some changes that are fairly simple for government to implement, yet have big impacts.
1. Government acquisition and program personnel need to be more accessible and increase communications regarding requirements and procurement timelines. Industry told me government program/acquisition personnel rarely respond to requests to discuss programs, requirements, and agency priorities in order to develop proposals and solutions or offer alternatives.
GSA’s Information Technology Category has made extensive use of RFIs, draft RFPs, industry days, one-on-one meetings (over 100 individual meetings on Alliant 2 and EIS) and collaborative platforms such as interact.gsa.gov for collaboration and input. I’ve heard many times from government reps that they don’t have time or don’t know how to handle sharing with multiple companies since sharing has to be handled equitably.
I’m here to tell you we have to find time to meet with industry. There are many ways to share information equitably. GSA spends an extensive amount of time communicating and collaborating to develop all of our governmentwide contracts to ensure we get as much input and feedback as possible. The governmentwide IT category and sub-category teams (Mobile, Software, and Laptop/Desktop) are also spending lots of time conducting industry days, participating in technology demonstrations, and meeting individually with companies. And the Office of Federal Procurement Policy (OFPP) encourages federal program and acquisition representatives to interact with industry as much as possible – they’ve issued three Mythbusting memos on the subject.
So my advice is to establish relationships and regular forums for communication with your industry partners and potential partners. The Alliant PMR and shared interest groups that have formed under the contract were called out as a best practice, and, unfortunately, are rare practice for government contracts.
Agencies should seize the opportunity inherent in active program management to help make the contract successful. GSA’s Alliant program and contracting staff are in constant communication with the industry – they share contract data, potential agency opportunities on the contract, outreach and training to agency customers, account management and agency buying trends; meet many client-facing GSA representatives; and provide a place for industry to resolve issues and challenges in a trusted environment.
Without spending time upfront to talk about what we need with industry, we aren’t going to get good competition or the innovative solutions we are looking for. I think open communications often comes from a feeling of safety and having top cover, and our government leaders need to provide that encouragement to our workforce.
2. e-Tools and Repository of Solicitations. Many agencies do an excellent job of using one system to post opportunities and retain statements of work and proposals in an historical repository. This is a great practice that reduces cost and provides clarity to industry about past requirements and incumbent contractors – things that are important to them as part of their bid/no-bid decision process. One participant said this about the Navy’s SeaPort-e system:
“You can see a changing dynamic in a scope of work and what solutions a customer is looking for. That transparency is robust enough to do a real analysis to understand that customer even better.”
That’s what we strive to do for the governmentwide category management efforts: share data and information, conduct more robust market research, and provide a platform like the Acquisition Gateway so agencies and industry have one place to go to find information pertinent to all agencies and across categories.
3. Statements of Work vs. Statements of Objectives. Government, in general, is still prescribing the HOW we want work to get done and what kind of people we want on the job (i.e., prescribing labor categories), rather than describing what we need and what the outcome should be.
Industry reported that they still see voluminous, prescriptive RFPs instead of simpler statements of objectives. When government uses the prescriptive RFP, it makes it harder for industry to offer innovative solutions – yet the government regularly says that’s what it wants. We need to train our folks to write statements of objectives and then how to manage contracts for outcomes and performance. It’s harder to do, but it’s where we need to be.
The industry unanimously agreed that GSA’s FEDSIM does a great job of this. FEDSIM conducts IT and professional services procurements on behalf of other agencies using a true Integrated Project Team approach. They bring in program, technical, acquisition, and legal staff to work with customer agency staff on requirements development and drafting the solicitation. In addition, FEDSIM uses standard acquisition processes and templates, and works very closely with industry to provide opportunity pipeline information and conduct market research during presolicitation (Check out their new website and you’ll see what I mean.). They write in clear performance-based terms and employ trained project managers and CORs to manage the projects after award.
Industry also pointed out that the way government structures smaller requirements often requires the same level of effort from industry to bid. So the tendency is for industry not to bid those requirements and instead spend their time bidding larger opportunities. This results in reduced competition and fewer innovative solutions for government on the smaller requirements.
4. STOP issuing Requests for Information asking for corporate capabilities! If an agency is going to use an existing contract, there is no need for capabilities RFIs. Agencies should be focused instead on asking for a few key pieces of information regarding the requirements themselves. Industry spends lots of time and money responding to general RFIs and then rarely ever get any information or response back from the government. This should be part of the market research and pre-solicitation process.
Another bad, costly, and confusing practice is for government to issue the same RFI against multiple contracts. Industry feels compelled to respond to all of them because of the uncertainty of where the requirement might end up. Unfortunately, this is a very costly and time-consuming practice.
With the Acquisition Gateway, agencies now have a single place they can find government-wide and agency-specific contracts for specific categories of spend. This should really help eliminate those general RFIs.
Using a tool like Interact provides a great way to share information online and let government and industry respond and ask questions – everyone has equal access. But government should still make time for those in-person discussions.
5. Things that drive up cost – Schedule slips and procurement delays. Industry budgets a certain amount of money each year for bid and proposal costs. As government delays the process, it extends the time industry must spend to pursue the work. It also comes with opportunity costs for not being able to bid on other work. This isn’t helpful if we want highly qualified partners who can bring us innovative solutions.
Requiring industry to provide references and agencies to fill out questionnaires on past performance. Industry questioned the value of government requiring past performance information as part of the evaluation process in the manner it typically uses. We all agree that both experience and past performance are critical factors. For the governmentwide contracts, the value is to offer qualified companies with strong program management and technical capabilities, so experience and past performance are both critical parts of the qualification process.
Systems like Contractor Performance Assessment Reporting System (CPARS) and Past Performance Information Retrieval System (PPIRS) can be used for at least part of what the government needs in the evaluation process, but another alternative offered was reciprocity across government in sharing contract Quality Assurance Surveillance Plans.
Industry estimated that the process used by the OASIS and Alliant 2 teams (a combination of FPDS-NG reports, CPARS/PPIRS reports, and past performance surveys only if a CPARS/PPIRS report was not available) saved between 40-70% in offeror bid and proposal costs.
Guessing at the cost of the requirement. Industry shared that a best practice is to publish the range of estimated costs the government thinks (and is willing to spend) to do the job directly in the solicitation. Part of the rationale for this is that the government isn’t writing clear requirements and isn’t sharing enough information for industry to be able to “guess” what the government is asking. Another reason this makes sense is that the amount that the government is spending is already public. Rather than falling into the “Price to Win” trap, leveling the playing field allows the government to select what is truly the best value .
GSA’s FEDSIM organization has used this practice successfully for years (I did it when I worked at FEDSIM 20 years ago). When the range is provided, industry can determine the kind of solution they can bid for what the government can spend.
6. Protests. As you might imagine, this topic brought lots of energetic discussion. Wrapped up in the topic are industry-government communications, risk, quality, and company strategy.
Industry suggested that government should improve relationships and communication. This includes sharing more information and being accessible in the pre-solicitation phase, writing clearer requirements, and allowing for in-person debriefs. As a result of these activities protests may decrease.
Our government representatives didn’t quite buy it. They pointed to cases in which those things were taking place and yet we still received protests. There was clear agreement from both government and industry that protests are often used as a strategy by an incumbent company to buy more time and income.
The group then discussed using something like a protest bond or fee that a company would have to pay if they lost a protest, hoping to encourage only protests that were charging substantive deficiencies or issues.
I don’t think much of what came up in our discussion was a surprise to anyone; however, I truly appreciated industry’s candor and how they gave us an opportunity to share and learn from this feedback. Both government and industry have responsibilities in federal acquisition,both parties can make improvements. Small changes can have big impact.
