Patent ID: 12242775

DETAILED DESCRIPTION

FIG.1is a diagram showing an example system100for simulation of electrical power grid interconnections. The system100includes a power grid simulation server110and a user device102accessible by a user104. The server110includes a model database116and a simulation database126. The user device102may communicate with the server110over, for example, a network105.

In some examples, the model database116, the simulation database126, or both, can be separate from the server110and may communicate with the server110over the network105. The network105can include public and/or private networks and can include the Internet.

The user device102can be an electronic device such as a computing device. The user device102can be, for example, a desktop computer, a laptop computer, a smart phone, a cell phone, a tablet, a PDA, etc. The user device102is accessible by the user104.

The server110is a server system and can include one or more computing devices. In some implementations, the server110may be part of a cloud computing platform. The server110may be maintained and operated, for example, by an electrical grid operator such as an electrical power utility.

In general, the user104can provide interconnection data108to a simulation server110through an input user interface106provided through a user device102. The simulation server110can conduct simulations to generate simulation results122. The simulation server110can perform tests on the simulation results122to generate test results132. The simulation server110can provide the simulation results122, the test results132, or both, to the user device102. The user device102can present the simulation results122, the test results132, or both, through an output user interface136.

FIG.1illustrates various events, shown as stages (A) to (F), with each representing a step in an example process for simulation of electrical power grid interconnections. Stages (A) to (F) may occur in the illustrated sequence, or in a sequence that is different from the illustrated sequence. For example, some of the stages may occur concurrently.

The system100can perform simulations of electrical grid interconnections using a process600, shown inFIG.6. The process600includes receiving data for a proposed interconnection to a power grid (602). The power grid can be an electrical power grid that transmits electrical power to loads such as residential and commercial buildings. A proposed interconnection can be any change made to existing distribution feeders. A distribution feeder distributes power from a substation of a bulk power system to customer loads. The feeder is supplied from a large substation transformer at the substation, and includes load, or network or service, transformers for the distributed loads. The proposed interconnection can be, for example, a new building, renewable power plant, or stationary or mobile power storage facility. The proposed interconnection can also be, for example, an expansion to an existing building, facility, or electrical load. The interconnection data for the proposed interconnection to the power grid can include, for example, a location, a size, a positioning, a power output, or a connecting phase of the proposed interconnection.

For example, in stage (A) ofFIG.1, the system100displays an input user interface106to the user102via the user device102. The input user interface106can include an input form to enable the user104to input interconnection data108. In some examples, the input form may be a part of a power grid interconnection application that can be used by an electrical grid operator as a basis for approval or denial of the interconnection application.

The input user interface106includes input fields for various data. For example, the input user interface106includes an input field for project location, panel, and inverter details. The user104can input the interconnection data into the input fields. The input user interface106is described in greater detail with reference toFIG.2. In stage (B) ofFIG.1, the user device102sends the interconnection data108to the power grid simulation server110, e.g., over the network105.

The process600includes accessing a power grid model (604). The power grid model can include a model of real-world power grid assets, e.g., an as-built grid model114. The grid model114can include a topological representation of the power grid, electrical specifications of grid components, and empirical operation characteristics. The power grid model can also optionally include a model of one or more previously proposed interconnections to the power grid, e.g., planned grid modifications112that have not yet been built. The as-built grid model114and the planned grid modifications112can be stored in a model database116. The detail of the grid model114is sufficient to allow for accurate simulation and representation of steady-state, dynamic and transient operation of the grid.

In some examples, the grid model114can include a complete electrical model of a feeder that the proposed interconnection will connect to. For example, the grid model114can include a high resolution electrical model of one or more electrical distribution feeders. The grid model114can include, for example, data models of substation transformers, distribution switches and reclosers, voltage regulation schemes, e.g., tapped magnetics or switched capacitors, network transformers, load transformers, inverters, generators, and various loads. The grid model model114can include line models, e.g., electrical models of medium voltage distribution lines. The grid model114can also include electrical models of fixed and switched line capacitors, as well as other grid components and equipment.

The line models can include multiple segments that can represent interconnections between poles. In the case of underground lines, the segments can represent interconnections between risers or between underground connections such as transformers and meters. In some examples, the line models can be represented by equivalent inductors and resistors and capacitors for associated line lengths. In some examples, the line models can include models of mutual inductance between lines, capacitance between lines, and capacitance from the lines to ground. Line model attributes can be based on the line's connection type and on the type of conductors used. Line model attributes can also be based on construction details, e.g., whether the lines are overhead or underground.

The grid model114may be calibrated by using measured electrical power grid data. The measured electrical power grid data can include historical grid operating data. The historical grid operating data can be collected during grid operation over a period of time, e.g., a number of weeks, months, or years. In some examples, the historical grid operating data can be average historical operating data. For example, historical grid operating data can include an electrical load on a substation during a particular hour of the year, averaged over multiple years. In another example, historical grid operating data can include a number of voltage violations of the electrical power grid during a particular hour of the year, possibly averaged over multiple years, or otherwise represented statistically.

In some examples, the grid model114can include assumptions. For example, the grid model114can include measured data for certain locations of the power grid, and might not include measured data for other locations. The grid model114can use assumptions to interpolate grid operating data for locations in which measurements are not available. An assumption can be, for example, an assumed ratio or relationship between loads at industrial locations of the power grid compared to residential locations of the power grid.

In some examples, the grid model114can include measured data for certain time intervals, e.g., certain hours, and might not include measured data for other time intervals. The grid model114can use assumptions to estimate or interpolate grid operating data for time intervals in which measurements are not available. An assumption can be, for example, an assumed relationship between loads at a particular location at nighttime compared to daytime. In another example, an assumption can be an assumed relationship between loads at a particular location during an hour of the day in summertime, compared to during the same hour of the day in wintertime.

In some examples, the grid model114can include measured data for certain characteristics, e.g., electrical load, and might not include measured data for other characteristics. The grid model114can use assumptions to estimate grid operating data for characteristics for which measurements are not available. An assumption can be, for example, an assumed relationship between load and voltage at a particular location of the power grid.

In some examples, measured data can be used to resolve and reduce errors caused by assumptions in the grid model114. In some examples, the grid model114can include conservative values in place of missing or incomplete data. In some examples, the grid model114can use worst case assumptions to enable worst case analysis.

The planned grid modifications112can include previously approved interconnection projects. Previously approved interconnection projects can be, for example, projects that are, or were, ahead in an approval queue. In this way, new interconnections can be evaluated against the as-built grid model114and also evaluated against the to-be-built grid model.

For example, a first user may submit interconnection data for a first interconnection. Based on satisfactory results, the first user may submit the first interconnection for approval, and the grid operator may approve the first interconnection. Grid model data for the first interconnection can then be stored as a planned grid modification112in the model database116. A second user may then submit interconnection data for a second interconnection. The power grid simulation server110can then perform an electrical power grid simulation based on the as-built grid model114combined with the planned grid modifications112, including the first interconnection. Thus, cumulative impacts of the first interconnection and the second interconnection can be modeled and considered before approving the second interconnection.

The process600includes generating, using the interconnection data for the proposed interconnection to the power grid, and the power grid model, and the simulated power grid data (606). The simulated power grid data can be based on simulating operation of the power grid, with the proposed interconnection coupled to a location of the power grid identified by the interconnection data, during a simulated time period. The simulated power grid data can include a number of different temporal and spatially dependent characteristics of the power grid.

The simulated time period can be, for example, a simulated year. In some examples, the power grid simulator120can generate simulated power grid data, or simulation results, for each hour of the simulated year. The simulation can include predicted loads and transients over the course of the simulated year based on historical data. For example, predicted loads may vary based on predicted seasonal effects (e.g., weather conditions) and calendar effects (e.g., weekends, holidays).

The location of the power grid can include a geographic location identified by the interconnection data. For example, the location can include a postal address or a latitude and longitude coordinate position. The simulated power grid data can be based on the proposed interconnection coupled, or electrically connected, to the power grid at the identified location.

The electrical grid characteristics can include, for example, voltage, current, power, power factor, load, utilization, and temperature. In some examples, the power grid simulator120can compare a pre-interconnection simulation to a post-interconnection simulation to determine an incremental impact of the interconnection.

For example, in stage (C) ofFIG.1, the power grid simulator120receives the interconnection data108from the user device102, and the grid model114from the model database116. The power grid simulator120can then perform a series of simulations. The simulations can be based on, for example, root-mean-square (RMS), power flow, positive sequence, and/or time series voltage transient analysis.

The amount of data processed during each simulation can depend on the size and framework of the distribution feeder that the proposed interconnection will connect to. The simulation can analyze predicted effects for all connections to the affected distribution feeder and all components of the affected distribution feeder. Thus, the complexity of simulations can vary depending on construction of the distribution feeder.

For example, the simulations can vary depending on length, power, and number of loads of a distribution feeder. A typical distribution feeder can range in length from approximately one mile to ten miles. A typical distribution feeder can range in power from approximately one to ten megawatts. The number of loads connected to a feeder can range from a few hundred residential loads to several thousand residential loads. In some cases, there may also be as few as a few dozen commercial or industrial loads, and as many as hundreds of commercial or industrial loads.

The construction of a distribution feeder can also vary based on location. In urban environments, residential loads typically share transformers. In rural environments, each residential load may have a separate transformer. Commercial and industrial loads are typically served by three-phase transformers. Thus, the number of loads and transformers in a feeder could be as low as a few hundred loads with a few hundred transformers for a rural feeder. The number of loads and transformers in a feeder could be as many as thousands of loads with hundreds of single phase transformers in an urban environment, coupled with dozens or hundreds of larger three phase loads and transformers.

In some examples, the power grid simulator120can simulate operation of multiple feeders. For example, simulations can include analyses of operation of all feeders across a geographic region, e.g., a city, county, province, or state. In some cases, the power grid simulator120can model operation of each individual feeder within the region, and can aggregate the results in order to model operation of the multiple feeders of the region.

In some cases, the power grid simulator120can model operational impacts of multiple feeders on each other. For example, multiple feeders may connect to a shared substation transformer. The power grid simulator120can simulate the impacts of transients of one feeder on another feeder that is connected to the same transformer.

The power grid simulator120can analyze the expected operation of the power grid with the interconnection installed by applying empirical historical data to the grid model with the interconnection installed. The empirical historical data can include historical electrical grid characteristics based on, for example, measurements, calculations, estimates, and interpolations. The characteristics can include, for example, load, voltage, current, and power factor. The empirical historical data can represent power grid operation of multiple interconnected components within a designated geographical area. The empirical historical data can represent average electrical grid operating characteristics over a period of time, e.g., multiple weeks, months, or years.

In some examples, the simulation can analyze the operation of the power grid prior to the addition of the proposed interconnection and after the addition of the proposed interconnection. For example, the power grid simulator120can generate, using the grid model114, pre-interconnection simulated power grid data, or simulation results. The pre-interconnection simulation results can include electrical operating characteristics of the electrical power grid over a simulated period of time without the proposed interconnection.

The test evaluator130can evaluate, using the one or more metrics, the pre-interconnection simulation results to output pre-interconnection evaluation results. The pre-interconnection evaluation results can include pass and fail results for each metric for simulated operation without the proposed interconnection.

The simulation server110can compare the pre-interconnection evaluation results with the evaluation results for operation with the proposed interconnection. The simulation server110can then determine a change in evaluation results due to the proposed interconnection. Thus, the simulation server110can determine a direct incremental impact of the interconnection on the electrical grid operating conditions.

In some examples, the power grid simulator120can generate the pre-interconnection simulation results before the simulation server110receives the interconnection data108. For example, the power grid simulator120can generate the pre-interconnection simulation results periodically, e.g., once per day or once per week. In some examples, the power grid simulator120can generate the pre-interconnection simulation results in response to an event, e.g., in response to the grid model114being updated. The test evaluator130can evaluate the pre-interconnection simulation results to generate pre-interconnection test results. The simulation server110can store the pre-interconnection simulation results, the pre-interconnection test results, or both, in the simulation database126. Upon receiving interconnection data108, the simulation server110can then compare the simulation results122for the proposed interconnection with the stored pre-interconnection simulation results. The simulation server110can also compare the test results132with the stored pre-interconnection test results.

In some examples, the simulations can cover a range of operating conditions, particularly under extremes of voltage from the Bulk Power System (BPS) and extremes in load on the electrical distribution feeder. The power grid simulator120can simulate corner cases of the system with the proposed interconnection added to the existing system. The simulations can also cover electrical grid conditions during steady-state operation and during transient operation. The power grid simulator120can accurately simulate operations of loads and sources, aggregated loads and sources, and disaggregated loads and sources.

In some examples, an interconnection such as an inverter connected resource may cause transients in the electrical power grid. For example, an interconnection may cause sudden changes in voltage magnitude and phase on the electrical power grid. Multiple interconnections can amplify the sudden changes, and may cause cascading trips. The power grid simulator120can examine both causes and effects of simulated electrical transients. For example, the power grid simulator120can analyze effects of the proposed interconnection on the electrical power grid, e.g., phase and voltage magnitude changes. The power grid simulator120can also analyze effects of the phase and voltage magnitude changes on the proposed interconnection.

In some examples, voltage from the BPS can change quickly relative to control capabilities of electrical loads and inverter connected resources of the distribution system. With greater numbers of interconnections, it is possible for rapid phase shift from the BPS to cause tripping in the distribution system, e.g., due to limitations of the phase-locked loops (PLLs) of the inverter connected resources. The power grid simulator120can model the PLLs of the inverter connected resources to predict conditions that may result in tripping.

Based on the series of simulations, the power grid simulator120outputs simulation results122. The simulation results can include time-varying electrical power grid characteristics at different locations of the electrical power grid for the simulated time period. The power grid simulator120can output the simulation results122to the simulation database126and to a test evaluator130. The simulation database126can store the simulation results122as simulation result data124.

The process600includes evaluating, using one or more metrics, the simulated power grid data (608). The one or more metrics may reflect criteria from industry standards. For example, the one or more metrics may reflect criteria from interconnection standards such as IEEE 1547-2018. In some examples, the one or more metrics may reflect criteria from local industry standards. For example, simulation of interconnections in California may be evaluated based on criteria from California Rule 21, while simulation of interconnections in Hawaii may be evaluated based on criteria from Hawaii Rule 14H.

For example, in stage (D) ofFIG.1, the test evaluator130receives the simulation results122. The test evaluator130can then perform tests and evaluations of the simulation results122to determine compliance with the metrics associated with the applicable standards.

As an example, the test evaluator130can evaluate the simulation results122using voltage constraint metrics. The test evaluator130can identify voltage constraint violations in accordance with a standard such as ANSI C84.1. The test evaluator130can identify particular grid locations and simulated times of the voltage constraint violations over the simulated time period. The test evaluator130can also determine a predicted number of violations that occur in the electrical power grid during each time increment of the simulated time period. For example, the test evaluator130can determine a number of voltage constraint violations that occur during each hour of the simulated year.

In addition to voltage constraints, other example metrics can include metrics associated with voltage variability, voltage fluctuations, periodic voltage deviations, voltage transients, thermal limit violations, and backfeed constraints. The metrics can also include protection coordination for hierarchical fuse/breaker operation in fault conditions, fault current response issues, transient overvoltage, overvoltage, undervoltage, fault current capability, fault current contribution, sensitivity to phase shift, and short circuit currents. The test evaluator130can evaluate the simulation results122, using the metrics, in steady-state, transient, and dynamic conditions.

The process600includes outputting evaluation results of the one or more metrics (610). The evaluation results, e.g., test results132, can include pass or fail results for each of the one or more metrics. The test results132can also include a time-varying number of violations of each metric over the simulated time period.

For example, in stage (E) ofFIG.1, the test evaluator130outputs the test results132to the simulation database126and to the user device102. The simulation database126can store the test results as test result data134. The user device102can provide the test results132to the user104, e.g., through an output user interface136.

The test results132can include an identification of failed metrics, the timing, frequency and duration of the failed metrics, and the grid locations of the failures. For passed metrics, the test results can also include margins to the passing metric.

In some examples, the test results132can include recommended changes to the proposed interconnection that can result in a passing score, reduce the number of violations, or both. For example, the simulation server110can modify the interconnection data108. The power grid simulator can generate modified simulated power grid data, or modified simulation results, using the modified interconnection data. The test evaluator130can evaluate, using the one or more metrics, the modified simulation results to output modified test results. In this way, the simulation server110can validate the modified interconnection data against the same criteria used to evaluate the interconnection data108.

The simulation server110can compare the modified test results to the test results132. The simulation server110may determine that the modified test results are improved over the test results132. For example, the modified test results may be improved due to including fewer failures and violations, including no failures, increasing a passing margin to one or more metrics, etc. In response to determining that the modified test results are improved over the test results132, the simulation server110can output the modified interconnection data for the proposed interconnection. For example, the simulation server110can output the modified interconnection data for display to the user104as a recommendation.

Recommended changes to the interconnection application can include a range of changes including curtailment, rebuild of electrical assets, addition of storage, voltage controls, etc. Upon display of the recommendations to the user104, the user104may then choose to incorporate the recommended modifications and resubmit the modified interconnection data. In some cases, in addition to or instead of recommended changes to the interconnection application, the test results132can include recommended changes to the power grid that would result in a passing score, reduce the number of violations, or both.

In stage (F) ofFIG.1, the user device102displays the test results132to the user104through the output user interface136. The output user interface136can display a list of tests and results for each test. In some examples, the output user interface136can display a visualization of the simulation results122, the test results132, or both, in a two-dimensional and/or three-dimensional map view. In some examples, the output user interface136can display a graph, e.g., a line graph or a bar graph, that shows the number of violations over a period of time. The output user interface136can be interactive in order to enable the user104to examine the results. For example, the user104can select, e.g., using a computer mouse, an individual test, time period, or location, in order to view respective detailed simulation results. Example elements that can be displayed through the output user interface136are described with reference toFIGS.3,4A-4B, and5.

FIG.2illustrates an example user interface200including input fields for various data. The user interface200shows data for a proposed solar panel interconnection. The user interface200can be displayed to a user through a user device, e.g., the user device102of the system100.

The user interface200includes an input field for project location data202. The project location data can include, for example, a street address of the proposed interconnection, or a latitude and longitude of the proposed interconnection. In some examples, the project location data can include an allowed variability for the proposed location of the interconnection.

The user interface200also includes input fields for solar photovoltaic plant panel details204and inverter details206. The panel details204can include a power rating and an AC output for the solar panels. The inverter details206can include an inverter model, power rating, voltage rating, and power supply phase for the inverter.

The user interface200can include input fields indicating whether the inverter is certified208and whether the inverter is co-located with the load210. The user interface200can also include a user-selectable icon212for submitting the interconnection data. Once the user selects the user-selectable icon212, the user device102can send the interconnection data collected through the user interface200to the power grid simulation server110.

FIG.3illustrates an example user interface300showing output results for an interconnection simulation. The user interface300shows data for a proposed solar photovoltaic plant interconnection, e.g., the proposed interconnection that was submitted through the user interface200. The user interface300can be displayed to a user through a user device, e.g., the user device102of the system100.

The user interface300can display a test summary302including a list of tests and results for each test. The test summary302can display the metric as determined by the simulation, and the limit to which the metric was evaluated against. The results can include a “pass” or “fail” verdict. In some examples, the test summary can include a user-selectable icon305that can enable the user to view the results in additional detail. For example, additional detail can include a map view showing a location of violations, a time view showing a time of violations, or both.

The user interface300includes an example graph304showing a number of voltage violations, or failures, over a simulated period of time. The graph304includes an x-axis representing progression of time measured by a first time increment, e.g., days, over a first time period, e.g., five weeks. The graph304includes a y-axis representing a progression of time measured by a second time increment, e.g., hours, over a second time period, e.g., a day. The graph304shows a number of points. Each point corresponds to an x-axis coordinate and a y-axis coordinate. Each point represents a time interval occurring during the time period of five weeks. A color shading of each point represents the number of violations of an electrical grid parameter during the time interval.

The number of violations during a particular hour during the five-week period can be represented by a color shading defined by a legend306. Although the graph304shows voltage failures, the graph304can show violations for any parameter or metric tested by the test evaluator130. In some examples, the user interface300can include an option for the user to switch between viewing different metrics. For example, the user interface300can include a drop-down selectable icon308to enable selection of other metrics, e.g., power failures.

In some examples, in response to a user selecting a point of the graph304, the user interface300can display a corresponding evaluation result. The corresponding evaluation result can include, for example, a number of violations that occurred during the selected time increment.

For simplicity, only three ranges of failures are shown in the graph304ofFIG.3. According to the legend306Grid coordinates shaded white represent times during which the number of failures was between 0 and 2,500. Grid coordinates shaded gray represent times during which the number of failures was between 2,500 and 5,000. Grid coordinates shaded black represent times during which the number of failures was between 5,000 and 7,500. Additional ranges can be included, and can be represented by any color-coding scheme. In some examples, the color shading may be a gradient shading.

The user interface300includes example graphs310,312showing time-varying trends of voltage failures. The graph310shows a number of voltage failures by time of day. The graph312shows a number of voltage failures by day of week. The graphs310,312can show data for a particular day, or averaged data over multiple days. Data for the graphs310,312can be, for example, simulation result data generated over a simulated time period.

In some examples, the user interface300can include user-selectable icons320for approving or denying the proposed interconnection. For example, the user may be a grid operator. Based on reviewing the simulation results as displayed through the user interface300, the grid operator can select to approve or deny the interconnection.

Though described as including certain elements and features, the user interface300can include more elements or fewer elements. For example, a user may adjust settings and preferences for the elements displayed on the user interface. In some examples, a user may select a preference to view a two-dimensional map view of the grid instead of, or in addition to, the graph304. In some examples, the user may select to view power failures instead of, or in addition to, voltage violations.

FIGS.4A,4B, and5illustrate example user interface elements400a,400b, and500, for displaying interconnection simulation results and test results. In some examples, the user interface elements400a,400b, and500can be incorporated into the user interface300. In some examples, the user interface elements400a,400b, and500can be linked from the user interface300. For example, using the user device102, the user may select a link displayed on the user interface300. Upon selecting the link, the user device102can present the user interface elements400a,400b, and/or500to the user.

FIGS.4A and4Billustrate example user interface elements400a,400bshowing a two-dimensional map view of evaluation results. The user interface elements400a,400bcan display a visualization of the simulations results122, the test results132, or both, in the two-dimensional map view.

The user interface elements400a,400beach show a line-diagram representation of power lines in the power grid overlaid on a map of a geographic region in which the power grid is located. The line-diagram includes a number of line segments. A color shading of each line segment can be used to represent the evaluation results at a particular spatial location of the power grid. The evaluation results can be for a particular simulated time, or can be averaged or accumulated over a period of simulated time.

Attributes of the line segments of the user interface elements400a,400bcan represent characteristics of the simulated electrical power grid operation. An attribute can be, for example, a color, shading, or thickness of the line segment. Characteristics of the simulated operation can include e.g., voltage, real power, power factor, line utilization, and transformer utilization. Characteristics of the simulated operation can also include violations of electrical power grid metrics. For example, the attributes of the line segments can represent a location of voltage violations.

InFIGS.4A and4B, line segments represent locations of electrical power grid components. Dark shaded line segments410represent locations of the electrical power grid where there are no violations, or where the number of violations is below a threshold limit. Light shaded line segments420represent locations of the electrical power grid where there are violations, or where the number of violations is above a threshold limit.

In some examples, in response to a user selecting a point of the line segments, the user interface element400aor400bcan display a corresponding evaluation result. The corresponding evaluation result can include, for example, a number of violations that occurred in the corresponding grid location over the simulated period of time.

In the user interface element400a, the number of violations is below the threshold limit for all locations of the electrical power grid. Thus, all line segments of the user interface element400bhave a dark shading. The user interface element400amay show, for example, power grid simulation results without a proposed interconnection.

In the user interface element400a, the number of violations is below the threshold limit for some locations of the electrical power grid, and above the threshold limit for other locations of the electrical power grid. Thus, certain line segments of the user interface element400bhave a dark shading, while other line segments of the user interface element400bhave a light shading. The user interface element400bmay show, for example, power grid simulation results with a proposed interconnection. Thus, by comparing the user interface element400ato the user interface element400b, a user can compare simulated pre-interconnection and post-interconnection operation of the power grid. In the example ofFIGS.4A and4B, installing the interconnection likely results in voltage violations in various locations of the electrical power grid.

FIG.5illustrates an example of a user interface element showing a three-dimensional map view of power grid data. The user interface element500includes a visualization of the power grid data in three windows. The user interface element500can show, for example, simulated electrical power grid characteristics for the electrical power grid with the proposed interconnection coupled to a location of the power grid identified by the interconnection data.

In some examples, the user interface element500can include a comparison view. The comparison view can enable a user to view simulated electrical power grid characteristics both for the as-built electrical power grid and for the electrical power grid with the proposed interconnection. By comparing the pre-interconnection characteristics with the post-interconnection characteristics, the user can determine impacts of the interconnection on the electrical power grid.

The user interface element500includes a first window510. The first window510includes a line-diagram representation of power lines of the power grid. The user interface element500can also show representations of other elements of the power grid with the line-diagram. The line-diagram is overlaid on a map508of a geographic region. The map508of the geographic region is a map of the geographic region in which the power grid is located. The user interface element500can include a map menu514. A user can select one or more icons of the map menu514in order to view the line-diagram overlaid on a street-view, satellite, aerial, and/or topological map view, or any combination of map views.

The line-diagram includes one or more line segments512(illustrated as dashes in one branch of the line diagram). Each line segment can represent a portion of the wires of the power grid. Attributes of each line segment512can represent power grid data at a particular spatial location of the power grid. In some implementations, the spatial resolution (and size in pixels) of each line segment can vary to accommodate the spatial resolution of the received power grid data. For example, if power grid data is available at 1000 foot intervals along a 10,000 foot length of feeder line, the GUI can represent that particular length of feeder line with 10 different line segments. The color and/or shade and/or width, and/or height of a line segment can indicate one or more characteristics of the power grid at that line segment at a particular point in time. Line segments can show moving arrows indicating the direction and magnitude of a characteristic of the power grid at that line segment at a particular point in time.

The user interface element500includes a player534. The player534enables the user interface element500to show characteristics of the power grid over time. The player534includes a “play” icon536that allows the user to play, pause, and resume the display of characteristics of the power grid over time. The player also includes538icons that allow the user to select different playback rates. The player also includes a time display540of the time for which the characteristics of the power grid are shown.

The user interface element500includes a second window520. The second window520includes at least one graph with an X axis in the direction of arrow522and a Y axis in the direction of arrow524. Each graph can represent values of a characteristic of the power grid over time and space. Each value can be represented by respective coordinates on the graph and a shade. For each value of the characteristic, an X-coordinate represents a distance of the value from a reference point in the power grid, e.g., a power source. For each value of the characteristic, a Y-coordinate represents a time of the value. A marker perpendicular to the Y axis and moving in the direction of the Y axis marks the time of the values along the marker, which may also be the time displayed in the player534and the time of the characteristics of the power grid represented in the user interface element500. A shade of the value represents a magnitude of the value. In some examples, the magnitude is an absolute magnitude. In some examples, the magnitude is a relative magnitude. In some examples, data may not be available for all locations of the power grid. Missing data can be represented by a dark or black shading.

The user interface element500includes a third window530. The third window530includes a menu. The menu includes user-selectable icons532that permit toggling representation of different characteristics of the power grid on and off. The user can select the icons532of the menu in the third window530in order to view one characteristic or a selected combination of characteristics in the first window510and the second window520. When a user selects one of the icons532to toggle a respective characteristic on, representation of the respective characteristic is displayed within the first window510, the second window520, or both. When a user selects more than one of the icons532to toggle a combination of respective characteristics on, a representation of the respective characteristics is displayed together spatially and temporally within the first window510, and side-by-side in the second window520, or both.

For the user-selectable icons532that permit toggling representation of different characteristics of the power grid, the characteristics themselves are represented by different colors, shown in the third window530. The magnitude of the value of the characteristics can be represented by shades or gradients. Anomalous values of the characteristics can be represented by different colors or shades.

The third window530includes a selector533that allows the user to select, for the toggled on characteristics of the power grid, to display by color in the first window510and the second window520either all values or only anomalous values.

In some examples, a user can simulate adding and removing assets to the power grid. For example, the user can simulate adding power sources and/or power loads to the power grid. The user interface element500can display effects of the changing assets on the characteristics of the power grid.

In some examples, a user can input an optimization requirement for adjusting one or more characteristics. The computing system can compute a solution to the optimization requirement and can display simulated characteristics for implementing the solution.

This disclosure generally describes computer-implemented methods, software, and systems for electrical power grid visualization. A computing system can receive various electrical power grid data from multiple sources. Power grid data can include different temporal and spatially dependent characteristics of a power grid. The characteristics can include, for example, power flow, voltage, power factor, feeder utilization, and transformer utilization. These characteristics can be coupled; for example, some characteristics may influence others and/or their temporal and spatial dependence may be related.

Data sources can include satellites, aerial image databases, publicly available government power grid databases, and utility provider databases. The sources can also include sensors installed within the electrical grid by the grid operator or by others, e.g., power meters, current meters, voltage meters, or other devices with sensing capabilities that are connected to the power grid. Data sources can include databases and sensors for both high voltage transmission and medium voltage distribution and low voltage utilization systems.

The data can include, but is not limited to, map data, transformer locations and capacities, feeder locations and capacities, load locations, or a combination thereof. The data can also include measured data from various points of the electrical grid, e.g., voltage, power, current, power factor, phase, and phase balance between lines. In some examples, the data can include historical measured power grid data. In some examples, the data can include real-time measured power grid data. In some examples, the data can include simulated data. In some examples, the data can include a combination of measured and simulated data.

Implementations of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly-implemented computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. The computer storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

The term “data processing apparatus” refers to data processing hardware and encompasses all kinds of apparatus, devices, and machines for processing data, including, by way of example, a programmable processor, a computer, or multiple processors or computers. The apparatus can also be or further include special purpose logic circuitry, e.g., a central processing unit (CPU), a FPGA (field programmable gate array), or an ASIC (application-specific integrated circuit). In some implementations, the data processing apparatus and/or special purpose logic circuitry may be hardware-based and/or software-based. The apparatus can optionally include code that creates an execution environment for computer programs, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. The present disclosure contemplates the use of data processing apparatuses with or without conventional operating systems, for example Linux, UNIX, Windows, Mac OS, Android, iOS or any other suitable conventional operating system.

A computer program, which may also be referred to or described as a program, software, a software application, a module, a software module, a script, or code, can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, e.g., one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files, e.g., files that store one or more modules, sub-programs, or portions of code. A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network. While portions of the programs illustrated in the various figures are shown as individual modules that implement the various features and functionality through various objects, methods, or other processes, the programs may instead include a number of sub-modules, third party services, components, libraries, and such, as appropriate. Conversely, the features and functionality of various components can be combined into single components as appropriate.

The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., a central processing unit (CPU), a FPGA (field programmable gate array), or an ASIC (application-specific integrated circuit).

Computers suitable for the execution of a computer program include, by way of example, can be based on general or special purpose microprocessors or both, or any other kind of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a central processing unit for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device, e.g., a universal serial bus (USB) flash drive, to name just a few.

Computer-readable media (transitory or non-transitory, as appropriate) suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The memory may store various objects or data, including caches, classes, frameworks, applications, backup data, jobs, web pages, web page templates, database tables, repositories storing business and/or dynamic information, and any other appropriate information including any parameters, variables, algorithms, instructions, rules, constraints, or references thereto. Additionally, the memory may include any other appropriate data, such as logs, policies, security or access data, reporting files, as well as others. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, implementations of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube), LCD (liquid crystal display), or plasma monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.

The term “graphical user interface,” or GUI, may be used in the singular or the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Therefore, a GUI may represent any graphical user interface, including but not limited to, a web browser, a touch screen, or a command line interface (CLI) that processes information and efficiently presents the information results to the user. In general, a GUI may include a plurality of user interface (UI) elements, some or all associated with a web browser, such as interactive fields, pull-down lists, and buttons operable by the business suite user. These and other UI elements may be related to or represent the functions of the web browser.

Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN), a wide area network (WAN), e.g., the Internet, and a wireless local area network (WLAN).

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any system or on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular implementations of particular systems. Certain features that are described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of sub-combinations.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be helpful. Moreover, the separation of various system modules and components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Particular implementations of the subject matter have been described. Other implementations, alterations, and permutations of the described implementations are within the scope of the following claims as will be apparent to those skilled in the art.

For example, the actions recited in the claims can be performed in a different order and still achieve desirable results.

Accordingly, the above description of example implementations does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure.