DSO Sustainment Support and Integration _RFI 25-4012.pdf

REQUEST FOR INFORMATION (RFI 25-4012)

Information Technology Services to obtain Document Services Online (DSO) Sustainment and Integration Support

This Request for Information (RFI) is issued in support of ongoing acquisition planning 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 Small Business Communities to provide the required capabilities.

The Government does not intend to award a contract based on this RFI or reimburse any costs associated with the preparation of responses to this RFI

Description: The DLA Information Operations, Enterprise Capabilities, Document and Automation Management J62KA is seeking information from interested contractors on accomplishing the requirements outlined in the DRAFT Document Services Online (DSO) Sustainment and Integration Support Performance Work Statement (PWS). The period of performance is for one base and two 12-month option periods to begin from time of award.

Responses Instructions

RFI responses must conform to the following format and space limitations:

• Word or .pdf document with font no smaller than 10 pt. font, however text included in graphics, tables, and figures can be no smaller than 9 point.

• Responses to this RFI must total no more than 6 pages. The cover page and cover letter are not included in the total page count.

• Additional information in excess of this limit will not be considered

• Responses to this RFI must be submitted via email to Kevin.Buckman@dla.mil no later than July 31, 2025, 1:00PM ET.

RFI responses must contain the following:

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

o Company name o Company business size with socioeconomic classification based on North American

Industry Classification Code.

o Company point of contact and contact information (name, address, phone number, email address, and fax number) o Date submitted o If using subcontractors, all company information should be presented (name, size, etc.)

mailto:Kevin.Buckman@dla.mil

• Section 2 – Market Research and Responses to Questions The purpose of this section is to obtain information that will assist in deciding on whether any IT services company in the market are able to satisfy the requirements and objectives.

1. Project Plan Development - Section 2.3.1 The Contractor shall develop a project plan to accomplish the requirements of this PWS to include the planning, direction, coordination, and control for effective and efficient accomplishment of all requirements contained in this PWS. The project plan must include a description of how the DSO application with existing capabilities will be used to meet the requirements in the PWS. Access to the MDSF source code will be required for development and maintenance of the DSO Plug-Ins, therefore contractor must provide proof of authorized access of the MDSF code. Project Plan must be delivered within two weeks from award.

2. Maintain & Update Existing DSO Plug-Ins & Extensions -Section 2.3.2 The contractor shall provide a presentation and documentation on the how the requirements will be met through code changes, test the code changes, and provide a version release.

Any changes made will become part of the baseline code.

Integration code is tied to the MDSF software product. To make enhancements such as DSO Plug-Ins, it will require access to the source code from the Print ePS Software (ePS), the OEM of the MDSF product. The contractor must supply proof to the government that they have the rights to modify change the source code of MDSF via a letter from Print ePS Software (ePS).

3. Coordinate, Sustain & Administer the overall DSO Platform -Section 2.3.3 The contractor shall provide a presentation and documentation on the how the requirements will be met through code changes, test the code changes, and provide a version release.

Any changes made will become part of the baseline code.

Integration code is tied to the MDSF software product. To make enhancements such as DSO Plug-Ins, it will require access to the source code from the Print ePS Software (ePS), the OEM of the MDSF product. The contractor must supply proof to the government that they have the rights to modify change the source code of MDSF via a letter from Print ePS Software (ePS).

4. Specify, Develop, Test, Deploy & Support New MINOR DSO Plug-Ins & Extensions

- Section 2.3.4 As DLA Document Services continues to evolve from a print-centric to a digital-centric communication organization, the DSO platform is being asked to evolve with it. This requires analysis of each evolutionary step to determine how the DSO Platform needs to adapt.

The DSO platform is made up of multiple components from both the COTS product company ePS and government contractor funded Plugins & Extensions. When a challenge is presented the strategy for solutioning requires a multifaceted approach. The government needs to offer solutions that could involve one or many solution types.

5. Monthly 8570 Report - Section 2.3.5 The contractor shall provide a monthly 8570 deliverable report to the COR that includes a list of applicable 8570 key personnel. The following information shall be provided in the report, due by the 10th calendar day of each month.

6. Specify, Develop, Test, Deploy & Support New MAJOR DSO Plug-Ins & Extensions -

Section 2.3.6 A major DSO Plug-In & Extension is a solution that takes more than six (6) months of overall effort. These solutions are complex, multi-faceted, and typically require collaboration between many stakeholders to both define and deploy.

The major DSO Plug-In & Extensions will follow the same process as the minor Plug-Ins & Extensions with a significant increase in scope and calendar time. See TASK for reference.

An example of this is the upcoming (2025-26) new ICAM project which will alter how all users authenticate and receive permissions on the platform.

Another example is major changes to the Billing Module Plug-In that were made in 2023. As the DSO Plug-Ins & Extensions age, major changes will be required to mitigate technical debt, improve security stature, and update to match the overall infrastructure of DLA.

7. Documentation & Training - Section 2.3.7 The DSO platform had been managed by the same PM since the COTS product was purchased in 2010. In December 2025, that PM retired and another core resource with decades of experience retired as well. The government seeks to invest in a documentation effort with a contractor who has tacit knowledge and context over the total solution. This will put the government in a position to be self-sufficient in the understanding and support of this critical platform, no matter what the tenure of the PM or other key resources.

8. Capability:

1. List your past performance with U.S. government contracts/projects that required migration of one application into another application. Include size, scope, and schedule.

2. PWS requires the need for permission from EFI to have access to the EFI DSF code.

Outline how your company would obtain this permission, and/or if they have obtained permission from similar software manufacturers in the past list the software vendors you have obtain code level permission.

Primary Point of Contact Kevin Buckman Kevin.Buckman@dla.mil

(445) 737-3968

Contracting Office Address DLA Contracting Support Office (DCSO-F) 8725 John J. Kingman Road Fort Belvoir, VA 22060 United States