1 / 18

Planning Process for a Single Database Presented by Terry Anderson and Jessica Jagoditsh

Planning Process for a Single Database Presented by Terry Anderson and Jessica Jagoditsh. What We Will Cover. Why merge? Prerequisites Decision to move forward! Process Overview Cleanup requirements Handy tidbits. Why Merge?. State and federal reporting mandates Stronger integration

edda
Télécharger la présentation

Planning Process for a Single Database Presented by Terry Anderson and Jessica Jagoditsh

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. Planning Process for a Single Database Presented by Terry Anderson and Jessica Jagoditsh

  2. What We Will Cover • Why merge? • Prerequisites • Decision to move forward! • Process Overview • Cleanup requirements • Handy tidbits

  3. Why Merge? • State and federal reporting mandates • Stronger integration • Enhanced reporting • Centralized management of common fields • Increased efficiency – single login

  4. However….. • Complexity of merge • Success depends on • Cleanup team organization • Sufficient time • Adequate resources • Incomplete cleanup results in reschedule of merge project

  5. However…..

  6. Project Manager

  7. Prerequisites • Must be running full suite • PO submitted • All data conversions from legacy system complete for least 6 months prior to merge • SSNs must be in Skyward

  8. Prerequisites (Cont’d) • All necessary cleanup done before live merge • Both databases at same release level • ISCorp • 5+/- day window - downtime

  9. Decision to move forward!

  10. Decision to move forward! • Develop a team • Business • Student • Tech • Begin to meet with Skyward PM • Skyward CS person assigned • Create a calendar and cleanup plan

  11. Process Overview • Initial call • Develop Schedule • District completes initial cleanup - review • Preliminary merge • Results review • Continue cleanup • Live merge

  12. Example Timeline • February 6th – 1st meet with PM • Begin cleanup • Work with customer service (CS) • April 23rd – Pre-merge verification with CS • May 7th-11th – Preliminary merge and QA • June 29th – Final pre-merge checks • July 9th – 13th – Downtime - Live merge

  13. Cleanup Requirements • Duplicate alpha key reviews • Name merges on both databases • Duplicate SSN reviews • STU/FIN name comparisons • Pre-merge verification reports

  14. Handy Tidbits • Skyward available throughout process • Merge into Student • Name record from Business • Alpha key tie-breakers can change

  15. Handy Tidbits • System wide access • SSN – held in background • Scheduling merge – reporting, payroll, etc. • ISCorp

  16. THANK YOU FOR ATTENDING!

More Related