Buyer’s guide
How to choose aviation safety software
Seven questions to put to every vendor, the red flags to watch for in a demo, and how an evaluation with eAviora runs.
Start from the job, not the feature list
01 · The rule
The rule you answer to sets what the system must hold: FAA Part 5, EU 376/2014, Transport Canada’s CARs, the IOSA Standards Manual.
02 · The audit
The audit ahead sets the deadline, and the evidence the auditor will ask to see.
03 · The records
Count what you keep today, reports, hazards, actions, audits, documents, training, and where each one lives.
The questions
Seven questions for any vendor, us included
Ask each one in the demo, and ask to see the answer on screen.
01Linked recordsAre an occurrence’s barrier ratings, actions, indicators and risk profile linked records the platform computes over?
In the demo, ask to see
Open one occurrence and follow it to its hazard, its barriers, its action and the indicator it moved, without leaving the record.
How eAviora answers
One operational graph: occurrences, hazards, actions, audits, findings, indicators and the risk profile are linked records.
See the graph02Risk libraryDoes the risk library ship ready to use, or is it a blank canvas?
In the demo, ask to see
Open the bow-tie for a risk you face before anyone has configured anything.
How eAviora answers
85 bow-tie models, 682 named barriers, 183 scenarios and 516 indicator definitions ship in the box.
See the library03AI oversightIs every AI proposal reviewed by a person, and the decision kept?
In the demo, ask to see
Ask the AI to classify a report, reject its proposal, then check that the record keeps your decision and your name.
How eAviora answers
On a record, eAvy and the agents propose and a person accepts, edits or rejects, with their name kept. A bulk import you start can apply high-confidence classifications, marked unvalidated, and sends the rest and a sample to a person.
See eAvy04ClosureCan a record close while its risk is open, and can a machine set that state?
In the demo, ask to see
Try to close an action that has had no effectiveness check, then ask the AI to move a record forward.
How eAviora answers
Barriers are rated before an occurrence moves on, and an action closes after its effectiveness check, on by default. No AI can move a record’s workflow stage: a person does.
See the gates05Risk pictureIs the risk picture computed, or assembled by hand for each review?
In the demo, ask to see
Ask where this month’s risk picture came from, number by number.
How eAviora answers
The Safety Risk Profile is computed from seven components and kept as snapshots, so last year can be shown as it was.
See the profile06IsolationIs each organisation isolated in the database itself?
In the demo, ask to see
Ask how one customer’s records are kept from another’s, and which layer enforces it.
How eAviora answers
Row-level security on every organisation’s tables, forced on, under a database role that cannot bypass it.
See the trust center07StandardsWhich rule catalogues ship, and how do you add one that does not?
In the demo, ask to see
Ask to open your own regulator’s requirements and declare one against its evidence.
How eAviora answers
The IOSA Standards Manual, editions 18 and 19, and Transport Canada’s CARs ship. Any other rule, such as FAA Part 5, is registered as a standard of your own.
See complianceRed flags
Five things to watch for in a demo
- Copy and paste between modules. If the presenter re-types a reference to get from the occurrence to its action, the records are not linked.
- An empty risk model. A blank matrix and bow-tie mean months of authoring before the first assessment.
- AI nobody approves. If a suggestion lands on the record with no name beside it, ask who answers for it in the audit.
- A status someone typed. Ask what the green on the dashboard is computed from.
- An export without the links. Records you cannot take out with their links are records you cannot leave with.
Evaluating eAviora
Four steps, each with an exit
No big-bang migration. Each step has an exit, and each step earns the next.
What happens
Bring a real scenario. Watch it move from report to closure.
Choose the scenario: an occurrence, a finding or an audit from your own operation.
Your exit
Stop here with nothing to undo.
What you get
Your operation, not a demo tenant.
Real occurrences, findings and audits in a bounded evaluation group, with success criteria agreed up front.
The people who built it.
Evaluation runs with the engineers who own the workflow, not a handoff to a ticket queue.
A migration path, priced.
What it takes to move your history in, quoted against your operation size and the modules you run.
What we ask
Real scenarios.
Bring live occurrences, findings and audits, not toy data. An evaluation on sample data proves nothing about yours.
A review cadence.
A standing session where we watch your team work and fix what slows them down.
A verdict on record.
If a gate fails your audit, say so on record. That is the outcome the evaluation is for.
How pricing works
No list prices. Pricing is quoted against your operation size and the modules you run, on an annual subscription, and AI use is metered in credits from one shared monthly pool.
Ask us the seven questions
On your own records, with the people who build eAviora.