The platform | One operational graph
One operational graph for safety, quality and compliance.
One operational graph connects occurrences, hazards, barriers, actions, audits, indicators and governance decisions. SMS, QMS, security and compliance in one governed picture, for airlines and aviation operators.
- Overview
- Workflow
- Linked
- Discussion
- History
Every record opens on the same five tabs.
Overview, Workflow, Linked, Discussion and History, whether it is an occurrence, a hazard, an audit or an action. Three of them, on a hard landing:
- Overview
- Workflow
- Linked
- Discussion
- History
Where the record stands
- Its stage, and the next step with what it is waiting on.
- Its risk position on the 5 by 5 matrix, beside 12 months of occurrences in its risk family.
- The people on the record and what each one owes.
Everything it is connected to
- The hazard it belongs to, the investigation and the corrective actions.
- Documents and files, with the evidence they carry.
- Each link is a record you can open, and each names its kind.
Who did what, and when
- Decisions, stage moves, edits and files, in order, with the person and the time in UTC.
- What eAvy proposed, with its confidence, and who accepted it.
- Kept in an append-only audit log beside the record.
The links are records too.
Occurrences, hazards, barriers, actions, requirements and documents, with the link between each pair named and kept.
One queue, instead of a folder of email.
Every person opens one queue with what is waiting on them, ranked by urgency.
Decisions that become actions.
The review board reads the same picture the safety office works from, and a decision lands as an action in its owner’s queue.
Friday 13 November | 14:00ZHard landing, runway 24R: accept the residual risk?
Proposed: accept once the action is verifiedGusting crosswind landings: add a barrier?
Proposed: a refresher for the crews on this routeComposite risk 62 of 100: keep the snapshot
Proposed: record what the board was shownA risk profile the records produce.
Seven named components, fused into one banded score per risk theme and shown beside its worst ICAO risk level. Each profile is kept as a snapshot, so the board reads the answer it was given.
A built aviation risk library, assessed against your operation.
Bow-tie models with named barriers and indicator definitions arrive with the platform. Barrier health is read from how each barrier held when it was challenged.
A record closes on evidence, not on a checkbox.
- HeldWeakened
Barriers are rated before the record moves on
Every barrier an occurrence challenged is rated, unless your risk policy says a band does not need it.
- DoneEffectiveness checkClosed
Actions close after an effectiveness check
The check is on by default and set by policy, so the fix is proven before the action closes.
- A. LaurentP. Novak
The owner is not the verifier
By default, the person who owns an action cannot be the one who verifies it.
AI proposes. Humans approve.
eAvy and a fleet of specialist AI agents read records and propose: a classification, a risk, a link, a draft. Nothing they propose is written to a record until someone accepts it, and the decision is kept with the reviewer’s name.
eAvy read the report for flight NWA412 and proposes a classification from your taxonomy. The safety manager decides.
From the narrative: a hard touchdown on runway 24R, 2.1 g at touchdown, flight NWA412.
Filed with no signal. The same record the office reads.
The eAviora app for iPhone and iPad works offline on the same platform. The web app works at phone width too.
See the eAviora appDifferent teams, the same records.
- M. TremblayThe safety managerWorks a queue of what is waiting on them, ranked by urgency, not an inbox.
- P. NovakThe quality auditorFollows the trail from a finding to the action, the evidence and the people who verified and closed it.
- A. ChenThe accountable executiveReads one computed risk answer per theme, kept as a snapshot.
- J. BergeronThe investigatorReads the occurrence with its linked records, its flight data and the earlier look-alike, in one place.
Open to your systems, closed to everyone else.
- A documented, versioned REST APIWith an OpenAPI description generated from the same definitions the API serves.
- A connector for AI assistantsAn MCP server that is isolated per organization, checked against each user’s permissions and audited.
- Enterprise identitySAML single sign-on, SCIM provisioning and multi-factor sign-in.
- Isolation in the database itselfRow-level security on every organization’s tables, and signed webhooks for the events your systems subscribe to.
About the platform.
It includes one. The Safety Management suite covers the four components of ICAO Annex 19, and the same graph carries quality audits, security events, compliance, documents and training.
Yes. Each module has a list price, and a module added later writes to the same graph as the ones you started with.
The web app works at phone width, and the eAviora app for iPhone and iPad files reports where there is no signal.
Yes. Records export as JSON or CSV, and occurrence reports as E5X for ECCAIRS.
Bring one of your records.
A walkthrough on your own operation, with the people who build eAviora.