- Sector
- AI and quality audit
- Date
- 2026
- Delivered by
- Final-year project · Stellantis MEA
- Built with
- Claude, via AWS Bedrock
- Sourced answers
- Guided audit
- 10 documents generated
- 37 h → 2 h
- 01 · The problem
A quality audit is mostly writing
Goal
A quality audit in a large automotive group draws on standards, internal procedures and customer requirements scattered across several systems. The auditor has to cross-check everything by hand, then write notes, questionnaires, presentations and action plans: slow work, and different from one auditor to the next.
Result
ARIA centralizes that knowledge, answers with its sources and drafts the audit documents. The auditor keeps control of the judgment and no longer re-types anything.
- 03 · Who decides?
ARIA proposes, the auditor decides
In a regulated profession, the machine does not decide. ARIA prepares and drafts; at every step that commits the audit, the decision goes back to the auditor.
Propose
Reads the planning sheet and pre-fills the audit details.Propose
Checks the procedures, drafts the questionnaire and proposes a schedule.Propose
Generates the scoping note, the kick-off note and the opening presentation.Propose
Extracts findings from the evidence, with rating and risk level.Propose
Drafts the action plans, the closing presentation and the conclusion note.Decides
Confirms the scoping details.Decides
Approves the audit schedule.Decides
Reviews each document before using it.Decides
Confirms each finding before it enters the file.Decides
Approves the action plans (approval note R4).01 · Scoping
ARIA proposes
Reads the planning sheet and pre-fills the audit details.The auditor decides
Confirms the scoping details.02 · Preparation
ARIA proposes
Checks the procedures, drafts the questionnaire and proposes a schedule.The auditor decides
Approves the audit schedule.03 · Kick-off
ARIA proposes
Generates the scoping note, the kick-off note and the opening presentation.The auditor decides
Reviews each document before using it.04 · Findings
ARIA proposes
Extracts findings from the evidence, with rating and risk level.The auditor decides
Confirms each finding before it enters the file.05 · Closing
ARIA proposes
Drafts the action plans, the closing presentation and the conclusion note.The auditor decides
Approves the action plans (approval note R4).
ARIA sends nothing to the customer: it generates documents that the auditor downloads, reviews and sends themselves.
- 04 · Technology
The same architecture, two versions
ARIA exists as a production version on Databricks, and as a local version that uses only free tools. The twelve layers are the same; only the technology of each changes. Switch from one version to the other.
The version deployed at Stellantis MEA, integrated into the company's data platform.
- Databricks app, deployed as a bundle
- Claude through the enterprise AWS Bedrock gateway
- Managed vector search: 6 indexes
- Data in Delta tables and governed volumes
- 05 · Results
From 37 hours to 2 hours of drafting per audit
Measured on the work of an auditor from the pool: drafting an audit's documents goes from 37 hours to about 2 hours. The time recovered goes back to what matters: preparing, running and analyzing the audit.
95%
Time saved
On drafting the documents
37 h → 2 h
Per audit
Average, auditor from the pool
35 h
Recovered per audit
For execution and analysis
10
Documents generated
Word, PowerPoint and Excel
Measurements from the ARIA project, presented in its monthly review at Stellantis MEA.
- 06 · Goal and result
A tool built for a real audit cycle
Goal
Design, as a single builder and as my final-year project at ENSA Agadir, a quality-audit assistant that respects the profession's rules: answer only with sources, guide the auditor and produce documents ready for review.
Result
ARIA was designed, built and defended before an academic and industry jury, then validated in a real audit cycle at Stellantis MEA.
- 02 · How ARIA works
Six diagrams to see what it really does
A cited answer, an audit end to end, a three-mode agent, evidence photo analysis, knowledge intake and procedure lookup: each diagram follows how the system really works.