Meetings Management 2.0: Difference between revisions
mNo edit summary |
|||
(19 intermediate revisions by the same user not shown) | |||
Line 8: | Line 8: | ||
* Replacing the meeting calendar functions currently offered by the DS legacy web application. | * Replacing the meeting calendar functions currently offered by the DS legacy web application. | ||
{| class="wikitable" | |||
| | A detailed list of main features is presented in the table below: | ||
| | {| class="wikitable" style="margin:auto" | ||
| | |style="width: 33%" <td style="vertical-align:middle;text-align:center"|'''Feature''' | ||
|style="width: 34%" <td style="vertical-align:middle;text-align:center"|'''Description''' | |||
|style="width: 33%" <td style="vertical-align:middle;text-align:center"|'''Main Benefits''' | |||
|- | |- | ||
| colspan="1" rowspan="1" |<span style="color: green">'''Next gen, intuitive UI'''</span> | | colspan="1" rowspan="1" |<span style="color: green">'''Next gen, intuitive UI'''</span> | ||
Line 21: | Line 23: | ||
| colspan="1" rowspan="1" |'''Wizard including progression tracker''' | | colspan="1" rowspan="1" |'''Wizard including progression tracker''' | ||
| colspan="1" rowspan="1" |A step-by-step guide (4 steps maximum) allows meeting creators to easily schedule meetings and ensure all required information is compiled in the same place. | | colspan="1" rowspan="1" |A step-by-step guide (4 steps maximum) allows meeting creators to easily schedule meetings and ensure all required information is compiled in the same place. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: SteelBlue">Error reduction</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |'''Summary page''' | | colspan="1" rowspan="1" |'''Summary page''' | ||
| colspan="1" rowspan="1" |The summary page, i.e. the last step of the meeting creation process, provides a comprehensive view of all meeting details before publishing and allows to update/adjust any parameter easily. | | colspan="1" rowspan="1" |The summary page, i.e. the last step of the meeting creation process, provides a comprehensive view of all meeting details before publishing and allows to update/adjust any parameter easily. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: goldenrod">Empowered meeting creator</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |<span style="color: green">'''Cloning meetings'''</span> | | colspan="1" rowspan="1" |<span style="color: green">'''Cloning meetings'''</span> | ||
| colspan="1" rowspan="1" |The clone feature allows to duplicate an existing/previous meeting in one click directly from the meeting list. Only new information (such as date/time) will need to be updated. | | colspan="1" rowspan="1" |The clone feature allows to duplicate an existing/previous meeting in one click directly from the meeting list. Only new information (such as date/time) will need to be updated. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: blue">Time saving</span> | |||
*<span style="color: goldenrod">Empowered meeting creator</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |<span style="color: green">'''Enhanced management of contributions'''</span> | | colspan="1" rowspan="1" |<span style="color: green">'''Enhanced management of contributions'''</span> | ||
| colspan="1" rowspan="1" |Single location to manage ETSI and 3GPP contributions settings: contributions can be defined directly from the meeting creation interface and at meeting creation time with direct links to allocation management and reservation of block of contributions. | | colspan="1" rowspan="1" |Single location to manage ETSI and 3GPP contributions settings: contributions can be defined directly from the meeting creation interface and at meeting creation time with direct links to allocation management and reservation of block of contributions. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: blue">Time saving</span> | |||
*<span style="color: goldenrod">Empowered meeting creator</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |Synchronization meeting types & bodies | | colspan="1" rowspan="1" |'''Synchronization meeting types & bodies''' | ||
| colspan="1" rowspan="1" |Only the relevant meeting types to the concerned bodies are displayed. | | colspan="1" rowspan="1" |Only the relevant meeting types to the concerned bodies are displayed. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: SteelBlue">Error reduction</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |Events and sub-events | | colspan="1" rowspan="1" |'''Events and sub-events''' | ||
| colspan="1" rowspan="1" |Sub-events can be configured under one global event, allowing individual registration for each sub-event. | | colspan="1" rowspan="1" |Sub-events can be configured under one global event, allowing individual registration for each sub-event. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: blue">Time saving</span> | |||
*<span style="color: indigo">Enhanced delegate experience</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |<span style="color: green">'''Possibility for external / non-EoL users to register for certain meeting types'''</span> | | colspan="1" rowspan="1" |<span style="color: green">'''Possibility for external / non-EoL users to register for certain meeting types'''</span> | ||
| colspan="1" rowspan="1" |TB/ISG Open Sessions can be open for self-registration of external / non EoL users. The Open Sessions will be displayed in the same section of the ETSI portal as other concerned TB/ISG meetings. There is no need to use “type = workshop” anymore. | | colspan="1" rowspan="1" |TB/ISG Open Sessions can be open for self-registration of external / non EoL users. The Open Sessions will be displayed in the same section of the ETSI portal as other concerned TB/ISG meetings. There is no need to use “type = workshop” anymore. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> / Empowered meeting creator / Enhanced delegate | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: blue">Time saving</span> | |||
*<span style="color: goldenrod">Empowered meeting creator</span> | |||
*<span style="color: indigo">Enhanced delegate experience</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |Advanced features for meeting administrators | | colspan="1" rowspan="1" |'''Advanced features for meeting administrators''' | ||
| colspan="1" rowspan="1" |With the new version, the meeting creators can now: | | colspan="1" rowspan="1" |With the new version, the meeting creators can now: | ||
Line 53: | Line 74: | ||
* Cancel a meeting after the scheduled date without asking Meeting Support for help (the meeting will appear as “Cancelled” in the ETSI portal) | * Cancel a meeting after the scheduled date without asking Meeting Support for help (the meeting will appear as “Cancelled” in the ETSI portal) | ||
| colspan="1" rowspan="1" | | | colspan="1" rowspan="1" | | ||
<span style="color: blue">Time saving / Empowered meeting | *<span style="color: blue">Time saving</span> | ||
*<span style="color: goldenrod">Empowered meeting creator</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |Independent management of online and F2F | | colspan="1" rowspan="1" |'''Independent management of online and F2F registration''' | ||
| colspan="1" rowspan="1" |For hybrid meetings, different dates can be defined for online and F2F registration. F2F registration can be closed without impacting online registration. | | colspan="1" rowspan="1" |For hybrid meetings, different dates can be defined for online and F2F registration. F2F registration can be closed without impacting online registration. | ||
| colspan="1" rowspan="1" |<span style="color: blue">Time saving / Empowered meeting creator / Enhanced delegate experience</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: blue">Time saving</span> | |||
*<span style="color: goldenrod">Empowered meeting creator</span> | |||
*<span style="color: indigo">Enhanced delegate experience</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |Enhanced room allocation calendar view | | colspan="1" rowspan="1" |'''Enhanced room allocation calendar view''' | ||
| colspan="1" rowspan="1" |Day/Week/Month view of ETSI Premises room allocation provides a clear and comprehensive overview of room usage and availability, including current pre-booked and booked rooms. | | colspan="1" rowspan="1" |Day/Week/Month view of ETSI Premises room allocation provides a clear and comprehensive overview of room usage and availability, including current pre-booked and booked rooms. | ||
| colspan="1" rowspan="1" |<span style="color: blue">Time saving / Empowered meeting creator</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: blue">Time saving</span> | |||
*<span style="color: goldenrod">Empowered meeting creator</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |Enhanced meeting list with advanced search / filter options | | colspan="1" rowspan="1" |'''Enhanced meeting list with advanced search / filter options''' | ||
| colspan="1" rowspan="1" |It is easier to search, sort and filter meetings using the meeting list. | | colspan="1" rowspan="1" |It is easier to search, sort and filter meetings using the meeting list. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: blue">Time saving</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |<span style="color: green">'''Advanced room reservation module for ETSI premises'''</span> | | colspan="1" rowspan="1" |<span style="color: green">'''Advanced room reservation module for ETSI premises'''</span> | ||
| colspan="1" rowspan="1" |This embedded module streamlines and enhances the process of booking meeting rooms in ETSI: | | colspan="1" rowspan="1" |This embedded module streamlines and enhances the process of booking meeting rooms in ETSI: | ||
* by providing smart recommendations based on needs and room availability | * by providing smart recommendations based on needs and room availability | ||
* by offering instant/real-time booking if recommended resources are booked | * by offering instant/real-time booking if recommended resources are booked | ||
* by supporting room pre-booking even if the meeting is saved as a draft | * by supporting room pre-booking even if the meeting is saved as a draft | ||
* by generating an automated ticket to the ETSI Helpdesk when equipment is required | * by generating an automated ticket to the ETSI Helpdesk when equipment is required | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: blue">Time saving</span> | |||
*<span style="color: goldenrod">Empowered meeting creator</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |<span style="color: green">'''Enhanced room allocation management'''</span> | | colspan="1" rowspan="1" |<span style="color: green">'''Enhanced room allocation management'''</span> | ||
| colspan="1" rowspan="1" |The room administrators do not need the DS desktop application anymore to handle room allocation, all actions can be done seamlessly directly from the Meeting Management module. | | colspan="1" rowspan="1" |The room administrators do not need the DS desktop application anymore to handle room allocation, all actions can be done seamlessly directly from the Meeting Management module. | ||
| colspan="1" rowspan="1" |<span style="color: green">Ease of use</span> | | colspan="1" rowspan="1" | | ||
*<span style="color: green">Ease of use</span> | |||
*<span style="color: blue">Time saving</span> | |||
|- | |- | ||
| colspan="1" rowspan="1" |Usability enhancements | | colspan="1" rowspan="1" |'''Usability enhancements''' | ||
| colspan="1" rowspan="1" |The theme used is WCAG 2.1 AA compliant. | | colspan="1" rowspan="1" |The theme used is WCAG 2.1 AA compliant. | ||
| colspan="1" rowspan="1" |Inclusiveness | | colspan="1" rowspan="1" | | ||
*<span style="color: navy">Inclusiveness</span> | |||
|} | |} | ||
| |||
* As the application evolves, please note that the content/videos/screenshots might differ from the current version. We are doing our best to keep this | <span style="color: red">'''Disclaimer'''</span> | ||
* As the application evolves, please note that the content/videos/screenshots presented on this help page might differ from the current version of the application. We are doing our best to keep this page up to date. | |||
* All details displayed on the screenshots/videos are from a testing environment, so please consider them as dummy data. | * All details displayed on the screenshots/videos are from a testing environment, so please consider them as dummy data. | ||
* The menu and options shown could differ depending on user rights. | * The menu and options shown could differ depending on user rights. | ||
== Access rights == | == Access rights == | ||
Line 98: | Line 135: | ||
There are 3 different profiles: | There are 3 different profiles: | ||
* Meeting administrators => ETSI Staff, access is not limited depending on Bodies (with few exceptions); | * '''Meeting administrators''' => ETSI Staff, access is not limited depending on Bodies (with few exceptions); | ||
* Super-users | * '''Super-users''' | ||
** Body Officials (Chair, Vice Chair, Secretary, Acting Chair, Convenor). In case of Joint meeting, only the Body Officials of the "master"/parent Bodies (i.e., the Body to which the meeting was primarily attached at Meeting creation) are part of the Meeting Super-users group. | ** Body Officials (Chair, Vice Chair, Secretary, Acting Chair, Convenor). In case of Joint meeting, only the Body Officials of the "master"/parent Bodies (i.e., the Body to which the meeting was primarily attached at Meeting creation) are part of the Meeting Super-users group. | ||
** Rapporteurs (active work items' rapporteurs are allowed to create and manage specific type of meetings for their specific groups) | ** Rapporteurs (active work items' rapporteurs are allowed to create and manage specific type of meetings for their specific groups) | ||
* Room Administrators => ETSI Staff members who are part of the Events (EVE) meeting support team + ITC team. | * '''Room Administrators''' => ETSI Staff members who are part of the Events (EVE) meeting support team + ITC team. | ||
[[File:MMPv2_Access_Rights.png|center|frame|Fig 1 - Access rights table]] | |||
[[File:MMPv2_Access_Rights.png|center|frame]] | |||
== Meeting category - type matrix == | == Meeting category - type matrix == | ||
Depending on Meeting category and Body (if it is the case) the user has the possibility to decide what type of meeting to create. | Depending on Meeting category and Body (if it is the case) the user has the possibility to decide what type of meeting to create. | ||
[[File:MMPv2 Meeting category - type matrix.png|center|thumb|655x655px]] | [[File:MMPv2 Meeting category - type matrix.png|center|thumb|655x655px|Fig 2 - Meeting category - Meeting type matrix]] | ||
== Meeting statuses == | == Meeting statuses == | ||
[[File:MMPv2 Meeting Statuses .png|center|thumb|655x655px]] | [[File:MMPv2 Meeting Statuses .png|center|thumb|655x655px|Fig 3 - Meeting statuses diagram]] | ||
Line 128: | Line 164: | ||
== Room statuses == | == Room statuses == | ||
[[File:MMPv2 Room Statuses 1.png|center|thumb|655x655px]] | [[File:MMPv2 Room Statuses 1.png|center|thumb|655x655px|Fig 4 - Room statuses diagram]] | ||
''' | '''AVAILABLE =''' a room for which there are no reservations or requests between a specific start/end date/time. | ||
''' | '''PREBOOKED =''' when the user is choosing an available and recommended room and saves the meeting as draft. | ||
''' | '''BOOKED =''' when the user is publishing a meeting for which it selected an available and recommended room. | ||
''' | '''PENDING =''' when the user is choosing an available, but not recommended room, and it press the Publish button. The meeting will not be published until the EVE team will review the room request. If the EVE team approve the room request, the status of the room becomes Booked. In case EVE team denies the room request, the room status becomes Available. | ||
[[File:MMPv2 Room Statuses 2.png|center|frame]] | [[File:MMPv2 Room Statuses 2.png|center|frame|Fig 5 - Meeting support Room request process]] | ||
| | ||
== Room recommendations matrix == | == Room recommendations matrix == | ||
[[File:MMPv2 Room recommendations matrix 1.png|center|thumb|655x655px]] | When the meeting is organized on ETSI Premises, the system is recommending a list of meeting rooms, depending on availability and room capacity. Below is the matrix that indicates which meeting room could be displayed as "Available & Recommended" depending on its capacity (marked in this table with "x" and light blue background) and which meeting rooms will be displayed as "Available" (marked in this table with dark blue background).[[File:MMPv2 Room recommendations matrix 1.png|center|thumb|655x655px|Fig 6 - Room recommendations matrix]]For more details, please see the legend below:[[File:MMPv2 Room recommendations matrix 2.png|center|frame|Fig 7 - legend for Room recommendations matrix]] | ||
[[File:MMPv2 Room recommendations matrix 2.png|center|frame]] | |||
== Create a meeting == | == Create a meeting == | ||
| For starting the creation of a new meeting, there are multiple options: | ||
[[File:MMPv2 Main Menu.png|center|frame]] | |||
| - go to https://portal.etsi.org/meetings-management/#/ | ||
- if you the user is already on the meetings management administration page (https://portal.etsi.org/meetings-management/#/admin/list), by clicking on "Create meeting" button: | |||
[[File:MMPv2 Main Menu.png|center|frame|Fig 8 - Meetings management application main menu]] | |||
- from the ETSI Portal -> Meeting calendar, by clicking on "New meeting" | |||
[[File:MMPv2_Meeting_details_4.png|center|frame]] | |||
After clicking on 'Create meeting' button on the top-left corner, the user is redirected to the 1st step of meeting creation’s form: | After clicking on 'Create meeting' button on the top-left corner, the user is redirected to the 1st step of meeting creation’s form: | ||
Line 166: | Line 207: | ||
* Registration start | * Registration start | ||
All the fields and drop-down options | All the fields and drop-down options not marked with a * are considered optional. | ||
(Some mandatory fields might be prefilled, but the user can still edit them). | (Some mandatory fields might be prefilled, but the user can still edit them). | ||
Line 182: | Line 223: | ||
Hover over your mouse on an input field, little tooltip appears, providing you with essential info or guidance: | Hover over your mouse on an input field, little tooltip appears, providing you with essential info or guidance: | ||
[[File:MMPv2 Meeting details 3.png|center|thumb|655x655px]] | [[File:MMPv2 Meeting details 3.png|center|thumb|655x655px]] | ||
Below is a short demo video covering the 1st step of Meeting creation: | |||
[[File:MMPv2_New_Meeting_Details.webm|center|thumb|640x360px]] | [[File:MMPv2_New_Meeting_Details.webm|center|thumb|640x360px]] | ||
Line 193: | Line 236: | ||
The user needs to fill in all the necessary fields marked * about the desired meeting room: | The user needs to fill in all the necessary fields marked * about the desired meeting room: | ||
* Start & End booking date/time and Room capacity needed are prefilled from the previous step; | * Start & End booking date/time and Room capacity needed are prefilled from the previous step; the user can edit the information upon the needs; | ||
* The user can request here special IT equipment they need for the meeting or any other requirements (like whiteboards, post-its, etc): | * The user can request here special IT equipment they need for the meeting or any other requirements (like whiteboards, post-its, etc): | ||
[[File:MMPv2 Room allocation 2.png|center|thumb|655x655px]] | [[File:MMPv2 Room allocation 2.png|center|thumb|655x655px]] | ||
* There is an option to add more rooms to the meeting – | * There is an option to add more rooms to the meeting – pressing the green plus button below meeting room #N. When pressed, Meeting Room #N appears and "Start & End booking date/time" and "Room capacity needed" are mandatory to fill in. | ||
[[File:MMPv2 Room allocation 4.png|center|thumb|655x655px]] | [[File:MMPv2 Room allocation 4.png|center|thumb|655x655px]] | ||
On the right side of the screen, there is a Room selector that offers the possibility to choose the room for the meeting. The best suitable options will be marked as ‘Available and ‘Recommended’: | On the right side of the screen, there is a Room selector that offers the possibility to choose the room for the meeting. The best suitable options will be marked as ‘Available and ‘Recommended’: | ||
[[File:MMPv2 Room allocation 3.png|center|thumb|496x496px]] | [[File:MMPv2 Room allocation 3.png|center|thumb|496x496px]] | ||
To preview the room, the user must click on the blue text ‘Preview room’ under the room name in the room selector, that will lead them to the pictures of the room: | |||
[[File:MMPv2 Room allocation 5.png|center|thumb|496x496px]] | |||
<gallery widths="300" heights="300"> | |||
File:MMPv2 Room allocation 6.png | |||
File:MMPv2_Room_allocation_7.png | |||
</gallery> | |||
Line 290: | Line 334: | ||
==Email notifications== | ==Email notifications== | ||
{| class="wikitable" style="margin:auto" | |||
|style="width: 33%" <td style="vertical-align:middle;text-align:center"|'''Notification topic''' | |||
|style="width: 34%" <td style="vertical-align:middle;text-align:center"|'''Send''' | |||
|style="width: 33%" <td style="vertical-align:middle;text-align:center"|'''Details''' | |||
|- | |||
|Meeting created (saved as draft) | |||
|TO: meeting creator | |||
|One-time notification about successful meeting saved as draft. It will be send only for the first "Save as draft" action. | |||
|- | |||
|Meeting published | |||
|TO: meeting creator | |||
CC: meetings@etsi.org (if ETSI Premises) | |||
|One-time notification about successful meeting publication | |||
|- | |||
|Answer to your room requested for meeting | |||
|TO: meeting creator | |||
CC: meetings@etsi.org | |||
|When meeting room booking has been approved. | |||
|- | |||
|Change to your room requested for meeting | |||
|TO: meeting creator | |||
CC: meetings@etsi.org | |||
|When meeting room booking has been updated. | |||
|- | |||
|ETSI rooms pre-booking reminder | |||
|TO: meeting creator | |||
CC: meetings@etsi.org | |||
|Several reminders when meeting status = “Draft” and has at least one ETSI room request in status “prebooked”. | |||
|- | |||
|Maximum room capacity reached | |||
|TO: meeting creator | |||
CC: meetings@etsi.org | |||
|When the meeting room allocated to the meeting has almost reached the maximum capacity. | |||
|- | |||
|Meeting updates | |||
|TO: meeting creator | |||
CC: meetings@etsi.org (if ETSI Premises) | |||
|Updates taken into account: start & end dates, time, location, presence type, allocated meeting room. | |||
|- | |||
|Meeting canceled | |||
|TO: meeting creator | |||
CC: meetings@etsi.org (if ETSI Premises) | |||
|When a meeting is canceled. If ETSI Premises any room that was prebooked or booked will be now automatically released. | |||
|} | |||
{| class="wikitable" style="margin:auto" | |||
|style="width: 33%" <td style="vertical-align:middle;text-align:center"|'''Notification topic''' | |||
|style="width: 34%" <td style="vertical-align:middle;text-align:center"|'''Send''' | |||
|style="width: 33%" <td style="vertical-align:middle;text-align:center"|'''Details''' | |||
|- | |||
|Non-recommended room requested for meeting | |||
|TO: meetings@etsi.org | |||
CC: meeting creator | |||
|When the selected room is not marked as “Recommended” and the user clicks "Save as draft" or “Publish meeting”. | |||
|- | |||
|List of local meetings without room request | |||
|TO: meetings@etsi.org | |||
|List of local meetings without room request, with start date less than 1 month. Notification to be sent each Monday. | |||
|- | |||
|Notification to Meeting support for Other requirements | |||
|TO: meetings@etsi.org | |||
CC: meeting creator | |||
|Once the field "Other requirements" from the "Room allocation" screen is filled in and the meeting is published, a notification will be sent to the Meeting support team and cc'd to the meeting creator. | |||
|- | |||
|Meeting update @registered participant | |||
|TO: registered participant | |||
|Updates taken into account: start & end dates, time, location, presence type. | |||
|- | |||
|Meeting canceled @registered participant | |||
|TO: registered participant | |||
|When a meeting is canceled. | |||
|- | |||
|Notification to IT for IT equipment | |||
|TO: helpdesk@etsi.org | |||
CC: meeting creator | |||
|Once the field "IT equipment" from the "Room allocation" screen is filled in and the meeting is published, a notification will be sent to the Helpdesk team and cc'd to the meeting creator. | |||
|} | |||
==Room allocation validation (Meeting Support team)== | ==Room allocation validation (Meeting Support team)== | ||
[[File:MMPv2_New_Room_allocation_validation_Meeting_Support_team.webm|center|thumb|640x360px]] | [[File:MMPv2_New_Room_allocation_validation_Meeting_Support_team.webm|center|thumb|640x360px]] |
Latest revision as of 13:57, 30 October 2024
🚧🚧🚧🚧🚧under construction🚧🚧🚧🚧🚧🚧🚧
Intro
The Meeting Management Project (MMP) focuses on developing an updated web application for managing meetings. The key improvements include:
- Implementing a revamped meeting management web application;
- Upgrading the room booking and pre-booking features;
- Replacing the meeting calendar functions currently offered by the DS legacy web application.
A detailed list of main features is presented in the table below:
Feature | Description | Main Benefits |
Next gen, intuitive UI | The new intuitive, user-centred interface for the meeting management module provides a seamless user experience to schedule meetings and navigate the meeting list and room allocation. |
|
Wizard including progression tracker | A step-by-step guide (4 steps maximum) allows meeting creators to easily schedule meetings and ensure all required information is compiled in the same place. |
|
Summary page | The summary page, i.e. the last step of the meeting creation process, provides a comprehensive view of all meeting details before publishing and allows to update/adjust any parameter easily. |
|
Cloning meetings | The clone feature allows to duplicate an existing/previous meeting in one click directly from the meeting list. Only new information (such as date/time) will need to be updated. |
|
Enhanced management of contributions | Single location to manage ETSI and 3GPP contributions settings: contributions can be defined directly from the meeting creation interface and at meeting creation time with direct links to allocation management and reservation of block of contributions. |
|
Synchronization meeting types & bodies | Only the relevant meeting types to the concerned bodies are displayed. |
|
Events and sub-events | Sub-events can be configured under one global event, allowing individual registration for each sub-event. |
|
Possibility for external / non-EoL users to register for certain meeting types | TB/ISG Open Sessions can be open for self-registration of external / non EoL users. The Open Sessions will be displayed in the same section of the ETSI portal as other concerned TB/ISG meetings. There is no need to use “type = workshop” anymore. |
|
Advanced features for meeting administrators | With the new version, the meeting creators can now:
|
|
Independent management of online and F2F registration | For hybrid meetings, different dates can be defined for online and F2F registration. F2F registration can be closed without impacting online registration. |
|
Enhanced room allocation calendar view | Day/Week/Month view of ETSI Premises room allocation provides a clear and comprehensive overview of room usage and availability, including current pre-booked and booked rooms. |
|
Enhanced meeting list with advanced search / filter options | It is easier to search, sort and filter meetings using the meeting list. |
|
Advanced room reservation module for ETSI premises | This embedded module streamlines and enhances the process of booking meeting rooms in ETSI:
|
|
Enhanced room allocation management | The room administrators do not need the DS desktop application anymore to handle room allocation, all actions can be done seamlessly directly from the Meeting Management module. |
|
Usability enhancements | The theme used is WCAG 2.1 AA compliant. |
|
Disclaimer
- As the application evolves, please note that the content/videos/screenshots presented on this help page might differ from the current version of the application. We are doing our best to keep this page up to date.
- All details displayed on the screenshots/videos are from a testing environment, so please consider them as dummy data.
- The menu and options shown could differ depending on user rights.
Access rights
Meeting management application is accessible using an EOL account.
There are 3 different profiles:
- Meeting administrators => ETSI Staff, access is not limited depending on Bodies (with few exceptions);
- Super-users
- Body Officials (Chair, Vice Chair, Secretary, Acting Chair, Convenor). In case of Joint meeting, only the Body Officials of the "master"/parent Bodies (i.e., the Body to which the meeting was primarily attached at Meeting creation) are part of the Meeting Super-users group.
- Rapporteurs (active work items' rapporteurs are allowed to create and manage specific type of meetings for their specific groups)
- Room Administrators => ETSI Staff members who are part of the Events (EVE) meeting support team + ITC team.
Meeting category - type matrix
Depending on Meeting category and Body (if it is the case) the user has the possibility to decide what type of meeting to create.
Meeting statuses
UNSAVED = this value is displayed in the meeting creation screen, when the user is starting the creation process, but it has not yet saved any information (it has not yet pressed the “save as draft” button). The value indicates to the user that no information is saved yet in the data base, therefore once the user is quitting the page/closing the browser, the information will be lost. The meeting is not yet displayed in the meeting calendar.
DRAFT = this meeting status is indicating that the “save as draft” button has been saved at least once during the creation process. To be sure that the most recent information added has been saved, the user should press the “save as draft” button. The meeting is not yet displayed in the meeting calendar.
PRECONFIRMED = the user has finished the creation and has pressed the “Publish” button, but the meeting cannot be published until the EVE team is approving the room request. The meeting is not yet displayed in the meeting calendar.
CONFIRMED = the user has finished the creation and has pressed the “Publish” button. All conditions are met for the system to automatically confirm the meeting creation (and room allocation if it is the case). The meeting is displayed in the meeting calendar (unless it has been marked as hidden).
FINALIZED = the end date/time of the meeting is in the past. The meeting is displayed in the meeting calendar (unless it has been marked as hidden).
CANCELLED = the meeting has been cancelled after being Confirmed.
Room statuses
AVAILABLE = a room for which there are no reservations or requests between a specific start/end date/time.
PREBOOKED = when the user is choosing an available and recommended room and saves the meeting as draft.
BOOKED = when the user is publishing a meeting for which it selected an available and recommended room.
PENDING = when the user is choosing an available, but not recommended room, and it press the Publish button. The meeting will not be published until the EVE team will review the room request. If the EVE team approve the room request, the status of the room becomes Booked. In case EVE team denies the room request, the room status becomes Available.
Room recommendations matrix
When the meeting is organized on ETSI Premises, the system is recommending a list of meeting rooms, depending on availability and room capacity. Below is the matrix that indicates which meeting room could be displayed as "Available & Recommended" depending on its capacity (marked in this table with "x" and light blue background) and which meeting rooms will be displayed as "Available" (marked in this table with dark blue background).
For more details, please see the legend below:
Create a meeting
For starting the creation of a new meeting, there are multiple options:
- go to https://portal.etsi.org/meetings-management/#/
- if you the user is already on the meetings management administration page (https://portal.etsi.org/meetings-management/#/admin/list), by clicking on "Create meeting" button:
- from the ETSI Portal -> Meeting calendar, by clicking on "New meeting"
After clicking on 'Create meeting' button on the top-left corner, the user is redirected to the 1st step of meeting creation’s form:
Meeting details
On Meeting Details page, the user must fill in the mandatory fields (marked with *):
- Meeting Category
- Meeting type
- Start & End dates
- Presence types allowed
- Generated Meeting reference
- Meeting contacts
- Registration start
All the fields and drop-down options not marked with a * are considered optional.
(Some mandatory fields might be prefilled, but the user can still edit them).
Once all the mandatory fields are filled in (and some optional, depending on the user‘s needs), the user has 2 options to continue at the bottom of the Meeting details screen:
- either click on the ‘Save as draft’ button – this will save your meeting as a draft;
- Or click the button ‘Next step’ to go to the next step
Useful tip:
Hover over your mouse on an input field, little tooltip appears, providing you with essential info or guidance:
Below is a short demo video covering the 1st step of Meeting creation:
Room allocation
‘Room allocation’ is the 2nd step of the meeting creation process. The user can proceed to the room allocation after they complete the ‘Meeting Details’ step:
- If the meeting being created is taking place at ETSI premises, the user will see the following screen :
The user needs to fill in all the necessary fields marked * about the desired meeting room:
- Start & End booking date/time and Room capacity needed are prefilled from the previous step; the user can edit the information upon the needs;
- The user can request here special IT equipment they need for the meeting or any other requirements (like whiteboards, post-its, etc):
- There is an option to add more rooms to the meeting – pressing the green plus button below meeting room #N. When pressed, Meeting Room #N appears and "Start & End booking date/time" and "Room capacity needed" are mandatory to fill in.
On the right side of the screen, there is a Room selector that offers the possibility to choose the room for the meeting. The best suitable options will be marked as ‘Available and ‘Recommended’:
To preview the room, the user must click on the blue text ‘Preview room’ under the room name in the room selector, that will lead them to the pictures of the room:
- File:MMPv2 Room allocation 7.png
The user must select the desired room by clicking on it on the room selector:
- The Room becomes highlighted
- Meeting Room #N label changes from ‘To complete’ to ‘Completed’
The user can proceed to the next step, go back to the previous step or save the meeting as a draft.
- If the meeting being created is NOT taking place at ETSI premises, at the 2nd step ‘Room Allocation’ , the user will see the following message on the screen:
From this screen, the user is able to go back to ‘previous step’, continue with meeting creation choosing ‘next step’ button or opt for ‘save meeting as a draft’.
Payment settings
Contribution settings
- Contributions is the 4th step of meeting creation process.
Once on the Contributions screen, the user may opt for allowing contributions to a meeting simply by switching ‘Switch on if you allow contributions’ on:
- Once the switch is on, the user must fill in the mandatory (marked with *) Contribution allocation fields:
- Contribution reservation start
- Contribution reservation end
- Contribution upload end
- Meeting prefix
- Once all mandatory Contribution settings are defined, the user can continue to the next step, go back to the previous step or save the meeting as a draft. (Some mandatory fields might be prefilled, but the user can still edit them).
Summary
- The last step of meeting creation process is the Display of the meeting's summary:
- All the meeting details (all the field labels and values chosen) are summarized inside a collapsible/expandable section, divided into groups (which correspond to the previous steps:
SCREENSHOT
- A complementary print-to-PDF option “Print to PDF” appears below the meeting details section:
- A “Save as draft” button is shown, at the bottom centre-left, allowing the user to save the changes in the database, but without making the meeting public. The meeting is saved in status "DRAFT".
- At the bottom of the Summary screen, there are several action buttons. The user can go back to the previous step, save the meeting as a draft, publish the meeting or delete the meeting:
Update meeting
Clone meeting
Cancel meeting
Delete meeting
View meeting list
View Room allocation (for all users)
Email notifications
Notification topic | Send | Details |
Meeting created (saved as draft) | TO: meeting creator | One-time notification about successful meeting saved as draft. It will be send only for the first "Save as draft" action. |
Meeting published | TO: meeting creator
CC: meetings@etsi.org (if ETSI Premises) |
One-time notification about successful meeting publication |
Answer to your room requested for meeting | TO: meeting creator
CC: meetings@etsi.org |
When meeting room booking has been approved. |
Change to your room requested for meeting | TO: meeting creator
CC: meetings@etsi.org |
When meeting room booking has been updated. |
ETSI rooms pre-booking reminder | TO: meeting creator
CC: meetings@etsi.org |
Several reminders when meeting status = “Draft” and has at least one ETSI room request in status “prebooked”. |
Maximum room capacity reached | TO: meeting creator
CC: meetings@etsi.org |
When the meeting room allocated to the meeting has almost reached the maximum capacity. |
Meeting updates | TO: meeting creator
CC: meetings@etsi.org (if ETSI Premises) |
Updates taken into account: start & end dates, time, location, presence type, allocated meeting room. |
Meeting canceled | TO: meeting creator
CC: meetings@etsi.org (if ETSI Premises) |
When a meeting is canceled. If ETSI Premises any room that was prebooked or booked will be now automatically released. |
Notification topic | Send | Details |
Non-recommended room requested for meeting | TO: meetings@etsi.org
CC: meeting creator |
When the selected room is not marked as “Recommended” and the user clicks "Save as draft" or “Publish meeting”. |
List of local meetings without room request | TO: meetings@etsi.org | List of local meetings without room request, with start date less than 1 month. Notification to be sent each Monday. |
Notification to Meeting support for Other requirements | TO: meetings@etsi.org
CC: meeting creator |
Once the field "Other requirements" from the "Room allocation" screen is filled in and the meeting is published, a notification will be sent to the Meeting support team and cc'd to the meeting creator. |
Meeting update @registered participant | TO: registered participant | Updates taken into account: start & end dates, time, location, presence type. |
Meeting canceled @registered participant | TO: registered participant | When a meeting is canceled. |
Notification to IT for IT equipment | TO: helpdesk@etsi.org
CC: meeting creator |
Once the field "IT equipment" from the "Room allocation" screen is filled in and the meeting is published, a notification will be sent to the Helpdesk team and cc'd to the meeting creator. |