The cost to the taxpayer of attempting to eliminate all risk is prohibitive. The Executive Branch will accept and manage the risk associated with empowering local procurement officials to take independent action based on their professional judgment.
If a policy or procedure, or a particular strategy or practice, is in the best interest of the Government and is not specifically addressed in the FAR, nor prohibited by law (statute or case law), Executive order or other regulation, Government members of the Team should not assume it is prohibited. Rather, absence of direction should be interpreted as permitting the Team to innovate and use sound business judgment that is otherwise consistent with law and within the limits of their authority. Contracting officers should take the lead in encouraging business process innovations and ensuring that business decisions are sound.
That was from the Federal Acquisition Regulation (FAR) Part 1.102-2 and -3, quoted in DHS’s PIL Boot Camp Workbook.
Certainly this and other provisions are why many people say the FAR is not the main barrier to acquisition innovation. Contracting officers could accomplish a great deal if they read the whole thing and took initiative.
I think there’s a ring of truth to that. Contracting officers should be experts in the FAR, and should thus know the what is prohibited and what is not. If an action is not addressed in the FAR, then it is assumed open for innovation rather than closed for approval.
The problem, however, is that the boundary conditions for innovation is not the FAR, but includes a host of other considerations that the contracting officer cannot be expert in. Often, the FAR references a regulation which is explained in great detail in DOD guidance, memos, implementation guides, and so forth. Then there is considerations of what is in law, or mandated by Executive Order, or numerous other regulations.
As FAR Part 1.102 (d) states:
In exercising initiative, Government members of the Acquisition Team may assume if a specific strategy, practice, policy or procedure is in the best interests of the Government and is not addressed in the FAR, nor prohibited by law (statute or case law), Executive order or other regulation, that the strategy, practice, policy or procedure is a permissible exercise of authority.
It’s not simply the volume, but the uncertainty as to what rules apply and from where they might originate. Assuming all members of the Acquisition Team are experts, and know their respective areas of law and regulation fully, there still can be error when it comes to communication and execution.
Therefore, the risk-averse mindset still prevails. Often, each functionalist struggles to keep up with the breadth of rules within his or her own purview — let alone trust that all other Acquisition Team members have complete and accurate knowledge of their own areas, and have correctly interpreted the present situation in that context.
So acquisition leadership needs to go one step farther. No Acquisition Team member should be punished for a mistake, even if it conflicted with some law or regulation, unless it is clear and obvious from the viewpoint of a reasonable third-party person with the same functional experience that only malicious intent or severe incompetence could have resulted in the actions. This dramatically lowers downside risk for the huge percent of the workforce trying to do their best to contribute their knowledge and energy.
This is an area where Good Old Fashioned AI, of the Expert System variety, could be used to great effect. Expert Systems are perfect for decision contexts where the rules are byzantine but concrete. If the Services were serious about improving contracting and acquisition strategies, they would be investing in state of the art tools for the acquisition workforce.
I think the question is how concrete acquisition rules really are, or whether subjectivity and context is king. I remember the Air Force tried to build a supercomputer to navigate regulations:
“The defense acquisition system is a construct of government, erected over decades and codified in statute that now exceeds 180,000 pages. It is so complex that the Air Force commissioned a supercomputer to make sense of it.”
I don’t think much came out of that. Perhaps a deep dive on what happened there is in order.
https://www.airforcetimes.com/news/your-air-force/2015/08/11/air-force-wants-supercomputer-to-cut-through-bureaucracy/
http://www.lexingtoninstitute.org/scott-chandlers-speech-achieve-defense-acquisition-goals-better-buyer-customer/
Good article. See my tips and tools about the real heroes having to fight through this bureaucracy every day. https://nps.edu/web/acqnresearch/newsletter