Fear & Loathing in Contracting
-
Content Count
57 -
Joined
-
Last visited
Recent Profile Visitors
4,597 profile views
-
thank you- yes I have read through these- and since we are buying more 6 1/2 years worth of a requirement at one time and there are no options- sure looks like a multi-year contract to me. When I raised this with my supervisor, he said no way it was multi-year since it was not approved by Congress. I went to the Policy folks at HQ and they agree with me... but then legal came back and agreed with my supervisor. We are all at a loss at this point and are open to some other opinions hahaha!
-
How the contract is classified will drive what type of approvals I will have to pursue from those above me.
-
yes sir
-
The following has triggered quite the debate at work: We have a 6 1/2 year year Foreign Military Sales (FMS) requirement. It will be a "C Type" contract with no options. It will be funded 100% upfront with non-expiring FMS funds. Will this be a multi-year or multiple year contract?
-
Has anyone recently used FAR 15.102 oral presentations in any source selections? If so, what were your experiences? The good, bad, and the ugly. How did you use them? As a substitute for written information? Just to augment written information? If you have used them (or are simply just aware of any) do you know of any prior/sample RFP's you could direct me? Thanks
-
Is anyone aware of the existence of any studies connecting the adjustment of key variables in the source selection process to improvements in acquisition outcomes? After digging around, so far the only one I was able to find was a DEC2015 NPS report entitled, "RELATIONSHIP OF SOURCE SELECTION METHODS TO CONTRACT OUTCOMES: AN ANALYSIS OF AIR FORCE SOURCE SELECTION." It is actually very good and useful; but it would be great if there was any more out there. Also- is anything like this being pursued as a research topic at any traditional universities? In other words, are there any non-DoD/Agency
-
This is an ACAT program so requirements are are controlled via the JCIDS process. As this is to be a production contract, its requirements must be driven by an approved CPD, which in this case is an Army CPD. The USMC requirements trace back to specs that they are sending to the Army PM folks who then blend it into their docs and then say- no impact on our stuff- ok. And since we are talking about several 100 M here, with USMC covering a bit more than half- they of course want to be part of the source selection process. Specifically, they want folks on the eval boards. Further complicatin
-
I am an Army Contracting Officer in charge of the source selection for the production of an Army system. Since it always looks good for the program management folks to reach out to the other services (demonstrates you understand the “big picture”), this has occurred. In this case, the USMC wants to “be part of the procurement.” On the contracting side, it has always been our position to attempt to accommodate where it makes sense and when it does not jeopardize our core objective of meeting the Army mission. Now in the current situation, the participation of the USMC is considerable. Their des
-
Clarification: The contractor would have agreed at the time of the original award to provide the increased rights, but the price would have been much higher. The customer business decision balanced the price (at the time) against identified benefits and made the business decision not to purchase the increase rights.
-
thanks Seeker. I had posted prior to your post- from my end anyway- so we cross posted.
-
There are multiple software and data rights clauses on the prime contracting including DFARS 252.227-7013, 252.227-7014, 252.227-7015, & 252.227-7027. I have been particularly focused on DFARS 252.227-7014(b)(4) "...may be modified by mutual agreement.." How though does this solve the scope issue?
-
The following scenario pertains to a major system that is in the final stages of a "smart" shutdown and its related primary development contract. The original large sole source contract was awarded 3 years ago. A critical system component is a piece of software that the contractor asserted as exclusively developed with IR&D funding and having Restricted Rights. At the time, the Government made the business decision to accept the software with these rights. Since then, the program has been placed under Smart Shutdown and the contractor and PM have had some conversations on purchasing the so
-
The term "embryonic requirement" was probably not the best choice of words. I meant to convey that it is very early in the source selection process. The requirement is actually "moderately mature." It is for a configurable software solution that serves to integrate/coordinate/co-configure capabilities across a family of systems. Most of the family member systems are either in the last steps of development or sustainment. Even "moderately mature" is a bit of a loaded term. The PM group (who is driving this RFI) has been designated as the "Trail Boss" leading all the systems groups that need to
-
Software
-
RFI. It basically asks about whether your SW can do X, Y, Z, etc... and then asks to elaborate on certain aspects of the SW. Responders submit a white paper & fill out a supplied grid chart. RFI has since closed and there were more than a dozen respondents. Customer now wants to "evaluate" the responses and "down-select" to no more than 3. These 3 will be invited into a lab setting to demo their SW. Based on lab results, observations, SW performance capabilities/limits, etc... the customer will then use this info to help flush out/adjust the requirement.