Solar Management Interface (SMI)

A scalable and extendable web-based solar management platform (SMP) that interfaces with targeted operating data through third-party sensor networks for: Remote Monitoring, Design, Construction, and Operations of Solar Installations.

Challenge

For the SMI to be centered around solar energy, it has some specific implications like: Data-Driven Decision Making by collecting data, and processing this data toward the creation of a design, Maximum Utilization/Minimal Loss by taking into account the variation in the Sun output throughout the day and the year for maximum utilization, and Need-based Design as energy can not be available all the time.

Constraints

When it comes to installing any tech-related product in the desert, there are too many signs that you need to put into consideration. In our case, we wanted to install the SMI on light hardware to be able to attach it to wells where we pump water.

Users

Administrator

Stakeholder

KS O&M

Client (Owner)

Technology

Ubuntu

Python

django

Bootstrap

Introducing The “SMI”

Proprietary software that Interfaces with third-party sensor networks. Scalable to service multiple systems in one site. And flexible to meet client specifications.

Operations Management

Operations Management enables the user – Mainly the operations & support engineer – to manage Operations on site including but not limited to Station monitoring, Substation monitoring, Notifications / Warnings, Meter Readings, and the Last Updated (Notifications).

This can be also viewed within a specific timeframe (Day – Month – Year)

Maintenance & Support Management

Karmsolar has one of the best support systems out there. By having the ability to monitor open/resolved/critical tickets and the accompanying performance loss… It seems like you have full insights on the station’s status.

Faults & Errors Monitoring

The dashboard for Faults & Errors enables users to view the following details on each and every incident:

  1. Incident brief (written by the support engineer)
  2. The component with the error
  3. Number of times it occurred
  4. Status of the incident
  5. Severity level (depends on different factors)
  6. Performance loss accompanied by the fault/error