Help
Results must:
*MISSING[LBL_SEARCH_OPTIONS]*

Pick start and end date Date:
From:   
  
To:   
ERP Change Management Policies and Procedures There are 0 replies:
Anonymous  
ERP Change Management Policies and Procedures Original post: Thu 4/17/2014 at 12:30 PM

SLC ITS

ERP Change Management Policies and Procedures

 

Change Management Policy

 

Definition

 

ERP Change Management is the process of requesting, programming, approving and launching a planned or unplanned change within the IT infrastructure. It begins with the communication to IT staff and it ends with the satisfactory implementation of the change and communication of the result of the change to the target audience.   Regular maintenance and applications of available OS upgrades is done via automatic updates from the server side OS. 

 

Scope

 

The intended scope of the change management process is to cover changes to the Jenzabar ERP and PowerFAIDS Applications in the production environments. Primary functional components include the following:

 

Hardware – Installation, modification, removal or relocation of computing equipment.

Database – Changes to databases or files such as updates, additions, reorganizations and major maintenance.

Application – Application installations, patches or major release being applied to production.

 

Out of Scope

 

Tasks that require an operational process but are outside the initial scope of the ERP Change Management process include:

 

Disaster Recovery – Database and / or VM image restoration 

Changes to non-production elements or resources

Changes within the daily administrative process such as password resets, user adds and deletes, etc.

Functional configuration of Business Units

Schedule Changes – Requests for creation, deletion or revision to job schedules, back-up schedules or other regularly scheduled jobs managed by the ERP Staff.

 

Process for Changes to EX 

 

Formally request a change for All requests for change to Jenzabar EX will be documented by formally requesting the change via email to IT staff. The request will recorded in footprints by a member of the IT staff and a ticket will be assigned.

 

Analyze and Justify Change – IT Staff will work with the change requester  to develop a specific justification for the change and identify the impact on infrastructure, business operations and budget, identify business as well as technical risks, develop technical requirements, and review specific implementation steps.

 

Approve and Schedule the Change The IT Director will review the request with the appropriate team members to assess the urgency and impact of the change on the infrastructure, end user productivity and budget.  In the event of a major or significant change, the IT Director will determine whether the project will require the contracting of Jenzabar to perform the work or be consulted and whether the requested change will violate and software agreements.

 

Plan and Complete the Change – The IT Director will assign specific IT members and identify appropriate end-user members to complete the change in a manner that will minimize impact on the infrastructure and end users. In the event that the change does not perform as expected or causes issues to one or more areas of the production environment, the team will determine if the change should be removed and the production environment returned to its prior stable state. 

 

Post Implementation Review – A review will be conducted by the assigned IT team to ensure the change has achieved the desired goals. Post implementation actions may include acceptance, modification, or backing-out of the change. The team formally documents the final disposition of the change by closing out the footprints ticket.

 

Process for Changes to Powerfaids 

 

Formally request a change for All requests for change to PowerFAIDS will be documented by formally requesting the change via email to IT staff. The request will recorded in footprints by a member of the IT staff and a ticket will be assigned.

 

Analyze and Justify Change – IT Staff will work with the change requester  to develop a specific justification for the change and identify the impact on infrastructure, business operations and budget, identify business as well as technical risks, develop technical requirements, and review specific implementation steps.

 

Approve and Schedule the Change The Associate Director of IT will review the request and assess the urgency and impact of the change on the infrastructure, end user productivity and budget.  In the event of a major or significant change, the Associate Director of IT will determine in conjunction with the Director of Financial Aid whether the project will require the assistance of the College Board to perform the work or be consulted and whether the requested change will violate and software agreements.

 

Plan and Complete the Change – The Associate Director of IT will assign specific IT members and identify appropriate end-user members to complete the change in a manner that will minimize impact on the infrastructure and end users. In the event that the change does not perform as expected or causes issues to one or more areas of the production environment, the team will determine if the change should be removed and the production environment returned to its prior stable state utilizing the Virtual Environment Rollback or to employ the College Board to remedy the issue.

 

Post Implementation Review – A review will be conducted by the assigned IT team in conjunction with the Director of Financial Aid to ensure the change has achieved the desired goals. Post implementation actions may include acceptance, modification, or backing-out of the change. The team formally documents the final disposition of the change by closing out the footprints ticket.

 

Edited:Thu 4/17/2014 at 12:36 PM by Anonymous
Original Post New