Integrations
Connected to the systems you already run
cimoio.aero is the source of truth for qualification and authorization data — and it shares that data with your MRO, planning, HR and learning systems. Openness is built in; interfaces are our focus.
One source, many consumers
Authorization data is decision data: your MRO system decides releases on it, planning tools staff checks with it. cimoio.aero keeps that data correct — and delivers it where decisions are made. Inbound, your HR system feeds joiners, movers and leavers; learning platforms return bookings, results and certificates. Every exchange replaces a manual handover — and every manual handover you remove is an error source gone.
Interfaces we have built
These are not off-the-shelf connectors — and we say that openly. Every landscape is different, so interfaces to surrounding systems are built individually, on our generic interface models. The examples below exist in production today; your variant is scoped in days, not months, because the patterns are proven.
AMOS
Authorization data delivered to the MRO system — so release decisions rest on current data.
SAP
Staff and organisational data exchanged with your ERP/HR landscape.
HR systems
Joiners, movers and leavers flow in automatically — assignments follow the role.
LMS platforms
Bookings handed over, results and certificates returned — where possible via LTI, so content stays on the provider's server.
Each of these was built for a specific customer landscape — and each next one gets faster.
Open by default
REST API
Programmatic access to your data — for your IT, your tools, your scripts.
Excel & CSV import
Bulk data in: master data, qualification records, historical lists — loaded via templates.
Excel & CSV export
Every list leaves the system as a file — for reports, audits and your own analysis.
JSON export
Structured, machine-readable data for downstream systems.
Single Sign-On
Log in with your identity provider — all common SSO technologies supported.
Automated e-mail exchange
Structured requests and confirmations with training providers — automated, without a live interface.
Your system isn't listed? That's normal.
No two system landscapes are alike — that's why our focus is on building interfaces, not on pretending a catalogue covers them all. Bring your landscape to a conversation: we'll tell you honestly what exists, what gets built, and what the Excel-and-API route covers on day one.
Frequently asked
Are AMOS and SAP integrations plug-and-play?
No — and we'd rather tell you that here than in the project. They are individually built interfaces on proven patterns. The scoping conversation tells you effort and timeline for your landscape.
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.
How do training providers connect?
Via structured, automated e-mail exchange and file transfer — honest answer: there is no live provider API. Bookings, confirmations and certificates still flow without manual typing.
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.
Bring your system landscape
In thirty minutes we map your systems against the patterns we've built — and you leave knowing what connects, how, and what it takes.