Problem Statement

Notifications is a key feature to our clients and our marketing team, which means we need to develop new and improved notifications.

Scope

Must have:

• Needs to work for existing site controllers

• Notifications via email

Dev Todos & Ideas

• Update sensor only to need the sensor id (remove PLC device ID)

• incoming events are compared against notification rules by the notification-service

• if a unknown sensor is received a new sensor config is created in the cloud and stored in PSQL

• sensor configs can be tied notifications rules - frank pls write better thx

• UX: the user home page should mention if events have been received but dont have a ntfc configured, 98 out of 112 events have notification rules

Where do things happen

User flow and (new???) components

1. Wizard: Get data into cloud (this highly depends on the device)

   1. I have a SC

   2. I dont have an SC but want one

   3. I send data via MQTT

2. X: Configure event rules for my existing sensors

   1. Create trigger

   2. Define severity

   3. Define message

3. X: Configure which sensors should create a notifivation

   1. When to send

   2. Who shall receive it

   3. How to send the notification

Nice to have:

• Add anything you want but don't strictly need

Not in scope:

• Add anything you don't want to include

Events

Where does the event come from

Timeline

Use the roadmap planner (/roadmap) to help your team stay on track. To edit workstreams or dates, select the placeholder below and tap the pencil icon.

Type /trello to add a card or board to this page or /jira to include a Jira issue, chart, or project.

Milestones and deadlines

Plot out milestones and deadlines using the table below. Put each milestone on its own row, @mention milestone owners, and type /date to quickly add deadlines.

Reference materials

Add links to relevant research and any other key documents