TOKAI and RAT
ATS notifications, occurrences, risk analyses and safety recommendations in one system, with E5X export and direct submission to ECCAIRS.
More than 80 users worldwide.
Read the case study →Capability 01
Safety reporting and investigation platforms
Software that takes a safety occurrence from the first report to a finished investigation, and on to the authority, across states, languages and legal regimes. We built the TOKAI web application and RAT for EUROCONTROL, and EMCIP for EMSA.
The problem
One record, many hands, a legal clock.
A reporting platform has to work for the person filing a notification at the end of a shift and for the investigator who opens the same record weeks later. In between, someone scores the risk, someone writes a safety recommendation, and the mandatory report has to reach the authority in a format its system reads.
The clock is set by regulation. Regulation (EU) No 376/2014 gives organisations 72 hours to report an occurrence to the competent authority. Each organisation designs its own report templates, and the platform has to work in several languages.
What we have built
Two platforms, for air traffic and for shipping.
EMCIP
Casualty notification and investigation for every EU state, Iceland and Norway: a taxonomy editor, data-quality rules, workflows, a public portal with open data, and transfer to IMO GISIS. Built from 2017, live in September 2018, developed until 2026.
Read the case study →Standards and data formats
Regulations and data formats.
- (EU) No 376/2014
- (EU) 2015/1018
- E5X format and ECCAIRS
- RAT methodology
- Directive 2009/18/EC
- IMO GISIS
How we would approach yours
Start from the reports people already file.
- Read what existsThe forms, spreadsheets and systems your people use today, and what the regulation asks of them.
- Model the taxonomy firstAgree the fields and classifications before drawing a single screen, so the data holds up for as long as the platform runs.
- Plan the exchange earlyE5X to ECCAIRS, GISIS, or your authority's own format, designed in from the first release.
- Decide where it runsOn your premises, in the cloud or on a closed network.
- Release early, then regularlyA first release your users can work in, then regular releases from the same team.
A typical engagement
Build and run, under a framework contract.
- Model
- Build and run
- Team
- A product team that designs, builds, deploys and supports it
- After launch
- Regular releases and support from the same team
Next step
Tell us what you need.
Need a platform of your own?
Reporting, investigation or safety data, built and supported through its service life.
Contact usTaking over a reporting platform?
We support and extend systems another team built.
Support and evolutionWho else will ask, and what they'll want
- ProcurementCompany details, certification and references, on Trust.
- IT securityCertification facts and written policies, on Trust.
- Your legal teamWhat we sign under Part-IS and NIS2, on Trust.