Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Building the Hybrid Cloud
- Connected Government: How to Build and Procure Network Services for the Future
- Continuing Diagnostics and Mitigation: Discussion of Progress and Next Steps
- Federal Executive Forum
- Federal Tech Talk
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Moving to the Cloud. What's the best approach for me
- Navigating Tough Choices in Government Cloud Computing
- The New Generation of Database
- Satellite Communications: Acquiring SATCOM in Tight Times
- Targeting Advanced Threats: Proven Methods from Detection through Remediation
- Transformative Technology: Desktop Virtualization in Government
- The Truth About IT Opex and Software Defined Networking
- Value of Health IT
Shows & Panels
EXCLUSIVE: DHS directorate withdraws controversial vendor checklist
Thursday - 7/26/2012, 5:40am EDT
The Homeland Security Department's National Protection and Programs Directorate is backing away from a draft vendor communication guidance plan after receiving strong push back from industry.
The draft document first issued in April would have required NPPD senior executives to answer a 15-question checklist before meeting with any contractors. The questions ranged from the obvious, such as who they were meeting with and about what, to what some in industry called controversial, such as how many times NPPD officials have met with the company in the last six months and if the company has any contracts with DHS and all details about those contracts.
Industry representatives said they were most concerned about the requirement that would have prohibited agency executives from meeting with contractors if the "proposed meeting relates to current or planned contracting opportunity, a response to a (request for information), an unsolicited proposal or any circumstance where DHS has identified a need for products or services."
But a DHS official said the document is no longer in play.
"The draft document was not, nor will be, put into practice," said the official, who requested anonymity because the document is pre-decisional. "NPPD continues to work to ensure its employees are properly informed in the area of vendor engagement."
Agency sources said NPPD issued the draft document to about 100 senior executives in the spring and the general counsel has signaled that the agency and contractors should use the checklist.
DHS spokeswoman Marsha Catron said all of DHS is required to use the existing vendor communication plan.
"Recognizing that effective vendor engagement is critical to the acquisition process, the department's robust industry outreach team hosts DHS industry days, small business events and other vendor outreach activities to achieve the common goal of mission success," Catron in an emailed statement.
A chilling effect on communication
Industry experts say the guidance would have harmed both NPPD and contractors.
"Many of the questions and the information being requested from applicants for these meetings actually put a very significant chill on any communication," Alan Chvotkin, senior vice president and general counsel for the Professional Services Counsel, said in an interview with Federal News Radio before NPPD's decision not to put the guidance in place. "We are concerned if left unchanged it would actually end up denying more meetings than facilitating meetings between industry and the government.
On hearing the news that NPPD decided not to move forward with the guidance, Chvotkin said PSC welcomes DHS' endorsement of vendor outreach and discussion.
"In our view, the NPPD questionnaire for meeting schedulers and others asked more than just legitimate set-up questions that would aid in identifying meeting topics and attendees. We viewed the document as providing more justification for NPPD officials to decline vendor meeting requests than for facilitating such communications," he said. "We hope that NPPD would either withdraw the document or re-write it to more clearly align with the department's vendor outreach plan."
Trey Hodgkins, senior vice president for national security and procurement policy at TechAmerica, said his association's members also had a lot of concern over the draft guidance.
"I'm glad they have recognized it was a poorly thought out checklist that discouraged vendor engagement and that better outcomes that can be derived from that engagement and have abandoned its use," he said. "It is our hope that the department will proactively encourage vendor engagement, both collectively and individually, as needed to achieve best value for the taxpayer."
Good roadmap for ethics
But not everyone thought the checklist was such a bad idea.
Scott Amey, general counsel for the Project on Government Oversight, said this type of guidance has several benefits.
"I actually think it's a fairly good roadmap to avoid two types of problems we see in procurement," Amey said. "One is the problem with not having a level playing field. I think this memo gets to that. In essence, it's a checklist. It's also to help the agency and specifically personnel avoid conflicts of interest and any ethical dilemmas that often appear in government spending cases."
Chvotkin and Hodgkins said this type of memo shows that the Mythbusters campaign hasn't trickled down far enough in the agencies. The Office of Federal Procurement Policy issued two Mythbusters memos to help improve vendor-agency communication. OFPP's goal is to dispel commonly held myths about what agencies and contractors can talk about and when.
"At the point of execution, we still have a risk-adverse community and the indications from Mythbusters activity and the campaign apparently have not addressed those risks that the executers are concerned about," Hodgkins said. "Then in some of the efforts to implement the Mythbusters campaign there is a overlay of legal concern and, of course, nobody wants to run afoul of the legal entity within their agency or department. These kinds of guidance tend to leave one with the conclusion there is a lot of risk going down this road, and to the degree the acquisition workforce is a risk adverse environment, the general conclusion that many of them make is this is not something that is worth engaging in."