Overview

Background

The current implementation of eRecruitment is an old version and the support the supplier is able to provide is limited because of this. eRecruitment was implemented with a character set which is not the usual one used with eRecruitment and this places UoE in a unique support position with Core. Core have advised that the character set must be converted to the character set the application expects before upgrading. The eRecruitment Proof of Concept project (HRS086) successfully tested converting the character set as part of the Upgrade process.

Scope

In Scope 

• Upgrade of eRecruitment to v21
• Conversion of the character set
• Updates to BI universe required due to Upgrade

Out of Scope

• Any enhancements to the service. The Upgrade will introduce functional enhancements by default but this project will not be requesting any.

Objectives

• To move eRecruitment onto the expected Character Set
• To upgrade to v21
• Improve the support position for this key university service
• Refresh and re-engage with the eRecruitment User group, ensuring it represents all 6 personas
• Update the eRecruitment BI universe if required due to the upgrade

Deliverables

• v21 of eRecruitment implemented (Core & IS Apps, with testing by HR & User Group)
• Converted character set (Core & IS Apps, with testing by HR & User Group)
• Revised BI Universe if required (IS Apps development with testing by HR )
• Fully updated user manuals and guidance (HR)
• User training (HR)

Benefits

• eRecruitment will be on new character set
• Improved support  position
• Maintained and even improved performance against SLA with Supplier
• New functionality by default in v21
• Stable service which can then be enhanced
• Re-engaged User Group

Success Criteria

• v21 implementation is a smooth transition for users.