<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Project reports on AereA GmbH - Software that still runs in five years</title>
		<link>https://www-franzi.uat.aerea.de/en/project-reports/</link>
		<description>Recent content in Project reports on AereA GmbH - Software that still runs in five years</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
			<managingEditor>info@aerea.de (AereA GmbH)</managingEditor>
		
		
			<webMaster>info@aerea.de (AereA GmbH)</webMaster>
		
		
		
			<atom:link href="https://www-franzi.uat.aerea.de/en/project-reports/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>EcoPulse - platform for energy monitoring and load control</title>
				<link>https://www-franzi.uat.aerea.de/en/project-reports/ecopulse/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-franzi.uat.aerea.de/en/project-reports/ecopulse/</guid>
				<description>&lt;h2 id=&#34;starting-point&#34;&gt;Starting point&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#starting-point&#34;&#xA;     aria-label=&#34;Direct link to the section Starting point&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Energy and charging infrastructure rarely grows to a plan. It grows in steps: first the photovoltaics, then the storage, later the wallboxes, at some point a second meter for the new part of the building. Every device brings its own interface, every manufacturer its own data model.&lt;/p&gt;&#xA;&lt;p&gt;The result is an operation with plenty of numbers and still no basis for decisions: the inverter knows its generation, the wallbox knows its charge state, the meter knows the grid draw - but nobody knows the whole picture at the same point in time.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Phonalisa - modular IP telecommunications system</title>
				<link>https://www-franzi.uat.aerea.de/en/project-reports/phonalisa/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-franzi.uat.aerea.de/en/project-reports/phonalisa/</guid>
				<description>&lt;h2 id=&#34;starting-point&#34;&gt;Starting point&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#starting-point&#34;&#xA;     aria-label=&#34;Direct link to the section Starting point&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;A telephony system is not a project with an end date. It is a product that grows over years: new endpoint generations, new multi-tenancy requirements, a changing threat situation at the network border. That duration is the actual requirement.&lt;/p&gt;&#xA;&lt;h2 id=&#34;platform-and-core-system&#34;&gt;Platform and core system&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#platform-and-core-system&#34;&#xA;     aria-label=&#34;Direct link to the section Platform and core system&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Modular IP telecommunications system based on &lt;strong&gt;SIP, RTP and XMPP&lt;/strong&gt; with CTI functionality&lt;/li&gt;&#xA;&lt;li&gt;Multi-tenant management of extensions, ring groups, queues and call rules&lt;/li&gt;&#xA;&lt;li&gt;Automated device integration and provisioning of endpoints&lt;/li&gt;&#xA;&lt;li&gt;Client and import functions for migrating existing data&lt;/li&gt;&#xA;&lt;li&gt;Complementary services around directory, presence and call control&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;session-border-controller-and-security&#34;&gt;Session border controller and security&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#session-border-controller-and-security&#34;&#xA;     aria-label=&#34;Direct link to the section Session border controller and security&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;The network border is the most exposed component of a telephony platform. We built our &lt;strong&gt;own SBC&lt;/strong&gt; for it: encryption of signalling and media streams via TLS, SRTP and ZRTP, DDoS protection, rate limiting, hardening of the exposed services and certificate management.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Industrial data platform for plant engineering</title>
				<link>https://www-franzi.uat.aerea.de/en/project-reports/industrial-data-platform/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-franzi.uat.aerea.de/en/project-reports/industrial-data-platform/</guid>
				<description>&lt;h2 id=&#34;starting-point&#34;&gt;Starting point&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#starting-point&#34;&#xA;     aria-label=&#34;Direct link to the section Starting point&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;An internationally active plant manufacturer operates machines at customers worldwide. Their operating data is valuable for service, optimisation and further development - but it has to travel across factory and national boundaries without creating unsecured channels.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-task&#34;&gt;The task&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#the-task&#34;&#xA;     aria-label=&#34;Direct link to the section The task&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;A platform for industrial data exchange that scales with the number of connected installations, separates data classes cleanly and secures communication end to end. Plus documentation that enables the client&amp;rsquo;s own teams to operate and evolve it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Condition monitoring - migration from C&#43;&#43; to .NET Core</title>
				<link>https://www-franzi.uat.aerea.de/en/project-reports/condition-monitoring-migration/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-franzi.uat.aerea.de/en/project-reports/condition-monitoring-migration/</guid>
				<description>&lt;h2 id=&#34;starting-point&#34;&gt;Starting point&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#starting-point&#34;&#xA;     aria-label=&#34;Direct link to the section Starting point&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;The condition monitoring backend had grown over years. Functionally it worked, but every extension cost disproportionate time - mainly because data access was tightly interwoven with the business logic.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-task&#34;&gt;The task&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#the-task&#34;&#xA;     aria-label=&#34;Direct link to the section The task&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Migration to a current stack, without pausing the product and without carrying the structural problems along.&lt;/p&gt;&#xA;&lt;h2 id=&#34;approach&#34;&gt;Approach&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#approach&#34;&#xA;     aria-label=&#34;Direct link to the section Approach&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Instead of a 1:1 port to .NET Core, we &lt;strong&gt;redesigned the data access layer&lt;/strong&gt; and built it on Entity Framework. The migration plan follows functional boundaries: after every step the system runs and can be tested. Operation is containerised via Docker against PostgreSQL.&lt;/p&gt;</description>
			</item>
			<item>
				<title>User interfaces for a medical laser system</title>
				<link>https://www-franzi.uat.aerea.de/en/project-reports/laser-system-medical/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-franzi.uat.aerea.de/en/project-reports/laser-system-medical/</guid>
				<description>&lt;h2 id=&#34;starting-point&#34;&gt;Starting point&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#starting-point&#34;&#xA;     aria-label=&#34;Direct link to the section Starting point&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;A laser system in medical use is planned and controlled through its user interface. That interface is therefore not a frontend but a safety-relevant part of the device.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-task&#34;&gt;The task&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#the-task&#34;&#xA;     aria-label=&#34;Direct link to the section The task&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Development, testing and documentation of the planning and treatment interfaces, plus extension of the associated test tools and implementation of safety-critical updates within the running product lifecycle.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Vehicle bus analysis platform</title>
				<link>https://www-franzi.uat.aerea.de/en/project-reports/vehicle-bus-analysis/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-franzi.uat.aerea.de/en/project-reports/vehicle-bus-analysis/</guid>
				<description>&lt;h2 id=&#34;starting-point&#34;&gt;Starting point&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#starting-point&#34;&#xA;     aria-label=&#34;Direct link to the section Starting point&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Vehicle bus data from CAN, FlexRay and automotive Ethernet accumulates in large volumes during measurement. The central analysis platform for it had grown in C++ over years - functionally extensive, structurally hard to change.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-task&#34;&gt;The task&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#the-task&#34;&#xA;     aria-label=&#34;Direct link to the section The task&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Less additional development capacity than &lt;strong&gt;technical leadership&lt;/strong&gt;: modernise the architecture, evolve how the teams work, and connect both so that it holds after the engagement ends.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Tax software of a state finance authority</title>
				<link>https://www-franzi.uat.aerea.de/en/project-reports/tax-software/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-franzi.uat.aerea.de/en/project-reports/tax-software/</guid>
				<description>&lt;h2 id=&#34;starting-point&#34;&gt;Starting point&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#starting-point&#34;&#xA;     aria-label=&#34;Direct link to the section Starting point&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;A tax administration system does not change because someone had a better idea, but because a law comes into force. The deadlines are set externally and cannot be moved.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-task&#34;&gt;The task&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#the-task&#34;&#xA;     aria-label=&#34;Direct link to the section The task&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Further development and quality assurance over several years, with the requirement of having a reliable regression run for every statutory deadline.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
