Defense Enterprise Accounting Management System (DEAMS) ASMC Briefing Robert W. Mann 1Lt Carl J. Protsch Det 2/AES Approved for Public Release; Distribution Unlimited AFOTEC Public Affairs Public Release Number 2012-002

Overview Need for DEAMS AF Enterprise Perspective What is DEAMS Implementation Schedule AFOTEC’s Role

Current Capability Gap 27 April 2018 Current Capability Gap Current financial legacy systems are outdated, unreliable, and expensive to maintain Not compliant with Chief Financial Officers Act Standard Financial Information Structure Office of Management and Budget’s Financial Systems Integration Office Core Financial System Requirements Air Force Contingency Operations Financial Management support deferred Current financial legacy system (IAPS/BQ) using 1960s technology - Unreliable due to manual processes involved with interfaces - SFIS non compliance largely due to non standard data elements in all AF finance systems

Enterprise Perspective The payment process

DEAMS System Overview Hardware: Sun Enterprise servers Oracle 12R in FY12 Hardware: Sun Enterprise servers Software: Oracle 11i “configured” for user processes Resides on Global Combat Support System – Air Force 106 interfaces with ~30 external systems 1 legacy system subsumed

AFOTEC’s Role DEAMS is here Testing & assessing a “stabilized” system in the operational environment Test vs Assessment vs Evaluation Define software stabilization

Scope and Methodology Operations 27 April 2018 Scope and Methodology Operations Live environment with ~700 real-world users performing real-world missions at Scott AFB AMC MAJCOM; Air National Guard; Air Force Reserves; USTRANSCOM; and DFAS, Limestone, Maine Live interfaces, queries, and reports for all areas and levels Capability Functionality Procure to Pay Commit Funds, Obligate Funds Records Funds Disbursement Plan, Property & Equipment (Assets) Asset Tracking, Asset Depreciation Orders to Cash Revenue Recognition, Customer Billing Cash Receipt General Accounting Funds Management, Financial Compliance Cash Management, General Ledger Management Time and Labor Time and Labor Management Maintenance Routine hardware, software, and functional maintenance Emergency “fixes” to category 1 deficiency reports Documentation and training

Mission Scenario OVERVIEW First, the Comptroller Squadron has to load funds to spend. Next, the Resource Advisor begins ordering process through a Form 9. Contracting is notified via email generated by DEAMS that they have an approved Form 9 awaiting sourcing (finding a supplier). Contracting then creates a Purchase Order in the Standard Procurement System (SPS). This purchase order is transmitted to DEAMS via an interface. DEAMS will then obligate funds. Contracting sends Purchase Order to supplier. Supplier accepts the contract and begins to fulfill the order. Once the supplier fulfills the order, the customer records the receipt and acceptance of the order in WAWF. The Supplier submits an invoice (bill for goods or services) through Wide Area Work Flow (WAWF). This Invoice is transmitted to DEAMS via an interface. This information is transmitted to DEAMS via an interface. Once DEAMS has receipt, acceptance and invoice of the order “matched” to the Purchase Order, DEAMS sends a payment file to Central Disbursing System (CDS) (ie, DFAS) for payment. CDS issues a payment to the Supplier. CDS sends to DEAMS information on payment via an interface. DEAMS performs Period End Activities and Comptroller Squadron runs reports to verify transactions and status of funds. Applicable MOEs for this scenario: *MOE 2.8 Percent of transactions entered through DEAMS which contain invalid data and are processed *MOE 2.11 Error rate for matching Accounts Payable (P2P Procure to Pay) *MOE 2.13 Percent Vendor payments made within the specified Prompt Payment Act (PPA) Rule timeline (**KSA) **MOE 2.19 Period End data are available to the official financial reporting system by the prescribed day (**KPP)

AF Rollout

DEAMS Preview

Questions? 11