Versions Compared

Old Version 1

changes.mady.by.user Rushikumar (Rush) Bhatt

Saved on

compared with

New Version 2

changes.mady.by.user Rushikumar (Rush) Bhatt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleWant to get up-to-speed? Expand this section...

Request

(What the customer is looking to accomplish/do?)

  • Facilities would like to notify (initially via email only) a subset (as identified by FO) of the University population regarding COVID-19 positive location(s) as they are identified. Initial meeting was held on  to discuss what ITS has as options — the focal point of discussion being, if Everbridge—which is the University's primary system that is used for all (emergency) notifications.

Initial Light Bulb(s)

  • Rushikumar (Rush) Bhatt  Everbridge sounds like the most logical solution for two main reasons, among others—
    1. We already provide certain areas of the University to execute a non-emergency notification to limited population
    2. We can build rules, within Everbridge Administration UI, to limit the population that will be exposed to given role
      • This COMPLETELY ensures that a notification executed by a specific/setup role will ONLY reach the population that they have access to and not the entire user-base within Everbridge

In other words, say we have total user-base of 50K within Everbridge; the requirement (derived from the rule(s), provided by the customer) calls for access to 150 of those users. The role can be setup as such, that when the notification is triggered by this new role, the most people that the notification would reach is no more than 150


Of course, provided Office of Emergency Management's approval for the usage of the Everbridge system.


Table of Contents
exclude/^.*?\bRequest\b.*?\bInitial Light Bulb(s)\b.*?$/m

(error) Road-blocks

Most, if not all, of the following, by themselves is NOT a road-block... however, taking (or treating) them as a whole, makes it a road-block!

...

ProsCons
  • Setup will be within Everbridge
  • Limited as to how optimally this can be done, due to system limitations (See (error) 3, 4, and 5, above)
  • Still be able to limit the overall number of users exposed 
  • Precise control over the number of users, so long as
    • the Group is built correctly AND
    • when the notification is triggered by the new role, the target population is set correctly
  • No IT involvement, outside of creating the role and assigning an empty group which can be populated by the new role
  • Has a potential of sending a notification to the entire user-base
  • Contacts without UConn Unit can now be added (compared to (lightbulb) 1 above)
  • Each of the 466 contacts will need to be manually added by the designated role admins
  • Can maintain group membership at whim

...