Skip to content

Axis Wise Education · Institutional platforms · DAT 504

Collect once.
Answer everything.

One source of truth for institutional data: students, staff, programs, research. Captured once at the source, governed by agreed definitions, and served to every report, portal, and platform that asks.

Prospectus entry

Course
DAT 504
Field
Institutional data management
Prerequisites
None: this is the prerequisite
Duration
Registry live in 8–12 weeks
Assessment
A census that agrees with itself
Offered by
Axis Wise Education
StatusIntake open

Fig. DAT.2The census

One question, five answers.

Ask around your institution: “How many students do we have?” Then watch the answers arrive: each one confident, each one different.

Census: “how many students do we have?”Five answers
The registryEnrolled and active, as of this morning.12,480
The LMSEveryone who logged in this semester.11,902
FinanceEveryone who was billed.12,733
The websiteA proud, round marketing number.13,000+
Last year’s ranking submissionWhatever definition fit the template.12,199

Disagreement1,098 students wide

Defensible answersAll five

Every one of those numbers is defensible. That’s precisely the problem, and no dashboard can fix it from above.

Fig. DAT.3The catalog

Written once. Borrowed everywhere.

The discipline works like a library: every record catalogued once, with an owner and a version, then borrowed by whoever needs it. Never copied.

Catalog: record STU-2024-8817Version 1: the only one
Record
Enrolment: B.Eng Software
Captured
At the registry, on day one
Validated
Rules v4: at entry, not at year-end
Owner
Registry (named, not implied)

Borrowing history

Ministry template, Q3

Regenerated from source each quarter

generated

Ranking submission

Served through the ranking body’s own definitions

mapped

Accreditation exhibit 4.2

Cited with evidence attached

linked

Dean’s dashboard

Read live, never exported

live

Student portal

The student sees their own record, and can flag errors

scoped

Copies made0

Re-keyedNever

That’s the whole discipline: records are borrowed, never copied. The moment data is copied, it starts to lie.

Fig. DAT.4The modules

What the course covers.

Five modules that turn scattered records into an institutional registry:

DAT 541

The registry

Master records for students, staff, programs, and research: each with one home, one owner, and one version of the truth.

One record per fact

DAT 542

Integration & collection

SIS, LMS, finance, HR, and research systems connected: data captured once at the source and never typed twice.

Collected once, at source

DAT 543

Definitions & governance

The data dictionary that ends the definition wars: every term agreed, owned, versioned, and encoded so systems enforce what committees decided.

A peace treaty, enforced

DAT 544

Quality & validation

Rules that catch errors at entry instead of inside a ranking submission, with completeness and freshness visible per office.

Errors caught at the door

DAT 545

Serving & access

Feeds and APIs serving analytics, portals, accreditation, and AI: role-scoped, audit-trailed, and always the current version.

Truth on tap

Fig. DAT.5Entry requirements

Not every institution needs this yet.

The honest admissions policy. Foundations pay off in specific conditions:

Wait a semester when

  • The institution is small enough that one spreadsheet genuinely is the truth
  • Core records still live on paper: digitisation comes first
  • Nobody on the org chart owns data: sponsorship before systems
  • You need one report fixed, not a foundation laid

Enrol now when

  • Basic counts differ depending on which office you ask
  • Every new report starts from zero, again
  • One irreplaceable person knows where everything lives
  • Analytics, accreditation, or AI projects keep stalling on “the data isn’t ready”

This is the course the other five stand on, and the first thing that stands on it is usually reporting.See what it carries: Institutional Analytics

Fig. DAT.6The syllabus

A semester, well spent.

No boiled oceans. A phased foundation with a visible win early: the census starts agreeing within weeks.

Weeks 1–3

01Orientation

The honest inventory: every system, every owner, every definition in dispute, and the real state of quality. Findings are yours regardless.

An honest inventory

Weeks 3–6

02The dictionary

Definitions negotiated, agreed, and written down, with owners and versions. The political work, facilitated; the outcome, encoded.

A peace treaty on definitions

Weeks 6–12

03The registry

Master records live, sources connected, the first domains flowing: usually students and programs first.

One registry, live

Weeks 12–16

04Quality gates

Validation at entry, completeness dashboards per office, and the census run again, in agreement with itself.

Errors caught at the door

Ongoing

05Stewardship

New sources, new fields, new askers: absorbed as configuration, not projects. The truth stays true.

Truth that stays true

The truth stays in-house.

  • Master records
  • Data dictionary
  • Pipelines
  • Documentation

Fig. DAT.7Office hours

Questions, answered straight.

Is this just a data warehouse?

A warehouse is one component. The course is the whole discipline: master records with owners, agreed definitions, quality gates, and serving, measured by a business outcome, not a technology one: every question gets one answer.

Our SIS vendor says their product already is the single source of truth.

For what it captures, it genuinely is, and it stays that way. But institutions run on many systems, and the registry sits above them as the neutral layer where their records are joined, governed, and served. We don’t replace your SIS; we make it one well-behaved citizen among several.

Our definition fights are political, not technical.

Correct, which is why the dictionary stage is facilitated negotiation, not a schema exercise. What the system adds is enforcement and honesty: agreed definitions get encoded, exceptions get named, and disagreements become visible instead of surfacing inside a ranking submission.

Doesn’t centralising data increase our privacy risk?

The opposite, in practice. Today your student data travels by email attachment and lives in unnumbered spreadsheet copies. A registry means fewer copies, role-scoped access, audit trails, and retention rules, which is what your data-protection law has been asking for all along.

We tried a data project before. It died.

They usually die from the same three causes: boiling the ocean, no named owners, and no visible win before the sponsor loses faith. This syllabus is built against all three: phased domains, owners from day one, and a census that agrees with itself inside the first term.

How is it priced?

Fixed quotes per stage, starting with a small Orientation fee: every stage documented in committee-ready language, because a foundation project lives or dies by its sponsorship paperwork.

Fig. DAT.8Enrolment

Ask five offices one question.

If you get five answers, we should talk. One conversation to map your sources and definitions, and a committee-ready plan to make the next census agree with itself.

Malaysia · Working worldwide