Custom & recursive mapping
Build Assessment, CLO and PLO pathways, then create your own frameworks and map one custom framework to another—even in multi-level chains.
OBE KitAI is a standalone outcome-based education (OBE) management platform developed by MovKitAI PLT in Sarawak, Malaysia. It helps universities manage course learning outcomes (CLOs), programme learning outcomes (PLOs), attainment, academic reports and continuous quality improvement (CQI) without replacing their existing learning management system (LMS) or other campus systems.
Rooted in Sarawak, Malaysia, where “Kitai” means “us”, the name OBE KitAI carries a simple yet meaningful idea: our OBE. It reflects the shared responsibility of educators and institutions in advancing outcome-based education through collaboration and continuous improvement in teaching and learning.
Your university may already have a learning management system (LMS), student information system, and established admissions and enrolment workflows. You should not have to replace them just to improve outcome-based education.
OBE KitAI is a standalone OBE management solution focused on outcome frameworks, CLO/PLO mapping, attainment analysis, academic reporting and continuous quality improvement. Adopt a dedicated OBE platform while your existing teaching and administrative systems remain in place.
Outcome frameworks · CLO/PLO mapping · Attainment · Reports · CQI
OBE KitAI does not require LMS replacement. Any automated data exchange or system integration depends on the institution’s implementation and available interfaces; it is not implied by this illustration.
Configure evolving outcome frameworks, examine genuine programme differences, extend your evidence and finish review cycles with less administrative effort.
Build Assessment, CLO and PLO pathways, then create your own frameworks and map one custom framework to another—even in multi-level chains.
Shared courses receive an Overall report across enrolled students and separate programme-specific views with their respective outcome mappings.
Recognise that a course may be core for one programme but optional for another. Calculate cohort attainment using the correct programme-specific core-course scope.
Name numeric indicators such as Pass Rate (%), Student Feedback Score or any other measurable result. Add reporting columns without an application-code or schema change.
Surface outcomes needing attention, document continuous-improvement actions and support follow-up reviews across teaching offerings.
See incomplete course tasks and send targeted reminder emails identifying what each lecturer still needs to complete.
Start semester-level Course Report ZIP downloads and cohort Student Report email workflows—without opening reports one at a time.
Disclose calculation basis, assessment weighting, PLO mapping strengths, threshold values and optional assessment-weight allocation summaries in reports.
Use controlled administrative roles, audit trails, encrypted live data and read-only signed external attainment API access.
For each custom mapping framework, independently enable or disable Calculate Attainment at the programme/semester framework baseline. Definitions and mappings remain available even when its attainment is disabled.
Enable optional Report weights for CLO and Assessment-mapped custom frameworks. Reveal how assessment Marks are allocated—for example, 60% Secure and 40% Non-secure assessment evidence.
Switch Action Plan requirements on or off for each programme. Course teams can also enable or disable the one-assessment-to-one-CLO mapping check.
Not every educational objective fits neatly into standard CLO and PLO structures. Create new outcome frameworks and link them to your existing evidence—without rebuilding the application for every emerging academic priority.
Define Sustainable Development Goal-related outcomes and map relevant curriculum evidence to the SDG dimensions your institution chooses to assess.
Custom outcomesDescribe values or graduate attributes, map them from PLOs or other framework outcomes, and report attainment using the mappings you configure.
Cross-framework mappingDefine emerging competencies such as responsible AI use, AI literacy or critical evaluation as assessable outcomes within your own framework.
Future-ready assessmentThese are possible institution-defined frameworks. OBE KitAI does not claim to predefine their outcome descriptions, assess AI use automatically or assign SDG attainment without configured evidence and mappings.
Define assessment, CLO and PLO relationships—and go beyond them. Administrators can create additional frameworks, map them directly from assessments, CLOs or PLOs, or connect a new framework to one already created. Recursive chains remain calculable without hardcoding a new report structure.
Not every framework needs a score today, and not every programme follows the same review process. Turn supported calculations and requirements on or off without removing curriculum mappings or rewriting the system.
Administrators can define an Assessment-mapped framework—for example, to categorise assessment design in an AI world—and enable Report weights to show each outcome's share of configured assessment Marks.
Example percentages require suitable configured assessment Marks and mappings. The system calculates allocations; it does not automatically judge whether an assessment is secure, AI-resilient or non-secure. An assessment mapped to multiple outcomes may contribute to each one, so not every framework's outcome percentages must sum to 100%.
Academic programmes share courses—but not always the same curriculum requirements. OBE KitAI identifies Core Courses separately for each programme and admission cohort , so overall cohort outcome calculations follow the appropriate programme structure.
It also distinguishes programme-specific outcome mappings and the latest applicable repeated-course result, instead of treating every enrolment as an identical requirement.
Explore the cohort report| Course | Programme A | Programme B |
|---|---|---|
| COURSE 101 | Core | Optional |
| COURSE 202 | Optional | Core |
| COURSE 303 | Core | Core |
View each course's mapping-framework attainment within the selected cohort, including optional courses; overall cohort attainment follows programme-specific Core Course rules.
| Course / teaching semester | PLO1 | PLO2 | PLO3 | PLO4 | PLO5 | PLO6 | PLO7 | PLO10 | PLO11 |
|---|---|---|---|---|---|---|---|---|---|
| COMP1104 — Introduction to Algorithms2025 Semester 1 | 87.4% | 82.1% | 79.6% | – | – | 91.5% | – | – | – |
| ISYS1203 — Fundamentals of Information Systems2025 Semester 1 | 77.2% | 73.8% | – | 80.4% | – | – | 68.7% | – | – |
| ISEC2201 — Secure Systems2025 Semester 2 | – | 81.5% | 84.3% | – | 78.5% | – | 74.6% | – | – |
| COMP2106 — Object-Oriented Application Development2025 Semester 2 | 89.8% | 85.2% | 83.6% | – | 88.1% | – | – | – | – |
| NETW2102 — Data Communication Systems2025 Semester 2 | 74.6% | 72.9% | – | – | – | 77.3% | 76.8% | 70.2% | – |
| ISYS2303 — Database Applications2026 Semester 1 | 82.3% | 79.7% | 77.4% | 75.1% | – | – | – | – | 73.9% |
| COMP3105 — Distributed Application Systems2026 Semester 1 | 90.1% | – | 86.2% | 84.5% | – | 88.9% | – | 81.4% | 79.2% |
| Average | 83.6% | 79.2% | 82.2% | 80.0% | 83.3% | 85.9% | 73.4% | 75.8% | 76.6% |
Overall PLO attainment is calculated using the selected programme's applicable Core Courses. Outcome visualisations below use fictional example results.
Sample programme-level core-course outcomes. The bar chart, donut and radar are rendered in HTML, CSS and SVG—not as a screenshot. Values are illustrative.
Evidence at every level of outcome-based education. Explore Course, Student and Cohort Reports recreated from the actual OBE KitAI report designs—with clear mapping tables, attainment charts and calculation bases, but entirely fictional academic data.
See the genuine report sequence: mapping results, assessment attainment, overall CLO/PLO calculations and separate programme-specific outcome summaries.
An Assessment → CLO matrix displays the attainment of each mapped assessment. A dash indicates that no mapping exists.
| Assessment | CLO1 | CLO2 | CLO3 |
|---|---|---|---|
| Quiz | 90.0% | – | – |
| Project | 75.0% | 75.0% | – |
| Final Exam | – | 80.0% | 80.0% |
| Assessment | Mapped CLO(s) | Marks | Attainment |
|---|---|---|---|
| Quiz | CLO1 | 20 | 90.0% |
| Project | CLO1, CLO2 | 30 | 75.0% |
| Final Exam | CLO2, CLO3 | 50 | 80.0% |
In this fictional example, 18, 15 and 16 of 20 learners respectively meet the 50% pass threshold for Quiz, Project and Final Exam. CLO values are the Marks-weighted average of their mapped assessment attainment.
| Outcome | Description | Calculation Basis | Attainment | Threshold | Status |
|---|---|---|---|---|---|
| CLO1 | Explain core digital system principles | Quiz (20), Project (30) | 81.0% | 50% | Attained |
| CLO2 | Implement and test integrated components | Project (30), Final Exam (50) | 78.1% | 50% | Attained |
| CLO3 | Evaluate system reliability | Final Exam (50) | 80.0% | 50% | Attained |
| Outcome | Calculation Basis | Attainment | Threshold | Status |
|---|---|---|---|---|
| PLO1 | CLO1 (3), CLO2 (3) | 79.6% | 50% | Attained |
| PLO2 | CLO2 (3), CLO3 (3) | 79.1% | 50% | Attained |
Each programme has ten fictional enrolled learners. Programme PLOs are calculated from the respective programme’s CLO attainment, rather than copied from the Overall values.
| Calculation Scope | PLO1 | PLO2 |
|---|---|---|
| Overall · 20 enrolled students | 79.6% | 79.1% |
| B-DIGTECH · 10 students | 77.1% | 78.1% |
| B-SOFTDES · 10 students | 82.0% | 80.0% |
Trace an individual learner’s latest applicable mapped outcomes back to their attempted courses and reported PLO values.
Programme-specific overall attainment is calculated from configured Core Courses. If a course is repeated, only the latest calculable offering contributes; historical attempts remain visible.
| Outcome | Description | Calculation Basis | Attainment | Threshold | Status |
|---|---|---|---|---|---|
| B-DIGTECH / PLO1 | Apply fundamental computing knowledge | DGT2102: CLO1 (3); DGT2204: CLO1 (3); DGT1101: CLO1 (3) | 81.3% | 50% | Attained |
| B-DIGTECH / PLO2 | Analyse and solve digital technology problems | DGT2102: CLO2 (3); DGT2204: CLO2 (3); DGT1101: CLO2 (3) | 76.0% | 50% | Attained |
| B-DIGTECH / PLO3 | Develop and evaluate digital solutions | DGT2204: CLO3 (3); DGT1101: CLO3 (3) | 82.0% | 50% | Attained |
A programme and teaching semester accompany each course-level result. All three listed courses are fictional Core Courses for this synthetic example.
| Programme | Course | Semester | Outcome | Attainment | Threshold | Status |
|---|---|---|---|---|---|---|
| B-DIGTECH | DGT2102 — Applied Digital Systems | 2025 Semester 2 | PLO1 | 80.0% | 50% | Attained |
| B-DIGTECH | DGT2102 — Applied Digital Systems | 2025 Semester 2 | PLO2 | 72.0% | 50% | Attained |
| B-DIGTECH | DGT2204 — Software Design Studio | 2025 Semester 1 | PLO1 | 88.0% | 50% | Attained |
| B-DIGTECH | DGT2204 — Software Design Studio | 2025 Semester 1 | PLO2 | 84.0% | 50% | Attained |
| B-DIGTECH | DGT2204 — Software Design Studio | 2025 Semester 1 | PLO3 | 88.0% | 50% | Attained |
| B-DIGTECH | DGT1101 — Computing Foundations | 2025 Semester 1 | PLO1 | 76.0% | 50% | Attained |
| B-DIGTECH | DGT1101 — Computing Foundations | 2025 Semester 1 | PLO2 | 72.0% | 50% | Attained |
| B-DIGTECH | DGT1101 — Computing Foundations | 2025 Semester 1 | PLO3 | 76.0% | 50% | Attained |
For DEMO-001, DGT2102 contributes PLO1 = 80.0% and PLO2 = 72.0%. Student-level PLO values are averaged across the Core Courses that have a calculable result for each outcome.
Follow the report’s sequence: cohort scope and learner list, PLO attainment with three charts, calculated custom outcomes, and outcome-by-course matrices.
Repeated-course policy: for each learner and course, attainment uses the latest semester with a recorded and calculable result; earlier attempts are not averaged into the cohort result.
| No. | Student ID | Courses Attempted |
|---|---|---|
| 1 | DEMO-001 | 3 |
| 2 | DEMO-002 | 3 |
| 3 | DEMO-003 | 3 |
| 4 | DEMO-004 | 2 |
| 5 | DEMO-005 | 2 |
Showing five of ten entirely fictional learner identifiers in this compact demonstration.
| Outcome | Description | Calculation Basis | Attainment | Threshold | Status |
|---|---|---|---|---|---|
| PLO1 | Disciplinary knowledge and its applications | DGT2102: CLO1 (3), CLO2 (3); DGT2204: CLO1 (3); DGT1101: CLO1 (3) | 78.0% | 50% | Attained |
| PLO2 | Critical analysis and problem-solving | DGT2102: CLO2 (3), CLO3 (3); DGT1101: CLO2 (3) | 74.0% | 50% | Attained |
| PLO3 | Solution design, integration and testing | DGT2204: CLO2 (3), CLO3 (3); DGT1101: CLO3 (3) | 82.0% | 50% | Attained |
| PLO4 | Professional communication and collaboration | DGT1101: CLO3 (3) | 70.0% | 50% | Attained |
Calculation Basis always identifies the source course, including where only one course contributes to a PLO.
This fictional framework is directly mapped from the final cohort PLO percentages (equal-weight Approach B).
| Outcome | Description | Calculation Basis | Attainment | Threshold | Status |
|---|---|---|---|---|---|
| CGC1 | Custom graduate capability 1 | PLO1, PLO3 | 80.0% | 50% | Attained |
| CGC2 | Custom graduate capability 2 | PLO2, PLO4 | 72.0% | 50% | Attained |
| CGC3 | Custom graduate capability 3 | PLO3, PLO4 | 76.0% | 50% | Attained |
The recursive mapping uses the updated CGC attainment (PLO → CGC → VALUE), not earlier student-level CGC results.
| Outcome | Description | Calculation Basis | Attainment | Threshold | Status |
|---|---|---|---|---|---|
| VALUE1 | Institution-defined capability value 1 | CGC1 | 80.0% | 50% | Attained |
| VALUE2 | Institution-defined capability value 2 | CGC2 | 72.0% | 50% | Attained |
Rows show fictional Core Courses and columns the mapped programme outcomes; a dash means no mapped result. The Average row excludes dashes. This particular synthetic sample has equal, complete course contributions for each available outcome, so the visible column means agree with the programme-level PLO summary.
| Core Course | PLO1 | PLO2 | PLO3 | PLO4 |
|---|---|---|---|---|
| DGT2102 — Applied Digital Systems | 77.1% | 78.1% | – | – |
| DGT2204 — Software Design Studio | 78.5% | – | 82.0% | – |
| DGT1101 — Computing Foundations | 78.4% | 69.9% | 82.0% | 70.0% |
| Average · available values only | 78.0% | 74.0% | 82.0% | 70.0% |
The second branch follows PLO2 (74.0%) and PLO4 (70.0%) → CGC2 (72.0%) → VALUE2 (72.0%). CGC3 combines PLO3 (82.0%) and PLO4 (70.0%) for 76.0%.
Illustrative reports only. All student IDs, course codes, programme names, descriptions and numerical examples in these previews were created for this demonstration. No university logo, real academic record or identifying student information is used.
Pass Rate (%). Student Feedback Score. Assessment Completion (%). Industry Engagement (%). Administrators define their own numeric reporting field names and enter values for the relevant courses—without changing application code or adding hardcoded report fields.
Numeric Additional Reporting values can appear alongside CLO/PLO attainment and in applicable cohort-level summaries. Define a meaningful heading, enter numeric evidence, and report it across courses.
| Course | Pass Rate (%) | Feedback (1–5) | Engagement (%) |
|---|---|---|---|
| COURSE 101 | 87 | 4.3 | 65 |
| COURSE 202 | 93 | 4.6 | 70 |
| COURSE 303 | 89 | 4.2 | 82 |
Configure assessments, CLOs, PLOs and recursively linked custom outcome frameworks.
Capture marks and administrator-defined additional reporting values with validation.
Check thresholds, compare programmes and cohorts, and identify areas requiring action.
When Action Plans are enabled for the programme, document improvements, revisit actions in later offerings and close the loop through follow-up review.
View the previous offering's action, record its follow-up and document the current offering's Action Plan in the same Continuous Improvement panel.
NETW2102 — Data Communication Systems / 2025 Semester 2
| Previous Offering Action Plan | Follow-up on Previous Action Plan | Existing Semester Action Plan |
|---|---|---|
| 2025 Semester 1 During the previous offering, students struggled with diagnosing network faults. Introduce guided protocol-analysis workshops and short diagnostic exercises before the final assessment. 185 characters |
200 characters · must be >100 |
The application displays a three-column Continuous Improvement table. When applicable, a follow-up is required for an earlier Action Plan longer than 100 characters; a required current Action Plan must also exceed 100 characters. Programme-level Action Plan settings can disable this requirement.
OBE KitAI combines its completion checklist with targeted communication and practical bulk outputs—so quality teams can focus on the evidence, not repetitive clicking.
Review each course's outstanding OBE tasks. Identify which lecturers have not completed their work, then send a reminder email listing the specific missing actions.
Start a cohort Student Report email run with one action. Eligible students receive their own report using the configured institutional-address rules.
Choose a programme and teaching semester, then initiate one bulk Course Reports ZIP workflow instead of downloading each course report separately.
Real workflows apply eligibility and once-per-day email protections. Large exports or cohort email runs are processed in bounded batches rather than one unbounded request. These panels are illustrations, not functional email controls.
The actual checklist identifies lecturer-side requirements, continuous improvement and separate programme-review status in one consolidated view.
Scope: Programme A · Semester: 2025 Semester 2
| Programme | Course | Lecturer | CLO & OBE Framework | Assessment Configuration | Students & Marks | Continuous Improvement | Programme Review | Overall |
|---|---|---|---|---|---|---|---|---|
| Programme A Threshold 50% | NETW2102 Data Communication Systems | Lecturer A Assigned | ✓ CLO: 4 defined✓ CLO → PLO mapped | ✓ Assessments configured✕ Assessment → CLO incomplete | ✓ Students enrolled✕ Marks: 62 / 80 | Action Plan: Pending marksPrevious Follow-up: Not required | Not Ready | Incomplete |
| Programme A Threshold 50% | COMP1104 Introduction to Algorithms | Lecturer B Assigned | ✓ CLO descriptions✓ Framework mapping | ✓ Assessments complete | ✓ Marks: 96 / 96 | ✓ Action Plan completed✓ Previous Follow-up | Pending Review | Pending Review |
| Programme A Threshold 50% | ISEC2201 Secure Systems | Lecturer C Assigned | ✓ CLO: 3 defined✕ PLO mapping incomplete | ✕ Assessment weights: 80 / 100 | ✕ Missing marks | Action Plan: Pending marks | Not Ready | Incomplete |
| Programme A Threshold 50% | ISYS2303 Database Applications | Lecturer D Assigned | ✓ CLO/Framework complete | ✓ Assessment configuration | ✓ Marks: 120 / 120 | ✓ Continuous Improvement | Reviewed | Complete |
Incomplete = outstanding lecturer-side work; Pending Review = work ready for administrator review; Complete = required checklist items and programme reviews are current. The reminder action is displayed as a disabled demo, not a live email button.
OBE KitAI combines structured academic workflows with controls intended to support accountability, traceability and responsible access to student assessment information.
Adapt OBE to your institution’s needs with customisable outcome frameworks, flexible mappings, attainment calculations, and additional reporting. Enable or disable features independently for each programme, allowing different programmes to adopt different configurations—all within one unified platform.
Designed for academic teams that need clarity without losing the detail.
In Sarawak, “Kitai” means “us”. That is the inspiration behind the name OBE KitAI: our OBE, or even our OBE kit. It reflects an approach to outcome-based education shared by academic teams.
No. OBE KitAI is a standalone outcome-based education management platform designed to complement existing university systems. Institutions can continue using their current LMS, student information, admissions and enrolment systems while using OBE KitAI for outcome mapping, attainment, reporting and CQI. Data transfer or automated integration, if required, depends on the available interfaces and the institution’s implementation.
Yes. A framework can source its outcomes from Assessment, CLO, PLO or a previously defined custom framework. Multi-level chains are supported, while circular dependencies are handled safely through validation that detects and prevents invalid circular mappings.
Yes. SDG, VBE and AI-assessment criteria can be represented as administrator-defined custom frameworks. Administrators create the relevant outcomes and mappings; these frameworks and their criteria are not automatically evaluated without configuration.
Yes. Administrators give numeric indicators their own headings and enter numerical values without asking a developer to change application code.
Yes. Course reports distinguish overall attainment across the enrolled student scope from programme-specific outcomes and calculations. Cohort reports also use the Core Courses defined for the relevant programme, even when another programme treats the same course as optional.
Checklist & Review identifies outstanding course tasks for lecturer reminders. Bulk Student Report email and selected-semester Course Report ZIP workflows minimise individual report-by-report handling; email eligibility and batching safeguards apply.
Outcome attainment and thresholds help identify improvement needs. Academic staff can document action plans and later review their effectiveness, supporting the close-the-loop process rather than claiming that educational decisions are automatic.
Unit Reports · Overall and programme-specific ULO/PLO attainment for the same teaching offering.
| Outcome | Description | Attainment |
|---|---|---|
| ULO1 | All-enrolled ULO attainment | 83% |
| PLO1 | Overall all-enrolled scope | 82% |
Programme-specific ULO and PLO attainment
ULO1 · 80% PLO1 · 85%Programme-specific ULO and PLO attainment
ULO1 · 86% PLO1 · 89%Outcome attainment by student, using student identifier, with PDF preview and download in the real system.
ULO · PLO · Custom outcomesThe real bulk ZIP includes programme-specific and Overall Unit Reports for each eligible offering.
Cohort calculations use the selected programme’s configured Core Units.
| Unit | ULO mapping | Assessments | Marks |
|---|---|---|---|
| UNIT 101 | Complete | Pending | Pending |
| UNIT 202 | Complete | Complete | Complete |
Review incomplete tasks and email lecturer-specific reminders.
Interface layout and appearance based on the actual OBE KitAI Reports HTML/CSS. All names and percentages are illustrative; this preview is not connected to student records.