AI for Capella: Connect Capella to Your AI Ecosystem

Webinar Transcript Summary

 

Sept 2026 |  Stéphane Lacrampe (Obeo) | EN       

Video       Slides

Introduction

Artificial intelligence offers new opportunities for Model-Based Systems Engineering (MBSE), particularly in accessing, analyzing, and maintaining complex system architectures. However, its adoption raises important questions about reliability, traceability, and engineering responsibility.

Obeo's new AI for Capella solution addresses these challenges by enabling AI agents to interact directly with Capella models while preserving their consistency and integrity. Rather than replacing systems engineers, the objective is to simplify modeling activities, accelerate analysis, and support better-informed engineering decisions.

Why AI for Capella?

Capella models provide a particularly valuable foundation for AI because they contain structured engineering knowledge based on the Arcadia methodology.

Unlike unstructured documents, these models explicitly describe capabilities, functions, components, interfaces, dependencies, and relationships across engineering viewpoints.

This structured information enables AI agents to interpret engineering questions, navigate complex architectures, identify dependencies, and detect potential inconsistencies.

The main objective is to reduce time spent on repetitive modeling operations and information retrieval, allowing engineers to focus on architectural decisions and system design.

Architecture and Integration

AI for Capella adopts a Bring Your Own AI approach, allowing organizations to use their preferred AI environments, including ChatGPT, Claude, or locally hosted language models.

The integration relies on the Model Context Protocol (MCP), an open standard connecting AI agents to external tools.

An MCP server installed within Capella exposes controlled modeling capabilities to AI agents. These agents can query, create, or modify model elements through Capella's native mechanisms rather than manipulating model data directly.

Access permissions, including read-only and editing profiles, ensure that engineers retain control over authorized operations.

The architecture also enables AI agents to combine Capella information with external engineering repositories, including requirements management, PLM, and documentation systems, when suitable connections are available.

Live Demonstrations

The webinar illustrated several practical applications using Capella models.

Model Creation and Onboarding: An AI agent guided a new user through Arcadia concepts and automatically created an optical mouse architecture, including components, functions, exchanges, diagrams, and functional chains.

Architecture Exploration: Using an In-Flight Entertainment System model, the agent generated accessible system summaries, explained component responsibilities, traced capabilities to physical equipment, and identified incomplete architectural relationships.

Impact Analysis and Consistency: The agent evaluated potential consequences of requirement changes, aircraft platform modifications, and equipment failures. It also detected inconsistencies between system and logical architecture states, including missing safety-related behavior.

Architecture Evolution: A new Wi-Fi capability was introduced by identifying reusable components, creating additional actors and functions, and updating architectural diagrams.

Requirements and Documentation: The AI generated preliminary design requirements and review documentation. It also demonstrated the possibility of producing M2Doc templates for repeatable, model-based document generation.

Automotive System Design: Starting from an Excel spreadsheet containing supplier components, requirements, and technical constraints, the agent generated an automatic emergency braking architecture. It then evaluated mass, cost, power consumption, and latency, identifying a latency exceeding the project target by 26 milliseconds.

These demonstrations highlighted the potential of AI to accelerate modeling and analysis while also revealing the importance of precise prompts and engineering validation.

Roadmap

AI for Capella supports several Capella versions and follows a regular development cycle, with releases approximately every eight weeks.

Upcoming priorities include improved reliability, simplified installation, enhanced documentation, broader AI compatibility, and additional modeling automation capabilities.

Future developments will also extend AI to Publication for Capella, enabling stakeholders to explore published architecture models through natural-language queries without installing Capella.

Q&A Highlights

  • Q: How can AI hallucinations be limited?
    A: AI-generated conclusions must be reviewed by engineers. Detailed prompts and deterministic model queries, potentially implemented through Python for Capella or M2Doc, can help verify results.
  • Q: Will AI replace experienced systems engineers?
    A: No. AI accelerates repetitive operations and analysis, but engineering judgment, contextual understanding, architectural decisions, and validation remain human responsibilities.
  • Q: Can AI for Capella interact with other add-ons?
    A: Yes, particularly when add-ons expose modeling operations through diagram palettes. Requirements add-on support is available, while broader PVMT integration is being developed.
  • Q: Can AI combine Capella information with external engineering repositories?
    A: Yes, provided the AI environment has access to those repositories. AI for Capella supplies the connection to Capella rather than directly integrating every external system.
  • Q: Can AI analyze relationships between system and subsystem models?
    A: AI can work across multiple Capella projects, but specific system-to-subsystem relationship analysis has not yet been validated.
  • Q: Is Microsoft Copilot supported?
    A: Initial integrations have been successful, although compatibility may depend on the Copilot configuration and subscription.