03. REVISED EC2 Ordering Guide.docx

Attachment 03 FA877322R0005 Solicitation

This Ordering Guide (dated 21 September 2022) sets forth the procedures for issuing TOs against the Enterprise Cyber Capabilities (EC2) Multiple Award Indefinite Delivery Indefinite Quantity (IDIQ) contract in order to fulfill Air Force cyber requirements. This ordering guide does not authorize any policy deviation unless expressly stated. It is considered a living document and will be updated periodically as needed.

Introduction Thank you for choosing the Enterprise Cyber Capabilities (EC2) contract to fulfill your cyber service needs!

The EC2 is a multiple-award Indefinite Delivery, Indefinite Quantity (IDIQ), 10-year (five-year base and five-year option period) contract with a $5.3 billion combined maximum on the total value of orders that can be placed under the contract. The EC2 acquisition team will track orders placed under the EC2 IDIQ Contract to ensure the IDIQ maximum is not exceeded. Due to on-ramp procedures in Section H of the contract, a contract may have been awarded on different dates; however, all contracts shall have the same contract end date.

The EC2 multiple award IDIQ is considered a “partial small business set-aside.” A small business set-aside will be confirmed utilizing the rule of 2 at Task Order (TO) level during the market research phase. If the contracting officer has a reasonable expectation that offers will be obtained from at least two responsible small businesses and award can be made at fair market price, then a 100% small business set-aside should be established for the TO IAW FAR 19.502-2(b). No pools will be established.

Task Orders will be awarded by utilizing procedures identified in FAR 16.505 Ordering.

This Ordering Guide explains how the EC2 contract can be used to satisfy a wide variety of cyber services. It does not address general contracting issues or concepts unless necessary for complete understanding.

A detailed listing of the IDIQ awardees and subsequent contract numbers is available at the EC2 online platform (currently being developed).

Scope of the EC2 contract The EC2 IDIQ contract covers cyber services that are: commercial and non-commercial; classified and non-classified; and CONUS and OCONUS. All EC2 TOs must be within scope of the EC2 IDIQ. The North American Industry Classification (NAICS) for the EC2 IDIQ contract is 541330 Engineering Services (Exception 1) Military and Aerospace Equipment and Military Weapons. The scope also allows for ancillary services and costs necessary to complete a total solution through a cyber service objective.

The EC2 Cyber Framework is comprised of the following components:

· Categories (7) – A high-level grouping of common cybersecurity functions

· Specialty Areas (SAs) (31) – Distinct areas of cybersecurity work

· Work Roles (49) – The most detailed groupings of cybersecurity work comprised of specific Knowledge, Skills, and Abilities (KSAs) to perform tasks in a Work Role on subordinate TOs

Operate and Maintain (O&M)

Data Analyst

Communications Security (COMSEC) Manager

Cyber Policy and Strategy Planner

Cyber/IT Project Manager

Product Support Manager

Cyber/IT Investment/Portfolio Manager

Cyber/IT Program Auditor

Cyber Instructor

Mission Assessment Specialist

Target Network Analyst

All Source-Collection Requirements Manager

Cyber Ops Planner

Partner Integration Planner

Cyber Defense Forensics Analyst

Secure Software Assessor

Security Architect

Systems Developer

The EC2 IDIQ Performance Work Statement (PWS) is the authoritative resource for the EC2 Cyber Framework, and it provides more in-depth details of the Framework. A copy of the contract and attachments can be found at the EC2 online platform (currently being developed).

The PWS Supplement maps the Categories and SAs to specific Work Roles and associating KSAs and Tasks. This spreadsheet is located on the EC2 online platform (currently being developed).

NOTE: These documents are intended as guides only, additional Work Roles can be added as required at the TO level and can be incorporated within the existing Categories and/or SAs.

Services Not Included on EC2 Task Orders Absent pre-coordination and authority, EC2 TOs shall NOT include any of the following:

· Inherently governmental functions – see the prohibition at FAR subpart 7.503(a)

· Personal services as defined in FAR subpart 37.104(a)

· Architect & Engineering (A&E) Services subject to the Brooks Act and FAR Part 36 acquisition procedures (note: This does not preclude use of Architects and Engineers for services not required to be under FAR Part 36 such as Construction Management, etc.)

· Services that are outside the scope of the EC2 IDIQ contract Which Agencies can use EC2?

The EC2 IDIQ contract may be used by Department of Air Force organizations only.

How Do I Begin Using EC2?

In order to solicit and place TOs under EC2, you must be a warranted Federal Contracting Officer (CO), as defined in FAR Subpart 2.1 Definitions, hereby referred to as the Ordering Contracting Officer (OCO).

EC2 IDIQ Procuring Contracting Officer (PCO) Responsibilities

· Award, administer, and manage the EC2 IDIQ contract.

· Enforce of contractual terms and conditions

· Exercise contractual options

· Monitor ceiling limitations

· Make scope determinations for potential order teaming agreements

· Changes in awardees’ status to include mergers, debarment, names, size status updates, subcontracting plan updates, etc.

· On or Off-Ramp contractors

· Monitors and evaluates performance against the IDIQ contract requirements by each contract holder

· Holds exclusive, non-delegable rights to modify the EC2 IDIQ Contract terms and conditions

· Provides advice and guidance to ordering/requiring activities, OCOs and contractors regarding all EC2 procurement-related matters

· Conducts meetings with EC2 prime contractors as scheduled and/or necessary

· Monitors Limitations on Subcontracting (aggregate for all orders, not each order) for SB Requiring Activity Responsibilities

· Defines TOs requirements

· Prepares SOW/PWS/SOO for TO RFPs

· Funds requirements

· Assists OCO with quote/proposal evaluation

· Assists OCO with performance monitoring and appraisal

OCO Responsibilities

· OCOs are responsible for TOs issued under EC2 from cradle to grave

· OCOs are expected to comply with:

· The EC2 IDIQ contract terms and conditions and the EC2 Ordering Guide

· The Federal Acquisition Regulation (FAR) or authorized agency supplement or exception thereto

· Applicable agency-specific statutes and policies

· OCOs must request authority to solicit and award each TO

· Notify the PCO of increases to TOs

· Monitor performance and elevate issues to the PCO, as necessary

What are some of the benefits of using the EC2 IDIQ?

· The EC2 IDIQ is flexible, easy to use, and allows ordering activities to:

· Purchase commercial or non-commercial services

· Use fixed price and cost reimbursable contract types, including hybrid mixtures of contract types

· Establish standard CLIN structures tailorable to individual TO requirements

· Order and perform work within CONUS and OCONUS

· Meet or exceed small business goals in all categories

· Add/order specific labor categories

· Include ancillary services and other direct costs (ODCs) as needed

· The EC2 contract is UNPRICED for maximum order flexibility eliminating the need to endure reconciling order level proposals against contract level rates

· Incorporates OPM and USAF Category Management (CM) best practices that will enable detailed spend analysis to generate further rate, process, and demand savings for EC2 customers

Step 1: Acquisition Planning Considerations Orders from multiple-award IDIQ contracts, such as the EC2 contract, are not exempt from Acquisition Planning as prescribed in FAR Part 7. Conduct market research for your requirement in accordance with regulations as you would do with any procurement.

OCOs shall follow the ordering procedures in FAR Subpart 16.505.

The following contract types may be used in TOs:

· Fixed-price, all types

· Cost-reimbursement, all types

· Hybrids of either of these types

If using a hybrid of contract types, please use separate Contract Line Item Numbers (CLINs) for the work under each contract type and annotate each CLIN with the associated contract type. This is important for clause implementation.

Use of Labor Hour and Time and Materials contract types is prohibited.

· IDIQ or BPA against EC2 IDIQ Is Prohibited Agencies may NOT issue IDIQ order instruments or Blanket Purchase Agreements (BPAs) against the EC2 IDIQ contract (see Harris IT Services Corporation B-411699,B-411796: Oct 2, 215). However, considerable flexibility with respect to variable levels of effort and requirements can be achieved using optional CLINs, and Cost-type CLINs. (e.g., issuing a not to exceed Cost-type order with a wide scope that is incrementally funded via “Technical Direction Letters” within the scope of the TO). OCOs seeking further guidance on these flexibilities are encouraged to submit a scope review (see the “Pre-solicitation scope reviews” section) outlining the desired flexibility.

· Security Clearance considerations for classified orders The TO solicitation should clearly express all requirements for security clearances, both facility, and personnel. Please adhere to classified handling procedures at all times.

Example for Classified work:

1. Customer notifies EC2 contract awardees of an upcoming classified work performance, classified PWS, or classified solicitation and award. The customer requests interested vendors respond. Provide instructions on how the solicitation may be viewed, i.e., location (SCIF) or SIPR email instructions

2. Post solicitation (in secure location, distribute via SIPR emails)

3. Review Offers and Award

4. There is no evaluation of security in the source selection for the EC2 IDIQ. As a result, there is no DD Form 254 stipulated at the contract level. OCOs should ensure applicable DD Forms 254 are included in the solicitation and evaluated prior to TO award.

5. Notify EC2 IDIQ Contract PCO of Award – (Workflow Address is currently being developed) that an award has been made along with dollar value if it is not considered classified (The TO is not required to be provided).

· Task order limitations TOs must be solicited and awarded prior to the EC2 term expiring and may extend up to 2 years after the EC2 IDIQ contract term expires. TO option periods may be exercised after the EC2 term expires provided the final TO option period does not extend beyond 2 years after the expiration of the EC2 term. The EC2 contract will expire on TBD unless extended pursuant to FAR 52.217-8.

After the EC2 IDIQ contract term expires, it will remain active for administration only. The EC2 contract shall govern the terms and conditions of active TOs to the same extent as if they were completed during the EC2 term.

· FAR 52.216-19 Minimum and maximum order limitations Minimum Order

· A contractor is not obligated to accept an order valued under $1,000.00, but it is not prohibited from doing so Maximum Order

· There is a $500 million maximum order limitation under the EC2 IDIQ

There is a $5.3 billion ceiling

Step 2: Mandatory Pre-solicitation scope review request The EC2 IDIQ acquisition team requires OCOs to submit a pre-solicitation scope review request. See Appendix A for process and instructions. The OCO must submit the following to initiate the scope review:

· Information Summary Sheet

· Performance Work Statement (PWS)/Statement of Work (SOW)

· IGCE (format provided on the EC2 online platform in development)

Step 3: Develop the solicitation Use the solicitation form and format for TOs normally prescribed and used by your agency for task order solicitations, consistent with FAR 16.505 procedures.

NOTE: Use of the Uniform Contract Format found in FAR 15.204-1 is not required for EC2 orders. Furthermore, we do not recommend its use for EC2 TOs as it can lead to confusion between the ordering procedures found in FAR 16.505 versus source selection procedures found in FAR 15.3, which are not applicable to EC2 TOs. A task order Fair Opportunity Proposal Request (FOPR) template is provided in Appendix B of this ordering guide.

In addition to the information required by FAR 16.505(a)(7), provide the following information at a minimum:

· NAICS

· SOW/PWS/SOO

· Type of Services (Commercial or Non-Commercial)

· CLIN Structure

· Evaluation Factors

· Fair Opportunity Source Selection Methodology

· Contract Type(s)

· Period of Performance

· Place of Performance

· Solicitation Questions Due Date

· Proposal Due Date

· Proposal Instructions

· Other Pertinent Information (e.g., agency specific clauses, optional clauses, etc.)

· North American Industry Classification System (NAICS) Selection The OCO must assign the NAICS code to each TO solicitation. The size standard applicable to a TO to solicit is determined by the NAICS code. The NAICS code assigned should reflect the principal nature of the work required under the TO. The NAICS for the EC2 IDIQ contract is 541330 Engineering Services (Exception 1) Military and Aerospace Equipment and Military Weapons. The scope also allows for ancillary services and costs necessary to complete a total solution through a cyber service objective. If the principal purpose of the requirement is for any other NAICS code, it is out of scope for the EC2 IDIQ Contract.

If it is determined in Market Research at the TO level that SB is not capable, and the Government has historically utilized SB to support the effort, the Government will accomplish additional market research outside of the EC2 IDIQ vehicle. If it is determined that unrestricted is the most appropriate via the EC2 contract for a TO a subcontracting plan will be required if awarded to a Large Business.

· Clauses and Provisions In accordance with FAR 52.301, Solicitation Provisions and Contract Clauses (Matrix), the EC2 IDIQ contract cannot predetermine all the contract provisions/clauses for future individual TOs. Clauses and provisions from the EC2 IDIQ contract automatically flow down to all TOs as set forth in FAR 52.301 based on their specific contract type (e.g., cost, fixed price, etc.), performance work statement, competition requirements, and dollar value as of the date the TO solicitation is issued. (Note: Any Applicable and/or Required provisions/clauses that require fill-in information must be provided by the OCO in full text).

FAR provisions and clauses not identified in FAR 52.301 may be used in contracts for commercial items consistent with the procedures and limitations in FAR 12.302.

No clauses unique to commercial contracting procedures are included in the EC2 IDIQ; therefore, they must be added into appropriate TOs. The OCO must identify in the TO solicitation whether FAR Part 12 commercial clauses/ provisions apply or do not apply.

The clause, 52.217-8, Option to Extend Services, was included in the contract for flow down to the TO. It was NOT evaluated as part of the contract award. Including it in any TO requires inclusion into the IGCE and evaluation for award. Furthermore, the OCO must include any Optional, and/or Agency-Specific provisions/clauses for each individual TO solicitation and subsequent award.

· Services Contract Labor Standards (SCLS)

To the extent that any labor for services are within the scope of the EC2 IDIQ contract and subject to SCLS in accordance with FAR Subpart 22.10 and other applicable agency specific regulatory supplements, the OCO must identify such work in the TO solicitation and make a determination as to whether SCLS wage determinations are to be applied or not. EC2 does not include clauses applicable to any service contract labor standards that are part of a total solution within the scope of EC2. The OCO must incorporate the appropriate clauses and provisions in each TO solicitation and subsequent award when SCLS apply.

· Davis-Bacon Act Work Minor amounts of construction, alteration, or repair may be included as ancillary services in TOs when integral and necessary to delivering a total cyber services solution to a mission need. The OCO is responsible for ensuring that construction, alterations, or repairs are covered by the purpose element of the appropriation used to fund the construction portion of the TO.

The OCO shall identify construction under a separate CLIN. The OCO must also include all applicable construction clauses and wage decisions in the TO.

· Rights in Data The OCO should ensure that the applicable Rights in Data clause(s)/provisions is (are) clearly assigned in each TO solicitation and resulting TO. Rights in Data is a highly specialized area and OCOs should seek advice from qualified professionals on these issues to ensure the proper clauses are in effect for a TO.

· Subcontracting Plans IAW FAR 19.705-1(b)(2) Contracting Officers placing orders may establish small business subcontracting goals for each order. Establishing goals shall not be in the form of a new subcontracting plan as a contract may not have more than one plan (19.705-2(e)).

· Deliverables Deliverables for TOs to include Contract Data Requirement Lists (CDRLs) and Data Item Descriptions (DIDs) are not defined or stipulated at the contract level. OCOs in coordination with the requiring activities should ensure applicable CDRLs/DIDs are included as part of the TO. A list of recommended deliverables and sample CDRLs/DIDs will be provided on the EC2 online platform (currently being developed).

· Quality Assurance Surveillance Plans (QASPs) The EC2 IDIQ QASP provides criteria to surveil performance of IDIQ awardees which does not apply to TOs awarded. Ordering Contracting Officers shall develop a QASP for each TO, as applicable, to comply with FAR Subpart 37.6, Performance-Based Acquisition, and FAR Subpart 46-4, Government Contract Quality Assurance. In addition, FAR Subpart 46.103, Contracting Officer Responsibilities state that agencies shall develop QASPs when acquiring services. Authority for issuance of the QASP is provided under FAR Part 46, Inspection of Services.

Step 4: Issue the Solicitation

· Methods of issuing the TO solicitation An EC2 TO solicitation shall be issued by emailing contractors via the EC2 distribution link available at the EC2 online platform (being developed). Using this method to broadcast the solicitation notice to all contract holders satisfies the “fair opportunity” notification requirement. For classified work see Security Clearance Considerations for Classified Orders section above.

· If Issuing a Sole Source/Direct Award order Simply email the solicitation documents directly to the company. Company points of contact information can be found at the EC2 online platform (currently being developed). Note that sole source acquisitions require justification and documentation IAW FAR Part 6.

· EC2 is UNPRICED The EC2 IDIQ contract is UNPRICED to ensure maximum competition and flexibility at the order level. Pricing is determined fair and reasonable based on competition at the order level.

Step 5: Evaluate Proposals OCOs should evaluate proposals based on the methodology stated in the TO solicitation to maintain fairness in the ordering process and mitigate protest risk. Some EC2-specific features OCOs should consider when evaluating proposals include:

· Price The OCO is responsible for analyzing order proposals and documenting the cost or price evaluation to include a determination that the final agreed to price is fair and reasonable. To the maximum extent practicable, price analysis should be based on competition. Rates are determined fair and reasonable at the order level in accordance with FAR 16.505(b)(3).

· Acceptable Accounting System All EC2 contractors have accounting systems that have been determined to be adequate to support cost reimbursement contracts if a TO has cost reimbursement CLINs.

Step 6: Award the TO Some EC2-specific features OCOs should consider when executing TO awards include:

· Submit copy of the TO Submit the EC2 TO Award Information Form with an electronic copy of the TO award to the EC2 IDIQ CO within 5 days after award. A copy of the Award Information Form is provided in Appendix C of this ordering guide. This process is the same for any modifications issued throughout the life of the order that increase the total amount (e.g., exercise of options, increase in funding, etc.)

· Public notice of awards not providing for fair opportunity For orders based on an exception to fair opportunity, in accordance with FAR 16.505(b)(2)(ii)(D) the OCO must post the required public notice within 14 days after placing the order. If exception (A) (urgency-unacceptable delay) is used, the public notice must be posted within 30 days after placing the order. This posting requirement includes posting the justification approved for the exception at the Government point of entry: https://sam.gov/content/homev.

Note the actions excluded from this notice requirement are

· Disclosures that would compromise national security

· Socioeconomic set-asides authorized by FAR 16.505(b)(2)(i)(F)

· Sole Source 8(a) orders up to the thresholds detailed in FAR 19.805-1(a).

· Order Level Protests All protests at the TO level are handled by the agency soliciting the TO. Please refer to FAR 16.505 (a)(10) and FAR Part 33.1 for additional information regarding orders and protests.

· Order Level Debriefings OCO must comply with current policy regarding the requirements for debriefings.

· Ombudsman For orders issued by an ordering activity, refer to their ombudsman.

· Reporting TO awards in FPDS-NG Contract actions are reported in the Federal Procurement Data System (FPDS) within 3 days after execution of the action. It is important that each EC2 TO is reported as an order under the correct EC2 contract number.

Make sure your FPDS-NG report accurately reflects the appropriate values in all fields, those related to award data, fair opportunity procedures used, and number of offers received. The FPDS-NG system will propagate the NAICS code field in your TO action report with the NAICS code reported for the EC2 IDIQ contract.

Step 7: Administer the order/execute the work/close-out the order Some EC2-specific features OCOs should consider when administering TO awards include:

· Quality Assurance – Contractor Surveillance The OCO is responsible for ensuring contractor performance meets the minimum requirements established in the order, documenting the order file, and communicating with the contractor to ensure the Government is receiving the contracted services. Monitoring contractor performance should be delegated to a contracting officer’s representative (COR). The specific authority/limitations of the COR should be delineated in an appointment letter, a copy of which should be provided to the contractor.

· Performance Evaluation Each OCO is responsible for ensuring that the contractor’s performance on each order is reported in CPARS in accordance with the policies in FAR 42.15. Follow your agency procedures for preparation, review, and submission of performance reports. TO performance may be considered in placing contractors in a dormant status.

· TO Closeout TO files shall be closed out by the OCO in accordance with the policies in FAR 4.804. The OCO shall email EC2 IDIQ EC2 PCO (Workflow address is in development) within 30 days after TO closeout to report the TO has been closed out.

END OF ORDERING GUIDE

APPENDIX A: EC2 Scope Review Process

Thank you for your interest in using the Air Force Enterprise Cyber Capabilities (EC2) multiple award Indefinite Delivery Indefinite Quantity contract subject to FAR 16.505 ordering procedures. Ordering Contracting Officers issuing a TO against the EC2 contract must submit this request to the EC2 Procuring Contracting Officer (PCO) prior to releasing a solicitation.

The scope compatibility review is not a legal review. Please follow your internal agency policy regarding review levels. The response to this EC2 scope review will provide advice/opinion from a Subject Matter Expert (SME) on the scope compatibility assessment of the Ordering Activity’s requirement based solely on the information provided when the scope review is requested.

IMPORTANT NOTE: The Ordering Activities Ordering Contracting Officer (OCO) makes the final and official EC2 Scope compatibility notwithstanding whether the OCO agrees with the SME assessment.

Instructions:

1. Complete Information Summary Sheet (in development/elements are listed below)

2. Complete a Performance Work Statement (PWS) or Statement of Work (SOW).

3. Complete an Independent Government Cost Estimate (IGCE) using your organization’s government estimate and input it into the EC2 template provided on the EC2 online platform (in development). It should include labor categories, hours, and other direct costs.

4. Submit the information summary sheet, PWS/SOW, and the completed IGCE template to the EC2 PCO Workflow (in development).

We cannot complete the scope review until all three documents are received.

Note: If you do not hear back within five business days of submitting all documents, email workflow (in development) for update. Please make sure to include the project name for your inquiry.

Project Name Dollar Value Project Name

Estimated TO Base Year Dollar Value:

Estimated TO Total Dollar Value (including all option years)

Estimated Period of Performance:

Estimated Award Date:

Summarize Principal Purpose of Requirement:

Is this a new Requirement or follow-on from a previous OASIS order?

Organization where you work:

Ordering Contracting Officer’s Contact Information:

Ordering Contracting Officer’s Supervisor Contact Information:

APPENDIX B: TASK ORDER SOLICITATION TEMPLATE

[Upon filling out the following template, please delete all instructional information in red and any sections that do not apply. Also, this template format is not mandatory; however, the minimum information herein is necessary for a proper solicitation under the EC2 IDIQ contract] TASK ORDER FAIR OPPORTUNITY PROPOSAL REQUEST No. [Insert Solicitation Number] Solicitation Title: [Insert brief description of work] Issuing Office: [Insert Agency Name and Address] Agency Contact(s): [Insert Name(s), Telephone number(s), and email address (es) of OCO and/or Contract Specialist] Issue Date: [Insert Date FOPR was issued] Questions Due Date: [Insert Time, Time Zone, and Date Questions are due and where to send/email questions] Proposal Due Date: [Insert Time, Time Zone, and Date Proposals are due and where to send/email proposal]

1.0 EC2 TASK ORDER INFORMATION

1.1. NAICS Code and Small Business Size Standard: The principal nature of the requirements described in this solicitation is consistent with services performed by industries in the [insert the NAICS code and title] with a small business size standard of [insert small business size standard]

1.2. Product Service Code (PSC): The services in this solicitation are best represented by PSC Code(s): [insert the applicable PSC Code and title. See PSC Manual located at www.acquisition.gov under acquisition systems]. OCOs may assign multiple PSC codes based on the NIST / NICE KSA’s for services requested in the TO. PSC codes can be assigned at the TO CLIN or SLIN level.

1.3. Type of Contract: The primary type of contract resulting from this solicitation is: [insert the Predominant contract type (Cost Plus Fixed Fee, Firm Fixed Price, Time and Materials, etc.) Note: If a hybrid type of contract results from this solicitation, identify Contract Type by CLIN in Section 2.0.]

1.4. Type of Services: The services required are: Commercial Non-Commercial

1.5. Extent of Competition: This solicitation will be based on: [check the box that applies.]

Exception to Fair opportunity as designated below (FAR 16.505(b)(2)) [Check only one exception below] FAR 16.505(b)(2)(A) [The agency need for the supplies or services is so urgent that providing a fair opportunity would result in unacceptable delays]

1.6. Security Clearances:

[IF N/A delete 1.6.2. Note: For individual security clearance levels and instructions, please identify in the PWS/SOW or Labor Category section of the solicitation]

1.7. Performance Location(s):

1.7.3. Place(s) of Performance: The places of performance(s) for this PWS/SOW are:

[insert city(ies), state(s), and/or country(ies) services will be performed in; If performance will be in multiple locations and/or a mix of CONUS, OCONUS, Government and Contractor sites, also identify in the solicitation’s Section 3.0, Description of Services, which services are performed where. Also, identify if Gov’t Site or Contractor Site]

1.8. Period of Performance: The period of performance for this PWS/SOW is:

[Enter the Period of Period of Performance for the TO. For example: “The period of performance for this TO is from date of award through 1 year thereafter, with 5 (1-year) options that may extend the cumulative term of this TO to 5 years” If the period of performance and options are different by CLIN, address the period of performance for each CLIN in Section 2.0 below]

2.0. Contract Line Items (CLINs) and Contract Type by CLIN

[List the CLINs with their descriptions and pricing information. Remember to use separate distinct CLINs for work with different pricing types. Repeat for each Option Year(s) as applicable. See example CLINs below and on EC2 Landing Page (in development). Tailor CLINs necessary to meet your requirement specifically] CLIN 0001 (Firm Fixed-Price): Provide Program Management and oversight support services for the Citizens Assistance and Response to Emergencies (CARE) Program. These services are performed in CONUS, on Government site, in Washington, D.C. Sections 3.1, 3.2, 3.3, 3.4, and 3.5 apply.

Total Firm Fixed Price: $ CLIN 0002 (Cost Plus Fixed Fee): Provide Engineering and Logistics support services to the CARE Operations Centers in Washington, D.C.; New York, NY; San Francisco, CA; and Chicago, IL. These services are performed in a mix of Government and Contractor facilities as delineated in Sections 3.0. 3.1, 3.6, 3.7, 3.8, and 3.9.

Total Estimated Cost:

Fixed Fee:

Total Estimated Cost Plus Fixed Fee:

3.0. Description of Services

[Use your agency preferred format for your PWS/SOW/SOO. Remember that performance-based is preferred. For Example:

3.1 Background

3.2 Scope

3.3 Performance Work Statement/Statement of Work

3.4 Places of performance and work conditions/hours ETC.

4.0. Delivery and Performance Information

[Enter a table of deliverables, if applicable, and/or other applicable service delivery terms. Include performance standards and metrics that will apply to your performance-based statement of work, or performance measurements that will be used to verify non-performance-based services. Address, quantity and quality considerations, due dates, deliverable submittal instructions, and similar information related to the basis for contractor performance evaluations]

5.0. Labor Categories and Descriptions

[Identify the labor categories, definitions, and skill requirements necessary for successful completion if applicable to your requirement. Identify security clearance levels if applicable]

6.0. Invoicing instructions

[Identify invoice instructions and procedures]

7.0 Solicitation Provisions and TASK ORDER Clauses

All Applicable and Required provisions/clauses set forth in FAR 52.301 automatically flow down to all EC2 TOs, based on their specific contract type (e.g., cost, fixed price, etc.), statement of work, competition requirements, commercial or not commercial, and dollar value as of the date the TO solicitation is issued. Representation and Certification Provisions from the EC2 IDIQ contract automatically flow down to all EC2 TOs.

7.1. FAR Optional and Agency specific TO Provisions/Clauses. The following additional provisions and clauses apply to this TO: [Add any FAR Optional or Agency Specific provisions and clauses here that will apply to the TO solicitation and resultant TO award. Remember to provide any Fill -ins to any flow down clauses or optional/agency specific clauses.]

8.0. Proposal Preparation and Submission

[Insert instructions for preparation and submission of proposals. Keep submission requirements to a minimum].

No-Bid Statement. The FOPR will include language specifying that if a prime elects not to submit a proposal for a TO requirement, that Contractor shall submit a "no bid" statement to the Contracting Officer, as specified in the TO solicitation, on or before the TO proposal due date. The Contractor shall provide (within three business days) its rationale for not bidding in the "no bid" statement.

9.0. Evaluation Factors and Basis of Award

[Identify the evaluation factors to be considered in selecting a proposal for award. Identify if a trade-off is going to be considered. Tailor this section based on the dollar value and complexity of the TO.]

APPENDIX C: EC2 TASK ORDER AWARD INFORMATION FORM

An editable copy is provided at the EC2 online platform (currently being developed).

image1.png image2.png