Meeting Minutes - 2025-12-04

Date: 2025-12-04
Time: 13:30 CET - 14:00 CET Location: Google Meet Attendees:

• Viktor Semenov
• Tom Grizetti
• Edward Yusko
• Yurii Chabanov
• Mykola Surygin

Agenda

1. Calculations confirmation
2. Libararies update
3. Sprinterra waits for task prioritization
4. Client level documentation
5. Initial assessment briefing

Notes & Discussion

1. Calculations confirmation

• Sprinterra waits on calculations confirmation
• Marco will respond with his judgement ASAP.

2. Libararies update

• Some libraries used in the project are outdated and better be updates for security reasons.

3. No work to be done. Sprinterra waits for task prioritization

• This is why Viktor is onboarded.
• Viktor is Sprinterra’s day-to-day contact.

4. Client level documentation

• Currently docs are on the site level.
• We want to have more generic, client-level document storage where documents are not tied to a specific site.
• Documents should be available only to logged users.
• Files are isolated per client, not global.
• This is not urgent, but required.
• This task is independent of calculations, Marco’s absense is not a blocker.

5. Initial assessment briefing

• Data ingress and portal backend are sharing resources. They need to be split in two to avoid tampering sensors data ingress by user actions or DDOS attack.
• Using time-series database to store sensors data should improve extracting data for dashboard and reporting. Also build-in archiving and averaging is possible for historical data. Azure SQL server may already provide this functionality, need to be researched by DevOps.
• Report generation need to be streamed and not built in-memory. This will significantly reduce load on the infrastrcuture and will allow hosting this service as a function, not a full-time VM. This is less convenient from the developer point of view, but should be tolerated for the sake of report generation simplicity. This approach allows to
• Simplified report in PDF format should be added with only the final data, thus making it easy to open.
• Old sensor data should be archived for cost-effective storage. Again, maybe azure already offers something for this. Otherwise we need to make a plan for this. This is not ugent, but required once dataset grows.
• Frontend need to be served via CDN and cached at the edge, closer to the users. Use brotli compression for static assets, with gzip as fallback. Use http/2 and http/3 with http/1.1 as fallback. This will improve page load time for client.
• Viktor have not found deployment monitoring tool but it is present in functional. Sprinterra also has Disaster Recovery Protocol and Viktor want to take a look at it.

Decisions Made

• Mykola will clarify infra questions with devops
• Viktor will formalize requirements on client-wide document storage
• Client-wide documentation storage should go into implementation

Action Items