Emergent IV BAA Amendment 19 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 4

19 04/05/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 answer questions relating to the Use Case for Hackathon.

a. Question: For clarity, is this the use Case, and only use case that will be used for the Demo?

Answer: At the demonstration, this is the only use case that would be used for vendors to demonstrate their capabilities. During the demonstration phase, vendors may be subject to prompt questions to further demonstrate technical and functional requirements noted in their technical proposal.

b. Question: I assume we should talk about this use case in our Tech Proposal, but also broader use case capabilities as well?

Answer: Please discuss this use case as well other the other capabilities noted in the requirements to align to DoD and DLA mission sets. The use case approach should be integrated into the proposal which should illustrate the methodologies to training AI/ML/GENAi data models for product development.

c. Question: Is this SITREP use case a change in scope from the BAA?

Answer: No, the BAA requirements are to provide the functional and technical approaches and methodologies for Ai, ML, and Gen Ai testing and development. This will derive a solution that meets the DLA missions sets, moreover, the BAA Amendment 15 sites 14 task areas that align to best practices and principals for Ai, ML and Gen Ai solutions sets. The use case provided is a culmination of those task areas.

d. Question: What is the nature of the relationship between this SITREP use case task and the tasks and areas of interest outlined in the BAA?

Answer: Expounding on the previous questions regarding the task areas provided in the BAA Amendment 15, the SITREP targets task areas that are foundational to meet the tactical and strategic priorities of DLA. Additionally, DLA’s intent of the SITREP is to have the vendor demonstrate not only the technical capability but more importantly their functional understanding of DLA internal and external business practices.

e. Question: Given this SITREP use case, does DLA expect that we will tailor our technical proposal to this specific task area?

Answer: DLA expects the vendor to be savvy to clearly articulate their technical capabilities not only in SITREP specific task area but their overall approach to Ai, ML, and Gen Ai domains to derive solutions that meet DLA’s Combat Logistics Global Supply Chain mission.

f. Question: We presume that since this utilizes OS data, this effort (up to and including the hackathon demonstration) is not CUI. Are follow on tasks expected to be performed entirely at an unclassed level, or entirely at CUI and/or higher?

Answer: Yes, the initial tasks will be with unclassified/CUI and higher level.

g. Question: Or can we provide a plan to complete work at an unclassed level with demonstrations, evaluations, integrations and support at a higher level?

Answer: Initially, DLA will provide data unclassified/CUI data sources.

Additionally, DLA welcomes the vendor to provide a future state of how their Ai, ML, Gen Ai solution can adjust to classified data sources to include data demonstration and evaluation in classified environments.

h. Question: Just to confirm, our understanding is that DLA is not funding the hackathon demonstration; all cost scoping is for the technical solution proposed in our technical and cost proposal.

Answer: That is correct

i. Question: Can you help contextualize this SITREP use case within the most recent DLA strategic plan; is this more in-line with LOE 5 and CC-C or LOE 4 and CC-B, or does DLA have a different envisioned context for this use-case?

Answer: It encompasses all LOEs and encourages the vendor to leverage public facing data sources to obtain for additional sourcing for the SITREP.

j. Question: Can we be provided with current SITREP samples to ensure our demonstrated solution aligns with DLA best practices and existing training, workflow and decision structures? Alternatively, are there DLA staff who currently produce SITREPs with whom we can speak to assess and discuss workflow, practices and output?

Answer: No, DLA SITREP contains sensitive data based on our mission;

however, the goal is not about the SITREP data but how your capabilities create content based on the guidance and intent provided for the criteria as well as your understanding of the DLA domain.

k. Question: Can you describe or outline the data sources, providers or clarify the types of data that DLA currently employs and/or expects to employ to support this SITREP use case task. Does this differ from the data sources or providers associated with the tasks and areas of interest outlined in the BAA?

Answer: The data derived from the task areas outline in the BAA are a solid source of data to support SITREP development, in addition to DoD and DLA public facing sites (EG, webpages, OPM, SAM.gov, etc.). Please note, our expectations is that the vendor has an understanding of DoD and DLA web scrapping sources and binoculars.

2. All other Terms and Conditions remain unchanged.