Amendment 0001 to answer questions.docx

Amendment 0001 to Answer Questions:

Question 1: Integration with Existing Army Systems – Will the new inventory management software be required to integrate with any legacy Army logistics, supply chain, or ERP platforms (e.g., GCSS-Army, DPAS, LMP)? If so, will the Army provide APIs, middleware, or other integration support?

Answer 1: No requirements to integrate with any existing systems.

Question 2: Customization & AI-Driven Automation – The SSN specifies customizable workflows and user-defined nomenclature. To what extent does the Army expect AI-driven automation, predictive analytics, or machine learning capabilities for demand forecasting and inventory optimization?

Answer 2: While AI considerations are a nice to have, they are not specified in the requirements document.

Question 3: Cybersecurity & DISA Compliance Requirements – Beyond the DISA STIG requirements, are there any specific RMF (Risk Management Framework) compliance milestones that the selected vendor must meet? Will the government provide ATO (Authority to Operate) support, or is the contractor responsible for obtaining all cybersecurity approvals?

Answer 3: The implementation will be solely under our local ATO for the network and will be required to abide by all DISA STIG requirements and be supported by the vendor to provide necessary security patches when identified by the company or through the DoD IAVA program.

Question 4: Incumbent System & Transition Strategy – Can you confirm if there is an incumbent software provider currently supporting inventory management? If so, are there performance gaps or transition concerns that should be addressed in the new solution?

Answer 4: Data from incumbent software provider will be pulled as a .csv and uploaded into the new software as a .csv.

Question 5: Deployment Model & Data Hosting – Will the Army accept a commercial cloud-hosted solution (AWS GovCloud, Azure Government, etc.), or is the requirement strictly for on-premises hosting within Army data centers Answer 5: The only way we will allow the use of a commercially cloud-hosted solution is if the solution has FedRAMP approval and an Army Provisional Authorization to Operation (P-ATO). The Army is trying to get things hosted on C-ARMY rather than commercially hosted, so the restrictions are tight in order to gain commercial cloud approval which the commercial company would be responsible for obtaining. We recommend an on-premises solution if the system requirements are something we are running and can support with current staffing.