Course plans that grow from outcomes.
Build OBE-based RPKPS — from programme, course, and sub-course outcomes down to every meeting — with student workload calculated for you, approved step by step, and published to an open catalogue.
Already signed in to App ITTS? You go straight through without typing anything.
02/ 08Open catalogue
Everything ratified, open to anyone.
Students, assessors, and industry partners can read the outcomes, weekly plan, assignments, and assessment of every course — no account needed.
- Published documents
- 11
- Courses
- 11
- Study programmes
- 3
- Academic years
- 1
Study programmes
Recently ratified
- TI218 · Jaringan Komputerv1 · 2026/2027 Ganjil · November 3, 2026
7499150f · fe72103c - SI220 · Pemrograman Data Sciencev1 · 2026/2027 Ganjil · November 3, 2026
69186c0d · 4022eb80 - IF114 · Grafika Komputerv1 · 2026/2027 Ganjil · November 3, 2026
3d2cd43a · d2e7cd6b - IF208 · Interaksi Manusia dan Komputerv1 · 2026/2027 Ganjil · November 3, 2026
54becf53 · 2f62dc2f
03/ 08Curriculum books
Every programme's curriculum, read like a book.
Graduate profiles, learning outcomes, courses, and the curriculum map, assembled straight from the curriculum in force — the same one lecturers use to write their RPKPS.
04/ 08Features
One place, from curriculum to evaluation.
Everything shown here already runs in the application — none of it is a roadmap.
OBE outcome map
Programme, course, and sub-course outcomes come from the curriculum book. The validator checks that every sub-outcome is assessed and every meeting is mapped.
Calculated workload
Contact, structured, and independent study time are calculated from the learning-mode policy — always 45 hours per credit per semester.
AI drafts with your key
AI writes a complete draft with a closed assessment map, following your directions, using the lecturer's own API key.
Bilingual import & print
Fill it from an Excel template and print Indonesian–English .docx with the programme letterhead. Translations are AI-assisted and approved one by one.
Attainment evaluation
Import grades per class, calculate course and programme outcome attainment, analyse test items, and record the follow-up.
Teaching materials
Textbooks written chapter by chapter from the weekly plan — diagrams as code, ISBN-ready .docx, plus .pptx slides.
05/ 08Workflow
From assignment to publication, every seal is recorded.
The signature chain follows the Kampus ratification page: Coordinator, Head of programme, then Quality Assurance.
- 01AssignmentThe head of programme appoints a coordinator for each course per academic year.
- 02DraftingThe teaching team drafts by hand, from an AI draft, or from an Excel template.
- 03SubmittedLecturers initial, the coordinator submits; the content is locked during review.
- 04ApprovedThe head of programme approves, or returns it for revision with notes.
- 05Ratified & publishedQuality Assurance adds the final seal; the document is frozen with a fingerprint and published.
- 06EvaluationClass grades are imported, attainment is calculated, and the follow-up feeds the next round.
Drafting, review, and ratification deadlines are set per academic year; updates arrive as notifications and email.
06/ 08Who it is for
Every role sees its own work.
Staff roles are derived from positions in App ITTS, not handed out manually.
Lecturers & coordinators
Draft and maintain the RPKPS of the courses they teach.
- Teaching teams and handover
- AI drafts and template import
- Teaching materials from the weekly plan
Head of programme
Manages the programme curriculum and approves its RPKPS.
- Coordinator assignment board
- Curriculum revision proposals
- Programme-level attainment
Quality Assurance
Reviews and ratifies the documents that get published.
- The final ratification seal
- Deadlines per academic year
- Oversight across programmes
Assessors & students
Read the valid documents and their evidence, without editing.
- Only ratified documents
- Frozen copies with SHA-256 fingerprints
- Preview links for site visits
07/ 08Quality & security
What is ratified does not shift quietly.
Every published document is frozen and fingerprinted. Any later change shows, rather than hides.
A fingerprint on every seal
Each signature stores the fingerprint of the content at that moment. Content that shifts mid-chain cannot be approved.
Curriculum through formal proposals
Programme, course, and sub-course outcomes change only through a revision proposal to the head of programme, effective from an academic year.
AI keys never readable again
Lecturers' API keys are stored encrypted with AES-256-GCM; only the last four characters are ever shown.
Sign-in only through App ITTS
One campus account. Names, titles, and NIDN are read from App ITTS, not copied here.
08/ 08FAQ
Frequently asked questions
Who can sign in?
Kampus staff with an active App ITTS account; their roles follow their positions. Assessors and students registered by an administrator sign in with an App ITTS account using the same email.
Do I need an account to read an RPKPS?
No. Every ratified RPKPS is open in the catalogue, together with its SHA-256 fingerprint.
How can I tell that the file I hold is genuine?
Compare the fingerprint printed on the file with the one on that course's catalogue page. If they differ, the content has shifted from what was ratified.
Does AI write my RPKPS?
AI only drafts when you ask, using your own API key. The draft is still checked by the validator and only becomes content once you apply it.
Can course outcomes be changed from inside an RPKPS?
No. Outcomes come from the curriculum book; changes are proposed through a Curriculum Revision Proposal to the head of programme and take effect from the next academic year.
What if the curriculum is revised after a document is published?
Frozen copies are never rewritten, so the published document and its fingerprint stay the same. The revision applies to documents of later academic years.