DMSI Architecture_RFI_Contract_2025-FINAL-Released-14APR25.pdf

SOURCES SOUGHT SYNOPSIS / REQUEST FOR INFORMATION

NEW CONTRACT for SUSTAINMENT, SURVEILANCE AND

DEVELOPMENT

SUPPORT FOR AN ARCHITECTURE TOOL FOR THE DEPOT

MAINTANENCE SYSTEM INTEGRATION (DMSI) SYSTEMS

Air Force Life Cycle Management Center (AFLCMC/GBM)

14 April 2025

THIS IS A REQUEST FOR INFORMATION ONLY

1.0 SYNOPSIS

This Request for Information (RFI) is issued solely for market research purposes. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. The United States Department of the Air Force (DAF) is not seeking proposals, nor will it accept unsolicited proposals at this time.

This RFI is for planning purposes only and shall not be considered as an invitation for bid, request for quotation, request for proposal, or as an obligation on the part of the Government to acquire any products or services. Any response to this RFI will be treated as information only. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this announcement or the Government use of such information. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated, or received for this effort. The information provided may be used by the Air Force in developing its acquisition strategy and statement of work/statement of objectives and performance specifications.

Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. The Government does not intend to award a contract based on this RFI or otherwise pay for the information submitted in response to this RFI.

The purpose of this market research is to determine if any contractor has the capability to provide the architecture tool and the sustainment/surveillance/development support of that tool for the Depot Maintenance System Integration (DMSI) Systems. These systems include Programmed Depot Maintenance Scheduling System (PDMSS), AFMC Labor Standards Data System (ALSDS), Job Order Production Master System (JOPMS), Depot Maintenance Materiel Support System (DMMSS), Exchangeables Production System (EPS), and Inventory Tracking System (ITS).

The Government is seeking responses from vendors registered under North American

Industry Classification System (NAICS) 541511 – Custom Computer Programming Services only.

2.0 BACKGROUND AND DESCRIPTION

The Depot Maintenance Systems Integration (DMSI) program currently utilizes a common architecture, framework, and security tables tool for its suite of systems. DMSI consists of six systems supported by a centralized data base, the Depot Maintenance Consolidated Operational Database (DMCODB), which provides all operational data used by these components: AFMC Labor Standards Data System (ALSDS), Depot Maintenance Material Support System (DMMSS), Exchangeables Production System (EPS), Inventory Tracking System (ITS), Job Order Production Master System (JOPMS) and, Programmed Depot Maintenance Scheduling System (PDMSS)

The current architecture tool provides a client and web option. The status of each system is provided below.

AFMC Labor Standards Data System (ALSDS)- Converting from a client framework to a PHP web framework.

Depot Maintenance Material Support System (DMMSS)- Converting from a client framework to a PHP web framework.

Exchangeables Production System (EPS)- Converting from a client framework to a PHP web framework.

Inventory Tracking System (ITS)- Converting from a client framework to a PHP web framework.

Job Order Production Master System (JOPMS)- Converting from a client framework to a PHP web framework.

Programmed Depot Maintenance Scheduling System (PDMSS)- Currently utilizes a java framework but uses the common Security module.

The solution system needs to provide a common architecture, framework, and security protocols for the DMSI components as well as the following application services: User Administration Module, Application Level/role-based Security, Error Handling, Transaction Management, Common GUI Look & Feel, Object/Component Management, Application Scenarios, Application Partitioning, Broadcast Messaging, Report Engine, and Audit Logging.

3.0 SCOPE/REQUIREMENTS/CAPABILITIES

The Depot Maintenance Systems Integration (DMSI) Program Management Office, Air Force Life Cycle Management Center (AFLCMC/GBM), located at Wright-Patterson AFB, is conducting market research to identify qualified businesses to provide an architecture and framework solution as well as framework conversion and sustainment support within the DMSI environment allowing DMSI to maintain standard, structured, and scalable enterprise level applications. Additionally, the solution must provide security framework providing security tables and procedures that support all of the DMSI applications and administration for granting application-level menu access to authorized users.

Parties interested in responding to this Request for Information must provide the following information and/or documentation that demonstrate technical capability in developing, modifying and sustaining a new framework solution, or demonstrate the capability in modifying and sustaining the current framework solution.

1. (CRITICAL) Do you currently have the capability to modify and maintain Spectrum

System Development Architecture (SSDA)™ source code? Please answer with either “Yes” or “No”.

1a. If the answer to Question 1 above is “No”, do you have any agreements in-place that would allow you to modify and maintain Spectrum System Development Architecture (SSDA)™ source code by 1 Jan 2027? Please answer with either “Yes” or “No”.

2. (CRITICAL) What is the estimated cost to the Government for the license for the capabilities described above? Is this a new architecture/framework or would we utilize the current architecture/framework?

3. (CRITICAL) What is the estimated cost to the Government for the conversion support to the new architecture solution?

4. (CRITICAL) What is the estimated level of effort to convert to a new architecture?

What is the estimated level of effort to continue on existing architecture?

5. (CRITICAL) Describe in detail, your experience in performing the modifications or maintenance needed for a new/ or current architecture/framework that considers impacts to the using systems.

6. Experience during the past five years performing software maintenance on applications which operate within the AF or DoD computing environment using the software specified below (specify experience with each product):

DoD Software Products and Technical Architecture/Guidance

Java Runtime Environment (JRE/JDK) Sourcetree

Java Archive (JAR) File RHEL 9

JavaBeans Chrome

Web Application Archive (WAR) Windows 11

EXtensible HyperText Markup Language

(XHTML)

Windows Server

Java Database Connectivity (JDBC) Microsoft 365

Appeon PowerBuilder 2022 R3 Project 2019

JBoss EAP 7.1.x, 7.4.x, and 8.x XML

Apache NetBeans Checkmarx

Visual Studio Code (VS Code) SonarQube

GitHub Copilot extension in VS Code PHP

GitHub HTTP/HTTPS

GitHub Desktop NIPRGPT & ChatGPT

Selenium IDE Apache Shiro

Selenium WebDriver PrimeFaces

Jenkins DrExplain

Docker Jasper Reports

Dependency-Track VMWare Worstation Pro

Desktop/Server Virtualization Chilcat Software

ISMT

Oracle Products

DBMS

Client Instant Client Database Design VirtualBox Wallet SQL Developer SQL Plus SQL Scripts (PL/SQL)

BES Atlassian Tools Jira Confluence Zephyr Scale Bitbucket

7. (CRITICAL) What is your experience working with Air Force systems and DOD requirements?

8. (CRITICAL) Does your architecture tool support PHP and JAVA applications?

9. (CRITICAL) Does your personnel have at least three years of recent experience of software maintenance/sustainment/development of a software framework and architecture tool?

10. (CRITICAL) Are your personnel classified as a Senior Developers have or will meet DoD Cybersecurity Workforce Framework work role Advanced Software Developer (as identified in DoDD 8140.01) prior to 01 Feb 2025?

4.0 PLACE OF PERFORMANCE

Work is to be performed primarily at Contractor managed facilities and/or an approved DAF location. Work performed at any alternate location shall be subject to the availability of appropriate equipment required to meet the terms and conditions of the program. The Contractor may permit employees to work at an alternate duty location provided prior Government notification is coordinated and the terms of the contract and PWS continue to be met.

5.0 CLEARANCES

Contractor personnel shall be required to have the appropriate level of investigation and/or security clearance for the site at which they are located during the performance of duties in support of this order. At a minimum, all Contractor personnel are to have a completed favorable National Agency Check Inquiry (NACI)/Entrance National Agency Check. Contractor personnel shall be required to submit a request for a user ID when access is required to a Government computer, to include the submission of proof to the PMO Security Manager that a favorable National Agency Security Check has been completed. The contractor shall be required to obtain a CAC before start of work. The Contractor personnel shall be required to obtain Common Access Cards (CAC) for the purpose of encryption and physical and digital identification for access to systems. The Contractor shall not involve any foreign national (resident aliens exempt) in work performed under this requirement.

6.0 ORGANIZATIONAL CONFLICT OF INTEREST

Organizational Conflict of Interest (OCI) as defined and discussed in FAR 9.5, Organizational and Consultant Conflicts of Interest, is a concern in all acquisitions across the Department of Defense. Early involvement with our industry partners is a key element of the OCI process, and it is critical for the Government to be able to identify any potential OCI issues as early as possible for an acquisition. This would allow ample time to address and evaluate any potential OCI issues, if required, prior to contract award with minimal impact to critical acquisition schedules.

Interested vendors are requested to evaluate your potential OCI issues with regard to this requirement for services for all systems identified, and the Contractor is encouraged to identify any OCI issues, as stated in FAR 9.5 to the Contracting Officer (CO). This will assist the CO in determining if the contractor will need to submit an OCI Mitigation Plan for any solicitation that might result from this notice.

7.0 INFORMATION REQUESTED

Interested parties should submit a capability package, with a cover letter, that is brief and concise, yet clearly demonstrates ability to meet the stated requirements with sufficiently qualified personnel. Provide qualification information (type and duration of employee experience relevant to the requirements) and the level of involvement (prime or subcontractor) and the time periods for work on similar projects. The capabilities package should clearly present evidence that the interested party is fully capable of providing the required services and as such may contain any information that the interested party feels is relevant. Provide a list of Government and/or commercial contracts with the following information:

a. Contract number and description of services

b. Contracting officers’ name, address, and telephone number

c. Program managers’, project leads’, and/or technical leads’ name, address, telephone number, and a list of tasks performed for these personnel.

8.0 INSTRUCTIONS FOR RESPONSE:

Send responses electronically to Contract Specialist, Eric Lagasse; email:

eric.lagasse@us.af.mil; Commercial Phone: (937) 257- 6822, and Heather Garay;

email: heather.garay.1@us.af.mil, and the Contracting Officer, Antonio J. Ayubi; e-mail:

antonio.ayubi@us.af.mil; Commercial Phone: (937) 904-2126.

As this is an RFI document, initial prospective business responses should be in the form of a Capability Statement. The Government recognizes that proprietary data may be submitted as part of this effort. If so, clearly mark restricted or proprietary data. The Capability Statement should include the following elements:

Submit an 8-page (maximum) paper not including cover page, describing the items listed above. The responses should be formatted as follows:

Page size shall be 8.5 x 11 inches; foldouts are permitted but will be assessed towards total page count.

Pages shall be single-spaced. The font shall be Arial and the font size shall be no less than twelve (12) point. Use at least a 1-inch margin on the top and bottom and ¾ inch side margins.

Capability statements need to address fully the critical areas identified above.

Responses shall also include information regarding the following:

1) The level of contractor’s interest (likelihood of submitting a proposal as a prime contractor).

2) Address potential teaming arrangements if likely to submit a proposal.

3) If a teaming arrangement is considered, describe tasks the prime would perform versus tasks the subcontractor would perform.

4) Prospective Business Identification

a. Company Name and Cage Code

b. Address

c. Phone Number

d. Fax Number

e. E-mail

f. Point of Contact Information

g. A website address that provides additional information about the prospective business

h. The highest security clearance that your company currently holds.

i. Verify your business status as a Service-Disabled Veteran-Owned

Business.

5) Identify company Cage Code, DUNS Number, size/socio-economic status (large, small, 8(a), etc.) and provide any other information that the Air Force should consider in reviewing the response.

Due Date: Responses are due no later than 5:00 PM EST on 21 April 2024, and shall be electronically sent to eric.lagasse@us.af.mil and antonio.ayubi@us.af.mil.

Late responses will not be reviewed. Respondents who submit proprietary data shall clearly mark the data with appropriate markings. Any questions should be directed to the Contracting Officer or to the Contract Specialist. The Government does not intend to award a contract based on this Sources Sought. A determination not to compete this action based on responses received is solely within the discretion of the Government. Responses to the RFI will not be returned.

Please note that all prospective contractors must be registered in the System for Award Management (SAM) database, formerly the Central Contractor Registration (CCR), to be awarded a Department of Defense contract. To learn more about this SAM requirement and how to register, please visit the SAM internet website at http://www.sam.gov/ or call 1-866-606-8220.

In accordance with DAFFARS 5301.91, an Ombudsman has been appointed for this acquisition. The Ombudsman does not diminish the authority of the Program Director or Contracting Officer, but communicates contractor concerns, issues, disagreements, and recommendations to the appropriate Government official. When requested, the Ombudsman shall maintain strict confidentiality as to the source of the concern. The Ombudsman does not participate in the evaluation of proposals or in the source selection process. The Ombudsman should be contacted only with issues or problems that have been brought previously to the attention of the Program Manager and/or Contracting Officer and could not be resolved satisfactorily at that level, concerned parties may contact the following individual: Col. Todd Dye:

Deputy Director, Acquisition Excellence & Program Execution Directorate

(AFLCMC/AQ-AZ)

Bldg. 572, 1865 Fourth Street, Room 240 Wright-Patterson AFB, OH 45433-7630 937-255-7777