TOPIC RELEASE 2 Q and A_Ph II.pdf

Question Answer

Q1: For Topic Release 2, the email inviting us to submit a Phase II proposal refers to proposal instructions in “Section 3 of the subject BAA”. Section 3 of HDTRA1-20-S-0001 refers to eligibility to submit a proposal, and does not contain submission instructions. To avoid any confusion, please clarify which section and which JSTO- CBD BAA the DTRA Acquisition team is referring to. If it’s not HDTRA1-20-S-0001 found at Caution-https://beta.sam.gov/ < Caution-https://beta.sam.gov/ > , please provide a link to the BAA.

A1. The Phase II proposal invitation is in response to BAA HDTRA1-20-S-0001. The reference to Section 3 of the BAA for instructions on developing a full proposal should have identified Section 4, Proposal Submission Information.

Q2: For Topic Release 2, please identify/clarify font size and font type requirements for the Phase II proposal documents. HDTRA1- 20-S-0001 does not specify; however there is a checklist on the DTRA submission site that refers to 12-point Times New Roman for the font.

A2: There are no specific font size/type requirements for the Phase II proposal documents.

Q3: For Topic CBI-03, the email inviting us to submit a Phase II proposal in response to CBI-03 refers to a “schedule detailed in the call”. There is no schedule detailed in HDTRA1-20-S-0001 or in Topic Release 2. To avoid any confusion, please clarify what is the desired schedule? For example, is it the 9 month base period followed by the options mentioned in the email?

A3: The desired schedule for all Phase II proposals in response to Topic CBI-03 is as follows: The offeror should propose an initial nine (9) month base period to support a feasibility study in Phase I of the project which consists of six (6) months for proof of concept model development and initial validation, followed by three (3) months of model refinement and documentation updates based on Government feedback. The first Option Period should begin at month 10 and begin ISM development.

Q4: For Topic CBI-03, it is assumed that access to the HPAC software will be provided to the awardee. Are there any restrictions (i.e. facility/personnel clearance, usage etc.) with regards to HPAC access or usage?

A4: HPAC is considered For Official Use Only (FOUO) and successful offerors would have to treat the software as such. The output can range anywhere from Unclassified to Sensitive Compartmented Information (SCI), depending on the data that is used for its calculations. Access to HPAC source code and executables will be provided to successful offerors post award.

Q5: For Topic CBI-03, it states that the “Software must comply with DoD standards for authorization to operate”. Please clarify what is intended by this statement. Does this mean that the software must have Unlimited Rights, Government Rights, or that other rights categories are acceptable so long as there is no restriction on software operation by DoD?

A5: Authorized To Operate (ATO) means the software must meet RMF/Security Standards in order to gain an ATO from an approving official to go onto DoD networks. The ATO process will be discussed with successful offerors post award.

Q6: For Topic CBI-03, it states that the “Software must be tested, verified, and maintained.” Please clarify what is intended by this statement with regards to maintenance? For example, does DTRA anticipate follow-on maintenance/support contracts, or that the contractor maintains the software some other way?

A6: There are three separate requirements in the statement, "Software must be tested, verified, and maintained." Tested:

Software must undergo unit testing and integration testing while in Development. Verified: Software, upon delivery to CBI, must be Validated & Verified by end-users. Maintained: Once the software is transitioned & deployed, it is anticipated there will be follow-on contract(s) for Operation & Maintenance (O&M). Specific protocols will be discussed with successful offerors post award.

HDTRA1-20-S-0001 BAA Q&A