Services
About
Contact
Get in
Touch
Enrol. Train. Certify. One system, zero gaps — AMTOS unifies personnel, scheduling, question bank, online exams, attendance and regulatory reporting in one cloud-hosted platform purpose-built for Part-147 schools.
A product by Aggregator Solutions
System Overview
AMTOS unifies every stage of an EASA Part-66 Aviation Maintenance Engineering programme — from first enrolment through to the issuance of a Certificate of Recognition (EASA Form 148). Administrators, instructors and students each see a role-tailored interface built on a single shared database, eliminating duplication and ensuring that records are always authoritative and up-to-date.
Step 01 — Foundation
Before training can begin the organisation must be populated with its people. AMTOS holds a single Personnel record for every individual — staff, instructor, or student — and each record can optionally be linked to a system login. Role assignment determines exactly what that person can see and do within the platform.
Role access is concentric — each outer role has a subset of the inner roles' permissions.
Step 02 — Structure
A Track is the top-level certification pathway — for example Cat A, Cat B1.1 or Cat B2. Each track is a curated collection of courses, and when a student is assigned to a track they automatically inherit its full course curriculum. Tracks carry a total credit value and can be inspected to see exactly which courses they contain.
A track bundles courses; each course generates one or more scheduled classes.
Step 03 — Curriculum
Courses are the atomic unit of the curriculum. Each course maps to a Part-66 module number, carries its own document library, and may have prerequisites. Grading components (theory, practical, essay) can be configured independently per course, giving administrators fine-grained control over how final grades are calculated.
Step 04 — Learners
Students are a specialised type of Personnel record. Beyond the standard profile fields, each student record holds their nationality, regulatory identification data, a photo, and a personal document vault. Large cohorts can be loaded in minutes via Excel bulk import, with automatic track assignment available at import time.
Student record anatomy — profile, documents, tracks and login in one place.
Step 05 — Registration
Enrolment bridges students and scheduled classes. Assigning a student to a track provides a high-level affiliation; enrolment into individual classes confirms their participation in a specific timetabled delivery. Both individual and bulk enrolment are supported, and an enrolment-locking mechanism lets administrators freeze class rosters ahead of an exam period.
Step 06 — Timetabling
AMTOS provides a visual, drag-and-drop scheduler for planning the entire training calendar. Classes are the concrete delivery of a course — they carry start/end dates, a facility, an instructor and a roster of enrolled students. Country-specific public holiday calendars prevent accidental scheduling on rest days, and any class can override the default holiday list where operational requirements demand it. External calendar events can also be imported directly from Outlook or Google Calendar via the ICS / iCalendar format.
Classes visualised on a full-width timeline with holiday and today markers.
Step 06b — Advanced Planning
For schools running multiple cohorts simultaneously, AMTOS provides a Cohort Planner that automatically generates a full-semester timetable using a Simulated Annealing meta-heuristic. The engine resolves instructor and classroom conflicts across all cohorts at once, respects the EASA Part-147 curriculum sequence, skips public holidays, and avoids clashing with any pre-existing classes — all in a single optimisation pass. The result is previewed as a colour-coded multi-cohort Gantt chart before being committed to the live schedule.
SA Cooling Curve — Conflict Cost vs Temperature
Conflict cost collapses as the SA engine cools. Hard violations carry a ×1,000 penalty that forces near-zero conflicts in all published schedules.
Built-in EASA Part-147 Curriculum Blocks
Step 06c — Content Protection
Course syllabi, manuals and lecture materials are delivered through a dedicated Secure Protected View rather than a plain file download. The viewer renders PDFs page-by-page on an HTML5 Canvas using PDF.js, and burns a personalised forensic watermark into every page server-side before it is streamed — making unauthorised distribution traceable back to the individual student. A matching set of client-side controls prevents printing, right-click saving, and developer-tools inspection.
<canvas> elements
via PDF.js. The document is never exposed as a downloadable file object in the browser —
students see rendered pages, not a raw PDF stream.@media print rule hides the entire page body
— including the canvas, header and container — so any print or PDF-print attempt produces
a blank page. Ctrl+P is also intercepted at the keyboard level before the
browser print dialog can open.contextmenu event is suppressed globally on the
viewer page, preventing the browser's “Save image as” or
“Inspect” options from appearing when a student right-clicks on any rendered
page.[Authorize(Roles="Student")]. Unauthenticated or unauthorised requests
receive HTTP 404 / 403 — the raw file path is never exposed in the HTML, and direct URL
guessing returns nothing.Step 07 — Assessment
AMTOS includes a full question-bank authoring system with an approval workflow, plus two distinct exam delivery modes. The question bank is structured around a three-level EASA Part-66 syllabus taxonomy (Module → Submodule → Sub-submodule), ensuring every question maps precisely to a regulatory objective. Multiple-choice theory exams are taken online by students in real time, with questions assigned either uniformly (same set for everyone) or randomised per student. For written assessments requiring longer responses, Essay Exams present a fully separate submission-and-grading workflow: students upload a PDF within a configurable open/close window, and administrators review and grade the submission before releasing marks through the same controlled publication workflow as MCQ results.
Step 07a — Integrity
AMTOS provides a full proctoring layer for online theory exams — from invigilator check-in gates and biometric face verification through to a live proctor dashboard and automatic focus-loss detection. Every action is logged with a timestamp, giving exam administrators a complete audit trail for each sitting.
FaceMatchingService. EASA Part-147 CBT guidance note references this check.Step 07b — Alignment
For schools requiring rigorous regulatory alignment, AMTOS extends the question bank with ATA chapter tagging and a Blueprint system. Blueprints define the required distribution of questions across ATA chapters — so every exam is verifiably balanced across the EASA Part-66 syllabus rather than drawn at random.
AtaChapter field is exposed in the question list DTO, grid filters, and export
views.Step 08 — Presence
Attendance is recorded at the class-session level for every enrolled student. AMTOS presents this data as a pivot table — students on one axis, dates on the other — so instructors and administrators can spot absence patterns instantly. An instructor can toggle a student's presence directly in the grid, making real-time updates from the classroom straightforward.
Attendance Pivot — Students × Sessions
Step 09 — Verification
Before results reach students, an instructor or administrator reviews each attempt in full — question by question. Individual questions can be excluded/awarded (e.g. due to ambiguity) in two modes: excluding/awarding for a specific student or system-wide. A release-summary screen confirms the pass/fail count before results are published. Students immediately see their results, including which questions they answered correctly.
Step 09b — Compliance
Before a student can sit any exam, AMTOS automatically checks their attendance record against configurable absence thresholds. Students whose absence percentage exceeds the threshold are blocked from participating and see an amber warning card instead of the exam link. Administrators can investigate each case and either lift the block (clearing it entirely) or force a permanent block — with a mandatory reason recorded for audit purposes.
SystemSettings:
AbsenceThresholdPct (per-module, default 10 %) for Theory/Practical, and
AbsenceThresholdEssayPct (cumulative, default 10 %) for Essay exams. Both are
editable live from the Admin UI without a deployment.
ExamEligibilityOverrides table for audit. Override reasons appear in the grid
for future reference.
Step 10 — Hands-On
Workshop practical skills (P1–P9) are assessed against a defined set of criteria for each module. An instructor creates a Practical Exam linked to a class, then opens individual student attempts and scores each criterion live during the assessment. Scores are held in draft until the instructor deliberately releases them, ensuring students only see validated results.
Assessment Matrix — Modules × Criteria
Step 11 — Insight
Every user role in AMTOS has a personalised dashboard. The admin homepage surfaces live KPI gauges drawn from the database in real time. Above that, a full DevExpress BI Dashboard Designer lets administrators build and publish rich, interactive dashboards — charts, pivots, maps and more — without writing code. Instructors see their own classes and attendance; students see their personal exam and results calendar.
Admin KPI Dashboard
Step 12 — Certification
At the end of training, two regulatory documents formalise completion. The CoR Checklist is a comprehensive regulatory progress report (passport check, hours attended, theory results M1–M17, workshop practicals P1–P10, aircraft practical, and signatures). The Certificate of Recognition (EASA Form 148) is the formal certificate listing module pass dates and track — the final output of the training programme. Behind both sits the Student History Report: the complete audit trail that tells the story of how and when that certificate was earned — every session, every exam question, every practical criterion, and every eligibility decision, all in one retrievable record. All three query the live database at generation time — no manual compilation.
CoR Checklist — Layout Wireframe
Step 13 — Quality Management
To maintain regulatory compliance (EASA Part-147), AMTOS includes an integrated Quality Management System. This module allows quality managers and administrators to schedule and record audits, raise Non-Conformance Reports (NCR) with automated indexing, and track Corrective & Preventive Actions (CAPA) assigned to personnel.
NCR-YYYY-XXXX). High severity items are visually highlighted in soft red on the dashboard grid.QMS Records — Relational Schema
Step 14 — Integration
AMTOS supports enterprise identity federation and e-learning interoperability out of the box. Schools can authenticate users through any OIDC-compatible identity provider (including Azure Active Directory) and expose courses and quizzes to external LMS platforms via LTI 1.3 Advantage — making AMTOS a plug-in component of a wider learning ecosystem.
System Architecture
AMTOS is a multi-tenant SaaS application deployed on a Windows IIS server. Each
school (tenant) operates on its own isolated SQL Server database — a database-per-tenant model
— with tenant resolution handled automatically via subdomain routing: a custom
TenantResolver reads the host header and a DbContextFactory instantiates the
correct connection string. The presentation layer is rendered server-side by ASP.NET MVC 5 using
the Razor view engine, enriched by the DevExpress v25.1 component suite for grids, schedulers, dashboards
and PDF reports. Authentication is handled by ASP.NET Identity. Data persistence
uses Entity Framework 6 Code-First migrations.
Additionally, the system features a built-in Multi-Tenant Provisioning Wizard that automates the deployment of new schools, complete with support for custom database naming constraints (enabling seamless hosting on shared environments like Plesk with custom database prefix rules). To facilitate evaluation and staging, the wizard supports the instant deployment of "Demo Environment" sandbox clones. These sandboxes are isolated databases that run on a dynamic connection routing architecture, pre-configured with a 5-step quick-start seeder panel and a manual data clean/reset module directly accessible from their administrative dashboards.