A lot of pieces must fit together seamlessly within a computer system (and to other systems) to guarantee success and long-term value.

 

 

We use Change Management to reduce risk by analyzing and prioritizing requests for changes to HRMS and other applications, and to keep track of the details.

In October 2009, the HRMS Release Management process has been implemented. It is a process which "bundles" several approved changes in one release to reduce the impact of changes on users, similar to the updates that Microsoft provides for Windows and Office products. It provides structure to the release of system changes so that customers know what changes to expect and when.

System changes can be large or small, impact multiple users, affect stored data, or involve hardware or software. Applying changes in planned releases saves time and money and reduces service disruptions. Types of changes include:

• Technical Upgrades – changes necessary to maintain vendor support and warranties, and to work with current technology.
• Enhancements and Fixes – modifications which increase performance and functionality, or solve a problem.
• External Requirements – updates required by legislative action, or for regulatory compliance such as tax rates.

Note: During this time, only regular maintenance and fixes to any errors will be performed on the E-Recruiting system. One strategy for meeting the Governor’s Shared Services Directive is to replace E-Recruiting with a hosted recruitment solution that has a single point of entry for job seekers to find job opportunities and apply for state positions. For additional information, visit Recruitment Shared Services.
 

 

HRMS Release Management Communications

• DOP to Implement new HRMS Release Management Process
• HRMS Release Management

 

HRMS Release Management Schedule

• HRMS Release Schedule - New 11/18/09: A list of target dates when DOP plans to implement a release, and is subject to change at any time.

 

 

HRMS Release Management Approved Changes

 

 

 

• October 29, 2009: Proposed HRMS Release 
• October 29, 2009: Final HRMS Release 
• November 24, 2009: Proposed HRMS Release - New 
• December 22, 2009

 

HRMS Release Management Emergencies/Exceptions to Standard Release Windows

• Criteria for Emergencies/Exceptions 

  

 

HRMS Change Requests and Incident Summary

• All Open Change Requests - updated 11/16/09
  A report that provides a list of all open HRMS Change Requests.      
• HRMS Incident Summary - updated 11/6/09
  A spreadsheet that provides a summary count of all open HRMS Incidents with a breakdown by agency. 

 

System Upgrade

• HRMS Upgrade
• HRMS Upgrade Impacts
• HRMS Data Definitions Project

 

 

 

HRMS Cross Agency Functional Team

The HRMS Cross Agency Functional Team is an advisory body to both the DOP HRMS Functional Team and the HRMS Governance Committee. Policy and process recommendations, prioritization and resource conflicts, as well as unresolved change management processes are escalated to the Governance Committee.

The Team reviews, discusses, and prioritizes HRMS change requests submitted to DOP as well as reviewing possible administrative process changes as an alternative to change requests.
 

Updated:  11/19/09