Skip to main content

Eclipse Capella Industry Consortium Charter

June 12, 2017

Definitions

A list of definitions of terms used in this document.

  • Arcadia refers to the MBSE method supported by Capella.
  • The Eclipse Capella Industry Consortium is referred to as the Capella IC in this document
  • Capella Project (“Capella”) refers to the Polarsys project hosted at https://www.polarsys.org/capella/.
  • Capella refers to the Polarsys Solution consisting of a ready-to-use and well-tested package with the Capella Project and its open source dependencies, as described at https://www.polarsys.org/solutions/capella.[a][b]
  • Capella Add-ons refers to the plug-ins which extends the scope and feature set of Capella, including connectors, and which are not included in Capella itself.
  • Capella Studio refers to the solution consisting of Capella and its SDK which is used to extend Capella.
  • Model Based Systems Engineering (MBSE) refers to model-based systems design and architecture.
  • Suppliers refers to any organization providing commercial software related offerings, including proprietary products, professional services, training, and mentoring, related to the technologies within the scope of this consortium.

Vision/Mission

To fulfill the overall MBSE vision, industrial users needs a mature, full-featured, sustainable solution which can be widely distributed as an open source alternative to existing proprietary modeling tools.

The Capella tools, in association with the Arcadia method, can meet this need.

The Capella ecosystem will include companies developing complex systems and software, suppliers providing offers on top of Capella and academics researching MBSE themes. A place to foster collaboration, share investments, exchange best practises, and to leverage Open Innovation will ensure a vibrant ecosystem that will enable the co-development of new MBSE capabilities.

The Capella IC aims to host the Capella Ecosystem stakeholders in a vendor neutral way, organized by an open governance model.

Overall Goals

The main goal of the Capella IC is to make Arcadia the leading system engineering method and Capella the leading MBSE tool. Other key goals are in the following thematic areas:

Knowledge sharing

  • Share MBSE experiences and case studies among consortium members to enable broad adoption of Capella and Arcadia in operational projects.
  • Establish a technology watch service to help members leverage innovation in Capella and its ecosystem.
  • Keep up-to-date with new and noteworthy, future improvements, success stories, and user feedback.
  • Organize private exchange workshops between members

Joint development financing

  • Coordinate investments from consortium members in the different aspects of the overall MBSE solution to reduce development time, risk, and costs, and to maximize ROI

Product Management

  • Capture, consolidate, and manage requirements from the different consortium members and application domains
  • Define development priorities based on consortium members requirements/needs
  • Discuss the roadmap among users and contributors
  • Operate a transparent process supported by tools.

Promotion

  • Promote the use of Capella as a leading industrial MBSE solution
  • Provide materials to explain the value of Capella and Arcadia to executives and managers

Community Development

  • Provide a focal point for organizing collaboration and creating partnerships among suppliers, end-users, and research/academia

Technical Scope/Projects

The initial areas of work for the Capella IC include:

  • Capella
  • Capella Studio
  • Underlying technologies and plug-ins used by Capella and Capella Studio
  • Capella Add-ons

Additional areas of work may be defined in the future by the Steering Committee of the IC.

Modeling Processes

The scope of the Capella IC includes the following key modeling processes:

  • Definition of the Problem - Customer Operational Needs Analysis
  • Formalization of system requirements - System Needs Analysis
  • Development of System Architectural Design - Logical Architecture (Notional Solution)
  • Development of System Architecture - Physical Architecture
  • Formalize Component Requirements - Contracts for Development and IVVQ (Integration Validation Verification Qualification)
  • Co-Engineering, Sub-Contracting and Multi-Level Engineering
  • Adaptation of Arcadia to support new dedicated Engineering Domains and to improve integration capabilities with other tools

Membership

Summary of Membership Classes and Membership Fees

Membership is based on a one year renewable commitment. As Capella IC is a neutral and transparent consortium, the rules for joining are clearly defined by the Working Group participation agreement and the Eclipse membership agreement.

As the Capella IC is a sub-group of the Polarsys Working Group, and as Polarsys itself is a working group of the Eclipse Foundation, there are two additional membership requirements for joining the Capella IC:

  • Eclipse Solution membership as a minimum requirement, in compliance with the Eclipse bylaws and processes
  • Polarsys membership, in compliance with the Polarsys charter

All Capella IC members must pay both Eclipse Membership fees and Polarsys WG Membership fees. No additional fees are mandatory to join the Capella IC.

Each year, Polarsys members are entitled to allocate a pre-determined portion of their membership fees to ICs and Common Activities. To join the Capella IC, a minimum 20% of this pre-determined portion, must be allocated to the Capella IC.

The fees to join the Capella IC are currently USD 0. Fee changes are at the discretion of the Capella Steering Committee.

Membership Classes

The membership classes of the Capella IC are designed to reflect the varied interests of the members. The membership class of each Capella IC member is confirmed once per year.

Driver Member

Driver members want to influence the development of Capella and be an integral part of the group of organizations that govern the development of the open source MBSE solution. They invest a substantial amount of resources to sustain the Capella IC activities and contribute to the development of the open source technologies.

Typical Drivers members are organizations that use MBSE solutions at the core of their development process and who consider Capella as a strategic asset.

Each Driver member must document annually a minimum investment in the Capella IC activities such as allocation of internal developers, features outsourcing, maintenance and support contribution, marketing. These activities do not include investments for internal deployments within the members’ teams or for private customizations. The minimum annual amount is $50 000. The Steering committee is responsible for the analysis and approval of the annual investment documentation.

Participant Member

Participant members participate in the development of the Capella ecosystem. They contribute to the development and adoption of Capella according to their roles, such as the development of viewpoints for tools providers, participation at conferences, or providing requirements or user experiences for end-users.

Research/Academia Member

Research/academia members are Universities and research organizations that want to participate in the development of the overall MBSE solution based on Capella. Their contributions take the form of addressing various relevant research topics, using Capella for teaching/training purposes, and contributing to the overall development of the ecosystem.

Committees

The Capella IC has 3 standing committees: the Steering Committee, the Product Management Committee and the Marketing Committee.

Committee members and Chairpersons are elected and serve for one year from April 1 to March 31 of the following year, or until their respective successors are elected or nominated, or as otherwise provided for in this charter.

Steering Committee

The Capella IC is led by the Steering Committee.

Composition

  • Each Driver Member has one seat on the Steering Committee.
  • Participant Members elect one representative.
  • The Chair of the Marketing Committee and Product Management Committee each have one seat.
  • The Chair is elected by a simple majority of Steering Committee members.

Responsibilities of the Steering Committee

  • Define the overall strategic directions of the consortium.
  • Define and manage the consortium budget.
  • Define and amend the charter.
  • Define and implement the overall strategy for the development of the Capella ecosystem.

Product Management Committee

The Product Management Committee reports to the Steering Committee.

Composition

  • Each member has one seat.
  • The Chairperson is elected by a simple majority of the Product Management Committee members.

Responsibilities of the Product Management Committee

  • Capture, consolidate, and manage requirements from members.Define development priorities based on consortium members’ requirements/needs.
  • Define and maintain the technical/product roadmap and development priorities.
  • Ensure the consistency and integrity of the architecture and its components.
  • Interact with research groups involved in consortium activities.

Marketing Committee

The Marketing Committee reports to the Steering Committee.

Composition

  • Each member has one seat.
  • The Chairperson is elected by a simple majority of the Marketing Committee members.

Responsibilities of the Marketing Committee

  • Define a marketing strategy to promote Capella.
  • Create marketing materials.
  • Organize communication on Capella.
  • Organize events.
  • Interact with the Polarsys Marketing Committee.

Back to the top

-->