Criminal Conflict of Interest

On
March 26, 2010 the Department of Justice reported that a former Department of Energy (DOE) employee, Ms. Donna
Scott, had pled guilty to criminal conflict of interest and her husband
had pled guilty to making a false statement to a federal agent. We have
written before about both organizational and
personal conflicts of interest—notably here and here. There is a proposed rule in play that would establish
standards for contractor personal conflicts of interest similar to those already in place for government employees,
making this an issue applicable to pretty much everybody.
According
to the DOJ announcement, Mrs. Scott “coordinated the use and renovation
of DOE office space.” Included in her duties was the oversight of the
renovation of a lobby and conference room in a DOE building in
Germantown, MD. Her duties also included the acquisition of new
furniture for those spaces. While employed by DOE, she “recommended to a co-worker
that the co-worker obtain price quotes for furniture from her husband,
Timothy Scott. Timothy Scott provided these price quotes to Donna
Scott’s co-worker, both of which referenced Timothy Scott as the
manufacturer’s representative.” However,
the co-worker was told that she needed two additional price quotes in
order to “satisfy competitive bidding requirements.”
So, to help her co-worker satisfy “competitive bidding
requirements,” Mrs. Scott—
--admitted
that she subsequently obtained two
additional price quotes for each transaction from her husband and
provided them to her co-worker as the competitive price quotes. Donna
Scott admitted that she knew, unlike the original price quotes, that
none of these new price quotes referenced Timothy Scott by name.
Moreover, the additional quotes bid a higher price for the furniture
than the initial quote, making Timothy Scott’s original bid the lowest.
Mrs.
Scott’s co-worker used the three quotes to justify why Mr. Scott’s low
bid was fair and reasonable, and DOE then purchased the furniture from
Mr. Scott.
In addition to the foregoing, Mrs. Scott—
--selected furniture worth approximately $300,000 from
particular manufacturers for the cafeteria renovation project. [She] admitted that she knew these manufacturers’
representatives planned to use her husband as their dealer of record for
these transactions, thus earning her husband a commission. [She]
arranged for the furniture to be purchased by the General Services
Administration (GSA) on behalf of the DOE. As a result, Timothy Scott
earned approximately $24,174 in commissions from the manufacturers.
According
to the DOJ announcement, “Donna and Timothy Scott
each face maximum sentences of five years in prison and fines of
$250,000 or the greater of twice the gross gain or loss from the
offense. U.S. District Judge Peter J. Messitte has scheduled sentencing for June 3, 2010.”
DCAA Publishes New Audit Guidance on Allowable Air Fares
In December
2009, we reported on changes to
allowability rules regarding air fare costs. We noted several problems
with the new rule and predicted problems with implementation and with
DCAA audit guidance.
We wrote, “based on our experience with Government auditors, that is not how
the rule will be interpreted in audits of such costs.”
We were correct. Implementation has proved difficult, and
DCAA has just issued audit guidance that will cause problems
and—likely—litigation.
On March 22, 2010 DCAA issued MRD
10-PAC-010(R) entitled “Audit
Guidance on Revision to FAR 31.205-46(b) and (c) – Limiting Airfare to
the Lowest Airfare Available to the Contractor.” See
the entire MRD here. The MRD contains the following guidance—
- Auditors should question airfare costs claimed in excess of the
lowest airfare available to the contractor.
- To
comply with the revised rule, the contractor’s policies and procedures
should provide for advance planning of travel to assure that the lowest
priced airfare available to the contractor for flights during normal
business hours is documented and utilized as the baseline allowable
airfare cost.
- To determine the lowest airfare
available to the contractor for flights during normal business hours,
the contractor must now consider nonrefundable airfares and lower
airfares negotiated with airlines, travel service providers, credit card
companies, etc. However, auditors should not question airfare costs
claimed in excess of nonrefundable airfare available during normal
business hours if the contractor’s data show that its experience with
cancelling nonrefundable tickets results in increased cost in comparison
to the cost of refundable tickets.
- Ordinarily,
with adequate advance planning, documentation substantiating the lowest
airfare available takes the form of quotations from competing airlines
or travel service providers from which the lowest priced airfare can be
selected, giving proper consideration to any potential discounts or
credits to the contractor’s cost. There may be instances where only one
flight is available for a given mission need and, therefore, only one
quote is obtained, in which case the one quotation would substantiate
the lowest priced airfare available. However, auditors observing
frequent instances in which a single quotation is obtained to support
the airfare should assess whether the design or execution of the
contractor’s policies and procedures results in unreasonable airfare
costs.
Notice that DCAA has taken the
ambiguous FAR rule and decided (without support for its position) that
contractors now need “quotations from competing airlines … from which
the lowest priced airfare can be selected….” If one is to comply with
DCAA’s position, one would need to run mini-competitions for each trip,
and justify any fare paid over the lowest price offered. This is a
patently absurd position and one that is almost certain to result in a
challenge from a contractor who has air fare costs questioned because of
a lack of such competing quotes.
We
predicted that the poorly drafted rule, whose language did not align
with the purpose articulated in the promulgating comments, would cause
unintended problems. We don’t necessarily relish saying so, but we were
right.
Contractors must review the rule and
their travel practices, establish a position (which may or may not
match DCAA’s flawed interpretation of the rule), and be prepared to
fight with DCAA regarding differing interpretations and compliance
mechanisms.
Not fun. We told you so. And we
were right.
|
Secure Border Initiative Fails

In September 2006 Boeing beat Raytheon and was awarded the
“Secure Border Initiative” (SBI) contract to “to secure U.S. borders and
reduce illegal immigration, including an array of technical aids and
elements on both the northern Canadian border and the southern border
with Mexico.” Known as “SBInet,” Boeing was to
develop and install a “virtual fence” for the
Department of Homeland Security (DHS) U.S. Customs and Border Protection
Agency (CBPA). The SBInet contract was initially valued at $2
billion.
On March 16, 2010, DHS Secretary
Janet Napolitano announced that she would reprogram $50 million from the
SBInet contract and “spend
it on proven, off-the-shelf technology to protect U.S. borders,”
according to this CNN story. CNN reported that—
As
originally envisioned, SBInet
was to give the United States control of its borders through a system
of movable surveillance towers, high-tech sensors, radars, cameras and
communication relays that would give Customs and Border Protection
agents the ability to see and respond to intruders. But the system, which is being developed by
Boeing, has come under withering criticism from the Government
Accountability Office and others who say that it has been riddled with
problems. Napolitano said
the SBInet has been ‘plagued with cost overruns and missed
deadlines.’
As a
result, Secretary Napolitano said that she was freezing SBInet funding except for a 53-mile
portion in Arizona, until a “re-assessment” of the project is complete.
Meanwhile, $50 million in ARRA stimulus funds that was to be used to
“accelerate deployment of … surveillance technology and associated
command and control technologies” would be reprogrammed and used to
acquire “commercially available technology, including mobile
surveillance, thermal imaging devices, ultra-light detection,
backscatter (full body image) units, mobile radios, cameras and laptops
for pursuit vehicles and remote video surveillance system enhancements.”
In February, 2010, Secretary Napolitano testified before the
Senate’s Homeland Security Committee that “SBInet, a contract and a concept that was entered into years ago,
has been plagued with troubles from day one… It has never met a
deadline, it hasn’t met its operational capacities, and it doesn’t give
us what we need to have.” (Source: this Defense Industry Daily recap of SBInet history.) The DID article links to several GAO reports
critical of the project; the
article quotes GAO as reporting the following points—
· SBInet technology
deployment for the southwest border was planned to be complete by early
fiscal year 2009. When last reported in February 2009, the completion
date had slipped to 2016….
· Important aspects of SBInet
remain ambiguous and in a continued state of flux, making it unclear
and uncertain what technology capabilities will be delivered, when and
where they will be delivered, and how they will be delivered. For
example, the scope and timing of planned SBInet
deployments and capabilities have continued to change since the program
began and, even now, are unclear. Further, the program office does not
have an approved integrated master schedule to guide the execution of
the program, and GAO’s assimilation of available information indicates
that the schedule has continued to change. This schedule-related risk is
exacerbated by the continuous change in and the absence of a clear
definition of the approach that is being used to define, develop,
acquire, test, and deploy SBInet…. While the program
office recently issued guidance that defines key practices associated
with effectively developing and managing requirements, such as
eliciting user needs and ensuring that different levels of requirements
and associated verification methods are properly aligned with one
another, the guidance was developed after several key activities had
been completed. In the absence of this guidance, the program has not
effectively performed key requirements definition and management
practices. For example, it has not ensured that different levels of
requirements are properly aligned, as evidenced by GAO’s analysis of a
random probability sample of component requirements showing that a large
percentage of them could not be traced to higher-level system and
operational requirements. Also, some of SBInet’s
operational requirements, which are the basis for all lower-level
requirements, were found by an independent DHS review to be unaffordable
and unverifiable, thus casting doubt on the quality of lower-level
requirements that are derived from them. As a result, the risk of SBInet
not meeting mission needs and performing as intended is increased, as
are the chances of expensive and time-consuming system rework.
· SBInet
program uncertainties, such as not fully defined program expectations,
changes to timelines, and confusion over the need to obtain
environmental permits contribute to ongoing delays of SBInet
technology deployments…. According to program officials, as of August
2008, fencing costs averaged $7.5 million per mile for pedestrian
fencing and $2.8 million per mile for vehicle fencing, up from estimates
in February 2008 of $4 million and $2 million per mile, respectively.
Furthermore, the life-cycle cost is not yet known, in part because of
increasing construction costs and because the program office has yet to
determine maintenance costs and locations for fencing projects beyond
December 2008. In addition, land acquisition issues present a challenge
to completing fence construction
.
Rep. Bennie
G. Thompson, D-Mississippi, chairman of the House Homeland Security
Committee, was quoted as saying that SBInet has been a "grave and expensive disappointment. Today's
announcement is recognition that this troubled program needs better
management and stronger oversight."
We have written over and over that effective program
management is the key to survival in the current (and future) budget
squeeze. SBInet is yet
another example of the ramifications associated with poor program
management. There is no doubt in our minds that it will not be the last
program to pay the price for unacceptable contract outcomes.
FAPIIS Finally Here!

We told you about FAPIIS (Federal
Awardee Performance and Integrity Information System) last September,
when FAR Case 2008-027 (implementing § 827 of the FY 2009 Defense
Authorization Act) was published as a proposed rule. We called it “past
performance information on steroids” and said it was “a significant
proposed rule that may affect the ability of certain contractors to
receive Federal contract or grant awards.” On
March 23, 2010 the FAR Councils issued the final FAPIIS rule, which can
be found here.
Summary
of the final rule:
FAPIIS is intended to
significantly enhance the scope of information available to contracting
officers as they evaluate the integrity and performance of prospective
contractors. In addition to providing one-stop access to EPLS and PPIRS,
FAPIIS will also include contracting officers' non-responsibility
determinations (i.e., agency assessments that prospective contractors do
not meet requisite responsibility standards to perform for the
Government), contract terminations for default or cause, agency
defective pricing determinations, administrative agreements entered into
by suspension and debarment officials to resolve a suspension or
debarment, and contractor self-reporting of criminal convictions, civil
liability, and adverse administrative actions. The system will collect
this information, on an ongoing basis, from existing systems within the
Government (i.e., EPLS and PPIRS), contracting officers (for
determinations of non-responsibility and contract terminations),
suspension and debarment officials (for information on administrative
agreements), and contractors (for information related to criminal,
civil, and administrative proceedings).
We’re
not going to reiterate all the aspects of this fairly complex rule.
You can click the link to our original article to get the gist, or click
the link to the final rule to get all the details. Instead, we’re
going to focus on the FAR Councils’ promulgating comments, where they
disposition the public comments received. Here
are some (but not all) of the Councils’ comments.
- The
Councils seek to ensure that FAPIIS provides contracting officers with
efficient and effective access to the information they need to evaluate
the business ethics and quality of prospective contractors competing for
Federal contracts. To achieve this goal, the Councils have taken a
phased approach to the implementation of FAPIIS, focusing first on the
information specifically identified by Congress in section 872(c) of the
FY 2009 NDAA. … Going forward, this approach will allow the Councils to
carefully consider policy and procedural issues as new sources of
information are identified pursuant to section 872(b) and (c)(6). For
the next phase of FAPIIS, the Councils and OMB are carefully considering
a proposed rule that would build on several suggestions made by the
public and augment reporting by: (1) lowering the threshold for covered
actions that trigger FAPIIS reporting from $500,000 to the simplified
acquisition threshold and (2) expanding the current scope of reporting
to include other violations of laws, as opposed to violations only in
the context of Federal contracts. This information can further enhance
the utility of FAPIIS and give contracting officers a fuller picture of a
contractor's history of compliance. However, a number of the other
above-described suggestions for expansion raised concerns for the
Councils. For example: Requiring the collection of information on all
proceedings, regardless of outcome, could potentially create instances
where negative judgments on contractors' responsibility are made
regardless of the outcome of the referenced proceedings. If information
regarding yet-to-be-concluded proceedings were allowed, negative
perceptions could unfairly influence contracting officers to find a
contractor non-responsible, even in situations that later end with the
contractor being exonerated. The Councils are strongly committed to
helping contracting officials avoid these types of
situations. Incorporating all the information from ORCA is
inappropriate. Much of the information in this system is not designed to
support contracting officers in making responsibility determinations.
Extending the archival period (for retaining information beyond five
years) is also inappropriate as this period was created for auditing
purposes, not for use by contracting officers in making responsibility
determinations.
- The Councils appreciate
the need to ensure that information included in FAPIIS will contribute
to the stated purpose of the database and that appropriate training is
provided to help contracting officers in their use of this information.
The Councils did not agree, however, that significant revisions were
warranted based on the requested refinements. In particular, the
collection of information on administrative agreements entered into to
resolve a suspension or debarment is required by section 872, so it must
be included in the system. Regarding the concern raised with the
definition of ``covered person,'' the existing requirement at FAR
52.209-5 includes certification regarding both the offeror and the
principals. Additionally, since the FAPIIS requirement for information
does not relate to all offenses by the principals, but only to those
that relate to the performance of a Federal contract or grant, this
information should be available to the offeror. As further
clarification, the Councils have removed an inconsistency within the
definition of ``principal'' between the stated meaning (person within
the business entity) and one of the examples (head of a subsidiary). A
subsidiary is not generally within the business entity, but is a
separate and distinct legal entity. Therefore, the Councils have removed
``head of a subsidiary'' from the list of examples in the definitions
of ``principal'' throughout the FAR, because it can imply a meaning
broader than the stated definition. Deletion of this example should not
result in any change of meaning, since this is just an example, and the
definition clearly states that principals are persons within the
business entity.
- … the Administrator of GSA shall develop policies to require the
timely and accurate input of information into the database. To this end,
the Councils will work with the FAPIIS Program Manager, the Federal
Acquisition Institute (FAI), and the Defense Acquisition University
(DAU) to develop guidance for contracting officials and SDOs on proper
input, accuracy, and timeliness of data into FAPIIS. In addition, the
Councils have added a requirement to the rule similar to that at FAR
4.604 for data entry into the Federal Procurement Data System, stating
that the contracting officers and SDOs are responsible for the timely
submission and sufficiency of the data. There is no single entity that
can be held accountable because the information in FAPIIS comes from
various sources. However, each system to which FAPIIS connects has its
own guidelines for timeliness and accountability and separate
initiatives are being pursued to strengthen these systems. For example,
OFPP's memorandum of July 29, 2009, Improving the Use of Contractor Performance Information … requires the
submission of report cards to the Past Performance Information Retrieval
System (PPIRS). PPIRS has a standard format for supplying all the
report card information collected from the Federal agencies to
authorized Government users for use in source selection decisions, and
the Government is working to improve compliance by Federal agencies in
reporting this data and the quality of the information entered into
PPIRS. In improving the compliance and quality of the data, over time,
the accuracy of the data should improve. In the meantime, the Councils
have added a requirement for timeliness and accountability for the
Government personnel who will be entering data directly into the
database. With respect to contractors, there are a range of penalties
available to the Government for non-compliance with the requirements of a
contract, such as determination of non-responsibility, termination for
default, or suspension or debarment.
- FAPIIS
will provide access to data on active suspensions and debarments, even
if the suspension or debarment was imposed more than five years ago.
FAPIIS will also provide access to data on expired suspensions and
debarments for five years after the expiration date. To access records
after this period, agencies would need to utilize the Excluded Parties
List System's archives. With respect to the $10 million threshold, the
Councils concur that additional clarification is needed to capture the
value of modifications when calculating the total value of all current,
active contracts and grants. The language in the final rule has been
refined to clarify that offerors must consider the total value of the contracts and grants
including all priced options and modifications.
- The Councils appreciate the importance of helping contracting
officials obtain the skill and aptitude necessary to discern the
relevance and weight to be given the information reviewed. The Councils believe that training, rather than more specific
standards in the regulations, is a better way to achieve this goal. The
Councils will work with FAI and DAU to develop guidance and training for
contracting officials on the proper use of the information contained in
FAPIIS, and the type of information that would warrant submission to
agency SDOs.
- The Councils recognize
that some of the data in the database may not be relevant when
determining present responsibility and are committed to avoiding
situations of unjustified determinations of non-responsibility. Without
the language, contracting officers may think they are required to
utilize outdated information that has no bearing on a contractor's
present responsibility. The statement does not, as one commenter
suggested, limit a contracting officer from considering any information
that can be appropriately considered and that is relevant. In light of
the comments, the Councils have clarified the explanation for the
caution by stating that FAPIIS may contain information on any of the offeror's previous contracts and
therefore may contain information relating to contractors for products
or services that are completely different from those being acquired. The
Councils have also added cross references to FAR 15.305(a)(2) as a reminder of relevance
requirements in the consideration of past performance.
- In the final rule, FAR section 9.104-6 focuses just on
responsibility determinations. For past performance evaluations, the
contracting officer is referred to FAR section 15.305(a)(2), which addresses how to evaluate the
relevance of data and clearly states that this evaluation is separate
from the responsibility determination required under subpart 9.1. The
final rule also incorporates use of FAPIIS into the procedures
addressing agency evaluations of contractor performance in FAR 42.1503
since there may be information in FAPIIS, such as terminations for
default or cause and defective pricing assessments, that is not in PPIRS
but still may be appropriately used, along with the information in
PPIRS to evaluate an offeror's performance.
- The proposed language,
which has been retained without change in the final rule, requires
contracting officers to notify, prior to proceeding with award, the
agency official responsible for initiating debarment or suspension
action in accordance with agency procedures. This notification process
closely tracks that already established in FAR 9.104-5 for situations
where an offeror provides an affirmative response on its responsibility
certification and therefore should not create undue additional delay. In
addition, no changes have been made to procedures currently used to
ensure an opportunity for the offeror to provide its input where
responsibility is in question. The final rule follows the current
practice for providing offerors with an opportunity to explain their responsibility if the
contracting officer obtains relevant information from FAPIIS that could
lead to a non-responsibility determination. Similarly, the rule makes no
changes to the due process obligations associated with suspension or
debarment actions.
- The Councils disagree with
the arguments set forth to oppose application of the rule to commercial
item and COTS acquisitions. An exemption for commercial item and COTS
acquisitions would exclude a significant portion of Federal contractors,
thereby undermining an overarching public policy to achieve greater
integrity and performance quality in contracting that this law is
intended to further. There also does not appear to be any unique burden
that would undermine access to the commercial marketplace. The
requirement for contractors to submit information into FAPIIS applies to
those contractors with active Federal contracts and grants totaling
more than $10 million at the time of proposal submission, and
contractors with this level of activity generally should be equipped to
collect and update the information in the system. The commenter even
acknowledged that there is a reasonable likelihood a contractor offering
a commercial item or COTS item may already be covered by the reporting
requirement by virtue of past awards for other than commercial items and
COTS. … The required determinations have been made and, consistent
with these determinations, the final rule has been promulgated to cover
acquisitions of commercial items and COTS.
- The
Councils have incorporated the business rules that impact the
contractor into a new clause addressing updates of information regarding
responsibility matters: (1) The Contractor will receive notification
when the Government posts new information to the Contractor's record.
(2) Only Government personnel and authorized users conducting business
on behalf of the Government can view system information, with the
exception that a Contractor can view its own information. Public
requests for information will be handled under the Freedom of
Information Act procedures including, where appropriate, procedures
promulgated under E.O. 12600. (3) The Contractor will have an
opportunity to post comments regarding information that has been posted
by the Government. The contractor comments will be
retained as long as the associated information is retained, i.e., for a
total period of six years. Contractor comments will remain a part of
the record unless the Contractor revises them.
- The Councils acknowledge the concern regarding standardization
of the collection of all past performance data in general. As mentioned
above, the Federal Government is making strides to improve the
collection of past performance information required by FAR subpart
42.15. This includes the memorandum issued by the Office of Federal
Procurement Policy (OFPP) on July 29, 2009, which required the
submission of report cards to the Past Performance Information Retrieval
System (PPIRS). PPIRS has a standard format for report card
information, and provides that information to all authorized Government
users for use in source selection decisions. We are working to improve
compliance with the requirement to submit data to this system and to
improve the quality of the data submitted. As these efforts proceed, the
accuracy of the data should improve.
There you
have it. FAPIIS is now in play and contractors will have to deal with
it.
|