AI- and Ontology-Based Enhancements to FMEA for Advanced Systems Engineering: Current Developments and Future Directions
This paper reviews how integrating Artificial Intelligence and ontologies transforms traditional Failure Mode and Effects Analysis (FMEA) into a dynamic, data-driven, and semantically enriched process within Model-Based Systems Engineering, while addressing current challenges and outlining future directions for more resilient and intelligent engineering workflows.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are building a massive, incredibly complex Lego castle. In the old days, when engineers wanted to make sure this castle wouldn't collapse, they used a method called FMEA (Failure Mode and Effects Analysis). Think of FMEA as a giant, static spreadsheet or a long checklist. A team of experts would sit around a table, brainstorming, "What if this brick falls out?" or "What if this tower gets too heavy?" They would write their answers down in plain English on paper or in Excel.
The problem is, modern engineering (like building self-driving cars or advanced robots) is too complex for a simple spreadsheet. The "castle" has millions of moving parts, changes every day, and the experts can't possibly remember every connection. The old checklists become outdated the moment they are written, and they are full of human guesswork.
This paper argues that we need to upgrade this process using two powerful new tools: Artificial Intelligence (AI) and Ontologies.
Here is a simple breakdown of how the paper suggests fixing this:
1. The Old Way: The Static Checklist
Traditionally, FMEA is like a paper map drawn by a single explorer.
- The Flaw: It's slow, subjective (based on who is in the room), and disconnected from the actual building process. If you change one brick in the castle, you have to manually update the paper map. Often, people forget to do this, so the map becomes useless.
- The Result: You might miss a hidden crack in the foundation because the checklist didn't ask about it, or because the expert who wrote it was tired.
2. The New Tool #1: Artificial Intelligence (The Super-Reader)
The paper suggests using AI to act like a super-fast, tireless librarian who can read millions of maintenance logs, repair reports, and design notes instantly.
- How it works: Instead of humans guessing what might break, the AI scans thousands of past records to find patterns. It can say, "Hey, every time this specific type of motor gets hot, it fails in this specific way."
- The Benefit: It automates the boring parts. It can predict failures before they happen and prioritize which risks are the most dangerous, removing the human bias of "I think this is risky" vs. "I think that is risky."
- The Catch: Sometimes the AI is a "black box." It gives an answer, but it can't always explain why it thinks that, which makes engineers nervous about trusting it with safety-critical decisions.
3. The New Tool #2: Ontologies (The Universal Translator)
This is the most important concept in the paper. An Ontology is like a strict, shared dictionary or a rulebook for meaning.
- The Problem: In engineering, one team might call a part a "sensor," while another calls it a "detector." To a computer, these are two different things. This causes confusion and breaks the connection between different parts of the project.
- The Solution: An ontology forces everyone to agree on exactly what a "failure," a "function," or a "structure" means. It creates a structured web of knowledge where everything is connected logically.
- The Analogy: If AI is the librarian, the Ontology is the library's catalog system. It ensures that when the AI finds a "broken wheel," it knows exactly which part of the car that refers to, how it connects to the engine, and what happens if it breaks. It turns messy text into a clear, logical map.
4. The Magic Combination: AI + Ontology
The paper's main idea is that you need both to make this work.
- AI without Ontology is like a smart student who reads a lot but doesn't understand the rules of the game. It might make up facts (called "hallucinations") or get confused by jargon.
- Ontology without AI is like a perfect dictionary that no one uses because it's too hard to update manually.
- Together: The Ontology provides the ground rules (the "truth"), and the AI uses those rules to learn and predict.
- Example: The AI might suggest, "This part is likely to fail." The Ontology checks this against the rules and says, "Yes, that makes sense because this part connects to a known weak point." This makes the AI's answer explainable and trustworthy.
5. The Big Picture: Model-Based Systems Engineering (MBSE)
The paper places all this inside a bigger concept called MBSE.
- Old Way: You have a 3D model of the car, and a separate paper document (FMEA) about its risks. They don't talk to each other.
- New Way: The FMEA is built directly into the 3D model. If you change the design of the car in the model, the "risk map" updates automatically. The AI and Ontology act as the glue that holds the design, the safety rules, and the real-world data together.
Summary of Challenges
The paper admits this isn't a magic wand yet. There are hurdles:
- Data Quality: AI is only as good as the data it eats. If the old records are messy, the AI gets confused.
- Trust: Engineers need to understand why the AI made a decision. The Ontology helps here by providing the "reasoning trail."
- Standardization: Everyone needs to agree on the "dictionary" (Ontology) so that different companies and tools can talk to each other.
The Bottom Line
This paper proposes a future where building complex systems isn't about filling out static forms. Instead, it's about creating a living, intelligent knowledge system. In this system, AI acts as the brain that spots patterns, and Ontologies act as the skeleton that keeps everything logically connected. This allows engineers to build safer, more reliable systems that can adapt and learn as they are being designed and used.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.