Integrated Academic Management System · by ITL
ITL IAMS unifies registration, advising, examinations, finance and administration in a single, modular system — with a desktop portal for daily work and a web dashboard for monitoring and reports, running entirely on your own infrastructure.
A complete academic management platform — built as twenty focused modules that share one identity provider, one database and one set of integration contracts.
A JavaFX application for staff, faculty and students: login, the 20-module registry, day-to-day workflows, and report export — one install, no browser required.
A live dashboard served by nginx: system status, the module registry and exported institutional reports — reachable from any device on your network.
PostgreSQL and nginx ship with the platform and run without administrator rights or cloud accounts. Your data stays on your machines.
Every module is a self-contained unit — own schema, own screen, own tests — integrated through 13 shared contracts. Available modules light up automatically; the platform keeps running even while pieces are being developed.
The web dashboard as your team sees it — recreated here from the running system. Switch the tabs, then meet the desktop portal below.
/api/status (live) · auto-refresh every 10s
Reports are exported from the desktop app with one click and published here.
One login for every role — students, faculty, staff and administrators.
Built for the realities of campus IT: private data, limited budgets, existing staff.
The whole platform — application, database, web tier — runs on your hardware. No cloud account, no vendor-hosted student data.
The portable PostgreSQL and nginx stack needs no system-wide installation, no services to register — it runs from a folder.
Twenty modules, thirteen shared contracts. Modules integrate through well-defined services and fail open — partial rollouts never take the platform down.
Health and status endpoints, a live module registry, and an audit trail are part of the platform — not an afterthought.
Desktop portal for heads-down work, web dashboard for everyone else — always consistent, always current.
326 automated tests cover every module, including database integration tests that verify the platform against the real schema.
A deliberately boring, dependable stack — chosen for long-term maintainability and offline-capable builds.
The same package scales with you.
Run the full platform on a laptop — in front of a committee, with synthetic demo data. Nothing to install, nothing to clean up.
Move it to one machine on your network and the web dashboard reaches your whole office — status, modules and exported reports.
Phase 2 of the roadmap: production hardening, SSO/MFA, scale and migration support from the ITL team.
ITL IAMS is not one-size-fits-all: every deployment is tailored to the respective academic institution — its name and branding, its academic structure, its rules. Below is an indicative adaptation plan for a standard single-campus deployment.
Your institution's name, logo and colors across the desktop portal, the web dashboard, the login screen and every exported report.
Schools, departments, programs, degrees and identifier codes configured to match your registry — not a fixed template.
Course codes, prerequisites, credit limits, grade scale, fee heads, scholarship rules and report formats adapted to your regulations.
Discovery & scoping: structure, catalog, fee rules, branding assets, data sources.
Configuration & branding: structure codes, catalog import, report templates.
Data migration: students, faculty and history; integration checks.
Pilot with one department or semester; training for registry and IT staff.
Go-live and hypercare: on-site or remote support through the first cycle.
| Role | Allocation | Focus |
|---|---|---|
| Project lead / architect | 1 × 8 weeks | Scoping, configuration, integration, go-live |
| Java developer | 2 × 6 weeks | Module adaptation, branding, report formats |
| Database engineer | 1 × 4 weeks | Schema mapping, data migration, tuning |
| QA / test engineer | 1 × 4 weeks | Regression on the adapted platform |
| Trainer / documentation | 1 × 2 weeks | Staff training, admin & user guides |
| Total | ≈ 30 person-weeks | standard single-campus deployment |
Indicative engagement budget: USD 8,000–15,000 equivalent for a standard adaptation (≈ 30 person-weeks) — final quote after a one-day scoping workshop. Your institution's side needs only a project coordinator and one IT contact, part-time.
Request a guided demo — the full 20-module platform, running on a single laptop.
Contact details are placeholders — edit the block marked EDIT-ME in site/index.html.