Latest Contributions by AnastasiiaSavchenko

  Hello Community! We would like to announce that we have officially set dates for the annual UNC gathering! Location: at the facilities of Veitur Energy in Reykjavik, Iceland. Dates: October 10th - October 11th. There will be a tour around one of the Veitur facilities on the evening of October 9th, so plan to arrive earlier if you would like to join. More details and detailed agenda will follow soon.  Please use this link to register your interest: https://shorturl.at/Wr3jy  See you all in October!!!  ... View more

In the attached compressed file you can find UN22 data model supportive documentation. This is a predecessor of the latest Electric Foundation Solution published by UNC group internal team of developers in 2022. In the package you can find:  UNC Policy, version 22 UNC22 Electric Distribution Model description UNC22 Structure Model description UNC22 DataElements description, beta version UNC22 Readme   ... View more

Hi all, Here is the latest Esri Electric Utility Network Foundation solution. This solution template contains a configuration that leverages a data model with integrated requirements from the Utility Network Community (UNC) founded by European electric distribution and transmission companies.  Please refer to Release notes section in the link above to track changes made in the latest electric foundation solution. ... View more

Hello all! Please join this community platform where you can ask questions, share ideas, and stay in touch with your peers from European Utility Network Community special interest group. Feel free to say hi and/or share with everyone your role and responsibilities in Utility Network migration project, as well as start your own post! Please be advised that @LydiaStekkinger is a UNC group community manager. If you have any questions or suggestions for content, or would like to be an active contributor, feel free to reach out to Lydia! P.S. Here is a cool picture of all of us in Rotterdam last week!   ... View more

Hi everyone, For those of you who haven`t had a chance to attend the district heating and cooling demonstration during #IMGIS, this is a great video to catch up on the latest district heating and cooling data modeling news. This video demonstrates:  - which components are included as a part of the district heating and cooling data model template Beta 2; - advanced modeling capabilities of the ArcGIS Utility Network for your district heating and cooling assets, including boiler plants, pump, and heat exchanger stations; - geospatial analytics for your district heating and cooling network, including water and thermal trace; - modeling your district heating and cooling network in 3D and as a part of a multi-domain network; - sharing information about your district heating and cooling assets with anyone in your organization, accessible from any device - desktop, web map, or mobile app. Thank you, Anastasiia Savchenko ... View more

By Anastasiia Savchenko and Tom DeWitte The summer is done, and the falling leaves are hinting that winter is coming. But progress on the District Heating and Cooling (DHC) data model continues its steady pace to completion. Since the late August release of beta 1, we have been working towards a mid-October release of beta 2. This will be the final beta before the release of version 1 later this year. With beta 2 the data model is feature complete, and many of the lessons learned from testing have been incorporated. Overall, this effort is on track to be completed before 2020 ends. Here is a brief summary of what’s left to be accomplished prior to the release of version 1. Data Model During the month of September testing was performed to check the ability to create and maintain information managed with the data model.  More challenging was the testing to verify that the structure network defined for this data model could be loaded into existing Esri Utility Network data models for water, electric, and gas.  Issues identified by these rounds of testing have been incorporated into the beta 2 version of the data model.  Beta 2 is feature complete. No more modifications other than corrections identified thru testing are planned before the final release. Data Dictionary Writing a data dictionary is not fun, but it is very important to explain the what, the how, and the why of the data model.  Work on the data dictionary has been ongoing and is currently about 66% complete. This data dictionary will include a description of each feature class subtype layer.  For each subtype layer, a full description of each attribute that is appropriate is provided. Additionally, the data dictionary will include a listing and description of each attribute rule that is to be included with the data model. Sample Data The sample dataset continues to evolve.  More detail has been added as well as continual cleanup of the pipe system connectivity. If you would like to see the sample data in action, click on the link below to see a Storymap containing interactive 2D and 3D maps: Symbols As this data model nears completion there is one more outstanding task.  This is the task to create an iconography-based symbology style set specifically for this data model. Being an iconography-based symbol means, no alphanumeric characters. The goal is to use universally recognized images to represent each unique type of asset.  These types of symbols can be used world-wide regardless of the native language.  Test Drive If you are interested in reviewing and testing this data model, you can download the ArcGIS Pro 2.6 compatible asset package from here: https://community.esri.com/docs/DOC-15522-district-heating-and-cooling-data-model-beta-2  If you are interested in deploying this data model to support your system or record needs, please let us know.  You can contact us via geonet or directly via email: tdewitte@esri.com, asavchenko@esri.com . ... View more

By Anastasiia Savchenko and Tom DeWitte   In May, we published the first progress update about a new Esri initiative to create District Heating and Cooling Data model. This post is the continuation of the effort to keep you informed about the District Energy data model's latest developments. The newest release of the data model is Alpha 4, and it includes the updated sample data, attribute rules, terminals, subnetworks, and heat exchanger configurations. Let's discuss all these changes in more detail.   DOWNLOAD THE ALPHA 4 PACKAGE     Sample Data Progress It is vital to provide a sample dataset, a well-thought digital twin of the several district energy system configurations. Thus, the sample data's newest version includes the supplemental configuration of the hot water and chilled water systems. Modeling this way is suitable when the district energy system serves several buildings (for example, row houses), but it measured by one meter. In this scenario, the meter measures consumption at the end of the service line, from which energy transported to multiple buildings through the network of customer pipes. Often urban areas with high population density have limited underground space, making it essential to use such system configurations. Introduction of the Business Rules Improving the editor's experience through automation and a strong rule base to help the editor enter the information correctly the first time is a key benefit of business rules. Alpha 4 is the beginning of the inclusion of attribute rules to the data model template. Attribute rules are a principal geodatabase capability of the Utility Network technology. Adding these rules is essential. They will make sure that your digital twin satisfies the business-specific requirements of the industry. The Alpha 4 release of the DHC data model includes a set of calculation attribute rules. Calculation attribute rules are responsible for an automatic population of the attribute based on the defined expression. An excellent example of this is the rules which will calculate pipe surface area and pipe volume based on the pipe shape length and diameter. More attribute rule calculations and attribute rule constraints will be added in the beta release of the data model template. Introduction of the Contingent Values In addition to the attribute rules, the Alpha 4 DHC data model includes contingent values. Contingent values are the recently-added capability of the geodatabase. Their primary function is to prevent users from entering invalid values by restricting the list of valid values for the attribute field. For example, the pipe selection of the materials available to the user changes based on the type of the system the pipe belongs to – whether it is hot water, steam, condensate, or chilled water system. Terminal Configurations In Utility Network, it is possible to model devices with a higher degree of realism by defining terminals. In the district energy system, terminals represent the incoming and outgoing flow of the hot water, chilled water, steam, or condensate. The newest DHC Alpha 4 data model includes terminal configurations for the bypasses, customer connections, and heat exchangers. The newly added terminal configuration of heat exchangers is critical to tracing analytics with this data model template. It allows for downstream traces that follow thermal energy flow through the heat exchanger and follow water flow, circulating into the heat exchanger, and then loop back. Subnetwork Configurations Besides attribute rules and terminals, the Alpha 4 DHC data model continues to build the subnetwork configurations. Subnetworks model the subsystems of a District Energy pipe system such as thermal energy system zones, pressure zones, and circulation zones. Subnetwork consists of all the participating features in the topological subset of the tier. These features include devices, lines, and junctions. Modeling of thermal energy flow vs. water flow In the district energy system, the commodity: hot water, chilled water, or steam; being transported thru the pipe system is not consumed directly by the end consumer. Instead, commodity transports and delivers the thermal energy it carries. In comparison, in other utility systems, the commodity consumed at the customer location. For example, drinking water runs from the tap; electricity provides light and power to the appliances; gas feeds the stoves and heating units. In these typical examples, the commodity runs from the source to the consumer device where it is consumed (sinks). The customer does not consume the district energy commodity. Instead, commodity warms or cools the surroundings through which it runs due to a combination of thermal processes - convection, conduction, and radiation. The heat exchanger is the device used to transfer the thermal energy without also continuing the flow of the commodity, which creates a unique modeling situation for district energy systems.  The flow of thermal energy is not always the same as the flow of the water or steam! The Alpha 4 release is the first release to provide a configuration that allows users to perform traces of the water flow through the pipe system and trace the thermal energy flow through the pipe system.  Here are some videos to show you downstream traces of the thermal energy and the water flow. You can run the trace for water flow through circulating with the heat exchanger (scenario 1). Or you can run the trace of the thermal flow through the heat exchanger (scenario 2). Not Done Yet There is still lots to be done! Although it is summer and work is usually slow due to vacation, the goal of the community is to stay productive and continue evolving this data model template. As the model moves from alpha to beta, you will see further refinement of the subnetwork definitions, summary attributes, and network attributes.  You will also see the addition of more attribute rules and connectivity rules.  Stay tuned! Conclusion Even though there is much yet to do, this effort is on schedule.  But we are always looking for more volunteers with industry knowledge to help with this effort.  If you work in or support the Steam, Heated Water, or Chilled Water utility organizations and are interested in joining one of our working groups, please let us know.  You can contact us via geonet or directly via email: tdewitte@esri.com, asavchenko@esri.com. ... View more

Hi Community members!  As you know I`m a designated sample data creator  for the DHDC data model. As we agreed the sample data is created for the City of Rotterdam. I have theoretic understanding of how the heating and cooling system should look like, but I`m lacking practical knowlegde. And so I`m asking you, experts, to help me with the following questions: 1. How do you usually model the supply and return pipes at the building level? On the picture below I have 4 pipes (heating supply and return, and cooling supply and return) that are coming to the houses. At the end of each pipe I have meter. I assume I should actually have 2 meters instead of 4? What is your experience?  From my understanding DH and DC are closed loop systems, so technically inside (?) the building should be a connection of this two pipes. How do you usually model such situation? 2. How do you usually model the supply and return pipes at the heating/cooling level? Same question but for the heating/cooling plant side. I`ve added heating plant as a point currently. Please give me some examples how do you usually model pipes coming in and out of the plants in your projects? 3. I`m looking for some screenshots/pdf pictures of the realistic district heating drawings. I will use them only as an inspiration for the sample data.  Do you have any suggestions? I`m clueless where the pumps/valves/etc should be located to make it look realistic as much as it possible? Can someone provide me with it? Looking forward to hear for you all, Thank you, Anastasiia ... View more