Todd Davis

Other than trade professions, I've only expereinced the term while enlisted in the Air Force and typically refers to those at the E-4/E-5 level, which is well below a GS-13 level. https://usafofficer.com/air-force-enlisted-rank-structure/ I did locate a couple articles that refer to a journeyman level position being a GS-13. Both relate to law enforcement positions, so maybe the term is used in that profession and someone applied that term to contracting? https://www.govexec.com/management/2019/02/us-marshals-complain-system-unfairly-denies-them-promotion/154811/ https://www.osi.af.mil/OSI-Careers/Civilians/FAQs/

I don't think a degree is very useful. It seems that degrees are much easier to obtain today and probably take less effort and aptitude depending on the school. I’d rather see some sort of written and oral assessments that help determine the knowledge and experience a person has, as well as their accomplishments. I think these are better determinants of a person’s value to an organization.

Have you considered a Grants Managment Specialist (1109)? The ones you mention are also good ideas. I transition to the 0301 series (Miscellaneous Administration and Program) and have a role as a Chief of Staff, albeit in an acquisition organization. I'm not sure how many different contracting offices you've worked in or roles that you have but I would suggest looking at other agencies/offices. I know our agency values good business advisors in acquisitions.

I tried from my home home computer using Chrome. I get the error message that ji20874 gets. However, in the lower left hand side there is the word "Advanced." Click on that and you should get the option to proceed to the site. I did and after clicking "proceed" it took me to the DCAA site. Same thing with Firefox. Click on "Advanced" and then "Add Exception." With Internet Explorer, click "More Information" then "Go on to the webpage." I've also seen this before with other sites.

I'm from a civilian agency and was able to get on the ASBCA site earlier today.

Interesting. If filed with the GAO, it now costs now costs $350 to file a protest (as of May 1st).

I don't think either degree is necessary to advance in contracting. I completed my MBA because I had been focused on working in the private sector outside of Federal contracts between my current and former stints in Federal service. I apply very little of what I learned in getting the MBA to my work today in contracting. I also work with a couple people how have JDs. While some of that course work likely taught them skills that help them in contracting, I'm confident most of it didn't make them more expert at Federal contracting. I've known folks with advanced degrees that are not very good at contracting and others without any degree that are some of the best I've known. What I think matters more is hands on experience, learning from others, courses in specific aspects of Federal contracts, relevant certifications, and reading the FAR and other literature on the subject.

I don't have the answer, but if you haven't already, try contacting the responsible CO at GSA. Their contact information is in the schedules eLibrary. Also, there is general contact information for Schedule 70 at https://www.gsa.gov/technology/technology-purchasing-programs/it-schedule-70.

A proposed rule at 81 FR 88086 was published for comment on 12/6/2016 that would add a new language at 19.505 regarding performance of work requirements that address subcontracting limitations and the non-manufacturer rule. A final rule has not yet been published and it could change, or it might not even become part of a final rule. This is what is states regarding the compliance period. Also, changes to implement this were proposed to the clause 52.219-14, Limitations on Subcontracting, as well as the other set-aside clauses that include subcontracting limitations. "(b) Compliance period. A small business contractor is required to comply with the limitation on subcontracting— (1) For a contract that has been set aside, by the end of the base term and then by the end of each subsequent option period. However, the contracting officer may instead require the contractor to comply with the limitation on subcontracting by the end of the performance period for each order issued under the contract; and (2) For an order set aside under a contract as described in 8.405–5 and 16.505(b)(2)(i)(F), by the end of the performance period for the order."

For commercial items see FAR 12.303. For letter RFPs see FAR 15.203(e). If I recall correctly, I believe that some may use another format not specified in the FAR for construction, possibly a format established by a trade group. However, my memory could be failing me and I might be wrong. I don't believe FAR Part 36 specifies an alternative format for construction or A-E services. If the FAR says the UCF is not required for use and another part of the FAR does not specify another format, then I don't think you would be prohibited from any other format.

I remember mowing the lawn at the squadron when I was young contract specialist in the Air Force. It only lasted a year or so before it started getting contracted out base-wide in the mid 90's. Not long thereafter there were CORs running around the base with rulers measuring blades of grass.

In our agency we require the fair opportunity selection process to be based on qualifications only (FAR 16.500(d) and 16.505(a)(9)). After selection, price proposal is requested. Doing so saves the other contractors from wasting their time on putting together a price proposal.

Simplify

Here is a link to the bona fide need rule as it applies to services. It should answer your question. You'll see the appropriateness of using annual/single year funds for services in a subsequent fiscal year is based upon whether or not the service is severable. http://www.wifcon.com/bona/bonafide5.htm

It is not a matter of being honor-bound. There is a statutory requirement for a CO to set-aside certain procurements, which is implemented at FAR Subpart 19.5. If the acquisition exceeds the micropurchase threshold, but not the SAT it "is automatically reserved exclusively for small business concerns and shall be set aside for small business unless the contracting officer determines there is not a reasonable expectation of obtaining offers from two or more responsible small business concerns that are competitive in terms of market prices, quality, and delivery. If the contracting officer does not proceed with the small business set-aside and purchases on an unrestricted basis, the contracting officer shall include in the contract file the reason for this unrestricted purchase." See FAR 19.502-2(b) for actions over the SAT. Also, by making a decision not to set-aside a procurement for small business, it does not exclude small business from participating or receiving award. It simply means they must compete with entities that are other than small businesses. As you may already be aware of, FAR 19.202-2 provides some guidance on locating small business sources. If your concerned about the adequacy or reasonableness of a decision not to set-aside an acquisition for small business, I'd recommend reviewing some of the protests decisions and opinions that are listed here on Wifcon at the link below. A new opinion by the Court of Federal Claims regarding the "rule of two" was just posted yesterday. http://www.wifcon.com/pd19_502.htm

The question is fairly broad, so I'm not sure if this will help. I'm assuming that you are issuing a purchase order under the authority at FAR Subpart 13.5. If so, I believe it would be reported just as any other purchase order. If I recall correctly, there is a specific field that asks if the action was awarded pursuant to the authority at Subpart 13.5. See if this guide from the FPDS website helps. Click on "Create a PO" under "Awards." https://www.fpds.gov/help/index.jsp Regarding the extent completed, the guide states: F Competed under SAP: Select this code when the action is competed under the Simplified Acquisition Threshold. G Not Competed under SAP: Select this code when the action is NOT competed under the Simplified Acquisition Threshold. While the guidance uses the term "threshold", I've always followed the guidance in the name of the field itself, which is SAP. Therefore, if I used SAP procedures over the SAT under Subpart 13.5, I would use one of these two responses as appropriate.

Maybe I didn't articulate it well, but my point was that if I was appointed as a COR to do specific things, the fact that I have a warrant doesn't factor into the responsibilities I've been delegated. I've only been delegated certain responsibilities by the CO for the contract (assuming those do not involve changing or terminating the contract) and those activities are all I should do because that is all that I was asked to do. However, if was then asked by the CO or their supervisor to do something outside the COR delegation like issuing a modification or terminating the contract, I'd proceed with that action under my authority as a CO, not as a COR. I know realize the whole issue of appointing a CO as a COR should be unnecessary, since a CO can simply designate another CO as a ACO for a contract and define their responsibilities in that designation letter. I agree. I'm limiting myself by professional courtesy and organizational responsibility (not legal authority), since the contract is not assigned to me to act as the CO.

At the time I didn't think of the option of being delegated certain ACO responsibilities which I believe you may be referring to at FAR 42.202. That makes more sense than appointing a CO as a COR. Also, even if a CO were appointed as a COR, I agree that having to obtain the certification should be waived as being unnecessary. I obtained mine so as not to be found out of compliance with a policy that applies to individuals appointed as CORs. In hindsight, I could have argued that the requirement should not apply to an individual who is already a CO. Fortunately, I didn't waste 8 hours and was able to apply continuous learning from my FAC-C certification maintenance to obtain the COR certification.

When I found myself in this situation as a FAC-C Level III CO with an unlimited warrant, I was appointed (in writing) as a COR on a contract and of course did not serve as the CO for the contract. Because policy requires all CORs to be FAC-COR certified, I obtained my Level I FAC-COR certification. They way I view it, just because I'm a CO, doesn't mean I have unlimited authority to change other CO's contracts anytime I want. If I'm appointed as a COR, my possession of a FAC-C certification and warrant is irrelevant. I must follow the policies applicable to CORs. Besides, obtaining the certification should take an hour, if not minutes. A CO should be able to quickly click through 8 hours of online training and ace the test (what is required in my agency for a Level I COR).

Articles on the issue have referred to it as Sec. 801 because that is where it was in the version of the bill the House originally passed. However the final bill that passed Congress and was signed by the President moved it to Sec. 846 and changed the title slightly to "procurement through commercial e-commerce portals". It uses the term "portals" instead of "marketplaces." The original bill required DoD to use it. The final version states that agencies "may" use it. Also, some of the criteria listed in the original post that were in the original bill are not actually present in the final law. I even saw an article published yesterday on another site that referred to Sec. 801. Implementation and reporting phases and requirements were added, etc. I haven't read the full versions of each to see what all the differences are or how meaningful they are, but I would not rely on articles that refer to it as Sec. 801 as the information it is based on may not be what is in the law.

If I understand the post correctly, the statement of work is for the interagency agreement and not the federal contract. If so, I don't see a problem. The agreement can be for a total of 5 years with a firm commitment on price and funding for future years to be agreed upon each year. Each year, if both agencies agree upon price and funding is available, the agreement can then be amended and additional funds obligated under the agreement. There is no requirement for the interagency agreement to have firm pricing for future years nor are funds for future years being obligated under the agreement up front. If the agencies cannot agree on the amount or funding is not available, the agreement can then be cancelled. Separately, I believe the contract would need to have priced option periods. Others in this form may have guidance on whether unpriced options are ever permitted. Some agencies specifically address the issue of unpriced options on contracts. For example, my agency specifically prohibits unpriced options. You would want to structure the interagency agreement so that a decision on amending the agreement to agree on the amount and add funds for the next year is done in advance of having to exercise the option on the related contract and so that funds are in hand when exercising the option. This may also require structuring the contract option to permit it to be exercised after the end of the period of performance end date or into the beginning of the next fiscal year if funding will not be made available until then (FAR 17.204(d)). Assuming the interagency agreement is amended to specify the amount and funds obligated, the option on the related contract would then be exercised. If funding is not available or the agencies cannot agree on the amount then the option on the related contract would not be exercised and the interagency agreement would then be canceled. There is no obligation for the government to exercise the option under the contract. Subpart 17.2 does not apply to interagency agreements, only to contracts. The FAR only applies to acquiring things by contract (FAR 1.104) and does not generally apply to interagency agreements. Only Subpart 17.5 deals with the issue of interagency agreements for the purpose of acquiring goods or services.

I agree with Matthew. Also, an agency or office may have an agency FAR supplement or a local policy/standard operating procedure or practice that may require it. For example, our agency requires that modifications affecting price include documentation of the basis for determining the price is fair and reasonable. This is not the PNM described by FAR Part 15, but serves a similar purpose. Even if a PNM is not required by the FAR or your agency, the basis for the price change should be documented and demonstrate that the amount of the adjustment is considered fair and reasonable. Lastly, while not specifically referring to a PNM, FAR 4.803 does describe the type of documentation that is to be included in a contract file, when applicable. This includes a "record of negotiation" and "documents supporting modifications issued by the contracting office."

I've only worked for the USDA for the 7 years, but have not seen that term used since then. However, the USDA agency I work for used the term Government Representative (GR) to refer to the technical person from our agency that was the point of contact for recipients of Federal cooperative agreements that used the funds to award construction contracts. The GR didn't act as a COR for the contract though since it wasn't a Federal contract, but instead worked with the recipient on the administration of their contract.

While the FAR definition of COR includes a reference to COTR, the term COTR does not appear anywhere else in the FAR, just COR. I suspect the term was left in the definition since there were already COTRs in place and they didn't want some people to think they were two different roles. The term COR was not added to section 1.602-2 and the definition of COR at 2.101 until FAC 2005-50 dated 3/6/2011. The only thing that I recall seeing that changed the term COTR to COR was related to the certification program managed by FAI. See the link to a September 2011 OFPP letter below. That letter cites the aforementioned change to the FAR. https://www.fai.gov/drupal/pdfs/FAC-COR_20Sep2011.pdf USDA uses the term COR. Prior to the 2011 OFPP letter the term COTR was used in internal policy.

I've not applied this to a solicitation, nor do I think it is necessary. I was just making an observation about how some (probably a large number) COs and contractors view pricing on Government contracts. If it were me, I'd not make a mention of it in the solicitation and see what type of pricing is received in the proposals (see FAR 17.203(c)-(g) regarding stating limits on option pricing in the solicitation). If I chose to conduct discussions and an offeror proposed an escalation for the option periods, I'd ask them why that is. If the rationale made sense, I'd not address the matter further. However, if based on the type of procurement, I believed there was an opportunity to gain efficiencies under the contract and obtain better pricing in the option periods, I'd make my argument during negotiations. I don't view the aforementioned limits on what is stated in the solicitation as a prohibition on trying to negotiate lower option pricing when it make sense.