ChBA Phase 1_Attachment 4 - Legacy Application Portfolio Current State_2026-02-27.pdf
PDF 71 KB Posted
- Attached to
- Accelerated Transformation of Legacy Applications and Systems (ATLAS) Challenge Based Acquisition (ChBA)
- Solicitation number
- ATLAS-1
About this file
This is an attachment to a Challenge Based Acquisition (ChBA) solicitation that describes the current state of a legacy application portfolio requiring modernization under the Accelerated Transformation of Legacy Applications and Systems (ATLAS) program.
The portfolio consists of heterogeneous platforms and frameworks accumulated over multiple technology generations, supporting safety, mission support, and administrative business functions. Application frameworks include Microsoft .NET Framework and .NET, Java (monolithic and early service-based architecture), ColdFusion, legacy web application frameworks, and batch processing frameworks. Data infrastructure encompasses relational databases (Oracle, PostgreSQL, Microsoft SQL Server), legacy data stores, file-based persistence mechanisms, ETL pipelines, and messaging-based data exchanges with mixed patterns of coupled and shared databases. Hosting environments include on-premises data centers, public and government cloud environments (AWS, Azure), virtualized infrastructure (VM-based), and Kubernetes containers. The architecture is predominantly monolithic with limited service decomposition, point-to-point integration, shared middleware components, and mixed stateful and stateless designs. Delivery and operations tooling includes traditional CI/CD and manual release processes (Jenkins, Bitbucket), broader DevOps toolchain components (Artifactory, Terraform, Ansible, Datadog, SonarQube, Jira, Confluence), mixed configuration management, and legacy logging and monitoring tools with limited standardization across teams.
Modernization efforts currently reflect partial containerization, limited microservices and cloud-native adoption, inconsistent documentation and architectural visibility, and varying levels of cloud readiness and technical debt. The organization is actively evaluating AI services and platforms, currently utilizing AWS, Azure, Google, OpenAI, Google, and Anthropic models. Enterprise shared services platforms in use include OKTA and CyberArk for identity and access management, Fusion for enterprise search, Gravitee and Qlik/Talend for APIs, KSN and SharePoint Online for collaboration, Microsoft PowerBI and PowerApps, UiPath for RPA, Alfresco for document management, and MyProfile.
View the file
Other files
Show all 11
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
Accelerated Transformation of Legacy Applications and Systems (ATLAS) Challenge Based Acquisition (ChBA)
Attachment 4 - Legacy Application Portfolio – Current State
The legacy application portfolio consists of a heterogeneous mix of platforms, frameworks, data stores, and deployment patterns accumulated over multiple generations of technology and includes applications supporting safety, mission support and administrative business functions. The portfolio includes but is not limited to the following:
Application Frameworks
• Microsoft .NET Framework and .NET
• Java (monolithic and early service-based architecture)
• ColdFusion
• Legacy web application frameworks and custom- built runtimes
• Batch processing and scheduled job frameworks
Data Platforms & Storage
• Relational databases including Oracle, PostgreSQL, and Microsoft SQL Server
• Legacy data stores and file-based persistence mechanisms
• Data Integration layers, ETL pipelines and messaging-based data exchanges
• Mixed patterns of highly coupled and shared databases across applications
Hosting & Infrastructure
• On prem data centers
• Public and Government Cloud Environments (AWS, Azure)
• Virtualized Infrastructure (VM-based deployments)
• Kubernetes container
Architecture
• Predominantly monolithic application architecture
• Limited-service decomposition and point-to-point integration
• Shared middleware components and enterprise integration patterns
• Mixed stateful and stateless application designs
Delivery & Operations Tooling
• Traditional CD/CD and manual release processes including but not limited to Jenkins, Bitbucket
• Broader DevOps toolchain including but not limited to, Artifactory, Terraform, Ansible, Datadog, SonarQube, Jira, Confluence
• Mixed configuration management and scripting-based deployments
• Legacy logging, monitoring, and security tooling
• Limited standardization across application teams
Modernization State
• Partial containerization
• Limited adoption of microservices and cloud-native services and platform capabilities
• Inconsistent documentation and architectural visibility across the portfolio
• Inconsistent use of modern CI/CD, security automation
• Varying levels of cloud readiness and technical debt
AI Tooling
• Constantly evaluating AI services and platforms
• Currently utilize AWS, Azure, Google provided AI services and Open Ai, Google and
Anthropic models broadly.
Enterprise Shared Services Platforms
• Identify and Access Management – OKTA, CyberArk
• Enterprise Search - Fusion
• API – Gravitee, Qlik/Talend
• Collaboration – KSN, SharePoint Online, OneDrive
• Microsoft PowerBi, PowerApps
• RPA - UiPath
• Document Management – Alfresco
• MyProfile
File details come from the government source that posted it. Updated .