Page 1 of 8 Pages

SOURCES SOUGHT NOTICE

612675480

The Defense Information Systems Agency (DISA) is seeking sources for Enterprise Level Engineering and Systems Analysis Support (ELESAS)

CONTRACTING OFFICE ADDRESS: DISA/DITCO-NCR, 6910 Cooper Ave, Ft. Meade

MD, 20755

INTRODUCTION:

This is a SOURCES SOUGHT NOTICE to determine the availability and technical capability of small businesses and large 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 Enterprise Engineering Directorate (DISA OE) is seeking capabilities from potential sources for engineering support for systems engineering, enterprise level network systems assessments, systems and tools development, performance evaluation, and technical evaluations for the IT technology relating to software defined everything environments, Department of Defense (DoD) Network infrastructure and applications and services. Details on the focus areas are provided at the end of this notice, see Appendix A.

As described later in detail, this is a complex engineering development and support task requiring the contractor to:

Deliver enterprise level subject matter experts within a few days of notification by the PM for diagnostic support with existing access and knowledge of existing DISA performance monitoring systems and knowledge of subject systems requiring diagnostic support.

Develop and deliver new applications used to support network analysis, user experience metrics and end-to-end diagnostics within the Department of Defense (DoD) networks at up to the Top-Secret level using evolving technologies including artificial intelligence within the constantly evolving security requirements within DoD within both IPv4 and IPv6 environments and impact levels (IL) 2, 4, 5, 6 and in the future IL 7.

The anticipated period of performance is 30 September 2027 to 29 September 2032.

The anticipated place of performance is primarily at Fort George G. Meade, MD but may include travel requirements anywhere in CONUS or OCONUS based upon emerging mission requirements.

Page 2 of 8 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: Many elements of ELESAS are new requirements. However, portions of this requirement are currently being executed under the following:

Contract Number: HC104718D2004, task order HC104722F0211 Contract Vehicle: SETI Incumbent and their size: Booz Allen Hamilton (BAH), large business Method of previous acquisition: Fair opportunity competition Period of performance: 30 September 2022 to 29 September 2027

REQUIRED CAPABILITIES:

1) OE21 requires enterprise level subject matter experts on short notice (within days) with appropriate clearances and accesses for various monitoring systems within DISA to include diagnostic support as described in Appendix A, 4.1.1. A sampling of the applications and programs that have requested diagnostic support or other performance engineering support functions are provided in Appendix A, 4.1. Some of those mission spaces (e.g. White House classified communications support) are extremely time sensitive and considered a “no fail” mission requirement. As this is a developing environment, there are times where new technologies arise and there is a need for diagnostic assistance. Describe and provide an example of how your company has successfully filled similar highly technical positions with clearances within a short period of a few days or up to a few months.

2) Analysis of systems for support requires in depth knowledge of the current and proposed suites of monitoring solutions within DISA (e.g. Netscout, IPFix, various security tools) as well as supporting technologies (e.g. AWS Cloudwatch), the limitations of these tools (points of observability, data rates), and how they feed into other systems in DISA (e.g.

SNOW, GMS). OE has been increasing the use of AI tools and complex analysis capabilities such as DataBricks in tool development and predictive analyses. Describe and provide examples of your company’s experience of enterprise level expertise with developing custom decision support tools using data from monitoring solutions such as Netscout, IPFix, and other commonly used tools within the current DISA environment. Include expertise in developing custom solutions within those tools

Page 3 of 8 Pages and how they were extended using AI tools with a reference to the size of the data lakes accessed to support the AI tools selected.

3) Enterprise Level Predictive Engineering requires modeling the traffic capacities for various network configurations in both the optical and IP layers around the world to support DoD missions, developing reports and contingency plans for numerous scenarios, and simulation modeling for specialized areas such as voice traffic on different networks and National Command Level applications. Describe and provide an example of your experience of enterprise level experience with network capacity and path modeling in both the optical and IP layers. Include which automated tools were used.

SPECIAL REQUIREMENTS:

Must have Top Secret Facility Clearance. Please provide your current Facility Clearance level.

SOURCES SOUGHT:

The North American Industry Classification System Code (NAICS) for this requirement is 541512 Computer Systems Design Services with the corresponding size standard of $34M.

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 from small businesses 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.)

Page 4 of 8 Pages

Businesses who wish to respond must send a response via email NLT 2:00 PM Eastern Daylight Time (EDT) on October 14, 2026 to Benjamin Cumming (KO), benjamin.cummings6.civ@mail.mil and Sarah Thacker (CS), sarah.a.thacker2.civ@mail.mil. Interested businesses should submit a brief capabilities statement package addressing the specific requirement needs above (no more than ten pages) demonstrating the ability to perform the services listed under Required Capabilities and clearance under Special Requirements.

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.

For information on DISA’s requirements, you can find current information on our home page:

www.disa.mil – that includes current forecast and the current acquisition strategies. If there is no information regarding the requirement you may be inquiring about, then there is no additional publicly available information. Please continue to review www.disa.mil.

http://www.disa.mil/

Page 5 of 8 Pages

Appendix A

1. Background. DISA OE is an organizational unit within the Enterprise Integration and Innovation Center (EIIC) providing specialized problem resolutions support for issues experienced by these fielded SAS, as well as analysis and technical assessments for SAS supported by DISA. Problems with the performance of fielded applications and concerns with the supporting networks tend to be especially dynamic and require rapid access to information. This drives a need for expertise in a wide range of technological areas using diverse tool sets to understand these complex applications supported in a software defined network with many shared resources. Portions of DISA-OE perform end-to-end optimization, analysis, and troubleshooting of DISA and mission partner enterprise applications, services, and shared infrastructure capabilities. DISA- OE is frequently called upon to provide technical solutions to performance issues covering multiple technology domains. DISA-OE also will be asked to help enhance operational efficiency, optimize service performance, and resolve operational problems among multiple stakeholders. The support DISA-OE provides includes modeling elements of the infrastructure within the DoD. This includes using several specialized monitoring tools (both commercially available and locally developed) to capture information about both systems and networks.

The end-to-end nature of OE responsibilities ties together the need to blend tool development, alert definitions and development, modernization efforts such as IPv6 deployment and metric assessments among other disciplines together in achieving performance engineering goals for complex programs to provide adequate end user performance for DISA supported users.

DISA-OE can participate with ensuring programs are sufficiently mature to be supportable by DISA Operations. DISA-OE often provides solution analysis for technical problems that arise among different interdependent programs and projects and performs analytic studies to determine optimal future supported services network and computing resource configurations. An example here might be a planned technical refreshment for large elements of the infrastructure and determining which currently hosted applications will be impacted in what ways.

That can be as minor as ensuring they are made aware of a planned authorized service interruption (ASI) or as major as determining that these named supported systems require their own technical refreshment efforts to function after the infrastructure element upgrade.

2. Objectives. The objective of this task order is to provide engineering support for systems engineering, enterprise level network systems assessments, systems and tools development, performance evaluation, and technical evaluations for the IT technology relating to software defined everything environments, DoD Network infrastructure and applications and services.

Page 6 of 8 Pages

3. Scope. The contractor shall provide enterprise level subject matter experts (SMEs) within diverse technical skill areas to assist DISA-OE with identification, diagnosis and problem resolution analysis for systems and infrastructure elements supported by DISA over the course of the order. The nature of this analysis assistance is best described as supporting systems with high mission impact and providing analysis responses in a limited and short time frame as compared to typical order timeframes. That can be as short as a week or as long as a full year. The systems to be supported, technologies required, and test and monitoring tool expertise required will vary frequently over the life of the order. The contractor may also support the DISA-OE by analyzing DISA and DoD standard engineering and business processes to provide recommendations on the monitoring, reporting and system architectures of monitoring tools, DoD Network infrastructure and applications and services. The contractor shall support various data collection, analysis and problem resolution efforts for developmental and existing applications and elements of the infrastructure within DoD in support of all DISA-OE missions.

Individuals shall have access to SECRET information through SIPRNET.

Individuals will also have access to TOP SECRET information through briefings.

4. Primary Mission Focus Areas. The work to be performed as already noted is quite varied and unpredictable. The core mission focus of this contract is supporting the Performance Engineering Division (OE2). The work performed is primarily focused in performance engineering with two additional areas for other Divisions as well as some support for other DISA initiatives outside of OE.

4.1 Enterprise Level End to End Performance Engineering

The OE2 Division can be (and is) called upon to address any and all aspects of end-to-end performance problems with developmental and fielded systems. Everything from the end user out to the working applications and back is fair game. All aspects of the system life cycle are fair game, driving a need for a very flexible workforce to support these requirements.

4.1.1 Diagnostic Support

This category encompasses diagnostic engagements for complex systems experiencing performance issues. The issues are typically brought to the OE2 organization after all the other support tiers (Help Desk, Program Office Engineering Staff, Program Support Contractors, etc.) have been unable to diagnose root causes for performance challenges with deployed or developmental systems. These often involve very new technologies or very old technologies, and by the time they get assigned to OE, have been causing enterprise level performance problems (e.g. all DoD users are impacted) so are high to very high visibility. The contractor will be expected to be able to

Page 7 of 8 Pages provide enterprise level subject matter experts (SMEs) on short notice with appropriate clearances and systems accesses to address these problems for whatever technologies arise. Accesses mean access to the diagnostic and reporting systems used within DISA. Typical requirements are to be able to correctly frame the problem, create test strategies and plans, execute those plans and develop the data needed to diagnose root cause analysis for complex systems. Historically this has been aided by having members of the contractor team supporting that application also participate in the test and diagnostic processes. Examples of diagnostic support engagements have included Thunderdome security impacts, Voice Over IP failures on classified and unclassified networks, mobile communications at several classification levels, mission partner IPv6 implementation impacts, assorted types of classified conferencing applications, supporting Defense Threat Reduction Agency (DTRA) initiatives, combatant command imaging application network support, assorted Defense Health Agency applications, White House communications of various types and applications used for strategic troop movement planning. Depending upon mission requirements, the Government might require the contractor to bid and provide an option for “Follow The Sun” support for 24/7 operational support for complex diagnostic engagements for high profile systems. Examples might include troubleshooting for an under-performing pilot recovery system or a command-and-control related system while the US is engaged in low (or high) intensity kinetic conflict.

4.1.2 Service Performance and Monitoring Management (SPMM) Support

DISA has been undertaking program steps to ensure new and upgraded existing information systems within the DoD improve their user experience. That effort focuses on the reliability, maintainability, and user experience for the applications in ways that had not previously been a priority compared to budget, schedule and security concerns. This is evolving into a multi-step process of reviews with programs with OE2 assessing how they will support their systems and also capture and report on their user experience. Analysis of systems for support requires in depth knowledge of the current and proposed suites of monitoring solutions within DISA (e.g. Netscout, IPFix, various security tools) as well as supporting technologies (e.g. AWS Cloudwatch) and the limitations of these tools (points of observability, data rates) and how they feed into other systems in DISA (e.g. SNOW, GMS). The contractor would assist the Government in conducting these assessments as well as advising programs on improvements to better meet overall DISA objectives. It is expected that there will be ten to twenty assessments per week when the program is fully operational. The applications or program assessed will range from very small (updates cryptographic content worldwide) to very large (a global command and control system).

4.1.3 Diagnostic Tools and Reporting Support

Many of the tools used to collect network or performance information are quite complex, requiring specialized training and support. They also can change frequently as new tools win favor and are purchased or leased. The contractor will optionally be asked to bid and support the deployment, care and upkeep of deployed monitoring tools. They will provide training on the tools and shall support the development of

Page 8 of 8 Pages various reports and dashboards as needed. They would be expected to support developing alerts for various systems when monitoring shows performance issues, and depending upon the tools in question, develop, deploy and maintain synthetic monitoring tools (e.g. “bots”) used to capture application performance information.

They will also be expected to be able to support a significant level of diagnostic analysis using the information provided by their tools.

4.1.4 Support An Analysis Capability.

To support the diverse mission requirements within the OE problem space, OE maintains a cloud-based computing resource that hosts numerous developmental tools and analysis initiatives. The contractor would be required to support the updates and care and operations of this resource. Both unclassified/sensitive (IL4/5) and IL6 (Secret) environments are maintained.

4.2 Enterprise Level Predictive Engineering

The Predictive Engineering Division (OE3) has historically been the largest consumer of contracting engineering services within OE. Their missions include but have not been limited to modeling the traffic capacities for various network configurations in both the optical and IP layers around the world to support DoD missions, developing reports and contingency plans for numerous scenarios, and simulation modeling for specialized areas such as voice traffic on different networks and National Command Level applications.

They have developed numerous decision support tools with highly variable update rates and audiences, especially during periods of active kinetic engagements.

4.3 Enterprise Level Observability Engineering

The Observability Engineering Division focuses on making sense of the large volumes of data collected by the numerous DISA managed monitoring systems. They are pursuing numerous artificial intelligence driven initiatives and use a variety of tools such as DataBricks to develop actionable intelligence from source data derived from the sensor and maintenance platforms. They also manage various policy areas such as Chief Engineer Panels (CEPs).

4.4 IPv6 Implementation Support

This contracting effort also optionally provides support for the DISA IPv6 Implementation Effort in Infrastructure Directorate’s IE4 Division. These efforts range from policy updates, tracking implementation progress within the Combatant Services, and can include details like circuit modeling.

4.5 Enterprise Level Information Modeling

In support of other DISA organizations, OE may be called upon to support testing standards impacts on the performance of complex systems. Examples might be testing changes to commonly used data standards (e.g. Link 16, Link 22) enhancements to create new functions.