As a fuel compliance officer for the Internal Revenue Service, David Wind sets out each morning from the Pittsburgh area to help ensure that the federal government collects the more than $20 billion it is owed annually in fuel excise taxes. He is one of 140 FCOs, all highly trained and experienced employees who root out billions of dollars in fraud in the fuel distribution network.

On paper, the job seems pretty simple: Test the fuel in diesel-powered trucks that are used on our roads and highways. It involves inspecting trucks at company yards, construction sites and farms. It also involves inspecting businesses such as truck stops and wholesale fuel dealers. Only fuel on which federal and state taxes have been paid can be used to operate highway vehicles. The revenue is used to build and maintain the nation's roads and bridges.

Highway vehicles cannot be run legally on tax-free fuel, which is dyed red to distinguish it from tax-paid fuel. Red fuel is only for off-highway vehicles, such as bulldozers or back hoes.

Determining whether fuel is red might be simple, but determining who is responsible for illegal activity and who is subject to civil penalties is anything but. Here is how Wind describes a common situation: "I visit farmers who own both highway vehicles and those that never leave the farm. They often have storage tanks for both undyed tax-paid fuel [for the highway] and dyed tax-free fuel [for farm implements]. When sampling the fuel in the highway vehicles, I might find red fuel, which is illegal. If a farmer insists he has done nothing wrong, I sample the fuel out of his undyed storage tank. If I find the same shade of red, the problem could be beyond the farmer-who could have been sold tainted fuel. I would need to investigate the wholesaler. If a company knowingly sold the tainted fuel, I would propose civil penalties against the wholesaler, not the innocent farmer."

Each day, the 140 FCOs arrive unannounced at work sites and businesses and conduct searches of private property. They carry out investigations and assess taxes. They make decisions that often are unpopular and can shut down a person's livelihood. As one FCO says, "Just about every FCO has been unfortunate enough to put someone out of business."

Their diligence not only uncovers tax fraud in a billion-dollar industry, but it helps ensure voluntary compliance with tax laws. In fact, the work they do is a textbook definition of the term "inherently governmental work." Until just a few years ago, the IRS labeled FCOs as inherently governmental on annual lists that federal agencies are required to provide to Congress.

So, why is the IRS now taking steps to allow private sector companies to bid for this work? Why is the agency charged with collecting our nation's taxes and safeguarding the private financial information of U.S. citizens and business suddenly opening its doors to contractors?

The FCO is only one example in an effort at the IRS to move inherently governmental work to private companies. Strongly opposed by the National Treasury Employees Union, turning this work over to the private sector would put at risk effective and efficient tax collection, the voluntary nature of our tax system, and the personal and financial privacy of taxpayers who might soon find their private information on the open market.

Another IRS plan that would feature contractors doing inherently governmental work is to use private sector debt collectors to go after taxpayers who owe money. Not only would the IRS have to provide personal information, including Social Security numbers, to the most complained-about industry in America, but debt collectors would be paid a bounty on what they collect. This situation is ripe for abuse.

Whether they are fuel compliance officers, revenue agents or clerks, IRS employees are dedicated to their work. They have chosen public service and they are accountable to the American people. It is time for the IRS to step away from the contracting-out chopping block and let employees do their jobs.

By using this service you agree not to post material that is obscene, harassing, defamatory, or
otherwise objectionable. Although GovExec.com does not monitor comments posted to this site (and
has no obligation to), it reserves the right to delete, edit, or move any material that it deems
to be in violation of this rule.

Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

In order to better understand the current state of external and internal-facing agency workplace applications, Government Business Council (GBC) and Riverbed undertook an in-depth research study of federal employees. Overall, survey findings indicate that federal IT applications still face a gamut of challenges with regard to quality, reliability, and performance management.

PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.