HR001123R0001 Amend 0001.pdf

DARPA

CMO SERVICES DIVISION

675 N. RANDOLPH STREET

ARLINGTON VA 22203-2114

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purposes of this amendment are to:

1. Revise Solicitation Sections G, L, and M.

2. Add Attachment 9 - Questions and Answ ers.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 32

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 03-Mar-2023

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X HR001123R0001

X 9B. DATED (SEE ITEM 11)

10-Feb-2023

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

03-Mar-2023

CODE

DARPA

CMO

ATTN: MARY BETH COLAVITO

675 N. RANDOLPH STREET

ARLINGTON VA 22203-2114

HR0011 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE HR0011

FACILITY CODECODE

EMAIL:TEL:

HR001123R0001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION G - CONTRACT ADMINISTRATION DATA

The following have been modified:

CONTRACT ADMINISTRATION DATA

G-1.0 Points of Contact

G-1.1 Government Notwithstanding the Contractor’s responsibility for total management during the performance of this contract, the administration of the contract will require maximum coordination between the Government and the Contractor. The below individuals will be the Government points of contact during the performance of this contract.

G-1.1.1 Contracting Officers All contract administration will be effected by the Contracting Officer (CO). Communication pertaining to the contract administration should be addressed to the CO. Contract administration functions (see FAR 42.302 and DFARS 242.302) are assigned to the cognizant contract administration office. No changes, deviations, or waivers shall be effective without a written modification of the contract executed by the CO or his/her duly authorized representative authorizing such changes, deviations, or waivers.

The CO for the IDIQ contract is Mary Beth Colavito.

G-1.1.2 Contracting Officer’s Representative (COR) The Contracting Officer’s Representative (COR) is not authorized to change any of the terms and conditions of the contract. The Contractor is advised that only the CO can change or modify, in writing, the contract terms or take any other action which obligates the Government. Then, such action must be set forth in a formal modification to the contract. The authority of the COR is strictly limited to him/her, without re-delegation, to the specific duties set forth in his/her letter of appointment, a copy of which will be furnished to the Contractor at time of award. Contractors who rely on direction from other than the CO or a COR acting outside the strict limits of his/her responsibilities as set forth in his/her letter of appointment do so at their own risk and expense.

Such actions do not bind the Government contractually. Any contractual questions shall be directed, in writing, to the CO.

The COR supports the CO during administration of this contract by:

Making final decisions regarding any recommended rejection of deliverables;

Providing technical clarification relative to overall workload matters;

Providing advice and guidance to the Contractor in the preparation of deliverables and services; and Providing acceptance of deliverable products to assure compliance with requirements.

All technical direction will be issued in writing by the COR or will be confirmed by the COR in writing within ten (10) calendar days after verbal issuance. A copy of the written direction will be furnished to the CO.

If in the opinion of the Contractor, any instruction or direction issued by the COR is outside of their specific authority, the Contractor shall not proceed but shall notify the CO in writing within five (5) business days after receipt of any instruction or direction.

The COR for the IDIQ contract is TBD.

G-1.1.3 Task Order Contracting Officer’s Representative (TCOR) The program office point of contact will be identified as the TCOR for each individual task order award. The TCOR is the individual within the program management function who has overall technical responsibility for this effort. The TCOR provides technical direction to the Contractor, i.e., shifting work emphasis between areas of work; fills in details, or otherwise serves to accomplish the purposes of this effort. Technical direction shall be within the general Performance Work Statement (PWS) for this effort.

In addition to providing technical direction, the TCOR will:

Monitor the Contractor's technical progress, including surveillance and assessment of performance, and recommend to the COR to notify the CO, any changes in the requirement;

Assist the Contractor in the resolution of technical problems encountered during performance; and

Perform inspection and acceptance or recommendation for rejection of Contractor deliverables and identify deficiencies in delivered items.

This does not replace any other quality assurance inspection requirements that are specified elsewhere within this contract.

NEITHER the COR nor the TCOR has the authority to issue any technical direction which:

Constitutes an assignment of work outside the general scope of this effort Constitutes a change as defined in the "Changes" clause In any way causes an increase or decrease in cost or the time required for performance Changes any of the terms, conditions, or other requirements of this effort Suspends or terminates any portion of this effort

G-1.2 Contractor

G-1.2.1 Program Manager The Contractor shall provide a Program Manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Contractor when the Program Manager is absent shall be designated in writing to the CO. The Program Manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

G-1.2.2 Task Order Project Manager The Project Manager for each task order will facilitate communication between the Government and the Contractor. The Project Manager will participate in Technical Interchange Meetings (TIMs) upon request by the CO or COR to discuss the status of Contractor efforts and accomplishments in direct relation to specific task orders. In addition, the Project Manager will manage Contractor employees and performance associated with any issued task order, keep the Government appraised of actual or potential Contractor program management problems associated with specific task orders, report unresolved problems to the Government, perform corrective actions for all identified Contractor deficiencies, support periodic meetings, teleconferences, and In Progress Reviews (IPRs) convened at the direction of the CO/COR and/or senior officials to review status of effort, requirements, and accomplishments.

G-2.0 Non-Personal Service Statement Contractor employees performing services under this PWS will be controlled, directed, and supervised at all times by management personnel of the Contractor. Contractor management will ensure that employees properly comply with the performance work standards outlined in this PWS. Contractor employees will perform their duties independent of, and without the supervision of, any Government official. The tasks, duties, and responsibilities set forth in specific task orders may not be interpreted or implemented in any manner that results in any Contractor employee creating or modifying Federal policy, obligating the appropriated funds of the U.S. Government, overseeing work of Federal employees, providing direct personal services to any Federal employee, or otherwise violating the prohibitions set forth in Part 7.5 and 37.1 of the FAR. The Government will perform the inspection and acceptance of the work provided.

G-3.0 Subcontractor(s) Consultants and subcontractors may be used if beneficial to the Government.

G-4.0 USE OF NON-GOVERNMENT ADVISORS

Contractors are advised that technical and price data submitted to the Government in response to task order requests for proposals may be released to non-Government advisors that have signed non-disclosure agreements for review and analysis. If a Contractor objects to disclosure of a portion of any task order proposal, objection to disclosure shall be provided in writing to the CO within 10 calendar days of task order request for proposal issuance and shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the Contractor objects to disclosure to non-Government advisors.

G-5.0 TASK ORDER PROCEDURES

The Government will issue the Task Order (TO) Request for Proposal (RFP) to the prime Contractor(s) consistent with the ordering procedures contained in the FAR and DFARS. The Government intends to give all multiple award Contractors a “fair opportunity” to compete unless an exception is authorized in statute or regulation to the “fair opportunity” process (see FAR 16.505(b), and as it may be amended in the future).

TOs will be issued on a Fixed Price, Labor Hour, or Cost-Reimbursement basis. For Fixed Price task order awards, invoicing and payment terms will be negotiated at the individual task order level. For Cost-Reimbursement task orders, the Government may require the submittal of cost and pricing data with proposals and will conduct a cost realism analysis.

Performance can only be authorized by issuance of a Task Order or revision thereto issued by the CO. Any changes will be issued in writing, will set forth any additional obligation incurred by the Government, will be adequately funded, and shall be signed by the CO in advance of the contractor initiating the change.

G-5.1 Task Order Request for Proposal (RFP) The Government will issue an RFP which will include at a minimum:

Performance Work Statement (PWS), Statement of Work (SOW), or Statement of Objectives (SOO)

Period of Performance (POP) Anticipated Contract Type(s) CLIN Schedule or request for contractor-proposed CLIN Schedule Applicable Evaluation Criteria (non-price/cost and price/cost factors) Questions/Clarifications Due Date Proposal Due Date

G-5.2 Task Order Proposal Each proposal shall include a brief description of the following (if requested in the RFP):

Technical proposal stating how the Contractor proposes to accomplish the effort, including a description of the performing team member(s) and any requested key personnel (to always include at least a Task Order Project Manager).

Price/cost proposal organized by CLIN and any supporting cost details (labor category mix, hours, and direct/indirect rates). Rates for labor hour orders shall be at or below those contained in the established Pricing Attachment 3 in Section J of the base IDIQ contract. Discounts are highly encouraged.

The percentage of the proposed total price for the TO that will go to small businesses.

Small business prime contractors shall be defined by the applicable size standard associated with the NAICS code 541990. Small business subcontractors shall be defined by the applicable size standards associated with the NAICS code that the prime contractor determines best describes the product or service being acquired by the subcontract.

For each TO RFP after the first, the actual percentage of the total price of previous task orders that went to small businesses. A separate percentage should be submitted for each previous task order received under this contract.

For each TO RFP after the first, personnel retention rate by task order and compliance statistics with the performance requirements outlined in PWS Section 11.2.

Resolution of any potential organizational conflict(s) of interest (OCI) or a statement explaining why none exists.

Any additional input as required by the RFP.

G-5.3 Task Order Evaluation Process The evaluation process for each TO will use a variation on the best value analysis spectrum (Lowest Price Technically Acceptable to Trade-Off based on complexity). Non-price/cost and price/cost factors will be considered as evaluation criteria. Specific factors will be established by individual TO. In making the best value determination, it is possible that after conducting a tradeoff analysis of the proposals, the lowest price may not necessarily represent the best value.

After proposals have been evaluated against the factors identified in the RFP, and the Contractors’ rates have been verified, the TO will be awarded to the IDIQ contract holder whose proposal represents the best value to meet the Government’s needs.

Contractors are put on notice that, among other evaluation factors listed in the RFP, total small business utilization for the proposed task order may be an evaluation factor. Contractors are also put on notice that after the issuance of the first task order, past performance with regard to proposed small business utilization on previous task orders may be an evaluation factor on every subsequent RFP.

G-5.4 Authorized Ordering Officials All DARPA contracting officers within warrant restrictions may order from this IDIQ. DARPA Agents, fulfilling DARPA requirements, may order from this IDIQ with written delegation from the IDIQ Contracting Officer.

SECTION I - CONTRACT CLAUSES

The following have been added by reference:

252.227-7013 Rights in Technical Data--Other Than Commercial Products and Commercial Services

JAN 2023

252.227-7014 Rights in Other Than Commercial Computer Software and Other Than Commercial Computer Software Documentation

JAN 2023

The following have been added by full text:

52.215-23 LIMITATIONS ON PASS-THROUGH CHARGES (JUN 2020)

(a) Definitions. As used in this clause--

Added value means that the Contractor performs subcontract management functions that the Contracting Officer determines are a benefit to the Government (e.g., processing orders of parts or services, maintaining inventory, reducing delivery lead times, managing multiple sources for contract requirements, coordinating deliveries, performing quality assurance functions).

Excessive pass-through charge, with respect to a Contractor or subcontractor that adds no or negligible value to a contract or subcontract, means a charge to the Government by the Contractor or subcontractor that is for indirect costs or profit/fee on work performed by a subcontractor (other than charges for the costs of managing subcontracts and any applicable indirect costs and associated profit/fee based on such costs).

No or negligible value means the Contractor or subcontractor cannot demonstrate to the Contracting Officer that its effort added value to the contract or subcontract in accomplishing the work performed under the contract (including task or delivery orders).

Subcontract means any contract, as defined in Federal Acquisition Regulation (FAR) 2.101, entered into by a subcontractor to furnish supplies or services for performance of the contract or a subcontract. It includes but is not limited to purchase orders, and changes and modifications to purchase orders.

Subcontractor, as defined in FAR 44.101, means any supplier, distributor, vendor, or firm that furnishes supplies or services to or for a prime Contractor or another subcontractor.

(b) General. The Government will not pay excessive pass-through charges. The Contracting Officer shall determine if excessive pass-through charges exist.

(c) Reporting. Required reporting of performance of work by the Contractor or a subcontractor. The Contractor shall notify the Contracting Officer in writing if--

(1) The Contractor changes the amount of subcontract effort after award such that it exceeds 70 percent of the total cost of work to be performed under the contract, task order, or delivery order. The notification shall identify the revised cost of the subcontract effort and shall include verification that the Contractor will provide added value; or

(2) Any subcontractor changes the amount of lower-tier subcontractor effort after award such that it exceeds 70 percent of the total cost of the work to be performed under its subcontract. The notification shall identify the revised cost of the subcontract effort and shall include verification that the subcontractor will provide added value as related to the work to be performed by the lower-tier subcontractor(s).

(d) Recovery of excessive pass-through charges. If the Contracting Officer determines that excessive pass-through charges exist;

(1) For other than fixed-price contracts, the excessive pass-through charges are unallowable in accordance with the provisions in FAR subpart 31.2; and

(2) For applicable DoD fixed-price contracts, as identified in 15.408(n)(2)(i)(B), the Government shall be entitled to a price reduction for the amount of excessive pass-through charges included in the contract price.

(e) Access to records. (1) The Contracting Officer, or authorized representative, shall have the right to examine and audit all the Contractor's records (as defined at FAR 52.215-2(a)) necessary to determine whether the Contractor proposed, billed, or claimed excessive pass-through charges.

(2) For those subcontracts to which paragraph (f) of this clause applies, the Contracting Officer, or authorized representative, shall have the right to examine and audit all the subcontractor's records (as defined at FAR 52.215- 2(a)) necessary to determine whether the subcontractor proposed, billed, or claimed excessive pass-through charges.

(f) Subcontracts. The Contractor shall insert the substance of this clause, including this paragraph (f), in all cost-reimbursement subcontracts under this contract that exceed the simplified acquisition threshold, as defined in FAR

2.101 on the date of subcontract award, except if the contract is with DoD, then insert in all cost-reimbursement subcontracts and fixed-price subcontracts, except those identified in FAR 15.408(n)(2)(i)(B)(2), that exceed the threshold for obtaining cost or pricing data in FAR 15.403-4(a)(1) on the date of subcontract award.

(End of clause)

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The Table of Contents has changed from:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Attachment 1 1 - TASS PWS 17 10-FEB-2023 Attachment 1A 1A - Additional

Requirements

4 10-FEB-2023

Attachment 2 2 - DARPA NDA 1 10-FEB-2023 Attachment 3 3 - LH LCAT Pricing

Spreadsheet

1 10-FEB-2023

Attachment 4 4 - Technical Experience Referenced Contracts

10-FEB-2023

Attachment 5 5 - Past Performance Questionnaire

6 10-FEB-2023

Attachment 6 6 - Accounting System Checklist

3 10-FEB-2023

Attachment 7 7 - Solicitation Question Matrix

10-FEB-2023

Attachment 8 8 - Draft DD254 5 10-FEB-2023 to:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Attachment 1 1 - TASS PWS 17 10-FEB-2023 Attachment 1A 1A - Additional

Requirements

4 10-FEB-2023

Attachment 2 2 - DARPA NDA 1 10-FEB-2023 Attachment 3 3 - LH LCAT Pricing

Spreadsheet

1 10-FEB-2023

Attachment 4 4 - Technical Experience Referenced Contracts

10-FEB-2023

Attachment 5 5 - Past Performance Questionnaire

6 10-FEB-2023

Attachment 6 6 - Accounting System Checklist

3 10-FEB-2023

Attachment 7 7 - Solicitation Question Matrix

10-FEB-2023

Attachment 8 8 - Draft DD254 5 10-FEB-2023 Attachment 9 9 - Questions and

Answers

7 03-MAR-2023

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

PROPOSAL PREPARATION

Section L: Proposal Preparation and Submission

L.1 Solicitation Point of Contact Mary Beth Colavito Contracting Officer Defense Advanced Research Projects Agency Contracts Management Office (DARPA/CMO) 675 N. Randolph Street Arlington, VA 22203-2114 Email: TASSIDIQREQUIREMENT@darpa.mil

L.2 Overview Solicitation HR001123R0001 is a Request for Proposal (RFP) issued by the Defense Advanced Research Projects Agency (DARPA) under North American Industry Classification System (NAICS) Code 541990 “All Other Professional, Scientific, and Technical Services.” DARPA Contracts Management Office (CMO) intends to award approximately seven (7) multiple-award Indefinite Delivery / Indefinite Quantity (ID/IQ) contracts under a single full and open competition solicitation.

The DARPA-wide Technical and Analytical Support Services (TASS) contract will be a centrally managed multiple-award Advisory and Assistance Services (A&AS) ID/IQ contract, with a combination of Fixed Price (FP), Cost-Reimbursement (CR), and Labor Hour (LH) Task Orders (TOs).

L.3 Proposal Due Date Proposals are due by 10:00 am Eastern on Monday, March 13, 2023, via email (Subject Line:

TASS ID/IQ Proposal – [Offeror Name]) to DARPA CMO Contracting Officer at TASSIDIQRequirement@darpa.mil.

L.4 Questions Due Date Questions/clarifications to this solicitation are due by 10:00 am Eastern on Wednesday, February 22, 2023. The DARPA CMO Contracting Officer is the sole point of contact for all questions under this solicitation. Offerors shall submit all questions using the Questions Matrix in Attachment 7 via email (Subject Line: TASS ID/IQ Questions – [Offeror Name]) to the

Contracting Officer at TASSIDIQRequirement@darpa.mil. Questions will be answered in the form of an amendment to this solicitation and posted electronically on SAM.gov.

L.5 Offer Acceptance Period The offer acceptance period is a minimum of 180 calendar days from the proposal due date and should be appropriately represented in block 12 of the signed Standard Form (SF) 33, Solicitation, Offer and Award. The Offeror agrees to hold its offered prices firm for the services solicited herein and to accept any resulting contract subject to the terms and conditions stated herein. If there is a discrepancy between the offer acceptance period requirement in this solicitation and the SF 33, the date entered on the SF 33 will take precedence. Offers with an acceptance period of less than 180 calendar days will not be accepted.

L.6 Proposal Submission Requirements

Offerors are instructed to read the entire solicitation document, including all attachments, prior to submitting questions and/or preparing your proposal. Omission of any information from the proposal submission requirements during the Contracting Officer's compliance review may result in the rejection of the proposal.

Offerors shall submit their proposals via email to TASSIDIQRequirement@darpa.mil.

The proposal shall be formatted into a transmittal letter and six (6) separate electronic files by volume number and title as follows:

Volume I - Transmittal Letter Volume II - Administrative Volume III - Technical Experience Volume IV - Management Approach Volume V - Past Performance Volume VI - Small Business Participation Volume VII - Price

The file shall be labeled with the solicitation number and company name. It is the sole responsibility of the Offeror to ensure that the electronic files submitted are virus free and can be opened and read by the Government. Submissions shall not be locked, encrypted (except the file containing the information requested in Section L.8.2(a), which may be encrypted if necessary), or otherwise contain barriers to opening. All proposal documents shall be in Adobe (.pdf) or compatible format except portions of the price submission, which shall be in MS Excel 2016 (.xlsx) or compatible format. Attachment file sizes may not be larger than 10MB.

Offerors shall adhere to Volume numbers, format and/or templates, and page limitations.

Offerors shall include their company name or company name abbreviation and Volume number in the filename (e.g., CMPNYA - Vol. II). If page limitations are exceeded, where page limits are expressed, the excess pages will not be evaluated.

Classified submissions will not be accepted.

L.7 Volume I - Proposal Transmittal Letter (3 page limit)

Volume I shall contain a letter formally transmitting the proposal to include the following:

a. Statement of Compliance. Each Offeror shall include a statement indicating complete compliance with this solicitation, or detailed analysis of any objections, exceptions, contingencies, or additions. Any objections, exceptions, contingencies, or additions shall also cross-reference the particular paragraph(s) in this solicitation to which it applies.

b. Proprietary Information. Each Offeror shall include a statement indicating whether the Offeror intends to make use of any proprietary information.

c. Format and Content. Each Offeror shall describe any deviations in its proposal from the specified format of this solicitation. If the content of the Offeror's proposal differs significantly from these guidelines, state the differences, and explain the reason for the differences.

d. Points of Contact. Each Offeror shall include primary and alternative points of contact to include title, mailing address, email, and phone number.

e. Business size status (under NAICS Code 541990).

f. Unique Entity Identifier (UEI) and Commercial and Government Entity (CAGE) Code(s).

L.8 Volume II - Administrative (No page limit)

Volume II shall include all solicitation documents as outlined below and in this order. If an Offeror fails to provide or adequately comply with any of the following requirements, the proposal may be rejected without further evaluation.

L.8.1 Joint Venture/Teaming Arrangements The Offeror shall provide, if applicable, a summary describing the Joint Venture/Teaming Arrangement established for this solicitation and a document establishing the legally binding nature among the joint venture/teaming parties. The Government encourages teaming to the maximum extent practicable required to meet solicitation requirements. The Offeror shall indicate on the summary if any teaming arrangements are exclusive. In order to promote maximum competition, the Government discourages exclusive teaming arrangements.

L.8.2 Security

a. The Offeror shall provide, as part of this proposal Volume, a copy of its documentation from the Defense Counterintelligence and Security Agency (DCSA) Facility Clearance Branch that grants its facility and security clearance level at the Top Secret level proving it was granted by time of proposal submission.*

b. Include a statement certifying the Offeror's ability to provide and maintain contractor personnel up to and including a Top Secret/Sensitive Compartmented Information (SCI) minimum with Special Program Access eligibility.

* Note: The Top Secret Facility clearance must be current at time of proposal submission, and the Government will not sponsor facility clearances in anticipation of this award.

L.8.3 Organizational Conflict of Interest

The Offeror shall disclose complete information of any work performed by its company that is in any way associated with the contemplated acquisition or which could result in a potential organizational conflict of interest. Under DARPA organizational conflict of interest policy, without prior approval or a waiver from the DARPA Deputy Director, in accordance with Federal Acquisition Regulation (FAR) 9.503, a contractor cannot simultaneously be a scientific, engineering, technical assistance (SETA) support contractor and also be a research and development performer at DARPA. Therefore, all Offerors must affirm whether it (its organizations and individual team members) are acting as a research and development performer to DARPA through an active contract or subcontract. All affirmations must identify the prime contract number(s). Affirmations shall be furnished at the time of proposal submission by the Offeror on behalf of themselves and all proposed subcontractors and consultants. All facts relevant to the existence or potential existence of organizational conflicts of interest (FAR 9.5, Organizational and Consultant Conflicts of Interest) shall be disclosed. The disclosure shall include a description of the action the Offeror has taken or proposes to take to avoid, neutralize, or mitigate such a conflict. If, in the sole opinion of the Government, after full consideration of the circumstances, a proposal fails to fully disclose potential conflicts of interest and/or any identified conflict situation cannot be effectively mitigated, the proposal will be rejected without technical evaluation and withdrawn from further consideration for award.

If a prospective Offeror believes that any conflict of interest exists or may exist (whether organizational or otherwise) or has questions on what constitutes a conflict of interest, the Offeror should promptly raise the issue with DARPA by sending his/her contact information and a summary of the potential conflict to the Contracting Officer before time and effort are expended in preparing a proposal and mitigation plan.

The Offeror shall acknowledge the requirement for a Non-Disclosure Agreement in the format prescribed by Attachment 2 by including a copy within this Volume submission signed by the authorized representative listed in in Section L.8.4. This Non-Disclosure Agreement will be included in successful ID/IQ awards and will be mandatory for all personnel working under task order awards.

L.8.4 Standard Form 33 The Offeror shall complete blocks 12 through 19 of the Standard Form (SF) 33. If any amendments to this solicitation are issued, the Offeror shall acknowledge each amendment number and date in block 14 of the SF 33. The Offeror's legal name and address in block 15A must match the information for the Offeror in System for Award Management (SAM) (http://www.sam.gov), including the corresponding Commercial and Government Agency (CAGE) Code number and Unique Entity Identifier (UEI). The name, title, signature, and date identified in blocks 16, 17, and 18, must be an authorized representative with the authority to commit the Offeror to contractual obligations.

L.8.5 Accounting System The Offeror shall provide proof of a Defense Contract Audit Agency (DCAA)-approved accounting system or must complete the Accounting System Checklist in Attachment 6 and include it within this Volume submission. Offerors should note that if it is awarded an ID/IQ contract without already having a DCAA-approved accounting system, it will not be eligible to submit proposals for task order requirements with Cost-Reimbursement Contract Line Item Numbers (CLINs) until a DCAA Cost Accounting System Audit is performed and approved after ID/IQ award.

L.8.6 Subcontracting Plan Small businesses, as defined in FAR 52.219-1 as a Small Business Concern, are not required to submit a Subcontracting Plan. For other than small businesses, the Offeror shall provide a Subcontracting Plan. An individual Subcontracting Plan is preferred, but an Offeror may submit any type of Subcontracting Plan as long as it conforms with FAR 19.704, Subcontracting Plan Requirements, and FAR 52.219-9, Small Business Subcontracting Plan, including a Department of Defense Comprehensive Subcontracting Plan as long as it is approved by the Defense Contract Management Agency. Subcontracting Plans shall reflect the Offeror's commitment, in terms of the value of the total acquisition, to small businesses as proposed in response to Factor 4: Small Business Participation. Subcontracting Plans that do not reflect at least the same small business participation (e.g., percentage and type of small business concern) as proposed in response to Factor 4 will be considered non-compliant with this solicitation.

L.8.7 Meeting Space Capability The Offeror shall provide either proof of existing facilities or proof of a contingency offer within the proposal that can be executed upon ID/IQ contract award to meet meeting requirements outlined in PWS paragraph 7.9.3 by the ID/IQ Period of Performance start date.

L.8.8 Representation, Certification, and other Statements of Offerors The Offeror shall complete representations, certifications, acknowledgments, and statements via the System for Award Management (SAM) (http://www.sam.gov). A completed copy from SAM and any additional Section K information required by this solicitation shall be included in this Volume.

L.8.9 Terms and Conditions The Offeror is required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors. By submission of its proposal, the Offeror accedes to all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements.

L.9 Volume III - Evaluation Factor 1: Technical Experience (15 page limit)

Volume III shall be specific, detailed, and complete to demonstrate clearly and fully that the Offeror has the technical experience to accomplish all requirements of the PWS. Offerors shall document their current, relevant technical experience as it relates to the following exemplar sections of the PWS:

PWS Section 7.1.2 (Technical Expertise/Subject Matter Expertise (SME))* PWS Section 7.2.2 (Program Financial Execution) PWS Section 7.9.1 (Event Assistance)

Statements that the Offeror has demonstrated experience to accomplish the listed functions without supporting information or narrative is inadequate. This section shall be written to enable evaluators to make a thorough evaluation as to whether the Offeror has demonstrated experience and shall contain specific descriptions and examples of work performed to include value, complexity, and nature in exemplar PWS Sections 7.1.2, 7.2.2, and 7.9.1, listed in order of importance. The individual PWS Section responses are not to be considered subfactors for evaluation. Each Offeror will only receive a single rating for Factor 1.

*For PWS Section 7.1.2, the Offeror shall show experience across the breadth of the type of technologies performed within technical offices identified in PWS Section 4 (i.e., Biological Technologies, Defense Sciences, Information Innovation, Microsystems Technology, Strategic Technology, and Tactical Technology).

Factor 1: Technical Experience will focus on what work the Offeror has done correlated to this requirement, while Factor 3: Past Performance will focus on how well the Offeror has historically performed. Therefore, Offerors shall demonstrate a direct link between technical experience cited in this factor and contracts submitted for past performance.

Any technical experience referenced must have been performed since January 1, 2018, and must have a contract/order value over $15 million. An ID/IQ contract must have at least one task order exceeding $5 million. All contract values shall be representative of obligation amounts; when submitting for an ID/IQ contract, the obligation amount shall represent the combined obligation of all awarded task orders.

Given the value, complexity, and nature of this procurement, all past or current contract performance referenced as technical experience shall be performance as a prime contractor. All referenced contracts shall be listed in Attachment 4, providing a minimum of the following information: contract number, period of performance (including months/years), contract value, the amount invoiced to date, and Government point of contact (POC).

Attachment 4 will not count against established page limits but shall not include any more information than required.

There is no limit on the number of contracts/orders that can be referenced and listed within Factor 1: Technical Experience.

L.10 Volume IV - Evaluation Factor 2: Management Approach (10 page limit) The Offeror shall provide its proposed management approach for delivering high quality support services to accomplish all requirements of the PWS through Sections (a) through (d) below, which are for factor organization purposes only and are not to be considered subfactors for evaluation. Each Offeror will only receive a single rating for Factor 2.

a. Overall ID/IQ Management Plan

Plan for managing multiple task orders and multiple subcontractors. The plan shall describe how the Offeror is able to manage several orders and several subcontractors across the full range of PWS requirements.

Program Management Team construct, qualifications, and commitment. The Program Management Team is defined, at a minimum, as the overall Contract Program Manager and any other members required to successfully manage an ID/IQ of this size and complexity (e.g., office leads, functional leads, etc.). Offerors shall provide resumes of the proposed Program Management Team, the type of commitment individual(s) has with the company (e.g., contingent, employed, representative), and letter(s) of intent (if applicable). The proposed Program Management Team will be considered Key Personnel at the ID/IQ level. Note: Resumes submitted are restricted to two (2) pages per individual on the Program Management Team and do not count towards the overall 10-page limit.

Letters of intent are restricted to one (1) page per individual on the Program Management Team and do not count towards the overall 10-page limit.

b. Recruitment and Retention

The Offeror shall describe its overall staffing/hiring methodology to address evolving DARPA needs. The Offeror shall describe what subcontracting and hiring practices will be used and illustrate the process for filling vacancies for extremely technically advanced expertise in a timely manner. Identify how the corporation/team can readily obtain the experience and expertise required to accomplish the full range of PWS support requirements. Offeror shall include the historical average time(s) to execute services subcontracts (i.e., not commodity purchases) for all contracts described in Technical Experience via Attachment 4 (measured as time between Government identification of a new in-scope requirement during the performance of a contract or task order and the date of the subcontract award issued to meet this requirement).

The Offeror shall describe its plan to incentivize on-site, off-site, and hybrid employees with varying levels of telework available per task order and position.

The Offeror shall describe a specific detailed plan for effectively retaining Science and Technology (S&T) and Research and Development (R&D) professional support in efforts to minimize the turnover rate to avoid mission degradation.

In accordance with FAR 52.222-46, Evaluation of Compensation for Professional Employees, the Offeror shall submit a total compensation plan setting forth salaries and fringe benefits proposed for all professional employees (per FAR 22.1102 definition) who will work under the contract. The compensation levels proposed should reflect a clear understanding of work to be performed and should indicate the capability of the proposed compensation structure to obtain and keep suitably qualified personnel to meet mission objectives. The salary rates or ranges must take into account differences in skills, the complexity of various disciplines, and professional job difficulty. NOTE: Total Compensation Plan does not count towards the overall 10-page limit for Management Approach.

c. Training

The Offeror shall describe in detail how it plans to quickly and effectively train and mentor new personnel on DARPA procedures, collaboration tools (especially those listed in PWS Section 7.3.5), and policy.

d. Culture

The Offeror shall describe its methodology for measuring, strengthening, and promoting its organizational culture in a hybrid (in-person and virtual) work environment. Specifically, the Offeror shall describe its approach to promoting its organizational culture among its on-site, off-site, and hybrid employees, including its plan to:

o Rapidly onboard and successfully assimilate new personnel to DARPA culture, and then create, promote, and preserve a sense of community between its personnel, as well as Government and other contractor personnel, in a hybrid environment;

o Facilitate knowledge sharing across multiple contractor and Government teams supporting DARPA; and o Ensure that provided collaboration tools (especially those listed in PWS Section 7.3.5) are available and maximally leveraged to integrate hybrid personnel.

L.11 Volume V - Evaluation Factor 3: Past Performance (12 page limit)

The Offeror shall submit a Past Performance Volume containing the following information:

a) Table of Contents; b) Summary Page; c) Past Performance Information Submissions; d) Contractor Performance Assessment Reporting System (CPARS) and Questionnaire Submissions; and e) Organization Structure Change History, if applicable.

a. Table of Contents (No page limit) The table of contents should include page numbers for each CPARS evaluation by contract and applicable Period of Performance.

b. Summary Page (No page limit) The Summary Page shall describe the role of the

Offeror and each teaming partner, if applicable, for the proposed TASS effort.

c. Past Performance Information Submissions (12 page limit)

Offerors may provide up to six (6) past performance information submissions, of which at least half of the submissions must be from the prime contractor. Given the value, complexity, and nature of the procurement, all past or current contract performance information submitted for the prime or any subcontractors shall be performance as a prime contractor. All submissions shall relate to experience submitted within Factor 1: Technical Experience and shall only be for contracts/orders over $15 million or for an ID/IQ contract with at least one task order exceeding $5 million. All contract values shall be representative of obligation amounts; when submitting for an ID/IQ contract, the obligation amount shall represent the combined obligation of all awarded task orders.

All submissions must be recent, as defined by services performed since January 1, 2018.

Offerors shall provide a two-page summary for each Past Performance Information Submission.

The summary shall include the following (in the below order):

i. Identify the full contract number (and task/call order number if applicable – each task/call order is considered a submission) and program/requirement title.

ii. Identify the period of performance to include the months, days, and years

(MM/DD/YYYY; e.g., 02/15/2018 – 02/14/2022).

iii. Identify the current obligation dollar amount, total contract value, and/or potential ceiling, as applicable.

iv. Identify contract type(s).

v. Identify whether the submission was performed by the Offeror or a proposed subcontractor as the prime.

vi. Identify the Government customer office name for the submission and provide the names, titles/roles, phone numbers, and email addresses of the following Government customer points of contact (POC) that may be knowledgeable of the Offeror's performance on the submission: Program Manager, Contracting Officer (CO), Administrative Contracting Officer (ACO), and Contracting Officer's Representative/Contracting Officer's Technical Representative (COR/COTR).

vii. Provide a brief description of the effort performed as a prime contractor and any significant portions of the effort performed by key subcontractors.

viii. Demonstrate how the Offeror's or proposed subcontractor(s)' performance is relevant (in scope, magnitude, and complexity) to the PWS requirements.

ix. Describe any problems encountered on the identified contract and any corrective action taken, to include response to any adverse past performance information available to the Government, as well as any efforts to identify and manage program risk.*

*Note: Merely having problems does not automatically equate to a "Limited Confidence" or "No Confidence" assessment, since the problems encountered may have been unavoidable, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered.

The Offeror (or Subcontractor) shall clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may give the Offeror a higher confidence assessment rating. For example, submittal of quality performance indicators or other management indicators that clearly support an Offeror has overcome past problems would assist the Government when assigning the confidence assessment rating.

If the Offeror does not have any past performance information, the Offeror must state in this section that it possesses no relevant past performance. Offerors with no relevant past performance will receive a past performance rating of "Neutral Confidence".

In the conduct of its past performance evaluation of Offerors, DARPA may use a variety of sources in addition to information provided by the Offeror. DARPA/CMO may use past performance information obtained from sources other than those identified by the Offeror. These sources may include, but are not limited to, CPARS, Past Performance Information Retrieval Systems (PPIRS), technical reports, evaluator's personal knowledge, commercial or any available published information, and information derived from present or past Government or commercial customers of the Offeror. Those Offerors who have no relevant past performance history will not be evaluated either favorably or unfavorably on past performance. DARPA reserves the right to determine which contracts submitted by the Offeror are relevant to the requirements and to utilize only those references.

d. CPARS and/or Past Performance Questionnaires (No page limit)

For each Past Performance Information Submission, Offerors shall submit ALL Contractor Performance Assessment Reporting System (CPARS) evaluations that were completed for the relevant time period (since January 1, 2018).

If CPARS evaluations are not available, Offerors (or subcontractors) shall request that their Government customer submit past performance information on the Past Performance Questionnaire (PPQ) found at Attachment 5. The POCs identified on the questionnaire must be able to provide information on the quality of the Offeror or subcontractor's performance. The Offeror's customers must send past performance information to TASSIDIQREQUIREMENT@darpa.mil by the proposal due date. The Offeror shall include in this section proof of correspondence with Government customer requesting past performance information (e.g., copy of date-stamped email).

e. Organization Structure Change History (No page limit)

Many Offerors have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized its divisions, business groups, subsidiary companies, etc. In many cases, these changes have occurred during the performance of relevant past efforts or between conclusion of recent past efforts and source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this procurement. To facilitate this relevancy determination, include in this proposal Volume (if applicable), a "roadmap" describing all such changes in the company within the past seven (7) years. As part of this explanation, show how these changes impact the relevance of any efforts identified for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources, as well as that provided by the Offeror, the Offeror's "roadmap" should be specifically applicable to the efforts identified but general enough to apply to efforts on which the Government receives information from other sources. This information is required for the Offeror and any teaming partner(s) being used for past performance information submissions. The Government reserves the right to exclude sources due to conflicts of interest.

Determination of Responsibility: Even though the assessment of past performance information as a specific evaluation factor is separate and distinct from the determination of responsibility required by FAR 9.1,…