Skip to content

Services

idataraya plans the rollout around the academic calendar, installs the system in the institution's own environment, and maintains it under one yearly agreement.

An engineer going through a document with a colleague at a desk

Rollout plan and proposal

Send the institution, the number of students and the systems in use today. An engineer replies with a rollout plan, an integration plan and a proposal. It goes live on one programme, one campus or one intake first, before the whole administration commits to it.

Installation and migration

asasii campus runs in the institution's own cloud account or data centre. idataraya installs it, hardens it and integrates it with the academic systems already in place. Migration happens between intakes, not during one, with cutover dates chosen against the institution's own calendar. Admissions and fee collection continue throughout, and the previous path stays available until the new one is trusted.

Support and maintenance

One team looks after the system for the life of the agreement, and is staffed when intake arrives.

  • Severity-based response times, measured monthly
  • Continuous monitoring from within the institution's environment
  • A drilled backup and restore
  • Releases, patches and incident response
  • Changes as programmes and fee structures change

The yearly agreement

Software updates, the customisations made for you, monitoring, severity-based response and restoration targets, and the changes needed as programmes and fee structures change. Hosting stays with you. It is a fee, not a subscription.

Security and Malaysian compliance

The questions the registry, the bursar's office and audit ask, answered in the system.

Security and data overview
PDPA 2010
Student and parent data stay in the institution's own environment.
Roles
Access is scoped to role, because student records include minors and their families.
Single sign-on and MFA
On every console, with the institution's own identity provider.
Audit trail
Every change to a record is logged with who made it and the previous value, and kept for seven years.
Your own environment
Deployed in the institution's own cloud account or data centre, as its data policy requires.
Export
Every record exports on request.

See it on your own campus

Send us the institution, the number of students and the systems in use today. An engineer replies with a rollout plan, an integration plan and a proposal.