Publication for Capella

System architecture at the heart of your engineering process


Publication for Capella provides a seamlessly integrated view between your system architecture and related engineering activities (IVVQ, Requirements, etc...).

Publish Capella models on a web server, connect them with requirements, change requests, test cases, releases, etc... defined in third-party repositories, and expose them to authorized stakeholders.

The supported repositories include Siemens Polarion® and IBM Jazz.


Request a quote Discover the features

Integrated sources of truth

Author system design and work items with dedicated, but connected, tools
and make this data available across different engineering disciplines.



Expose Models

Systems engineers can expose their Capella models by regularly publishing them on a server.

The model elements, with all the related diagrams and the linked artifacts, become easily navigable from a web browser to any authorized user.


Expose Capella models

Manage Traceability

Systems engineers, working with Capella, can collaborate with other engineers working with connected ALM or RMS tools.

Both, they can create and manage synchronized traceability links between architecture elements and artifacts such as requirements, change requests, test cases, releases, etc...


See how-to drag&drop requirements from Siemens Polarion


See how-to drag&drop requirements from IBM DOORS Next

Manage traceability between Capella models and requirements tools such as Polarion and Doors

Much more than just a static HTML export!

In contrast to the static documentation generated from a Capella model,
Publication for Capella provides dynamic access to a live model deployed on a server.


Better communication and collaboration

Break silos between teams by providing online access to an integrated view of your system architecture.
It facilitates your engineering teams to reuse work items and system elements.



Systems Engineer

Define an integrated system architecture federated with third-party repositories, and decide when to expose this consistent content to other stakeholders.

From the Capella Workbench

  • Publish Capella models on the Publication server.
  • Drag&drop artifacts defined in connected repositories directly into Capella to create traceability links.
  • Manage the traceability links from Capella.
Publication for Capella - Links management

Project Engineer

Create requirements, issues, test cases, etc, in third-party repositories, and collaborate with systems engineers to align these artifacts with the system architecture.

From a Third-Party Repository connected to the Publication server (ex: Polarion or DOORS Next)

  • Manage traceability links between artifacts defined in a connected repository and Capella model elements.
Publication for Capella - Links management

Interested Stakeholder

Benefit from an integrated and consistent view of the system architecture: a detailed model with verified traceability relationships to related engineering artifacts.

From a Web Browser

  • Find an element in a published Capella model.
  • Browse its properties, relations and diagrams.
  • View its traceability links and related artifacts.
Publication for Capella - Browse links

Project Administrator

Control how the Capella models are exposed to stakeholders, and how they can be integrated with various third-party repositories containing engineering artifacts.

From the Publication Server

  • Configure the type of links between the Capella model elements of a project and third-party artifacts.
  • Connect third-party repositories to the Publication server.
  • Manage authorized users on a per-project basis.
Publication for Capella - Configure links

Flexible Deployment

Team for Capella On-Premise


The server is deployed on your own infrastructure

Team for Capella Cloud


The server is installed on a Cloud infrastructure managed by Obeo
Learn more  

Supported Repositories

Siemens Polarion®
(versions 19 to 23)


IBM® Jazz
(versions 7.0.2 to 7.0.3)

Yes (but some limitations exist if Global Configuration is activated)

Other tools

Evaluation required: the other tool needs to support OSLC-AM providers


 Read the Change Log


Digital Thread from Requirements to Architecture

Efficiently maintain CONSISTENCY and ALIGNMENT between Capella models and third-party repositories (like ALM or RMS).

  • Reduced errors from managing identical data on different systems
  • Less time spent searching for data in different sources
  • Informed decisions based on up-to-date information



Digital thread in action!

Watch this video to see how Publication for Capella 
enables a digital thread between Capella and ALM/RM tools




Integration using standard APIs

Third-party repositories such as Application Lifecycle Management Systems (ALM) and Requirements Management Systems (RMS) allow you to efficiently capture, organize, and link artifacts: requirements, tasks, issues, change requests, test cases, releases, etc. Rather than spreadsheets, using such tools is the best solution to efficiently manage your projects.

To enable traceability with objects managed in other repositories, some ALM and RMS tools support OSLC (Open Services for Lifecycle Collaboration), a set of specifications for APIs to interact with data on the web: searching, visualizing, and analyzing.

OSLC (Architecture Management) is an OSLC specification for exposing fine-grained architectural data to external systems via a modern Linked Data approach: no import/export between tools, resources are connected together to create a virtual continuity between repositories and to make it easier for tools to work together in different areas. 

By supporting this specification, Publication for Capella enables the traceability between any system element in Capella and any artifact in OSLC-compliant tools.




Contact Us