Amendment 0001 to answer questions.docx

Amendment 0001 to Answer Questions March 7. 2025:

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.

Amendment to Answer Questions March 11. 2025 Question 6: Are you looking for an off-The-Shelf solution or a custom software solution?

Answer 6: Either would work as long as they meet the Government’s requirements.

Amendment to Answer Question March 17, 2024 Question 7: Is this an opportunity to take an entirely fresh look at warehouse control and inventory management from procurement to distribution all the way back to audit and accounting?

Answer 7: The system we intend to implement needs to be standalone and does not communicate or integrate with any other government inventory systems.

Amendment to Answer Question March 31, 2024 Question 8: Are you currently using an SAP system today for Inventory Management?

Answer 8: We are not currently using an SAP system.

Amendment to Answer Question March 31, 2024 Answers from SME in Red DEVCOM Soldier Center:

0. Is the scope restricted to this center, or will it be expanded to other Centers/Sites? Scope restricted to this center.

0. Does this Center include multiple physical warehouses or just a single warehouse? 3 storage areas/warehouses

1. number of materials/SKUs? Approximately 30 skus

1. number of locations/warehouses? See above

1. number of end-users? 10 would be the max at this time.

1. Beyond WMS:

1. Is the legacy WMS instance incapable of managing inventory, being deprecated, or no longer supported by the OEM? No longer supported

1. Is the entire legacy WMS being replaced, or is the Army just looking to integrate a new inventory management capability? Requirement is localized to a single isolated team

1. Besides the Product Platform and Implementation scope, including Base Configuration and Workflows, Warehouse Structure Management, etc., is the Army looking for this “beyond WMS” capability to also manage any of the following: none of the below are needed at this time.

2. Labor Management

2. Yard Management

2. Slotting and Rearrangement

2. Wave Management

2. Material Flow Systems

2. Cross Docking

2. Quality Management

2. Transportation Management

1. Timing: Where did the ’15-week deliverable’ timeline originate? Self designated timeline

1. Deliverables:

3. Does the Army have a notional Schedule or POAM by which each phase (from System Configuration, Dev, Integration, Test, Data Migration, Cut-over, etc.) must be completed to hit the 15-week deliverable timeline? Not beyond what is already listed

Amendment to Answer Questions April 8, 2024

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.

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: Naming the incumbent software provider is not necessary. Data from that software will be pulled as a .csv and uploaded into the new software as a .csv.

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.

6. Are there additional security requirements beyond DISA STIG compliance that need to be considered?

Answer 6: STIGS, IAVAs (i.e. security patching), and supported by the vendor. The answer to #5 should also be considered because if we have an on-premise solution, it must be with applications that we have the staff expertise to support. For instance we utilize SQL Database. If there are alternate database technologies we don’t currently have supported by our administrators being required by the vendor, we may not be able to properly stand it up and support it locally.