This epic will implement SiteVisor backend API:

Issues:

• #9
• #10
• #12
• #8
• #13
• #6
• #5

All objects in the scene such as rooms, sensors, POIs etc need to be stored in a database from where they will be loaded on demand.

Secure the communication to the cluster by encrypting it with TLS.

Implement a basic Websocket server to act as a connector between Kafka Consumer and the app's frontend.

SiteVisor Backend will act as a connector between Kafka and the frontend.

It should consume the data from the Kafka topics and be able to forward the data through websocket connection.

A proof of concept implementation will suffice for now.

Implement SiteVisor Users API.

The idea was to implement a few user roles and give them different permissions:

• Project owner
• Facility manager
• Technician
• Environmental engineer

Implement SiteVisor Projects API.

Add automated tests for the backend.

As multple SiteVisor project will be sharing the same Kafka cluster, there is a need for access management to make sure no data leaks unintentionally.

Implement API to create an alert for a sensor.
The notification could then be displayed on the user dashboard.

Add a relation between Room and Sensor.

Add API for Sensors.

Add Maintenance tasks API.

At minimum, the users should be able to create, view, update, delete tasks.

The user should be able to create/read/update/delete records in the database through an API.

Sensor data should be stored in a database for future analysis and features like graphs etc.

Add API for rooms in the building.