Skip to main content

Eclipse Papyrus Industry Consortium Charter

October 17, 2015

Definitions

A list of definitions of terms used in this document.

  • Model Based Engineering (MBE): We use the term Model Based Engineering (and the acronym MBE) as a generic term to refer to model-based or model-driven development. In this document, this term could be replaced by other terms used in the industry such as Model Driven Development (MDD), Model Driven Architecture (MDA), and Model Based System Engineering (MBSE).
  • Papyrus Industry Consortium is referred to as Papyrus IC in this document
  • Papyrus Toolsuite: We use the term Papyrus Toolsuite to refer to the solution composed of Papyrus and related open source components.
  • Suppliers: We use the term Supplier to refer to any organization providing commercial offerings related to the technologies developed in the scope of this consortium, including proprietary products, professional services, training, and mentoring.

Vision/Mission

  • WHY is it needed
    • To fulfill the overall MBE vision, the industry needs an open source alternative to existing proprietary modeling tools to eliminate vendor lock-in, provide the ability to develop new tool features and integrations as required, and ensure long-term availability
    • To develop the advanced MBE tool offerings end-users need, suppliers need access to a customizable, extensible, and open tool platform
    • To develop new MBE capabilities, and enable innovations and technology transfer, Research/Academia needs access to an open industrial platform that can be used for both research and teaching purposes
  • WHAT it does
    • Develop a customizable and extensible industrial-grade open source MBE tool suite based on the Papyrus/Eclipse platform, other key open source technologies, and leading industry standards
    • Develop a MBE methods and processes body of knowledge comprising of agreed best practices and use cases guiding the usage of this tool suite.
  • WHO it does it for
    • or companies developing software-based systems, from Enterprise Software to Internet of Things (IoT) and Cyber-Physical Systems (CPS)
  • HOW it does what it does
    • By fostering and leveraging collaborations between members of a composed of end-users suppliers, and research/academia

Overall Goals

  • Development of industrial-grade open source solution
    • Plan and coordinate the development of an industrial-grade Papyrus Toolsuite to ensure both the availability of key capabilities, and the evolution and long-term availability of a complete MBE solution
    • Capture, consolidate, and manage requirements from the different consortium members and application domains
    • Define development priorities based on consortium members requirements/needs
    • To meet this objective, a number of different aspects must be addressed, including QA/testing, customization, packaging, distribution, training, commercial support, and continuous evolution/integration
  • Joint development financing
    • Coordinate investments from consortium members in the different aspects of the overall MBE solution to reduce development time, risks, and cost, and maximize ROI
  • Knowledge sharing
    • Share MBE knowledge, expertise, and experiences among consortium members to enable broad adoption of the Papyrus Toolsuite and MBE in general
    • Establish a MBE methods and processes body of knowledge to help improving development productivity and product quality
  • Promotion of open source solution
    • Promote the use of the Papyrus Toolsuite as a leading industrial MBE solution
  • Development of the community
    • Work together on the development of a vibrant community of end-users, suppliers, and research/academia focused on the development, promotion, and broad adoption of the Papyrus Toolsuite
  • Standardization
    • Take leadership position in standardization initiatives to ensure that the open source solution is based on open industry standards
    • Leverage existing standards developed by lead industry standard organizations, including OMG, ISO, and INCOSE
    • Develop close relationship with those lead industry standard organizations to be in a position to influence the development of the required standards
  • Collaboration on research projects
    • Define research priorities to ensure mid/long-term evolution of the open source modeling solution
    • Foster collaborations between consortium members to drive strategic research projects to allow key evolutions
  • Contribution to MBE education and training
    • Work in collaboration with academic partners and universities to help establishing high-quality education programs in MBE
    • Encourage consortium members to directly contribute to the training of both undergraduate and graduate students

Technical Scope Initial draft

It is very important to mention that the technical scope of the consortium will be defined and approved by the Steering Committee.

Also, the technical scope will be periodically reviewed and updated by the Steering Committee based on the needs of the consortium members and the level of available resources.

Modeling Aspects

The scope of the Papyrus IC will include the following key modeling aspects

  • System modeling
  • Software modeling
  • Architecture modeling
  • Functional modeling
  • Information/data modeling
  • Business process modeling
  • Requirements modeling

Modeling will be based on use of standards (UML and SysML) and Domain Specific Modeling Languages (DSML) defined as extensions of standard languages, including UML-RT, RT-UML, and xtUML.

Membership

Main elements of Membership Classes

  • Membership commitment is on an annual basis
    • Membership is checked annually and can be terminated, suspended or changed to a different membership class by the Papyrus IC Steering Committee if the member fails to deliver membership fees or previously committed results.
  • Eclipse/Polarsys Requirements
    • Be at least Eclipse Solution members
    • Adhere to the Eclipse bylaws and processes
    • Adhere to the Polarsys charter
  • Membership Fees
    • The Papyrus IC is established as a Special Interest Group (SIG) of the Eclipse Polarsys WG
      • As such, all Papyrus IC members are also members of Polarsys without any additional fees
    • Each Papyrus IC member must pay both Eclipse Membership fees and Polarsys WG Membership fees as defined below
      • Papyrus IC members must at least be Eclipse Solution members. Eclipse membership fee details can be found on the Eclipse website
      • Papyrus IC members must pay Polarsys membership as defined in the Polarsys charter with the following equivalence
        • Papyrus IC User Lead Member -Polarsys Steering Committee fees
        • Papyrus IC User Participant Member - Polarsys Participant Member fees
        • Papyrus IC Supplier Lead Member - Polarsys Participant Member fees
        • Papyrus IC Supplier Participant Member - Polarsys Participant Member fees
        • Papyrus Research/Academia Member Polarsys Guest member fees
        • Papyrus IC Observer Member - Polarsys Guest member fees
  • Resource allocation
    • Number of days per year that a member company is committing to different aspects of the consortium activities as required by the different committees
    • In the calculation of the overall member contribution, these resources will be accounted for at USD 1,200 per day
  • Technical contributions
    • Commitment to make a given level of technical contributions to the development of specific aspects of the Papyrus Toolsuite
    • Technical Contributions can take the form of
      • Financial commitment to invest an amount of money in the development of specific technical aspects
        • In this case, the technical development is carried out by an external supplier
      • SW engineers (e.g. developers, architects) dedicated to the development of specific technical aspects
        • Companies providing internal resources to work on development of open source technologies approved by the Steering Committee can get recognized contributions towards Technical Contributions
        • In the calculation of the technical contribution, these resources will be accounted for at the following rate
          • Developer: USD 650 per day
          • Architect or Senior Developer: USD 750 per day
      • Proprietary technology components contributed to the consortium as new open source components
        • In this case, the Steering Committee is responsible for getting an evaluation of the transferred technology
    • In all cases, the contributions need to be approved by the Steering Committee
    • A list of examples of acceptable contributions is provided in section Examples of Acceptable Contributions

Membership Classes

  • User Lead Member

    User Lead members want to influence the development of the Papyrus Toolsuite and be an integral part of the group of organizations that govern the development of the open source MBE solution. They invest an essential amount of resources to sustain the Papyrus IC activities and contribute to the development of the open source technologies.

    Typical User Lead members are organizations that use MBE solutions at the core of their development process and who consider MBE solutions as a strategic asset.

    • Membership fees: Eclipse membership + Polarsys Steering Committee membership
    • Resource allocation: minimum 30 person-days
    • Technical contributions: minimum 100K USD
    • Total contribution: USD 175K to 200K (depending on the membership fees)
  • Supplier Lead Member

    Supplier Lead members want to influence the development of the Papyrus Toolsuite and be an integral part of the group of organizations that govern the development of the open source MBE solution. They invest an essential amount of resources to sustain the Papyrus IC activities and contribute to the development of the open source technologies. The main contributions from Supplier Lead members come in the form of technical contributions to the development of the different open source components.

    Typical Lead Supplier members are organizations that provide commercial offerings (products and/or services) based on the Papyrus Toolsuite and who consider these technologies as strategic to their business.

    • Membership fees: Eclipse membership + Polarsys Participant membership
    • Resource allocation minimum 30 person-days
    • Technical contributions: minimum 100K USD
    • Total contribution: USD 175K to 200K (depending on the membership fees)
  • Participant Member

  • Participant members want to participate in the development of the Papyrus ecosystem. They contribute to the development and adoption of the Papyrus Toolsuite through different types of contributions.

    The Participant Member class includes any organization, user or supplier, small or large, that view the Papyrus Toolsuite as an important part of their corporate and product strategy.

    • Membership fees: Eclipse membership + Polarsys Participant membership
    • Resource allocation: minimum 10 person-days
    • Technical contributions: minimum 10K USD
    • Total contribution: USD 25K to 50K (depending on the membership fees)
  • Research/academia Member

    Research/academia members are universities and research organizations that want to participate in the development of the overall MBE solution based on Papyrus by addressing different research aspects, use Papyrus for teaching/training purposes, and contribute to the overall development of the ecosystem.

    • Membership fees: None Polarsys Guest membership status
    • Resource allocation: 8 person-days
    • Technical contributions: None
    • Note
      • Each research/academia member must be invited/sponsored by a User Lead or Supplier Lead member and approved by the Steering committee
      • Research/academia membership is renewable on an annual basis
  • Observer Member

    Observer members are organizations who have been invited for one year by the Steering Committee of the Papyrus IC to participate to the activities of the consortium.

    Typical Observer members include RD partners, potential future full-fledged members who want to have a closer look before deciding on their strategy, and organizations that canÕt commit the required level of resources but can still contribute to the activities of the Papyrus IC in different ways.

    • Annual fees: None Polarsys Guest membership status
    • Resource allocation: 8 person-days
    • Technical contributions: None
    • Notes
      • An Observer member must be invited/sponsored by a User Lead or Supplier Lead member and approved by the Steering committee
      • Observer status is renewable on an annual basis
      • While they don't have voting rights, Observer members can still collaborate with consortium members on technical developments (e.g. co-funding of development of specific open source components) and research projects, and contribute to the definition of the overall strategy and promotion of the Papyrus Toolsuite

Rights and Benefits for the Different Membership Levels

The table below identifies the rights and benefits of the members regarding the different committees of the Papyrus IC.

  • "X" indicates that every member of that membership class has a seat on the corresponding committee
  • "Elected" indicates that a number of seats on the corresponding committee will be allocated for that membership class based on the following rule
    • At least one seat will be allocated
    • One additional seat will be added for every additional five (5) Lead member seats (the sum of User Lead and Supplier Lead member seats) beyond one (1)
    • Participant member seats are allocated following the Eclipse single transferable vote, as defined in the Eclipse Bylaws.
  • "-" indicates that a member of that membership class has no seat on the corresponding committee

A list of additional member benefits will be defined by the Steering Committee once established.

Papyrus IC membership rights regarding committee participation

User Lead Member Supplier Lead Member Participant Member Research/Academia Member Observer Member
General Assembly X X X X X
Steering Committee X X Elected Elected -
Product Management Committee X X Elected - -
Architecture Committee X X - - -
Research/Academia Committee X X Elected Elected -

Committees

Committee members and chairman will be elected and will serve from April 1 to March 31 of each calendar year, or until their respective successors are elected and qualified, or as otherwise provided for in this charter.

Steering Committee

The consortium is led by the steering committee that is composed of representatives of the different membership classes as defined in Table 1.

  • Composition
    • Chairman: elected representative from the User Lead member companies
    • Participants: see Table 1
  • Responsibilities
    • Define the overall strategic directions of the consortium
    • Define and manage consortium budget
    • Define and maintain technical/product scope, roadmap and development priorities
    • Approve technical contributions of the consortium members

Product Management Committee

The Product Management Committee reports to the Steering Committee

  • Composition
    • Chairman: elected representative from the User Lead member companies
    • Participants: see Table 1
  • Responsibilities
    • Define and maintain technical/product roadmap and development priorities
    • Ensure quality of the different open source components
    • Oversee the definition and delivery of product packages
    • Define and implement product marketing strategy
    • Define and implement the overall strategy for the development of the Papyrus ecosystem

Architectural Committee

The Architectural Committee reports to the Steering Committee

  • Composition
    • Chairman: elected representative from the User Lead member companies
    • Participants: see Table 1
  • Responsibilities
    • Define and maintain the overall product architecture
    • Ensure the consistency and integrity of the architecture and its different components
    • Analyze and provide recommendations on potential tool integrations

Research/Academia Committee

The Research/Academia Committee reports to the Steering Committee

  • Composition
    • Chairman: elected representative from the User Lead member companies
    • Participants: see Table 1
  • Responsibilities
    • Identify key research directions
    • Interact with research groups involved in consortium activities
    • Interact with funding agencies to promote research on Papyrus open source platform
    • Participate to key research events (conferences, workshops, and commercial events) to promote Papyrus as a lead MBE platform for research projects
    • Interaction with universities to help establishing high-quality training and education programs both at the undergraduate and graduate level
    • Gather the training material exploited by the academics, related to the Papyrus Toolsuite
    • Maintain an information set on advanced research, demos, and prototypes around the Papyrus Toolsuite (papers, press, videos, SW, etc.

Examples of Acceptable Contributions

This section provides a list of examples of acceptable contributions towards Papyrus IC membership levels. In all cases, it is important to mention that the Steering Committee is responsible for approving the contributions and that all contributions must be explicitly approved.

  • Monetary contributions
    • Funding of development projects in which they have a particular interest
  • Project contributions
    • Committers working on Eclipse projects>
    • Technical contributions done by non-committers to Eclipse projects
  • Customization and DSML
    • Development of new DSML for Papyrus
  • Integration
    • Investigate the potential integration of Papyrus IC solutions with other tools/solutions used in the industry
    • Develop new integrations for Papyrus IC solutions
  • Testing
    • Testing of the different releases and the registration of new bugs
    • Testing of bug fixes
    • Contributions to the establishment of testing frameworks for the different Eclipse projects, including development of test cases for the different Eclipse projects
  • Product Management
    • Contributions to the creation and evolution of the Papyrus IC roadmap
    • Management of specific development projects
    • Contributions to the development of product requirements and project plan
    • Contributions to the documentation of Papyrus IC solutions
    • Development of open source tutorials for Papyrus IC solutions
    • Creation of marketing materials (logos, icons, datasheets, posters, etc.) for Papyrus IC solutions
  • Support
    • Participation in open forums and mailing lists for Papyrus IC solutions
  • Promotion of the Papyrus IC solutions
    • Participation to industry events (e.g. conferences and workshops) to promote Papyrus IC solutions
    • Presentation of Papyrus IC tutorials/training in public forums
    • Writing white papers, data sheets, and experience reports for Papyrus IC solutions
    • Evangelism and community development activities for the Papyrus IC
  • Research and scientific contributions - the goal to accept items like these would be to involve the scientific community and to encourage transition from science to practical application
    • Research projects on improving Papyrus
    • Research papers on Papyrus and related technologies
    • Case studies on Papyrus and related technologies (lead or participation)
    • Scientific workshops and conferences (Participation, Organization, PC)
  • Participations to industry organizations - Such activities will help to promote the usage of Papyrus as an industrial tool as well as highlight how the tool can and is used in industry, and increase and enhance the visibility of Papyrus amongst potential users, and help promoting the achievements of the user community
    • Collaborative work on Industry specifications and standards that benefit, enhance, and promotes a Papyrus-based Model-Based -System Engineering, -Software Engineering, and/or -Software Development
      • E.g. contribution to OMG (UML, SysML,etc), ISO (standardization of specifications)
    • Participation and contribution to working groups promoting open source modeling, especially Papyrus, and other approaches to MBS
      • E.g. participation/contribution to INCOSE working groups such as model interoperability, SEBOK, and efforts aligned with INCOSE vision for MBSE
    • Participation in industry conferences and workshops to promote and demonstrate usage of Papyrus
      • E.g. INCOSE Symposium, Workshop, and Chapter events; EmbeddedWorld.
    • Collaboration with industries in the creation of papers, case studies, and experience reports where Papyrus solutions are used in an industrial context
  • Contributions to MBE education and training
    • Contributions to the definition or improvement of MBE education and training programs
    • Supervision or co-supervision of undergraduate and graduate students in fields of interest to the Papyrus IC
  • Other activities
    • Other activities/contributions as defined by the Papyrus IC Steering Committee

Back to the top