Attachment 0004 - FMS-ACES Requirements Master List (RML).xlsx
XLSX spreadsheet 201 KB Posted
- Attached to
- FMS-ACES DRAFT Announcement Federal contract opportunity
- Solicitation number
- W519TC-23-R-ACES
About this file
This document contains an attachment to a federal contract opportunity for the FMS-ACES program. The attachment provides a requirements master list detailing over 200 functional and non-functional requirements for the Foreign Military Sales Army Case Execution System. The requirements cover capabilities related to case initiation and management, logistics execution, financial execution, interfaces, data management, alerts and notifications, document management, and more. They specify requirements for systems of record integration, business process workflow automation, data validation, reporting, and compliance with various laws, policies, regulations and standards. Non-functional requirements address technical, cybersecurity, performance, availability, disaster recovery, audit readiness, and compliance factors. The document organizes the requirements and identifies their associated maps, steps, groups, and status. It also contains supplemental sections on capability descriptions, business rules, acronyms, and applicable directives.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| FMS-ACES Industry Day Attendees POC List.xlsx | XLSX spreadsheet | |
| FMS-ACES - Industry Day Registered Vendor List_2023-09-06.xlsx | XLSX spreadsheet | |
| Attachment 0003 - FMS-ACES Statement of Objectives (SOO).docx | DOCX document | |
| Attachment 0005 - FMS-ACES Operational Views.zip | ZIP file | |
| FMS-ACES OT Announcement and Instructions_DRAFT Final.pdf | ||
| Attachment 0001 FMS-ACES Product Roadmap.xlsx | XLSX spreadsheet | |
| Attachment 0006 FMS-ACES_OTA__Terms_and_Conditionsv02.docx | DOCX document | |
| Attachment 0007 - FMS-ACES_Questions_Comments_TEMPLATE.xlsx | XLSX spreadsheet | |
| Attachment 0002 FMS-ACES COST ROM Template.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Table of Contents
| Table Of Contents | |
| Tab Name | Description |
| RTM - Baseline and Working | 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 |
| Business Rules | A list of Business Rules the system is required to implement. Included are business rules logic, data validation rules, data required to generate reports, specific user access rules, etc. This list is not all encompassing and is intended to provide further context. Business Rules are aligned to Core Capability (Column C) and Category (Column D) where applicable. |
| 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 |
AY_RTM - Working with Children
| KPPs & KSAs | Requirement ID | Core Capability | Proposed Core Capability | Category (where applicable) | Associated Map(s) | Map Step(s) | FMS-ACES Requirement Statement | USASAC Questions/Comments | ||
| 1 | Foundational | Interface | A1, A1.1, A2, A3, B1, B4 | The system shall provide the ability to receive and/or send data via interfaces in accordance with SV-3f and Interface System Agreements (ISAs). | Send/Receive Data via Interfaces | |||||
| 1.01 | A1 | O1.2.5.5.15 | DSAMS interface | **Identify incoming data | ||||||
| 1.02 | A1.1 | O1.2.5.2.20 | DSAMS interface | **Identify incoming data | ||||||
| 1.03 | A2 | O1.2.5.4.4 | DSAMS interface | |||||||
| 1.04 | A3 | O1.2.6.2.8 - DSAMS | ||||||||
| O1.2.6.2.2 - GFEBS/PBAS | DSAMS/GFEBS/PBAS interfaces | **Identify incoming data | ||||||||
| 1.05 | B1 | no step | GFEBS/PBAS interfaces | **Identify incoming data | ||||||
| 1.06 | B1 | O1.3.1.1.23 | Do we interface logistics data back to DSAMS? | **Identify incoming data | ||||||
| 1.07 | B1 | O1.3.1.1.20 | FINIMP Milestone Status from DSAMS | **Identify incoming data | ||||||
| 1.08 | B4 | O1.3.1.3.7 | Implmented Milestone Status from DSAMS | **Identify incoming data | ||||||
| 2 | Foundational | Data | A1, A1.1, A2, A3, B1, B4 | The system shall provide the ability to, when appropriate, systemically create a new and/or populate an existing data strucuture(s) from data received via an interface. | Update data strucutre(s) from interface data | |||||
| 2.01 | A1 | Case Master Record Creation/Update(s) | **Identify what data to store | |||||||
| 2.02 | A1.1 | Case Master Record Creation/Update(s) | **Identify what data to store | |||||||
| 2.03 | A2 | O1.2.5.4.1 | Case Master Record Creation/Update(s) | **Identify what data to store | ||||||
| 2.04 | A3 | O1.2.6.2.1 | Case Master Record Update(s) | **Identify what data to store | ||||||
| B1 | O1.3.1.1.1 | |||||||||
| O1.3.1.1.7 | Case Master Record Update(s) | |||||||||
| 2.05 | B4 | O1.3.1.3.1 | LOA information Case Master Record Update(s) | **Identify what data to store | ||||||
| 3 | Foundational | Data | A1, A1.1, A2, A3, B1, B2, B3, B4, C3.10 | The system shall provide the ability to manually create a new and/or populate an existing data strucuture(s) based upon defined user roles. | CRUD |
Need to confirm if this is actually used in these maps and if so, which steps are associated?
| 3.01 | A1 | Case Master Record Creation/Update(s) | ||||
| 3.02 | A1.1 | Case Master Record Creation/Update(s) | ||||
| 3.03 | A2 | Case Master Record Creation/Update(s) | ||||
| 3.04 | A3 | Case Master Record Update(s) | ||||
| 3.05 | B1 | adjusting values to accommodate interface errors | ||||
| 3.06 | B2 | allow manual update to implemented status (emergency) | ||||
| 3.07 | B3 | allow manual update to implemented status (forced) | ||||
| 3.08 | B4 | Case Master Record Creation/Update(s) | ||||
| 3.09 | C3.10 | Presidential Drawdown Creation/Update(s) associated with RCN provided by the PD EXORD | ||||
| 4 | Foundational | Alerts and Notifications | A3, B1, B4, C3.10 | The system shall provide the capability to compare incoming information from interfaces to identify what information has changed, so a notification/alert may be provided to the end user for review/approval as defined in business rules. | Generate alert/notif from comparison of values coming in on interface. | |
| 4.01 | A3 | *O1.2.6.2.4 | During Case Master Record updates from interfaces, compare incoming FMS case master data and alert/notify appropriate roles of changes found. | **Identify the business rules for which roles to be alerted for which fields, etc. | ||
| 4.02 | B1 | *O1.3.1.1.4 | compare offered info to accepted - G8 compare financial values and notify CCM | **Identify business rules for what needs to be compared and which users should be alerted | ||
| 4.03 | B1 | *O1.3.1.1.10 | G8 compare financial values and notify CCM | **Identify business rules for what needs to be compared and which users should be alerted | ||
| 4.04 | B1 | no step | Alert/Notif to G9 from CCM that OA Disapproval posted in DSAMS ??? and inform CCM of OA Disapproval in DSAMS | is this correct...we would get the notif from the interface? | ||
| 4.05 | B4 | Validate that data structure(s) contain data consistent with implemented LOA | **Identify business rules for data to be compared and who, if anyone, should be alerted | |||
| 4.06 | C3.10 | For Presidential Drawdowns, when specific Presidential Drawdown data changes alert/notify the appropriate roles. | **Identify business rules for data to be stored for PDs and which roles should be alerted | |||
| 5 | Case Initiation | Data | A1 | The system shall provide the capability to systemically determine case type based on data received. | **Need to determine if we already have business rules for determining the case type or not. --this is done in CMA today....so ref those rules...and be sure to add PDs |
Does this show on a current map? Should it?
6 Case Initiation Data C3.10? The system shall provide the capaibility to systemically create the Presidential Drawdown (PD) number with asociated Record Control Number(s) (RCN) provided by PD EXORD. There is no map specific to PDs in A/B so what map do we assoicated? A2?
Isn't this the systemic creation so this should be the ability to read from the PD EXORD PDF and generate???
| 7 | Foundational | Remarks | A1, A1.1, A3 | The system shall provide ability to add remarks to the case master record based on defined user roles. | Remarks on Case Master Record (CMR) | ||||
| 7.01 | A1 | *O1.2.5.5.2 | allow remarks about transpo plan | ||||||
| 7.02 | A1.1 | *O1.2.5.2.22 | |||||||
| *O1.2.5.2.13 | G8/CCM remarks about discrepancies identiifed and resolution(s) | ||||||||
| 7.03 | A1.1 | *O1.2.5.2.4 | |||||||
| *O1.2.5.2.5 | G8 remarks about reivew | ||||||||
| 7.04 | A3 | allow remarks about data eval/correction?? | |||||||
| 8 | Foundational | Review | A1, A1.1, B5 | The system shall provide the capability to automate reviews and evaulations, as much as possible, based upon defined business rules. | Automate Reviews and Evaluations | ||||
| 8.01 | A1 | *O1.2.5.5.13 | Review if case is executable or not based | **Identify business rules to determine that a case is not executable | |||||
| 8.02 | A1 | *O1.2.5.5.14 | Determine if transpo plan is required | **Identify business rules --end stat should be indicator which identifies plan is required. | |||||
| 8.03 | A1.1 | *O1.2.5.2.4 | |||||||
| *O1.2.5.2.5 | Automate Financial/Logistical review of basics, mods, and amends? | **identify the portions of the reviews/evals that can be automated and lay out the business rules. | |||||||
| 8.04 | B5 | *O1.3.1.4.15 | Automate line review to determine if executable or not | ||||||
| 9 | Foundational | A1, A1.1, A3, B1, B2 | The system shall provide the capability to send automated communications (e.g. internal messaging, email, text) based on established business process activity triggers and document templates | Automated communications - email, messaging, etc. | |||||
| 9.01 | A1 | *O1.2.5.5.3 | CCM or autogen email to CPM about case not being executable | ||||||
| 9.02 | A1.1 | *O1.2.5.2.24 | |||||||
| *O1.2.5.2.23 | autogen email informing of discrepancies or no discrepancies | ||||||||
| 9.03 | A1.1 | *O1.2.5.2.3 | CCM takes corrective action email to G8 | ||||||
| 9.04 | A1.1 | *O1.2.5.2.7 | G8 emails to CCM to provide financial concurrence | ||||||
| 9.05 | A1.1 | *O1.2.5.2.29 | CCM informs CPM of no discrepancies (or handle solely through remarks?) | ||||||
| 9.06 | A3 | *O1.2.6.2.5 | Notif to CCM about comparison of "Offered" and "Proposed" data | ||||||
| 9.07 | B1 | *O1.3.1.1.11 | Email to CCM errors found during financial review | ||||||
| 9.08 | B1 | *O1.3.1.1.17 | CCM email to G8 NC that corrections cannot be made - Post OA Disapproval in DSAMS | ||||||
| 9.09 | B2 | no step | G9 emails CCM, CPM, and DSCA that Case is Implemented | ||||||
| 9.1 | B5 | *O1.3.1.4.3 | CCM to notify CPM that line is NOT executable | ||||||
| 10 | Logistics | C1.1, C1.2, C1.3 | The system shall provide the capability to systemically initiate skeletal requisitions for all FMS Case Types based upon defined business rules. | Skeletal or Shell? What is the best word...basically we know the entire requisition cannot/will not be created and 'released' without an end user for reviewing and approving. | |||||
| 11 | Foundational | Document Management | A1, B1, B2, B3, B4 | 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 contained to a specific case, line, requisition, etc. according to user defined user roles. | Ability to associate/attach documents with a case | ||||
| 11.01 | A1 | Correspondence with CPM about Transpo Plan?? (CCM to CPM) | |||||||
| 11.02 | B1 | no step | Receive and store electronic copies of signed letters of acceptance and other documents associated to the case | ||||||
| 11.03 | B2 | *O1.3.1.5.29 | Receive documentation and authority from DSCA (usually via email) for emergency implmentation | ||||||
| 11.04 | B2 | no step | Receive notice of Emergency Implementation (EI) milestone posted in DSAMS | ||||||
| 11.05 | B3 | *O1.3.1.2.11 | Receive and store electronic copies of signed letters of acceptance and other documents associated to the case | ||||||
| 11.06 | B4 | *O1.3.1.3.2 | G8-CCM attach NC Notif of finacial implementation approval??? | ||||||
| 11.07 | B5.1 | *O1.2.5.3.18 | CCM to attach error report received | ||||||
| 12 | |||||||||
| 13 | |||||||||
| 14 | |||||||||
| 15 | |||||||||
| 16 | |||||||||
| 17 | |||||||||
| 18 | |||||||||
| 19 | |||||||||
| 20 | |||||||||
| 21 | |||||||||
| 22 | |||||||||
| 23 | |||||||||
| 24 | |||||||||
| 25 | |||||||||
| 26 | |||||||||
| 27 | |||||||||
| 28 | |||||||||
| 29 | |||||||||
| 30 | |||||||||
| 31 | |||||||||
| 32 | |||||||||
| 33 | |||||||||
| 34 | |||||||||
| 35 | |||||||||
| 36 | |||||||||
| 37 | |||||||||
| 38 | |||||||||
| 39 | |||||||||
| 40 | |||||||||
| 41 | |||||||||
| 42 | |||||||||
| 43 | |||||||||
| 44 | |||||||||
| 45 | |||||||||
| 46 | |||||||||
| 47 | |||||||||
| 48 | |||||||||
| 49 | |||||||||
| 50 | |||||||||
| 51 | |||||||||
| 52 | |||||||||
| 53 | |||||||||
| 54 | |||||||||
| 55 | |||||||||
| 56 | |||||||||
| 57 | |||||||||
| 58 | |||||||||
| 59 | |||||||||
| 60 | |||||||||
| 61 | |||||||||
| 62 | |||||||||
| 63 | |||||||||
| 64 | |||||||||
| 65 | |||||||||
| 66 | |||||||||
| 67 | |||||||||
| 68 | |||||||||
| 69 | |||||||||
| 70 | |||||||||
| 71 | |||||||||
| 72 | |||||||||
| 73 | |||||||||
| 74 | |||||||||
| 75 | |||||||||
| 76 | |||||||||
| 77 | |||||||||
| 78 | |||||||||
| 79 | |||||||||
| 80 | |||||||||
| 81 | |||||||||
| 82 | |||||||||
| 83 | |||||||||
| 84 | |||||||||
| 85 | |||||||||
| 86 | |||||||||
| 87 | |||||||||
| 88 | |||||||||
| 89 | |||||||||
| 90 | |||||||||
| 91 | |||||||||
| 92 | |||||||||
| 93 | |||||||||
| 94 | |||||||||
| 95 | |||||||||
| 96 | |||||||||
| 97 | |||||||||
| 98 | |||||||||
| 99 | |||||||||
| 100 | |||||||||
| 101 | |||||||||
| 102 | |||||||||
| 103 | |||||||||
| 104 | |||||||||
| 105 | |||||||||
| 106 | |||||||||
| 107 | |||||||||
| 108 | |||||||||
| 109 | |||||||||
| 110 | |||||||||
| 111 | |||||||||
| 112 | |||||||||
| 113 | |||||||||
| 114 | |||||||||
| 115 | |||||||||
| 116 | |||||||||
| 117 | |||||||||
| 118 | |||||||||
| 119 | |||||||||
| 120 | |||||||||
| 121 | |||||||||
| 122 | |||||||||
| 123 | |||||||||
| 124 | |||||||||
| 125 | |||||||||
| 126 | |||||||||
| 127 | |||||||||
| 128 | |||||||||
| 129 | |||||||||
| 130 | |||||||||
| 131 | |||||||||
| 132 | |||||||||
| 133 | |||||||||
| 134 | |||||||||
| 135 | |||||||||
| 136 | |||||||||
| 137 | |||||||||
| 138 | |||||||||
| 139 | |||||||||
| 140 | |||||||||
| 141 | |||||||||
| 142 | |||||||||
| 143 | |||||||||
| 144 | |||||||||
| 145 | |||||||||
| 146 | |||||||||
| 147 | |||||||||
| 148 | |||||||||
| 149 | |||||||||
| 150 | |||||||||
| 151 | |||||||||
| 152 | |||||||||
| 153 | |||||||||
| 154 | |||||||||
| 155 | |||||||||
| 156 | |||||||||
| 157 | |||||||||
| 158 | |||||||||
| 159 | |||||||||
| 160 | |||||||||
| 161 | |||||||||
| 162 | |||||||||
| 163 | |||||||||
| 164 | |||||||||
| 165 | |||||||||
| 166 | |||||||||
| 167 | |||||||||
| 168 | |||||||||
| 169 | |||||||||
| 170 | |||||||||
| 171 | |||||||||
| 172 | |||||||||
| 173 | |||||||||
| 174 | |||||||||
| 175 |
RTM - Baseline - 20 JUL 2023
| 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 upon defined business rules. | |
| 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 Country Case or Line based upon defined user roles. | |
| 13 | Logistics | Processing | The system shall provide the ability to calculate an average monthly demand for each NIIN determined to be included in the CLSSA forecast process. | |
| 14 | Logistics | The system shall provide the capability to systemically create the Publication requisition based upon uploaded DD 4569 form. | ||
| 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 updated manually or systemically. | ||
| 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) based upon defined business rules. | ||
| 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 business rules. | ||
| 20 | Logistics | The system shall provide the capability to send a request to cancel requisitions validated by source of supply based upon defined business rules. | ||
| 21 | Logistics | The system shall provide the capaibility to systemically create a Supply Discrepancy Report (SDR) ingested by scanning pdf of SF364. | ||
| 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 value is less than $1 based upon defined business rules. | ||
| 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 Improved Item'. | |
| 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 according to defined business rules. | |
| 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 rules. | |
| 37 | Financial Execution | Processing | The system shall provide the ability to receive and process case, line/subline, and requisition funding data in accordance with defined business rules. | |
| 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 used for producing the Quarterly Billing Statement DD Form 645 | |
| 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 centralized error correction activities. | |
| 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 SCMS and the EUM database (PL 1225/1228 compliance). | |
| 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 Interface System Agreements (ISAs). | |
| 57 | Foundational | Data | The system shall provide the ability to, when appropriate, systemically create a new and/or populate an existing data strucuture(s) from data received via an interface. | |
| 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, Track Contracting Milestones, ACC Contracting Action] | |
| 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 rules. | |
| 60 | Foundational | Remarks | The system shall provide ability to add remarks to the case, line/subline, requisition, and SDR levels based on defined user roles. | |
| 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. according to user defined user roles. | |
| 64 | Foundational | Data Management | The system shall provide the ability to CRUD reference tables based on defined user roles. [i.e. CCOPES Inhibitor copes, CMA Reason Codes, etc] | |
| 65 | Foundational | Interface | The system shall provide the ability to systematically prioritize and process incoming transactions based on defined and configurable business rules. | |
| 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, country, service, case and line/subline. |
| 68 | Foundational | Query/Report | The system shall provide the ability to view and query database audit information via the user interface based upon defined user roles. | |
| 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 availability. | |
| 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.)
• Text prediction ability for search, help, 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 to add/remove columns/data shown). Individual views of data (like Quick Views) should be interactive and provide the capabilty to drill down into related data.
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
- Report recycled 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 systemic (systamatic?) corrections made for audit and/or alerts/notifications to end users. |
| 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 | 96 | 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. |
| 100 | Non-Functional Technical | Compliance | The system shall be compliant with CJCSI 6211.02D (DISN) as implemented by the DISA DISN Connection Process Guide. | |
| 101 | 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 provide automatic provisioning to dynamically scale capacity during demand spikes to maintain performance and decrease capacity during lulls to reduce costs. | |
| 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. | |
| 122 | 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. | |
| 124 | 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 | |
| 132 | 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 | |
| 137 | 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. |
| 142 | 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 | |
| 144 | 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 | |
| 146 | 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. | |
| 147 | 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. |
Capability Descriptions
| Capability | Description |
| Case Initiation (A) | The case/line level baseline data, including financial and logistical controls which are used to manage case execution and track the cost/schedule/performance. It also initializes the counts and values which will be used to track/summarize the execution process. |
| Case Implementation | A group of interfaces and data received from the Case Development system of record (DSAMS - Defense Security Assistance Management System) that provide the legal and regulatory authorizations to begin fulfilling the requirements of the Letter of Offer and Acceptance (LOA). |
| Logistics Execution | 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 system. |
| Financial Execution | Procedures for distributing 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. |
| Case Lifecycle | 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. |
| Case Closure | A series of procedures and reports to manage the FMS Case Closure program at case, requisition, and line 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. |
Interface Details
| 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 | Joint Munitions Command (JMC) | 1 | FTP via DISA SFG/API | One Way (To JMC) | 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 |
| 26 | Wide Area Work Flow (WAWF) | 2 | FTP via DISA SFG/SFTP | Bi-Directional | As Required, Daily |
Page &P of &N
Interface Requirements
| Reqt # | Requirement | Systems of Record |
| The system shall provide the ability to interface with Systems of Record (SOR) within the DoD. | ||
| 175 | 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) 176 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) Joint Munitions Command (JMC)* 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) U.S. Air Force Security Assistance Center (AFSAC) - AFSAC Online (AOL) Virtual Contracting Enterprise (VCE) Wide Area Work Flow (WAWF) Web Supply Discrepancy Report (WEBSDR) 177 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) 178 The system shall provide the ability to interface with DoD enterprise analytical platforms and data warehouses. Advancing Analytics (ADVANA)
* (May become a user versus an interface)
AIE Requirements Traceability Matrix (RTM) Baseline v1.0
15 JUN 2018
&P of &N
Interface Definitions 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.
Page &P of &N
LRPDs
| 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 |
| DSCA Policy 21-07, Standard Financial Information Structure Implementation Policy | 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, and Loans | https://armypubs.army.mil |
| AR 12-1, Security Assistance and International Logistics: Security Assistance Training, Export, and Policy | https://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/ |
| DoD 5105.38-M, Security Assistance Management Manual | https://samm.dsca.mil |
DoDD 5105.65, Defense Security Cooperation Agency (roles and responsibilities) https://www.esd.whs.mil/
| DoDD 5230.24, Distribution Statements on Technical Documents | https://www.esd.whs.mil/ |
| DoDI 5230.24, Distribution Statements | https://www.esd.whs.mil/ |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .