Expense Assignment System IV (EAS IV)
Release Notes
Software Release 5.1.3.1
Final
5 February 2011
Deliverable # 50
Contract Number: W74V8H-04-D-0030-0012
/ Hewlett-Packard Enterprise Services (HPES)Four Skyline Place
5113 Leesburg Pike, Suite 300A
Falls Church, VA22041-3215
EAS IV Release Notes, Software Release 5.1.3.1
Document Information
Document title: / EAS IV Release Notes, Software Release 5.1.3.1Document filename: / EAS IV 5.1.3.1 ReleaseNotes_Final_5 Feb 11.doc
Document Version: / 1.0
Issued by: / HPES
Issue date: / 7 February 2011
Author: / Karen Lameo
Owner: / Wayne Foshay
Status: / Final
Document Stakeholders
The stakeholders identified in this section are responsible for reviewing and approving these release notes at inception and after any subsequent changes.
Richard Edwards, GSDep Director, HR Solutions Contracting Officer’s Representative
Defense Health Services Systems (DHSS) / signature / date
Audrey Ard Heil, PMP
Defense Health Services Systems
Project Controller / signature / date
Wayne Foshay
HPES
Project Manager / signature / date
Maureen Hafner
HPES
Configuration Management Specialist / signature / date
Ken Moniza
HPES
Engineering Lead / signature / date
Revision History
Version Number / Revision Summary / Date1.0 / Draft Creation for EAS IV and the EAS IV Repository Software Release 5.1.3.1, to include CRs SCR044026/ CR00179, CR00625, CR00576, CR00583, CR00666, SCR074120/CR00423, CR00699, and CR00614. / 19 January 2011
1.0 / Final Creation for EAS IV and the EAS IV Repository Software Release 5.1.3.1, to include CRs SCR044026/ CR00179, CR00625, CR00576, CR00583, CR00666, SCR074120/CR00423, CR00699, and CR00614. / 7 February 2011
Table of Contents
1. Objectives
2. Scope
3. System Software Identification
3.1 Release Information
3.2 Software Life Cycle Phase
3.3 Installation/Deployment Targets
3.4 Deployment Dates for Each Target
4. Release Description
4.1 Inventory of Materials Released
4.2 Inventory of Software Contents
4.3 Changes Installed
4.3.1 System Requests
4.4 Adaptation Data
4.5 Installation Instructions
APPENDIX A : Acronyms and Abbreviations...... A-
List of Tables
Table 31: Software Components and Versions
Table 32: EAS IV and EAS IV Repository Environments
Table 41: System Requests Implemented in Release 5.1.3.1
February 20111Version 1.0
EAS IV Release Notes, Software Release 5.1.3.1
EAS IV Release Notes, Software Release 5.1.3.1
1.Objectives
This document describes the contents of the Expense Assignment System IV (EAS IV) Release 5.1.3.1 deliverable. It is developed under Defense Medical Information Systems/Systems Integration, Design Development, Operations and Maintenance Services - III (D/SIDDOMS – III) Contract W74V8H-04-D-0030-0012.
February 20111Version 1.0
EAS IV Release Notes, Software Release 5.1.3.1
2.Scope
The purpose of the Release Notes is to provide a standardized means to identify items that are contained in each release. The proper identification of new, changed, and enhanced features of each release will allow for a more successful installation and implementation of these items. Also, adherence to this standard will ensure that implemented changes do not adversely affect the system or its security policies.
The Release Notes are generated throughout the system life cycle (SLC) of EAS IV. The identification of release information as defined in this document is applicable to all personnel responsible for the analysis, design, development, maintenance, and testing of the EAS IV application.
The Release Notes are generated for each release pertaining to patches, enhancements, upgrades, and routine maintenance.
February 20111Version 1.0
EAS IV Release Notes, Software Release 5.1.3.1
3.System Software Identification
3.1Release Information
The software version information described in this document pertains to EAS IV Software Release 5.1.3.1_February 2011.
The table below reflects the software components and their versions for EAS IV Software Release 5.1.3.1_February 2011.
Table 31: Software Components and Versions
Software Component / Software VersionOperating System Solaris / S10R8
Operating System Solaris 10 Kernel / 144488-06
Operating System Java / 1.5.0_24
Oracle Database 10g / 10.2.0.4
Oracle Application Server 10g / 10.1.2.3
Oracle Client 10g / 10.2.0.4
Tomcat BOXI / 5.5.30
Java SDK BOXI / 1.5.0_24
BOXI R2 SP6 / 11.5.12.1838
3.2Software Life Cycle Phase
EAS IV Software Release 5.1.3.1 is currently in the Production phase of the software life cycle process.
3.3Installation/Deployment Targets
The intended installation targets for EAS IV Software Release 5.1.3.1 are the designated servers at the Defense Information System Agency (DISA) in San Antonio, Texas and in Oklahoma City, Oklahoma. The EAS IV Tier 3 team is currently providing installation support to these servers. The EAS IV Tier 3 team utilizes a virtual private network (VPN) connection to the DISA site to perform the install. These environments are identified below.
Table 32: EAS IV and EAS IV Repository Environments
EAS IV / EAS IV RepositoryApp / DB / App / DB
Development / X / X / Development / X / X
Development Test / X / X / N/A
Production Test - DTE / X / X / Production Test - DTE / X / X
Production Test - Training / X / X / N/A
Production / X / X / Production / X / X
3.4Deployment Dates for Each Target
Deployment dates to all environments are contained in the Server Checklist as part of the EAS IV Software Release 5.1.3.1 Production Release and Project Schedule delivery.
February 20111Version 1.0
EAS IV Release Notes, Software Release 5.1.3.1
4.Release Description
The following paragraphs contain a description of the changes that have been made to the EAS IV system since the last baseline release. The changes herein described consist of data modifications, and code modifications and additions to enhance usability. The overall system architecture and design did not change for this release.
4.1Inventory of Materials Released
EAS IV Software Release 5.1.3.1 is delivered to the EAS Program Office (EAS PO) via the DHSS Deliverables Management System (DMS). The EAS IV Project Schedule is also included with the release software. A compact disk (CD) is also created and stored in the HPES EAS IV library.
4.2Inventory of Software Contents
A complete listing of the deliverables can be found on the EAS IV 5.1.3.1 Deliverable Packing List.
4.3Changes Installed
The changes that are included in EAS IV Release 5.1.3.1 are listed in Table 4-1. Software code changes were applied to the EAS IV Production Test environment from 5 November 2010 through 7 January 2011. Internal testing was conducted from 9 November 2010 through 11 January 2011.
Developmental Test and Evaluation (DT&E) testing of the software code changes was conducted from 20 January 2011 through 4 February 2011. Approval to deploy was received on 4 February 2011.
Server maintenance occurred for the following items in the Production environment requiring system downtime between the hours of 8:00 a.m. ET and 4:00 p.m. ET on 5 February 2011.
- EAS IV Tier 3 Team Maintenance Task 1: EAS IV SW Release 5.1.3.1 Code Release
- EAS IV Tier 3 Team Maintenance Task 2: Complete data updates on the EAS IV Repository in support of Classes 10, 20, 21, and 22 changes. Note, this will be a phased approach updating each fiscal year separately starting with the most current fiscal year and working backwards. Each fiscal year data update takes approximately 20 hours to complete. The EAS IV Repository will be offline during this time period.
After the updates were applied, production testing was conducted to ensure that there were no impacts to the production environment. Production testing occurred to check system navigation, the reporting tool, and Allocation and Transmission services. No data were changed. Approval was received by the Army Medical Expense and Performance Reporting System (MEPRS) Program Office to run an Allocation for a site that is no longer a Parent facility.
February 20111Version 1.0
EAS IV Release Notes, Software Release 5.1.3.1
4.3.1 System Requests
The System Requests that are included in Release 5.1.3.1 for the EAS IV Web Application are listed in Table 41.
Table 41: System Requests Implemented in Release 5.1.3.1, February 2011
Change Type / CR# / TT ID# / Description / ResolutionEAS IV Repository Application and Database Server / SCR044026/CR00179/CRS08229/ TT403/5021
CR00659/CRS09017/TT4941
CR00696/CRS09024/TT5041 / System change request was received to address several issues with the EAS IV Repository.
- When using the Parent DMIS Name from Class 1 in conjunction with elements from Classes 5, 6, 9, 10 or 16, the data becomes corrupt and not reliable. When the Parent DMIS Name is removed from the query the data returned is correct and can be validated at the local (facility) level. (TT403/5021)
- When Skill Type Description is used in a query, it does not appear in the report. When running a query pulling data from Class 8 using skill type description, the user gets a context prompt. (TT403/5021)
- Total professional salary expenses derived from Class 20 are higher than those derived from either Classes 8 and 9 or Class 21, which give the same result for total professional salary. Professional salary expenses in the data derived from Class 20 show expenses have been allocated from the cost pools, yet there still are expenses remaining in the cost pools. Adding up expenses remaining in the cost pools, the sum is exactly the difference between the total expenses for Class 20 and the total for either Class 21 or Classes 8 and 9. (TT403/5021)
- Remove the Assigned Full-time Equivalent (FTE) field from the database table supporting the class and remove it from the class 10. This will also require that the load process change so the Assigned FTE field will not be loaded for post allocation. Assigned FTEs should be retrieved from Class 7, Personnel Detail. (TT403/5021)
- In Class 12, when you include DoD Standard Expense Element Code (SEEC) description, the Service Unit Costs are overstated. (TT403/5021)
- Running a query using Class 16 with and without DMIS ID name from Class 1 showed that there is a variance. It's not great, and doesn't occur with every DMIS ID, but there is a difference amounting to over $2M for FY2003.
- When using Class 21, the visits and Dental Weighted workload is different in Class 21 when Class 1 for Regional Medical Command (RMC) and RMC Descriptions are used. When RMC and RMC Descriptions are used, both visits and dental workload is less. (TT403/5021).
- Classes 21 and 22 are summary classes in which data from other classes is aggregated to create these classes. Currently, a record is only written to the class if it has an expense and then that record is updated if it finds a personnel record and/or workload record. This is incorrect. Even if there is no expense but there is personnel data and/or workload data, a record should be written. Currently, if there is no expense, the load process will not write a personnel and/or workload data record if there is no expense record. If no expense, rather than skipping the personnel and/or workload records it should be writing them to the table. Once the load code is fixed, the data will need to be regenerated for these classes. (TT403/5021)
- Summary Ambulatory Expense Analysis Report by DoD SEEC; Summary Ancillary Expense Analysis Report by DoD SEEC; Summary Dental Expense Analysis Report by DoD SEEC; Summary Inpatient Expense Analysis Report by DoD SEEC; Summary Ambulatory Expense Analysis Report by DoD SEEC Ctgy; Summary Ancillary Expense Analysis Report by DoD SEEC Ctgy; Summary Dental Expense Analysis Report by DoD SEEC Ctgy; Summary Inpatient Expense Analysis Report by DoD SEEC Ctgy – The report sums Service Unit Cost by Service Unit Code. This is not a meaningful measure. Also, using DoD SEEC Description or DoD SEEC Category Description returns incorrect results. (TT403/5021)
- EAS IV Repository Ancillary Data Set Accepted Report – remove grand total at bottom; doesn’t make sense to grand total. (TT403/5021)
- EAS IV Repository Cost per Visit Using Total Expenses Report – remove column in report entitled Parent DMIS ID because Parent DMIS ID is in the header. (TT403/5021)
- EAS IV Repository Direct Expense Accepted Report –
- Fix the DoD SEEC Description field and place it next to the DoD SEEC.
- Add a subtotal of Direct Expense Net Month and Direct Obligation Net Month for Functional Cost Code (FCC)/DMIS ID Combination within a Schedule Type Code.
- Add a subtotal of Direct Expense Net Month and Direct Obligation Net Month for DMIS ID within a Schedule Type Code.
- Add a grand total of Direct Expense Net Month and Direct Obligation Net Month within a Schedule Type Code. (TT403/5021)
- EAS IV Repository Expense Allocated FCC Summary Report (All Codes tab) – add a grand total for each of the Expense Indicator Description fields at the bottom of the report. (TT403/5021)
- EAS IV Repository Patient Acuity Accepted Report – remove multiple column headings and use one column heading breaking on FCC. Center column headings. (TT403/5021)
- EAS IV Repository Personnel Accepted Report – rename last column to Nonavailable Other FTE (currently report shows as having Nonavailable Sick FTE). (TT403/5021)
- EAS IV Repository Summary (Ambulatory, Inpatient, Ancillary, and Dental) Expense Analysis Report by SEEC Category – remove grand total at bottom. (TT403/5021)
- The EAS IV Repository Summary (Ambulatory, Inpatient, Ancillary, and Dental) Expense Analysis Report by SEEC – provide a total for the Service Unit Cost and Total Expense fields within each 4th level Functional Cost Code for each combination of DMIS ID, 4th level Functional Cost Code, Service Unit Code, and DoD SEEC Category for a particular fiscal year and fiscal month. (TT403/5021)
- EAS IV Repository Respiratory Therapy/Pulmonary Therapy Accepted Report – remove grand total at bottom. Center column headings. (TT403/5021)
- When adding skill type suffix description to an EAS IV Repository query, the query took an exceptionally long time to run. (TT4941)
- When running a query in Class 24, Skill Type subclass, the query brings up contexts and it should not. (TT5041)
- The data issue between Class 1 and Classes 5, 6, 9, and 10 could not be reproduced in Production and therefore, a change to the universe was not made. Since the timeframe that this was initially reported, the DMIS ID Year table underwent needed table maintenance which was performed three years ago. This more than likely resolved the issue.
- Running a query from Class 8 no longer brings up a context prompt.
- The load process has been updated to exclude cost pool accounts in the creation of Class 20. Existing cost pool account records have been deleted from Class 20.
- The EAS IV transmission code has been modified to exclude Assigned FTEs for personnel allocated data. The load process for Class 10 has been modified to remove Assigned FTEs. The Assigned FTE field has been removed from Class 10. Assigned FTEs for existing records have been purged from Class 10. At the time of deployment, any transmission files previously processed using the old code will not be able to be processed. The data will need to be re-allocated and re-transmitted.
- The EAS IV Repository join between the DoD SEEC Year and Service Unit Cost tables was modified to make the cardinality from outer to outer to inner to outer.
- There was a universe change to correct the joins in Class 16.
- This issue could not be reproduced in Production and therefore, a change to the universe was not needed. Since the timeframe that this was initially reported, the DMIS ID Year table underwent needed table maintenance which was performed three years ago. This more than likely resolved the issue.
- The load processes for the creation of Class 21 and Class 22 have been updated to ensure inclusion of all expense, personnel, and workload records. Class 21 and Class 22 data have been re-created to include records for all expense, personnel, and workload data.
- The reports mentioned in item 8 have been updated to eliminate the summary of Service Unit Costs by FCC values. In addition, the statistical amount field has been changed from Measure-Sum to Measure-None.
- Items 9 Through 17. Reports were updated to conform to the stated requirements.
- Items 18 through 19. EAS IV Universe join corrected resulting in performance improvement and elimination of context prompt.
EAS IV Application Server / CR00625/CRS08263/TT780 / When the EAS IV WebI product deployed, the Respiratory Therapy/Pulmonary Function data could not be entered through batch entry. The MEPRS Management Improvement Activity requested that the Respiratory Therapy/Pulmonary Function be moved to Data Sets data type to allow batch entry. (TT780) / The Respiratory Therapy/Pulmonary Function is now located in Workload Adjustments under the Data Sets data type. Data will now be entered using DDDA/DMIS and DHAA/DMIS data sets and can now be entered by batch entry.
EAS IV Application Server / CR00576/CRS08233/TT1237 / Site personnel reported that they made a personnel adjustment transferring Full-time Equivalent and Salary Expense data from one FCC to another FCC. Typically, this will update the associated records in Expense Accepted; however, the personnel adjustment did not automatically update the Expense Accepted table. (TT1237) / The personnel adjustments transfer code was updated to ensure all transfers from personnel record to another either creates a new financial record or updates the existing record in the Expense Accepted table.
EAS IV Application Server / CR00583/CRS08234/TT1269/5336
CR00647/CRS09022/TT5135
CR00772/CRS09025/TT5178
CR00785/CRS09026/TT5271
CRS08572/TT5333 / Several issues were reported with EAS IV not restricting the DMIS ID and FCC dropdown lists in the Error Correction Unit and Adjustments to the rules set up on the MTF Business Rules table.
- The system did not restrict users from entering incorrect data in the FCC dropdown list in Workload Adjustments. (TT1269)
- Site personnel were unable to select a DMIS ID in the Error Correction Unit (ECU) Data Sets Detail screen because the software code that determines whether a DMIS ID code is valid or not is using cal_month (one digit) rather than cal_month_mm (two digits). The DMIS ID in question was activated on 1/1/2009 so the system did not recognize the DMIS ID as being valid. (TT5135, TT5333)
- The FCC dropdown list for the F Acct Raw Proc Data set does not read the standard business rules for populating the data set. Site was able to enter workload data for FDCA. This data set should only allow the following FCCs per the standard business rules: FAC_, FAF_, FBI_, FBJ_, FBK_, FEA_, FEC_, FEF_. Standard data sets should use the standard business rules for populating the FCC dropdown list. Non-standard data sets (D***/DMIS) should use the MTF data set business rules. (TT5178)
- Site personnel are unable to select a particular FCC from the Adjustments Workload FCC dropdown list because the business rules are not being read correctly. (TT5271)
- Site personnel are unable to select a particular FCC from the Error Correction Unit FCC dropdown list because the business rules are not being read correctly. (TT5336)