Jump to content
The Wifcon Forums and Blogs

Don Mansfield

Members
  • Content Count

    2,519
  • Joined

  • Last visited

Posts posted by Don Mansfield


  1. 13 hours ago, formerfed said:

    This is getting away from the original thought and that’s use of a SOO and oral interactions.  The idea of a SOO is getting a variety of innovative and competitive approaches.  If only experience and past performance is evaluated, how do you differentiate among approaches?  What if one offeror uses a scrum methodology, another uses lean, and a third proposes.  Let’s say the offeror using scrum stumbles through orals with poor answers.  The one with lean can’t produce employees for the orals with extensive knowledge but their experience is good.  The third using kanban did a great job in orals but your CIO doesn’t know it well and isn’t comfortable.  How do you evaluate the three?

    1. What assurance would you have that the "approach" presented in response to the SOO would be the "approach" that the offeror would use in performing the contract?

    2. What evidence do you have that a person stumbling through an oral presentation with poor answers correlates to poor software development? Developing software and providing oral responses to technical questions are not the same skills. I would not expect software developers to impress at an oral presentation. I would expect them to be more like Elliot Alderson.

    3. What assurance would you have that the people answering the questions in an oral presentation would be the people developing the software?


  2. 2 hours ago, Witty_Username said:

    I don't have any experience contracting for agile software development, so maybe it's a gap in my knowledge of how an agile software development contract would be structured in the first place.

    Take a look at the Agile Contracts Primer. There are pricing arrangements starting on p. 25. Chapter 3 covers contract models. The primer is not specifically written for Government contracting, which is one reason I like it. The Government publications that I've seen on contracting for agile software development don't seem to fully let go of the traditional Government contracting mindset. "Soundness of approach"? Please. (No offense formerfed).

    Here's a must-read account of the realities of IT acquisition: https://medium.com/@EricHysen/lessons-learned-from-the-governments-biggest-attempt-to-fix-tech-procurement-bd2265421211


  3. 13 hours ago, Freyr said:

    Just for my own curiosity as someone still fairly new to being an 1102, if the effect is the same then what's the difference other than the course of action that produces it? If we waive the issue for everyone and just document the circumstances/reasoning then that would have the same effect as posting an amendment that removes it right?

    I think either way you would effectively be amending the solicitation (waiving the issue for everyone would be a constructive amendment). However, FAR 15.206 requires that you issue an amendment to affected parties and that the amendment contain certain minimum information. It's a procedural requirement.


  4. @Jacques,

    Thanks for your explanation. 

    1 hour ago, Jacques said:

    We should be suspicious of any interpretation of the DFARS that ASSUMES the DFARS language is a deviation from a requirement in the FAR.  These sorts of interpretations resemble those "revocation by implication" interpretations that are disfavored when interpreting a statute.  Rather, the normal rules on interpretation should be used, which includes harmonizing the language of the two regulations when they can be.

    I agree with this, but I think that you also need to keep in mind that when the DFARS conflicts with the FAR, it's usually by design. I'm not sure you can typically make that assumption when harmonizing conflicting statutes or regulations.

    Good discussion. Thank you.


  5. 1 hour ago, Jacques said:

    Do you really want to use this example?  "Customary"?  Where FAR 32.501-1(b)(2) permits "advance agency approval" to use a higher rate?  I just want to make sure this is the example you want to use before I start researching.

    No, you can skip the example. I think I'll be able to understand your concept of "deviation" if you just answer my last two questions. 


  6. @Jacques,

    Bad example. My apologies. Let's try this one instead.

    FAR 32.501-1(a):

    Quote

    The customary progress payment rate is 80 percent, applicable to the total costs of performing the contract. The customary rate for contracts with small business concerns is 85 percent.

    DFARS 232.501-1(a):

    Quote

    The customary progress payment rates for DoD contracts, including contracts that contain foreign military sales (FMS) requirements, are 80 percent for large business concerns and 90 percent for small business concerns.

    Is the DFARS deviating from the FAR? Yes or no?

    DFARS 201.304(a)(1)(iv) states that the DFARS contains "deviations from FAR requirements"? You wrote:

    Quote

    When the DFARS was modified to add this language, I took it to mean that deviations would appear in the DFARS proper rather than the newly-created DFARS PGI.

    What did you mean by that? What would be an example of a deviation in the "DFARS proper"?


  7. 20 minutes ago, USN1102 said:

    Semantics aside, if I understand correctly:

    1. As FAR 16.301-3(a)(2) is just repeating the requirement stated at FAR 7.103(e). DoD deviates from the FAR requirements for written APs as seen in  DFARS 207.103(d)(i)(B).  Therefore no written AP is required. 

    2. However, per Class Deviation 2019-O0001, the procurement in question being CPFF between $25M and $50M, my HCA approval is required prior to award.

    3. On a broader policy perspective, using the FAR 5.301/DFARS 205.303 public award announement example, there is a clearly traceable Part 5 "deviation" from $4M to $7M. The same approach can be used for my intial written AP query: DFARS 207 deviates from FAR 7.03 therefore, as a DoD 1102, I follow that written AP DFARS policy even though DFARS Part 216 is silent on deviating FAR 16.301-3(2) by the virtue that Part 7/207 "Acquisiton Planning" is more germane for all things written AP.

    1. Correct.

    2. Not sure. Can't access deviation.

    3. Correct. 


  8. @Jacques,

    Let's try this. FAR 5.301(a) states:

    Quote

    Contracting officers shall make information available on awards over $4 million (unless another dollar amount is specified in agency acquisition regulations) in sufficient time for the agency concerned to announce it by 5 p.m. Washington, DC, time on the day of award.

    DFARS 205.303(a)(i) states:

    Quote

    The threshold for DoD awards is $7 million. Report all contractual actions, including modifications, that have a face value, excluding unexercised options, of more than $7 million.

    Is DFARS 205.303(a)(i) a deviation from a FAR requirement? Yes or no?


  9.  

    11 minutes ago, Jacques said:

    There is no written deviation because there is no need for a deviation because the FAR doesn't require what you seem to assume it does.

    I'm not assuming anything. FAR 7.103(e) states:

    Quote

    A written plan shall be prepared for cost reimbursement and other high-risk contracts other than firm-fixed-price contracts, although written plans may be required for firm-fixed-price contracts as appropriate.

     


  10. Jacques,

    According to DFARS 201.301(a)(1), the DFARS contains--

                        (i)  Requirements of law;

                        (ii)  DoD-wide policies;

                        (iii)  Delegations of FAR authorities;

                        (iv)  Deviations from FAR requirements; and

                        (v)  Policies/procedures that have a significant effect beyond the internal operating procedures of DoD or a significant cost or administrative impact on contractors or offerors.

    The different thresholds for written acquisition plans in the DFARS are a deviation from FAR requirements.


  11. 22 hours ago, Sherrie Walters said:

    I currently work for the Department of the Navy and have a customer who wants my agency to contract for a no cost award. It is a service being performed for the Navy (removal of used oil) that the contractor will then be able to clean and sell for their profit. There will also be a requirement for a COR as the Government has a responsibility to review/confirm that the vendor has all of the proper Federal and State licenses required along with other duties they will need to perform. I have been getting conflicting information about the correct way to proceed. I need to know if it should be done as a purchase order "P" or contract "C" award. The only thing we can evaluate is past performance and responsibility which leans toward it being a "C" award. If anyone has done one recently for the Navy, please let me know how you awarded it. Thanks in advance.

    I don't think what you're describing meets the definition of "acquisition" at FAR 2.101, because you wouldn't be using appropriated funds. If that's true, then the FAR doesn't apply. I'm not saying it couldn't be done, just that the contracting would not be regulated by the FAR.

×
×
  • Create New...