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.
Classes visualised on a timeline with holiday and today markers.
Step 07 — Assessment
AMTOS includes a full question-bank authoring system with an approval workflow, plus two distinct exam delivery modes. 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 accept PDF uploads within a defined submission window.
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 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 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 any point during or after training, two regulatory documents can be generated as PDFs. The CoR Checklist is a comprehensive progress report (passport check, hours attended, theory exam results for modules 1–17, workshop practical P1–P10, aircraft practical, and signatures). The Certificate of Recognition (EASA Form 148) is the formal certificate listing module pass dates and track. Both are available to admins for any student, and to students themselves from their portal.
CoR Checklist — Layout Wireframe
System Architecture
AMTOS is a three-tier web application hosted on a Windows IIS server. The presentation layer is rendered server-side by ASP.NET MVC using the Razor view engine, enriched by the DevExpress component suite for grids, schedulers, dashboards and PDF reports. Data persistence is handled by Entity Framework Code-First against a SQL Server database.