Chief Architect Alexander Alten-Lorenz discusses E.ON's transformation from a utility company to an energy technology company to address challenges and opportunities from decentralization of energy distribution in a digital world. Key aspects of the transformation include using machine learning, AI, cloud services, and IoT to connect energy assets, access real-time data, and remotely control settings. E.ON's new technology platform provides a unified IoT operating system and cloud native architecture using microservices and Kubernetes to deliver business products and services.

1. Alexander Alten-Lorenz: Chief Architect Digital, E.ON
The Future of Energy
Decentral energy distribution in a digital world

2. .. creating entirely new challenges & opportunities.
Energy generation and delivery is transforming ..
Reality

3. A connected energy world will
only be functional if we are able
to access all assets, understand
conditions in real-time and
remotely change settings.
Decentral energy distribution in a digital world

4. First Reaction

5. Aftershock Reaction
Let’s create something new
and transform from a Utility
Company to an Energy
Technology Company

6. Machine Learning and AI
Cloud Services
Internet of Things
P2P / Smart Contracts
Learn from data to better predict
behavior (Power, Weather, Outages,
…)
Give access to data and energy
services (Consumption, production,
flexibility, …)
Connect to Energy assets securely in
real-time (PV, Battery, Car, Boiler,
Grid, …)
Transfer energy related values
between participants (eMobility, …)
E.ONTechnology:ToolingView

7. One Gateway Hardware
platform for all solutions
One IoT Operating
System and Platform
Different products
E.ONTechnology: PlatformView

8. Business
Product A
Business
Product B
Business
Product C
Business
Product D
Device Twin Connectors Models Devices
Cloud native: Microservices, Kubernetes and Kafka / SaaS / PaaS
Unified IoT Operating System
1. Business Applications
2. Platform Services
4. Connectivity
5. Gateway
E.ONTechnology: LogicalView
Cloud MQTT Broker and Routing
3. Platform
OnPrem ETL / Push

9. 1. Container Orchestration: Kubernetes
2. MQTT Broker: GoLang with Apache Kafka and Azure
3. Service-to-Service Communication: gRPC
4. Programming Languages: Go, Kotlin, Java (), JS
5. Infrastructure as Code: Terraform
6. Version Control: Git @ GitLab
7. Continuous Deployment: GitLab Runner
8. Packaging: HELM
9. Monitoring and Logging: StackDriver
E.ONTechnology:Tech Stack

10. E.ONTechnology:What we learned
1. Developers have to be empowered to improve continuously by themselves
2. Start with Infrastructure as Code as soon as possible
3. Don‘t see GDPR as enemy, decouple machine and personal data asap
4. Use the portability of Cloud Native, use the technology which fits most
5. Throwing away can be faster than refactoring
6. Refactoring is not a success key, constant improvement is

11. E.ONTechnology: Development
Join Johannes‘ session “The Monorepo” to see how we
structure our code base and CI/CD pipelines

12. Thank you!
Further information can be
found at www.eon.com
apply:
www.eon.com/jobs