Attach007-FMS-ACES RFI - Operating Environment Description.pdf

UNCLASSIFIED

Foreign Military Sales – Army Case Execution System (FMS-ACES)

1 FMS-ACES Operating Environment Version 1.0; October 2022

Document Purpose: This document provides insights on the envisioned operating parameters for the

FMS-ACES system and the data stored in support of the legacy CISIL application that will need to be migrated to FMS-ACES.

FMS-ACES Operating Environment: FMS-ACES will be an enterprise application that will only be accessible over the DoD NIPRNet serving mostly Department of the Army personnel located in CONUS locations. There will be non-DoD personnel using the application, but they will be provided .mil accounts and access to the system. The system will integrate with 26 other Federal Government systems of varying age and integration capabilities, some only able to exchange information via SFTP while others will have API capability. Table 1 lists several operating parameters for FMS-ACES.

Table 1: FMS-ACES Operating Environment

Parameter Description

Number of Users Core Users CONUS: 1000

Core Users OCONUS: N/A

Core Concurrent Users: 600

Number of Locations CONUS: 10

OCONUS: N/A

User Composition 1000 core personnel distributed as:

• 90% End users

• 7% Staff and Support

• 3% Management

Connectivity NIPRnet

Domains .mil

Security CAC Enabled/Law Regulated

Privacy Controlled Unclassified Information (CUI)

Data Format Types Text, Numeric, Boolean, GIS, Date, Time

Storage Total for Data: 8TB

Total for Documents: 30TB

Retention Requirements: 10 years after final FMS case closure

Document Formats Microsoft Suite (docx, pptx, xlsx, rtf)

ASCII (csv, txt, tsv, dat, xml)

Adobe (pdf fillable/non-fillable)

Image (png, jpg, gif, tif, bmp)

Others (zip, shp)

2 FMS-ACES Operating Environment

Parameter Description

Number of Business

Processes

~75 process flows

• 54 documented process flows

• 21 additional process flows in development

Number of Interface

Partners

26 System Interfaces including:

• File transfer over SFTP for legacy systems

• API integration for modern system

User Environment Types Full connectivity

Legacy Data and Migration: The legacy CISIL system was developed and delivered in the 1970s and is written in the COBOL programming language. There have been several external initiatives (Army

Reports and the Case Management Analyzer (CMA)) that have been deployed to augment CISIL capabilities. Data exists as follows:

• Internal CISIL Data: CISIL is not built upon a database. Its data is instead stored in multiple flat files and VSAM files (industry standard in the early 70s for mainframe systems for rapid data retrieval). There are approximately 75 different files used by CISIL for storing its data.

Attachment 008 - Sample Files contains 29 sample data files that preserve the structure of the

CISIL data files but may not preserve the size of the file (number of records and file size). A high-level description of the data within these files follows:

‒ Files have as few as 1 data field and as many as 73 data fields

‒ Files are fixed position files (each data field begins in a specific column and has a fixed maximum length

‒ Files may have as few as a single record to as many as 7.5 million records.

‒ File sizes range from as small as 4MB (estimated) to as large as 40GB (estimated)

• Army Reports: This is a standalone DSCA owned/operated application that has its own Oracle database populated daily from many of the CISIL data files. The data in this database does not need to be migrated into the FMS-ACES system, but it does provide some insights into how the data within the CISIL files are related while also providing a variety of generic ad-hoc reports used by end users. The PDF for this ERD is included in in Attachment 008 – Sample Files.

• Case Management Analyzer: This is a standalone application that augments CISIL functionality.

It has its own database derived from CISIL datafiles. There is no ERD available for this system.

The data in this database does not need to be migrated into the FMS-ACES system, but it does provide some insights into how the data within the CISIL files are related.

• Case Attachments: Each case in CISIL is augmented by attachments in various file formats.

These files have formats that available as early as the 1970’s until today. The files are not uniquely identified to the case study by UUID but instead by filename. Supporting files for

3 FMS-ACES Operating Environment current cases in CISIL will need to be migrated to FMS-ACES and directly associated with the case.

• Microfiche: Input/Output records based on archival rules per specific time frames from CISIL are stored in microfiche. Purging of the Input/Output file is done quarterly. These attachments will not be migrated to FMS-ACES.

Figure 1: ERD for Army Reports Database