Sources Sought Notice.pdf

Page 1 of 5 Pages

SOURCES SOUGHT NOTICE

Tracking Number: 622469280

The Defense Information Systems Agency (DISA) Services Development Executive Office (SD) Command and Control (C2) Portfolio Management Office (SD4) is seeking sources for the Joint Capabilities Requirements Manager (JCRM) software sustainment and maintenance.

CONTRACTING OFFICE ADDRESS:

Defense Information Technology Contracting Organization (DITCO) National Capital Region

(NCR)

P.O. Box 549 Fort Meade, Maryland 20755-0549

INTRODUCTION:

This is a SOURCES SOUGHT NOTICE to determine the availability and technical capability of large businesses and small businesses (including the following subsets: Small Disadvantaged Businesses, certified 8(a), Service-Disabled Veteran-Owned Small Businesses, HUBZone Small Businesses and Woman-Owned Small Businesses) to provide the required products and/or services.

The DISA Joint Planning and Execution Services (JPES) Program Management Office (PMO) is seeking information from potential sources for: sustaining the operational legacy system that supports the Joint Operation Planning Process (JOPP) and Global Force Management (GFM) Process until the system is modernized and the legacy system can be sunset. The operational legacy system is the Joint Capabilities Requirements Manager (JCRM). JCRM is a tool that takes operational plans inputted into the Joint Operations Planning and Execution System (JOPES) and creates orders for those plans, which in turn are sent to the Department of Defense (DoD) secretary for authorization. JCRM will be modernized into JPES. However, the JCRM transition date is currently not known but is estimated to take place during calendar year 2030.

Historically, JOPES and JCRM Sustainment and Maintenance have been issued under one contract/task order, however, it is the Government’s intent that by 1st Quarter Calendar Year 2025, JOPES will sunset and transition to JPES. As a result, it is anticipated that JOPES support will no longer be needed, however, JCRM sustainment and maintenance will be required until JCRM is modernized and transitioned to JPES. The scope of this effort includes project management as well as support and maintenance for JCRM only.

The anticipated Period of Performance is March 2025 through March 2030.

The anticipated Place of Performance: Unclassified work could primarily be conducted at the contractor’s facility. Classified work which includes Cybersecurity and Information Assurance support would primarily be completed on-site at DISA Headquarters – 6910 Cooper Ave. Ft Meade, MD 20755.

Page 2 of 5 Pages

DISCLAIMER:

THIS SOURCES SOUGHT NOTICE IS FOR INFORMATIONAL PURPOSES ONLY. THIS

IS NOT A REQUEST FOR PROPOSAL. IT DOES NOT CONSTITUTE A SOLICITATION

AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT.

RESPONSES IN ANY FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER

NO OBLIGATION TO AWARD A CONTRACT AS A RESULT OF THIS NOTICE. NO

FUNDS ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO THIS

NOTICE. ANY INFORMATION SUBMITTED BY RESPONDENTS IS STRICTLY

VOLUNTARY.

CONTRACT/PROGRAM BACKGROUND:

Contract Number: 47QTCA18D001Q / HC1047-22-F-0018 Contract Vehicle: GSA MAS Incumbent and their size: InterImage, Inc. – Woman Owned Small Business (WOSB) Method of previous acquisition: Sole Source Period of performance:

Base Period: March 7, 2022, through March 6, 2023 Option Period 1: March 7, 2023, through September 6, 2023 Option Period 2: September 7, 2023, through March 6, 2024 Optional 6-Month Extension in accordance with (IAW) Federal Acquisition Regulation (FAR) 52.217-8: March 7, 2024, through September 6, 2024 (Not exercised)

Contract Number: 47QTCA18D001Q / HC1047-24-F-4001 Contract Vehicle: GSA MAS Incumbent and their size: InterImage, Inc. - WOSB Method of previous acquisition: Sole Source Period of performance:

Base period: March 7, 2024, through December 6, 2024 Option Period 1: December 7, 2024, through March 6, 2025 Option Period 2; March 7, 2025, through June 6, 2025 Option Period 3: June 7, 2025, through September 6, 2025 Optional 6-Month Extension IAW FAR 52.217-8: September 7, 2025, through March 6, REQUIRED CAPABILITIES:

1) Information Assurance (IA) and Cybersecurity are important to JCRM as an operational system while the modernized effort is being developed. Describe and provide an example of your company’s experience providing Cybersecurity and IA that utilizes the Risk Management Framework, such as: reporting and disclosing the status of security related matters, reviewing the Information Assurance Vulnerability Alert (IAVA) weekly and assessing impacts, updating Plans of Action and Milestones (POA&Ms) in the

Page 3 of 5 Pages enterprise Mission Assurance Support Service (eMASS), providing Commercial Off The Shelf (COTS) patch releases, and maintaining a fully Security Technical Implementation Guide (STIG)-compliant environment.

2) JCRM is an operational program that is utilized worldwide 24 hours per day, seven days per week, and 365 days per year. It is essential that the system remain available for users without issue. Describe and provide an example of your company’s experience providing Tier 3 Help Desk Support. This should include specialized skills and support over and above the skills and experience of Tier 2 support. Tier 3 deals with complex system and software issues that require in-depth technical, architectural, and developmental knowledge to solve a problem which may require a workaround or modification to the system and/or software.

3) JCRM has several external users connected to the system. Maintaining the system is important to the overall user experience. Describe and provide an example of your company’s experience in providing preventive, adaptive, and corrective maintenance for a system in sustainment and the methodology used (i.e., Agile). “Preventive maintenance” is defined here as: performing activities to prevent the occurrence of errors, reducing software complexity, and thereby improving program understandability and increasing software maintainability. “Adaptive maintenance” is defined here as: the implementation of changes in a part of the system, which has been affected by a change that occurred in some other part of the system or by an external system. Adaptive maintenance consists of adapting software to changes in the environment. “Corrective maintenance” is defined here as: corrective actions that deal with the repair of faults or defects found in day-to-day system functions. A defect can result due to errors in software design, logic, patches, and coding.

4) Similar to the above required capability is providing perfective maintenance. Describe and provide an example of your company’s experience in providing perfective maintenance on a system to include implementing new or changed user requirements and the methodology used. This also involves making functional enhancements to the system in addition to the activities to increase the system's performance even when the changes have not been suggested by faults. This includes enhancing both the function and efficiency of the code and changing the functionalities of the system as per the users' changing needs.

5) Testing is an integral part of fielding software. Describe and provide an example of your company’s experience conducting test and evaluation for preventive, perfective, adaptive, and corrective maintenance. Software testing is a process of executing a program or application with the intent of finding the software bugs and verifying that a software program or application meets requirements and operates as intended. Testing may be comprised of testing conducted at the contractor’s facility, Contractor Integration Testing (CIT) at the Government’s facility in a Secret Internet Protocol Router (SIPR) environment, and support for Government Acceptance Testing (GAT), which may consist of one or more of the following test events based on complexity of the change: (System

Page 4 of 5 Pages

Acceptance Test (SAT), Operational Test, Limited User Assessment (LUA), Risk Reduction Test Event (RRTE), Interoperability Test (IOP), and Cybersecurity Testing).

SPECIAL REQUIREMENTS:

The work to be performed under this contract/order is up to the Secret level. Therefore, the company will need to have a final Secret Facility Clearance from the Defense Counterintelligence and Security Agency Facility Clearance Branch at the time of proposal submission.

SOURCES SOUGHT:

The North American Industry Classification System Code (NAICS) for this requirement is 541512 with the corresponding size standard of $34,000,000.00.

In order to make a determination for a small business set-aside, two or more qualified and capable small businesses must submit responses that demonstrate their qualifications.

Responses must demonstrate the company’s ability to perform in accordance with FAR clause 52.219-14, Limitations on Subcontracting.

To assist DISA in determining the level of participation by small business in any subsequent procurement that may result from this Sources Sought Notice, provide information regarding any plans to use joint ventures (JVs) or partnering. Please outline the company's areas of expertise and those of any proposed JV/partner who combined can meet the specific requirements contained in this notice.

SUBMISSION DETAILS:

Responses should include:

1) Business name and address;

2) Name of company representative and their business title;

3) Small Business Socio-economic status (if small);

4) CAGE Code;

5) Prime contract vehicles; to include ENCORE III, SETI, NIH CIO-SP4, NASA SEWP V, General Service Administration (GSA): OASIS, ALLIANT II, VETS II, STARS III, MAS (including applicable SIN(s), groups or pools), or any other Government Agency contract vehicle that allows for decentralized ordering. (This information is for market research only and businesses with a valid cage that lack prime contract vehicles are still encouraged to respond to this notice.)

Questions regarding this announcement shall be submitted in writing by email using the question and response form attached to this announcement to daniel.p.obrien81.civ@mail.mil by no later than (NLT) 4:00 PM EDT on Wednesday April 10th, 2024.

mailto:daniel.p.obrien81.civ@mail.mil

Page 5 of 5 Pages

Businesses who wish to respond must send a response via email NLT 4:00 PM EDT on Friday April 19, 2024 to daniel.p.obrien81.civ@mail.mil. Interested businesses should submit a brief capabilities statement package addressing the specific questions above (no more than five pages) demonstrating the ability to perform the services listed under Required Capabilities.

Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received that is marked Proprietary will be handled accordingly. All submissions become Government property and will not be returned. All government and contractor personnel reviewing submitted responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as pursuant to 41 USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.

mailto:daniel.p.obrien81.civ@mail.mil