Institute of Learning · MBRU · Academic pack, 26 workflows · Generated from the documents, 2 September 2026
IoL Data Lineage
Data reaches IoL from fourteen units across MBRU, not from one office. Every academic workflow states, in its section 7, the data it generates: what, at which step, by whom, and where it lands. Read together, those 298 rows are the academic pack's data map. This page draws it and asks the only question that matters for OBEF: does each piece of data have a home?
1. Where the data goes, and which points it serves
Left, the workflow that captures it. Middle, where it lands. Right, the KPI it serves, sized by the number of data elements feeding it. Hover any ribbon for the count; click a node to isolate its paths.
CHEDS templateIoL register (mostly still to build)Submission or other systemNo home yetOBEF KPI
Figure 1. Two thirds of the academic pack's data lands directly in a CHEDS template column, which is the good news: the Ministry's own schema is most of the data model. The orange ribbons are the registers the pilot still has to build, and the red ones are data with no named destination at all.
2. Does the data have a home?
Per workflow, how many of its data elements land in a CHEDS column, in a named IoL register, in the submission itself, or nowhere yet. A workflow whose bar is mostly orange or red is a workflow whose points depend on a register that does not exist.
CHEDS templateIoL registerSubmission or other systemNo home yet
Figure 2. WF-25 alumni outcomes generates the most data and depends most on a register that does not yet exist, which is the same conclusion the maximisation plan reached from the weights. WF-09 assessment lives almost entirely in the assessment repository, because nothing in CHEDS carries KPI 2.1.
3. How exposed is each KPI?
Elements feeding each KPI, and from how many workflows. A KPI fed by one workflow has one point of failure. Weight is the programme-level weight.
Figure 3. KPI 2.1 assessment quality is fed from 8 workflows, which is a reconciliation problem: every contributor must agree on the same denominator. KPI 4.6 is fed from a single workflow, which is a resilience problem. The red segments are elements with no home yet, concentrated in KPI 2.1 assessment quality, where nothing in CHEDS carries the assessment repository.
4. Who collects it
The data does not come from one office. Fourteen units capture it, six reporting to Academic Affairs, six to Administrative Affairs, Quality and IQA independently to the Senior Director, and 78 of the 298 elements are assigned to a generic "Data Steward" that names no unit at all. Each cell is the number of data elements a unit captures for a KPI; darker is more. A KPI with many dark cells in its column is a KPI IoL has to assemble from several departments.
Academic AffairsAdministrative AffairsIndependent or leadershipUnassigned
Figure 4. The bar at the left of each row is the affair the unit reports to under the ownership decision of 2 September 2026. The largest row is the one without a name. Every element assigned to a generic Data Steward is an element whose real collecting department has not yet been decided, and it is the first thing to fix before any department is asked to capture anything.
5. Every data element
Workflow
KPI
Data element
Capture point
Captured by
Unit
Affair
Destination
Level
Source: section 7 of each document in IoL Pilot/Workflows/. Regenerate when a document changes; do not edit this page by hand.