a new software architecture for a distributed, modular and ...create microservices for different...

KIT – The Research University in the Helmholtz Association

KIT - Institute for Applied Computer Science (Prof. Dr. Veit Hagenmeyer)

www.kit.edu

A new software architecture for a distributed, modular and scalable IT infrastructure of future power system control centersEric Braun

Institute for Applied Computer Science2

Outline

MotivationRequirementsConcept

BackendFrontend

PrototypeConclusion

Eric Braun - A new software architecture for a distributed, modular and scalable IT infrastructure of future power system control centers

20.02.2017


Motivation

Energy Lab 2.0 as power system control centerincoming data will be stored, analyzed, and visualizedcontrol electrical equipmentbig variety of applications


20.02.2017

http://tdworld.com/site-files/tdworld.com/files/imagecache/large_img/uploads/2014/08/nyisonewcontrolroom022614-2approved.jpg


Motivation: Role in Energy Lab 2.0

SenSSiC (Smart Energy System Simulation and Control Center)


20.02.2017


Motivation: Role in Energy Lab 2.0

Control, Monitoring and Visualization Center


20.02.2017


Requirements


20.02.2017


Requirements

Data Managementstructured datatime seriesdocuments or fileslinks between data


20.02.2017


Requirements



20.02.2017

{„name“: „IAI Building“,„number“: 449,„address“: ……

}


Requirements



20.02.2017

{„name“: „Janitza UMG 512“,„description“: “Power quality analyser“,

…}


Requirements



20.02.2017

{„name“: „Mesurement“,„identifier“: „MMXU“,„TotW“: …,„Hz“: …,…

}


Requirements



20.02.2017


Requirements

Visualization / Monitoringline / bar chart

maps

3D visualizations

Analysise.g. forecasting (electricity consumption)

Controle.g. electrical equipment


20.02.2017


Requirements

non-functional

high performance

secure system

easy to use applications

(e.g. no programming knowledge needed)


20.02.2017


Concept


20.02.2017


Basic State-of-the-art Concept


20.02.2017

Frontend Applications

Backend Services

Databases


How do we design such an infrastructure?

avoid common mistakes:

monolith

custom solution for every usecase

desktop application as frontend

State-of-the-art technologies

build it for people with little IT knowledge


20.02.2017


Monolith

one hardware serverone technology stackone codebase

easy scaling (replicate whole software)easy development

codebase too bigscalability is not efficientupdates are problematicdeployment to server takes hours or days


20.02.2017

http://odino.org/images/monolith.png


Microservices

small projectslow couplingbetter scalabilitydefined by (HTTP) interface, not by implementationsmall development teams


20.02.2017


Custom Solution for Every Usecase

don‘t …use databases with fix schemas (relational database)

changes to the structure of the data a lot of workcreate microservices for different applications

do …use NoSQL databases

e.g. MongoDB, Elasticsearchcreate microservices based on different features

no timeseries for electr. service BUT a generic timeseries service


20.02.2017


Desktop Application as Frontend

often only run on a specific platform (e.g. windows, linux, android)need installation

web frontend that can run in any modern browser


20.02.2017


Concept: Backend


20.02.2017


Generic Microservice Backend

separate services for different types of data


20.02.2017

Time Series Service

Master Data Service

Digital Asset Service


Generic Microservice Backend

additional services for more demanding applications


20.02.2017

Schema Service

Link Service

Geo Service

Application Configuration Service

Search Service

Auth Service (e.g. OAuth 2)


Architecture


20.02.2017

Gateway

Applications- Energy Management- Demand Site Management- Planning Tools- Asset Management


Concept: Frontend


20.02.2017


Concept: Frontend

configuration over programmingprogramming is done by the developerthe user only configures the rest

all applications in the same design (e.g. Material Design)suitable for desktop, tablet, smartphone, etc.


20.02.2017


Prototypes


20.02.2017


Prototype: Visualization


20.02.2017


Prototype: Analysis


20.02.2017


Prototype: Dashboard


20.02.2017


Summary and Outlook

summary:requirments for the IT infrastructurehow to design the infrastructureconcept of the frontend and backend different prototypes

future tasks:implementation of the whole conceptintegration of various applications for Energy Lab 2.0


20.02.2017


Thank you for your attention!

Mail: [email protected]


20.02.2017


Sources

Icons made by SimpleIcon, Madebyoliver, Freepik from www.flaticon.comhttp://www.janitza.com/files/topics/products/Energie-und-Spannungsqualitaets-Messtechnik/UMG-512/Janitza-Klasse-A-Spannungsqualitaetsanalysator-UMG512.pnghttp://www.novatechweb.com/wp-content/uploads/2013/04/iec.png


20.02.2017


Scalability of Microservices


20.02.2017




20.02.2017

B

1 req. / min1 req. / min

A




20.02.2017

B

1 req. / min1.000.000req. / sec

A




20.02.2017

B

1 req. / min1.000.000req. / sec




20.02.2017

A AA

A A A

B

1 req. / min1.000.000req. / sec

A AA

a new software architecture for a distributed, modular and ...create microservices for different...

Documents