Define the answer you need
Goal, users, acceptance criteria and the limits of the request, before any query is opened.
Arcedal / MRO reporting
Reporting for airlines and MROs
Reporting that understands context.
A specialist service to build and maintain MRO reports, starting from a defined need, knowledge of the environment and functional review.
See how we work01 / The service
The query comes later.
Context comes first.
A report is more than SQL. It is an answer that has to respect the operational logic, the data model and the rules the team relies on to make decisions.
Arcedal starts from a well-defined need and turns the available knowledge into a reviewable delivery.
A person reviews every delivery before it reaches your team: the platform speeds the work up, it does not make the decisions.
- 01
- Document the reports you already have: what each one does, in business and technical terms, ready to publish to Confluence.
- 02
- Prepare SQL checked against your TRAX schema and deliver it as a JasperReports report (.jrxml) with its parameters.
- 03
- Measure impact before a change: which reports and columns are affected, for example in a TRAX upgrade.
- 04
- Keep a glossary and a map of table relationships that business and technical teams share.
02 / The process
From request to a delivery you can review.
Scope is set before work starts: which question the report must answer, from which tables, and how it will be signed off.
Review context and references
Environment, access, existing reports and required material, before a delivery is confirmed.
Prepare, cross-check and deliver
The Arcedal team does the work; the client team reviews the result and the business rules.
03 / The platform
Technical knowledge should not be scattered.
Our own platform keeps the thread between reports, SQL, tables, glossary and known relationships. Everything it proposes can be reviewed: it cites the reports and tables it relied on.
It works from the schema structure and the SQL of your reports. It does not connect to your operational database and does not need to see your data.
04 / Before we start
What is worth making clear.
Fit is confirmed against a real need. These answers do not replace that first review.
Are we buying a service or a platform?
The initial offer is a full service: the Arcedal team uses the platform to deliver the agreed work. Self-service SaaS is a possible future option, not the current offer.
Do you need access to our database?
No. We work from the schema structure (tables, columns and volumes) and the SQL of the reports you already have; your operational data stays in your installation. Running queries and bringing back results is a capability in development: when it arrives it will be optional and under your control.
Where does the AI run?
Wherever you decide. The platform works with local models, on your own infrastructure, or through an API with the provider of your choice. With the local option, neither the schema nor the SQL of your reports leaves your network.
What exactly do you deliver?
The reviewed SQL, the report ready for JasperReports (.jrxml, with its parameters) and its documentation: what it is for, what it does and which tables it uses.
Does it work with any MRO system?
Today we work on TRAX/eMRO with Oracle SQL. For another system we first review its schema and reports, and we will say so plainly if it is not a fit.
Is the generated SQL guaranteed?
The platform checks that every table and column exists in your schema, and a person reviews the logic and performance before delivery. Final acceptance is yours, against the criteria agreed at the start.
How much does it cost and how much time does it save?
Price, timeline and measurement depend on scope and the capacity required. This page does not publish savings figures, rates or schedule commitments.
Next conversation
Bring us a concrete need.
The first exchange is about identifying the report, the system and the information needed to assess fit.
Discuss a reporting need
No forms, no sign-up: you email us and we reply by email.