Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Administration It topic

No spam. Unsubscribe anytime.

Spring ISD outlines Aeries student‑information rollout, integration issues and next steps

2496651 · March 5, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

District IT and operations summarized the move from eSchool to Aeries, described data validation and process gaps during the July 2024 go‑live, and said further targeted training and integration work with third‑party systems (DecisionEd, Schoology, reporting feeds) remain priorities.

Spring Independent School District on March 4 provided a status update on the district’s transition to the Aeries student information system, describing project milestones, implementation challenges and planned remedies after a July 2024 go‑live.

Why the change: District leaders said the legacy system (eSchool) had reached end‑of‑life and that Aeries offered a modern, cloud‑based system with built‑in integration points to many of the district’s other applications.

Implementation and issues: The project began with vendor selection in 2021–22 and a June 2022 board approval. District staff reported a multi‑year data conversion (seven years of historical records) and staged training (28 pre‑launch events and 51 post‑launch sessions). IT acknowledged several implementation issues that affected users: incomplete data validation between the legacy and new system, process gaps where campus workflows and the new system did not initially align, and resource constraints because the SIS team was performing implementation work while also supporting day‑to‑day operations.

Aeries integrations: Aeries was described as having stronger third‑party integration capability, but staff said some integrations with existing tools (DecisionEd analytics, Schoology gradebook sync and other applications) required additional tuning. IT indicated those integrations are being refined and that ServiceNow ticketing is used to prioritize and track issues.

Teacher and campus feedback: System engineers and a band director who uses the system from the field recounted successes and common user problems: Aeries gradebook sync with Schoology can pass grades and teacher notes into the district gradebook (reducing double entry) when configured correctly, but initial configuration errors and unfamiliarity with new workflows caused teacher frustration. IT staff described one‑on‑one support visits in schools and said some teachers reported immediate time savings after fixes.

District next steps: IT and the SIS team committed to continued training (online modules plus live refresh sessions), robust ServiceNow tracking of recurring issues, and tighter coordination with Aeries and other vendors to resolve integration items. Officials said the district retains access to eSchool as a fallback and is conducting targeted outreach to campus users to find systemic problems that need additional training or configuration changes.

Trustee questions and requests: Board members asked whether a pilot could have limited rollout risk (district said timeline and legacy system end‑of‑life constrained options), whether Aeries provided on‑site vendor support during the initial weeks, and whether auditors or external reviewers should assess the implementation. Trustees also asked for follow‑up reporting to document remaining gaps, impacts to state reporting and transcript integrity for graduating students.

Ending: IT said it will produce a follow‑up with detailed issue categories, a training schedule and confirmation that transcript and state reporting feeds are accurate.