Remote Consensus: Difference between revisions

From Help
(44 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Scope of the Remote Consensus application ==
== 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.
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: ===
=== Types of Remote Consensus: ===
* '''Consensus Measuring''' for Decisions
'''Consensus Measuring''' for Decisions
* '''Comments Collecting''' for Discussion  The application allows:
 
'''Comments Collecting''' for Discussion   
 
The application allows:
 
- The collection of '''comments'''
 
- The measurement of consensus by counting the number of '''oppositions'''


* The collection of '''comments'''
- 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. 
* 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, members must be subscribed to the TB/ISG membership list. To subscribe: <nowiki>https://portal.etsi.org/webapp/TBMembershiplist</nowiki>
Notifications related to each Remote Consensus are automatically disseminated to the TB/ISG mailing list.


=== '''Recommendations for the duration of a Remote Consensus''' ===
'''NOTE:''' To be able to receive Remote Consensus notifications, members must be subscribed to the TB/ISG membership list.  To subscribe: [https://portal.etsi.org/webapp/TBMembershiplist '''https://portal.etsi.org/webapp/TBMembershiplist''']
* The ETSI Directives do not impose a fixed duration, however the Chairman is advised to maintain a minimum period of 3 days to respect the global membership of ETSI across different time zones.
=== Recommendations for the duration of a Remote Consensus ===
The ETSI Directives do not impose a fixed duration, however the Chairman is advised to maintain a minimum period of 3 days to respect the global membership of ETSI across different time zones.


* Type DEC for Contributions such as a Liaison Statement or a Change Request (CR) – a minimum of 3 days.
Type DEC for Contributions such as a Liaison Statement or a Change Request (CR) – a minimum of 3 days.


* Type DEC for Contributions such as a Final Draft for Approval or a Meeting Report – a minimum of 7 days.
Type DEC for Contributions such as a Final Draft for Approval or a Meeting Report – a minimum of 7 days.
 
Type DIS for Contributions such as CRs – a minimum of 7 days.


* Type DIS for Contributions such as CRs – a minimum of 7 days.
It is recommended to group Contributions into one Remote Consensus.  
It is recommended to group Contributions into one Remote Consensus.  


== Getting started - How to access the Remote Consensus tool ==
== Getting started - How to access the Remote Consensus tool ==


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


'''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 [https://portal.etsi.org/ portal] to use the application'''
 
'''    Users must be logged on the portal to use the application'''
 
* Open the ETSI portal <nowiki>https://portal.etsi.org</nowiki> and '''log in with your EOL account'''
PIC


* Open the ETSI portal [https://portal.etsi.org '''https://portal.etsi.org'''] and '''log in with your EOL account'''
[[File:Picture log1.png|frameless]]
* Once logged on, select the relevant Technical Committee or ISG, e.g. ERM
* Once logged on, select the relevant Technical Committee or ISG, e.g. ERM
* Select the tab '''Remote Consensus'''    
* Select the tab '''Remote Consensus'''  
[[File:Remote con1.png|frameless|542x542px]]   


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


* To set up a new Remote Consensus, click on the link '''Create New'''
* 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.
* To search for a closed/previous Remote Consensus, use the dropdown menu and select one of the 3 options.


== Creating a new Remote Consensus ==
== Creating a new Remote Consensus ==
* Click on the link '''Create New'''
* Click on the link '''Create New'''
[[File:Picture Rem3.png|frameless|631x631px]]


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


'''NOTE:'''  
'''NOTE:''' Mandatory fields are marked with a red asterisk '''*'''.
 
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.
[[File:Picture Rem4.png|frameless|379x379px]]


'''Type''' Select either '''Consensus measuring (DECision at the end)''' or '''Comments collecting (DIScussion).'''  
'''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'').
'''Title''' Write the title (e.g. ''Approval of NFV003 Final Draft'' or ''Approval of Liaison Statement to XXX'').
Line 65: Line 68:
'''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.
'''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:'''  
'''NOTE:''' Start Date shall be greater than or equal to the current date. End Date shall be greater than the Start date.
 
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.
'''Freeze contribution submission''' if appropriate, use this field to prevent Contributions from being added after a specified date.
Line 75: Line 76:


A pop-up window will summarise the Remote Consensus properties and display the Remote Consensus reference.  
A pop-up window will summarise the Remote Consensus properties and display the Remote Consensus reference.  
[[File:Picture Rem5.png|frameless]]


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


* Click on '''Add Contributions'''
* Click on '''Add Contributions'''
[[File:Picture Rem6.png|frameless|376x376px]]
[[File:Picture Rem7.png|frameless|528x528px]]
* To add a Contribution either:
* To add a Contribution either:
* Type the sequence number, for example: '''000021''' and click on the '''Filter'''
* Type the sequence number, for example: '''000021''' and click on the '''Filter'''
Line 94: Line 100:
A popup window will confirm the Contributions in the Remote Consensus.
A popup window will confirm the Contributions in the Remote Consensus.


'''NOTE''':  
'''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 [[File:Hammer arrow icon.PNG|frameless]]
 
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 ===
=== Identifying a Contribution under Remote Consensus ===
Line 104: Line 106:
Contributions in a Remote Consensus are flagged with a hammer icon.  
Contributions in a Remote Consensus are flagged with a hammer icon.  


status ACTIVE (PLANNED, FROZEN or STARTED)  
[[File:Hammer arrow icon.PNG|link=http://help.etsi.org/File:Hammer%20arrow%20icon.PNG|frameless]] Status '''ACTIVE''' ('''PLANNED''', '''FROZEN''' or '''STARTED''')  


RATIFIED or REVIEWED  
[[File:Hammer only icon.PNG|frameless]] '''RATIFIED''' or '''REVIEWED'''


status ABORTED  
[[File:Hammer cross icon.PNG|frameless]] Status '''ABORTED'''


== Removing a Contribution from a Status ''PLANNED'' Remote Consensus ==
== Removing a Contribution from a Status ''PLANNED'' Remote Consensus ==
* Find the Contribution for removal and click on the small glasses icon.
*Find the Contribution for removal and click on the small glasses icon[[File:Glasses_icon.PNG|frameless]].
* Select the third tab '''Remote Consensus''' and click on the link '''REMOVE'''.
* Select the third tab '''Remote Consensus''' and click on the link '''REMOVE'''.
[[File:Picture Rem8.png|frameless|570x570px]]
* Enter the justification and click '''OK'''.
* Enter the justification and click '''OK'''.
[[File:Picture Rem9.png|frameless]]
The system will refresh the counter of Contributions in this Remote Consensus and update the History of the Contribution.
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.   
'''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.   
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 ==
== The start of a Remote Consensus ==
Line 126: Line 131:
An automated notification is sent to the TB/ISG mailing list including:
An automated notification is sent to the TB/ISG mailing list including:


* the Contribution name and number
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:'''
The duration and the type of Remote Consensus


An ACTIVE Remote Consensus cannot be modified or stopped.
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 ==
== Submitting a comment to a Contribution in a Remote Consensus ==
The procedure to submit a Comment to a Comments Collection (DIS) and a Consensus Measuring (DEC) Remote Consensus is identical.
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
[[File:Picture Rem3.png|frameless|568x568px]]
 
* Click on the glasses icon [[File:Glasses icon.PNG|frameless]] 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'''. 
[[File:Picture Rem14.png|frameless|355x355px]]
 
The system will then:
 
Create a record of the new comment


** Click on '''Comment'''.  By default the comment field is active.
Update the list of comments


*** Enter text in the '''Write a Comment''' field and click '''Save'''.  The system will then:
Issue a notification to the TB/ISG mailing list


*** Create a record of the new comment
Add the submitter to all future notifications on this Contribution.
*** Update the list of comments
*** Issue a notification to the TB/ISG mailing list
*** Adds the submitter to all future notifications on this Contribution.


== Raising an opposition to a Contribution ==
== Raising an opposition to a Contribution ==
*** Open the Remote Consensus tab
* 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 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'''. 
[[File:Picture Rem19.png|frameless|347x347px]]
 
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


** Click on '''Raise an opposition'''.  By default the comment field is active.
Adds the user to all future notifications on this Contribution
** 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  ==
== Clearing an opposition to a Contribution  ==
An opposition is displayed in the Remote Consensus tab of the 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'''.
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'''.
[[File:Picture Rem20.png|frameless|331x331px]]


The system will then:
The system will then:


* Create a record of the cleared opposition
Create a record of the cleared opposition
* Update the list of comments or oppositions
 
* Issue a notification to the TB/ISG mailing list
Update the list of comments or oppositions
 
Issue a notification to the TB/ISG mailing list.


== Weekly report notification ==
== Weekly report notification ==
Line 175: Line 194:
The system sends a weekly report to the TB/ISG mailing list with a status update including:
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
The number of Contributions in the Remote Consensus
* Duration of the review period
 
* The number of comments, oppositions or cleared oppositions
Duration of the review period
* Purpose and lifecycle of a Remote Consensus
 
* A hyperlink to the Remote Consensus report
The number of comments, oppositions or cleared oppositions
 
Purpose and life-cycle of a Remote Consensus
 
A hyperlink to the Remote Consensus report  
 
<blockquote>''Weekly report for '''NFV(18)DEC094''' is sent every '''Thursday''' at 4:00am CET.'' </blockquote><blockquote>''RC status: '''STARTED''' , with 2 available contributions.'' </blockquote><blockquote> ''0 comments.''</blockquote><blockquote>''RAISING COMMENTS AND OPPOSITIONS is ALLOWED until Wednesday 2018-10-24 at midnight.''</blockquote><blockquote> '''''NFV(18)000269''' (download) '''Draft - DGS/NFV-EVE011 v0.0.20 (GS NFV-EVE 011 ) "Cloud Native VNF Classification Spec"'''''</blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote><blockquote> '''''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"''''' </blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote><blockquote> </blockquote><blockquote>'''''Remote Consensus guidelines:'''''</blockquote><blockquote> ''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.''</blockquote><blockquote> </blockquote><blockquote> ''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.''</blockquote><blockquote> ''Comments (and oppositions) collected during the RC period can be viewed at any time via the '''RC Report'''''</blockquote><blockquote> </blockquote><blockquote> ''At the end of the RC approval period, an official reviews all comments, RATIFIES the result by recording an output status for each contribution.''</blockquote><blockquote> ''There are two types of Remote Consensuses:''</blockquote><blockquote> ''1- "Consensus measuring" RCs: a DECISION is expected at the end of the approval period, these can only contain contributions for decision'' </blockquote><blockquote> ''2- "Comment collecting" RCs do not imply a decision at the end of the period, these can only contain contributions for DISCUSSION.''</blockquote><blockquote> </blockquote><blockquote> ''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.''</blockquote><blockquote> </blockquote><blockquote> ''Participants can add comments, raise an oppositions, but also remove their oppositions at any time during the approval period.''</blockquote><blockquote> </blockquote><blockquote> ''When all contributions have been ratified, the Remote Consensus is considered as ratified.'' </blockquote><blockquote> </blockquote><blockquote> ''Remote Consensus lifecycle: PLANNED - (FROZEN) - STARTED - TO BE RATIFIED - RATIFIED''</blockquote><blockquote> ''Only officials and support staff can create a Remote Consensus for their TB.''</blockquote><blockquote> ''      -PLANNED: all delegates can add/remove contributions to/from the RC.''</blockquote><blockquote>      ''-FROZEN: only officials and support staff can add/remove contributions to the RC.''</blockquote><blockquote> ''      -STARTED: delegates can add comments, and raise or remove oppositions on contributions.''</blockquote><blockquote> ''      -TO BE RATIFIED: RC period if finished, officials and support staff are expected to ratify results.''</blockquote><blockquote> ''      -RATIFIED: all contributions of the RC have been ratified.'' </blockquote><blockquote> ''More help [[Remote Consensus|here]]'' </blockquote>


== The end of a Remote Consensus ==
== The end of a Remote Consensus ==
Line 185: Line 210:
At midnight CET on the final day of the Remote Consensus:
At midnight CET on the final day of the Remote Consensus:


* The system sends a final notification to the TB/ISG mailing list
The system sends a final notification to the TB/ISG mailing list
* The status of the Remote Consensus is updated '''TO BE RATIFIED.'''
 
The status of the Remote Consensus is updated '''TO BE RATIFIED.'''
 
[[File:Picture Rem22.png|frameless|584x584px]]


== Ratifying a Remote Consensus ==
== Ratifying a Remote Consensus ==
Line 192: Line 220:
The Chairman has the action to ratify the Remote Consensus, taking into account comments and oppositions.
The Chairman has the action to ratify the Remote Consensus, taking into account comments and oppositions.


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


NOTE: A ratification comment is mandatory for the output status of a '''REJECTED''' Contribution.
'''NOTE''': A ratification comment is mandatory for the output status of a '''REJECTED''' Contribution.
 
* Click on the Remote Consensus reference[:File:///C:/Users/Singer/AppData/Local/Microsoft/Windows/Temporary Internet Files/Content.Outlook/7A7V8QPJ/New remote consensus 2018v5.docx# msocom 1 <nowiki>[LC1]</nowiki>]  in Status '''TO BE RATIFIED'''


<span name="_msocom_1"></span>
* Click on the Remote Consensus reference in Status '''TO BE RATIFIED'''


place red circle on the RC reference [:File:///C:/Users/Singer/AppData/Local/Microsoft/Windows/Temporary Internet Files/Content.Outlook/7A7V8QPJ/New remote consensus 2018v5.docx# msoanchor 1 <nowiki>[LC1]</nowiki>]
<span name="_msocom_1"></span>[[File:RC toberatified.png|frameless|905x905px]]  


* Click on  and the Contribution will open on the General tab
* 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 the Remote Consensus tab and a new page will open
* Click on '''Ratify'''
* Click on '''Ratify'''
[[File:Picture Rem26.png|frameless|355x355px]]


If no comments or oppositions have been submitted during the review period the status will by default show as '''ACCEPTED'''.
If no comments or oppositions have been submitted during the review period the status will by default show as '''ACCEPTED'''.
[[File:Picture Rem23.png|frameless|230x230px]]


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


NOTE: Status - '''NOTED with revision pre-approved -''' the next revision of the Contribution will automatically be '''ACCEPTED'''.
'''NOTE:''' Status - '''NOTED with revision pre-approved -''' the next revision of the Contribution will automatically be '''ACCEPTED'''.


A pop message will confirm this action.
A pop message will confirm this action.
[[File:Picture Rem28.png|frameless]]


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.
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.
=== '''Final output statuses for a Remote Consensus (for DIScussion)''' ===
[:File:///C:/Users/Singer/AppData/Local/Microsoft/Windows/Temporary Internet Files/Content.Outlook/7A7V8QPJ/New remote consensus 2018v5.docx# msocom 1 <nowiki>[LC1]</nowiki>] To be done on Thursday if required


== The Report/Journal of a Remote Consensus ==
== The Report/Journal of a Remote Consensus ==
Line 226: Line 253:
An automated Report/Journal is always available for every Remote Consensus via the Remote Consensus tab and the icon.
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
2 views are available: '''Journal''' or '''Status Report'''


Both can be exported to CSV files
[[File:Picture Rem30.png|frameless|619x619px]]


<span name="_msocom_1"></span>
[[File:Picture Rem32.jpg|frameless|630x630px]]


<span name="_msocom_1"></span><span name="_msocom_1"></span>
Both can be exported to CSV files<span name="_msocom_1"></span><span name="_msocom_1"></span><span name="_msocom_1"></span>

Revision as of 14:41, 20 December 2018

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, 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 do not impose a fixed duration, however the Chairman is advised to maintain a minimum period of 3 days to respect the global membership of ETSI across different time zones.

Type DEC for Contributions such as a Liaison Statement or a Change Request (CR) – a minimum of 3 days.

Type DEC for Contributions such as a Final Draft for Approval or a Meeting Report – a minimum of 7 days.

Type DIS for Contributions such as CRs – a minimum of 7 days.

It is recommended to group Contributions into one 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

Picture log1.png

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

Remote con1.png  

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.

Creating a new Remote Consensus

  • Click on the link Create New

Picture Rem3.png

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

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

Picture Rem4.png

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.

Picture Rem5.png

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

Picture Rem6.png

Picture Rem7.png

  • 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 Hammer arrow icon.PNG

Identifying a Contribution under Remote Consensus

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

Hammer arrow icon.PNG Status ACTIVE (PLANNED, FROZEN or STARTED)

Hammer only icon.PNG RATIFIED or REVIEWED

Hammer cross icon.PNG Status ABORTED

Removing a Contribution from a Status PLANNED Remote Consensus

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

Picture Rem8.png

  • Enter the justification and click OK.

Picture Rem9.png

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

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

Picture Rem3.png

  • Click on the glasses icon Glasses icon.PNG 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.

Picture Rem14.png

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

  • 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.

Picture Rem19.png

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.

Picture Rem20.png

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

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 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.

Picture Rem22.png

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

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

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

RC toberatified.png

  • 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

Picture Rem26.png

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

Picture Rem23.png

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

NOTE: Status - NOTED with revision pre-approved - the next revision of the Contribution will automatically be ACCEPTED.

A pop message will confirm this action.

Picture Rem28.png

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

Picture Rem30.png

Picture Rem32.jpg

Both can be exported to CSV files