<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

    <channel>
    
    <title>Oles Morrison</title>
    <link>http://www.oles.com/</link>
    <description></description>
    <dc:language>en</dc:language>
    <dc:creator>keith@keithrusselldesign.com</dc:creator>
    <dc:rights>Copyright 2013</dc:rights>
    <dc:date>2013-03-29T22:05:52+00:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />
    

    <item>
      <title>Introduction to Domestic Preference Acts</title>
      <link>http://www.oles.com/blog/entries/introduction-to-domestic-preference-acts</link>
      <guid>http://www.oles.com/blog/entries/introduction-to-domestic-preference-acts#When:22:05:52Z</guid>
      <description>It comes as a surprise to no one that Congress has wide&#45;ranging ability to place conditions on the federal government&amp;rsquo;s ability to spend federal dollars.&amp;nbsp; What may surprise some contractors is the effect that Congress&amp;rsquo;s power via &amp;ldquo;domestic preference acts&amp;rdquo; has to limit how the contractor builds a project and what materials it procures to do so.&amp;nbsp; &amp;nbsp;
What do we mean when we say &amp;ldquo;domestic preference acts&amp;rdquo;? &amp;nbsp;These refer to the Acts that establish the long&#45;standing inclination of the United States government to ensure federal dollars are spent on domestic products.&amp;nbsp; For example:

Buy American Act of 1933 (41 U.S.C. &amp;sect;10a&#45;d)
Trade Agreements Act (19 U.S.C. &amp;sect;&amp;sect; 2511&#45;2518, implements WTO GPA)
Berry Amendment (applicable to DoD)
Surface Transportation Assistance Act of 1982 (&amp;ldquo;Buy America&amp;rdquo; &amp;ndash; which notably is not exactly the same as &amp;ldquo;Buy American&amp;rdquo;)

The BAA requires &amp;ldquo;substantially all&amp;rdquo; of an acquisition be attributable to American&#45;made components. This has come to mean that at least 50 percent of the costs must be attributable American content.&amp;nbsp; The BAA applies to &amp;ldquo;construction materials&amp;rdquo; and &amp;ldquo;end products,&amp;rdquo; depending on whether a supply contract or construction contract is involved.&amp;nbsp; A two&#45;part test has developed to determine whether the BAA applies and the GAO applies a case&#45;by&#45;case standard to determine applicability of whether something is &amp;ldquo;manufactured&amp;rdquo; in the United States sufficient to meet the requirements of BAA.
This principle is applicable to those involved with heavy civil construction via the Surface Transportation Assistance Act of 1982, with its separate policy known as &amp;ldquo;Buy America.&amp;rdquo;&amp;nbsp; This version governs procurements funded through the Department of Transportation, such as highway, bridge, rail, and transit construction. A product is defined as American&amp;ndash;made under &amp;ldquo;Buy America&amp;rdquo; if all of its manufacturing processes, constituent parts and/or materials originated in the United States. &amp;nbsp;The Federal Highway Administration (FHWA) applies the Buy America standards through 23 U.S.C. &amp;sect; 313, and 23 CFR &amp;sect; 635.410.
To further confuse matters, the 2009 American Recovery and Investment Act added its own amendments and requirements applicable to all projects funded with Recovery Act funds &#45; both direct federal and federal&#45;aid. (AARA Section 1605).&amp;nbsp; In addition, there are agency specific interpretations in the Act and there are also special restrictions attached to federal funds given to states for mass transit and highway projects.&amp;nbsp; &amp;nbsp;
The Moving Ahead for Progress in the 21st Century Act (MAP&#45;21), signed by President Obama on July 6, 2012, contains a provision that substantially broadened the application of Buy America to any contract eligible for Federal highway funding, regardless of the funding source of such contracts, if at least one contract for the project is funded with Federal&#45;aid highway funds.&amp;nbsp;
In response, FHWA the just issued its own clarification procedures in December 2012. &amp;nbsp;The FHWA concluded that for a manufactured product to be subject to Buy America, it had to be manufactured &amp;ldquo;predominantly&amp;rdquo; of steel or iron, meaning it consists of at least 90 percent steel or iron content when delivered to the job site (including the sites where any precast concrete products are manufactured) for installation.&amp;nbsp; For example, steel or iron products included fabricated structural steel, piling, sheet piling etc. are subject to Buy America.&amp;nbsp; The miscellaneous steel or iron components, subcomponents and hardware necessary to encase, assemble and construct the above components (or manufactured products not predominantly steel or iron) are not subject to Buy America coverage.&amp;nbsp; Products such as, clamps, fittings, sleeves, washers, bolts, nuts, screws, tie wire, spacers, lifting hooks etc. are not subject to the Act. FHWA also clarified that under MAP&#45;21, the Buy America provisions extend downward to include the utility work, if the project is funded with federal&#45;aid highway funds. (See, i.e. http://www.fhwa.dot.gov/construction/contracts/121220.cfm).
For another wrench in a contractor&amp;rsquo;s analysis, the Trade Agreements Act in effect modifies BAA and opens procurement to products from &amp;ldquo;designated countries&amp;rdquo;, for certain specified product categories, above certain specified thresholds, the amount of which is determined by the specific country. &amp;nbsp;It requires a very detailed analysis to ensure compliances with the TAA in relation to the other domestic preference acts.&amp;nbsp;
Unfortunately, for contractors, knowing which requirements apply and when they are subject to exemption or waiver can be difficult to ascertain and running afoul of these acts could involve audits, investigations, monetary sanctions, suspension or debarment and/or civil or criminal liabilities under the False Claims Act.&amp;nbsp; Should you have questions about the applicability of and compliance with these Domestic Preference Acts, please contact us.
&amp;nbsp;</description>
      <dc:subject></dc:subject>
      <dc:date>2013-03-29T22:05:52+00:00</dc:date>
    </item>

    <item>
      <title>When a false certification may not be “false” under the False Claims Act</title>
      <link>http://www.oles.com/blog/entries/when-a-false-certification-may-not-be-false-under-the-false-claims-act</link>
      <guid>http://www.oles.com/blog/entries/when-a-false-certification-may-not-be-false-under-the-false-claims-act#When:23:08:56Z</guid>
      <description>Government contractors routinely provide certifications during the contracting process.&amp;nbsp; For example, these certifications ask the contractor to verify that the cost or pricing data or claims submitted are true and honest.&amp;nbsp; Submitting a false claim can create liability under the Federal False Claims Act (&amp;ldquo;FCA&amp;rdquo;).&amp;nbsp; See 31 U.S.C. &amp;sect; 3729.&amp;nbsp; Lawsuits against contractors for potential violations of the FCA may come directly from the Government or through qui tam suits.&amp;nbsp; The central question in these cases is whether the contractor presented a false or fraudulent claim to the Government.
In some jurisdictions, not every failure to comply with a federal statute, regulation, or contract provision automatically creates liability.&amp;nbsp; Courts may distinguish between &amp;ldquo;express&amp;rdquo; and &amp;ldquo;implied&amp;rdquo; certification theories of liability.&amp;nbsp; Under an &amp;ldquo;express&amp;rdquo; certification theory, courts look to whether payment from the Government is contingent on an express requirement to certify compliance with an applicable statute or regulation.&amp;nbsp; Absent an express requirement, a contractor may not be liable for a false certification. Under an &amp;ldquo;implied&amp;rdquo; certification theory, the very act of seeking payment implies that the contractor complied with applicable rules and regulations.&amp;nbsp; If a contractor does not comply with applicable rules and regulations, the absence of an express requirement may not bar a court from holding a contractor liable.
A recent decision from a U.S. District Court in Texas provides an example of how courts deal with &amp;ldquo;express&amp;rdquo; and &amp;ldquo;implied&amp;rdquo; certification theories of liability.&amp;nbsp;&amp;nbsp; In U.S. ex rel. Long v. GSD &amp;amp; M Idea City LLC, Civil Action No. 3:11&amp;ndash;cv&amp;ndash;1154&amp;ndash;O (Jan. 18, 2013), a contracts manager brought a qui tam suit against a contractor alleging that certified overhead costs and profit numbers provided to the Government during contract negotiations were false.&amp;nbsp; The contractor argued that the contracts manager failed to show an FCA violation because the certifications at issue were not connected to a claim for payment.&amp;nbsp; The court agreed, and held that for a certification to be &amp;ldquo;false&amp;rdquo; under the FCA, the certification must be a &amp;ldquo;prerequisite&amp;rdquo; or &amp;ldquo;condition&amp;rdquo; necessary to payment.&amp;nbsp; The court dismissed the FCA claim because the contracts manager failed to demonstrate how any allegedly false certifications led to a false claim for payment.
The outcome in U.S. ex rel. Long may have been different in a jurisdiction applying an &amp;ldquo;implied&amp;rdquo; certification theory of liability.&amp;nbsp; In such a jurisdiction, the mere fact that the contractor did not act in compliance with federal statutes, regulations, or contract provisions by providing allegedly false overhead costs and profit numbers during a contract negotiation may have been sufficient to impose liability.&amp;nbsp; The distinction between false certifications made during contract negotiations and a claim for payment would not likely be dispositive.&amp;nbsp; Liability attaches as a result of the underlying fraudulent activity, not to a claim for payment.&amp;nbsp; This shows that depending on how a court treats a false certification, contractors can expect potentially inconsistent results.</description>
      <dc:subject></dc:subject>
      <dc:date>2013-03-26T23:08:56+00:00</dc:date>
    </item>

    <item>
      <title>More on NDAA 2013: Impact on the Small Business Administration</title>
      <link>http://www.oles.com/blog/entries/more-on-ndaa-2013-impact-on-the-small-business-administration</link>
      <guid>http://www.oles.com/blog/entries/more-on-ndaa-2013-impact-on-the-small-business-administration#When:17:23:56Z</guid>
      <description>As noted in our earlier blog entry, the National Defense Authorization Act of 2013 (&amp;ldquo;NDAA&amp;rdquo;), signed by President Obama on January 3, 2013 included significant changes affecting small business contracting. The changes largely came as a result of the House Armed Services Committee special &amp;ldquo;Panel on Business Challenges in the Defense Industry.&amp;rdquo;
Under Section 1641, the NDAA is expanding the mentor&#45;prot&amp;eacute;g&amp;eacute; program for &amp;ldquo;all small business concerns,&amp;rdquo; from its present application that only applies to 8(a) disadvantaged businesses. The NDAA directs the Small Business Administration (&amp;ldquo;SBA&amp;rdquo;) to create mentor&#45;prot&amp;eacute;g&amp;eacute; programs for each type of small business concern, for example HUBZone businesses, Service Disabled and Veteran Owned businesses, and Women&#45;Owned small businesses, among others. The NDAA requires the SBA to issue regulations establishing these mentor&#45;prot&amp;eacute;g&amp;eacute; programs within 270 days.
The mentor&#45;prot&amp;eacute;g&amp;eacute; program as it presently exists, applies to 8(a) disadvantaged businesses, and allows large businesses to act as mentors to small businesses.&amp;nbsp; This permits the two companies to form a joint venture and bid on small business contracts without violating size or affiliation rules. Section 1641 should expand the number of potential prot&amp;eacute;g&amp;eacute;s and create greater opportunities for large companies to serve as mentors.
The NDAA also changed the regulations on subcontracting calculations.&amp;nbsp; Previously, a small business was required to incur to incur at least 50 percent of the labor costs for service or supply contracts and 25 to 15 percent of the labor cost for general or specialty construction contracts. Sections 1651 and 1652 of the NDAA, change the calculations from &amp;ldquo;price&amp;rdquo; to &amp;ldquo;cost&amp;rdquo;, requiring a comparison of prime contract price to subcontract prices. The NDAA also creates penalties (of $500,000 or the dollar amount expended in excess of the permitted level, whichever is greater) for violating limits. The changes apply to the following contracts:

For service contracts, not more than 50 percent of the amount paid to the contractor with a small business set aside for a services contract can be spent on subcontractors. 
For supply contracts, the small business may not expend more than 50 percent of the prime contract price on subcontractors, less the cost of materials. 
For construction contracts, the SBA will determine the percentage after obtaining public comments.

Section 1681 creates a &amp;ldquo;safe harbor&amp;rdquo; for a firm that mistakenly represented itself as a &amp;ldquo;small business.&amp;rdquo;&amp;nbsp;&amp;nbsp; However, this very narrowly construed provision only provides a safe harbor if the company can show (1) it relied on an opinion provided by a Small Business Development Center or an entity participating in the Procurement Technical Assistance Program; and (2) the written opinion must have been submitted for review to the General Counsel of the Small Business Administration beforehand.
Section 1695 expands the bonding capacity of the SBA. The SBA now has the ability to guaranty surety bonds for small business contracts up to $6.5 million, an increase from the prior $2 million limit. Additionally, if the CO certifies that a guarantee is necessary for the small business to obtain bonding and that it is in the government&amp;rsquo;s best interests, Section 1695 permits the SBA to guarantee a bond for up to $10 million. The hope is that the increased bonding opportunities through the SBA will now allow small business to actively compete for the larger construction and/or service contracts.
Changes were also made to the Women&#45;Owned small business program ceilings on set&#45;aside contracts.&amp;nbsp; Under Section 1697, the dollar limits for set&#45;asides for women&#45;owned small businesses agencies have been removed in their entirety.&amp;nbsp;
We will continue to apprise you of any updates as these changes are implemented by the SBA over the course of 2013.</description>
      <dc:subject></dc:subject>
      <dc:date>2013-03-22T17:23:56+00:00</dc:date>
    </item>

    <item>
      <title>Government Steps Up Efforts to Track Contractor Performance and Integrity Data</title>
      <link>http://www.oles.com/blog/entries/gov-steps-up-efforts-to-track-contractor-performance-and-integrity-data</link>
      <guid>http://www.oles.com/blog/entries/gov-steps-up-efforts-to-track-contractor-performance-and-integrity-data#When:21:18:00Z</guid>
      <description>Over the last several years, the Office of Federal Procurement Policy (&amp;ldquo;OFPP&amp;rdquo;) has tried to get federal agencies to use its Past Performance Information Retrieval System (&amp;ldquo;PPIRS&amp;rdquo;). PPIRS is a database used to help a contracting officer make source selection and award decisions based on a prospective contractor&amp;rsquo;s prior performance on Government contracts. Since its advent, agencies have complied with the mandate to provide information to PPIRS, but underreporting is a recurrent problem. According to OFPP, underreporting limits the value of contractor performance assessments and the transparency of data about contractor integrity.&amp;nbsp;&amp;nbsp;&amp;nbsp;
In light of these problems, on March 6, 2013, OFPP released a memorandum to agency officials setting specific PPIRS reporting targets for agencies to meet over the next three years. &amp;nbsp;These reporting requirements are dependent on how a particular agency is currently entering data into PPIRS.&amp;nbsp; The Government&amp;rsquo;s updated compliance efforts will increase the microscope on contractor work performance.
OFPP is also asking agencies to improve contractor integrity data.&amp;nbsp; Along with PPIRS, OFPP wants to improve data collection for the Federal Awardee Performance and Integrity Information System (&amp;ldquo;FAPIIS&amp;rdquo;).&amp;nbsp; The FAPIIS was designed to enhance the Government&amp;rsquo;s ability to evaluate the business ethics and quality of perspective contractors competing for Federal contracts.&amp;nbsp; The system collects information from Government personnel such as nonresponsibility determinations, terminations for default or cause, defective pricing determinations, suspensions and debarments, etc.&amp;nbsp; Contractors also provide integrity information to FAPIIS&amp;nbsp; such as criminal convictions or adverse civil judgments or administrative proceedings.&amp;nbsp; The OFPP memorandum asks agencies to take a more aggressive approach in vetting contractor&#45;provided information such as sampling and/or conducting routine data quality reviews to ensure that the required integrity information is being reported.
Given Federal spending limitations and the Government&amp;rsquo;s renewed focus to cut waste, efforts to collect more information on contractors is unsurprising.&amp;nbsp; All this highlights the need for contractors to make sure their data reporting obligations are met, and more importantly, that contractors remain vigilant in complying with Federal laws and regulations concerning certifications, claim submissions, and general contract performance.
&amp;nbsp;</description>
      <dc:subject></dc:subject>
      <dc:date>2013-03-21T21:18:00+00:00</dc:date>
    </item>

    <item>
      <title>National Defense Authorization Act 2013 (NDAA): Overview of Title VIII of the Act</title>
      <link>http://www.oles.com/blog/entries/national-defense-authorization-act-2013</link>
      <guid>http://www.oles.com/blog/entries/national-defense-authorization-act-2013#When:04:41:07Z</guid>
      <description>Three months into the fiscal year, on January 2, 2013, the President signed the National Defense Authorization Act (NDAA) for fiscal year 2013. &amp;nbsp;Title VIII of NDAA contains many procurement and construction contract related provisions. This post briefly highlights some of the key provisions of the NDAA applicable to those seeking to contract with the federal government.&amp;nbsp; The impact of these provisions on contractors will depend on the results of some of the &amp;ldquo;reviews&amp;rdquo;&amp;nbsp; &amp;ldquo;guidelines&amp;rdquo; and &amp;ldquo;analyses&amp;rdquo; required by various agencies and their officials over the course of the next 180&#45;270 days, although some of the provisions take immediate effect.&amp;nbsp; The 44 provisions in Title VIII addressing procurement reform can be found in their entirety at Pub. L. No. 112&#45;239.&amp;nbsp;
A follow up post discussing those sections of the NDAA, outside of Title VIII, that apply only to small businesses can be found here.


Section 802 addresses Pass&#45;Through Contracts.&amp;nbsp; &amp;nbsp;Since 2009, the FAR required an offeror intending to subcontract more than 70 percent of the total cost of work to be performed under the contract to:&amp;nbsp; (i) identify the &amp;ldquo;amount of the offeror&amp;rsquo;s indirect costs and profit/fee applicable to the work to be performed by the subcontractor(s),&amp;rdquo; and (ii) provide a &amp;ldquo;description of the added value provided by the offeror as related to the work to be performed by the subcontractor(s).&amp;rdquo;&amp;nbsp; If the Contracting Officer deemed the pass through excessive, the costs could be declared unallowable.&amp;nbsp; However, under the new Act, Contracting Officers within DoD, the State Department and the Agency for International Development will now have the authority to contract directly with a prime contractor&amp;rsquo;s proposed subcontractor(s) when a prime contractor proposes to have its subcontractor(s) perform more than 70 percent of the work.&amp;nbsp; The Agency CO&amp;rsquo;s will have to document that this approach is in the Agency&amp;rsquo;s best interest.&amp;nbsp;


Section 804 addresses DFARs Profit Guidelines.&amp;nbsp; The Act requires DoD to review its profit guidelines &amp;ldquo;in order to identify any modifications to such guidelines that are necessary to ensure an appropriate link between contractor profit and contractor performance.&amp;rdquo; This review, which must obtain the views of private sector, the Government experts and interested parties, must consider (1) &amp;ldquo;[a]ppropriate levels of profit needed to sustain competition in the defense industry,&amp;rdquo; (2) &amp;ldquo;[a]ppropriate adjustments to address contract and performance risk assumed by the contractor,&amp;rdquo; and (3) &amp;ldquo;[a]ppropriate incentives for superior performance in delivering quality products and services in a timely and cost&#45;effective manner[.]&amp;rdquo; Based on the findings in that review, DoD is then required to &amp;ldquo;modify&amp;rdquo; the DFARs profit guidelines and make appropriate changes.

Section 811 addresses cost&#45;type contracts.&amp;nbsp; DoD is now required within 120 days of NDAA&amp;rsquo;s passage to modify its regulations &amp;ldquo;to prohibit [DoD] from entering into cost&#45;type contracts for the production of major defense acquisition programs&amp;rdquo; entered into after October 2014.&amp;nbsp; However, it will not apply in the case of a particular cost&#45;type contract if the Under Secretary of Defense provides a written certification to the congressional defense committees that a cost&#45;type contract is needed to provide a required capability in a timely and cost&#45;effective manner. In theory, this seems more restrictive than it really is.&amp;nbsp; Although Section 811 will limit the use of cost&#45;type contracts for production of major defense acquisition programs, it only applies to production phases of a program. It does not apply to development phases, or other earlier phases which is where cost&#45;type contracts have typically been viewed as more appropriate. See DFARS 235.006(b); See also, e.g., DoD Instruction 5000.02 (Milestone C).


Section 822 addresses the commercial test program.&amp;nbsp; It extends the authority for the FAR Subpart 13.5 commercial items test program from January 2012 to January 1, 2015. FAR Subpart 13.5 authorizes the use of simplified procedures for the acquisition of supplies and services in amounts greater than the simplified acquisition threshold (i.e., $150,000) but generally not exceeding $6.5 million, including options. The Comptroller General is directed to report, by October 1, 2013, on the use of this authority. The Comptroller General&amp;rsquo;s report is required to address: &amp;ldquo;(1) the extent of use of the authority; (2) the cited rationales for use of the authority; (3) the acquisition outcomes that have resulted; and (4) any waste, fraud, or abuse that have resulted from the use of the authority.&amp;rdquo;


Sections 827 and 828 expand the whistle&#45;blower protections.


Section 827 amends the whistleblower protections presently available to employees of DoD contractors (outside the intelligence community) by: (i) covering NASA contractors and their employees, and DOD and NASA subcontractor and grantee employees; (ii) expanding the protection to cover grand jury, court, or management official or other contractor/subcontractor employee with responsibility to discover, investigate or address misconduct; and (iii) providing for attorneys&amp;rsquo; fees and costs when the Government (and possibly the whistleblower) successfully files a law suit to enforce such protections. &amp;nbsp;In theory, the hope is that by including company management officials on the list of permitted recipients of protected disclosures, it will now encourage employees to raise concerns internally.&amp;nbsp; This in turn may provide contractors an opportunity to remedy a problem without external investigations being conducted.


Section 828 creates a program analogous to whistleblower protections now available to DoD contractor and subcontractor employees.&amp;nbsp; Under Section 828, after July 1, 2012, the protections are now extended for the employees of contractors, subcontractors and grantees of executive agencies &amp;ndash; with the exception of DoD, NASA and the intelligence community &amp;ndash; and affords such employees protection from reprisals as long as they &amp;ldquo;reasonably believe&amp;rdquo; they are disclosing &amp;ldquo;evidence of gross mismanagement of a Federal contract or grant, a gross waste of Federal funds, an abuse of authority relating to a Federal contract or grant, a substantial and specific danger to public health or safety, or a violation of law, rule, or regulation related to a Federal contract (including the competition for or negotiation of a contract) or grant.&amp;rdquo;


As a result of Sections 827 and 828, Government contractors should be quite careful when considering employment actions concerning whistleblowers. In addition to contractor employees, these new whistleblower protections now may cover subcontractor and grantee employees. &amp;ldquo;Reprisals&amp;rdquo; against the reporting individuals are also prohibited, even when requested by a DoD official.&amp;nbsp; As a practical concern, contractors and subcontractors should update their compliance programs, conduct appropriate whistleblower training, and update their internal whistleblower protection policies. &amp;nbsp;Contractors should also be aware of the permissive attorney&amp;rsquo;s fees provisions for whistleblower actions.


Section 829 addresses the potential for modification to personal conflicts of interest rules to DoD contractor employees. &amp;nbsp;Currently personal conflict of interest rules apply only to employees carrying out procurement functions that are associated with inherently governmental functions (i.e. such as drafting specifications, advising the Government about acquisitions, approving contractual requirements, or otherwise administering, assessing or awarding contracts.). &amp;nbsp;Section 829 now requires DoD to examine whether these rules should apply to &amp;ldquo;[f]unctions other than acquisition functions that are closely associated with inherently governmental functions,&amp;rdquo; &amp;ldquo;[p]ersonal service contracts&amp;rdquo; and/or &amp;ldquo;[c]ontracts for staff augmentation services.&amp;rdquo; &amp;nbsp;The Act now permits modification of the DFARs to accommodate this analysis, but no specific time frame is set forth for the modification.


Section 830 addresses Task &amp;amp; Delivery Order protests.&amp;nbsp; This section makes permanent GAO&amp;rsquo;s exclusive authority to review protests of DoD, NASA and Coast Guard task and delivery orders in excess of $10 million, as long as the protests do not involve increases in the scope, period, or maximum value of the contract under which the order is issued. (This authority was originally set to expire in September 2016).


Section 832 addresses DCAA access to Contactor&amp;rsquo;s Internal Audits.&amp;nbsp; DCAA is now required revise its guidance on access to internal contractor audit reports.&amp;nbsp; DCAA is also required to document all requests for defense contractor internal audit reports.&amp;nbsp; This &amp;ldquo;documentation&amp;rdquo; must include: (i) analysis that access to the internal reports are necessary to complete evaluation of the contractor business systems; (ii) a copy of the correspondence requesting such access; and (iii) the contractor&amp;rsquo;s response to DCAA.&amp;nbsp; &amp;nbsp;This final version that ended up in the Act is much more contractor&#45;friendly than the proposed senate version, which would have required DoD contractors to provide their internal audits as a condition of approval of the contractor&amp;rsquo;s business system.&amp;nbsp;


Section 852 addresses the expansion of FAPIIS.&amp;nbsp; The Federal Awardee Performance and Integrity Systems (FAPIIS) was established in 2010 with the goal of it being the sole resource for information about the business ethics of those competing for federal contracts. It includes determinations of responsibility, debarment/suspensions, defaults etc.&amp;nbsp; Section 852 now requires offerors to include information in FAPIIS about parent companies, subsidiaries or successor entities so that the integrity of the entire corporation can be considered.&amp;nbsp; As written, it is seemingly unclear whether this applies to all parent and subsidiary entities at all levels, or whether it is only those direct affiliated companies that will have to be reported.&amp;nbsp; If it is the former, this will be a problematic requirement for large corporations with many subsidiaries, some of which may have minor infractions that may be considered in unrelated evaluations of the offeror.


Section 864 addresses the allowable costs of contractor compensation.&amp;nbsp; The compensation cap of $763,000 remains in place, for now.&amp;nbsp; However, by May of this year the Comptroller General is required to submit a report to Congress on the impact of reducing the allowable costs of contractor compensations to either the salary of the President of the United States, or the Vice President.&amp;nbsp; This also requires that the Comptroller General undertake an analysis to determine how many contractor employees have compensation above those of the President and Vice President.


Section 867 addresses bid protest statistics.&amp;nbsp; The Comptroller General must now provide in its annual report to Congress &amp;ldquo;a summary of the most prevalent grounds for sustaining protests in the preceding year.&amp;rdquo;</description>
      <dc:subject></dc:subject>
      <dc:date>2013-03-19T04:41:07+00:00</dc:date>
    </item>

    <item>
      <title>Proposed Washington State Debarment Regulations for State Goods and Services Contractors Could Have Unintended Impacts on State Public Works Contractors</title>
      <link>http://www.oles.com/blog/entries/proposed-debarment-regulations-impacts-on-state-public-works-contractors</link>
      <guid>http://www.oles.com/blog/entries/proposed-debarment-regulations-impacts-on-state-public-works-contractors#When:05:22:22Z</guid>
      <description>Recently, the Washington State Department of Enterprise Services (DES) published a set of proposed regulations (Proposed WAC Ch. 200&#45;305) intended to establish the process for contractors who may be subject to contract debarment under the recently enacted procurement reform legislation (Chapter 39.26 RCW, which took effect on January 1, 2013).&amp;nbsp; The new procurement reform legislation (specifically RCW 39.26.200) gave the Director of DES authority to debar a contractor from consideration for award of state contracts based upon a number of different causes.&amp;nbsp; DES&amp;rsquo;s proposed regulations attempt to define the procedures for debarment, as well as the authority, extent and impact of contractor debarment.&amp;nbsp; While a number of the proposed regulations are equitable and consistent with RCW 39.26, some of the proposed regulations should be of serious concern to not only goods and services contractors, but also public works contractors.&amp;nbsp; Of greatest concern should be those regulations dealing with the impact of a DES debarment.&amp;nbsp;
First, the proposed regulations attempt to expand the effect of debarment to both state contracting and subcontracting.&amp;nbsp; Despite the fact that RCW 39.26 limits DES&amp;rsquo;s debarment authority to preventing a debarred contractor from consideration for award of state contracts as a prime contractor, DES&amp;rsquo;s proposed regulations would also prevent a debarred contractor from acting as a subcontractor on a state contract.&amp;nbsp; While the proposed regulations preventing subcontracting could be challenged in court as beyond the scope of DES&amp;rsquo;s regulatory authority, it would be far more preferable for this provision to be eliminated from the regulations now so as to prevent any confusion or disputes that may result.&amp;nbsp; This provision would not only cause problems to debarred contractors, but also could be problematic for non&#45;debarred contractors, as the latter would need to take care they were not subcontracting any work on a state contract to a debarred contractor.&amp;nbsp; In fact, if a non&#45;debarred prime contractor included a debarred subcontractor in its bid for a state contract, the prime contractor might have its bid rejected, or be at risk of a bid protest if awarded the contract, on the basis that the prime contractor&amp;rsquo;s bid was non&#45;responsive for including a debarred contractor ineligible to act as a subcontractor on the state contract.
A second major problem is that, even though the state legislature intended that DES&amp;rsquo;s debarment authority be limited to good and services contracts, the proposed regulations might also be interpreted to prevent a debarred contractor from bidding on state public works contracts.&amp;nbsp; This problem has arisen because the proposed regulations prevent debarred contractors from entering into &amp;ldquo;state contracts,&amp;rdquo; but provide no clear definition of what constitutes a &amp;ldquo;state contract.&amp;rdquo;&amp;nbsp; Public works contractors should be concerned that state agencies may attempt to apply the proposed regulations in a far more expansive manner than the legislature intended, namely state agencies may assert that a DES debarment results in contractor exclusion from all state contracts, including public works.&amp;nbsp; To avoid this overly expansive application, which also could be challenged in the courts, it is important that the proposed regulations be amended to clearly define &amp;ldquo;state contracts&amp;rdquo; as goods and services contracts only, and not public works.&amp;nbsp;
These are not the only issues in the proposed regulations that should be of concern to contractors. Contractors would be advised to review the proposed regulations (available online at http://des.wa.gov/SiteCollectionDocuments/About/rules/WSR_13&#45;02&#45;102_attachment.pdf) and submit comments during the public comment period (which runs through March 25, 2013).&amp;nbsp; A public hearing on the proposed regulations is scheduled for March 18, 2013.&amp;nbsp;
&amp;nbsp;</description>
      <dc:subject></dc:subject>
      <dc:date>2013-03-13T05:22:22+00:00</dc:date>
    </item>

    <item>
      <title>Legislative Watch: Congress Introduces the Hubzone Expansion Act of 2013</title>
      <link>http://www.oles.com/blog/entries/legislative-watch-congress-introduces-the-hubzone-expansion-act-of-2013</link>
      <guid>http://www.oles.com/blog/entries/legislative-watch-congress-introduces-the-hubzone-expansion-act-of-2013#When:05:20:42Z</guid>
      <description>The House of Representatives and Senate both recently introduced the HUBZone Expansion Act of 2013, H.R. 489 and S. 206 respectively.&amp;nbsp; The bill is designed to expand the HUBZone (Historically Underutilized Business Zone) program for communities affected by military base realignment and closure.&amp;nbsp; The bill would amend the Small Business Act to include as a base closure area for purposes of the HUBZone program of the Small Business Administration a military installation&apos;s municipality, county, census tract, or contiguous census tract having a total population of no more than 50,000, as determined by the most recent census. Both the House and Senate have referred the bills to their respective committees on small business matters.&amp;nbsp;&amp;nbsp;
The HUBZone Program was established by Congress in the Small Business Reauthorization Act of 1997. The program is intended to provide federal contracting assistance for qualified small businesses located in &amp;ldquo;historically underutilized business zones,&amp;rdquo; as a means to increase employment opportunities, investment, and economic development in those areas.&amp;nbsp; Locations currently classified as HUBZones can be found on the SBA&amp;rsquo;s website.&amp;nbsp;
To qualify for certification by the SBA as a HUBZone small business concern (SBC), a small business (as determined by the size standards in 13 CFR &amp;sect; 121.201) must be wholly owned by an Indian Tribal Government, a Indian Tribal Government&#45;owned Corporation, Alaska Native Corporation, Community Development Corporation, Small Agricultural Cooperative, or 51% unconditionally owned and controlled by one or more U.S. Citizens.&amp;nbsp; The wholly&#45;owned requirement is not necessary where the remaining ownership interest(s) are by U.S. Citizens or SBCs. The small business must also have its principal place of business in the HUBZone and have at least 35% of its employees residing in the HUBZone.&amp;nbsp;
Pursuant to the HUBZone Program, Contracting Officers may set&#45;aside contracts for competition restricted to HUBZone SBCs where there is a reasonable expectation that at least two responsible HUBZone SBCs will submit offers and an award can be made at a fair market price.&amp;nbsp; A sole&#45;source contract can be awarded to a HUBZone SBC where only one HUBZone contractor can satisfy a requirement and the anticipated contract price will not exceed $5 million for manufacturing contracts or $3 million for other contracts. &amp;nbsp;Alternatively, a HUBZone SBC is eligible for a 10% evaluation preference in procurements using full and open competition. &amp;nbsp;The regulations also require that HUBZone SBCs receiving a HUBZone contract allocate at least 50% of the contract funds incurred for personnel on its own employees or the employees of other qualified HUBZone SBCs.&amp;nbsp; HUBZone construction contracts also have specific subcontracting requirements that vary depending on whether the contract is for general or specialty construction.
The HUBZone Expansion Act of 2013 attempts to broaden the communities that are considered historically underutilized business zones.&amp;nbsp; I will be following the status of the bill and will post any pertinent updates on this blog.&amp;nbsp;
&amp;nbsp;</description>
      <dc:subject></dc:subject>
      <dc:date>2013-03-13T05:20:42+00:00</dc:date>
    </item>

    <item>
      <title>Tips on Navigating the System for Award Management for Federal Contractors</title>
      <link>http://www.oles.com/blog/entries/tips-on-navigating-the-system-for-award-management-for-federal-contractors</link>
      <guid>http://www.oles.com/blog/entries/tips-on-navigating-the-system-for-award-management-for-federal-contractors#When:22:47:04Z</guid>
      <description>The General Services Administration&amp;rsquo;s (GSA) launch of the System for Award Management (SAM) in late July 2012 has forced many federal contractors to adjust to a completely new system for reporting and tracking compliance issues.&amp;nbsp; SAM (www.SAM.gov) was designed to integrate three federal acquisition data systems &amp;ndash; Central Contractor Registration (CCR), Online Representations and Certifications Application (ORCA) and Excluded Parties List System (EPLS).&amp;nbsp; Since its inception, SAM has been plagued with numerous problems.&amp;nbsp; Users have reported that the system is slow to respond to requests, missing data fields and that the help desks are overwhelmed with inquiries from frustrated users.&amp;nbsp;
Because SAM is here to stay, at least for the near future, here are some tips for navigating SAM that all federal contractors should be aware of:
1)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If currently not registered in CCR, create an account on SAM so that you have an active record to be eligible for contract award and contract payments. Also, try to create your account during non&#45;peak hours if possible;2)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If already registered for CCR or ORCA, SAM registration is not necessary until it is time to update your registration. SAM should notify users when it is time to renew their registration via email 60, 30, and 15 days prior to the expiration of the record.&amp;nbsp; Because delays have been widely reported, contractors should update their information in advance of their expiration date to avoid being unable to correct inaccurate information at the time of impending award; and3)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Continue to monitor your business information on SAM and take measures to address any errors that occurred in the migration of your records. It is also good practice to follow up with your requests to SAM to correct errors in your SAM entry because of the various delays users have experienced thus far.</description>
      <dc:subject></dc:subject>
      <dc:date>2013-02-28T22:47:04+00:00</dc:date>
    </item>

    <item>
      <title>False Statements Accountability Act Liability for SDVOSB Fraud: Former Owner and Operator of Construction Company Sentenced for False Representations Made to Obtain Service&#45;Disabled Veteran&#45;Owned Small Business (SDVOSB) Set&#45;Aside Contracts</title>
      <link>http://www.oles.com/blog/entries/owner-operator-of-construction-company-sentenced-for-false-representations</link>
      <guid>http://www.oles.com/blog/entries/owner-operator-of-construction-company-sentenced-for-false-representations#When:00:21:26Z</guid>
      <description>On January 31, 2013, U.S. District Court Judge Mossman sentenced John Witty to pay a $206,844 fine, serve five years on probation, and perform 100 hours of community service at a veteran&amp;rsquo;s organization for knowingly making false representations to the Department of Veteran Affairs (&amp;ldquo;VA&amp;rdquo;) about being a service&#45;disabled veteran in order to obtain SDVOSB set aside contracts.
Witty, the former owner and operator of Gray Bear Construction pleaded guilty to one count of false statements and representations under 18 U.S.C. &amp;sect; 1001&amp;mdash;also known as the False Statements Accountability Act.&amp;nbsp; Witty, a veteran, admitted that despite knowing the VA had denied his application for a service&#45;connected disability (a prerequisite to being able to claim Service Disabled Veteran status), as owner and operator of Gray Bear Construction he falsely represented to the VA that his company was a SDVOSB.&amp;nbsp; As a result of Witty&amp;rsquo;s false representations, the VA had awarded Gray Bear Construction approximately $5,849,372 in SDVOSB set&#45;aside contracts, all of which the company was ineligible to receive.
The False Statements Accountability Act provides a broad and frequently used mechanism to penalize contractors for dishonesty in their dealings with the federal government.&amp;nbsp; A party runs afoul of the Act by knowingly or willfully making a materially false oral or written statement, representation, or omission (i.e. concealing information) to the federal government in any matter within the jurisdiction of an agency of the federal government.&amp;nbsp; Individuals convicted under the Act can face potential prison sentences of up to five years and fines of up to $250,000, while convicted corporations can face fines of up to $500,000.
Witty&amp;rsquo;s conviction stemmed from a blatant offense of the False Statements Accountability Act, and thus provides a clear example for contractors of what not to do.&amp;nbsp; However, the False Statements Accountability Act may also be used to penalize contractors that simply fail to require their employees to take reasonable steps to confirm the accuracy of information submitted to the government.
The Department of Justice&amp;rsquo;s (&amp;ldquo;DOJ&amp;rdquo;) prosecution of Witty also serves as a reminder of the current trend of the VA and DOJ vigorously investigating and prosecuting actual or perceived federal procurement fraud.&amp;nbsp; According to a press release issued by the DOJ, Witty is the 15th individual prosecuted during the past year for defrauding a VA program intended to provide preference to service&#45;disabled veterans for federal set&#45;aside contracts, and the VA is &amp;ldquo;diligently investigating others elsewhere who have similarly defrauded this program and expect additional prosecutions.&amp;rdquo; Accordingly, government contractors should ensure they are verifying the veracity of statements or submissions made to the federal government.</description>
      <dc:subject></dc:subject>
      <dc:date>2013-02-23T00:21:26+00:00</dc:date>
    </item>

    <item>
      <title>Saleemi v. Doctor’s Associates, Inc.: the Washington Supreme Court Heightens the Burden for Parties Appealing Confirmation of an Arbitration Award</title>
      <link>http://www.oles.com/blog/entries/wa-supreme-court-heightens-burden-for-parties-appealing-arbitration-award</link>
      <guid>http://www.oles.com/blog/entries/wa-supreme-court-heightens-burden-for-parties-appealing-arbitration-award#When:06:59:18Z</guid>
      <description>On January 17, 2013, the Washington State Supreme Court issued a decision in Saleemi v. Doctor&apos;s Associates, Inc., addressing whether a party who does not seek discretionary interlocutory review of a ruling ordering arbitration in Washington and invalidating a contractual choice of venue clause must demonstrate prejudice arising from the trial court&amp;rsquo;s order compelling arbitration in order to challenge the ruling on appeal from a judgment confirming the arbitration award.&amp;nbsp; The Court held that if a party waits to seek discretionary review of an order compelling arbitration on grounds of venue, damage limitations, or choice of law until after the arbitrator&amp;rsquo;s award, the party must show prejudice in order for an appellate court to address the merits of the party&amp;rsquo;s challenge.&amp;nbsp; The effect of the decision may be to cause further delay and costs to litigants by encouraging parties to seek interlocutory appellate review of orders compelling arbitration to avoid being faced with the higher burden of establishing prejudice that would accompany a subsequent challenge to an arbitration award. &amp;nbsp;On the other hand, Saleemi may also encourage parties to resolve important procedural issues at the outset of the arbitration, and thereby avoid the lost time and resources that inevitably are incurred when an arbitration award is vacated.
In Saleemi, plaintiffs entered into three franchise agreements with the defendant to own and operate three franchises in Washington.&amp;nbsp; The franchise agreements provided that any disputes would be arbitrated in Bridgeport, Connecticut, under Connecticut law, but stated Connecticut Franchise Law would not apply to franchises located outside of Connecticut. &amp;nbsp;After a dispute arose, the plaintiffs filed suit in Pierce County Superior Court.&amp;nbsp; A superior court judge found the choice of law and forum selection clause unenforceable and entered an order compelling arbitration in Washington, under Washington law, and with no limitations on damages&amp;mdash;contrary to a provision in the franchise agreements. &amp;nbsp;The defendant did not seek discretionary review of the Superior Court&amp;rsquo;s ruling and plaintiffs ultimately prevailed at the arbitration.&amp;nbsp;
The defendant then sought to vacate the award, primarily on the grounds that the trial court&amp;rsquo;s initial order compelling arbitration was in error.&amp;nbsp; The trial court denied the motion to vacate and the defendant appealed. &amp;nbsp;The Court of Appeals concluded that even if the trial judge&apos;s order was incorrect, the defendant had not shown prejudice and was not entitled to relief.
The Washington Supreme Court concurred with the Court of Appeals and held that where a party fails to seek discretionary review of an order compelling arbitration, the party challenging the order must show prejudice as a condition of relief from the arbitration award.&amp;nbsp; The Court reasoned that this approach promotes the prime purposes of arbitration, speed and convenience, while allowing a truly aggrieved party to obtain relief.&amp;nbsp; Thus, the Court analyzed whether the Defendants had been prejudiced by: (i) the application of Washington law to the dispute, (ii) the arbitrator&amp;rsquo;s ruling that there would be no limit on damages, and (iii) the fact that the arbitration was conducted in Washington rather than Connecticut.&amp;nbsp; Finding the defendants failed to prove any prejudice, the Court affirmed.&amp;nbsp;
Justice Madsen issued a concurring opinion, agreeing with the result, but disagreeing with the majority&amp;rsquo;s new prejudice standard.&amp;nbsp; Justice Madsen opined that the majority&amp;rsquo;s prejudice standard encourages motions for interlocutory discretionary review, which in turn causes delay, contravening the goal of arbitration as providing an efficient, swift form of dispute resolution.&amp;nbsp; Justice Madsen went on to note that it should be rare to permit discretionary review of such orders as it causes unnecessary delay to the arbitral process.&amp;nbsp; Thus, parties should not be penalized for failing to seek review that generally should not be granted.&amp;nbsp; Instead, Justice Madsen argued de novo review of a court&amp;rsquo;s order to compel arbitration is the proper standard of review and in accord with both Washington precedent and case law in other jurisdictions.
While it remains to be seen whether the Saleemi decision will affect litigants&amp;rsquo; behavior, there is a possibility that the decision may increase the frequency of interlocutory appeals, resulting in delays and increased costs associated with arbitrating a dispute.&amp;nbsp; As Justice Madsen&amp;rsquo;s concurring opinion points out, the majority decision incentivizes parties to seek interlocutory review of a court order to compel arbitration.&amp;nbsp; While parties may not always be inclined to do so, the prospect of facing a burden of establishing prejudice for failing to request discretionary review should be considered before acquiescing to a trial court&amp;rsquo;s order compelling arbitration.&amp;nbsp;
Though Saleemi may have the effect of increasing costs and delays due to more frequent interlocutory appeals, the majority&amp;rsquo;s analysis also discussed the potential time and cost savings associated with avoiding the need to vacate decisions based on procedural grounds that should have been addressed at the outset.&amp;nbsp; Thus, by heightening the burden for vacating an arbitration award on initial procedural grounds such as venue, the Court placed a barrier to litigants wasting significant amounts of time and money by throwing out an entire arbitration proceeding and award based on procedural issues that were likely known when the court issued the initial order compelling arbitration.&amp;nbsp;
Accordingly, while the Washington Supreme Court&amp;rsquo;s decision may have the effect of increasing time and costs in the early stages of an arbitral matter, the overall effect may be to lower the amount of arbitration awards that courts will vacate based on procedural grounds and/or deter litigants from attempting to take a second bite at the apple post&#45;arbitration.
&amp;nbsp;</description>
      <dc:subject></dc:subject>
      <dc:date>2013-01-31T06:59:18+00:00</dc:date>
    </item>

    
    </channel>
</rss>