gridX GmbH - Experts & Thought Leaders

As gridX Product Manager of Asset Integration Daniel Gomes Makohin says: “In the field, energy assets are the hands and eyes of XENON – and integration is the circulatory system making them work.” As the energy space becomes more and more decentralized, gridX is continually extending the compatibility of its platform. They do this by integrating additional distributed energy resources (DERs) to help their partners scale, focusing on the most future-proof original equipment manufacturers (OEMs), and the most relevant models within their portfolio. For this to happen, different assets and OEMs must be ‘integrated’ with their XENON platform. Synergies for multiple partners There are two ways to get the integration ball rolling. The first is when partners approach them with a request for a particular OEM with selected models. The second is when they find an OEM or asset that they determine to have great potential in the market or will bring synergies for multiple partners. Once one of these options is set in motion, the integration process gets under way. Integrating towards singularity Step 1: Evaluation Step 1.1: Is it a priority? When first faced with a new OEM or asset, their integration team asks themselves a series of questions to determine whether the integration makes sense on a business level – both financial and operational – for themselves and their customers. Typical questions are: What is the potential impact of this new asset in terms of revenue for both ourselves and our partners? What timeline do our partners expect for the rollout? What are the technical expectations? What’s the reputation of the product? Does the asset align to our energy management system’s (EMS’s) overall strategy? Step 1.2: Can we integrate it? After our team has assessed whether we want to integrate an asset, the next step is: can we? Information and technical documentation Then, depending on the device type, they require additional data points to be able to manage it The answer to this question comes down to data. They start with a general evaluation of all assets from the OEM to get an overview if all of the information and technical documentation they require is available. If it is, their team members then determine the technical feasibility of the integration based on these data points.  It’s important to note that these points include general measurements, as well as measurements that differ according to device type. For example, they require the following of all devices: A unique identifier Power measurements Voltage Current Apparent power Then, depending on the device type, they require additional data points to be able to manage it, rather than simply monitoring it. For this example, they’ll focus only on EV charging stations (EVCS) and battery inverters. EVCS Plug state Charging station state, e.g. ready, authorized, charging error Max. charge/discharge power Battery State of charge Minimum charge power Maximum charge power Capacity State of health Once these assessments are made, there is a further evaluation into the outlook of the OEM’s cooperation, validating their documentation and verifying if there is a plan for testing the integration. If all of these boxes are checked, they align with their partners and the OEM to greenlight the project, have the assets sent to their Test Lab and begin the integration process. Insufficient data accuracy Step 2: The actual integration They start the integration with initial tests in their Test Lab to confirm whether or not the device provides the necessary interfaces and information. If it does, the integration process continues. Step 2.1: Benchmarking For quality assurance, all assets go through a benchmark process. Integrated assets are measured in a predefined series of tests to rate response times, delays and accuracy of the interface. Assets that do not meet their quality standards (e.g. delayed response times, insufficient data accuracy, etc.) fail this phase and the integration process is stopped. To start the benchmarking process, their team develops software that allows the gridBox to “speak” to the asset (in this case, think of the gridBox as a polyglot that can speak multiple languages in order to communicate with different assets). Range of discovery protocols Step 2.2: Scanner implementation The scanner is the software that detects and identifies the device in a network and forwards its ID and device type to their backend. For the scanner, they rely on a range of discovery protocols like ARP and SEMP. The scanner is considered done once they are able to detect and identify the appliance in a network. Once the scanner has been implemented, their team must create the code for the “driver”: a piece of software that connects the gridBox to the asset. This is needed to monitor and, if possible, control the asset. Abstract control commands Step 2.3: Monitoring implementation This step is relevant for assets they want to control in addition to monitoring This step enables them to read values from an appliance and normalize them so that they can be reported to the backend in a standardized format. Because units and data types may vary by manufacturer and model, the data often needs to be converted to comply with their format (again, much in the same way language localization takes place when translating a text from something like English to Spanish, Dutch to Portuguese, etc.). Step 2.4: Controller implementation This step is relevant for assets they want to control in addition to monitoring. The aim here is to map abstract control commands to specific asset commands. In other words, protocols and commands vary from device to device. To provide an abstraction layer that removes this variation, they build an adapter. This would ensure, for example, that the command to discharge a battery is the same regardless of the actual battery and the protocol it employs. EV charging station The set of commands that they map here depends on the appliance type because although a battery requires both a discharge and a charge command, an EV charging station only requires a charge command (unless it supports bi-directional charging). Once all of the commands have been mapped and implemented, and the scanner and driver allow the asset and gridBox to speak the same language, they move on to final end-to-end testing and documenting the integration. Step 3: Testing and documentation The last step of the integration is testing. Their development team is highly skilled, and part of what makes them so skilled is their process of testing assets, products and features in order to debug and ensure the highest functionality. During the integration testing stage, they also document the setup process in order to keep quality consistent. Ensuring optimal performance Step 3.1: Practice (testing) makes perfect They have several tests that cover different use cases and touch on all of the features of their drivers They test each integration from end-to-end to ensure optimal performance between the asset and the different XENON modules (e.g., the Tariff Timer, Energy Optimizer, Peak Shaver, etc.). Depending on the asset they’re integrating and the needs of their partner, they run tests in their lab, in the field or both.  During the testing stage, their backend team takes control over the asset and attempts to manage it remotely in order to verify that everything is working as it should. They have several tests that cover different use cases and touch on all of the features of their drivers. Some tests can be executed independently, while others require actions, such as plugging in an EV for testing an EVCS. All tests are done in their lab. Asset’s individual functionalities The general criteria for testing is scanning to find the asset from the frontend and monitoring it. If necessary, their developers will also test whether it can be controlled, too. Tests differ according to asset type, such as: Meters Inverters EVCS Heat pumps IO devices Tests for each focus on the asset’s individual functionalities. For example, batteries that are controllable are tested for inverters, and EVCS is tested if they can do a PV surplus charge. Specific tests can also be requested, such as the capabilities for advanced uses like in time-of-use optimization. Extended field testing Step 3.2: Rollout After successful testing for monitoring and controllability with the EMS, the implementation follows the software rollout of gridX via weekly and stable releases. It is first pushed to the alpha stage. As it matures, it moves to beta and then stable. If requested or deemed sensible by/with the customer, they can also add extended field testing. For 4 to 6 weeks, they do end-to-end testing together with other devices at a customer location. If desired, this will be done after the software release (i.e., alpha stage). Documenting the entire process Step 3.3: Documentation As computer scientist Damian Conway once said, “Documentation is a love letter that you write to your future self.” And, in this spirit, they finish the integration by documenting the entire process. Installers will need to know how the appliance must be installed and configured to function with XENON Documentation typically covers the commissioning of the appliance. In this state, the asset always starts from the gridBox’s default setting. Each step and change made thereafter are documented thoroughly. Screenshots are required. As the developer testing the asset moves through the steps, they add all changes and findings to the commissioning documents. This serves two purposes: first, if changes are required in the future, extensive documentation makes it easier for any engineer to comprehend and amend the previous work. Second, installers will need to know how the appliance must be installed and configured to function with XENON. Once all steps are successfully completed, it is made available to their customers. Decentralized clean assets In addition to saying that integration is what makes XENON’s hands and eyes work, Gomes Makohin also adds: “Providing high quality integrations is fundamental to get the correct data and, later, to properly steer assets toward the optimal operation point, especially from an economical and environmental perspective. Put simply: if we can't reach the assets, nothing can be done at all.” Integration doesn’t just open the door for new assets and OEMs; it is the very doorknob that has to be turned Integration doesn’t just open the door for new assets and OEMs; it is the very doorknob that has to be turned. Without it – or without it done correctly – decentralized clean assets that are the foundation to the energy transition will work against each other, rather than in harmony, rendering the energy transition a failure. Part of what sets XENON apart from other home energy management systems is the close cooperation with OEMs. They don’t just rely on certain APIs from different OEMs; they work together with them. Revolutionizing the energy landscape The efforts of their integration team stand as a testament of their commitment to driving innovation and progress within the energy ecosystem. By meticulously integrating the most crucial and relevant OEMs and models for the partners, they not only accelerate their growth but also propel the entire industry forward. They empower their partners to scale faster than the market, ushering in a new era of integration (pardon the pun), efficiency and sustainability. As they continue to forge ahead, their mission remains clear: to revolutionize the energy landscape and shape a future defined by collaboration, ingenuity and boundless potential.

Users have probably heard the term dynamic load management (DLM). Users may know that it supports power systems by allowing more charge points to run on existing grid infrastructure, thereby reducing upfront costs and recurring grid fees. Users would also know that it assists with seamless vehicle grid integration, which is vital to making the adoption of electric vehicles (EVs) more widespread. But what benefits does it offer end users? Dynamic load management First, let’s cover the basics. Dynamic load management uses an advanced algorithm that controls charging points’ energy flows to avoid overloads at the grid connection point. It takes current building load and/or residual loads into account and optimally distributes the available energy between the charging stations on a phase-specific level, constantly optimizing the charging processes so that the entire electrical capacity is utilized.  But do these benefits flow onto the customers? The short answer is yes. The long answer users will find in the following 8 points of how dynamic load management specifically the features available on gridX’s Grid Protector module – benefits consumers.  1. Makes EV charging cheaper Avoiding uncontrollable peak loads can reduce grid fees by up to €2,000 per charge point per year Dynamic load management reduces the upfront investment costs in EV charging infrastructure by avoiding expensive grid extensions, starting at around €50,000. At the same time, avoiding uncontrollable peak loads can reduce grid fees by up to €2,000 per charge point per year. Such savings can then be passed on to end users to make charging their electric cars more cost-effective. When paired with solar panels or a battery (more on that later), these savings can rise even further. 2. Makes EV charging more convenient The vast majority of people have similar schedules – this means most people want to charge their car at work during the day or at home at night. As a first step, dynamic load balancing enables an increase of 8x as many charging processes spread throughout the day with existing mains connection power. Increasing the number of available charging stations at a location already offers consumers more convenience. DLM also acts as a foundation for many other features, such as priority charging or advanced algorithms taking input about routes or state of charge into consideration which ensure that the needs of electric car drivers can always be met, regardless of what their charging behavior is.  3. Optimizes phases to maximize charging speeds gridX’s load management balances the load symmetrically across all three phases by mapping the phases Because electrical grids run on three phases, each specific conductor for each phase must be protected by actively controlling the EV charging on it. Without phase optimization, inaccurate assumptions could result in reduced charging speeds. gridX’s load management, however, balances the load symmetrically across all three phases by mapping the phases, characterizing the connected EVs, and automatically reacting to unexpected charging behavior. This maximizes the utilization of the available grid capacity and enables charging processes to speed up by 50%, depending on the considered scenario.  4. Allows for different charging modes to suit users’ needs With gridX’s Grid Protector module, operators can select different charging modes to adapt the charging behavior to the users’ specific requirements. For example: the power can be distributed evenly between all charging points; certain charging points can be constantly prioritized; the cars can be charged on a first come, first serve basis; or charging points can be scheduled to charge with different power outputs during particular time slots. Customizing the algorithm based on the location and usual charging behaviors – a workplace would have very different requirements than an airport, for example – ensures that users always receive their desired and most suitable charge.  5. Eliminates power outages Dynamic distribution of power means no overloads at the grid connection point Dynamic distribution of power means no overloads at the grid connection point, which means no power system outages aka. blackouts. Such events completely disrupt not only electric vehicle charging but also every aspect of consumers’ and businesses' lives. 6. Enables the integration of PVs and batteries DLM solution enables the maximization of self-consumption, while also ensuring that the grid connection point is not breached. Using PV surplus charging means that connected EVs can be exclusively charged with PV surplus. If there is a lack of PV production, the battery, previously charged from surplus PV power, can be discharged to support charging needs. This empowers users to take charge (pun intended) of their electric vehicle charging and see their sustainable contribution knowing it is being charged from local renewable power sources.  7. Support all models and manufacturers DLM solution doesn’t care what make of car or brand of charge point consumers use. All protocols, manufacturers, and charging solutions are supported, which enhances the ease of charging for users.  8. Failsafe and uninterrupted operation Users can enjoy completely uninterrupted charging operations due to our gridBox’s failsafe mode, which kicks in in the case of a metering failure. In addition, an offline functionality enables local control and data processing to ensure a disruption in the internet connection doesn’t affect dynamic charging processes. 

In the UK, the cause of significant energy peaks often comes from an unlikely source: the humble kettle. Because British television viewing trends are so in sync, the habit of drinking tea during an ad break has historically placed such a huge strain on the grid, that they need to import additional energy from France. This phenomenon is known as the Great British Kettle Surge. Energy management solution The 1966 FIFA World Cup Final between England and West Germany, for example, had 32,000,000 viewers in the UK. An ad break during this match would have resulted in around 1.8 million kettles being simultaneously switched on, causing additional energy demand of over 2,000 Megawatt. Now imagine that instead of turning on a kettle, all of these people were to simultaneously plug in their electric vehicle – a device that could create a greater surge and cause a power peak that would last for much longer. The good news is that with the right energy management solution, electric vehicle charging can be managed, in line with building or household loads to reduce overall peak loads – also known as peak shaving.  Lower peak loads In theory, peak shaving is very simple: it is a load management method that minimizes peaks in the load profile to level out the electricity drawn from the grid. This simplifies the process of balancing demand and supply in the grid – a crucial lever to scaling renewable energy. resource-intensive process Under these tariffs, consumers are charged based on the highest load in a given period From a grid operator’s perspective, peak shaving stabilizes loads. This optimizes the operation of the grid and reduces the need for grid expansion, a very expensive and resource-intensive process. Consequently, many grid operators incentivize consumers to reduce peak loads by applying capacity or maximum demand tariffs. Under these tariffs, consumers are charged based on the highest load in a given period. Thereby, consumers have a financial incentive to keep peaks to a minimum. Cut demand or increase supply or both There are two sides to the peak shaving equation: demand side management and supply side management. For demand side management, demand is reduced. This may be achieved by limiting the available power for EV charging infrastructure or, in industrial use cases, shutting down unused or unnecessary heavy machinery. For supply side management, local power sources are utilized to reduce the power drawn from the grid. This can be achieved with local batteries or power generators, such as PV systems or diesel generators. Demand and supply-side management can be applied individually or in combination. Regardless of the chosen means, the result is the same: the load at the grid connection point is reduced – or to stay in theme: peaks are shaved. Peak shaving in practice Say on average once a month all six chargers are simultaneously operating at their maximum Peak shaving is worthwhile whenever there are large flexible loads. Let’s look at one common use case: EV charging. In a setup with six DC chargers (each 150 kW), the total charging power equates to 900 kW. However, it is rarely the case that all six chargers are used at the same time. Say on average once a month all six chargers are simultaneously operating at their maximum at the same time. This causes a peak of 900 kW. Assuming a price of €80/kW this adds up to €72,000.  If they shaved peaks on the demand side at a peak of 600 kW, they’d reduce the capacity charge to €48,000 – saving them €24,000 a year. And even then, in the rare event of six parallel charging sessions, each car would still be charged with 100 kW. Add a battery into the setup and they can further reduce capacity charges. At current prices of less than €130/kWh. They will quickly recover the investment. Aligning peak shaving with the market XENON platform enables anyone to shave peaks and align their load with external factors: 15-minute optimization: Most grid operators bill according to the average peak within 15-minute intervals. XENON’s peak shaver allows users to benefit from this practice and optimize for 15-minute averages. In practice, this enables the use of more power without an increase in the billed peak load. Holistic optimization: Connecting a local battery and/or a PV system to include supply side management in the peak shaving offering on XENON enables the share of renewables in the power mix to be maximized. Peak shaving is relevant for a variety of use cases and as the number of electric vehicles – and other electric assets – increases, the need to minimize peaks and balance loads will only increase.