CDL:Steering Committee Charter

From CDL
Jump to: navigation, search
Community agreement
Status 
Specifies a release status, e.g. of a business rule. The following status levels are defined in the Corporate Data League:
  • IDEA: Informal description of e.g. a business rule that is to be further detailed.
  • DRAFT: Completely defined concept (e.g. business rule) that is not yet released and still under construction.
  • UNDER REVIEW: Completely defined concept (e.g. business rule) which is "freezed" (i.e. not editable, only comments are allowed) and reviewed by a dedicated Business Rules Steward.
  • PLANNED: The concept (e.g. roadmap item) is scheduled to be released at a given date.
  • RELEASED: The concept (e.g. business rule or roadmap item) is used in stable CDL services and apps.
  • DEACTIVATED: The concept (e.g. business rule) is disabled but may be re-activated in the future.
  • ARCHIVED: The concept (e.g. business rule) is disabled because it is no longer relevant from a business perspective. It is only kept for history purposes.
RELEASED
Approver 
A member of the CDL team who approves the formal quality (i.e. not the content) of concepts (e.g. business rules or a procedures) to be released. For example, they check for broken links, content structuring, readability, examples and comprehensiveness, while Stewards are responsible for content quality.
Cdl steering committee
Release date 
Date and time when a concept (e.g. a business rule or a procedure) is released, i.e. when the status changes to RELEASED.
March 9, 2017
Next approval 
Date of next approval of e.g. a managed element or a community agreement.
February 8, 2019
Steward 
A Steward takes care of a particular concept, e.g. a business rule. Stewards are responsible for the content, which does not imply that the assigned Steward is solely responsible for providing feedback or editing the content.
Kai Hüner
Review started date 
Date and time when a review of e.g. a managed element or a comunity agreement started.
not under review

The function of the Steering Committee in the Corporate Data League (CDL) is to take responsibility for the performance of collaboration processes, the quality of shared business partner data and collaboratively managed metadata, and the achievement of commonly agreed roadmap objectives. While it is the accountability of each CDL Member to comply to the common guidelines of the Community Charter, the Steering Committee reviews the overall status of the CDL on a regular basis and decides about measures in case of significant issues. According to Community Charter principles (e.g. anonymity), the Provider (i.e. CDQ AG) monitors collaboration performance and data quality and provides anonymized reports on a regular basis to the Steering Committee.

Members of the Steering Committee and decision making

  1. Each company with a steering membership in the CDL (i.e. a Steering Member) is represented in the Steering Committee by the signer of the steering membership contract between the company and the Provider.
  2. For decisions, the Steering Committee strives for reaching consensus, i.e. a substantial number of Steering Members support the decision and no Steering Member registers a formal objection.
  3. To resolve a dissent, i.e. at least one Steering Member registers a formal objection, a vote may be conducted to take a decision by two-thirds majority.
  4. At a vote, each Steering Member has one vote. The Provider has no vote and cannot break a consensus.
  5. Representatives of Steering Members may delegate their voting right, but only to other employees of their company, not to another company.
  6. Steering Committee Members (or their delegates) have to join a Steering Committee meeting (at least remotely by phone or web meeting) to be considered for decision making.

Acceptance of new and exclusion of existing Steering Committee Members

  1. The Steering Committee can accept the application of a CDL Member to become a Steering Member by consensus. Two-thirds majority by vote is not sufficient.
  2. The Steering Committee can exclude a Steering Member from the Steering Committee by two-thirds majority in a vote.
  3. An application for exclusion must be well-founded and initiated at least 6 months prior to the exclusion vote by at least two Steering Members. Such an exclusion application must be aligned with the Provider and is shared with all CDL Members.
  4. An application for exclusion must be justified by activities or omissions which hinder Steering Committee processes, e.g. repeated prohibition of reaching consensus in the Steering Committee.

Acceptance of new and exclusion of existing CDL Members

  1. The Provider can decide about new CDL Members. It is the responsibility of the Provider to increase the CDL community but also to ensure a certain maturity of business partner data management capabilities of new CDL Members.
  2. The Steering Committee can exclude a CDL Member from the CDL by consensus, two-thirds majority by vote is not sufficient.
  3. An application for exclusion must be well-founded and initiated at least 6 months prior to the exclusion vote by at least two Steering Members. Such an exclusion application must be aligned with the Provider and is shared with all CDL Members.
  4. An application for exclusion must be justified by either continuous low collaboration performance, continuously provision of low data quality, or other activities or omissions which hinder CDL operations.

Revision of community agreements

  1. The Steering Committee is responsible to revise and approve several community agreements (i.e. the Intellectual Property Rights Agreement, Community Charter, and this document) according to the needs of the CDL.
  2. Aside from urgent needs due to not considered aspects, the current status of all community agreements is approved at the first Steering Committee meeting each year. Change requests have to be raised prior to such a meeting in order to enable a through discussion. If not already triggered by a CDL Member, the Provider triggers reviews 2 months before an approval meeting.
  3. A change of a community agreements requires consensus in the Steering Committee and of course must be compliant to relevant laws.

Roadmap planning

  1. The Steering Committee is responsible to define objectives for the annual roadmap of the CDL.
  2. The Steering Committee approves an annual roadmap for the upcoming year at the last Steering Committee meeting of a year by consensus. In case of dissent, voting by two-thirds majority is sufficient.

Direct exploitation of metadata

The Intellectual Property Rights Agreement offers the opportunity for the Provider to exploit CDL metadata (e.g. an up-to-date list of legal forms) directly, e.g. on a data marketplace, if the Steering Committee approves this commercial activity and if the Steering Committee is informed about any revenue from this activity.

  1. If the Provider wants to exploit CDL metadata directly, the Provider has to apply for approval by the Steering Committee for a specific context (e.g. a specific data marketplace, or a specific buyer). The Steering Committee has to approve a direct exploitation of CDL metadata by consensus. In case of dissent, voting by two-thirds majority is sufficient.
  2. The Provider has to inform the Steering Committee about any revenues from direct metadata exploitation and has to make a proposal for how to use these revenues. The Steering Committee has to approve the proposed use. In case of dissent, voting by two-thirds majority is sufficient.

Steering Committee Meetings

  1. The Steering Committee meets three times a year at a face-to-face workshop. If no representative of a Steering Member can join such a meeting in person, joining remotely (by phone or web meeting) is an accepted alternative to discharge the responsibility of a Steering Member, including voting.
  2. At the first Steering Committee meeting of a year, the status of all community agreements is to be approved.
  3. At the last Steering Committee meeting of a year, the roadmap for the next year is discussed and approved.