Skip to content
FRSign inBook a walkthrough

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.

Case file | SMS-OCC-2026-0412Under investigation
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
SMS-OCC-2026-0412Occurrence | Hard landing, runway 24R
SMS-HAZ-2026-0031Hazard
INV-2026-0018Investigation
ACT-2026-0107Corrective action
Flight data trace | Crew statementEvidence
Composite risk 62 of 100Safety Risk Profile
Sample data | Northwind Air, a fictional airline
One record

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:

Dossier | SMS-OCC-2026-0412Tolerable, action required
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
Hard landing, runway 24R
Overview tab

Where the record stands

Stage 5 of 11, InvestigationUnder investigation
Risk positionMajor, Remote: Tolerable, action required
J. BergeronInvestigatorOwes the cause
A. LaurentStation managerOwes the action
M. TremblaySafety managerRisk confirmed
  • 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.
Linked tab

Everything it is connected to

SMS-HAZ-2026-0031Hazard it belongs to
INV-2026-0018Investigation
ACT-2026-0107Corrective action
  • 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.
History tab

Who did what, and when

M. Tremblay rated a barrier: Effective2026-11-07 10:24Z
S. Okafor accepted the eAvy classification2026-11-06 16:40Z
First Officer filed the report from the eAviora app2026-11-06 14:12Z
  • 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.
Sample data | Northwind Air, a fictional airline
The operational graph

The links are records too.

Occurrences, hazards, barriers, actions, requirements and documents, with the link between each pair named and kept.

RaisedProposedInvestigatesContained bySMS-HAZ-2026-0031HazardSMS-OCC-2026-0405Firm landingINV-2026-0018InvestigationACT-2026-0107ActionSMS-OCC-2026-0412Hard landing
1 proposed linkC-FNWK | same aircraft, six days apartSMS-OCC-2026-0405 Firm landing on runway 24R, 2026-10-31, and SMS-OCC-2026-0412 Hard landing on runway 24R
Sample data | Northwind Air, a fictional airline
Linked as the work is doneAn investigation opened from an occurrence is linked to it; an action raised from a finding is linked to its source.
Proposed links wait for a personThe platform proposes links it finds, such as two occurrences on the same aircraft six days apart. Someone links them or dismisses them.
My Queue

One queue, instead of a folder of email.

Every person opens one queue with what is waiting on them, ranked by urgency.

13Required Yours to act on, with a deadline.
17Recommended Worth doing next.
6Watched Records you are following.
M. Tremblay | her queue, Tuesday 10 November | Required
SMS-OCC-2026-0412Confirm the cause of the hard landingWaiting on you since J. Bergeron finished the analysisDue today
ACT-2026-0107Review the corrective action evidenceA. Laurent uploaded the evidenceDue Thursday
SMS-OCC-2026-0425Assess the initial riskGround vehicle incursion on taxiway BDue Thursday
SMS-HAZ-2026-0031Review the hazard before the boardOn the agenda for FridayDue Friday
Sample data | the first rows of each tray
The Safety Review Board

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:00Z
Agenda item 1 | SMS-OCC-2026-0412

Hard landing, runway 24R: accept the residual risk?

Proposed: accept once the action is verified
Agenda item 2 | SMS-HAZ-2026-0031

Gusting crosswind landings: add a barrier?

Proposed: a refresher for the crews on this route
Agenda item 3 | Safety Risk Profile

Composite risk 62 of 100: keep the snapshot

Proposed: record what the board was shown
Sample agenda | 0 of 3 decisions recorded
Risk is computed

A 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.

62/ 100, composite riskTolerable, action requiredHigher is riskier | Residual target: Tolerable
Choose a component to see what it adds to the 62.
Base risk: 15.0 risk pointsScore 60 / 100 | weight 25% | Adds 15.0 of the 62 risk points.The risk levels of the records in the theme.
Sample data | Northwind Air, a fictional airline
The model, included

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.

The bow-tie for one risk familyP1P2P3P4P5R1R2R3R4High descentrateExcessivepitch-upBouncedlandingGust beyondlimitsWeightor balanceStructuraldamageHiddendamageHulllossOccupantinjuryAbnormalrunway contactRF-01-003ThreatsPreventive barriersTop eventRecovery barriersConsequencesOne of 85 bow-tie models | names from the library, shortened | Barrier health shown is sample data.
The ICAO 5 by 5
Major, RemoteTolerable, action required
85bow-tie models, one per risk family
682named barriers, each a record of its own
1,467threats, consequences and escalation factors
516safety performance indicator definitions
183operational scenarios beneath the families
Counts read from the library the platform seeds, checked against it by a test on every build. Taxonomy codes and indicator definitions are versioned. You map your own terms to them, so last year stays comparable with this year.
Closure is governed

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. LaurentStation manageris notP. NovakQuality auditor

    The owner is not the verifier

    By default, the person who owns an action cannot be the one who verifies it.

Sample data | Northwind Air, a fictional airline
Governed AI

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.

Governed AI | eAvy

eAvy read the report for flight NWA412 and proposes a classification from your taxonomy. The safety manager decides.

92%
eAvy proposes | 92% confidence | 2 creditsAbnormal Runway Contact, severity Major

From the narrative: a hard touchdown on runway 24R, 2.1 g at touchdown, flight NWA412.

Nothing is written until a person decides.
Meet eAvy, the AI assistant
The eAviora app
Hard landing, runway 24RFiled 14:12Z | synced 14:19ZSaved on device

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 app
Sample data | Northwind Air, a fictional airline
Who reads it

Different 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.
Built for IT review

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.
Questions buyers ask

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.

Bring one of your records.

A walkthrough on your own operation, with the people who build eAviora.