For installers & O&M teams

Turn site assets (PV / BESS / EV chargers, etc.) into a white-label, operable platform

No vague “dev hours”. We deliver verifiable outcomes: start from integration + unified data definitions, ship monitoring → alarms → reporting first; then extend to operations dashboards, efficiency analytics, and optional control.

Pilot-first
Reconcilable data model
Traceable alarm loop
First release
2–4 weeks
Pilot acceptance
6–12 weeks
Today: multiple platforms/protocols, inconsistent data definitionsNow
Delivered: unified view + traceable alarms + white-label weekly/monthly reportsAfter

3 visible outcomes in the pilot

Start with your existing MQTT/gateway data: normalized points → data dashboards → alarm workflow → monthly reports. After acceptance, scale to more sites and systems.

Campus microgrid (PV / BESS / EV, etc.)

Many subsystems and inconsistent semantics? Unify integration + definitions first, then deliver a complete O&M loop: monitoring → alarms → reporting.

  • Multi-protocol integration (MQTT / Modbus / API, etc.)
  • Data quality dashboards (missing / latency / anomalies)
  • Unified energy + asset semantics

Distributed PV O&M

Vendor apps are fragmented and reports don’t reconcile. Normalize multi-brand inverter/meter data and ship white-label weekly/monthly reports.

  • Multi-brand normalization
  • Site overview / trends / export
  • White-label report templates (PDF/Excel)

EV charging sites O&M

Operate with traceability: status, error-code normalization, alarm grading, handling records, and optional ticketing/reporting.

  • OCPP / API integration (as needed)
  • Error normalization + noise reduction
  • Weekly/monthly operations reports (utilization / offline / faults)

Deliverables

Clear scope. Verifiable acceptance.

The pilot scope & acceptance document becomes the baseline for delivery, acceptance, and change control: defined scope, unified semantics, complete evidence chain.

Change control
New device types / new definitions / monitoring-to-control expansions go through change review and are recorded in the checklist (scale after pilot acceptance).
Pilot scope & acceptance
Define what’s included/excluded and how to accept: scope, milestones, checklist, risks, and Not Included — prevent scope creep.PDF
Data contract (you own it)
Point list, units/scaling, enum dictionaries, validation rules, mapping strategy and sample payloads — scale without rework.Excel / JSON
Monitoring + alarm workflow
Unified monitoring, alarm engine (grading/noise reduction), handling records and evidence chain; reconcilable weekly/monthly reports.Web / API
White-label UI
Multi-site overview, asset view, alarm center, report center, admin configuration. Swap logo/name/theme to ship as your product.Web UI
Deployment kit (on-prem ready)
Private deployment to LAN/VPC: Docker Compose, init scripts, Nginx config, env templates and runbook; optional offline mode for site delivery.Docker / Shell / YAML
Docs & handover
Architecture, API docs, deployment/ops manual, handover checklist, acceptance records — no black box, your team can take over.PDF / MD
Extension principles
Add devices/definitions/control via change assessment and recorded acceptance items (scope/impact/checklist).Process

6–12 week pilot process

Scope locked · Milestones · Checklist acceptance

1

Kickoff & scope

Week 1: confirm scope, data sources (MQTT/gateway), point definitions, acceptance criteria and timeline.

2

Integration & normalization

Weeks 2–4: connect the pipeline, deliver mapping scripts and data quality metrics (missing/latency/anomalies).

3

Dashboards + alarm loop

Weeks 4–8: ship data dashboards, alarm rules and workflow (ack/handle/close) to form an evidence chain.

4

Monthly report & acceptance

Weeks 8–12: deliver a monthly report (PDF), pilot conclusion, and a scale-up plan.

Cases & delivery examples (anonymized)

Examples of how we deliver unified data definitions, a traceable alarm loop, and periodic reporting with checklist acceptance.

Case (anonymized) · Distributed PV O&M

Multi-site PV: generation/export monitoring with reconcilable definitions

Focus: monitor PV generation and export data with consistent, reconcilable definitions. First normalize point list/units/scaling/timing, then ship overview, trends, alarms and reporting.

100+ sites400+ devicesreconcilable reportingnormalized semanticsO&M loop
Sites
100+ sites
Devices
400+ devices
Loop
monitoring → alarms → reporting
Value
consistent, traceable reporting
Case (anonymized) · Campus energy

Campus energy: unified O&M for PV / BESS / EV / distribution / heat pumps

Challenge: unified asset view, consistent definitions, traceable alarms. Pilot first with scope and acceptance, then scale to dashboards, analytics and optional control.

~130 sitesmulti-systemalarm gradingdata qualityon-prem ready
Sites
~130 sites
Assets
PV / BESS / EV / distribution / HP
Focus
unified view + semantics
Deployment
LAN / on-prem
Case (anonymized) · Commercial site

Commercial site: PV+BESS+EV platform for owner-side operations

Designed for daily operations: readable, usable, traceable. Unified energy/asset view, monitoring, alarm workflow and periodic reporting.

owner opsPV+BESS+EValarm loopperiodic reportingwhite-label
User
owner-side ops
Assets
PV / BESS / EV
Loop
monitoring + alarms + reporting
Form
white-label platform

Ready to start a 6–12 week pilot?

Submit the pilot form for speed and clarity, or email us directly. We reply within 24 business hours.

Email us
enmage@enmage.com