120 likes | 222 Views
Selecting and Implementing a Student Information System.
E N D
Selecting and Implementing a Student Information System Buyer Beware: With so many Student Information System (SIS) products on the market claiming to do everything from raising test scores to automated NJSMART reporting, many school districts are unsure which SIS to purchase. The new purchase will inevitably reduce much work associated with running a district – or will it? Selecting and implementing the “right” SIS for your district is an extremely challenging task. Although every district has unique SIS needs, this session will focus on four key areas in order to avoid a SIS implementation failure in your district: 1. Software selection, 2. Estimated timelines, 3. Deployment, and 4. Training/Staff Development. Neil Charles ncharles@mhrd.k12.nj.us Morris Hills Regional District TechSpo 2008
Agenda • Introduction • Software Selection • What do districts want in a SIS? • Who are the major SIS vendors today? • Who are other SIS vendors? • Selection recommendations • Deployment: • What are some lessons learned? • What are some critical factors for successful implementation? • Estimated Timelines • Training / Staff Development • Associated Costs • Ease of use • Other • Hardware • Maintenance / upgrades • Backups • Who is responsible? • External interfaces
What do districts want in a SIS? EVERYTHING Source: IBM Business Consulting Services
Most school districts want… • Web-based, web-enabled, multi-platform or hosted solution • State reporting • Multi-tiered levels of access (admin, counselors, teachers, parents, students, etc.) • Secure • Special Education • Internal reporting • Health • Fees / Lockers / Inventory • Scheduling • Transcripts / Historical information • Attendance • Handheld devices • Teacher gradebook • Import / export data from/to other systems • EASY TO USE!
SIS Vendors Major SIS Vendors SASI ( www.pearsondigital.com ) Chancery SMS ( www.chancery.com ) Sungard Pentamation ( www.petamation.com ) STIOffice ( www.ssts.com ) AERIES Eagle Software (www.aeries.com ) PaC School Management Software Skyward ( www.skyward.com ) PowerSchool (www.powerschool.com ) eSIS Administrative Assistants Ltd. (www.aalsolutions.com ) TSIS2 TIES / SchoolMAX MAXIMUS (www.schoolmax.net ) Schoolmaster ( www.schoolmaster.com ) Other SIS Vendors Ace Software ADM2000 (http://www.acesoft.com ) CrossPointe (www.crosspointeschoolsonline.com ) eSD (http://www.eschooldata.com ) Genesis Student Information System (www.genesisedu.com ) Management Information Group SIRS ( www.migsirs.com ) Rediker Software (http://www.rediker.com ) The Student Tracker (www.contourdata.com )
Selection Recommendations • Average “shelf-life” in district 7-10 years • Each district has unique and diverse needs • Bigger doesn’t always equate to BETTER • Define current practices • Define needs: Needs assessment • Availability and timeliness of support / upgrades / customizations • Reputation of Vendor (partner) • Review current systems / interfaces • Host meetings with constituents and key stakeholders (supervisors, teachers, parents, students, IT, counselors, nurses, etc.)
Deployment – Lessons Learned • Implement module by module don’t try to do too many at once • In our old system… • It’s all about people, not technology • Support from the top is critical • The project leader makes a big difference • Communication3 • Roadmaps and timelines keep everyone focused • It’s easier to give than to take away!
Deployment – Critical Factors for Success • Upper level district and school leadership • A core project team • Project leader • Data integrity checks: Garbage in = Garbage out • Stable infrastructure • Cross-functional teams • Realistic timelines • Enthusiasm and sense of ownership • Communicate post implementation support and training • Success Publicity and recognition for involvement • Technical support / JIT training
Estimated Timelines - Most published articles indicate that school personnel should take their best timeline estimates and DOUBLE them. • Break up the timeline into phases or waves (eRate) • Be cautious of vendor timelines: if it sounds too good … • Don’t make promises • Don’t forget the conversion timeline! • Speak to other districts that went through a similar SIS transition Sample Timelines PowerSchool Mount Diablo Morris Hills SLEDTECH.org Ohio State University
Training / Staff Development • Define when / how staff will be trained • Try to limit training to no more than two hours at a time • Plan training for specific user groups • Communicate to staff “who to call when…” • Create experts or area specialists • External people aren’t necessarily better but they help validate what is being done • Have vendor include some training in proposal
Other • Hardware • Database (dBase, FileMaker, Oracle, RDM, SQL, Visual FoxPro, etc) • Maintenance / upgrades • Backups • Who is responsible? • External interfaces • SIF ( www.sifinfo.org )
Resources • "The Evolution of Student Information Systems," T.H.E. Journal, 10/1/2005, http://www.thejournal.com/articles/17446 • http://www.techlearning.com/showArticle.php?articleID=19400338 • http://www.crawleyinc.com/newsletters/March05/March05.pdf • http://www-03.ibm.com/industries/education/doc/content/solution/390886110.html Neil Charles ncharles@mhrd.k12.nj.us Morris Hills Regional District TechSpo 2008