Since I am ordering services from the contractor, I should be the OO, correct? My HQ is stating that the COR should be on ground and that the OO can be located anywhere. I told them that the OO needs to be co-located with the actual operation and the contractor because constant coordination is necessary. I can't be the OO and COR because it's a conflict - if I had to be one or the other, it makes sense to me to be the OO. The OO can provide information to the COR to validate invoices and create performance reports. Does this makes sense?
I operated this way before; I was an OO at the depot level for a transportation contact and the CORs were located at HQ SDDC.
Please let me know your thoughts on this. Thank you in advance.
Hate to tell you this... but based on the information you provided, I agree with your HQs.
Open full Question Details
It makes more sense the COR be located where the contractor is performing in order to be the “eyes and ears” of the KO and the requiring activity. If a COR has been delegated inspection/acceptance and/or the authority to provide technical direction and guidance to the contractor in their letter of designation; then better to be on sight to accomplish this. The responsibility of the COR is to make sure the government is getting what it paid for and that the government is meeting our requirements under the terms and conditions of the contract (e.g. prompt payment, etc.).
Whereas an OO (Ordering Officer) can issue orders (within their authority) from practically anywhere… as long as they have a suitable method for communicating the order to the contractor.
I do agree with you on the fact that having the OO and COR be the same person is a scenario that could most certainly create a conflict of interest… in the least. But note, depending on dollar value there may be exceptions and we highly suggest you discuss those with your HQs.
Note: For us in the Department of Defense;
a) OOs are appointed via the authority of FAR 1.603-3(b), DFARS 201.603-3(b) and 213.301.
b) CORs are appointed via the authority of FAR 1.602-2(d), DFARS 201.602-2 and DFARS PGI 201.602-2.