FAQ

Frequently asked questions

Everything about cimoio.aero — the product, Compliance as a Service, getting started, integrations and security. Search for a topic or browse by category.

The product

What is cimoio.aero?

cimoio.aero is the software for qualification, authorization and training management of technical aviation staff. It keeps qualifications, authorizations, trainings, competences and certificates in one system — from requirement to evidence, without media breaks.

Who is cimoio.aero built for?

For EASA Part-145 maintenance organisations, Part-CAMO organisations and Part-147 training organisations — from around 10 to 10,000 managed persons.

Is cimoio.aero modular?

Yes. You book the modules your organisation type needs and extend when you grow — a training organisation needs sales functions, an MRO doesn't.

Which user roles does the system know?

Administrative roles (Organizer) work in the management interface; operational staff (Surfer) — mechanics, managers, trainers — use a radically simplified self-service view, responsive for tablet and smartphone.

Does it work on the shop floor?

Yes — cimoio.aero runs in the browser, including shop-floor terminals and tablets. Mechanics see their own qualifications, authorizations and upcoming trainings in self-service.

In which language is the system available?

English — the language of aviation. System, templates, reports and documentation are English throughout, which keeps audits internationally presentable.

Who is behind cimoio.aero?

cimoio.aero is a joint product: developed by STL GmbH (Stuttgart, Germany) on a platform with 25 years of development history, configured, sold and provided by qamaas GmbH — practitioners from aviation maintenance and quality organisations.

Does cimoio.aero support FAA regulations?

Our focus is the EASA space, including countries that align with EASA rules. FAA requirements can technically be represented, but it is not our active market and we don't claim operational FAA experience.

Can we manage external staff and contractors?

Yes — subcontractors or external examiners can be managed with their qualification data without needing their own system login.

Can managers and auditors be managed too?

Yes. Postholders, auditors and internal trainers are managed with their specific qualification profiles — either as own groups or as additional authorizations on an existing profile.

Qualifications & authorizations

What's the difference between a qualification and a training?

A training is one way to reach a qualification — not the qualification itself. A qualification can also be reached through recognition of existing certificates, practical experience (OJT) or a competence assessment. cimoio.aero models all of these paths digitally.

What is a qualification profile?

A bundle of qualifications assigned to a person as their target. The system compares target and actual continuously — the gap is your to-do list.

How does an authorization differ from a qualification?

An authorization is the formal permission to perform and release work. It rests on qualifications, is granted through an approval workflow, and is monitored for aviation-law reasons — it cannot be suspended, only withdrawn and re-issued.

What is rolling renewal?

Instead of letting authorizations expire in fixed cycles and re-issuing them in bulk, every incoming training, certificate or assessment extends the underlying qualification — and the authorization simply continues. No cliff-edge dates, no surprises.

What happens when a qualification expires?

The system flags it well before expiry and notifies the employee, the supervisor and the responsible coordinator. If it does lapse, the authorization resting on it is withdrawn automatically and the employee sees it immediately in their record.

Can authorizations be revoked?

Yes — digitally, with immediate effect. The employee is informed, the record is updated, and connected systems receive the change so release steps can be blocked.

Which paths to a qualification does the system support?

Classroom training, web-based training, practical training (OJT), recognition of existing certificates, personal recognition by a superior, and competence assessment — each with its own digital workflow and evidence.

Can we see who is closest to a new authorization?

Yes. The target/actual comparison shows per person what is missing — so you can see who reaches a needed authorization fastest and plan cross-qualification deliberately.

Can we manage non-aviation permissions too?

Yes. Permissions required by other law or company policy — equipment, data protection, compliance topics — are managed with the same mechanisms but configurable more freely than aviation-law authorizations.

Can tooling and equipment be monitored?

Yes — the same mechanisms keep tools and equipment monitored for occupational-safety reasons under control, with ready-made profiles. Many Part-145 organisations switch this on from day one.

Compliance as a Service

What is Compliance as a Service?

cimoio.aero delivered as a working process instead of an empty system: pre-configured software, Built-in EASA Qualifications, documented processes, user trainings — and we keep all of it current. You start working, not configuring.

What does "working process" mean?

That the system doesn't arrive empty. The qualifications, the processes, the trainings and the way of working are delivered with it — you start working, not defining. What remains yours is the work itself: assigning, deciding, keeping your people current.

How fast can we start?

Ready to operate in 6 weeks — not in 8 to 12 months. The configuration and the content already exist; the guided onboarding loads your data, maps your organisation onto the standard and trains your people.

Does Compliance as a Service make us compliant?

No provider can honestly promise that — and we don't. We deliver and maintain everything up to it: the filled system, the content, the processes, the trainings. The last step to compliance stays yours: working with it.

What stays individual in the fixed configuration?

Your master data, your people, your organisational structure — and your authorization profiles, assembled from the standard building blocks to match your operation. The processes and the configuration itself follow the proven standard.

What if we run a process differently today?

In most cases the best-practice process replaces it — easier than it sounds, because the regulation behind it is identical for everyone. Where a requirement is genuinely structural, we'll say so early and point you to SaaS or Custom instead.

What happens when EASA rules change?

We monitor regulation continuously. You receive the assessment, the change in your content, and a rollout recommendation — as part of the subscription, not as a project.

How do we present this in an audit?

Live: target profiles, gap status and the evidence behind every authorization, plus exports for the record. The standard and its documentation are built to be shown, not explained.

Can we switch to SaaS or Custom later?

Yes. Your data is yours — the editions share the same platform, so a later move is a reconfiguration, not a migration.

Which content costs extra?

None beyond the subscription: the qualification content, processes, trainings and their updates are what the subscription is. The one-time onboarding covers setup and your profile library.

Does joining the standard mean losing control?

You keep every decision that is yours to make — who gets authorized, on what evidence. What you give up is maintaining the machinery behind it. Most teams call that a good trade.

Is Compliance as a Service available for Part-147?

In preparation. Today it covers Part-145 and Part-CAMO organisations; Part-147 and further organisation types will follow.

What are Shared Improvements?

All Compliance as a Service customers work on the same standard. When one organisation's experience improves a process, a profile or the tool, the improvement flows into the standard — one improves, all benefit.

What is included in the 6 weeks?

Guided Onboarding with a fixed scope: data transfer, set-up and training of your Organizers and Surfers — ready to operate in 6 weeks.

Can we start without Compliance as a Service?

Yes. SaaS with your own configuration is a full option — Compliance as a Service is the faster path, not the only one.

Editions & pricing

Which editions exist?

cimoio.aero SaaS (the standard software, configured and filled by you), Compliance as a Service (delivered filled and kept current), and Custom (individually adapted, for organisations with special requirements — on request).

What's the difference between SaaS and Compliance as a Service?

SaaS gives you the tool — you configure it, fill it with your content and track regulation changes yourself. Compliance as a Service gives you a working process: content, processes and trainings delivered and kept current.

Is on-premise operation possible?

Within the Custom edition, yes — including operation in your own data center. SaaS and Compliance as a Service run in German data centers, fully managed.

How is pricing structured?

Per managed person: you license the people whose qualifications the system manages, independent of whether they log in. The module price scales with organisation size.

What is a "managed person"?

Every person whose qualifications, authorizations or trainings the system manages — whether or not they ever log in. Mechanics using self-service don't cost extra.

Which contract terms are available?

Monthly, annual and three-year terms — longer terms, better rates.

What does Compliance as a Service cost?

One onboarding (one-time, by organisation size and profile scope) plus one subscription (software, regulation monitoring and the service license for processes and trainings).

Can we start with one module or one department?

Yes. Qualification is the base module of every subscription; further modules can be added whenever you need them. Many organisations start where the pain is largest — one module or one department — and expand from there.

Are there discounts for large organisations?

Yes — the price per managed person is graduated by size: the more people you manage, the lower the price per person.

Getting started

How long does an implementation take?

With Compliance as a Service: 6 weeks to go-live. With SaaS it depends on your own configuration and content work — typically a small implementation project for interfaces and data migration.

What do we have to deliver during onboarding?

Your master data — staff, organisational structure, departments, current qualification records — in our templates. We do the loading.

What happens to our historical certificates?

They are migrated alongside; the pace depends on how they were kept. Honest answer: a well-kept archive moves fast, a scattered one takes longer — but the system is operational without waiting for the full archive.

Why don't you start with a requirements workshop?

Experience: organisations that specify everything up front demand features they never use in production. We put the proven standard in place, you work with it seriously in a defined scope — and only then do we look at real deviations. The tool reshapes the requirements.

Do we need our own IT for this?

No. cimoio.aero runs in the browser; hosting, updates and maintenance are included. Your IT is involved where interfaces to your systems are built.

How are our people trained?

With Prepared User Trainings — role-based end-user trainings for the tool, for administrative and operational roles alike, run on your data rather than demo content.

Who supports us after go-live?

qamaas as your direct contact — people who know both the software and Part-145. Structured support with defined response times, documentation for every user group, and the ongoing content updates if you run Compliance as a Service.

Can we test cimoio.aero before buying?

We start with a demo on your own processes. Whether a pilot makes sense for you, we agree together in the quote.

Trainings & learning

Can cimoio.aero plan and run training events?

Yes — the full event routine: deriving who must attend, scheduling, invitations, cancellations, attendance, results and feedback, with automated communication from templates.

Does cimoio.aero provide trainings itself?

No — cimoio.aero is the platform, not a training provider. Regulated courses require appropriately certified providers; internal content runs on the integrated learning platform.

Can we run online trainings?

Yes. Internal web-based trainings run on the integrated learning platform — in short units that fit the workday instead of consuming full days, where regulation allows.

Can we connect our existing LMS?

Yes — bookings handed over, results and certificates returned. Where possible via LTI, so the content stays on the provider's server while results land in your records.

How do external training providers connect?

Via structured, automated e-mail and file exchange — honest answer: there is no live provider API. Requests, confirmations and certificates still flow without manual typing.

Can the system create certificates?

Yes — internal certificates are generated from templates and filed automatically as evidence.

How does certificate intake work?

Incoming certificates land in a central intake, are matched to person, training and qualification, and filed at the right place — with a human check where confidence is low.

How long are records retained?

Retention periods are configurable per record type. Our best-practice presets align with GDPR and EASA record-keeping requirements; expired records are deleted on schedule, documented.

Competence assessments

What is a competence assessment in cimoio.aero?

A structured, digital assessment run against a versioned Scenario: the prerequisite qualifications to verify, the practical Elements to perform, and the Observable Behaviors to evaluate — same structure, every assessor, every time.

Who may conduct assessments?

Only users holding the assessor role with their own assessor qualification — enforced by the system, not by convention.

What result does an assessment produce?

A binary judgement — competent or not competent — confirmed by the assessor and acknowledged by the assessee, with a signed record. The resulting competence carries its validity and feeds the authorization directly.

How does a competence differ from a qualification?

A competence always contains the qualification but is more: it establishes the ability to work in a given context, which needs qualification plus attitude and behaviour — and that is established through an assessment.

Can assessments done on paper be entered?

Yes — paper assessments can be captured as after-the-fact records, so the history stays complete while you move to digital execution.

Integrations & data

Does cimoio.aero integrate with AMOS or SAP?

We have built interfaces to AMOS, SAP and numerous HR and LMS systems — as individually built interfaces on proven patterns, not off-the-shelf two-way connectors. We'd rather tell you that here than in the project; your variant is scoped quickly because the patterns exist.

Is there an API?

Yes — a REST API for programmatic access to your data.

Can we import and export Excel?

Both. Bulk imports via templates (master data, records, historical lists) and exports of every list as Excel/CSV; JSON export for downstream systems.

How does HR integration work?

Your HR system delivers joiners, movers and leavers; profile assignments follow the role automatically, and a transfer flags what it means for existing authorizations.

Can our MRO system block releases based on authorizations?

cimoio.aero delivers current authorization data to connected systems — so release decisions rest on live data and release steps without a valid authorization can be blocked there.

Is Single Sign-On supported?

Yes — all common SSO technologies and multi-factor authentication; we align with your identity provider during onboarding.

Who owns our data?

You do. Export in open, machine-readable formats (CSV/JSON) is contractual — no lock-in by data hostage.

What happens to our data when the contract ends?

It is exported in open formats, handed over, and deleted on a documented schedule.

What can we do without any custom interface?

A lot: Excel/CSV import and export, JSON export, the REST API and SSO are standard. Many customers start exactly there and add interfaces where the data volume justifies it.

Who builds and maintains an interface?

We do — scoped with your IT, built on our generic interface models, maintained as part of the platform operation.

Security, hosting & data protection

Where is our data hosted?

In German data centers, in ISO 27001-certified environments. Your data never leaves Europe.

Is cimoio.aero ISO 27001 certified?

cimoio.aero is developed and operated by ISO 27001-certified STL GmbH and hosted in ISO 27001-certified German data centers.

Is cimoio.aero GDPR compliant?

Yes — processing follows GDPR with a data processing agreement as part of the contract, all subprocessors are European and disclosed, and built-in tools support data subject rights.

How are backups handled?

Daily encrypted backups, retained for 30 days, stored geographically separated from the primary systems.

Is our data encrypted?

Yes — in transit and at rest.

Are customers separated from each other?

Strictly. Multi-tenant isolation keeps your data yours alone, and access within your tenant follows a fine-grained role and permission model.

Is there an audit trail?

Yes. Qualification-relevant decisions — grants, revocations, assessments — and security-relevant access are logged revision-proof and reachable in drill-down.

What availability is guaranteed?

High availability with contractual service levels — the exact figures are part of the service agreement, which we share in the technical documentation.

What are the client requirements?

A current browser — Chrome, Firefox, Safari or Edge. No installation, no plugins, no client management. The interface works on desktop and tablet, including shop-floor terminals.

What technology does the platform run on?

The platform has been developed and continuously modernised for 25 years; architecture details are part of the technical documentation we share on request.

Support & operations

How does support work?

Web-based ticket system with defined response times per severity level, on business days — from people who know both the software and the regulation.

When does maintenance happen?

In announced maintenance windows outside working hours, with advance notice for upgrades — no surprise downtime midweek.

Is there documentation?

Yes — for every user group, from administrators to shop-floor self-service.

How do updates reach us?

As part of the service — hosting, updates and maintenance are included. No upgrade projects on your side.

Can our IT get the security documentation?

Yes — ISO certificate, security concept, DPA template, system documentation and a pre-filled IT assessment questionnaire are available on request.

Didn't find your answer?

Ask us directly — people who know both the software and the regulation.