Attachment 004 - FMS-ACES Requirements Master List (RML).pdf

UNCLASSIFIED

UNCLASSIFIED

Foreign Military Sales - Army Case Execution System

(FMS-ACES)

Attachment 004- FMS-ACES Requirements Master List

(RML)

Version 1.0

21 September 2023

Prepared By:

Product Lead, FMS-ACES

Tab Name Description

RTM

Requirements Traceability Matrix (RTM) ‐ FMS‐ACES Requirements List This includes:

Column B ‐ Identifies requirements that are Key Performance Parameters (KPPs) or Key System Attributes (KSAs) Column C ‐ Requirement ID Column D ‐ Core Capability (see FMS‐ACES Development and Deployment RFI.pdf for description of each) Column E ‐ Category (e.g., Query/Reports, Alerts and Notifications, Interfaces, etc.) if applicable Column F ‐ Requirement Statement

Capability Descriptions A description of the capability areas for which the requirements are aligned to Interface Requirements Alignment of required system interfaces to their corresponding requirements in the RTM Tab.

Interface Details 1‐n list of system interfaces required to be implemented, and associated attributes for each interface.

Interface Definitions Definition of interface attributes (columns C thru F in Interface Details Tab) LPRDs Applicable Laws, Policies, Regulations and Directives Acronyms Acronym List

Table Of Contents

Attachment 004 ‐ RML ‐ TOC 1

KPPs & KSAs

Requirement ID Core Capability Category (where applicable) FMS‐ACES Requirement Statement 1 Case Initiation Data The system shall provide the capability to systemically determine case type based on data received.

2 Case Initiation Business Process Workflow Automation

The system shall provide the ability to accept different case statuses (Proposed, Offered, Accepted, Implemented) and perform appropriate action based on validation rules.

3 Case Initiation The system shall provide the ability to identify, for appropriate lines, that a transportation plan is required for the line and set an indicator according to defined business rules.

4 Case Initiation Interface The system shall provide the capability to receive from DSAMS, capture, and view the Army case sub‐line information. This information includes quantity, price, NSNs and part number.

5 Case Implementation Data Validation The system shall provide the ability to perform logistical case review for execution.

6 Logistics Data The system shall provide the capaibility to systemically create the Presidential Drawdown (PD) number with asociated Record Control Number(s) (RCN) provided by scanning the pdf or Excel of PD EXORD.

7 Logistics Data Management The system shall provide the capability to systemically initiate skeletal requisitions for all FMS Case Types based

8 Logistics Business Process Workflow Automation The system shall provide the ability execute Travel Case funding data according to defined business rules.

9 Logistics Data Management The system shall provide the ability to store the major shipment milestones from initial shipment (from the depot or vendor) to receipt for BPC material to the extent possible.

10 Logistics Interface The system shall provide the ability to generate cancellation requests (869C) to the source of supply to stop logistical actions/delivery at the Country, Case, line/subline, requisition level as required.(i.e. sanctions).

11 Logistics Data Management The system shall provide the ability to recycle/reuse publication account numbers (PANs).

12 Logistics Processing The system shall provide the ability to systemically create a previously received CSP list and duplicate to a new 13 Logistics Processing The system shall provide the ability to calculate an average monthly demand for each NIIN determined to be 14 Logistics The system shall provide the capability to systemically create the Publication requisition based upon uploaded 15 Logistics The system shall provide the ability to validate NSNs for CSP report based upon defined business rules.

16 Logistics The system shall provide the capability to mark a requisition as 'suspended' via an indicator which may be

17 Logistics The sytem shall provide the ability to systemically validate and deliver digital publications for initial distribution on Publications Blanket Order case types based upon defined business rules.

18 Logistics The system shall provide the capability to systemically determine/assign the Fund Center for requisition(s)

19 Logistics The system shall provide the capability to systemically import transaction data based upon pre‐defined templates (A01‐ZT5, AE3‐Z25, AS3, Z12, SDR initial memo, etc.) of user provided data based upon defined

20 Logistics OBE: The system shall provide the capability to send a request to cancel requisitions validated by source of

21 Logistics The system shall provide the capaibility to systemically create a Supply Discrepancy Report (SDR) ingested by

22 Logistics The system shall provide the capability to review SDR information and provide suggestions for processing way forward (formerly CISIL SDR Expert System) based upon defined business rules.

23 Logistics The system shall provide the ability for systemic closure of a RCN on a Presidential Drawdown when the RCN

24 Logistics The system shall provide the capability to systemically create a list of spare parts that support weapons systems in the SSBO process ingested from a Source of Supply provided spreadsheet.

25 Logistics The system shall provide the capability to systemically import and manually add requisition status based upon defined business rules and user roles. [i.e. Ready to ship, etc]

26 Logistics The system shall provide the capability to add and assign, via user interface, workload indicators, Review of Impacts to Strategic Readiness (RISRs), Command Assignments, Priority Manager Tool,etc.

27 Logistics The system shall provide the capability to generate a PRON based upon business rules and defined user roles.

28 Logistics Data Validation The system shall not pass budget authority for a case line when the Contingency Line MASL is used.

29 Logistics Data Validation The system shall not permit any orders to be placed against a Contingency Line 30 Logistics Data Validation The system shall not permit any billing against a Contingency Line

31 Logistics Compliance The system shall provide the capability to identify on the requisition/order whether the requisitioned investment item is being sold from stock as 'Not to be Replaced', 'Replaced in Kind', or 'Replacement with

32 Logistics Business Process Workflow Automation

The system shall provide the capability to process requisitions with a single address, multiple addresses, or addresses that denote final destination.

33 Financial Execution Business Process Workflow Automation The system shall provide the ability to execute Emergency Order funding data.

34 Financial Execution Processing The system shall provide the ability to receive, execute, and validate Interfund and non‐Interfund Billing

35 Financial Execution Business Process Workflow Automation

The system shall provide the ability to manage the performance of and execution of disbursement transactions according to defined business rules.

36 Financial Execution Processing The system shall provide the ability to create and manage publication billing according to defined business 37 Financial Execution Processing The system shall provide the ability to receive and process case, line/subline, and requisition funding data in

38 Financial Execution Business Process Workflow Automation

The system shall provide the ability to manage the performance and execute the transaction of progress payments.

39 Financial Execution The system shall provide the ability to create and manage SDR billing.

40 Financial Execution Interface The system shall provide the capability to identify the type of budget authority.

41 Financial Execution Billing The system shall provide the capability to report the actual execution costs against initial pricing.

42 Financial Execution Billing The system shall provide the capability to create a standard financial delivery (i.e. XA) record. This delivery transaction provides a description of articles or services purchased and their value (estimated or actual) to be

43 Case Lifecycle Processing The system shall provide the ability to execute Case Financial Evaluations.

44 Case Lifecycle Processing The system shall provide the ability to execute Case Logistical Evaluations.

45 Case Lifecycle Processing The system shall provide the ability to execute Case Closure Evaluations.

46 Case Lifecycle Data Retention The system shall provide the ability to create and maintain the Case Master Plan.

47 Case Lifecycle Query/Report The system shall provide the ability to conduct Case Lifecycle Management Reviews (aka CEPS) to include 48 Case Lifecycle The system shall provide the ability to report C1 Delivery based on business rules and LRPDs [SAMM].

49 Case Lifecycle LPRDs The system shall send all physical shipping data for stock/DLMS items sent to Afghanistan, Iraq, and Pakistan to 50 Case Lifecycle Interface The system shall capture and send all serial numbers of EEUM items to the EUM Database.

51 Case Closure Processing The system shall provide the ability to reopen closed cases (both Accelerated/Non Accelerated).

52 Case Closure Processing The system shall provide the ability to manage and execute Line Recertification on reopened cases.

53 Case Closure Processing The system shall provide the ability to cancel a case after certification.

54 Case Closure Processing The system shall provide the ability to manage and execute Line Certifications.

55 Case Closure Processing The system shall provide the ability to manage and execute Case Certifications.

56 Foundational Interface The system shall provide the ability to receive and/or send data via interfaces in accordance with SV‐3f and 57 Foundational Data The system shall provide the ability to, when appropriate, systemically create a new and/or populate an

58 Foundational Data The system shall provide the ability to (CRUD) manually create a new and/or populate an existing data strucuture(s) based upon defined user roles. [Example: SDRs, Case Master Record (formerly the ILIF), MRHS, 59 Foundational Alerts and Notifications The system shall provide the capability to compare/reconcil incoming information from interfaces to identify what information has changed, so a notification/alert may be provided to the end user as defined in business

60 Foundational Remarks The system shall provide ability to add remarks to the case, line/subline, requisition, and SDR levels based on

Attachment 004‐FMS‐ACES RML ‐ RTM 1

Requirement ID Core Capability Category (where applicable) FMS‐ACES Requirement Statement

61 Foundational Review The system shall provide the capability to automate reviews and evaulations, as much as possible, so a notification/alert may be provided based upon defined business rules.

62 Foundational Alerts and Notifications The system shall provide the capability to send automated communications/alerts/notifications (e.g. internal messaging, email, text) based on established business process activity triggers and document templates.

63 Foundational Document Management The system shall provide the ability to use a document upload tool to associate supporting documentation (Word, PDF, etc.), images (.jpeg, .gif, etc.), and/or data to a specific case, line/subline, requisition, etc.

64 Foundational Data Management The system shall provide the ability to CRUD reference tables based on defined user roles. [i.e. CCOPES 65 Foundational Interface The system shall provide the ability to systematically prioritize and process incoming transactions based on 66 Foundational User Interface The system shall adopt the use of standard DoD Army FMS language and naming conventions.

KSA 03 67 Foundational Defined User Roles The system shall provide the ability to assign and manage roles based on organization, division, branch, 68 Foundational Query/Report The system shall provide the ability to view and query database audit information via the user interface based

69 Foundational Query/Report The system shall provide the ability to maintain and report application analytics/productivity/usage statistics.

Productivity statistics shall include concurrent users, job submissions, transactions throughput and system

70 Foundational User Interface The system shall provide the ability to track and display the real time status via dashboard of each case according to established business rules and parameters based on defined user roles.

71 Foundational Data Management The system shall provide consistency with numerical data formats (dates, dollars, numbers) IAW LRPDs.

72 Foundational Single Data Entry

The system shall provide user interface features designed to reduce the amount of direct keying required for transaction processing such as:

• Default values based on system maintained transaction and user profiles

• Value look‐up tables

• Highlighting or accentuating required fields

• Grayed data fields that are unavailable for user entry

• Cut/copy/paste functionality

• Keyboard shortcuts (e.g. function keys to invoke help facility, clear screen, etc.)

73 Foundational User Interface

The system shall provide a consistent web‐based user interface and experience across all approved devices for all authorized users.

For example, data should be shown in data grids that are filterable, sortable, pagable, and customizable (ability

74 Foundational Data Quality

The system shall provide the ability to reject/suspend transactions from business partners and provide the ability to recycle in accordance with defined business rules.

Reject processing shall include the ability to perform the following functions:

‐ Report rejected transactions

KSA 05 75 Foundational Alerts and Notifications The system shall include a centralized error detection and automated correction process (aka VVVs) with systemically assigned unique reject code(s) and reason(s), based on defined business rules, including a list of

76 Foundational Query/Report The system shall provide the ability for an authorized user to create, suspend, schedule, distribute, modify and/or terminate on a recurring time interval for reports to be generated.

77 Foundational Query/Report The system shall provide the ability to display a header and footer on reports, including defined information to be displayed, such as CUI disclaimers on pages and reports.

78 Foundational Data Retention The system shall provide the ability to maintain and display historic versions of the Case (new version would be created each time a Modification or Amendment is Implemented).

79 Foundational UI/UX The system shall provide the ability to allow users to access online help and embedded tool tips.

80 Foundational Common Operating Picture (COP) The system shall provide the ability to create and display an overall view of case Development and execution status, such as a Common Operating Picture (COP), based upon defined business rules.

81 Foundational Common Operating Picture (COP) The system shall provide the ability for a user to create and interact with configurable dashboards based on user role.

82 Foundational The system shall provide the ability to create/update/remove standardized pre‐populated fillable templates or forms based on defined user roles.

83 Foundational The system shall provide the ability to print on Government Furnished Equipment (GFE).

KSA 01 84 Foundational LRPDs The system shall provide the ability to implement system‐configurable parameter changes based on changes to and in support of applicable laws, regulations, policies, and directives (LRPDs).

85 Foundational Business Process Workflow Automation

The system shall provide the ability to automate and configure business process workflows via a visual display based on defined user roles.

86 Foundational Alerts and Notifications The system shall provide the ability to send system‐wide alerts and notifications to all authorized users.

87 Foundational UI/UX The system shall provide a user‐configurable, interactive, context‐aware help ability within business process implementation.

KPP 01 88 Foundational Compliance The system shall include shared data, in the proper format/structure, that provides full enterprise visibility of the case lifecycle and that is 100% compliant with DSCA/DoD established data standards.

89 Foundational The system shall provide the ability to navigate and access a hierarchy of related case data via dashboard [i.e.

all lines/sublines on a case, all requistions on a line, etc]

90 Foundational The system shall provide the ability to create/read/update/delete [CRUD] business rules using existing data fields based on user defined roles.

91 Foundational The system shall provide the ability to integrate with other common busniess applications (i.e. Outlook, Excel, etc.)

92 Foundational The system shall provide the ability to export/download a user selected data grid/summary screen (i.e.

dashboard or quick view/screen) into common file formats (i.e. PDF, Excel, etc)

KPP 03 93 Foundational Interoperability The system shall be compliant with DoDI 8330.01 Interoperability of information Technology, Including National Security Systems.

KSA 02 94 Foundational Business Process Workflow Automation

The system shall provide the ability to customize workflow processes to automate agency‐defined business rules and align with the current version of the DoD BEA.

KSA 03 95 Foundational Defined User Roles The system shall provide the ability to assign and manage roles based on organization, division, branch, country, service, case and line.

KSA 05

Foundational Alerts and Notifications The system shall include a centralized error detection and automated correction process, based on defined business rules, including a list of corrections made for audit and/or alerts/notifications to end users.

KSA 01 97 Foundational LPRD The system shall provide the ability to implement system changes based on changes to applicable laws, policies, regulations, and directives (LPRDs).

KSA 04 98 Foundational Interface The system shall provide the ability to interface with systems in accordance with the OV‐3: Operational Resource Flow Matrix and Information Exchange Requirements.

KPP 01 99 Foundational Compliance The system shall include shared data that provides full enterprise visibility of the case lifecycle and that is 100% compliant with DSCA/DoD established data standards or a waiver/transition plan is approved.

Attachment 004‐FMS‐ACES RML ‐ RTM 2

Requirement ID Core Capability Category (where applicable) FMS‐ACES Requirement Statement

100 Non‐Functional Technical Compliance The system shall be compliant with CJCSI 6211.02D (DISN) as implemented by the DISA DISN Connection Process Guide.

Non‐Functional Technical Cyber

The system shall provide the ability to incorporate Public Key Infrastructure (PKI), Public Key Cryptography (PKC) and Secure Sockets Layer (SSL) to enable secure authentication, log‐on, and encrypted transmission of sensitive data to client workstations in accordance with published DoD policy and procedures.

102 Non‐Functional Technical Cyber The system shall provide the ability to monitor all system logs to identify anomalies in data, data volume, account status, rejects, etc.

103 Non‐Functional Technical Cyber The system shall provide the ability to support DoD‐approved Antivirus protection with automatic update ability.

104 Non‐Functional Technical Cyber The system shall be compliant with DODI 8510.01 (Risk Management Framework for DoD Systems).

105 Non‐Functional Technical Cyber The system shall be compliant with applicable DoD STIGS.

106 Non‐Functional Technical Cyber The system shall be compliant with DoDD 8500.1.

107 Non‐Functional Technical Performance The system shall provide the ability to simultaneously process 1.7 million online transactions, including transactions submitted via system interface, in real time or batch process in 5 hours.

108 Non‐Functional Technical Data Quality The system shall provide the ability for system administrators to restart failed or incomplete batch jobs without creating duplicate records.

109 Non‐Functional Technical Performance The system shall provide the capacity to complete all required processing within the specified batch processing window and report on the system performance to this requirement

110 Non‐Functional Technical Performance The system shall provide the ability to have a response times of less than 5 seconds for all screens/queries..

Screens requiring more than 10 seconds should be tuned to the extent technically feasible.

111 Non‐Functional Technical Compliance The system shall be compliant with DoDI 8410.02 Support to DoD Information Network Operations

112 Non‐Functional Technical Compliance The system shall be compliant with DoDD 8320.02 CE‐01 Sharing Data, Information, and Information Technology (IT) Services in the Department of Defense or its superseding guidance

113 Non‐Functional Technical Compliance The system shall support compliance with DA and DoD requirements in a commercial cloud configuration, and the National Institute of Standards and Technology Special Publication 800‐145, September 2011.

114 Non‐Functional Technical Compliance The system shall ensure uninterrupted service during demand spikes to maintain performance, with a focus on cost‐effectiveness.

115 Non‐Functional Technical Compliance The system shall be compliant with FEDRAMP+ security controls and DoD Cloud Computing Security Requirements Guide (SRG) cloud security information impact level (IL) 4 security controls.

116 Non‐Functional Technical Compliance The system shall provide capabilities that are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., tablets, laptops).

117 Non‐Functional Technical Compliance The system shall provide the ability to limit a user's access to data and reports at the organizational level required with a level of accuracy that meets or exceeds industry standards (e.g., a 99.9% level of accuracy).

118 Non‐Functional Technical Compliance The system shall provide a 508 compliant or certified exempt, client, or Web‐based user interface.

119 Non‐Functional Technical System Availability The system shall provide a mission availability rate of 98%.

120 Non‐Functional Technical Performance The system shall have at least a 98% probability of operating over a 72 hour period without an Essential Function Failure (EFF).

121 Non‐Functional Technical Performance The system shall ensure a mean time between failures (MTBF) of greater than 4 weeks, and a mean time to repair (MTTR) of less than 2 hours.

Non‐Functional Technical Compliance

The system shall comply with all Information Assurance requirements as defined in the FMS‐ACES program guidance for DoD, Army, and National Institute of Standards and Technology (NIST) Policy, Guidance, and Directives.

123 Non‐Functional Technical Disaster Recovery The system shall provide a backup and disaster recovery ability.

Non‐Functional Technical Disaster Recovery

The system shall provide recovery of full capabilities within 24 hours of the official declaration of a disaster (e.g. loss of the primary data center), to include reestablishment of critical system interfaces, to a state not more than 4 hours prior to disaster Recovery Point Objective (RPO).

125 Non‐Functional Technical Compliance The system shall be compliant with the US Army Cloud Plan.

126 Non‐Functional Technical Compliance

The system shall be compliant with information confidentiality, integrity, and availability ratings of Moderate/Moderate/Moderate or lower in accordance with Federal Information Processing Standards (FIPS) 199 and National Institute of Standards and Technology (NIST) SP 800‐200.

127 Non‐Functional Technical Compliance

The system shall be compliant with applicable Office of Management and Budget (OMB) memorandums as they relate to Executive Order 14028 (e.g., M‐21‐31 Minimum Logging Standards, M‐22‐09 Federal Zero Trust Architecture Strategy, M‐22‐18 Third Party Secure Software Development Self Attestations).

128 Non‐Functional Technical Compliance The system shall be able to authenticate a user at Authenticator Assurance Level (AAL) 2 and Identity Assurance Level (IAL) 2 in compliance with NIST SP 800‐63, 800‐63A, and NIST 800‐63B.

129 Non‐Functional Technical Compliance The system shall be compliant with DoDI 8520.02 Public Key Infrastructure (PKI) and Public Key (PK) Enabling

130 Non‐Functional Technical Compliance The system shall be complaint with NIST 800‐53 Security and Privacy Controls for Information Systems and Organizations

131 Non‐Functional Technical Compliance The system shall be compliant with the Standard Financial Information Structure (SFIS) financial standard

The system shall be compliant with the Financial Improvement and Audit Readiness (FIAR)/Federal Information System Controls Audit Manual (FISCAM) financial standards

133 Non‐Functional Technical Compliance The System shall leverage the Army Identity, Credential, and Access Management (ICAM) solution in support of a Zero Trust security model.

134 Non‐Functional Technical Interoperability The system shall be compliant with DoDI 8330.01 Interoperability of information Technology, Including National Security Systems.

135 Non‐Functional Technical Data Migration The system shall provide the ability to accept and load legacy data for conversion.

136 Non‐Functional Technical Compliance The system shall be compliant with the Defense Logistic Manual DLM 4000.24 (all volumes) as directed in DoDD 8190.01E

Non‐Functional Technical

Audit

The system shall provide the ability to maintain an audit trail of systemic and manual changes to data after it has been commmitted. The audit information shall include the ID of the individual (or indication of systemic) making the change, the IP address from which the change was made, the date‐time group (DTG) of the change, what field/record was changed, type of change (add, modify, delete), what it was changed from, and what it was changed to.

138 Non‐Functional Technical Data Management The system shall provide the ability to retain and archive case and related information for the appropriate amount of time IAW DoD/Army data retention policies.

KSA 06 139 Non‐Functional Technical Performance The system shall provide the ability to simultaneously process 1.7 million online transactions, including transactions submitted via system interface, in real time or batch process in 5 hours.

KPP 02 140 Non‐Functional Technical Compliance The system shall be compliant with the US Army Cloud Plan.

KSA 07 141 Non‐Functional Technical Reliability, Availability, and Maintainability

The system will ensure a availability rate that adheres to the systems Reliability, Availability, and Maintainability standards.

Attachment 004‐FMS‐ACES RML ‐ RTM 3

Requirement ID Core Capability Category (where applicable) FMS‐ACES Requirement Statement

Non‐Functional Technical

Audit readiness & Compliance

The system shall provide the ability to archive and remove from the active data repository cases and related information from FMS‐ACES that exceed NARA and DA as well as the ability to retrieve and restore archived data into FMS‐ACES for the purpose of research and responses to official RFIs.

143 Non‐Functional Technical Audit readiness & Compliance The system shall be compliant with the Federal Financial Management Improvement Act (FFMIA) as applicable to Security Assistance

Non‐Functional Technical

Audit readiness & Compliance

The system shall be compliant with the most current versions of the Security Assistance Management Manual (SAMM) and shall provide the ability for system administrators to make changes to FMS‐ACES system configurations to reflect changes in the SAMM.

145 Non‐Functional Technical Audit readiness & Compliance The system shall be compliant with the most current versions of USSGL guidance and libraries

Non‐Functional Technical

Audit readiness & Compliance

The design shall ensure that standard line of accounting (SLOA) is perpetuated from the initiating transaction (DLMS requisition, non‐DLMS reimbursable funding document, or contract procurement document) and cannot be altered once funds are committed.

Non‐Functional Technical

Audit readiness & Compliance

The system shall provide a transaction level audit table that captures time and data of changes, user id making changes, IP address from where changes were made, the location of the data element being changed, what it was changed from, and what it was changed to. System administrators will be able to access the data in the transaction table in read only mode to review and audit changes to FMS‐ACES data.

148 Non‐Functional Technical Interface The system shall provide the ability to interface with financial systems of record (SOR).

149 Non‐Functional Technical Interface The system shall provide the ability to inferface with logistics systems of record (SOR).

150 Non‐Functional Technical Interface The system shall provide the ability to interface with DoD reporting systems of record (SOR).

151 Non‐Functional Technical Interface The system shall provide the ability to interface with DoD enterprise analytical platforms and data warehouses.

152 Non‐Functional Technical Data The system shall align with the guidance and policies established for the Army Data Mesh Framework.

153 Non‐Functional Technical Data The system shall comply with the Army's Universal Data Reference Architecture (UDRA).

154 Non‐Functional Technical Document Management The system shall provide the ability to generate and automatically populate Government form templates and preserve completed forms as a PDF.

Attachment 004‐FMS‐ACES RML ‐ RTM 4

Capability Description

Case Initiation (A)

The Case Initiation Capability Area consists of a group of interfaces and data received from the Case Development system of record (DSAMS ‐ Defense Security Assistance Management System) that provide legal and regulatory authorizations.

‐ Create Case Master Records ‐ Track Letter of Offer and Acceptance (LOA), Amendments, and Modifications from proposed to offered status

Case Implementation

The Case Implementation Capability Area consists of case and line/subline level baseline data, including financial and logistical controls which are used to manage case execution and enables the tracking of cost/schedule/performance.

‐ Initiates the case execution process ‐ Emergency Implementation

Logistics Execution

The Logistics Execution Capability Area consists of a set of procedures for creating, processing, updating, and tracking Requisitions (aka Customer Orders), maintain current and accurate statuses of shipments, and documenting receipt of requested goods.

These procedures provide a single comprehensive logistical status of each customer's order across the domestic supply systems.

‐ Initiating requisitions ‐ Managing requisitions: Supply Status, Shipment Status, Modifications and Cancellations ‐ Managing Special Processes: Cooperative Logistics Supply Support Arrangement (CLSSA) Program, Supply Discrepancy Reports (SDR) etc.

Financial Execution

The Financial Execution Capability Area consists of procedures for requesting distribution of funds, managing Interfund (Direct Cite) / Non‐Interfund (Centralized) billing, reporting these transactions to financial databases, and managing and reporting performance and fund status to Defense Integrated Financial System (DIFS).

‐ Case/Line Funding ‐ Customer Billing (interfund and non‐interfund)

Case Lifecycle

The Case Lifecycle Management Capability Area consists of a series of procedures and status reports to manage case execution and measure performance. Major procedures include Case Execution Performance, Case Management Alerts, Case Master Plan, Case Review, and Case Requisition Review.

‐ C1 (major item) Delivery Reporting ‐ Centralized Error Correction Activities

Case Closure

The Case Closure Capability Area consists of a series of procedures and reports to manage the FMS Case Closure program at case, line/subline, and requisition level. These procedures assign case / line closure responsibilities, prioritize workload based on the overall position of the case, and track closure progress with visibility to all key stakeholders. These procedures allow logistics review, financial reconciliation, and line certification as each line becomes supply service complete (SSC) throughout case execution.

‐ Case/Line Certification ‐ Interim to Final Certification

Attachment 004‐ RML ‐ Capability Descriptions 1

Interface

ID

System of Record (SOR) File

Format Count

Interface Type Interface Direction Periodicity

1 Advancing Analytics (ADVANA) 1 FTP via DISA SFG/SFTP One Way (To ADVANA) Weekly 2 Army Enterprise Systems Integration Program (AESIP) 3 FTP via DISA SFG/SFTP One Way (To FMS‐ACES) Daily 3 Defense Automated Addressing System (DAAS) 2 FTP via DISA SFG Bi‐Directional Daily 4 Defense Automated Addressing System Inquiry (DAASINQ) 2 FTP via DISA SFG Bi‐Directional Daily 5 Defense Agencies Initiative (DAI) 2 FTP via DISA SFG Bi‐Directional Daily 6 Defense Integrated Financial System (DIFS) 13 FTP via DISA SFG/API Bi‐Directional Daily, Semi‐Monthly, Monthly, Quarterly 7 Defense Logistics Information Service (DLIS) 3 FTP via DISA SFG/API Bi‐Directional Daily, Quarterly 8 Defense Logistics Agency Disposition Services (DLA DS) 2 FTP via DISA SFG/API Bi‐Directional Daily 9 Defense Security Assistance Management System (DSAMS) 7 FTP via DISA SFG Bi‐Directional Daily 10 Defense Security Cooperation Agency System 1000 (DSCA System 1000) 2 FTP via DISA SFG One Way (To DSCA System 1000) As Required 11 General Fund Enterprise Business System (GFEBS) 5 FTP via DISA SFG Bi‐Directional Daily 12 Invoicing, Receipt, Acceptance, and Property Transfer (IRAPT) 2 FTP via DISA SFG/SFTP Bi‐Directional As Required, Daily 13 Logistics Data Analysis Center (LDAC) 1 SFTP One Way (To FMS‐ACES) Monthly 14 Logistics Multiple Asset Integrated Tracking (LogMAIT) 2 SFTP Bi‐Directional Daily 15 Operational Data Store (ODS) 2 FTP via DISA SFG Bi‐Directional Weekly, Monthly 16 Project Office, Program Executive Office (PEO) for Missiles and Space (PEO M&S) 1 FTP via DISA SFG One Way (To PEO M&S) Daily 17 Program Budget and Accounting System – Order Control (PBAS‐OC) 15 SFTP Bi‐Directional Daily, Monthly 18 Security Cooperation Information Portal (SCIP) 4 FTP via DISA SFG Bi‐Directional Daily 19 Simplified Non‐Standard Acquisition Program (SNAP) 2 FTP via DISA SFG/API Bi‐Directional Daily 20 Standard Army Publication System (STARPUBS) 7 FTP via DISA SFG/API Bi‐Directional Daily, Weekly, Monthly 21 Tank‐automotive and Armaments Command (TACOM) 4 FTP via DISA Bi‐Directional Daily 22 U.S. Air Force Security Assistance Center (AFSAC) ‐ AFSAC Online (AOL) 2 SFTP Bi‐Directional Daily 23 United States Army Corps of Engineers (USACE) 2 SFTP Bi‐Directional Daily 24 Virtual Contracting Enterprise (VCE) 2 SFTP Bi‐Directional Daily 25 Web Supply Discrepancy Report (WEBSDR) 2 FTP via DISA SFG Bi‐Directional Daily

Attachment 004‐ RML ‐ Interface Details 1

Reqt # Requirement Systems of Record

The system shall provide the ability to interface with financial systems of record (SOR). Defense Agencies Initiative (DAI) Defense Integrated Financial System (DIFS) General Fund Enterprise Business System (GFEBS) Operational Data Store (ODS) Program Budget and Accounting System – Order Control (PBAS‐OC)

The system shall provide the ability to inferface with logistics systems of record (SOR). Army Enterprise Systems Integration Program (AESIP) Defense Automated Addressing System (DAAS) Defense Automatic Addressing System Inquiry (DAASINQ) Defense Logistics Information Service (DLIS) Defense Logistics Agency Disposition Services (DLA DS) PEO M&S (Missile and Space) Logistics Data Analysis Center (LDAC) Logistics Multiple Asset Integrated Tracking (LogMAIT) Simplified Non‐Standard Acquisition Program (SNAP) Standard Army Publication System (STARPUBS) Tank Automotive and Armaments Command (TACOM) U.S. Air Force Security Assistance Center (AFSAC) ‐ AFSAC Online (AOL) United States Army Corps of Engineers (USACE) Virtual Contracting Enterprise (VCE) Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) Web Supply Discrepancy Report (WEBSDR)

The system shall provide the ability to interface with DoD reporting systems of record

(SOR).

Defense Security Assistance Management System (DSAMS) Defense Security Cooperation Agency System 1000 (DSCA System 1000) Security Cooperation Information Portal (SCIP)

The system shall provide the ability to interface with DoD enterprise analytical platforms and data warehouses.

Advancing Analytics (ADVANA)

The system shall provide the ability to interface with Systems of Record (SOR) within the DoD.

Update Date: 30 AUG 2023

Attachment 004 ‐ RML Interface Requirements 1

File Format Count: The number of unique file formats exchanged between FMS‐ACES and the external SOR or Agency. Under the legacy system, all interfaces are conducted via file transfer. Future state FMS‐ACES will leverage real‐time or near real‐time interface exchanges to the extent possible.

Interface Type: How information is currently exchanged between the legacy system and external systems and agencies API ‐ Application Programming Interface; provides the capbility for real‐time processing FTP ‐ File Transfer Protocol SFTP ‐ Secure File Transfer Protocol

Interface Direction: Indicates the direction in which the information travels. Specifies the sender and receiver of transferred data.

Bi‐Directional ‐ both systems in the relationship send and receive data One Way (To XXXX) ‐ information is relayed in only one direction, the receiving system is called out in the parenthesis.

Periodicity: The frequency with which information (file formats) are exchanged between two systems. Interfaces with more than one periodicity indicate different file formats are transferred at different rates.

Attachment 004 ‐ RML Interface Definitions 1

LAWS Where to find Title 22 United States Code Chapter 39, Arms Export Control Act (AECA), Section 21 (m) https://uscode.house.gov

Public Law 104‐164: Amendment to the Foreign Assistance Act and the AECA https://uscode.house.gov

Public Law 101‐576: Chief Financial Officers Act of 1990 (CFO) https://uscode.house.gov Senate Report 104‐339: Federal Financial Management Improvement Act of 1996 (FFMIA) https://congress.gov

Public Law 97‐255: Federal Managers Financial Integrity Act of

1982 (FMFIA)

https://uscode.house.gov

Title 22 United States Code, Section 2151: Foreign Assistance Act of 1961 (FAA) https://uscode.house.gov

Title 15 United States Code, Chapter 96: Global and National Commerce Act (ESIGN Act) https://uscode.house.gov

POLICIES Where to find https://samm.dsca.mil/ (found in policy memos)

REGULATIONS Where to find AR 25‐30, Army Catalog of Publications/blank forms https://armypubs.army.mil AR 725‐1, Special Authorization and Procedures for Issues, Sales, ahttps://armypubs.army.mil

AR 725‐50, Requisitioning, Receipt and Issue System (Ch 11) https://armypubs.army.mil DFAS‐IN Regulation 37‐100 https://www.asafm.army.mil DOD 7000.14‐R, Administrative Control of Funds and Anti‐ deficiency Act https://comptroller.defense.gov

USASAC Reg 725‐10

DIRECTIVES Where to find CCOPES Manual CISIL Manual

DLM 4000.25, Defense Logistics Management Standards https://www.dla.mil/Defense‐Data‐ Standards/Publications/

DoDD 5230.24, Distribution Statements on Technical Documents https://www.esd.whs.mil/

DoDI 5230.24, Distribution Statements https://www.esd.whs.mil/ DoDD 4000.25‐7‐S1, Fund Code Supplement to MILSBILLS Inactive

DSCA Handbook 7003, MASL Handbook https://www.dsca.mil/sites/default/files/masl_han dbook_formatted_0.pdf

Homeland Security Presidential Directive 12, Identity, Credential and Access Management (ICAM) https://www.dhs.gov/homeland‐security‐ presidential‐directive‐12

DoDD 5105.65, Defense Security Cooperation Agency (roles and rehttps://www.esd.whs.mil/

DSCA Policy 21‐07, Standard Financial Information Structure Implementation Policy

AR 12‐1, Security Assistance and International Logistics: Security Assistance Training, Export, and Policy https://armypubs.army.mil

DoD 5105.38‐M, Security Assistance Management Manual https://samm.dsca.mil

Attachment 004‐ RML ‐ LRPDs

Acronym Full Name Additional Information (where applicable) A&T Administrative and Technical AA&E Arms, Ammunition and Explosives AAC Acquisition Advice Code ABAA Appropriation and Budget Activity Account ACAT Acquisition Category ACC Army Contracting Command ACCP Accelerated Case Closure Procedures/Program ACCT IND Accounting Systems Indicator ACES‐FMS Army Case Execution System for Foreign Military Sales ACH Army Combat Helmets ACOTA Africa Contingency Operations Training and Assistance ACQ Acquisition ACRL Accessorial Cost ACSA Acquisition and Cross‐Servicing Agreement ACU Army Combat Uniform ADM Administrative Surcharge AECA Arms Export Control Act AESIP Army Enterprise Systems Integration Program AFRICOM US African Command AFSAC Air Force Security Assistance and Cooperation Directorate AMC Army Materiel Command / Air Mobility Command (USAF) AMCOM Aviation and Missile Command (Army) Located in Huntsville, Alabama, manages missiles, helicopters, and associated equipment.

AMCU Army Multi‐Cam Uniform ANA Afghanistan National Army ANSI American National Standards Institute ANZUS Security treaty between Australia, New Zealand, and the

United States AOD Anticipated Offer Date The time required to respond to an LOR with an LOA depends on the type of case being prepared and the complexity of the program. The policy time frame for a

ARP Acquisition Requirements Package Objective of acquisition package is to assemble all documents needed to acquire supplies or services to satisfy approved requirements in a timely, efficient

ASA(ALT) Assistant Secretary of the Army for Acquisition, Logistics and Technology

ASAE Army Security Assistance Enterprise ASD Assistant Secretary of Defense ASDA Automated State Department Approval ASFF Afghanistan Security Forces Fund (DOD) ASLS Above Standard Leval of Service ATC Authorization to Contact B/L Bill of Lading BAC Billing Advice Code BO Blanket Order BO Back Order (Supply) / Blanket Order (FMS Case) BOE Blanket Open End (FMS Case) BPC Building Partner Capacity C3I Command, Control, Communications, and Intelligence C4I Command, Control, Communications, Computers, and

Intelligence C4ISR Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance CA Cancellation CAD Cartridge Actuated Devices CAGE Commercial and Government Entity Code CAP Connection Approval Procedures CAS Contract Administrative Surcharge CAS Contract Administrative Services / Cost Accounting Standard

CBJ Congressional Budget Justification CBL Commercial Bill of Lading CBO Congressional Budget Office CBW Chemical and Biological Weapons

Attachment 004‐RML ‐ Acronyms 1

CC Country Code / Customer‐Within‐Country (Transportation

Code) CCBL Collect Commercial Bill of Lading CCC Common Criteria Certification CCM Central Case Manager (Army) / Command Country Manager CCOPES Case Close Out Process Execution System CCSA Case Closure Suspense Account CDA Case Development Analyzer CDM Case Development Module (DSAMS) CDMA Case Development Modernization Analysis CDRL Contract Data Requirements List CE Case Execution CEA Case Execution Analyzer CECOM Communications ‐ Electronics Command (Army) Located at Aberdeen Proving Ground, Maryland, is responsible for the Army’s communications and CEFMS Corps of Engineers Financial Management System CEMI Case Execution Modernization Initiative CENTCOM US Central Command CEPS Case Evaluation Profile System CIIC Controlled Inventory Item Code CISIL Centralized Integrated System for International Logistics

(Army) CLA Classified Items CLIN Contract Line Item Number CLMS Case Lifecycle Management Suite CLRS Case Line Requisition SDR (Supply Discrepancy Report) CLSSA Cooperative Logistics Supply Support Arrangement CMO Contract Management Office CMR Case Management Review CN Counter Narcotics COCOM Combatant Command COE US Army Corps of Engineers COMRI Communication Routing Identifier COP Common Operating Picture COR Contracting Officer’s Representative COTS Commercial Off‐the‐Shelf CPD Congressional Presentation Document (obsolete, see CBJ) CPM Country Program Manager Individual responsible for overseeing case development and execution for all cases of a given country CPO Chief Performance Office CRD Contract Required Date Date the contract must be awarded in order to meet the

Required Delivery Date. The Contract Required Date is calculated by subtracting procurement leadtime from the

CRR Case Requisition Review CRSP Coalition Readiness Support Program CRUD Create, Read, Update, Delete CSCS Capital Security Cost Sharing CSF Coalition Support Fund CSP Concurrent (or initial) Spare Parts CTA Country Team Assessment CVC Combat Vehicle Crewman CWD Case Writing Division (DSCA) DSCA’s Case Writing Division (CWD) is to review all LOAs for consistent policy application. As such, the responsibility for providing accurate data in developing line prices and payment schedules on an FMS case is the responsibility of the IAs. The CWD has the responsibility of reviewing the price and payment schedule data for

CWP Coalition Warfare Program DAAS Defense Automatic Addressing System DAI Defense Agencies Initiative DAI accounting system used by MDA DAMES DLA Automated Message Exchange System DAPS Defense Automation and Production Service DASA DE&C Secretary of the Army for Defense Exports and Cooperation DASA‐DEC Deputy Secretary of the Army for Defense Exports and

Cooperation

Attachment 004‐RML ‐ Acronyms 2

DCA Defense Cooperation in Armaments DCAA Defense Contract Audit Agency DCC Direct Commercial Contract (also DCS) DCMA Defense Contract Management Agency DCMA Defense Contract Management Agency DCS Direct Commercial Sales (also DCC) DD Form 1513 Department of Defense Letter of Offer and Acceptance

(obsolete) DD Form 2285 Invitational Travel Order for International Military Student DD Form 250 Department of Defense Material Inspection and Receiving

Report DD Form 2875 System Authorization Access Request DD Form 645 Department of Defense FMS Quarterly Billing Statement DDN Defense Data Network DDTC Directorate of Defense Trade Control (DOS) DEPMED Deployable Medical Container DEPSECDEF Deputy Secretary of Defense DFARS Defense Federal Acquisition Regulation Supplement DFAS Defense Financial Accounting System DFAS‐IN Defense Finance and Accounting Service‐Indianapolis Center

DIACAP DOD Information Assurance Certification and Accreditation Process

DIC Document Identifier Code DIFS Defense Integrated Financial System DISA Defense Information Systems Agency DISAM Defense Institute of Security Assistance Management DISN Defense Information Systems Network DLA Defense Logistics Agency

DLATS

Defense Logistics Agency Transation Services Likely outdated term, was replaced by Defense Automated Adressing System (DAAS)

DLI Defense Language Institute DLIELC Defense Language Institute English Language Center (Lackland

AFB, TX)

DLIFLC Defense Language Institute Foreign Language Center (Presidio of Monterey, CA) DLIS Defense Logistics Information Service (DLA) DLMS Defense Logistics Management Standards a broad base of business rules designed to meet DoD's requirements for logistics support. The DLMS are developed in collaboration with the Military Departments, Defense Agencies, and participating Federal Agencies to accommodate the old DoD-unique logistics data exchange standards and processes commonly referred to as the "MILS" (Military Standard), plus new information exchange requirements supporting modernization. DLMS transactional exchanges are founded in American National Standards Institute (ANSI) chartered Accredited Standards Committee (ASC) X12 commercial standards and support

DLSC Defense Logistics Supply Center DO Defined Order (FMS Case) DoD Department of Defense DODAAC Department of Defense Activity Address Code DPAP Defense Procurement and Acquisition Policy DSADC Defense Security Assistance Development Center DSAMS Defense Security Assistance Management System DSAMS‐CDM DSAMS Case Development Module DSAMS‐TM Defense Security Assitance Management System ‐ Training

Module DSC Delivery Source Code

DSCA Defense Security Cooperation Agency DSCA Defense Security Cooperation Agency DSCA IM&T Defense Security Cooperation Agency Information

Management and Technology

Attachment 004‐RML ‐ Acronyms 3

DTC Delivery Term Code

DTR Defense Transportation Regulation, DOD 4500.9‐R DTS Defense Transportation System / Defense Travel System DU Dependable Undertaking DWCF Defense Working Capital Fund DWCF Defense Working Capital Fund (see WCF) DX Direct Exchange (Army) E/I End Item EA Expenditure Authority / Each EAA Export Administration Act of 1979 EACC Enhanced Accelerated Case Closure EAL Evaluation Assurance Level EBS Enterprise Business System (ERP) EDA Excess Defense Articles EDI Electronic Data Institute EEUM Enhanced End Use Monitoring EFF Essential Function Failure EFTS Enhanced Freight Tracking System E‐IMET Expanded International Military Education and Training

Program EIPC Enhanced International Peacekeeping Capabilities EOPDB Equipment Oriented Publication Data Base EPPA Enhanced Partnership with Pakistan Act ERGT Expeditionary Requirement Generation Team ERP Enterprise Resource Planning ESAPI Enhanced Small Arms Protective Insert ESD Estimated Shipment Date ESN Essential Item EUCOM US European Command EUM End‐Use Monitoring FAA Foreign Assistance Act of 1961 FAD Force Activity Designator FAR Federal Acquisition Regulation FCMS Financial Case Management System FDPO Foreign Disclosure Policy Office FDR/ER Foreign Disaster Relief/Emergency Response FDS Foreign Disclosure System FED LOG Federal Logistics Data FEDRAMP+ Federal Risk and Authorization Management Program FF Freight Forwarder FIAR Financial Improvement and Audit Readiness FICS FMS Integrated Control System FIFO First‐in‐First‐out FISCAM Federal Information System Control Audit Manual FK Not an acronym Document identifier for a bill FLIS Federal Logistics Information System FLO Foreign…