180 likes | 276 Views
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
E N D
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 • Enhanced reporting • Centralized management of common fields • Increased efficiency – single login
However….. • Complexity of merge • Success depends on • Cleanup team organization • Sufficient time • Adequate resources • Incomplete cleanup results in reschedule of merge project
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
Prerequisites (Cont’d) • All necessary cleanup done before live merge • Both databases at same release level • ISCorp • 5+/- day window - downtime
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
Process Overview • Initial call • Develop Schedule • District completes initial cleanup - review • Preliminary merge • Results review • Continue cleanup • Live merge
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
Cleanup Requirements • Duplicate alpha key reviews • Name merges on both databases • Duplicate SSN reviews • STU/FIN name comparisons • Pre-merge verification reports
Handy Tidbits • Skyward available throughout process • Merge into Student • Name record from Business • Alpha key tie-breakers can change
Handy Tidbits • System wide access • SSN – held in background • Scheduling merge – reporting, payroll, etc. • ISCorp