1. Expense Assignment System Version IV, release 3.1 Presented by Audrey Heil, RITPO

2. 2 EAS IV 3.1 Architecture SQL & RETURN DATA EAS IV access via web browser INTERNE T HTTP/HTTPS TIER 2 Application Business Logic Layer TIER 3 Data Layer TIER 1 Presentation Layer (User Layer) HTTPS TCP/IP Database Implementation EAS IV 3.1 Middleware

3. 3 EAS IV 3.1 Software Software ComponentSoftware Product RDBMS (Database layer)Oracle 9.0.2 EAS Application Middleware (J2EE container) Oracle 9i Application Server ReportsBusiness Objects 6.1 Transport for the middlewareApache Web-Server Presentation Layer (user layer)MS IE 6.0 or Netscape 7.0 or higher

4. 4 EAS IV 3.1 Advantages  Centralized application structure ensures: –More efficient system changes and software deployment. –System maintenance/administration is centrally controlled at a secure DISA facility. –Users can access the application via a web browser using their desktop.

5. 5 EAS IV 3.1 Limited Deployment  Limited Deployment at seven MTFs for a 30 day period –Services CDAs have approved the limited and full deployment timeline and recommended seven sites based on the following criteria: A mixture of CONUS/OCONUS and large/small sites. A DMHRSi-LCA test site has been requested. EAS IV 3.1 will accept DMHRSi-LCA files or current legacy personnel system files. Knowledgeable/experienced MEPRS staff.

6. 6 EAS IV 3.1 Limited Deployment  Limited Deployment at seven MTFs for a 30 day period Adequate site-level staffing for at least one month, as the sites will need to dual process for a proper comparison between the client-server and web versions. Site is up to date with respect to current processing deadlines. Site desktops meet minimum hardware specifications as outlined in the Software Installation Plan.

7. 7 EAS IV 3.1 Limited Deployment EAS IV v3.1.LD SitesBranch of ServiceTesting Site Name/Address 1Air ForceMcChord AFB 2Air ForceFairchild AFB 3Air ForceLackland AFB 4Army Womack AMC 5ArmyBrooke AMC 6NavyNH Great Lakes 7NavyNH Sigonella

8. 8 EAS IV 3.1 Limited Deployment  Sites will identify a technical POC to assist with extraction of the site-level EAS IV Informix database and installation of the EAS IV client application/Business Object software.  Test sites will perform dual processing and verify data accuracy.  Each site will complete a predeployment checklist to demonstrate testing readiness. Site personnel will receive functional training.

9. 9 EAS IV 3.1 Full Deployment  Full deployment will occur over a 3 month period.  The deployment schedule will be coordinated with the Service CDAs. Each site will load the desktop EAS IV 3.1 application and begin processing with the current month.  Current EAS IV servers may be retired/reallocated.

10. 10 EAS IV 3.1 Repository Deployment  During deployment of EAS IV 3.1, the current EAS IV Repository data, as well as the Historical Repository Data (MEQS III), will be converted to Oracle and populate the production environment.  As deployment commences, EAS IV 3.1 data will be sent to the Informix EAS IV Repository as well as the Oracle EAS IV Repository. Analysts will only be required to access the Informix Repository for a complete data picture.

11. 11 EAS IV 3.1 Training/Capacity Testing  EASPO is updating the EAS IV ilearning product –Final version will be available prior to limited deployment. –Product was reviewed by the Service testers during the initial 3.1 SQT.  TIMPO is scheduled to perform capacity testing prior to Deployment