Jump to content

ConMan411

Members
  • Posts

    17
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

1,364 profile views
  1. I’ll try the NCMA forums, thanks Vern.
  2. Do contractors not have a duty to say something or the right to investigate on matters? As a contractor the CO actions (if inappropriate) can cause consequences that jeopardize our award, obviously not what we want. For my concern posted, I really do not know what those consequences may have been - I am not an expert on this topic (clearly) but that would have been another question for me to find an answer to if I had to continue down that rabbit hole if it WAS a valid concern. Part of my duties on the contractor side is risk management for my company. With the opinions Vern provided, it sounds like my situation is on the program side and it's still within bounds - which is GREAT news for me, I will start beating up (collaborating professionally with) the program office instead. 😉 Again, thank you for the insights and your time, I do appreciate it! PS for Vern: It does appear it is on one line of accounting.
  3. Thank you, Vern! I have seen the Redbook referenced before; I will take the time to see if I can learn from that now that my curiosity has led me in that direction. I also appreciate your opinion that my concerns are likely unfounded, that lets me see it's just a rope and not a snake in our path.
  4. Hi Retreadfed - The funding is ALL at the Task Order level, but all Task Orders are added up and it goes against the ceiling values at the contract level. My comment is that with each funding action/modification (the contract level is modified to issue/incorporate the funding modifications to the Task Orders, the Task Orders are not modified without a contract level modification & each funding action that happens at the TO level is added as a new CLIN/SLIN/ACRN at the contract level because it is a new funding cite/accounting line), the CO is adjusting the ceiling of one bucket/line to accommodate the other bucket/line so funding does not exceed the ceiling for that particular one. In this case, Travel and ODCs require more ceiling so the CO is taking it out of our labor ceiling but doing a conversion to the penny of the funding each modification, instead of doing one realignment to meet the known needs of the program. I hope that provides more clarity. I appreciate your time and response.
  5. Thank you for the questions, Vern. The best question that I think you asked was if it was all on the same account line - which I know as fund cites - which would be certified through the certifying office. I think that is the thread for me to pull and if it is all on the same line. I will be looking into this today and this insight is very much appreciated. 1. When you say funding was "certified," do you mean that a finance office had certified that funds were (1) available and (2) had been reserved for a particular acquisition? Yes and Yes 2. When you say "converting the ceiling," do you mean reducing the ceiling for one purpose and increasing the ceiling for another? Yes and Yes (There are ceilings for each line or bucket (labor, material, travel, etc.) 3. Are all the funds from the same long-line account? I am going to verify this!! If the answers to those questions are yes, why do you worry that what you described might be improper? I am going to verify the previous question. Have you discussed this with the certifying accounting and finance office? If not, why not? I do not have access to that office as a contractor. What have you read about budget authority and obligation authority (not "contract authority")? I was reading GAO-16-464SP. Maybe it is not applicable to my situation, which is why I posted, but it was the closest written anything I could find for my situation. How this is being handled does not quite pass the sniff test because the execution is not following the awarded terms, the awarded ceiling values for each line are being adjusted with each round of funding, when it's known the values need to be further adjusted. Funding is being certified at a higher amount than the contract limits first and then we are issued a modification that has the funding and changed ceiling values, unless - as you point out - it is all on the same accounting line? But why have the ceilings for each different line/bucket on contract - which was evaluated and awarded in this fashion? Our CO is overworked and understaffed, probably under paid too, other corners are being cut and they like to get a bit creative with their solutioning - I just want to make sure we are not getting pulled into a situation that should not be happening on how they are allocating funding and changing the values.
  6. Scenario: Competitive Single award CPAF contract, Base +4 Option Periods. Mostly services but does have ceiling lines for ODCs, Travel, Materials, Labor, Award Fee at the contract level for each period separated out. Task Orders are issued against the contract, each Task Order has their own funding sources (so no co-mingling between TOs allowed). The owners of those funding sources are the ones required to "go find and certify their funds" - not the CO. Certain events happened and the government directed personnel to travel more than proposed, which increased the travel and ODC costs. The funding was always certified before costs were incurred. Concern: The contract level ceiling for those lines of travel and ODC have been surpassed, whereas the CO is just converting the ceiling from the labor to these lines with each incremental funding action at the contract level, without a proposal from the contractor, and after certified funding is received. At the top-level contract, there is a chart that shows what is the remaining value in that option year on each cost line, where normally is shown just a "From" "By" "To" chart, is now a "From" "By" By Realignment" "To", essentially realigning a portion of labor option value into ODCs and Travel. It is known the contractor needs increases in those lines (we are halfway into an option period), and eventually the labor ceiling will run out and there will not be any labor left, but I am not sure what regulation I can lean on to get the CO to stop doing this conversion; or find one that allows for it to happen. Request: I like to walk the straight and narrow line, so this does not sit well with me. Am I being overly conservative or is there regulation that may help encourage the CO to make the necessary changes to the contract level ceilings based on the current known needs? The best I could find is that it may scrape against Budget Authority (Contract Authority)?
  7. Thank you. We decided that the clause would be applicable, but not until we "invoiced" since Progress Payments are a financing tool. To comply, we reported zeros in SAM. I appreciate the responses.
  8. Thank you here_2_help, it confirms my understanding of the progress payments and how I view the total invoiced amount being zero. Maybe someone else knows more about the service reporting to see if the reporting is required when we are delivering something. We have other contracts that are services with a few materials that we report, but this task order is nothing at all like our "services" orders, this is delivering a complete system(s) built with COTS (if that matters).
  9. A task order awarded in 2016 has just now hit our Service Contract Reporting list in SAM. However, this is a FPIF task order and we are working on "progress payments" not "invoices" as we are delivering a system, with a ETA of 2021 for the DD250. I am a bit confused as to why we are now being asked to report on this task order, how its applicable since we aren't providing "services" and what amount I would use for "total invoiced" when we are using progress payments. Any advice? When I posed the question to our CO office, they referred me to the technical POC.
  10. I am not sure if this helps with the facts, and to be quite honest I feel I must be missing something major. Would Product Support be something totally different than the Service Agreements - even though neither have a set definition? Have I biased myself into thinking they are related? The language in the CDRL: "Service agreements for all hardware and software products delivered under this contract end no sooner than two calendar years after Final DD250." Language regarding product support in PWS: "The Contractor shall ensure all Product Support tasks are completed for the period from installation through Government acceptance (Final DD250) as detailed in PWS xxx." PWS xxx (Title being "Perform System Maintenance" has 2 subsections that state: xxx.1 The Contractor shall perform Level I and Level II system maintenance beginning at installation of system assets through the conclusion of the Final DD250. xxx.2 The Contractor shall repair and maintain the installed system to include collecting hardware and software repair data actions [CDRL DI-SESS-81315B - Failure Analysis and Corrective Action Report].
  11. Hi, It seems we have found ourselves in a situation where a CDRL is calling out an additional requirement that the Government wants but it is not stated in the PWS. Specifically, a longer duration of service agreements. The PWS does not include a specific requirement for "service agreements" only for "product support", which for Product Support has an end date stated through final DD250 in the PWS. The CDRL calls out "service agreements" with an additional 2 years after final DD250. There is no stated order of precedence, and both documents are called out as being incorporated into the contract, with the CDRL being listed first as an Exhibit and the PWS as an Attachment. My questions is: Can the Contractor be held accountable to deliver the additional duration of service agreements as listed in the CDRL if its not specifically called out as a requirement in the PWS or another area of the Contract? CDRL: DI-CMAN-81121, DATA ITEM DESCRIPTION: BASELINE DESCRIPTION DOCUMENT
  12. Postaward - Unfortunately all CLIN types were funded with 1 ACRN, I have inquired if we could go back and have separate ACRNS for each CLIN but was told by our former ACO it was too much work and could cause more confusion at this point (we are over a year into the program). We aren't shipping and invoicing in the most technical sense, we invoice for contractor use facilities (FFP) while requesting progress payments (cost based) for the build we are doing, which isn't to be delivered for a couple of more years. However, the facilities invoice was liquidated (payment withheld) by DFAS due to our ongoing progress payments on our delivery CLIN (FPIF) - since they share the same ACRN (per DFAS). I did speak with my new ACO since my original post, and there is concern that if we invoice for facilities again, it will get liquidated (payment withheld) and it will impact the master PPR numbers, it won't be balanced or something to that effect, maybe its the same issue that you bring up in your post. So I cancelled our most recent invoice due to this concern but I have not heard back from my PCO regarding the requested language/clarification so I am not sure what the PCO may decide to do yet on the entire issue. We would rather not submit PPRs or invoices until we have a clear understanding (or reach the end of our financial runway without payment), because I was also told that its very hard to get your money back once DFAS takes it, even if it was an error. I am on the contractor side so I have to temper down what I think should be able to happen to the limitations the COs have on what can actually be done. Any additional information or suggestions on the ACRN are welcomed as well. Thank you (and everyone else on here) for your input, it is appreciated.
  13. I guess I am hoping that if I can have the PCO put clear language in the contract, then that will tell the ACO how to enter it into the system, which should tell DFAS how to pay it. A wish and a prayer I suppose.
  14. ji20874 - Thank you for the language! Thanks to everyone for weighing in, I do appreciate it. I am going to see if the PCO could agree to the language offered by ji20874 and let him know it has also passed the Deviation Patrol check!
×
×
  • Create New...