HR104_Military_Dates



Application: HRMS

Module: Human Resources

Business Process: Hire Workforce

Requirement Number: HR104

Requirement Title: Ability to maintain Military Start and End Dates

Module Leads: Lina Simonu, Lisa Lagus

1. Requirement Description

Describe the requirement (gap). Include a description of the delivered PeopleSoft functionality.

APS maintains military Start and End dates as well as type of Military Service, such as War time and Peace time. Military information is needed to calculate dates for seniority list, longevity list, and retirement information. PeopleSoft has the ability to indicate whether an employee has had military service without Military Start and End dates associated with the type of service on the Personal Data record. The Federal PeopleSoft Personal Data Sub record does maintain Military Start and End dates, however, this sub record is only available through Applicant Personal Data. Need to determine whether the Federal Personal Data sub record may be used to store Military Start and End dates. This would require all employees to have their applicant data completed upon conversion and on going.

2. Business Need

Provide a justification for the requirement. Include information about frequency, volume, number of users impacted, etc.

Military Service is used in the calculation of seniority, longevity, and for retirement. Without this information, these calculations could not be made within the system. Longevity is calculated and paid twice a year. In April 2001, 31,221 longevity checks were produced. Seniority is calculated during layoff periods and some bargaining units request seniority be produced annually. Retirement is not in-scope so only war service dates for seniority and longevity will be tracked in Core-CT, not retirement war service dates.

3. Required By: (Y/N)

Federal ____ Agency ____ Bargaining Unit _X___

State Statutory _X___ State Regulatory ____ State Procedural ____

4. Requirement Priority

_High_____ (High, Medium, Low – please see “Requirements Prioritization Criteria”)

5. Recommended Solution

Enter an “X” next to the appropriate category

______ Process Solution

___ Option Number

__X____ Application Modification

2 Option Number

6. Explanation for Recommendation

Provide reasons for recommendation. Please do not re-state the description of the solution itself.

By utilizing the delivered sub record, we are minimizing modifications, while meeting the State’s requirement.

7. Organizational Impact of Recommendation

Describe the changes to the organization that result from the recommended solution. Include a description of any role, process, statute, or bargaining unit agreement affected.

None

8. Process Solutions

Describe the possible Process Solutions. Include a description of impacts and benefits of each solution.

Option 1. Presently, this information is maintained in an employee's personnel file and noted on an employee's payroll card. If the system is unable to maintain multiple military service dates, and corresponding type(s) of military service, agencies will continue to review/note this information manually. This information would then need to be referenced manually when calculating seniority, longevity, and retirement dates.

Option 2. Use the delivered PeopleSoft Applicant Data Federal Personal Data sub record, as is, to store the Military Start and End dates. These could only be entered for Applicants though, therefore, existing employees could not have this information updated or entered upon implementation, unless their applicant data was converted.

Option 3.

9. Application Modifications

Describe the possible Application Modifications. Include a description of impacts and benefits of each solution.

Option 1.

Modification Type (On-line, Batch, Interface, Report, Workflow): On-line

Complexity (Easy, Medium, Difficult): Difficult

Description: Add the Personal Data Federal sub record to the Personal Data record and page to store all Veteran information including Military Start and End Dates. In addition, the amount of military service needs to be calculated, in Years, Months, and Days. These values are used in the calculation of longevity and seniority. Fields would need to be added to this sub record to store Years, Months, and Days. In addition, peoplecode would need to be added to calculate the Years, Months, and Days based on the Military Start and End Dates. Any delivered reports will not run off a new sub-record, however, since this is a Federal sub-record, none of the reports in Education and Government PeopleSoft that the State has decided to use are impacted.

Option 2.

Modification Type (On-line, Batch, Interface, Report, Workflow): On-line

Complexity (Easy, Medium, Difficult): Medium

Description: Add the Personal Data Federal sub record to the Personal Data record and page to store all Veteran information including Military Start and End Dates. If the State creates a program to calculate longevity based on these dates, the Years, Months, and Days values do not need to be stored online. See Issue #30 for more information on longevity calculation. Any delivered reports will not run off a new sub-record, however, since this is a Federal sub-record, none of the reports in Education and Government PeopleSoft reports that the State has decided to use are impacted.

Option 3.

Modification Type (On-line, Batch, Interface, Report, Workflow):

Complexity (Easy, Medium, Difficult):

Description:

-----------------------

[pic]

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download