Jump to content
The Wifcon Forums and Blogs

Witty_Username

Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by Witty_Username

  1. If it's designed correctly to take over the dull, dirty, and dangerous tasks (ok, maybe 1102s only deal with the dull, not the other two) and then to feed the right information to the 1102 at each decision point for their decision it could be great. AIs have a relative advantage in some areas and humans have a relative advantage in others (and those areas are likely to change as AIs get more advanced). But imagining giving the AI a big database of existing government contracts to learn from reminds me of this: Saturday Morning Breakfast Cereal - Rise of the Machines (smbc-comics.com)
  2. Interesting. In that case you might more broadly define the need as finding out whether some particular design will work. "Failing fast" could be seen as fulfilling the need to find out what works, make changes, and try again. Of course you can keep opening the aperture and question whether any particular platform satisfies the need for a specific capability, and whether any specific capability satisfies the need for national defense, etc. I certainly think there is likely to be value in speeding up PALT, however it is defined, as long as it isn't done at the expense of some other part of the overall process. Understanding where contracting (or any particular role) fits in to the overall process is a challenge, particularly in a contracting office that supports many different external "customers", but I think by trying to understand the goals of the level above you (e.g. contracting understands program goals, etc.) you're more likely to be able to optimize your own part of the process in a way that doesn't negatively affect the overall process. Alternately if you don't understand the higher level goals you may well optimize your own part of the process in a way that hurts the overall process.
  3. I agree. And maybe the PALT on some of the DIVADS or A-12 contracts was 72% faster than current PALT, and yet the need was never satisfied. So I wouldn't declare overall success based on how fast a contract was awarded that never actually fulfilled the need. But, easy for me to say, hard to actually do (except to be aware that we shouldn't overly-incentivize a narrow definition of PALT that doesn't include delivery/success)...
  4. Solicitation to award is a very industry-focused definition of PALT, because it represents the time when offerors have their resources tied up in a proposal. It's probably not particularly meaningful to a program office or contracting office at all. Incentivizes contracting offices to minimize proposal preparation time and to award without discussions. The time from receipt of a "procurement-ready package" to award is a contracting office focused-definition of PALT. Also probably not very meaningful to a program office who can't get a procurement-ready package in the door. Incentivizes contracting offices to not "accept" less than perfect packages, which may well actually increase overall requirement satisfaction lead time for the program office. The time from identification of a need through delivery is a program office-focused definition of PALT and probably what really should be incentivized. But it's too broad to really assign responsibility for to a single entity (assuming the program office and contracting office are separate) so it's probably hard to do.
  5. I don't think it's helpful to try to categorize every requirement as either a service or a supply. I think the must useful categorization of a license or subscription, or an equipment rental or short-term facility rental (all of which have alpha character "service" PSCs but don't really fall within the definition of a service) is "not a FAR Part 37 Service." I'm not saying it is a supply, I'm just saying it isn't a service in the FAR Part 37 sense of the word where an identifiable task is performed by a contractor employee (or the T. Peter Hill, "On Goods and Services", 23 REV. INCOME & WEALTH 315, Dec. 1977 sense of the word as a "change in the condition of a person, or of a good belonging to some economic unit, which is brought about as the result of the activity of some other economic unit, with the prior agreement of the former person or economic unit”; or Vern Edwards, "Performance Work Statements", The Nash & Cibinic Report Vol 35 Issue 2, Feb. 2021 sense of the word as "work done in order to change an existing state of affairs" either). Why is it useful to separate from FAR part 37? Because there are a bunch of extra things you have to do for a FAR part 37 service that don't make sense for a non-FAR part 37 service, like a determination of non-personal services, inherently-governmental determination, acquisition strategy for the acquisition of services, performance-based service acquisition, maybe pay in arrears, etc. and yet it still doesn't make sense to call an intangible license a "supply." The Section 809 Panel Recommendation 43 notes that it is "[unrealistic to categorize] all purchases as either supplies or services [...] often leading to contracts that are neither optimized nor appropriate for the solution being acquired." So, call it a non-FAR 37 service, use the alpha-character PSC, and create a contract optimized for the actual requirement, not any particular category.
  6. I think that's reasonable. If you look at the software PSCs the manual is clear that the difference between a D "service" PSC and a 7 "supply" PSC is whether the license is perpetual or not, and the same logic could apply in your case. I don't think the use of an alpha-character PSC as prescribed in the PSC manual makes it a service in the FAR 37 sense, but you may still run into issues with CAR coding (e.g. if it's not a service at all do you call it a is it a performance based service or not a performance based service?), and people who expect anything with an alpha PSC to be treated entirely like a FAR 37 service (payment in arrears, certification of non-personal services, QASP, etc.). But to paraphrase Vern Edwards quoting GAO paraphrasing Galileo: it doesn't matter what you call something, it matters what it is...
  7. I think any system that involves so many people (a quick Google search said 165,000 people in the DOD acquisition workforce alone in 2017) is going to display emergent behavior. Hire a huge workforce, give them a complicated set of rules and systems, then change the rules and systems continuously over their careers and I believe as new rules are individually interpreted, new concepts are adopted, old habits gradually fade, and new habits are formed you're likely to get very unpredictable outcomes.
  8. I read Kill Chain and found it relevant and interesting (I originally was going to say "I enjoyed it" but that's not quite right). I don't recall coming away with the impression that the DOD was necessarily against adopting AI (although within narrower areas it seems like pilots tend to think that aircraft need pilots, and tankers tend to think that the military needs tanks), but rather that congress, the military, and industry (all "in risk-averse bureaucracies that seem inclined to resist and stymie change at every turn") are too wedded to the idea of improving "platforms" instead of making more effective kill chains. I do think that there are plenty of people and organizations outside the DOD who are very concerned about including AI in the kill chain, and explaining why AI could make war more ethical, not less ethical, seemed to be a major focus of the book. The book has a great explanation and critique of the defense acquisition system; here's a key explanation for the situation for each major player. DOD: "The issue is not a lack of authority to go faster or take more risk, but that those who must exercise those authorities, bear those risks, and be accountable for the outcomes rarely use the authorities they have. [...] Those who do make decisions often lack the authority and incentives to make riskier decisions to get better outcomes." Congress: "Members of congress cannot ignore the things and issues that are likely to win or lose them votes. [...] The future does not vote, but the present certainly does. [...] Congress passed law after law to create new processes, offices, paperwork requirements, and official homework checkers to ensure that some bad thing that happened once would never happen again." (maybe he was paraphrasing from Vern Edwards “Frictionless Acquisition” Nash & Cibinic Report Sep 2020 Volume 34 Issue 9 “The principal acquisition statutes […] reflect congressional responses to various issues that have annoyed politicians from time to time.”) Industry: "[When there were no longer any existential threats and congress and the DOD began to focus on transparency, efficiency etc.] "The US government created incentives for defense contractors to do the wrong things, and that is often what happened. [...] Companies adapted. [...] Many companies resented making these changes, which they felt forced into. [...] Many of these major moves represented gains in efficiency, but often at a cost to the effectiveness and speed of innovation." So I felt like there were two major takeaways from the book: 1) We need kill chains with cutting edge AI instead of platforms if we want our military to remain relevant; 2) "It ultimately comes down to incentives" which are currently: short-term focus on spending money in their districts and avoiding the next procurement scandal from congress incentivized by voters; risk-averse compliance-focused behavior from acquisition professionals incentivized both by congress and internal leadership; and an industrial base that gives both parties what they ask for (replacement platforms and auditable accounting systems).
  9. I would say certifications (or education, or experience, etc.) are often used when there is no measurable objective for the contractor to achieve, as is often the case in professional support services contracts. So the logic is likely "we want someone to sit here and work on this, but we can't really define the outcome of the work, so we at least want someone trained/experienced/certified." I'm not saying it's necessarily a good idea, or a good way to contract, but that's generally the thought process I hear.
  10. I think it's worth considering that offerors make choices in their proposals, and if the government can tell them what they value the most it can help them make the choices needed to submit offers that the government wants. For example, if I want to buy a house I don't just tell the realtor "show me every house with at least three bedrooms" and then try to sort through the pile, I might instead say "A low price is most important to me, show me low-priced three bedroom houses" or alternatively "I want as much room as possible and I'm willing to pay for it" and now the houses the realtor shows me are more likely to be what I'm looking for, and I should have some similar houses to compare. When it comes down to choosing which house to buy I'll still decide whether the extra money is worth the extra space in the end, but I likely won't be deciding between a tiny foreclosure and a million-dollar mansion. Same thing when you buy a car, you don't go to a Ford dealer and drive a Focus, a Mustang, and an F-150; you tell them you are interested in a economy, or speed, or towing capacity, and then you drive some cars that meet your preferred criteria. You still make tradeoffs (is the additional towing capacity of an F-250 worth the price compared to an F-150) but they are showing you the vehicles that they think are most in line with what you are looking for. In the same way, if a solicitation says past performance is the most important factor and non-price factors are significantly more important than price potential offerors may decide to invest in a teaming arrangement with someone currently performing similar work, even if it is more expensive, rather than leaning their process to try to propose the lowest price they can. Now, the government will (ideally) get several proposals from offerors with solid past performance to make tradeoffs among, rather than a random collection of high and low priced offerors with widely varying past performance.
  11. If this is a supply contract I would suggest that if you know you will not drink the water until next fiscal year you don't have a bona fide need for the water this fiscal year. Supplies are generally a bona fide need in the period in which they are used. There are two exceptions to the bona fide needs rule for supplies: stock-level exception, which would absolutely apply if you purchase a year's worth of bottles and kept them in your fridge and drank one per month; and lead-time exception for deliver lead-time or production lead-time, neither of which seem applicable here. I'm not necessarily convinced that it is a supply contract though. Maybe you are really paying a service contractor to maintain the water supply in your various buildings as a service, not simply ordering a supply delivered, in which case if you have a statutory exception to the bona fide needs rule for severable services (10 U.S.C. § 2410a for DOD or 41 U.S.C. § 3902 for non-DOD).
  12. Looks like it is the same as "Agency Code" here: https://www.fpds.gov/downloads/top_requests/FPDSNG_Contracting_Offices.xls Here are some examples: “5700” (Air Force), “2100” (Army), “1700” (Navy).
  13. Not to hijack the thread, but on a semi-related note apparently DPC is saying as of March that to order from an existing Government contract a cardholder needs to be designated "by name" by the contracting officer who awarded the contract (source: https://www.acq.osd.mil/dpap/pdi/pc/docs/SmartPay3/Ref B - JAM GPC Role Descriptions_3-23-21.docx).
  14. This seems so basic, but I can't make sense of it: What does FAR 13.202 mean when it says "The clause at 52.232-39, Unenforceability of Unauthorized Obligations, automatically applies to any micro-purchase, including those made with the Governmentwide purchase card"? The interim rule in Federal Register Vol. 78, No. 120, subsequently adopted without change in the final rule, discusses the problem they are trying to solve (open-ended indemnification) and the proposed fix is "FAR 13.202, Unenforceability of unauthorized obligations in micropurchases, is added to require the clause at 52.232–39, Unenforceability of Unauthorized Obligations, to automatically apply to any micropurchase, to prevent violations of the Anti-Deficiency Act." That language, "automatically apply", is different from any other prescription I could find in the FAR, implying that it is not simply requiring that the clause be included in some type of order, but if it were not included in an order (or ordering agreement) through what mechanism would that clause apply to a vendor? Maybe it was just strangely worded (although the use of "automatic" wasn't a one-time thing, it shows up multiple times across the interim and final rules before ending up in the FAR) because later in the 2020 final rule implementing the increased micro-purchase threshold it says "The additional awards at or below the MPT would not require provisions or clauses, except as provided in FAR 13.202" which seems to acknowledge that an award below the micropurchase threshold would, in fact, require the clause as provided in FAR 13.202, and so maybe it is not "automatically" applicable at all?
  15. And to throw in a Tragedy of the Commons reference: while any increased risk of a protest accrues directly to the contracting officer, any corresponding future benefit of generally improved proposals by the company is spread across all contracting officers. As an aside I think this separate allocation of risk and reward is reducing the usefulness of past performance evaluations too, because each individual contracting officer is disincentivized to actually report poor or even average performance since they risk a challenge that increases their individual workload now, while the corresponding benefit of having accurate past performance information available for future source selections is spread across all potential contracting agencies. But back to the specific question of whether more or less information actually increases or decreases protest risk I think Vern Edwards said it best in a post on discussions (http://www.wifcon.com/arc/forum355.htm): "If you don't do first rate evaluations, then maybe you should hide the evidence, at least until the GAO or the Court of Federal Claims asks for it and gives it to the protester's lawyer. If you have incompetents conducting your business, then maybe you should hide their work as long as possible."
  16. I think you could make a reasonable case that the modifications you describe are within scope of the original order, and so wouldn't even require an exception to fair opportunity: I know there is a school of thought that says any increase in quantity is out of scope, but would seven additional phone lines change the competitive landscape that existed for the original 50? Would you have gotten a quantity discount had you originally solicited for 57? Would additional offerors have submitted proposals had they known about the additional work? Should potential offerors have known that personnel come and go and the number of phones was likely to vary and did they take that into account in their decision to propose or not, or in pricing their proposals? Of course if you know that Verizon doesn't bother to propose on requirements less than 51, or if the base contracts have quantity discounts at 10, 50, 100, etc., or you have some other reason to believe that the competitive landscape would have been different had you originally solicited for 57, then it would be out of scope, however a logical follow-on exception to fair opportunity seems straightforward for the scenario you describe.
  17. I reread it again, and GAO seems to accept DEA's position that the original BPAs were competitively awarded so calls don't have to be (but they didn't take a hard look at the original competition because that would have required a solicitation protest). It seems like this would only be plausible if the BPAs contained fixed unit prices and the DEA was using those competitively-established fixed unit prices to place calls using the procedures they set up in the original solicitation (i.e. rotation), which was not itself subjected to scrutiny. I don't think it is clear enough to firmly establish that GAO is ok with rotation of calls above the micropurchase threshold. I think BPAs can be a great tool where we can negotiate software licenses or other terms & conditions up front and allow distributed ordering, particularly by credit card holders. Unfortunately I think the basically accidental use of some uncompetitive historical practices (e.g. treating it like an IDIQ and establishing a single BPA then placing non-competitive calls over the MPT against it) have caused agencies to restrict their use. By reinforcing good competitive practices we can keep this tool available for use.
  18. Again, since this is a beginner's forum I think it's important to be clear that the existence of a BPA, either single or multiple, has essentially no effect on the competition requirements of FAR Part 13 for each call. The concept of "rotating" sources likely comes from the FAR Part 13.203 which says micropurchases [including BPA calls] "shall be distributed equitably among qualified suppliers", effectively rotating them among BPA holders if there are multiple, so it is only applicable to micropurchase calls. There has been some talk that multiple BPAs with fixed prices could allow orders under $25,000 without further competition, but I don't think that is any different from use of standing price quotations under FAR Part 13.103, so again, it appears the existence of a BPA has no effect on the competition requirements for any individual call. So establish BPAs to enable distributed ordering, establish standing terms & conditions, etc. but not to sidestep competition. Vern Edwards said as much back in 2009 in the thread linked below: When a BPA is issued under FAR Part 13, calls against the BPA valued in excess of the micropurchase threshold are subject to the rules in FAR 13.104, esp. paragraph (d), and 13.106. See 13.303-5( c). Generally, that means that you should get three quotes for all calls at or below $25,000. If a call will be for $25,000 or less and you have enough BPAs to obtain three quotes from BPA-holders, you can seek quotes from them exclusively. If the call will exceed $25,000, then you must synopsize and consider all quotes or offers received prior to award. In short, the existence of a Part 13 BPA does not eliminate the need for competition for calls in excess of the micropurchase threshold.
  19. I see where FAR 19.502-2(b)(1) could be read to limit the application of 19.502-2(b) to "products" but (a) and (c) both refer to services and 19.502-2(b) refers you to both 19.502-2(c) which explains why "products" bears special mention (i.e. nonmanufacturer rule) and to 19.203(c) which says "For acquisitions of supplies or services that have an anticipated dollar value exceeding the simplified acquisition threshold […]" so it would seem like a stretch to me to read 19.502-2(b)(1) to limit application to supplies only, when set-asides for services are mentioned so often elsewhere and there is a reasonable explanation (need to explain nonmanufacturer rule) for why products are specifically called out.
  20. Since it sounds like you're DOD, the Department of Defense Source Selection Procedures dated 1 Apr 2016 add the requirement for acquisitions over $100 million that "the Agency head shall appoint, in writing, an individual other than the Procuring Contracting Officer (PCO) as the Source Selection Authority (SSA)."
  21. Since the NMCARS has acquisition strategy/plan templates with specific questions for each paragraph, I think an often-overlooked key point is to answer the specific questions they ask in each paragraph. Surprisingly often we'll overlook something they explicitly ask for, like an explanation of the PSC in paragraph 1.1. Another recommendation: Don't necessarily default to Bottom Line Up Front (BLUF) writing in an acquisition plan. Sometimes you need to apply persuasive writing techniques to lead the reader/approver along the path that leads to a decision. If you start with a BLUF that the reviewer wasn't expecting, or is non-preferred (e.g. the contract will be T&M), then the reviewer may immediately start forming roadblocks in their mind before you even begin to justify the decision. On the other hand if you start together with the reviewer on a statement that you both agree on either because it is a fact (e.g. "FAR 16.601(c) states that […]") or because it is a supported conclusion from a previous paragraph (e.g. "as market research, described in paragraph 1.3, demonstrated […]") then take the reader one step at a time through the logical steps that lead to your conclusion (e.g. "therefore T&M is the appropriate contract type") they will either have to agree with you (and approve your document) or at least they will have to point out the specific step in your logic chain that they don't agree with, which will make it easier for you to revise your document (or your conclusion) to come to an agreement.
  22. Do you really need to create your own IDIQ? Could you just do individual task orders instead under an existing 8(a) BIC GWAC like 8(a) STARS, using either direct awards or logical follow-ons if necessary? I'm assuming that by creating your own single-award IDIQ you expect to eliminate or streamline some of the requirements to award each task order. Are there other ways to achieve that same goal, maybe a single program acquisition strategy that allows for multiple task order awards using the same process?
  23. I agree that there are situations where use of a SOO, oral presentations, and real past performance evaluation makes sense to select the best offeror. But once you've selected the best offeror what would the resultant contract look like? You say it would likely be labor hour, so at that point you've got a set of pre-priced labor categories working to achieve what contractually-defined objective/outcome? Will the SOO have to be turned into a PWS with measurable objectives (by the Government or the offeror? Before or after award?), or will the contractor just be providing the labor hours to work on whatever the Government asks them to do? 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.
  24. This would be a good time to refer back to your market research and consider not only whether the change would alter the competitive landscape (i.e. 15.206(e) "additional sources likely would have submitted offers"), but also whether it would change cost drivers such that offerors who did propose might have chosen to propose in a different (and more beneficial to the Government) way had they known the details of the eventual requirement. It may be worth considering the possibility of solicitation amendments when you develop objectives for market research early in the acquisition planning process (if we're not careful sometimes our market research's only objective is "are two or more small businesses available" which wouldn't help with a solicitation "scope" question).
  25. Since one of the more useful definitions in trying to figure out whether a software license or a subscription or a rental or a lease or anything else is a supply or a service is the FAR 37 definition of service, which you quote, I think it is important to point out that the key part of the definition is "directly engages the time and effort of a contractor [i.e. an employee...] to perform an identifiable task", not the "primary purpose" that you highlight. In this example the provision of a backhoe only engages the time and effort of a contractor employee for about the same amount of time purchasing the backhoe might take, i.e. working the rental/sales counter and maybe delivering and picking up the item, therefore the amount of time and effort the contractor employee spends on an identifiable task (providing a backhoe) is the same for a rental as for a purchase. The vast majority of the cost associated with the contract is in the equipment, not in the identifiable task a contractor employee performs. Otherwise, by your logic, any supply purchase would be a service contract because the "primary purpose" is to provide some supply. In the FAR 47 transportation service example you are "directly engaging the time and effort of a [truck driver] whose primary purpose is to perform [the task of transporting something]. These two examples couldn't be more different.
×
×
  • Create New...