Sweden
Loading...
India
Loading...
Sim-EMS
This webpage contains the documentation of Energy Management System Analysis, Reference and Development Guide.
Implementation Architecture
Implementation Analysis
- Minimum Viable Product Roadmap
- EMS Dashboard Feature List
- Folder Structure
- Dashboard Component Analysis
- Sim-EMS Web Application Architecture`
EMS Explanation
- EMS Explanation
- Self Consumption Explanation
- State Machine Modes Explanation
- State Machine Definition
What is an EMS and Why It Matters
The Big Picture: Energy Management in Modern World
Imagine your home has: - Solar panels on the roof - A big battery in the garage - The normal power grid connection - All your household appliances
Without EMS: These components don't talk to each other. Solar might produce energy that goes to the grid when your battery is empty. Your battery might charge from the grid when solar is available. It's chaos.
With EMS: A smart brain coordinates everything to: 1. Use solar energy first for your home 2. Store excess solar in the battery 3. Only use grid power when needed 4. Sell energy back to grid when profitable
Real-World Analogy: Air Traffic Control
Think of EMS as Air Traffic Control for Energy:
| Airport System | Energy System | What Could Go Wrong |
|---|---|---|
| Planes (energy sources) | Solar, Grid, Battery | Mid-air collisions (overload) |
| Runways (wires/cables) | Electrical circuits | Runway overload (overcurrent) |
| Fuel levels | Battery charge | Plane crashes (battery damage) |
| Weather conditions | Grid stability | Dangerous landings (grid faults) |
| Air Traffic Control | EMS | Prevents disasters |
Without ATC: Planes crash, runways overload, chaos ensues. Without EMS: Batteries explode, inverters burn out, grid destabilizes.
Core Problem EMS Solves
1. The Duck Curve Problem
California's electricity demand on a sunny day:
▲
│ Without EMS:
│ Solar overproduces midday
│ │
Demand │ │
│ │
│──────┼───────► Grid overloads!
│ │ Then needs fossil
│ │ fuels when sun sets
│ ▼
└──────────────► Time
Morning Evening
WITH EMS:
Batteries store excess solar midday
Release energy during evening peak
Smooth the "duck curve"
2. Battery Protection
Batteries are expensive and dangerous if mishandled: - Overcharge → Fire/explosion risk - Over-discharge → Permanent damage ($10,000+ loss) - Wrong temperature → Reduced lifespan - Imbalanced cells → Early failure
EMS is the battery's bodyguard - constantly monitoring and protecting.
How EMS Works: The Complete Flow
Step 1: Data Collection (The "Eyes")
EMS constantly monitors:
• Battery: "I'm at 65% charge, getting warm"
• Solar: "I'm producing 5kW right now"
• Grid: "Electricity costs $0.30/kWh currently"
• House: "We're using 3kW of power"
Think: Like checking your car's dashboard
- Fuel gauge (battery SOC)
- Speedometer (power flow)
- Temperature gauge (battery temp)
- GPS (energy prices)
Step 2: Decision Making (The "Brain")
Based on rules and goals:
IF solar > house_load AND battery < 80%
THEN charge battery with excess solar
IF grid_price > $0.25 AND battery > 50%
THEN discharge battery to avoid buying expensive power
IF battery_temp > 40°C
THEN reduce charge rate by 50%
Think: Like a smart thermostat
- Learns your patterns
- Adjusts based on conditions
- Saves money automatically
Step 3: Control Execution (The "Hands")
Sends commands to devices:
• To inverter: "Output 2kW from battery"
• To solar: "Limit production to 4kW"
• To grid relay: "Disconnect from grid"
Think: Like driving a car
- Accelerator (increase power)
- Brake (decrease power)
- Steering (choose energy source)
Why Each Component in Our Architecture Matters
1. State Machine - The "Consciousness"
Imagine driving a car:
• PARK: Engine off, can't move
• DRIVE: Can accelerate, must follow rules
• REVERSE: Can go backward, slowly
• NEUTRAL: Engine on, but no power to wheels
EMS States:
• BOOT: Starting up, checking systems
• IDLE: Ready but not controlling
• RUNNING: Actively managing energy
• ERROR: Something's wrong, stop everything
• MAINTENANCE: Safe for technician to work
WHY IT MATTERS: Prevents sending "drive" commands when in "park"
2. Data Store - The "Memory"
Imagine a doctor's patient chart:
• Heart rate history
• Medication records
• Test results over time
• Current vitals
EMS Data Store:
• Battery voltage history
• Energy prices today
• Solar production patterns
• Current power flows
WHY IT MATTERS: Makes decisions based on history, not just instant readings
3. Safety Systems - The "Reflexes"
Human reflexes:
• Touch hot stove → Pull hand back (0.1 seconds)
• Bright light → Close eyes instantly
• Lose balance → Arms flail to regain stability
EMS Safety:
• Voltage too high → Stop charging immediately
• Temperature rising → Reduce power automatically
• Grid fault → Disconnect in milliseconds
WHY IT MATTERS: Prevents damage before humans can react
4. Control Modes - The "Personalities"
Different driving modes:
• ECONOMY: Maximize fuel efficiency
• SPORT: Maximize performance
• CRUISE: Maintain set speed
• MANUAL: Full driver control
EMS Control Modes:
• SELF-CONSUMPTION: Use your own solar first
• PEAK SHAVING: Avoid grid usage during peak hours
• CHARGE-ONLY: Fill battery from grid
• BACKUP: Prepare for grid outage
WHY IT MATTERS: Different goals for different situations
Real Example: A Day with EMS
Morning (6:00 AM)
Situation: Family wakes up, grid price = $0.15/kWh
EMS Action:
• Battery at 30% (low)
• Solar not producing yet (dark)
• House needs 2kW for breakfast/morning routine
Decision: Use grid power (cheap), save battery for later
Midday (12:00 PM)
Situation: Sunny, grid price = $0.40/kWh (peak!)
EMS Action:
• Solar producing 8kW
• House using 3kW
• Battery at 40%
Decision:
1. Solar → House (3kW) ✓
2. Excess solar → Battery (5kW) ✓
3. Battery charges to 80%
4. ZERO grid usage (saving money!)
Evening Peak (6:00 PM)
Situation: Sun setting, grid price = $0.45/kWh (very expensive!)
EMS Action:
• Solar producing 1kW (low)
• House needs 5kW (dinner, TV, etc.)
• Battery at 80%
Decision:
1. Solar → House (1kW)
2. Battery → House (4kW)
3. ZERO expensive grid power!
Night (10:00 PM)
Situation: Grid price = $0.10/kWh (cheap!)
EMS Action:
• Battery at 40% (used during peak)
• House needs 1kW (fridge, etc.)
Decision:
1. Grid → Battery (charge at 3kW)
2. Grid → House (1kW)
3. Battery fills overnight with cheap power
Result: Saved $15 today, extended battery life, helped stabilize grid.
The Disaster Without EMS
Scenario: Heat Wave + High Demand
Day: 95°F, everyone running AC
Time: 2:00 PM
WITHOUT EMS:
• Solar panels overheating (reduced output)
• Battery charging at full speed (gets too hot)
• Grid struggling with demand
• House AC cycling on/off (brownouts)
• Battery overheats → Permanent damage → $10,000 loss
WITH EMS:
• Detects high temperature
• Reduces battery charge rate by 50%
• Limits solar production to prevent overheating
• Sheds non-critical loads (pool pump, water heater)
• Battery stays cool, lasts years longer
• Grid gets relief from controlled demand
EMS as a "Money Printer"
Revenue Streams Enabled:
1. **Bill Savings**: Avoid buying expensive grid power
Example: Buy at $0.10, avoid buying at $0.45 = $0.35/kWh savings
2. **Grid Services**: Get paid to help stabilize grid
Example: California pays $100/kW-year for frequency regulation
3. **Solar Maximization**: Use more of your own solar
Example: Without battery, excess solar goes to grid at low price
With EMS, stores excess for later use
4. **Demand Charge Reduction**: Commercial buildings
Example: Reduce peak demand from 500kW to 300kW
Saves $10,000/month in demand charges
Architecture Components = Team Members
Think of EMS architecture as a sports team:
| Position | EMS Component | Role | If Missing |
|---|---|---|---|
| Coach | State Machine | Sets strategy, makes substitutions | Team runs in circles |
| Playbook | Data Store | Knows all plays, opponent history | Forgets what works |
| Defense | Safety Systems | Prevents opponents from scoring | Gets scored on easily |
| Quarterback | Control Logic | Calls plays based on situation | Random plays, no strategy |
| Wide Receivers | Device Interfaces | Catch commands, execute plays | QB throws to nobody |
| Scoreboard | Dashboard | Shows game status, stats | Don't know if winning |
| Team Doctor | Health Monitor | Checks player injuries | Play injured players |
| Stadium Announcer | Logging System | Announces plays, updates | Silent game |
Why Our Specific Architecture Matters
The "Edge-Cloud" Split
WHY SEPARATE?
Edge (Local Controller):
• Milliseconds response (safety!)
• Works without internet
• Handles hardware directly
• Safety-critical functions
Cloud (Remote):
• Complex calculations
• Historical analysis
• Multi-site optimization
• User interfaces
• Can be down without danger
ANALOGY: Aircraft
• On-board computer (edge): Immediate decisions, flight controls
• Air traffic control (cloud): Routing, weather, long-term planning
• Both needed for safe, efficient flight
The Layered Approach
Layer 1: Hardware Interface
• Talks "device language" (Modbus, CAN bus)
• Like speaking Spanish to Spanish devices
Layer 2: Data Normalization
• Converts to common format
• Like translator making everything English
Layer 3: Control Logic
• Makes decisions in common format
• Like manager making decisions in English
Layer 4: User Interface
• Presents information to humans
• Like dashboard showing status in simple terms
WHY LAYERS: Change one layer without breaking others
Example: Swap BMS brand → Only change Layer 1
The Business Impact
For Homeowners:
• 30-50% lower electricity bills
• Backup power during outages (freezer stays cold!)
• Longer battery life (5+ years extra)
• Increased solar self-consumption (70% → 95%)
For Utilities:
• Reduced peak demand (delays billion-dollar upgrades)
• Grid stabilization (fewer blackouts)
• Renewable integration (more solar/wind possible)
• Load balancing (smoother operation)
For Society:
• Reduced fossil fuel use
• More renewable energy integration
• Lower carbon emissions
• More resilient energy infrastructure
The Code We're Writing = Digital Power Plant Operator
Think of our EMS code as hiring a 24/7 power plant operator who:
- Never sleeps (unlike humans)
- Makes decisions in milliseconds (human: seconds)
- Never gets distracted (human: coffee breaks)
- Sees all data simultaneously (human: one screen at a time)
- Follows rules exactly (human: might cut corners)
- Costs pennies per day (human: $100,000/year salary)
Why This Specific Order of Implementation?
Safety First (State Machine)
Would you:
1. Build car engine
2. THEN add brakes
3. THEN add steering
OR:
1. Build frame and safety systems
2. THEN add engine
3. THEN add features
We're doing #2 - safety foundation first
Data Before Decisions
Would you:
1. Make medical diagnosis
2. THEN take patient's temperature
OR:
1. Collect all patient data
2. THEN make diagnosis
We're collecting data (DataStore) before making decisions (Control)
Local Before Cloud
Would you:
1. Connect car to internet
2. THEN make sure it can drive
OR:
1. Make sure car drives safely
2. THEN add GPS/navigation
We're making EMS work locally before adding cloud features
The Big Picture: Energy Transition
We're at a historic moment in energy:
PAST: Centralized power plants → Long transmission → Homes
(One-way flow, dumb consumption)
PRESENT: Solar on rooftops + Batteries in garages
(Two-way flow, needs coordination)
FUTURE: Millions of small energy resources coordinated
Like internet: distributed, resilient, smart
OUR EMS: Enables this future
Summary: Why Every Line of Code Matters
- Safety Code = Prevents fires, explosions, damage
- Control Code = Saves money, optimizes energy
- Monitoring Code = Extends equipment life
- Communication Code = Enables grid services revenue
- UI Code = Makes system usable for people
Every component in our architecture has a critical real-world impact. This isn't just software - it's the nervous system for the clean energy transition.