Meeting Minutes — 2026-02-19

Date: 2026-02-19
Time: 13:30 CET Location: Online Meeting

Attendees:

• Viktor Semenov
• Marco Potenza
• Tom Grizetti
• Edward Yusko
• Yurii Chabanov
• Mykola Surygin
• Pavlo Kalinkin
• Norayr Mkrtchyan

Agenda

1. Orders functionality updates
2. Baseline-only report generation status
3. Error notification overload and prioritization
4. Mobile app publication status
5. App walkthrough planning

Notes & Discussion

1. Orders Functionality Updates

Recent Changes:

• Added “Updated Date” field to orders.
• Order list view is now available to:
  • Maxwell (HTMS) admins
  • Resellers
• Previously, only order creation was visible; now full list and details are accessible.

Access & Visibility:

• Resellers see only their own orders.
• Maxwell admins see all reseller orders.

Delivery Packages:

• Orders now support delivery package management.
• From Maxwell side:
  • Add delivery packages
  • Modify packages
  • Delete packages
• Delivery form uses same columns as order table (liters, units, etc.).
• Feature is functional but still under development.
• Notifications in progress:
  • Reseller notified when order is fulfilled.
  • Maxwell admins notified when order is created.
  • All Maxwell admins will receive notifications (no differentiation yet).

2. Baseline-Only Report Generation

• Technically completed.
• Pending final clarification on data handling:
  • For baseline-only reports, use full data range without overlap sanitization.
  • Apply general thresholds from configuration to handle outliers.
• Release planned:
  • Mid next week (worst case: end of next week).

Recent Issue:

• Temporary MyMaxwell outage earlier today.
• Issue investigated and resolved.

3. Error Notifications & Prioritization

Problem Identified:

• Excessive error emails (hundreds).
• All errors marked “critical.”
• Important issues (e.g., panel offline for days) are lost among minor sensor fluctuations.
• Email overload is reducing usefulness of the alert system.

Examples of Issues:

• Sensors going offline/online frequently (minor).
• Complete loss of panel transmission for multiple days (major).
• Major data transmission gaps not being clearly prioritized.

Agreed Improvements:

1. Severity-Based Prioritization

   • Separate minor threshold violations from critical failures.
   • Complete panel communication loss to be highest priority.

2. Time-Based Filtering

   • Short sensor interruptions (minutes) → No alerts.
   • Consider alert only if:
     • Panel offline ≥ 24 hours.
   • 24-hour threshold considered reasonable and actionable.

3. User Segmentation

   • Differentiate between:
     • Maxwell super admins (technical alerts).
     • Resellers/clients (limited relevance).
   • Most internal alerts should be HTMS-facing only.

4. Retest Existing Logic

   • System was designed to send:
     • One notification per site per day.
   • Currently appears to be sending multiple.
   • Development team to re-test and verify grouping logic.

5. Separate Critical Category

   • Complete data transmission failure must:
     • Bypass daily grouping.
     • Be clearly labeled and elevated.
     • Potentially immediate notification.

Next Step:

• Add notification prioritization to upcoming sprint planning (Monday).
• Align with ongoing order notification development.

4. Mobile App Publication

Status:

• App description and privacy policy now provided.
• Next step: publish to App Store (Apple) and Google Play.

Decision Needed:

• Whether to:
  • Use HTMS developer account, or
  • Create a dedicated company developer account.

Notes:

• Apple Developer account costs approx. $100/year.
• Team will confirm whether previous account exists.
• Instructions to be sent to Tom if new account required.

5. App Review & Walkthrough Session

• Dedicated session requested to review app functionality in detail.
• Goal: Full walkthrough of current features (30–60 minutes).
• Screen sharing required during session.

Scheduled:

• Monday
• 12:30 (Tom’s time)
• 1-hour session
• Invite to include Victor, Marco, Edward, and possibly Nick.

Decisions Made

• Baseline-only report will use full data range with standard thresholds.
• Panel offline ≥ 24 hours qualifies as high-priority alert.
• Notification logic to be re-tested and redesigned with severity separation.
• Order and delivery notifications to continue development.
• Schedule dedicated app review session.

Action Items