Transcript EASi - An Introduction

EASi
An Introduction
TMA MEPRS Program Office
July 29, 2008
At the end of this presentation, you will:
• Have an appreciation for how far we have
come systems-wise.
• Be able to articulate the benefits of EAS
3.1.
• List the twelve modules that compose the
processing environment.
• Be familiar with the next steps in the
process (EAS 3.2).
A Little EAS
History
Purpose:
“Provide DoD MTFs, Intermediate
Commands, Surgeons General, and Office
of the Assistant Secretary of Defense for
Health Affairs (OASD/HA) with timely
access to expense, staffing, and workload
data.”
MEPRS-Central Users Manual (January 1995)
Some Milestones:
• Circa 1982 - Uniform Chart Of Accounts Expense
Assignment System, Version II (EAS II)
• 1985 – birth of MEPRS by combining Uniform Chart
of Accounts (UCA) and the Uniform Staffing
Methodologies (USM)
• ?? - EAS III implemented (Contest Question)
• Circa 1994 – EAS III feeds Defense Medical
Information System (DMIS) Summary System
Some More Milestones:
• 1995 – EAS III feeds MEPRS-Central (a subsystem of the DMIS Summary System)
• 1998 - MEPRS Executive Query System
(MEQS III)
• July 2001 – EAS IV production implemented
• August 2005 – implementation of EAS 3.1
(EASi)
File structure from
MEPRS-Central
SQL Sample
SELECT SUM(total_expense),
fiscal_year, dmisid, meprs4_cd
FROM meprs.expense_summary_94
WHERE dmisid = ‘0109’
GROUP BY meprs4_cd;
From this…
Workload
(CHCS)
Financial Data
(STANFINS,
STARS/FL,
CRIS)
Personnel Data
(UCAPERS,
SPMS, EAS)
Local EAS IV
Servers
EAS IV
Repository
…to this.
Enhancements
Enhancements
Then
Now
158 site specific servers
1 central server
Desk top application
Internet-based
application
Upgrades applied at all servers
Upgrades performed through
central server
Informix-driven database
Oracle-driven database
Multi-Tier architecture
Improved 3 -Tier architecture
An Example of Three - Tier Architecture from Wikipedia
EASi Modules
Modules:
• Systems Interfaces – allows validation of imported data.
• Error Correction Unit (ECU) - displays warnings and errors and
allows user to override system generated information.
• Adjustments – allows user to add, delete, move, or update
information.
• Table Maintenance – allows users to browse tables. Updating tables
requires special privileges.
• System Services – contains log-on and system administration
maintenance functions.
Modules (Cont.):
• Allocation – allows costing, allocation, pre-allocation validation, and
post-processing data transmission and reporting.
• Validation – applies business rules to source data for verification of
“clean” data prior to allocation.
• Reports – allows generation of standard or ad hoc reports.
• Exception Handling – aids user in investigating errors.
• Online Help – provides user access to system assistance either
through a topic index or through a search engine.
Modules (Cont.):
• Navigation – allows users access to the functions and features
behind the Graphical User Interfaces (GUIs).
• Infrastructure – supports database, interface, network protocol
activities, as well as COTS product integration.
What’s Next?
Next Steps:
 Convert EAS IV Central Repository database from Informix to
Oracle
 Migrate EAS IV Oracle Databases from 4800 * to new 25K servers
 Upgrade all EASIV Oracle databases to 10g Release 2
 Upgrade the current unsupported versions of Business Objects used
by the EAS IV application (BOXI)
 Address System Integration Requests (SIRs) and finalize pending
System Change Requests (SCRs)
By now you should:
• Have an appreciation for how far we have
come systems-wise.
• Be able to articulate the benefits of this
new system.
• List the twelve modules that compose the
processing environment.
• Be familiar with the next steps in the
process (EAS 3.2).
Questions?