Emergent IV BAA Amendment 16 1.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICAITON NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicble)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICIATION NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers 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 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 your 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 APPROPIRATION DATA (If required)

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

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

CHECK ONE 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.

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.

15C. DATE SIGNED

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

16C. DATE SIGNED

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

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

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

NSN 7540-01-152-8070

Previous edition unusable

1 5

16 03/13/2024

SP4701

DLA Contracting Services Office - Philadelphia 700 Robbins Ave.

Philadelphia, PA 19111 Attn: R&D CONTRACTING TEAM

SAME AS BLOCK 6

BAA0001-22

06/13/2022

See Continuation Pages.

Emergent IV BAA0001-22, dated June 14, 2022, is hereby Amended as follows:

1. The purpose of this modification is to answer questions that were posed from Amendment 15 regarding DLA’s J6 Hackathon.

a. Detailed Hackathon timeline:

1. Release of Amendment 15 2/28/24

2. TET will review White Papers as they come in.

3. Closing window to vendor responses 3/20/24

4. Contracting Officer to submit notifications to Vendors if they are moving forward to the next phase. Full Technical and Cost proposals requested from vendor. Rejection of White Paper notifications will be sent out 4/3/24

5. Final date for Vendors to submit the full Technical and Cost proposals 4/10/24

6. Notification to vendor that they are moving to the demonstration phase 4/17/24

7. Demonstrations 4/30/24 and 5/1/24

8. Final decision and notification to vendors 5/14/24

b. Question: What are the project deliverables for each task and/or phase?

Answer: Deliverables: 1. White Paper (see guidance under the Emergent IV);

2. Tech / Cost Proposals (in the event the vendor is selected to do so see guidance under the Emergent IV); 3. Demonstration (in the event the vendor is selected to do so see guidance under the Emergent IV Amendment 15).

c. Question: What are the evaluation criteria for the White Paper, Technical Proposal, and Demonstration?

Answer: The Cost and Technical Proposals will be evaluated in accordance with the Emergent IV BAA and the White Paper will be reviewed the same as any other White Paper submitted under the Emergent IV BA.

d. Question: Could the government clarify Section 6.0 Proposed Timeline?

Answer: Please see detailed timeline above.

e. Question: “Technical Evaluation Team to review White Papers – Two week after the window of responses is closed”

i. Does this mean the Evaluation Team begins review or ends its review on 4/3/2024?

Answer: The Technical Evaluation Team will end their review and notify the vendors by 4/3/2024.

f. Question: “Vendor requested to submit Technical proposals – One week”

i. Does this mean DLA will request proposals one week after it ends its review of the white papers? Or that vendors will be given one week to submit proposals after an RFP?

Answer: It means that the Technical Evaluation Team through the Contracting Officer on 4/3/24 will request proposals from the vendors selected to move forward to the next phase. In the event a vendor is not selected, they will receive a notification on 4/3/24 as well.

g. Question: We have the same questions on 6e and 6f. For full timeline clarity, could the government provide representative dates for the beginning and end of each phase?

Answer: Please see answer in a.

h. Question: Could the government please confirm that whitepapers (and corresponding proposals) should address only one of the given subtopics (Content Generation, Data Manipulation, Content Assistance)?

Answer: Per Section 4.0 Scope, submitters are not required to include all work areas in the White Paper submissions( since White Papers are limited to 6 pages); however, for those requested to submit a Technical and Cost Proposals, all of the above work areas are required to be included within the proposal. For the White Paper, the Vendor can address one of the subtopics in the scope area according to the BAA. In the event the Vendor is selected to move forward to submit a proposal, all 14 subtopics have to be addressed.

i. Question: For the purposes of the demonstration, could the government please confirm that it will provide one use case for each of the three subtopics (Content Generation, Data Manipulation, Content Assistance)?

Answer: In the event that the Vendor is asked to provide a full Cost and Technical Proposal (4/3/24), ONE use case will be provided. If the Vendor is selected to move forward to demonstrate their capabilities, it will be on the same use case that was previously provided on 4/3/24.

j. Question: Addressing all three subtopics in a single white paper (i.e., single project) may render the scope cost-prohibitive for the government.

Answer: The service work area(s)/task(s) to be addressed in the White Paper are detailed in section 4.0 Scope. For the White Paper, the Vendor can address one of the subtopics in the scope area according to the BAA. In the event the Vendor is selected to move forward to submit a proposal, all 14 subtopics have to be addressed.

k. Question: Addressing only one of the three subtopics could render our White Paper and Proposal moot if the government selects a demonstration use case from one of the other two subtopics.

Answer: The service work area(s)/task(s) to be addressed in the White Paper are detailed in section 4.0 Scope. For the White Paper, the Vendor can address one of the subtopics in the scope area according to the BAA. In the event the Vendor is selected to move forward to submit a proposal, all 14 subtopics have to be addressed.

l. Question: If selected for funded work, will all three project phases fall under a single J68 R&D award?

Answer: In the event that the Vendor is selected for award it will be a J68 R&D portfolio.

m. Question: What is the scope of the contract will DLA award at the end of this hackathon? Does DLA plan on issuing an award for an R&D project or is DLA planning on making an award for a production system?

Answer: The scope of the contract will be based on Emergent IV BAA Amendment 15, White Paper submission, and if requested Technical and Cost Proposal for demonstration. The award will be driven from the Vendor’s solutions set and ability to demonstrate transition into the DLA enterprise. The initial award will be R&D and DLA for long term sustainability.

n. Question: What IT environment will DLA use to host this system? Can this environment support the deployment of containers? Does DLA intend to modify the existing ATO of this environment or pursue a new ATO?

Answer: DLA is cloud agnostic; therefore, the solution must be scalable for a given cloud environment. Pertaining to the containers, if your capabilities are Azure or Google cloud based then DevSecOps does support the deployment of containers. DLA will upgrade the existing ATO to support AI solutions set.

o. Question: Is DLA willing to receive demos from more production-ready cloud environments like AWS or will they only accept demos in Google Labs?

Answer: The vendor can develop their solution in any cloud environment they prefer. DLA is cloud agnostic; therefore, allowing the vendor to use any cloud provider.

p. Question: The latest amendment does not specifically provide details on the period of performance and then total budget for the Gen AI hackathon teams.

Answer: The dollar value and period of performance will be based on responses received from the White Paper and subsequent Cost and Technical proposal.

2. All other Terms and Conditions remain unchanged.