SITS:Vision to Microsoft Fabric: HESA Data Futures and Student Analytics for UK Universities
SITS:Vision student records flow through raw, cleaned and measures layers in Microsoft Fabric into Power BI reporting.
UK universities are asked for more data, more often, and with less tolerance for error. Student numbers, continuation and completion measures, and the in-year returns that followed HESA Data Futures all draw on the same student records, yet the reports that leaders use day to day are often built separately from them. Connecting SITS:Vision to Microsoft Fabric gives an institution one governed, reusable foundation for regulatory returns, retention analysis and planning, without asking staff to rekey or reconcile spreadsheets.
This guide is for pro-vice-chancellors, registrars, directors of planning, data and student systems, and the IT leaders who support them. It explains the pressure on reporting, what Fabric adds to SITS:Vision, the realistic ways to get the data across, and the governance decisions to make before the first load.
Why University Reporting Is Under Pressure
The Office for Students notes that the original Data Futures programme concluded in 2024 and that an in-year student data collection programme launched in 2025. Whatever the detail of each return, the direction is clear: student data is expected to be accurate sooner, and institutions are expected to explain it. Alongside that sit regulatory measures such as continuation, completion and progression, and the internal questions about retention, engagement and recruitment that leadership asks every term.
Most institutions answer these questions from several places. The student record answers some, the learning environment, attendance, finance and CRM systems answer others, and the planning team joins them by hand. The cost is late numbers, versions that disagree, and specialist staff spending the weeks before a deadline reconciling data instead of analysing it.
What SITS:Vision Holds, and Where Analytics Stops
SITS:Vision, from Tribal, is a student record system that many UK universities use to manage the student lifecycle. It is the system of record, and it is built to run admissions, enrolment, progression and awards rather than to support analysis across the whole institution. Its data is usually held in an Oracle database, though the platform and hosting model vary by institution and should be confirmed.
That design is sensible for operations and limiting for analytics. Reporting against the live system competes with day-to-day processing, definitions are held in custom reports that few people maintain, and combining student records with engagement, finance or recruitment data is hard to do repeatably. Fabric does not replace SITS:Vision. It gives the institution a governed copy of the data that analysts can use freely.
Why Microsoft Fabric Fits the Higher Education Sector
Many universities already run Microsoft 365, Azure and Power BI, so identity, licensing and security are familiar. Fabric brings OneLake storage, pipelines, notebooks, a warehouse and Power BI into one environment billed against a single capacity, which keeps the platform manageable for a lean data team.
Capacity can be placed in a UK Azure region, which supports data residency requirements, although the final position belongs in your data protection impact assessment. Because the same platform serves planning, student support and finance, one set of agreed definitions can feed every dashboard, so the planning office and the faculty stop producing different answers.
How SITS:Vision Data Gets Into Fabric
The right route depends on who runs the SITS:Vision database and what your agreement with Tribal allows. We have not assumed one option. It is settled in a short discovery before anything is recommended.
| Route | When it fits | Check first |
|---|---|---|
| Mirroring from the Oracle database | The university controls the database and the vendor supports the approach | Oracle version, LogMiner and archive logging, vendor support position, load on the live system |
| Scheduled pipeline copy through a gateway | Mirroring is unavailable or not permitted | Refresh window, query load, keys that identify changed records |
| Vendor-hosted data access | Tribal hosts the environment | What data access the agreement includes and how often it can refresh |
| Existing extracts or a data warehouse | Reporting already depends on them | Which fields and how much history are missing |
Microsoft documents Oracle mirroring as using LogMiner, with archive log mode, supplemental logging and an on-premises data gateway as prerequisites, so check its current status and limits before relying on it. Whichever route you choose, the goal is the same: a trusted copy refreshed on an agreed schedule, with the live student record left alone. If other platforms are moving at the same time, our Microsoft Fabric migration approach shows how they fit one plan.
Building a Student Data Model That Reconciles to Data Futures
Design the model around the questions you must defend: who is enrolled, on which course and mode, at what point in the year, and what happened to them. A layered approach keeps this manageable. Keep a raw copy of the SITS:Vision tables, a cleaned layer where students, courses and cohorts carry one agreed definition each, and a measures layer that Power BI reads.
Build a reconciliation view from the start. It compares internal counts with what was submitted, so differences are found and explained before a deadline rather than after. Keep history, because continuation and progression questions need to compare cohorts over time, and a snapshot of today does not answer them.
- Fabric does not replace SITS:Vision. It adds a governed copy of student data that supports returns, retention analysis and planning.
- The route into Fabric depends on who runs the database and what your agreement with Tribal allows, so confirm both first.
- Oracle mirroring has specific prerequisites and a status that changes, so check the current Microsoft documentation before relying on it.
- Build a reconciliation view and keep history from the first release, so every submitted number can be explained.
- Start with one question, such as continuation, agree the definition, and ask for a short discovery to confirm the route for your institution.
Governance, UK GDPR and Student Data
Student data is personal data, and some of it is special category data. Bring it into Fabric with a clear lawful basis, a data protection impact assessment and a retention rule, and keep personal identifiers out of datasets that do not need them.
Row-level security lets a head of school see their own students while the planning office sees the whole institution. Separate workspaces for sensitive and general reporting, and an audit of who opens what, complete the picture. Our data governance consulting work and the Power BI Governance Platform keep these controls in place as the estate grows.
What to Build First and Next Steps
Start small. A continuation and retention view for one faculty, an enrolment against target view, and one reconciliation report are enough to prove the foundation and earn trust. Each needs a written definition agreed by planning, registry and the faculty before it is built. Our Power BI consulting team designs the models and reports on top of that foundation.
A short discovery confirms how your SITS:Vision environment is hosted, what data access you have, and which five or six questions the first release should answer. Numlytics designs and builds Microsoft Fabric data platforms and Power BI reporting. Speak with a certified consultant to map your student data to a model that stands up to scrutiny.