Jump to content
The Wifcon Forums and Blogs

Don Mansfield

  • Content Count

  • Joined

  • Last visited

Blog Entries posted by Don Mansfield

  1. Don Mansfield
    DoD implemented a Clause Control Policy in 2015 that would require the same degree of transparency in the development and use of "local clauses" by the military departments and defense agencies as FAR and DFARS clauses (see PGI Case 2015-P003 and attached). Specifically, local clauses would be subject to publication for comment in the Federal Register and codified in the Code of Federal Regulations (CFR). However, not a single local clause has been incorporated in the CFR since the new policy was implemented. At the same time, there seems to be a lot more requirements in statements of work that don't have anything to do with describing work, but read a lot like a FAR or DFARS clause. Some of it is even prescribed in agency supplements to the DFARS. What's going on here?
    The Acquivores discuss https://www.youtube.com/watch?v=fK6GKDEqAhM&ab_channel=DonAcquisition
    2015-P003 DFARS PGI Text LILO.doc
  2. Don Mansfield
    1.000 Scope
    The purpose of this post is to promote The Acquivore Podcast.
    1.001 Definitions
    As used in this post—
    Acquivore means an animal whose mental diet consists chiefly of Federal acquisition. The term includes acquiholics, acquiphiles, acquinauts, acquidemics, and acquimaniacs.
    The Acquivore Podcast means a video podcast dedicated to learning about, discussing, and thinking about Federal acquisition.
    1.002 Applicability
    This post applies to all acquivores.
    1.003 Policy
    Acquivores shall, to the maximum extent practicable, tune in to The Acquivore Podcast to enhance their professional development.
    1.004 Procedures
    (a) Starting February 10, 2021, and continuing every other Wednesday thereafter, the acquivore shall—
    (1) Watch The Acquivore Podcast live from 5:00pm to 7:00pm Pacific Time by going to http://donacquisition.adobeconnect.com/acquivorepodcast;
    (2) Participate in discussions during The Acquivore Podcast; and
    (3) Ask questions during The Acquivore Podcast.
    (b) If an emergency or unanticipated event prevents the acquivore from watching The Acquivore Podcast live, the acquivore shall watch a recording of the podcast on Don Acquisition’s YouTube channel. The acquivore shall also like and subscribe to the channel.
    (c) The acquivore may, at their discretion, earn a certificate for continuous learning points from The Acquivore Podcast, provided they—
    (1) Provide advance notification of intent to earn a certificate, in writing, no later than one calendar day prior to The Acquivore Podcast by sending an e-mail to don_at_donacquisition.com;
    (2) Complete a research assignment; and
    (3) Obtain a grade of 70% or higher on a 10-question multiple-choice quiz based on information in the research assignment.
  3. Don Mansfield
    “How do you do simplified acquisition?” is a common question I hear from acquisition personnel that are more familiar with using FAR part 15 procedures to solicit offers and award contracts. The question presupposes that there is a regulated set of procedures that one must follow—similar to what is prescribed in FAR part 15, agency FAR supplements to FAR part 15, agency guidebooks on source selection, and the decisions of the Government Accountability Office (GAO) and Court of Federal Claims (COFC). Fortunately, that is not the case. Rather, FAR part 13 (Simplified Acquisition Procedures (SAP)) expressly states that certain procedures contained in FAR part 15 (Contracting by Negotiation) do not apply and requires contracting officers to “use innovative approaches, to the maximum extent practicable, in awarding contracts using simplified acquisition procedures.” FAR 13.003(h)(4). An underlying message in FAR part 13 is to not bring your FAR part 15 baggage with you. The following list presents thirteen reasons why SAP is simpler than the competitive negotiation procedures of FAR part 15.
    See complete list.
  4. Don Mansfield
    Scenario: Acme Corporation responds to two different RFPs issued by the Government. RFP 1 is for commercial items and contains the untailored version FAR 52.212-1, Instructions to Offerors--Commercial Items. Acme responds to RFP 1 with Proposal 1. RFP 2 is for noncommercial items and contains FAR 52.215-1, Instructions to Offerors--Competitive Acquisition. Acme responds to RFP 2 with Proposal 2. The deadline for submission of the proposals for both RFPs is June 30. Both of Acme's proposals were submitted on time.
    On July 15, Acme realizes that it made an estimating mistake and has priced the proposals lower than they should have. Acme asks the contracting officer for each RFP if they can submit a revised proposal, since award has not yet been made. Both contracting officers refuse Acme's request. Acme then asks to withdraw both proposals.
  5. Don Mansfield
    A former student of mine is part of a team conducting a survey to gauge interest in a Mentoring program for Acquisition. If you work in federal acquisition and work for a federal agency (including DoD), please take a few minutes to complete the survey. The more junior you are, the better. From the team:
  6. Don Mansfield
    I invite you to participate in a plain language writing contest. To participate, re-write the passage below in plain language and post your entry in the comments section below. Here is the passage:
    You may submit more than one entry. I will score your entry for readability using the Dale-Chall Readability Formula. 
    Your entry must communicate the essential information in the passage to be acceptable. The acceptable entry with the lowest adjusted readability score will be the winner. I will send the author of the winning entry a copy of The Write Way: The S.P.E.L.L. Guide to Real-Life Writing by Richard Lederer and Richard Dowis.
    I will also give an award for the most humorous entry. I will send the author of the most humorous entry a copy of The Play of Words: Fun & Games for Language Lovers by Richard Lederer.
    The deadline for receipt of entries is December 27 at 4:30 pm Pacific Standard Time. If an emergency or unanticipated event interrupts normal Wifcon processes so that entries cannot be received on the Web site designated for receipt of entries by the exact time specified in the invitation, and urgent requirements preclude amendment of the invitation, the time specified for receipt of entries will be deemed to be extended to the same time of day specified in the invitation on the first work day on which normal Wifcon processes resume.
  7. Don Mansfield
    I was recently perusing some of the recent final rules issued by the FAR Council when I came across a statement that I found interesting. In responding to a comment concerning the applicability of TINA to task and delivery orders, the FAR Councils stated that TINA applicability is to be determined when negotiating a basic IDIQ contract, as well as when negotiating subsequent orders under the contract. A description of the comment that they received read as follows:

    The Councils' response was as follows:

    (See FAR Case 2008-012, Clarification of Submission of Cost or Pricing Data on Non-Commercial Modifications of Commercial Items (75 FR 13414)).
    My initial reaction was "Good, they got it right." However, I was not satisfied with the complete lack of explanation other than that this information was "commonly understood." "It is commonly understood?" is the equivalent to saying "Well, everybody knows?", which is not an answer that I would accept from a student nor is it one that the public should be accepting from the FAR Councils. Further, the FAR Councils' use of "commonly understood" raises the question: Commonly understood by whom? Based on my experience, "commonly debated" would be a more apt description.
    Task and Delivery Orders are "Contracts"
    By stating that TINA applicability determinations must be made at the task and delivery order level, the FAR Councils have, perhaps unwittingly, admitted that task and delivery orders are "contracts" as defined at FAR 2.101. Consider the requirements for obtaining cost or pricing data at FAR 15.403-4(a)(1):

    If TINA applies to task and delivery orders, then task and delivery orders must fall into one of the three enumerated categories. A task or delivery order issued by the Government is certainly not a subcontract, so (ii) is out. A task or delivery order under a contract is not a "written change in the terms of a contract", so they do not meet the definition of "contract modification", thereby eliminating (iii). Thus, task and delivery orders must be "contracts."
    However, one cannot reasonably describe this information as "commonly understood" either. Consider the following statements made in FEATURE COMMENT: Contesting Task And Delivery Order Awards At The COFC--Policy Implications Of A Choice Federal Courts May Soon Have To Make (51 NO. 20 Gov't Contractor ? 174). In discussing the automatic stay provisions of CICA, the author writes:

    The author, seemingly indecisive, also writes:

    This author is not alone. In FEATURE COMMENT: Acquisition Reform Revisited--Section 843 Protests Against Task And Delivery Order Awards At GAO (50 NO. 9 Gov't Contractor ? 75) the authors put forth the following argument:

    I agree with the first author's assessment of the potential controversy that would ensue if the FAR Councils were to redefine "contract" to include task and delivery orders. If the FAR Councils were to propose such a rule, I would estimate that they would receive no less than 100 public comments.
    Where's the Cost or Pricing Data Clause for Task and Delivery Orders?
    If it's "commonly understood" that TINA applies to task and delivery orders, why isn't there a standard FAR clause for use in task and delivery order contracts that compels the submission of cost or pricing with a task or delivery order proposal when applicable? There's a standard FAR provision at FAR 52.215-20, Requirements for Cost or Pricing Data or Information Other Than Cost or Pricing Data (Oct 1997), that can be used to compel offerors to submit cost or pricing data when submitting offers for a basic IDIQ contract. There's also a standard FAR clause at FAR 52.215-21, Requirements for Cost or Pricing Data or Information Other Than Cost or Pricing Data?Modifications (Oct 1997), that compels submission of cost or pricing data when pricing contract modifications (if applicable). Where is "Requirements for Cost or Pricing Data or Information Other Than Cost or Pricing Data?Task and Delivery Orders"? Why not have offerors agree to submit cost or pricing data (if applicable) with subsequent task and delivery order proposals?
    TINA Yes, CAS No
    The Councils' response in the publication of this rule reminded me of an earlier response pertaining to the applicability of CAS to task and delivery orders accompanying a final rule on CAS (70 FR 11743-01). In that response, the Councils reached the opposite conclusion. The exchange was as follows:

    Thus, a determination of CAS applicability is made only when placing the basic IDIQ contract. If an IDIQ contract is subject to CAS, all orders under the contract are subject to CAS. If an IDIQ contract is not subject to CAS, none of the orders under the contract are subject to CAS.
    So, according to the FAR Councils, a contracting officer must determine applicability of TINA when awarding a basic IDIQ contract and issuing any subsequent orders, but need only determine the applicability of CAS once?when awarding a basic IDIQ contract.
    This raises another yet another question?how is a CO supposed to know this? Consider the rules for determining CAS applicability at 48 CFR 9903.201-1:

    By asserting that CAS determinations are not made at the task or delivery order level, the FAR Councils must be using a definition of "contract" that is different than what appears at FAR 2.101. What definition are they using and why does that definition exclude task and delivery orders? I don't get it.
    If the FAR Councils believe that task and delivery orders are "contracts" as defined at FAR 2.101, then they can clear up a considerable amount of confusion by including these types of orders in that definition. If they do that, why not add a standard FAR clause compelling submission of cost or pricing data (when applicable) with task or delivery order proposals? While they're at it, how about an explicit statement in the FAR stating that TINA applicability determinations are made at the task and delivery order level and another statement that CAS applicability determinations are not? Probably too much to ask.
  8. Don Mansfield
    To answer the title question--most likely yes, for DoD. A recent DFARS final rule, Procurement of Commercial Items (DFARS Case 2016-D006), added the following definition at DFARS 202.101:
    Since small business concerns are exempt from CAS, most small business concerns would fall within the definition. This has significant consequences because the final rule also added the following at DFARS 212.102(a)(iii):
    So, DoD contracting officers can use FAR part 12 procedures to buy both commercial and noncommercial items from most small business concerns. I admit that I did not appreciate the scope of this rule when I first read it. I would have expected more dancing in the streets by both small business concerns and DoD contracting officers. Maybe there was and I missed it.
  9. Don Mansfield
    Assume you are soliciting quotes for an item of supply. Suppliers A, B, and C each sell the item for about $100/unit. However, the probability of late delivery is different for each supplier. Supplier A has a 31% chance of delivering late, Supplier B has a 21% chance of delivering late, and Supplier C has a 4% chance of delivering late. There’s a 100% chance that all suppliers will deliver no later than one week after the delivery date and any damages due to late delivery will be negligible.
    Your solicitation requests that vendors quote both a unit price and a per-unit delivery incentive. The supplier can only earn the delivery incentive if delivery is on time. Otherwise, the Government only pays the unit price.
    Supplier A quotes a per-unit price of $71 and a $41/unit delivery incentive.
    Supplier B quotes a per-unit price of $65 and a $41/unit delivery incentive.
    Supplier C quotes a per-unit price of $59 and a $41/unit delivery incentive.
    Considering only the total amount the Government would expect to pay, which quote do you think is best?
  10. Don Mansfield
    I've chosen the winners of the Plain Language writing contest. The following entry from @Jamaal Valentine was the acceptable entry with the best readability score:
    The most humorous entry came from @apsofacto:
    There were some others I really liked that didn't win. If we slightly change @bentley78's entry, we get:
    Thank you all for participating!
  11. Don Mansfield
    Assume that you are pricing a firm-fixed-price contract using cost analysis. The prospective contractor has included a contingency of $100,000 in its cost proposal of the type described at FAR 31.205-7(c)(1):
    There is a 90% chance that this contingency will occur. If it occurs, there's a 100% chance it will cost $100,000.
    The prospective contractor can take Precaution A, which will cost $50,000. If the contingency occurs, Precaution A would reduce the chance of the contingency costing $100,000 to 30% (there would be a 70% chance the contingency would cost $0).
    The prospective contractor can take Precaution B, which will cost $75,000.  If the contingency occurs, Precaution B would reduce the chance of the contingency costing $100,000 to 10% (there would be a 90% chance the contingency would cost $0).
    The prospective contractor is free to take Precaution A, Precaution B, or do nothing. 
    What amount for this contingency would you allow in the contract price?
    You may ask for more facts if you'd like or ask to make an assumption. Do not fight the hypothetical. Enjoy.
  12. Don Mansfield
    It's been almost 10 months since the FAR Council issued the last Federal Acquisition Circular (FAC). The streak of inactivity will be broken on November 6 when FAC 2005-96 will be published. The FAC contains a single rule that removes the Fair Pay and Safe Workplaces Rule. But that's not what makes the rule so remarkable. Item 16 of the FAC makes changes to the provision at FAR 52.204-8 as follows:
       Notice something strange? See that link to a YouTube Video? That's really there. It's in both the html and pdf versions of the FAC. It is officially contained in the FAR. What is the video? I won't spoil it for you--click and find out.
  13. Don Mansfield
    I always thought that the FAR Matrix was a good idea that was poorly executed. To begin with, it's notorious for containing errors. Second, most of the entries in the "Principle Type and/or Purpose of Contract" columns are "A", Required when applicable, which means you have to look up the prescription anyway. Lastly, the matrix isn't going to tell you if your agency deviates from the FAR prescription, which DoD does a lot. As such, I created a matrix that I think overcomes these problems.
    A few things about the matrix:
    It contains every provision and clause in the FAR, DFARS, and in DoD Class Deviation memoranda. It doesn't have any "Principle Type and/or Purpose of Contract" columns except for a Commercial Items column. It contains the actual prescription of the provision or clause. For readability, I removed the number and title of the provision or clause in the block and just wrote "use this provision..." or "use this clause..." The identifying information for the provision or clause is already contained in the row. For DoD, it contains additional instructions for the use of FAR clauses that is contained in the DFARS or in a class deviation. This information appears in bold. If you work for a civilian agency, just ignore what's in bold. In the "IBR" column (Incorporation by Reference), there are no "N" entries for "no", with the exception of the provisions and clauses prescribed at FAR 52.107. This may cause some people to freak out, so I'll explain. FAR 52.102(c) states: Thus, if the FAR Matrix contained a "Y" in the IBR column, my matrix will also contain a "Y". If the FAR Matrix contained an "N" in the IBR column, or the provision or clause came from the DFARS or a DoD class deviation, then my matrix will contain a "Y*". The key at the top of the matrix contains an explanation for the "Y*" entry. If you're wondering how to incorporate a provision or clause that contains fill-in material or something the offeror must complete, see FAR 52.102(a) and FAR 52.104(d).
    You can see the matrix on the DAU Acquisition Community Connection. I'm open to suggestions for making it better. Also, I would like to think that it doesn't contain any errors. However, if you spot one please let me know. As an incentive, I will add your agency's provisions and clauses (the ones in Title 48 of the CFR) to the matrix if you point out a mistake.
  14. Don Mansfield
    It’s time we rethink our approach to the training problem. Our traditional approach is to dictate a blueprint of training classes that must be followed in order to obtain prescribed levels of certification. To put it in acquisition terms, we’ve been using a design specification. What if we were to use a performance specification instead? What might that look like? Before answering these questions, we should identify what it is we are trying to achieve with training.

    The purpose of training is to make the trainee proficient in performing one or more defined learning objectives by means of specialized instruction and practice. A learning objective consists of three parts—an action, a condition, and a standard. For example, someone new to federal contracting will likely receive training to select FAR provisions and clauses (action) given a set of facts about an acquisition and access to the FAR (condition) (the implied standard would be “correctly”). It follows that if an individual already behaves in the prescribed way under the prescribed conditions to the prescribed standard, then training would be unnecessary for that individual—they’ve already attained the learning objective.

    Under the “design specification” training model that we currently use, there is an implied assumption that an individual cannot attain the requisite learning objectives without following the prescribed blueprint of training classes. Further, there is no method of demonstrating the attainment of the requisite learning objectives prior to the prescribed training classes. As a result, everyone must take the required training classes, regardless of individual necessity. Considering the resources involved in carrying out such a program, this is an expensive proposition.

    While the implied assumption of the “design specification” training model may prove true in some cases, a more reasonable assumption would be that some individuals need to follow the prescribed training blueprint and some do not. Those that do not would include those that have already attained the requisite learning objectives by other means and those that could without following the prescribed training blueprint. Thus, the challenge would be to identify those that don’t need a particular training class before requiring their attendance at the training class.

    What if we borrowed the thinking behind performance-based acquisition and applied it to the training problem (i.e., a “performance specification” training model)? That is, instead of dictating how the workforce is to attain requisite learning objectives, we specify the requisite learning objectives (performance outcomes) and method of assessment, and let the workforce decide how they are going to attain them. Some workforce members may choose a program of self-study, others may study in informal groups, some contracting offices may develop their own ongoing training programs, etc. Still others may choose to follow the existing blueprint of training classes. Regardless of how one attains the requisite learning objectives, all are held to the same standard using the same method of assessment.

    For an illustration of how such a model might look, consider the profession of actuarial science. Beanactuary.org contains the following description:

    Like other top-ranked professions (such as law and medicine), one must pass a set of examinations to achieve professional status as an actuary. Unlike other professions, in actuarial science you’ll have the opportunity to work as an actuary while completing the examination process—employers often allow study time during working hours, pay exam fees, provide internships, and even award raises for each exam passed. Though, to get the best start on a rewarding career, many soon-to-be actuaries begin taking exams while still in college. Of those that do, most achieve associateship in three to five years. All candidates acquire a core set of knowledge from required preliminary exams. The preliminary exams and Validation by Educational Experience requirements are the starting points for an actuarial career.

    To attain an “Associate of the Society of Actuaries” (ASA) designation from the Society of Actuaries, one must pass exams in probability, financial mathematics, models for financial economics, models for life contingencies, and construction and evaluation of actuarial models. In addition, there is one required e-Learning course and a required one-day seminar in professionalism. After attaining the ASA designation, one typically pursues a “Fellow of the Society of Actuaries” (FSA) designation within one of six specialties: corporate finance and enterprise risk management, quantitative finance and investment, individual life and annuities, retirements benefits, group and health, and general insurance. To attain the designation, the FSA candidate must take 3-4 more exams unique to the specialty, complete four e-learning courses, and attend a three-day case-based fellowship admissions course that requires each candidate to deliver an oral presentation on a topic within the field. In case you weren’t keeping track, that’s a total of four days of required attendance in classrooms to achieve the highest designation in the field. In contrast, DoD contract specialists must attend 32 days of classroom training to attain the lowest level of certification.

    What if to attain level 1 certification in contracting, one had to pass exams in, for example: acquisition planning, contracting methods, contract types, socioeconomic programs, and contract administration, and attend a one-day seminar on ethics? After level 1, contract specialists would choose a specialty in which they would pursue Level 2 certification. Specialties would be, for example, major system acquisition, research and development contracting, construction and A/E contracting, service contracting, IT acquisition, acquisition of commercial items, contract administration, etc. To attain Level 2 certification, contract specialists would have to pass a series of exams unique to that specialty. For example, to attain Level 2 certification in service contracting, there would be exams on specification of service requirements, source selection for services, pricing services, and service contract administration. There could also be a Level 2 admissions course where the candidate would have to submit and present a paper on a topic related to their specialty.

    If nothing else, use of the performance specification training model would cost less than the design specification model currently in use. I would go as far as to say that, on the whole, the workforce would be at least as competent as it is now.

    What’s your opinion? We’d like to know.
  15. Don Mansfield
    In January 1944, the Office of Strategic Services, a wartime intelligence agency and predecessor to the modern Central Intelligence Agency (CIA), issued Strategic Services Field Manual No.3 (Simple Sabotage Field Manual) to its agents to aid the Allied war effort in Europe. The purpose of the classified document was to explain the technique of simple sabotage, outline its possible effects, and present suggestions for inciting and executing it. It introduced the concept of simple sabotage as follows:
    The manual goes on to describe two types of simple sabotage: destructive and nondestructive. Regarding the latter type, the manual explains that—       
    The manual has a section titled “Specific Suggestions for Simple Sabotage” that provides suggestions for how to execute simple sabotage for different targets. There are suggestions on how to innocently start fires in buildings, set off automatic sprinklers to ruin warehouse stock, change sign posts at intersections and forks, dilute gasoline with water, wine, or urine so it won’t combust, and other Dennis the Menace type hijinks. What seemed most familiar were the suggestions under “General Interference with Organizations and Production.” Here are a few:
                   The manual was declassified in 2008, but I suspect it fell in to enemy hands long before that. The question is, though, why is the enemy targeting Federal contracting offices?
  16. Don Mansfield
    I'm looking for feedback on a tool that I'm creating for DoD. Basically, it would be a single document that would contain the FAR, DFARS, DFARS PGI, and DoD Class Deviations. The concept is similar to that used in the General Services Administration Acquisition Manual (GSAM), where both regulatory (GSAR) and nonregulatory information is integrated into one document and distinguished by shading. The main difference is the document that I envision also contains the FAR. I've attached a sample of what an integrated FAR subpart 1.1, DFARS subpart 201.1, and DFARS PGI subpart 201.1 would look like. Take a look and let me know what you think. I'd appreciate any feedback, but I'm particularly interested in the following:
    1. Would you use such a tool?
    2. Is there a better way to distinguish between FAR, DFARS, and DFARS PGI text than the use of shading?
    3. Do you have any ideas to make the tool better (more useful)?
    Consolidated FAR, DFARS, DFARS PGI, DoD Class Deviations.docx
  17. Don Mansfield
    “When I use a word,” Humpty Dumpty said, in rather a scornful tone, “it means just what I choose it to mean—neither more nor less.”
    “The question is,” said Alice, “whether you can make words mean so many different things.”
    “The question is,” said Humpty Dumpty, “which is to be master—that’s all.”

    --Lewis Carroll, Through the Looking Glass

    When Better Buying Power (BBP) 1.0 was first issued in September 2010, then Undersecretary of Defense for Acquisition, Technology, & Logistics (USD(AT&L)) Ashton Carter used the word “tradecraft” when describing one of the five “areas” of BBP initiatives. The area was called “Improving Tradecraft in Services Acquisition.” The initiatives that were subsequently identified under this area were:
    · Create a senior manager for acquisition of services in each component, following the Air Force’s example
    · Adopt uniform taxonomy for different types of services
    · Address causes of poor tradecraft in services acquisition
    · Increase small business participation in providing services
    “Tradecraft” was also used by current USD(AT&L) Frank Kendall in the 2015 Defense Acquisition Performance Assessment:

    It would seem that both Carter and Kendall are using “tradecraft” to mean the knowledge and skills for a particular occupation. However, that’s not what “tradecraft” actually means, nor is it commonly used in that sense. According to Merriam-Webster online dictionary (www.m-w.com), “tradecraft” means “the techniques and procedures of espionage”. The Oxford English Dictionary (OED) online (www.oed.com), gave three definitions of “tradecraft” dating as far back as 1812:

    In “’Tradecraft’ Infiltrates the Language” lexicographer Neal Whitman describes the resurgence of “tradecraft” in the language:

    Whitman uses a quote from Agent Maya in the movie Zero Dark Thirty to illustrate its most common use:

    The article continues:

    Regarding the OED definition, Whitman explains:

    While it would not seem out of the ordinary to hear this use of “tradecraft” on an episode of Downton Abbey, the broad meaning of the word is virtually dead in Contemporary English. “Tradecraft” has settled into semantic idiosyncrasy. While I’m not above purloining a word from another field if I find no other word as apt, there are plenty of words that could have been used to describe the particular BBP area (“skill”, “expertise”, and “proficiency” come to mind). As acquisition professionals, we have a hard enough time communicating in the language of acquisition without adopting words from other fields (no matter how cool they sound). The Plain Language Action and Information Network (PLAIN) advises us to “understand your readers and match your language to their needs” (see http://www.plainlanguage.gov/howto/wordsuggestions/index.cfm). When choosing words, the objective should be to communicate, not to impress. Even if “tradecraft” meant what the authors of BBP thought it meant, its obscurity would still have made it a poor choice.
    Eavesdropping, making dead drops, drycleaning--that's tradecraft. Creating senior manager positions in charge of service acquisition, adopting a uniform taxonomy for different types of services, increasing small business participation in service acquisition--that’s not tradecraft.
  18. Don Mansfield
    In a earlier blog entry, I posted a draft version of the provision at FAR 52.212-1 tailored for simplified acquisition procedures and requested comments. First, I'd like to thank everyone who provided comments. I believe the final version (below) is an improvement over the draft. Second, Carl Culham suggested that I include instructions on how to incorporate a tailored version of FAR 52.212-1 into a solicitation. I thought that was a good idea, so I will include instructions in this entry. Third, Vern Edwards tailored FAR 52.212-1 for SAP using plain language. His version is clear and easy to read, which may cause some of your lawyers and policy folks to balk at using it. If that's the case, you may want to refer them to plainlanguage.gov so they can familiarize themselves with the Federal Government's policy on the use of plain language to communicate with the public. Vern's plain language version is also posted below.
    Incorporating a Tailored Version of FAR 52.212-1
    FAR 12.302(d) contains the following guidance regarding tailoring:

    According to the format prescribed at FAR 12.303(e)(2), the addendum to FAR 52.212-1 should be located with the solicitation provisions. The addendum should be clearly identified as such (e.g., "Addendum to FAR 52.212-1"). Carl Culham suggested, and I agree, that there should also be some kind of lead in statement that indicates that the version of FAR 52.212-1 in the addendum supersedes the version of FAR 52.212-1 contained in the FAR (e.g., "FAR 52.212-1 is replaced in its entirety by this addendum"). If using the streamlined solicitation for commercial items discussed at FAR 12.603, then you must include a statement that the provision at 52.212-1, Instructions to Offerors -- Commercial, applies to the acquisition and a statement regarding any addenda to the provision. The addendum should then be included in full text.
    FAR 52.212-1 Tailored for SAP
    Here's the final version of the provision at FAR 52.212-1 tailored for SAP:

    FAR 52.212-1 Tailored for SAP (Plain Language Version)
    Here's Vern's plain language version of FAR 52.212-1 tailored for SAP:

    I hope some of you will try these provisions. If you do, let us know how it goes.
  19. Don Mansfield
    I recently gave a course on simplified acquisition procedures where I was again confronted with the use of the provision at FAR 52.212-1 Instructions to Offerors--Commercial Items in requests for quotations (RFQs) issued pursuant to FAR part 13. (We discussed this issue in the Wifcon forum before here and here). The problem is that the provision was not designed for use in RFQs under FAR part 13. To begin with, the provision requests "offers"--not quotations--which are different (see the definition of "offer" at FAR 2.101). The provision also includes elements that don't apply when requesting quotations under FAR part 13 (e.g., a minimum offer acceptance period, the dreaded late proposal rule, instructions on how to withdraw offers, a statement of intention to award without discussions, debriefing information, etc.). Although the FAR permits tailoring of FAR 52.212-1, it is typically just incorporated by reference without tailoring. I've wanted to create a version of FAR 52.212-1 tailored for SAP for a long time and I promised my last class that I would. As such, I submit my first draft to the Wifcon community for comment below. I've also created a side-by-side comparison of the untailored version of FAR 52.212-1 and my draft version that you can access here.

    Please provide comments and questions below.
  20. Don Mansfield
    In Latvian Connection General Trading and Construction LLC, B-408633, September 18, 2013, the Comptroller General denied a protest of a solicitation issued by an Air Force unit in Oman for armored cable to be used at Thumrait Air Base, Oman. At issue was the Air Force’s decision to not automatically reserve the acquisition for small business concerns, which both the protester and the Small Business Administration (SBA) argued was required under the Small Business Act. The protester relied on 15 U.S.C. § 644(j)(1), which states:

    [Note: these thresholds have since been raised by the FAR Council. See FAR 19.502-2( a ).]
    The SBA implemented this statutory provision at 13 C.F.R. § 125.2(f)(1), which states that contracting officers (COs):

    The Air Force argued that the automatic reservation, which is stated at FAR 19.502-2(a), did not apply because the acquisition was outside the United States and its outlying areas. The Air Force relied on FAR 19.000( b ), which states:

    The Comptroller General sought the views of the SBA regarding the geographical restriction at FAR 19.000( b ). In its comments, the SBA argued that this regulatory “statement of policy” does not properly implement Small Business Act requirements. Further, the SBA noted that elsewhere the Small Business Act exempts certain provisions from applying outside the United States. Thus, if Congress wanted to place a geographical restriction on § 644(j)(1), it would have done so.

    Siding with the Air Force, the Comptroller General stated:

    This logic suggests that had the FAR Council exempted Kansas City, Missouri, from the application of § 644(j)(1), that would have been okay, too.
    The New SBA Regulations
    Fast-forward two weeks to October 2, 2013. The SBA issued a final rule amending its regulations governing small business contracting procedures (see 78 FR 61114). 13 C.F.R. § 125.2 was amended as follows:

    Although the amended SBA regulation seemingly put to bed the issue of the geographical restriction stated at FAR 19.000( b ), the FAR Council has taken no action to amend the FAR (see “FAR Open Cases Report” at http://www.acq.osd.mil/dpap/dars/far_case_status.html).
    Where are We Now?
    On July 14, 2014, Latvian Connection, LLC, (Latvian) filed a protest with the Government Accountability Office (GAO) (B-410081.1) of a State Department solicitation for spare and replacement parts for the United States Consulate General in Dubai, United Arab Emirates (Solicitation No. 3458493). One of the bases of the protest was the State Department’s decision to not automatically reserve the acquisition for small business concerns. The Comptroller General sought the views of the SBA. In a letter to the GAO, the SBA explained their position as follows:

    [Letter from SBA to GAO, dtd. 25 August 2014, RE: B-410081 Protest of Latvian Connection, LLC]. The letter went on to reference the changes to 13 CFR § 125.2 shown above. The protest against the State Department solicitation was subsequently dismissed on other grounds.
    On December 10, 2014, Latvian filed a protest with the GAO (B-410921) of an Army solicitation for the installation of canopy sunshades on Camp Arifjan, Kuwait (Solicitation No. W912D1-15-R-0004). Again, Latvian argued that the acquisition should have been automatically reserved for small business as required by the Small Business Act and the newly amended SBA regulations. Presumably understanding that they would be fighting a losing battle, the Army amended the solicitation to automatically reserve it for small business concerns and the protest was dismissed. The description block of the amendment contained the following statement:

    As it stands, overseas COs and small business concerns seeking overseas contracting opportunities are in a tough spot. Overseas COs must deviate from the FAR to comply with the Small Business Act and SBA regulations. Small business concerns seeking overseas contracting opportunities are dealing with contracting officers that are blissfully ignorant of the changes to the SBA regulations due to the longstanding geographical restriction stated at FAR 19.000( b ). It may take nothing short of a GAO protest to get overseas COs to pay attention to the amended SBA regulations.
    The ball is squarely in the FAR Council’s court. It needs to revisit FAR 19.000( b ) in light of the amended SBA regulations. If there is a legal argument for keeping the geographical restriction at FAR 19.000( b ), then the Office of Federal Procurement Policy should issue guidance to that effect to agencies. If there is no legal argument for keeping FAR 19.000( b ), then it should be removed. Sitting back and letting overseas COs and small business concerns fight it out solicitation by solicitation is not fair to either party.
  21. Don Mansfield
    In a recent DoD IG report, the Army Contracting Command was cited for its failure to perform "component assessments" on 23 contracts subject to the Buy American Act (see DoD IG Report No. 2015-026). The report states as follows:
    Not having ever heard of such a requirement, I checked the reference to this requirement, which was allegedly located in DFARS 252.225-7001( a )(3)(ii)(A). DFARS 252.225-7001 is a contract clause entitled "Buy American Act and Balance of Payments Program". The clause does not contain "( a )(3)(ii)(A)", but it does contain a paragraph "( a )". Paragraph ( a ) defines, for purposes of their use in the clause, the terms "Commercially available off-the-shelf (COTS) item", "component", "domestic end product", "end product", "foreign end product", "qualifying country", "qualifying country component", "qualifying country end product", and "United States". The paragraph does not require the contracting officer to do anything. In fact, it doesn't require that anybody do anything--it merely defines words and terms. The balance of the clause imposes an explicit requirement on the contractor in paragraph ( c ) and an implied requirement on the contractor in paragraph ( d ):
    Nothing in the entire clause requires the contracting officer to do anything. The terms "contracting officer" and "component assessment" do not appear in the clause. The term "component test" appears once--in paragraph ( b ) (see above). No duty of the contracting officer can reasonably be inferred.
    When read together with the provision at DFARS 252.225-7000, it is clear that any assessment of end item components should be done by an offeror when determining how to complete the certification in DFARS 252.225-7000( c ):
    I assume that the Army Contracting Command pointed out the flawed assumption that the IG had made when responding to the audit. Let me just check their response to this finding to be sure:
    Oh, well. Get ready ACC contracting personnel--you will soon be receiving a policy memo requiring you to take CLC 027 Buy American Act. And no, it does not contain guidance on how contracting officers are to perform "component assessments".
  22. Don Mansfield
    In competitive acquisitions, it is common for solicitations to require offerors to conduct surveys of their past and present customers using standard questionnaires developed by the contracting office. Offerors are typically instructed to send the questionnaires to their customers with instructions to send the completed surveys to the contracting office. This information is then used to evaluate the offeror past performance. In effect, individual contracting offices have shifted the burden for collecting information about offeror past performance to the public.

    The problem with this practice is that it is done without regard for the requirements of the Paperwork Reduction Act (44 U.S.C. 3501 et seq.) (PRA). The PRA imposes a requirement on Federal agencies to obtain approval from the Office of Management and Budget (OMB) before collecting information from 10 or more members of the public. 44 U.S.C. § 3502 defines “collection of information” as—

    As part of the approval process, 44 U.S.C. § 3506©(2)(A) generally requires that each agency—

    OMB approval of a proposed collection of information or recordkeeping requirement is manifested in the issuance of a valid OMB control number. FAR 1.106 contains a list of approved information collections and OMB control numbers relating to Federal acquisition. The list includes, among other things, solicitation provisions requiring offerors to provide certain types of information in their proposals to the Government. For example, the requirement for offerors to provide certified cost or pricing data or data other than certified cost or pricing data is approved under OMB Control Number 9000-0013. The approval granted by OMB is not permanent, which is why the FAR Council will periodically publish their intent to request an extension of an existing OMB clearance in the Federal Register and provide an opportunity for public comment. Denial of OMB approval would render the information collection or recordkeeping requirement unlawful and, arguably, unenforceable if contained in a solicitation provision. To this point, 5 CFR 1320.6 states:

    In addition to periodically requesting the extension of existing OMB approvals for collections of information, the FAR Council must address compliance with the Paperwork Reduction Act in FAR rules published in the Federal Register. Typically, the Federal Register notice will either state that the rule does not contain any information collection requirements or that any information collection requirements are currently covered by an existing OMB clearance. If the FAR Council is imposing a new information collection requirement, the notice will contain an estimate of the administrative burden and solicit public comments.
    One need only look at the nearest competitive solicitation to conclude that contracting offices don’t pay much attention to these requirements. Despite the public protection provision of the PRA, it is unlikely that offerors will exercise their rights for fear of reprisal. As a result, the public will continue to absorb this administrative burden—a burden that is ultimately passed on to the Government in the form of higher overhead costs.
  23. Don Mansfield
    Section 1331 of the Small Business Jobs Act of 2010 (Pub.L. 111-240) recognizes the significant opportunities that exist to increase small business participation on multiple award contracts and the ability of set-asides— the most powerful small business contracting tool—to unlock these opportunities. Under Section 1331, Federal agencies may: (1) set aside part or parts of multiple award contracts for small business; (2) reserve one or more awards for small businesses on multiple award contracts that are established through full and open competition; and (3) set aside orders under multiple award contracts awarded pursuant to full and open competition that have not been set-aside or partially set-aside, nor include a reserve for small businesses.
    You can download the article "Section 1331 Authorities: A Primer" by clicking here.
  24. Don Mansfield
    This morning I read two different threads in the Wifcon forum. In the first thread, the discussion centered on late Government payments. (See “Significant Delays in voucher review/approval”). Some of the participants shared stories of how the Government does not consistently respect contractual payment due dates. Because some contractors are reluctant to enforce their rights under the payment clauses of their contracts, the Government continues to take advantage of them. One poster put it this way:
    I was embarrassed for the Government after reading this thread. Then, I read the following advice (from a different poster) in a thread dealing with how the limitation on subcontracting clause is applied (see "Small bus Set Aside 50%, can pass part of that to another Small?"):
    The underlying message: “it’s ok to take advantage of the fact that the government does not enforce this right under the contract.” After reading this, it became clear that Government personnel really aren’t that different than contractor personnel. On both sides, there will be those that respect the rights of the other party under the contract and those whose behavior is guided by what they can get away with. I think we should all strive to be included in the former group. Those in the latter group have little right to cry foul when they find themselves on the opposite sides of a contract.
  • Create New...