Case Development Modernization SOO.pdf

Defense Security Cooperation Agency Information Management & Technology

Case Lifecycle PEO

Statement of Objectives (SOO) Case Development Modernization

DSCA IM&T

Release 1.0 Date: Jan 20 2026

Table of Contents

Contents

Introduction Purpose Background Current State Challenges Future State Objectives Implementation Approach Interoperability Project Constraints Period and Place of Performance Summary

Introduction

Purpose

The purpose of the Case Development Modernization (CDM) initiative is to develop a modernized Case Lifecycle system to address critical challenges and evolving mission needs within the Security Cooperation (SC) enterprise. The modernization aims to streamline the Foreign Military Sales (FMS) case development process enhance transparency, reduce delivery timelines, and ensure compliance with cybersecurity, accessibility, and Zero Trust standards.

As of now no single Task Management or Document Repository system exists. The Case Development Modernization initiative includes the task management and document repository capability requirements that support the overall Case Lifecycle to streamline task management and have the capability for a case life cycle document repository. It should integrate seamlessly with the Case Development Modernization system for efficient data exchange and reporting.

By leveraging modern technologies, architectures, and methodologies, CDM will deliver a unified, scalable, and efficient platform that supports the entire Case lifecycle while ensuring interoperability with other systems across the Department of War (DoW).

This initiative is aligned with the President’s Executive Order 14268, "Reforming Foreign Defense Sales to Improve Speed and Accountability," and is essential to achieving the goals of improved delivery experience, enhanced situational awareness, and increased accountability across the Security Cooperation enterprise.

Background

The Defense Security Assistance Management System (DSAMS) is a mission essential system for the Security Cooperation (SC) community that provides military departments (MILDEPs) and Defense Agencies with the functionality necessary to develop and implement all unclassified Security Assistance (SA) cases, from the point of the customer’s request for material/services; through the establishment of the legal terms/conditions, initial pricing, payment schedules, and production of the Letter of Offer and Acceptance (LOA) document; ending with confirmation that initial funding and obligation authority is in place to proceed with case execution.

DSAMS provides additional functionality for FMS Training and Grant Training, commonly referred to as the training module. This provides the capability to fully execute cases involving foreign military training (as opposed to weapon systems or spare parts) for the MILDEPs. Originally created nearly 3 decades ago, it remains the IT backbone of foreign military sales.

The Security Cooperation tasks associated with processing FMS documentation from pre-Letter of Request (LOR) through to Case Closure are executed in decentralized systems making the tracking and reporting difficult. There is no current method to determine status of the overall process without requesting information across multiple organizations which results in a lack of situational awareness and transparency.

The President’s executive order 'Reforming Foreign Defense Sales to Improve Speed and Accountability EO 14268’ calls on DoD to modernize the entire case life cycle process to reduce time to delivery of materials and to increase transparency within the process; such that stakeholders in Security Cooperation enterprise can have improved delivery experience.

Additionally, the Case Launcher product prototype is currently under development. This prototype includes capabilities such as initializing a case, creating, editing, and tasking case lines, reviewing and entering case data and a Single Tracking System prototype for tracking foreign military sales efforts throughout the Case Lifecycle per EO 14268

A modernized Case Development Life Cycle is critical to achieving the goals outlined in the executive order.

Current State Challenges

DSAMS is a 27-year-old client-server application that coordinates case management and training case execution; it is accessed through a legacy Citrix environment. This architecture presents significant challenges stated below including high technical debt, limited scalability, performance issues, and frequent access disruptions due to Citrix instability. The aging application lacks transparency in operations, and data is siloed, making it difficult to access, share, or analyze information efficiently.

In addition, standalone smaller systems have been developed over time to perform narrow, supplemental functions that ideally should be integrated into a unified platform. These fragmented tools lead to process inconsistencies, duplicate data entry, and increased support overhead.

These limitations stem from an outdated technology which is unable to meet evolving business needs. Specifically:

Technological/Architectural Challenges: DSAMS's outdated architecture, utilizing disparate technologies like Java, PERL, Shell Script, PL/SQL, and CITRIX Storefront, restrict the system's ability to adapt to growing demands, such as providing broader access to case development information and latency in processing requests.

DSAMS’ reliance on highly complex database views, stored procedures, triggers and packages increase maintenance costs and prevents horizontal scaling. Additionally, DSAMS’ monolithic functional core limits the use of modern DevSecOps pipelines and static code analyzers, presenting greater risk and longer timeframes for major and minor enhancements.

Compliance Deficiencies: Legacy systems and processes within DSAMS fail to meet essential Zero Trust, Section 508 compliance, and other cyber findings, posing cybersecurity risks.

Process Fragmentation: Due to the proliferation of standalone systems and manual workarounds that replicate or supplement core system functions, critical case data resides in external MILDEP/IA and DoD systems (including COTS ERP packages and other custom-built applications) lacking seamless integration with DSAMS. These external systems, governed by varying business rules, interfaces, and data structures, create significant obstacles to efficient data sharing and consolidation. Thereby reducing the amount of actionable data that is available to security cooperation stakeholders.

Inefficient Data Collection:

Standalone systems data exchange are non-standardized, error-prone, labor-intensive, and lack adequate functional and administrative control by DSCA. This results in an unreliable, unpredictable, and sometimes opaque Case lifecycle process.

Modernization is crucial to address these core issues and enable us to effectively support the evolving needs of security cooperation.

Future State Objectives

• Ensure all capabilities satisfy business requirements and production readiness must include official signoff from business stakeholders.

• Establish Capabilities to replace legacy systems overtime.

• Enable horizontal scalability to reduce stress on the database and improve performance.

• Establish a modernized data exchange layer to facilitate efficient and real-time data processing.

• User interface with improved user experience and intuitive data entry/retravel.

• Solution a Case Lifecycle Task Management and Document Repository systems and integrate it with the Case Development Modernization system

• Provide Standard and Ad Hoc reporting with high data quality, accuracy, speed/flexibility satisfying business requirements

The following is the OV-1 envisioned for CDM:

Implementation Approach

Case Development Modernization (CDM) delivery includes, but is not limited to, the following activities and responsibilities:

The software development for CDM should be anchored in SAFe Agile framework and DevSecOps methodologies. The program will decompose requirements into epics, capabilities, and user stories, ensuring that development teams can deliver working software at a rapid cadence aligning with SAFe Agile methodology. Automated testing, continuous integration, and continuous delivery (CI/CD) pipelines will be central to this framework, enabling quick iterations and reducing certification and Authorization to Operate (ATO) delays. By aligning with modern software practices, Case Development Modernization (CDM) will ensure that value is delivered early and continuously throughout the lifecycle. CDM delivery includes, but is not limited to, the following activities and responsibilities:

• Identification and definition of case development product requirements (e.g. lightweight capability definitions, user-stories) based on both technical documentation and User- Feedback obtained through Human Centered Design and Agile processes.

• Assistance in the prioritization and planning of software work items within DSCA Product

Service Delivery Framework, as part of managing one or more software backlogs.

• Development of Solutions Architectures which utilize emerging and/or disruptive technologies (e.g. Artificial Intelligence (AI))

• Developing web-applications, APIs, and other software consistent with concurrently developed emergent architectures.

• Developing software documentation

• Developing and implementing an improved, modern data architecture while maintaining interim compatibility with a to-be-retired database

• Developing continuous integration and continuous delivery DSCA (CI/CD) pipelines, Infrastructure as Code (IaC), and automated tests for software systems

• Development of an automated means to generate CI/CD artifacts, culminating as a Software Bill of Materials (SBOM) or “body of evidence” used in the pursuit of an Authorization to Operate (ATO)

• Collaboration with the DSCA Software community of practice (i.e. Routine collaboration, best-practice and new technology identification)

• Support to Case Development Product/Program Managers and Owners as required

Interoperability

The core target state capabilities will be required to exchange data with key solutions across the DoD. As part of this modernization effort, the objective state will conform to modern data exchange practices, including application programming interfaces (API), to allow more efficient, real-time data processing. List of Interface Systems:

• Centralized Integrated System International Logistics (CISIL) to be replaced by Foreign Military Sales - Army Case Execution System (FMS-ACES)

• Management Information System for International Logistics (MISIL) to be replaced by Sea Services Security Assistance Logistics and Execution (S3ALE)

• Case Management Control System (CMCS) to be replaced by Case Tracking, Requisition, Accounting and Collaboration (CaseTRAC)

• Advana

• 1000 System

• Army Analyzer

• Airforce Security Assistance and Cooperation (AFSAC)

• Corporate Enterprise Training Activity Resource System (CETARS)

• Army Training Requirements and Resources System (ATRRS)

• General Accounting & Finance System (GAFS)

• Defense Integrated Financial System (DIFS)

• Drone buster Detect, Track, Identify, Mitigate (DTIM)

• General Fund Enterprise Business Systems (GFEBS)

• Defense Cash Accountability System (DCAS)

• Defense Enterprise Accounting and Management System (DEAMS)

• Defense Agencies Initiative (DAI)

• Security Cooperation Information Portal (SCIP)

• Socium

• USXPORTS

Project Constraints

• Approved AFG funding FY26 $5M

• Resource availability with competing priorities

• Case development must comply with:

o Arms Export Control Act (AECA) governing the export of defense articles and services. DSAMS must ensure all transactions comply with AECA provisions, including licensing requirements, end-use monitoring, and Congressional notifications o Foreign Assistance Act (FAA) guidelines regarding eligibility criteria, allocation of funds, and reporting requirements o National Defense Authorization Act (NDAA funding levels, program priorities, and oversight mechanisms o Federal Acquisition Regulation (FAR regulations to ensure fair and transparent acquisition processes o Fiscal Law and Appropriations Act adhere to fiscal law principles regarding budget execution and accountability o NIST (National Institute of Standards and Technology) standards S, NIST SP 800 related to cybersecurity o FISMA (Federal Information Security Management Act) for managing risk and protecting federal information systems o DFARS (Defense Federal Acquisition Regulation Supplement safeguarding Covered Defense Information (CDI) and Controlled Unclassified Information (CUI) o NIST SP 800-171 and the Cybersecurity Maturity Model Certification (CMMC) framework

• Refactoring of database code to modern APIs and application business layer to improve performance.

• Consolidation of four existing distinct Oracle database schemas into one Postgres database schema.

• Solution should be developed and hosted in DSCA AWS cloud.

• Solution should leverage DSCA Citadel CI/CD pipeline for DevSecOps.

• Zero Trust DoD CIO directive aligning with National Defense Strategy and Executive Order

(EO) 14028, Section 508 of Rehabilitation Act, Federal Information System Control Audit Manual (FISCAM) Audit and other Cyber Security findings compliance.

• To ensure full DISA Enterprise ICAM integration.

• Integrate Case Development Modernization system with other applicable FMF and IA systems across Case Lifecycle

• To ensure successful implementation, a governing body comprised of representatives from across the Security Cooperation(SC) enterprise must be established and followed.

Period and Place of Performance

• The period of performance is for one (1) Base year of 12 months with four (4) twelve (12) month option periods.

Base Year: 31 May 2026 – 30 May 2027 Option Year 1: 31 May 2027 – 30 May 2028 Option Year 2: 31 May 2028 – 30 May 2029 Option Year 3: 31 May 2029 – 30 May 2030 Option Year 4: 31 May 2030 – 30 May 2031

Summary

The target state system should be designed to replace legacy systems, leverage modern architecture, and effectively meet the mission needs of the Case Development Lifecycle.