Remote Consensus

Getting started - How to access the Remote Consensus tool

NOTE: Only community officials: Chairman, Vice Chairman, Secretary and ETSI Support staff can set up, manage and ratify a Remote Consensus.

    Users must be logged on the portal to use the application

• Open the ETSI portal https://portal.etsi.org and log in with your EOL account

• Once logged on, select the relevant Technical Committee or ISG, e.g. ERM
• Select the tab Remote Consensus

 

By default, Recent, Ongoing or Future Remote Consensus’ are displayed.

• To set up a new Remote Consensus, click on the link Create New
• To search for a closed/previous Remote Consensus, use the dropdown menu and select one of the 3 options.

Scope of the Remote Consensus application

• A Remote Consensus enables a TB/ISG to take decisions on Contributions (Drafts, Liaison Statements, Change Requests, Reports) outside of a face-to-face meeting.

Types of Remote Consensus:

Consensus Measuring for Decisions

Comments Collecting for Discussion

The application allows:

- The collection of comments

- The measurement of consensus by counting the number of oppositions

- The final interpretation of the consensus is the responsibility of the Chairman who ratifies the decision(s) at the end of the Remote Consensus period.

Notifications related to each Remote Consensus are automatically disseminated to the TB/ISG mailing list.

NOTE: To be able to receive Remote Consensus notifications, or to post a Remote Consensus comment (or opposition) members must be subscribed to the TB/ISG membership list. To subscribe: https://portal.etsi.org/webapp/TBMembershiplist

Recommendations for the duration of a Remote Consensus

The ETSI Directives mandate the following:

a clear definition of the proposal(s), and the duration of the time period for submitting comments and/or objections, shall be disseminated by the Chair of the Technical Group to the membership list at least seven (7) calendar days before the opening of the consultation;

The time period for participating in the Remote Consensus shall be at least seven (7) calendar days;

Creating a new Remote Consensus

• Click on the link Create New

A pop-up window will display the fields for completion.

NOTE: Mandatory fields are marked with a red asterisk *.

Community is pre-filled by the system. If applicable, use the drop down menu to select a Working Group.Type Select either Consensus measuring (DECision at the end) or Comments collecting (DIScussion).

Title Write the title (e.g. Approval of NFV003 Final Draft or Approval of Liaison Statement to XXX).

Description is optional and can be used to provide more detail on the remote consensus.

Status is by default set to PLANNED until the launch time.

Start date Select the start date for the Remote Consensus. Start time is always at 12:00 midday CET.

End Date Select the end date for the Remote Consensus when comments or oppositions will no longer be allowed. End Time is always at midnight CET.

NOTE: Start Date shall be greater than or equal to the current date. End Date shall be greater than the Start date.

Freeze contribution submission if appropriate, use this field to prevent Contributions from being added after a specified date.

Status Report Date is optional. Select the day for a weekly status report to be sent to the TB/ISG membership list.

• When all mandatory fields are complete, click on SAVE.

A pop-up window will summarise the Remote Consensus properties and display the Remote Consensus reference.

At the launch of every Remote Consensus a notification is sent to the TB/ISG mailing list.

Adding a Contribution to a Status PLANNED Remote Consensus

For consensus measuring, only Contributions for Decision (DEC) can be submitted.

For comments collecting, only Contributions for Discussion or Information (DIS) can be submitted.

• Click on Add Contributions

• To add a Contribution either:
• Type the sequence number, for example: 000021 and click on the Filter
• OR type a word from the title, for example: Release 2 and click on Filter
• OR click on Filter and the system will display all the Contributions for the year for the selected community.
• Select the Contribution(s) from the Contributions list and click on Add.
• Once all Contributions have been added click on Done.

A popup window will confirm the Contributions in the Remote Consensus.

NOTE: A Contribution added to a Remote Consensus becomes locked, meaning that no further actions are possible on this Contribution until the Remote Consensus has either ended or the Contribution has been removed. The lock is depicted by the hammer icon

Identifying a Contribution under Remote Consensus

Contributions in a Remote Consensus are flagged with a hammer icon.

Status ACTIVE (PLANNED, FROZEN or STARTED)

RATIFIED or REVIEWED

Status ABORTED

Removing a Contribution from a Status PLANNED Remote Consensus

• Find the Contribution for removal and click on the small glasses icon.
• Select the third tab Remote Consensus and click on the link REMOVE.

• Enter the justification and click OK.

The system will refresh the counter of Contributions in this Remote Consensus and update the History of the Contribution.

NOTE: Contributions can only be removed by the TB/ISG Officials, the submitter or ETSI Support staff before the launch of a Remote Consensus. 

Once the Remote Consensus has started, Contributions can only be removed by the TB/ISG Officials or ETSI Support staff. 

The start of a Remote Consensus

A Remote Consensus evolves from Status PLANNED to Status ACTIVE at the launch.

An automated notification is sent to the TB/ISG mailing list including:

- The Contribution name and number

- The duration and the type of Remote Consensus

- Guidelines on how to add a comment, raise an opposition and remove an opposition.

NOTE: An ACTIVE Remote Consensus cannot be modified or stopped.

Submitting a comment to a Contribution in a Remote Consensus

Note that submitting a comment (or raising an opposition) is only accessible to users who 1) are authenticated, and 2) have registered on the "TB Membership list" (see https://portal.etsi.org/webapp/TBMembershiplist))).

The procedure to submit a Comment to a Comments Collection (DIS) and a Consensus Measuring (DEC) Remote Consensus is identical.

• Click on the glasses icon to open the Contribution. A new window will open.
• Click on Comment. By default the comment field is active.Enter text in the Write a Comment field and click Save.

The system will then:

- Create a record of the new comment

- Update the list of comments

- Issue a notification to the TB/ISG mailing list

- Add the submitter to all future notifications on this Contribution.

Raising an opposition to a Contribution

Note that raising an opposition (or submitting a comment) is only accessible to users who 1) are authenticated, and 2) have registered on the "TB Membership list" (see https://portal.etsi.org/webapp/TBMembershiplist))).

• Open the Remote Consensus tab
• Click on the Remote Consensus reference (i.e. ERM(18)DEC606) in Status STARTED. A new window will open.

• Click on Raise an opposition. By default the comment field is active.
• Enter text in the Write a Comment field to justify the opposition and click Save.

The system will then:

Create a record of the new opposition

Update the list of oppositions

Issue a notification to the TB/ISG mailing list

Adds the user to all future notifications on this Contribution

Clearing an opposition to a Contribution

An opposition is displayed in the Remote Consensus tab of the Contribution.

Only the submitter or ETSI Support staff can remove an opposition.

• Click on the hyperlink Clear my opposition and add text if appropriate and then Save.

The system will then:

Create a record of the cleared opposition

Update the list of comments or oppositions

Issue a notification to the TB/ISG mailing list.

Weekly report notification

The system sends a weekly report to the TB/ISG mailing list with a status update including:

- The number of Contributions in the Remote Consensus

- Duration of the review period

- The number of comments, oppositions or cleared oppositions

- Purpose and life-cycle of a Remote Consensus

- A hyperlink to the Remote Consensus report

Example of a report:

Weekly report for NFV(18)DEC094 is sent every Thursday at 4:00am CET.

RC status: STARTED , with 2 available contributions.

0 comments.

RAISING COMMENTS AND OPPOSITIONS is ALLOWED until Wednesday 2018-10-24 at midnight.

NFV(18)000269 (download) Draft - DGS/NFV-EVE011 v0.0.20 (GS NFV-EVE 011 ) "Cloud Native VNF Classification Spec"

Decision Requested : Please approve

0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users

NFV(18)000271 (download) Draft - DGR/NFV-IFA012 v0.13.1 (GR NFV-IFA 012 ) "Os-Ma-Nfvo ref point Spec - svc mgmt & info model"

Decision Requested : Please approve

0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users

Remote Consensus guidelines:

A Remote Consensus (RC) allows approving or just gathering comments either on one single contribution or on a set of contributions grouped together. A single approval period is set for the whole group, and a single report monitors all the results.

During the RC period ETSI members subscribed to the related TB mailing list can add comments and/or raise oppositions on any of the contributions in the RC. Users can also monitor a contribution to receive an email each time a comment is added, or they can wait for the (optional) weekly report email to receive the status and comments on all contributions.

Comments (and oppositions) collected during the RC period can be viewed at any time via the RC Report

At the end of the RC approval period, an official reviews all comments, RATIFIES the result by recording an output status for each contribution.

There are two types of Remote Consensuses:

1- "Consensus measuring" RCs: a DECISION is expected at the end of the approval period, these can only contain contributions for decision

2- "Comment collecting" RCs do not imply a decision at the end of the period, these can only contain contributions for DISCUSSION.

For consensus measuring RCs the application lists the number of sustained oppositions (as defined in ETSI Working Procedures). For comment collecting, comments are allowed but raising oppositions is not possible.

Participants can add comments, raise an oppositions, but also remove their oppositions at any time during the approval period.

When all contributions have been ratified, the Remote Consensus is considered as ratified.

Remote Consensus lifecycle: PLANNED - (FROZEN) - STARTED - TO BE RATIFIED - RATIFIED

Only officials and support staff can create a Remote Consensus for their TB.

      -PLANNED: all delegates can add/remove contributions to/from the RC.

-FROZEN: only officials and support staff can add/remove contributions to the RC.

      -STARTED: delegates can add comments, and raise or remove oppositions on contributions.

      -TO BE RATIFIED: RC period if finished, officials and support staff are expected to ratify results.

      -RATIFIED: all contributions of the RC have been ratified.

More help here

The end of a Remote Consensus

At midnight CET/CEST on the final day of the Remote Consensus:

The system sends a final notification to the TB/ISG mailing list

The status of the Remote Consensus is updated TO BE RATIFIED.

Ratifying a Remote Consensus

The Chairman has the action to ratify the Remote Consensus, taking into account comments and oppositions.

Final output statuses for a Remote Consensus

There are 5 different output statuses for a Contribution in a Remote Consensus

• Click on the Remote Consensus reference in Status TO BE RATIFIED

• Click on  and the Contribution will open on the General tab
• Click on the Remote Consensus tab and a new page will open
• Click on Ratify

If no comments or oppositions have been submitted during the review period the status will by default show as ACCEPTED.

• Enter a ratification comment and select the final status
• Click on Ratify result

A pop message will confirm this action.

NOTE1: When a contribution is - NOTED with revision pre-approved - the next revision of that Contribution will automatically be ACCEPTED as soon as available.

NOTE2:A ratification comment is mandatory for the output status of a REJECTED Contribution.

NOTE3: when ratifying a remote consensus which only aims at "collecting comments" (and not for decision), the only ratification option will be "NOTED" or "NOTED with revision requested".

Once all Contributions have been updated, the portal will show the status RATIFIED and a final notification will be sent to the TB/ISG mailing list.

The Report/Journal of a Remote Consensus

An automated Report/Journal is always available for every Remote Consensus via the Remote Consensus tab and the icon.

2 views are available: Journal or Status Report

Both can be exported to CSV files