Jump to content
The Wifcon Forums and Blogs

jtolli

Members
  • Content count

    70
  • Joined

  • Last visited

Everything posted by jtolli

  1. Types of orders

    I learned many years ago that a "call order" was an order placed under a BPA. Don't remember if I actually learned that as part of training, or if someone just told me that. I have found that many people in contracting today aren't familiar with that term however. The GSA FPDS-NG Data Element Dictionary still refers to BPA orders as a "Part 8 BPA Call" or "Part 13 BPA Call".
  2. SIg Sauer

    Yes, I looked it up in the DoD Electronic Document Access (EDA) system.
  3. SIg Sauer

    The first order to satisfy the minimum order guarantee was issued at the time of contract execution.
  4. What do GS-1101s do?

    When I worked for the Army, I was an 1101. We were liaisons between the end customers, and the contracting office. We advised customers on procurement policies, assisted them in preparing documentation (Performance Work Statements, Independent Government Cost Estimates, Justifications & Approvals, etc.) by reviewing/editing their submittals. We also served as CORs for the non-personal services contracts. Finally, we were the Government Purchase Card holders for the organization. Our Army organization was assimilated into a new DoD level Agency that was stood up. Within this Agency we still have 1101 that do much the same thing that we were doing in the Army. Myself, I moved into the contracting office, still as an 1101, doing a lot of things that I did as an 1101 for the Army, but now on a much larger scale.
  5. It depends on the specific software. Some (most) software licenses are perpetual. Some software licenses are term licenses.
  6. Key Personnel in Solicitations

    Key personnel language in a PWS drives me crazy. Some of the things the customer puts in would seem to be unenforceable. It just so happens I got a new requirement in today that I am looking at. Here are some excerpts for key personnel. "Substitutions of proposed Key Personnel shall not be allowed for one-year after award, except under extreme circumstances." "Replacement of Key Personnel can be accomplished under the following circumstances: Death Serious, prolonged illness, the onset of which post-dates the contractor’s submission of that Key Person’s resume to the government. In the case of a Key person who was a Contractor employee when the Contractor submitted his or her resume to the government, the Key Person leaves the Contractor’s employment for reasons other than retirement and does not commence work for a subcontractor on this contract or for the contractor after a hiatus." "Failure to replace a Key Person pursuant to this clause and without a break in performance of the labor category at issue is a basis for default termination, as are Key Personnel proposed not performing this contract (e.g., the Offeror is unable to hire one or more of the Key Personnel it proposed). Offerors are responsible for conducting due diligence to ensure that Key Personnel proposed will perform on this contract should the Offeror receive the award. Offerors may propose Key Personnel who they do not employ at the time the offer is submitted, but failure of such proposed Key Personnel to commence work on this contract will be deemed a prima facie showing of the Offeror’s lack of adequate due diligence and reflect poorly on business integrity and responsibility."
  7. DFAS- Contractor Owed Interest

    I "think" the calculation is done by DFAS, it may even be automated I don't know. I do know that the contracting office does not do it. I also "think" it is paid automatically. This is based on what I have seen in payment systems, after an invoice with interest has been paid out. In todays world of IT, I would think that is all automated.
  8. Government uses contractors SOW

    I think it's important to note if the "contractor" who is preparing the SOW is doing it under an existing contract. See Viereck, B-237726, March 20, 1990. "The organizational conflict of interest provisions on which the Army relies are intended to assure that the government receives unbiased advice when it employs a firm --"the contractor"-- to prepare specification used in the competitive procurement of items. Viereck, however, was not hired by the government to prepare the specifications here."
  9. Official FAR Site

    illzoni, The only reason I caught those differences is because there was some debate at my agency as to whether a Limited Source(s) Justification should be labeled a "Limited Source Justification" or "Limited Sources Justification". Yeah, I know it is minor, and there are much bigger things to worry about, but it was just something that came up one day, and I discovered the difference between the two websites. It does make you wonder if there are other differences however, and if maybe they may be more significant. I know of no one who uses the acquisition.gov website for FAR research, and everyone I know uses the Air Force site. Even when I went to DAU training, they gave us the reference to the Air Force site.
  10. Official FAR Site

    I don't know if I would call them discrepancies, but I have noticed differences. For example, compare FAR 8.405-6. On the Air Force site it is titled, "Limited Sources". On the acquisition.gov site it is titled, "Limiting Sources". Similarly, see FAR 8.405-6©(2)(i) which, on the Air Force site, says, "...and specific identification of the document as a “Limited Source Justification.”" On the acqusition.gov site it reads, "...and specific identification of the document as a “Limited-Sources Justification.”". Those are just a couple of small variances I have noted. I like the Air Force site better, as the font is larger, which is easier on my old eyes.
  11. I have been tasked with doing research to determine why it is beneficial to the government to prohibit a vendor from submitting a proposal as a prime contractor, and also being a subcontractor to a different prime (or primes) who submits a proposal. This would be for a single-award IDIQ contract. I can't imagine what the downside is of having a vendor do this. Any thoughts?
  12. Thanks for the input Jacques. Based on the research I did, I could find nothing that prohibited restricting a prime from also being a sub to another prime in their proposal. But you did bring to light some interesting information with FAR Subpart 9.6. You bring up a good question regarding, "Can a sub team with multiple primes?" I also asked myself that same question yesterday. While doing my research I did find some GAO case law regarding subs teaming with multiple primes. These cases generally involved the requirement for Certificate of Independent Price Determination (FAR 52.203-2), and allegations of price collusion. I think Don asked the question that gets right to the point; What would be your justification for including the restrictive provision? My recommendation to my boss was that we not do it, unless we have some valid reason to do so, which I do not know about.
  13. Thanks for the input Retreadfed. This requirement is for IT support services. We expect ro receive numerous proposals, so I do not expect that we will receive a proposal from a vendor as a prime, who would also be the sub on a large number of the other proposals. Therefore adequate price competition should not be an issue. I asked my boss why would we want to prohibit a vendor from submitting as a prime, and also be a sub on a different vendor's proposal, and her response was , "why would we not want to prohibit it?"; find some justification to prohibit it.
  14. Thanks Joel. We have thought about the conflict of interest issue, but isn't that a contractor issue for them to sort out, versus something the government needs to be concerned with?
  15. Authorities Delegated to COR

    If I was a COR and I saw a contractor employee doing something that could cause injury to themselves or others, I would tell them to stop work, and then contact the CO. Whether that is permissable or not I would worry about later. I wouldn't allow policies and procedures to stand between me, and doing what is right. Doing the right thing is sometimes more important than doing things right. I acutally had this happen many years ago where I witnessed contractor employees on a contract (not construction) I was COR for, working in a confined space without having the proper prootective equipment, or the equipment to test the combined space for hazards. I verbally ordered the employees to to stop work and get out of the manhole until they were later told differently. They did get out, and I went and informed the CO immediately of what I had done. He agreed with my course of action, and issued an "official" stop work order in writing.
  16. FAR 13.104(b)

    As I understand the scenario as presented by JDYoung, and I have seen people do this before, you have a requirement for an item and you ask vendors who you know don't sell that item if they will give you a quote, of course the vendor tells you that they don't sell the item, so you ask them to send you a "no bid" or "no quote", and you then consider that "no bid" as a quote. Here is a specific example. You have a brand name requirement for a Dell lap top. You get a quote from Dell for the lap top. You then go to 2 other vendors who ypu already know are not Dell authorized resellers, and do not sell Dell lap tops. You ask them to send you a "no bid", and then say you solicited from 3 vendors, and only got one quote.
  17. Contractor Manpower Reporting

    CMRA = Contractor Manpower Reporting Application. The CMRA is a web based application developed by the Army in order to collect data on services that they contract for. Section 807 of the National Defense Authorization Act of 2008 required DoD to provide an annual inventory of contracted services to congress. The other services were using FPDS data to develop their inventory. More recently DoD has gone to standardized systems accross the board. They are calling this the enterprise CMRA (eCMRA). In reality it is the same web based application that the Army developed, now being used by the other services.
  18. Contractor Manpower Reporting

    Sounds like you are a contractor. I work for the Government, and have been using the CMRA for a few years. Have you tried e-mailing the CMRA help desk? Here is what I can tell you based on my experience. I don't believe you can create any sort of "enterprise" login for the CMRA. One of the limitations I noticed with CMRA, at least on the Government side, is that once an individual (COR) "claims" a contract, then only that individual can view the specifics of that contract. There is no way to transfer the contract to anyone else. So if the person who claimed the contract moves to a new job, then their replacement is out of luck as far as using the CMRA to do any research on that contract. I would imagine their are similar limitations for those individuals with a contractor or subcontractor role in the application. As for your questions regarding administering components, contracting organization, etc., are you referring to the NDAA Elements section? If so, that is not the contractors responsibility to complete, so you need not worry about it. As stated on the CMRA Contract Details screen, "Note: COR/COTRs and Contracting Officers are responsible for entering NDAA data. Contractors are not responsible for this data.". I am not surprised that you have got little to no information from the contracting office, in my experience contracting officers and specialists know very little about the CMRA as they typically don't use it. You would be better off asking the COR for the contract, as COR's do the bulk of the data input and review on the Government side. But I will also say that many COR's don't fully understand the CMRA, and in my experience many don't use it at all. As for training, I have not heard of any such training, and to be honest don't see a need for training, it is a pretty straight forward system to use.
  19. Funny or tragic? Part I

    In my experience a lot of people tend to confuse the various justification documents and formats from different parts (6, 8, 16) of the FAR. The Army's Computer Hardware Enterprise Software and Solutions (CHESS) program contracts are also Part 16 contracts, but the ordering guides instructs you to prepare justifications using the FAR Part 8 format. I just ran across a question on the Ask A Professor site when an individual asked about preparing Class Brand Name Justifications for Part 8 buys, and the answer given was that it is possible in accordance with FAR Part 6. Here is a link to that particular Q&A: https://dap.dau.mil/aap/pages/qdetails.aspx?cgiSubjectAreaID=3&cgiQuestionID=120988
  20. Good stuff sdvr! I had never ran accross that on the SEWP site before. Thanks!
  21. Also see this thread: http://www.wifcon.com/discussion/index.php?/topic/2675-three-year-pop/ I tend to use GSA as my yard stick for software maintenance now. I see how the specific product is classified on GSA. Does it fall under Special Item Number (SIN) 132-32 or 132-24? Assuming the product is on GSA of course. Based on that, I make my decision on whether it is a product (paid up front), or a service (paid in arrears). While that is not an authoritative source, it does give me some backup information that I can use as a rationale for making my decision.
  22. Three-year PoP

    If you are talking about software versus hardware maintenance, then the rules could be different. Software maintenance is more well defined. GSA has definitions for software maintenance as a product and software maintenance as a service. Many of the DoD Enterprise Software Initiative (ESI) blanket purchase agreements (BPAs) also now incorporate a definition on software maintenance as a product and software maintenance as a service. For Army customers, the Army Computer Hardware Enterprise Software and Solutions (CHESS) office also has came up with a definition of software maintenance as a product and software maintenance as a service. All of these definitions would indicate that software maintenance as a product can be paid for up-front, and I would opine that as a product the term could span more than 1 year. However, software maintenance as a service could not be paid for in advance, and in my opinion could not span for more than 1 year.
  23. Three-year PoP

    We wrangle with this issue all the time, and are currently dealing with it on a particular buy. The question seems to boil down to are you purchasing a supply (product) or a service? Is it a maintenance plan, or an extended warranty? See GAO Decision B-249006 where they say you can pay for warranties in advance, but not maintenance contracts. As far as what the SEWP vendor telling you about 1 year support agreements for HP equipment being gone, I don’t believe it, unless it is something that very recently came about (as in within the past few weeks). HP still has a 1 year support option available through GSA. HP is also a SEWP vendor, and when they quote on SEWP they will only allow you to pay monthly or quarterly in arrears, and will not accept up-front payment. Other SEWP vendors will want up-front payment for HP support however. See this related discussion: http://www.wifcon.com/discussion/index.php?/topic/2501-it-hardware-maintenance-supply-or-service/?hl=hardware
  24. I am very familiar with this issue, as I deal with it at least weekly. The issue I deal with is not only purchasing a "maintenance agreement" when you purchase the hardware, but then also renewing the agreement upon expiration of the initial agreement. Unfortunately it is a murky area. If you look at GAO Decision B-249006, GAO seems to draw a dividing line between maintenance and warranty based on whether periodic maintenance is provided under the agreement. However, if you are familiar with these IT equipment maintenance agreements, then you know that most only provide a break-fix type of arrangement. ji20874 provides a very good example when comparing these to health insurance. If you look on GSA Advantage!, you will typically find these classified under Special Item Number (SIN) 132-12 (Equipment Maintenance). If you look at the terms and conditions for the schedule they are on, you will typically find that these cannot be paid for in advance, but the vendor must bill in arrears, which is typical for services versus products. Whether this type of agreement is considered a product or a service does have some ramifications. For those of us who work for the Army, we have to do Service Contract Approvals (SCA) for service contracts. So, if these maintenance agreements are in fact classified as a service, then that mandates an SCA be completed. On the Army SCA form one of the FAQs is, "Is a Form required when a supply is purchased that also includes a service such as maintenance?" The answer given is, "The Form is applicable to “service contracts,” i.e. “tasks to be performed” rather than “supplies to be delivered.” If a product is being purchased and it comes with a “service,” such as a warranty, then the Form is not required. (However, a contract specifically for ongoing maintenance of equipment, vehicles, etc., does require a Form.)" Also, if the agreement is classified as a service, then up-front payments cannot be made, and payment needs to be made in arrears. Also, if these are services, then can we purchase multi-year (e.g. 5 year) agreements using 1 year funds? Obviously no. But if they are classified as a product, then we probably can purchase a multi-year maintenance agreement, and pay for the entire term up front.
  25. In my experience it has always been standard practice for potential new contractors to attempt to recruit incumbent contractor employees to come work for them if they get awarded the contract. This is nothing new. I would guess most incumbent contractors have come to expect this to happen. In fact I have seen some instances where incumbent contractors have their employees sign no compete agreements in an attempt to prevent their employees from swtiching over to a competitor who they will most likely compete against for the contract requirement. Also keep in mind that it is entirely up to the incumbent contractor employee whether they wish to go to work for a new employer (contractor) or stay with their current employer. Again in my experience, employees working for small contractors usually will be very interested in keeping a job and going to work for the new company. A lot of the big companies however have work elsewhere that they can move their employees to. But again it is up to the employee to decide what is best for them.
×