Clean Data Requirement:
- Business to Remove duplicate records and resolve data conflicts.
- Ensure that data is complete, accurate, and consistent – Filled out on PS supplied spreadsheet (attached below) without gaps/hidden rows/highlighted text /unfiltered– Employee Number, Email Address, Home Address (if required)
- Standardise data formats and values to facilitate data integration and analysis – Ensure information matches the requirement for Oracle load
- Reject/Approve data based on steps above
- Any additional requirements or additional employees must be consolidated and sent on an additional file and steps 1-4 must be followed
End to end Process
- Initial conversation: Business and People Services (PS) set out requirements for the bulk loading of letters.
- Data provision: Business provides data with a completed letter (with signature) to PS using a loader template.
- Letter review: PS reviews the letter.
- Follow Clean Data Requirement / Rejection Process (if applicable)
- Run mail merge (if required): PS runs a mail merge.
- 1st spot check: (if mailmerge is carried out) Business performs the first spot check if a mail merge was run.
- Dev environment load (if applicable): If there are over 200 letters, SysAdmin loads the data in the Dev environment.
- Load data: PS sends data to SysAdmin, who loads the data.
- 2nd spot check: PS performs the second spot check.
- Notification sent: SysAdmin sends a notification.
Service Level Agreement (SLA):
- Data provision: 10 days prior
- Letter review: 8 days prior
- Run mail merge: 5 days prior
- 1st spot check: 5 days prior
- Dev environment load: 5 days prior (if applicable)
- Load data: 5 days prior
- 2nd spot check: 0 days
- Notification sent: 0 days
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article