RFI Information 81225.pdf

PDF 167 KB Posted

Attached to
Request for Information (RFI) - HMMS Software and Sustainment Support (revised)
Solicitation number
20250812
Issued by

About this file

This Request for Information (RFI) seeks market research for a Hazardous Material Management System (HMMS) Software and Sustainment Support contract. The government is exploring potential solutions from large and small businesses to develop a comprehensive system for tracking, managing, and reporting hazardous materials across industrial sites. Key requirements include capabilities for authorized use tracking, Safety Data Sheet (SDS) management, artificial intelligence integration, data exchange methodologies, hazardous waste disposition, and compliance with regulations like the Resource Conservation and Recovery Act (RCRA).

Respondents must submit a 30-page detailed response by August 27, 2025, at 12:00 PM EDT to Nyeshia.McAllister@dla.mil, addressing specific functional, technical, and implementation questions. The RFI covers areas such as software licensing, disaster recovery, user support, knowledge management, implementation risks, and vendor viability. The government is not obligated to award a contract based on this RFI and will not reimburse response preparation costs. The primary federal agency involved is the Defense Logistics Agency (DLA), with potential integration points including the Defense Health Agency (DHA) and Defense Occupational Environmental Health Readiness System (DOEHRS).

View the file

Other files

File Type Posted
RFI PWS 81225.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Request for Information (RFI) for

Hazardous Material Management System (HMMS) Software and Sustainment Support

This Request for Information (RFI) is issued to support ongoing Acquisition Planning and capability requirements development. This RFI is issued solely for information and planning purposes and does not constitute a solicitation. All information received in response to this RFI marked Proprietary will be handled accordingly.

Responses to the RFI will not be returned. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. A response to this RFI is necessary to assist the Government in determining the potential levels of interest, adequate competition, market maturity and technical capabilities within the Large and Small Business Communities to provide the required capabilities.

The Government does not intend to award a contract on the basis of this RFI or reimburse any costs associated with the preparation of responses to this RFI. It will also not consider any solutions that are proprietary.

Description: See Draft PWS

Response Instructions

RFI responses must conform to the format below and provide the following information.

• Section 1 - Cover Letter. The cover letter must include the following information:

• Company name

• Company business size with socioeconomic classification based on North American Industry Classification Code.

• Company point of contact and contact information (name, address, phone number, email address, and fax number)

• Date submitted.

If more than one solution is proposed from a team of providers, all company information should be presented (name, size, etc.).

• Section 2 - Market Research Questions. The purpose of this section is to obtain information that will assist in making a decision on whether any additional information needs to be included in the PWS.

1. Review the Draft PWS and provide comments on the following areas:

a. Assumptions related to the PWS

b. Comments/Questions related to the PWS

c. Risks or concerns of bidding and executing the requirements as specified

2. Provide a list of technical documents/Government Furnished Information (GFI) that would be needed to propose against this Draft PWS.

3. Provide documentation/presentation on whether or not the company can support and deliver all of the governments HMMS and Project Support requirements through the IDIQ.

• Detail how your company would support project initiatives such as:

Development Security Operations (DSO), Application Programming Interface (API) connections, and Hazardous Waste Turn-In DoD Logistics Management Standard (DLMS) transactions for the HMMS systems

• Deliver on Artificial Intelligent (AI) capabilities via automated testing tools and software development

• Explain how your current support can continue working on future connections with Defense Health Agency (DHA) Defense Occupational environmental Health Readiness System (DOEHRS)

• Disaster Recovery. What is your plan to support the HMMS Disaster Recovery protocols?

• Share your customer support procedures in managing hazmat waste.

• Information Security Requirements. Federal IT implementations entail significant security requirements and compliance with National Institute of Standards and Technology (NIST) mandates. Explain how you will support HMMS using the DOD Risk Management Framework (RMF).

4. The Government may require each submitting company to provide an in person presentation/demonstrations on possible solutions.

Answer the following questions as part of the RFI:

Functional:

5. How do you track, manage and report Authorized Use at the employee level for an industrial site?

6. Provide your workflow and steps

7. What current methodology is used to validate, cross-reference and serialize HAZCOM information and Global Harmonization System information against National and Local Stock numbers?

8. Is this serialization connected at the NSN Level?

9. How do you use artificial intelligence to read, index and load SDS into your system?

10. What data exchange methodology is used to bi-directionally exchange data with the service users of the hazardous material systems users?

11. Explain how your current capabilities provide hazardous waste and special services through manifest and final disposition, meeting and/or exceeding the Resource Conservation and Recovery Act (RCRA) along with US and International modes of transportation.

12. How do you manage ICOFR requirements?

13. What OKTA version is used for user access?

14. Explain your current methodology for receiving contract and HAZCOM information electronically and committing it to the system of record.

15. What business intelligence tool is used to write ad-hoc and provide canned reports for the user base.

16. Explain the current methodology for decanting, pharmacy and locker tracking and reporting.

17. Define your current plan for SDS QR capabilities in the system?

Additional Questions:

18. What solution or solutions can your company provide to satisfy the objectives, system capabilities and requirements? Include the name of your product(s) and your three largest commercial or DoD Clients.

19. Do you have business case/return on investment/white papers regarding benefits and costs of implementing your product? If so, provide a reference summary within your response and provide the investment/white papers as a separate submission in support of the reference summary (not included in page count).

20. Does your product have the ability, out of the box, to perform all of the capabilities? If not, what is the level of effort (and approximate cost) associated with adding the capability? How is custom development done within the confines of the product?

21. Does your company offer software as a service? If so, how is the service structured/offered? Do you have other organizations using your product under a software as a service agreement? Do you have clients that can speak to this?

22. Does your company currently offer to host this product in a cloud environment? Do you have other customers currently subscribing to this hosting service/product?

Technology Platform

23. Application Type. On what type of technology is your solution based?

24. Future Technology. What are your technology plans for the proposed solution? Describe how you keep your product up-to-date with improvements in information technology. What is the schedule for future patches and upgrades?

What is your software life cycle as it pertains to customer software upgrades?

How long do patches and upgrades take on average? What software engineering methods are available and how can they lend to more timely delivery of enhancements?

25. Information Security Requirements. Federal IT implementations entail significant security requirements and compliance with National Institute of Standards and Technology (NIST) mandates. Has your software been certified and accredited by a federal agency using either NIST or the DOD Risk Management Framework (RMF)? If not, how do you plan to satisfy those requirements?

26. Section 508 of the United States Workforce Rehabilitation Act. Is the solution Section 508 compliant?

27. Prices. What is the Rough Order of Magnitude (ROM) price for the software, licensing fees, maintenance fees, and system integration services for the proposed solution? Provide a separate price for each proposed element and include any pricing assumptions in your response. Please contact the contracting office if you need further clarification. Clarifications will be published in FedBizOpps. Please respond on a pricing spreadsheet.

28. Licenses. What is your licensing schema?

29. Disaster Recovery. What is your disaster recovery plan?

30. User Support. Is there a ticketing system inherent in your tool (s)?

31. Knowledge Management. How do your clients use your knowledge library? Do you have a list of clients that can speak to this?

Implementation and Risk (Answer in an essay format)

32. Implementation Sequencing and Durations. Given your understanding of our requirements and environment, what is your typical implementation model? What is the estimated timeline from project initiation to full deployment? Please provide key milestones and the time it will take for each milestone within the timeline.

33. Risk. What are the five major risks associated with using your proposed solution to meet the requirements?

Vendor and Product Viability (Answer in an essay format)

34. General Services Administration (GSA) Schedules and Other Contract Vehicles. What GSA Multiple Award Schedule contracts, Government-wide Acquisition Contracts, Multi-Agency Contracts, or other contract vehicles does your company have to support the purchase of the proposed solution?

35. Enterprise Vendor Viability. As the vendor of the solution, provide an assessment of the strength of your customer base, and your presence in the market.

36. Vendor Support Services. What is the extent of support services for the solution proposed, including technical support, training, and consulting operations?

37. Product Maturity. What is the software lifecycle phase of the proposed solution?

Submission Instructions

Responses to this RFI must total no more than 30 pages, with text no smaller than 10 point;

however, text included in graphics, tables, and figures can be no smaller than 9 point. The cover page and cover letter are not included in the total page count. Any material submitted in excess of the 30-page limit and the page limitation exclusions will not be considered. The submissions must be in sufficient detail and clarity to provide the information needed to assess your company’s ability to provide a solution.

Email your company capabilities in response to this RFI to Nyeshia.McAllister@dla.mil RFI response must be submitted no later than August 27, 2025, 12:00 PM EDT.

Primary Point of Contact

Nyeshia McAllister Nyeshia.McAllister@dla.mil Phone: 215-737-3233

Response Instructions

File details come from the government source that posted it. Updated .