Enexa
Simulation Overview
  • Input SummaryAll configuration parameters
  • Simulation AlgorithmsReactive vs Smart EMS explained
  • Result OverviewSide-by-side comparison
Configuration
  • Location SetupEquipment specs & constraints
  • FinancialsCosts, income & margins
  • Solar ProductionPV generation profile
  • Charging SessionsEV demand profile
  • Not ModeledKnown gaps & limitations
Reactive BMS
  • BMS AlgorithmHow the reactive BMS works
  • BMS ReactiveRule-based simulation results
SmartEMS
  • SmartEMS AlgorithmHow the 2-layer optimizer works
  • SmartEMS ConfigPlanner tuning parameters
  • SmartEMS ResultsOptimized simulation output
  • SmartEMS DispatchingGate logic & energy flow rules
Solution Overview
  • Solution OverviewArchitecture & responsibilities
  • Comm ArchitectureAPI integration patterns
  • Middleware APITelemetry & command schema
  • Onboarding & ConfigMaster data & config API
  • Exception HandlingFallbacks & failure scenarios
Prototype
  • Site MonitoringReal-time telemetry dashboard
  • Dispatch LogsCommand execution & verification
  • Impact DashboardSavings & value demonstration
  • What-If ScenariosScenario analysis & comparison

Onboarding, Deployment & Configuration

Step-by-step guide for integrating a new site with Enexa. Enexa serves as the master data repository for asset registry and configuration, with Amperio Middleware fetching settings via API.

Enexa as Master Data Repository

Enexa serves as the central source of truth for asset registry and configuration. Amperio Middleware fetches configuration from Enexa API and applies it to site controllers.

1

Registration

Site & API credentials

2

Configuration

Assets & parameters in Enexa

3

Integration

API connectivity testing

4

Go-Live

Production optimization

1
Phase 1: Site Registration
Administrative setup in Enexa portal (Duration: 1-2 days)

Enexa Responsibilities

  • Create Site Record

    Unique site_id, customer association, billing setup

  • Generate API Credentials

    API key, secret, and MQTT certificates (X.509)

  • Configure Sandbox Environment

    Test endpoints, mock data, and logging enabled

  • Deliver Onboarding Package

    Credentials, certificates, and integration guide

Amperio Team Responsibilities

  • Provide Site Information

    Location, grid connection capacity, hardware inventory

  • Hardware Specifications

    Battery model, PV capacity, charger count and types

  • Network Connectivity

    Internet connection type, static IP (if any), firewall rules

  • Technical Contact

    Person responsible for integration and testing

Deliverables from Enexa

credentials.json

API key, secret, site_id, endpoints

certificates.zip

X.509 device cert, private key, CA chain

initial-config.json

Default site configuration for bootstrap

2
Phase 2: Site Configuration
Hardware setup and parameter tuning (Duration: 2-3 days)

Edge Gateway Setup

  1. 1

    Install Gateway Software

    Flash firmware image to edge device (Raspberry Pi, industrial PC, etc.)

  2. 2

    Load Certificates

    Copy X.509 certificates to secure storage on device

  3. 3

    Bootstrap Configuration

    Load initial-config.json, device auto-registers with Enexa

  4. 4

    Fetch Full Configuration

    Device calls Config API to get complete site setup

Hardware Integration

  1. 5

    Connect BMS

    RS485/CAN connection to battery management system

  2. 6

    Connect PV Inverter

    Modbus/SunSpec communication to solar inverter

  3. 7

    Connect EV Chargers

    OCPP 1.6/2.0 connection to charge points

  4. 8

    Connect Grid Meter

    Pulse counter or Modbus energy meter

Configuration via Enexa Portal

Enexa is the master for all site configuration. Amperio Middleware fetches configuration from Enexa's Configuration API and applies it to site controllers.

Battery Settings

Capacity, SOC limits, charge/discharge rates

PV Settings

Peak capacity, orientation, efficiency

Charger Settings

Connector types, power limits, OCPP config

Grid Settings

Import/export limits, tariff zones

3
Phase 3: Integration Testing
Validate all systems in sandbox environment (Duration: 1-2 weeks)

Functional Tests

  • Telemetry data reaches Enexa (all fields populated)
  • Commands are received and executed by middleware
  • Battery charges and discharges on command
  • EV charging starts/stops/throttles correctly
  • PV production data is accurate
  • Grid meter readings match utility meter

Failure Injection Tests

  • Cloud disconnect (60s timeout to autonomous mode)
  • BMS communication failure (safe state)
  • E-stop activation (immediate shutdown)
  • Grid outage detection (island mode or shutdown)
  • Invalid command rejection (safety bounds)
  • Certificate expiry simulation

Acceptance Criteria

  • - All functional tests pass for 48 continuous hours
  • - All failure injection tests demonstrate correct fallback behavior
  • - Telemetry latency p95 < 2 seconds
  • - Command execution latency p95 < 500ms
  • - No data loss during brief (<5 min) connectivity interruptions
4
Phase 4: Production Go-Live
Switch to production and monitored operation (Duration: 48 hours monitored)

Pre-Launch Checklist

  • - Production certificates installed
  • - Production API endpoints configured
  • - Alerting contacts verified
  • - Backup communication path tested
  • - Local autonomous mode validated

Launch Day

  • - Switch sandbox to production config
  • - Enexa support on standby
  • - Real-time monitoring dashboard active
  • - First EV charging session supervised
  • - First battery cycle supervised

Post-Launch (48h)

  • - Monitor all systems continuously
  • - Review optimization performance
  • - Address any edge cases
  • - Sign-off meeting with Amperio Team
  • - Transition to standard support