1 / 23

Transferring Staff in ESR Transition Planning Workshop 20th September 2012 Paul Spooner

Transferring Staff in ESR Transition Planning Workshop 20th September 2012 Paul Spooner. Objectives. Define the ‘as-is’ position – pre-transition Define the ‘to-be’ position – post-transition Understand the ‘staff transfer’ challenge

oberon
Download Presentation

Transferring Staff in ESR Transition Planning Workshop 20th September 2012 Paul Spooner

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Transferring Staff in ESR Transition Planning Workshop 20th September 2012 Paul Spooner

  2. Objectives Define the ‘as-is’ position – pre-transition Define the ‘to-be’ position – post-transition Understand the ‘staff transfer’ challenge Discuss the options that receiver organisations have to transfer staff records Ensure receiver plans include staff transfer activities, from source to receiver ESR VPDs Discuss associated ESR set-up activity Transaction teams – Recruitment, HR, Payroll, Learning Management Pensions General Ledger

  3. As-Is Position

  4. Currently… Over 140 PCT Virtual Private Databases (VPDs) containing staff records 10 SHA VPDs containing staff records Multiple transaction service providers – in-house and outsourced (Recruitment, HR, Pay, Learning) Some staff may be transferring in to the receiver from outside ESR, e.g Local Authority staff, DH staff

  5. To-be Position

  6. Working towards… All PCT and SHA organisations decommissioning PCT and SHA staff records need managing to ensure appropriate transfer or end-dating Some staff records not currently on ESR need to be transferred in to ESR. New organisations resulting from transition to be set up, as per authorisation by Statutory Instrument Current understanding is…

  7. Working towards…

  8. The Challenge

  9. What needs to happen… Following receiver VPD set-up, staff records within Source EA VPDs need to be managed according to their transfer status, either: Staff record transferred to receiver organisation VPD Staff record end dated, leaver process initiated for staff leaving the service QUERY…what will happen to retention records as at 31/3/13 for staff without a transfer outcome? Is this possible? Who will manage the record/VPD? QUERY…who will be granted historical ‘archive’ access to de-commissioned VPD data? Source EA Data Controller action

  10. Staff Transfer Options

  11. What needs to happen… There are 3 options for transferring staff records within ESR: Central demerge – 4-6 months project, McKesson, Source and Receiver led Inter Authority Transfer – Receiver led activity (working with the source EA), when required. Coordinated with ESR Programme team Manual Migration (Key-in!) – Receiver led activity (working with the source EA), when required

  12. Phase 1: Project Start-Up • Phase 2: Project Initiation • Phase 3: Data Preparation • Phase 4: Dress-Rehearsal • Phase 5: Live Demerge Event • Post-Demerge Consolidation Option A – Central Demerge…

  13. Requirements include: • Understanding of People mapping • Provision of basic employee data to create a new starter • Receiver Capacity ‘per employee record’ to: • manually enter new starter data, • request IAT transfer of data, • complete the employee record Option B – IAT…

  14. Requirements include: • Understanding of People mapping • Provision of employee record data from Source EA • Receiver Capacity to manually enter the data (basic record creation, circa 20 minutes per record) • If basic record creation – data completeness at point of transfer (impact to both local and national reporting) Option C – Manual Data Entry…

  15. TCS Lessons Learnt

  16. Option A – Central Demerge… • Close co-operation between source and receiver EAs is essential • Ensure that impacted organisations, such as HMRC, Pensions are liaised with asap • It is essential that both source and receiver EAs can provide suitable resource, across Rec/HR, L&D and payroll to deliver the project

  17. Option A – Central Demerge… • A minimum requirement for reconciliation reporting (Phase 5) includes: • Positions Analysis • NHS Absence Management Analysis • NHS Organisation Profile Analysis – Staff List • NHS Organisation Profile Monitoring Analysis • Partial Year End P35 Listing • Review URP’s / Roles / eLearning Logins? • CSD Dates

  18. Central Demerge and Pensions Interface • As part of the de-merge, ESR produces a Pensions interface file. • No automatic action takes place at NHS Pensions. • A change of an EA Code on the Payroll Description generates a change record for all staff transferred, and is included on the Changes Interface. • Has to be updated manually by NHS P Staff, therefore discuss transfers with NHSP before they take place….HOWEVER…

  19. Manual Update on POL • It is possible to amend the EA code of a record using POL.

  20. Interfaces & General Ledger Considerations David Booth

  21. General Ledger Areas for consideration include: In house or via a Service Provider? Is the GL interface required to feed a single or multiple finance systems? Has the Receiver Entity Code been agreed? Has the account code structure and chart of accounts been agreed? Note – ESR account Code Conversion facility

  22. Other Interfaces.. Areas for consideration include: E-recruitment interface, eg NHS Jobs Time and Attendance, Rostering Expenses Pensions

  23. Any Questions? 23

More Related