Chair's Guide - Revision history

Clarkel: /* General */

2025-11-04T09:38:27Z

General

← Older revision		Revision as of 10:38, 4 November 2025
Line 505:		Line 505:

	The OCG provides an opportunity for Chairs and ETSI representatives to CGs to exchange information and experiences, to discuss any issues prior to formal resolution of substantial objections in the Board and respond to Board requests for information.		The OCG provides an opportunity for Chairs and ETSI representatives to CGs to exchange information and experiences, to discuss any issues prior to formal resolution of substantial objections in the Board and respond to Board requests for information.

			The OCG is consulted before the creation or extension of an ISG or SDG.

	The OCG shall resolve, as far as possible, any duplication of effort or conflict of technical views between the TBs/ISGs to reinforce co-operation between the Technical Organisation, the ISGs and the CGs.		The OCG shall resolve, as far as possible, any duplication of effort or conflict of technical views between the TBs/ISGs to reinforce co-operation between the Technical Organisation, the ISGs and the CGs.
Line 510:		Line 512:
	A Chair will be periodically requested to report to the OCG and the Board on the progress, topics for decision and any issues.		A Chair will be periodically requested to report to the OCG and the Board on the progress, topics for decision and any issues.

	<pre>References: ETSI TWP Clauses 4 & 5		<pre>References: ETSI TWP Clauses 4 & 5, 3.2.1, 3.2.2, 7.2.1, 7.2.2
	</pre>		</pre>

Clarkel at 09:27, 4 November 2025

2025-11-04T09:27:01Z

← Older revision		Revision as of 10:27, 4 November 2025
Line 8:		Line 8:
	The OCG acts as a forum for co-ordination of TCs, ISGs, SDGs, SCs, other Coordination Groups (CGs) and the Secretariat and assists in the resolution in any duplication of effort or conflict of technical views between the Technical Groups.		The OCG acts as a forum for co-ordination of TCs, ISGs, SDGs, SCs, other Coordination Groups (CGs) and the Secretariat and assists in the resolution in any duplication of effort or conflict of technical views between the Technical Groups.

	The scope of this guide does not cover ETSI Partnership Projects (e.g. 3GPP, and oneM2M) or ETSI Projects. It is to be used in conjunction with the [[Delegate's Guide\|ETSI Delegate’s guide]] and the [https://portal.etsi.org/Services/editHelp/How-to-start/User-guides/Rapporteurs-guide ETSI Rapporteur’s guide].		The scope of this guide does not cover ETSI Partnership Projects (e.g. 3GPP and oneM2M) or ETSI Projects. It is to be used in conjunction with the [[Delegate's Guide\|ETSI Delegate’s guide]] and the [https://portal.etsi.org/Services/editHelp/How-to-start/User-guides/Rapporteurs-guide ETSI Rapporteur’s guide].

	= Responsibilities of the Chair =		= Responsibilities of the Chair =

Clarkel: version of the Directives

2025-11-04T09:26:23Z

version of the Directives

← Older revision		Revision as of 10:26, 4 November 2025
Line 4:		Line 4:
	The present document endeavours to provide step-by-step guidance for an ETSI Chair on the essential elements, most common practices and responsibilities of the ETSI Technical Groups: Technical Committee (TC), ETSI Project (EP), ETSI Partnership Project (EPP), Special Committee (SC) or Industry Specification Group (ISG), Software Development Group (SDG) and the Operational Coordination Group (OCG).		The present document endeavours to provide step-by-step guidance for an ETSI Chair on the essential elements, most common practices and responsibilities of the ETSI Technical Groups: Technical Committee (TC), ETSI Project (EP), ETSI Partnership Project (EPP), Special Committee (SC) or Industry Specification Group (ISG), Software Development Group (SDG) and the Operational Coordination Group (OCG).

	It has been formatted to be used as a reference guide according to the ETSI Directives ([https://portal.etsi.org/Resources/ETSI-Directives version 49, June ~~2024~~]). If in any doubt regarding the application of the correct procedures, the ETSI Directives prevail and the ETSI Technical Officer can provide guidance.		It has been formatted to be used as a reference guide according to the ETSI Directives ([https://portal.etsi.org/Resources/ETSI-Directives version 51, June 2025]). If in any doubt regarding the application of the correct procedures, the ETSI Directives prevail and the ETSI Technical Officer can provide guidance.

	The OCG acts as a forum for co-ordination of TCs, ISGs, SDGs, SCs, other Coordination Groups (CGs) and the Secretariat and assists in the resolution in any duplication of effort or conflict of technical views between the Technical Groups.		The OCG acts as a forum for co-ordination of TCs, ISGs, SDGs, SCs, other Coordination Groups (CGs) and the Secretariat and assists in the resolution in any duplication of effort or conflict of technical views between the Technical Groups.

Schmidth: /* ETSI working tools and services */

2025-05-27T08:42:40Z

ETSI working tools and services

← Older revision		Revision as of 09:42, 27 May 2025
Line 686:		Line 686:
	\|-		\|-
	\|Policy Affairs		\|Policy Affairs
	\|		\|Driving policy engagement, regulatory alignment, EU-funded international projects in digital standardisation, global cooperation and partnerships, and strategic outreach with policymakers and other stakeholders for ETSI
	\|Contact: [mailto: Policy@etsi.org policy@etsi.org]		\|Contact: [mailto: Policy@etsi.org policy@etsi.org]
	\|}		\|}

Schmidth: /* ETSI Secretariat Contacts */

2025-05-26T09:55:42Z

ETSI Secretariat Contacts

← Older revision		Revision as of 10:55, 26 May 2025
Line 684:		Line 684:
	\|https://www.etsi.org/about/our-partnerships		\|https://www.etsi.org/about/our-partnerships
	Contact: [mailto:Partnerships@etsi.org partnerships@etsi.org]		Contact: [mailto:Partnerships@etsi.org partnerships@etsi.org]
			\|-
			\|Policy Affairs
			\|
			\|Contact: [mailto: Policy@etsi.org policy@etsi.org]
	\|}		\|}

Clarkel: additional text

2025-04-09T09:16:15Z

additional text

← Older revision		Revision as of 10:16, 9 April 2025
Line 17:		Line 17:
	* Ensure the activities of the Technical Group adhere to the ETSI Directives and its rules, policies and procedures		* Ensure the activities of the Technical Group adhere to the ETSI Directives and its rules, policies and procedures
	* Maintain strict impartiality and act in the interest of ETSI and its members		* Maintain strict impartiality and act in the interest of ETSI and its members
			* Facilitate discussions across different cultures inclusively, so that decisions align with ETSI Values, protection of minority rights, gender neutrality etc
	* Ensure that the ETSI Guidelines for Antitrust Compliance are strictly observed		* Ensure that the ETSI Guidelines for Antitrust Compliance are strictly observed
	* ~~Inform~~ the Technical Group of the Code of Conduct for ETSI Members		* Remind the Technical Group of the Code of Conduct for ETSI Members at the start of each meeting
	* Remind the members of the Technical Group of their statutory obligations to submit IPR disclosures		* Remind the members of the Technical Group of their statutory obligations to submit IPR disclosures
	* Endeavour to reach consensus on all issues, including the approval of draft ETSI deliverables		* Endeavour to reach consensus on all issues, including the approval of draft ETSI deliverables

Clarkel: /* Consensus and consensus-making */

2025-01-23T15:46:18Z

Consensus and consensus-making

← Older revision		Revision as of 16:46, 23 January 2025
Line 329:		Line 329:

	'''If consensus cannot be achieved, the Chair may decide to take a vote which may be performed by a secret ballot either during a meeting or in between meetings.''' Before the vote, the TB/ISG/SDG/SC Chair shall provide a clear definition of the issues (e.g., TB/ISG/SC approval of a draft before publication).		'''If consensus cannot be achieved, the Chair may decide to take a vote which may be performed by a secret ballot either during a meeting or in between meetings.''' Before the vote, the TB/ISG/SDG/SC Chair shall provide a clear definition of the issues (e.g., TB/ISG/SC approval of a draft before publication).

			By definition, in consensus no decision is made against the will of a minority. If significant concerns remain unresolved, a proposal can be stopped or be submitted to a vote. This implies the Technical Group shall work on solutions to address minority concerns.

	Contributions for Decision by Consensus in between meetings shall use the ETSI Remote Consensus tool. Those contributions shall be available at least seven (7) calendar days before the Remote Consensus starts and the minimum duration of the Remote Consensus is at seven (7) days. The Technical Group is to be informed of the results of the Decision within seven (7) calendar days and recorded in the meeting report of the following meeting.<pre>References: ETSI TWPs, 1.7, 3.7.7 and RoP Annex 1.		Contributions for Decision by Consensus in between meetings shall use the ETSI Remote Consensus tool. Those contributions shall be available at least seven (7) calendar days before the Remote Consensus starts and the minimum duration of the Remote Consensus is at seven (7) days. The Technical Group is to be informed of the results of the Decision within seven (7) calendar days and recorded in the meeting report of the following meeting.<pre>References: ETSI TWPs, 1.7, 3.7.7 and RoP Annex 1.

Clarkel: /* General */

2024-12-02T09:05:41Z

General

← Older revision		Revision as of 10:05, 2 December 2024
Line 376:		Line 376:

	The Chair of an ISG shall be a delegate of an ISG Member organisation with the status of Full or Associate member.		The Chair of an ISG shall be a delegate of an ISG Member organisation with the status of Full or Associate member.

			In the event of a change in the supporting organisation of an ISG Chair, the move should be included in the minutes of the next ISG meeting. If no ISG meeting is planned in the immediate future, the ISG is to be informed by email.

	The procedures for the election of an SDG Chair/Vice-Chair/WG Chair described in TWPs, Clauses 7.3.2.1 and 7.3.2.2 shall apply.		The procedures for the election of an SDG Chair/Vice-Chair/WG Chair described in TWPs, Clauses 7.3.2.1 and 7.3.2.2 shall apply.

Clarkel: /* Participation of an ETSI Partner representative in ETSI meetings */

2024-10-04T14:31:12Z

Participation of an ETSI Partner representative in ETSI meetings

← Older revision		Revision as of 15:31, 4 October 2024
Line 457:		Line 457:
	Detailed information on Basic Co-operation Agreement between CEN, CENELEC and ETSI and the description of the 5 modes of cooperation is available in the TWPs, Annex P.		Detailed information on Basic Co-operation Agreement between CEN, CENELEC and ETSI and the description of the 5 modes of cooperation is available in the TWPs, Annex P.

	~~Full~~ overview of the ETSI Partnership Engagements can be found in the TWPs, Annex R.		A full overview of the ETSI Partnership Engagements can be found in the TWPs, Annex R.

	===Liaison Statements when there is no Partnership Agreement===		===Liaison Statements when there is no Partnership Agreement===

Clarkel: /* EC/EFTA cooperation and Chair's responsibilities */

2024-10-04T14:30:04Z

EC/EFTA cooperation and Chair's responsibilities

← Older revision		Revision as of 15:30, 4 October 2024
Line 583:		Line 583:
	The ETSI Director-General (or a nominated substitute) represents ETSI within the relevant committees of the EC and EFTA concerning advisory or regulatory standardisation issues.		The ETSI Director-General (or a nominated substitute) represents ETSI within the relevant committees of the EC and EFTA concerning advisory or regulatory standardisation issues.

	The TB/SC/ISG Chair should be aware of all the relevant communications between ETSI and the EC. The TB/SC/ISG Chair should also consider/verify relevant contributions of the TB/ISG to EC/EFTA Annual Union Work Programme (AUWP), the Rolling Plan for ICT Standardisation (ICT RP) and any other EU policy, when requested by ETSI Secretariat, e.g. twice a year.		The TB/SC/ISG Chair should be aware of all the relevant communications between ETSI and the EC. The TB/SC/ISG Chair should also consider/verify relevant contributions of the TB/ISG to EC/EFTA Annual Union Work Programme (AUWP), the Rolling Plan for ICT Standardisation (ICT RP) and any other EU policy, when requested by ETSI Secretariat, e.g. twice a year.

	The ICT RP ~~Standardisation~~ is a bottom-up approach: the standardisation community (not only ETSI), represented in the Multi-Stakeholder Platform (MSP), provides a programme of standards or other deliverables in support of EU policy objectives. It gives an overview of ongoing standardisation work, e.g. needs and gaps. ETSI as a member of the Multi-Stakeholder Platform (MSP) is included in the MSP consultation.		The ICT RP is a bottom-up approach: the standardisation community (not only ETSI), represented in the Multi-Stakeholder Platform (MSP), provides a programme of standards or other deliverables in support of EU policy objectives. It gives an overview of ongoing standardisation work, e.g. needs and gaps. ETSI as a member of the Multi-Stakeholder Platform (MSP) is included in the MSP consultation.

	Standardisation actions identified in Rolling plan for ICT Standardisation are complementary to other instruments, in particular the Annual Union Work Programme (AUWP).		Standardisation actions identified in Rolling plan for ICT Standardisation are complementary to other instruments, in particular the Annual Union Work Programme (AUWP).

	The AUWP is a top-down approach from the EC and reflects EC expectations, e.g. Standardisation Requests (~~SReq~~). The main goal of contributing to the AUWP is to indicate what needs to be mandated by the EC for ESOs (AUWP targets ESOs only). The AUWP is adopted after having conducted EC consultation with relevant stakeholders: ESOs, Member States and Annex III organisations (see Regulation 1025/2012). In many cases, a pre-condition for a Standardisation Request is an item in the AUWP. On the other hand, the AUWP is not binding for the EC.		The AUWP is a top-down approach from the EC and reflects EC expectations, e.g. Standardisation Requests (SReqs). The main goal of contributing to the AUWP is to indicate what needs to be mandated by the EC for ESOs (AUWP targets ESOs only). The AUWP is adopted after having conducted EC consultation with relevant stakeholders: ESOs, Member States and Annex III organisations (see Regulation 1025/2012). In many cases, a pre-condition for a Standardisation Request is an item in the AUWP. On the other hand, the AUWP is not binding for the EC.

	The ETSI Secretariat coordinates the response to the AUWP, the ~~Rolling Plan for~~ ICT ~~Standardisation~~ and any other EU policy. Information is shared among the ETSI members through the ETSI OCG and relevant ETSI BOARD meetings.		The ETSI Secretariat coordinates the response to the AUWP, the ICT RP and any other EU policy. Information is shared among the ETSI members through the ETSI OCG and relevant ETSI BOARD meetings.

	<pre>References:		<pre>References: