FedOpsFedOps
Description
***AMENDMENT 2*** Amendment 2 is provided for transparency for questions and answers received since the posting of the RFS. Please pay particular attention to the graphics font and submission instructions. Q: Would you prefer those as separate attachments, a combined .zip file or files embedded within the searchable .pdf itself? Will you be providing a DoD SAFE link or prefer another method for submitting this data? Additionally, could you please provide a clarification on the proposal instructions regarding font size? We obviously intend to comply with the 12-pt Times New Roman font requirement for the technical narrative, but can you confirm whether that font requirement also applies to tables and graphics? We have some tables and figures that have slightly smaller (size 10pt font) text, but we would like to ensure legibility and compliance. A: All components of the Solutions Brief, including the Technical Narrative and all attachments (e.g., Technical Data Sheet, Data Rights Assertions, ROM, etc.), shall be combined and submitted as a single, searchable .pdf file. Do not submit a .zip file or multiple separate attachments. The 12-point Times New Roman font and 1-inch margin requirements apply to the main narrative text of the Solutions Brief. Text within tables, figures, charts, and graphics may be no smaller than 10-point Times New Roman font to ensure legibility. Submissions shall be made via DoD SAFE. To ensure timely submission, interested Performers must request a DoD SAFE drop-off link from the Tiffanie.l.neal.civ@army.mil and Anthony.m.ambrosio.civ@army.mil no later than 1700 CDT 20 May 2026, 48 hours prior to the submission deadline, to allow time for submissions . The Government will then provide a secure link for the performer to upload their submission. It is the Performer's responsibility to ensure their submission is completely uploaded to DoD SAFE prior to the submission deadline stated in the RFS. Q: In the RFS, it mentions that the prototype project security level is up to secret (paragraph 1). Then, in paragraph two under operational constraints, you mention that the Solution must be physically handled as unclassified. Can you explain the differences here? A: The distinction in the RFS lies between the classification of the data and active operational environment (the Project) versus the classification of the physical hardware (the Solution) when it is powered down or in transit. Prototype Project Security Level (Up to Secret) The "Up to Secret" classification applies to the mission context and the data the system will process. During active operations, the prototype will process, transmit, or store Secret-level information. Therefore, personnel supporting the active mission environment or discussing the full operational scope of the project will operate under Secret-level security protocols. Operational Constraints: Physical Handling (Unclassified) The requirement for the Solution to be physically handled as unclassified dict…
Classification
Place of Performance
Contracting Office
Contacts
Attachments (5)