COMET_ORDERS and TASKING PROCEDURES.docx

COMET ORDERS and TASKING PROCEDURES (July 2021) - DRAFT

(a) GENERAL. The requirements identified in the Fair Opportunity Proposal Request’s (FOPR) Task Order Requirement Package (TORP) are in specific terms. Any task or subtask not specifically addressed in the TOPR must be assigned by the Procurement Contracting Officer (CO). The Contractor shall not honor any other forms or variations of tasking.

(b) DEFINITIONS. The Fair Opportunity Proposal Request (FOPR) requires the Contractor to act on tasks requested by the CO, and respond in the prescribed manner. The terms used to describe this process are defined as follows:

(1) Fair Opportunity Proposal Request (FOPR). FOPR is a document to communicate the Government's requirements to solicit fair opportunity proposals from prospective Contractors. A FOPR will include an attached TORP.

(2) Task Order Requirement Package (TORP). The TORP identifies the Government's technical requirements and outlines the work to be accomplished. A TORP will be generated by the Government for each task order. This will include a Performance Work Statement (PWS), Contract Data Requirements Lists (CDRLs), Administrative Requirements, Security Requirements, Instructions to offerors, and TO Evaluation Criteria.

(3) Fair Opportunity Proposal (FOP). A FOP is the Contractor's response to a FOPR within the specified time limit with either a FOP or a written negative reply to the CO. A FOP will contain at a minimum:

(a) Proposed approach for addressing the requirements of the FOPR and TORP;

(b) Technical Merit;

(c) Proposed Cost;

(d) Schedule; and

(e) Past Performance.

Response(s) shall also include estimates of person‐hours, materials, subcontracting, and other charges, time of performance/delivery, and the proposed “price” if Firm Fixed Price (FFP) or “estimated costs” if Cost Reimbursable or Time and Materials, for each type of CLIN utilized in each task order. Additional sections may be required to respond to unique Government requirements in the FOPR and TORP.

(4) Task Order. A task order (TO) establishes the specific requirements for work to be performed within the contract and is issued by the CO. The TO binds the Government and contractor(s) in mutual agreement.

(c) TASK FLOW. The task flow to perform the work under the contract shall be as follows:

(1) Orders may be issued at the sole option of the Government during the period set forth in the Ordering Clause hereof. Orders may be issued by the CO during the period set forth in SECTION I, FAR 52.216‐18, "Ordering." All FOPRs, TORPs, and TORP Amendments (corrections, additions, modifications, and deletions) shall be issued to the Contractor by the CO through the transmittal of a FOPR/FOPR Amendments.

(2) Prior to issuance of an order, the Government shall request a proposal by issuing a FOPR and TORP for the contemplated work. Upon receipt of a FOPR from the CO, the Contractor shall produce a FOP.

(3) Task Orders/CLINs issued under this contract may be accomplished on a FFP, Time and Materials, Labor‐Hour or any combination thereof depending on the nature of the task order requirement. If the task order is all one contract type or predominately one type, then the amount on the first page of the task order and the applicable CLINs will be a “price” (FFP), or an “estimated cost” (CR). The total amount of each task order shall establish an estimated cost, or allocated amount for the order, which the contractor exceeds at its own risk. Changes to the price/estimated costs shall be accomplished in accordance with all IDIQ terms and conditions.

(4) Task orders for support and data shall be issued by the CO in writing, dated, and numbered. It shall set forth the following:

(1) the support being ordered,

(2) associated data,

(3) delivery or performance dates,

(4) place of delivery or performance,

(5) packaging and shipping instructions, if any,

(6) the amount of funds obligated,

(7) the industrial resources priorities and allocations (DO/DX) rating, and

(8) identification of the cognizant Program Manager/Technical Monitor. Each TO shall allot specific amounts for CLINs requested in FOPR. Data requirements (CLIN 0005) are not separately priced (NSP). The Contractor shall furnish to the Government reports and data requested, at the price agreed upon based on the negotiated rates set forth in the IDIQ schedule or applicable TO.

(5) Coordination. During the FOPR process, contact between the Government and Offeror may be required for the purpose of technical coordination. Technical coordination shall include all verbal and written communications pertaining to clarification of the FOPR/TORP, resolution of technical problems, development of the FOP, and in‐progress review of Contractor efforts and reports. All communication shall be conducted through the CO.

(6) Government Review. The TORP technical monitor and the contract negotiator shall review the FOP and shall provide recommendations to the CO for approval or disapproval in accordance with the FOPR and TORP. The CO will issue a TO directing the Contractor to commence performance, unsuccessful FOPs will be notified via CO letter. If no proposals are found acceptable initially, the CO may open discussions with Offerors. In the event issues pertaining to a proposed work cannot be resolved to the satisfaction of the Government, the CO reserves the right to withdraw and cancel the proposed work. In such event, the Contractors shall be notified, via letter, of the CO’s decision. This decision shall be final and conclusive and shall not be subject to the Disputes clause or the Contract Disputes Act.

(7) Execution. Upon receipt of a signed/awarded task order, commencement of contractor performance shall occur.

(d) CONTRACTOR PERFORMANCE. Execution of Contractor performance shall commence on the date of award of the TO or on the identified start date within. Contractor performance is to be accomplished in strict accordance with the approved FOP in content, approach, and reporting schedule, unless otherwise directed in writing by the CO.