← All Projects
Project Lead / Architect

E5 Solstice

Comprehensive ERP System

ERPAPI-firstCloud DeploymentProcess AutomationAnalytics

01 — Problem Space

Solar energy companies manage a unique intersection of asset-heavy operations, project-based finance, and regulatory reporting. Off-the-shelf ERPs either force solar workflows into manufacturing templates or require expensive customization that breaks on every update. The need was to conceptualize and design a comprehensive ERP system with modules for finance, operations, and enterprise management — purpose-built to speak solar natively.

Constraints
  • Field teams needed mobile access in areas with intermittent connectivity
  • Financial reporting had to satisfy both internal stakeholders and energy regulatory bodies
  • Asset lifecycles span 20–25 years — the system needed to model long-term degradation and ROI
  • Integration required with existing SCADA systems and IoT sensor networks
The Core Question

How do you build an ERP that models the full lifecycle of a solar asset — from site assessment through 25 years of operation — while remaining accessible to field technicians with a phone and intermittent signal?

02 — System Architecture

API-first design with a clear separation between the data layer, business logic, and presentation. Every feature was built as an API endpoint first, then surfaced through the UI — ensuring mobile, web, and third-party integrations are always first-class citizens.

system_architecture.layers
1
Core Modules

Asset lifecycle management, project tracking, financial reporting, maintenance scheduling — each modeling solar-specific workflows

2
API Gateway

RESTful gateway with versioned endpoints, API key management, and request/response logging for audit compliance

3
Security Layer

Role-based access with field/office/executive permission tiers, plus audit logging on every state mutation

4
Infrastructure

Cloud-hosted with regional failover, offline-capable mobile sync, and CI/CD for zero-downtime releases

Key Architecture Decisions
API-first over UI-first development
Building the API first guaranteed that mobile access, SCADA integration, and future partner integrations would never be afterthoughts. The UI becomes just one consumer of a well-defined contract.
Evaluated technology stack options and deployment models
Compared cloud-native, hybrid, and on-premise deployment strategies against scalability requirements, operational costs, and regulatory constraints before committing to architecture.
Offline-first mobile with sync queue
Field technicians work on rooftops and in rural installations. Requiring constant connectivity would make the app useless where it’s needed most. Offline-first with conflict resolution was non-negotiable.
Incorporated process automation and analytics for decision support
Built analytics capabilities directly into the ERP modules rather than relying on external BI tools, ensuring operational data drives real-time decisions at every level.
Purpose-built asset lifecycle model over generic ERP module
Generic ERPs model assets as depreciating inventory. Solar assets have degradation curves, warranty windows, performance ratios, and regulatory reporting requirements that don’t fit standard templates.

03 — Data Flow

Data originates from IoT sensors and field technician inputs, flows through validation and enrichment layers, and surfaces in financial reports and operational dashboards. The key design challenge was maintaining data integrity across offline/online transitions.

1
Data Capture

IoT sensors report panel performance metrics; field technicians log maintenance activities via mobile app (works offline)

2
Sync & Validation

Mobile app syncs queued operations when connectivity returns; server validates against business rules and resolves conflicts

3
Enrichment

Raw sensor data is processed into performance ratios, degradation trends, and maintenance predictions

4
Business Logic

Enriched data feeds financial projections, warranty tracking, and regulatory compliance calculations

5
Reporting

Aggregated data surfaces in executive dashboards, investor reports, and regulatory filings with full audit trails

04 — Event-Driven Logic

The system monitors asset health and financial triggers continuously, using events to drive proactive maintenance and compliance actions rather than reactive firefighting.

PerformanceRatioDrop
Action: Flag asset for inspection, generate maintenance work order, notify field team lead
Outcome: Degraded panels are caught by data, not discovered during quarterly reviews
WarrantyExpiryApproaching
Action: Generate warranty claim checklist, schedule pre-expiry inspection, alert procurement for replacement budgeting
Outcome: Warranty value is captured systematically instead of expiring unnoticed
RegulatoryDeadlineT-30
Action: Compile required data from all modules, generate draft submission, route for compliance officer review
Outcome: Regulatory filings are prepared proactively with 30 days of review buffer
MaintenanceCompleted
Action: Update asset health score, recalculate performance projections, close work order, log technician hours
Outcome: Single field action cascades correctly through financial, operational, and HR systems

05 — UI/UX Decisions

Two radically different user groups — field technicians on phones in the sun, and executives at desks reviewing financials — required interfaces designed for their context, not a one-size-fits-all dashboard.

Separate mobile-native field app vs. desktop management dashboard
WHYField technicians need large tap targets, offline capability, and camera integration for photo documentation. Forcing them into a responsive version of the executive dashboard would have been hostile to their working conditions.
Visual asset health indicators (green/amber/red) over numeric scores
WHYA performance ratio of 0.82 means nothing to a field tech. A red panel on a site map means ‘go here and fix this.’ The same data, presented differently for different decision-makers.
Pre-filled regulatory report templates
WHYCompliance officers shouldn’t have to hunt for data across modules. The system knows what the regulator needs — it should assemble the report and ask for approval, not ask the human to build it.

Outcomes

  • Live production ERP system purpose-built for solar energy asset management across the full 25-year lifecycle
  • Offline-first mobile app enabling field operations in connectivity-poor environments without data loss
  • API-first architecture ensuring mobile, web, SCADA, and partner integrations are all first-class consumers
  • Event-driven maintenance and compliance workflows replacing reactive quarterly reviews with proactive, data-driven actions