Controller for modular power systems

Abstract

Various systems, methods, and computer program products are provided for operating a power system fabric via a controller. The method includes receiving controller runtime code of a power system fabric. The controller runtime code is specifically designed to configure and / or operate the power system fabric. The method also includes automatically deploying controller runtime code on the controller. The method also includes debugging the power system structure using the deployed controller runtime code. The power system architecture may be remotely commissioned.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application is a continuation-in-part application of co-pending PCT International Application No. PCT / US22 / 19163, which claims the benefit of U.S. Provisional Application No. 63 / 156,977 filed on March 5, 2021, and the contents of these two applications are incorporated herein by reference in their entirety. Technical Field

[0003] Example embodiments relate generally to power structure design and, more particularly, to generating schematic diagrams of power system structures. Background Art

[0004] The global power generation and distribution system is evolving from a centralized model with limited resources (electricity is generated in one place and distributed to the masses) to an increasingly more renewable and decentralized operating model that includes distributed power electronics, decentralized energy storage systems, and decentralized (renewable) generation sources to supply decentralized loads (e.g., appliances, electric vehicles (EVs), lighting, heating, ventilation, cooling individual residences, commercial facilities, and communities).

[0005] At the same time, this development has promoted the power system to become increasingly modular, which consists of solar photovoltaic modules, battery modules, and power conversion modules to manage power, change voltage and current levels for interoperability, and convert between direct current (DC) and alternating current (AC) for compatibility. Based on the availability of a variety of modules, system engineers can assemble customized decentralized power systems, which feature generation, storage, and distribution assets with intermediate power conversion devices and protection equipment. The modular characteristics of decentralized power systems simultaneously generate economies of scale and redundant reliability.

[0006] The various modules available on the market are characterized by limited specifications, lack of standardization, fragmented design tools, processes, supply chains, and require specialized skills to design and deploy operating systems that comply with local regulations. This makes the design process complex, resource-intensive, time-consuming and expensive.

[0007] The present invention aims to reduce the complexity of designing distributed, renewable or limited energy power generation systems by partially automating the design processes and features. Summary of the invention

[0008] An overview of some embodiments of the present disclosure is given below. This overview is not intended to indicate the key or important elements of all embodiments, nor to describe the scope of any or all embodiments. Its sole purpose is to present certain concepts and elements of one or more embodiments in the form of an overview as a preface to a more detailed description below.

[0009] In an example embodiment, a system for dynamically generating a representation of a power system structure is provided. The system includes at least one non-transitory storage device and at least one processing device coupled to the at least one non-transitory storage device. The at least one processing device is configured to provide one or more element icons that can be added to the power system structure representation. The one or more element icons each represent a physical element that can be used in the power system structure. The at least one processing device is also configured to receive an indication of a first element icon among the one or more element icons to be used in the power system structure. The at least one processing device is also configured to assign the first element icon to one of a plurality of element cells of the power system structure representation. The at least one processing device is also configured to determine a unit action, which is configured to indicate a relationship between a unit to which the first element icon is assigned and at least another element cell of the plurality of element cells of the power system structure.

[0010] In some embodiments, the unit action is a connection type between the selected component icon and a second component icon assigned to another unit of the plurality of component units, the connection type indicating how physical components associated with the first component icon and the second component icon are connected in the power system structure.

[0011] In some embodiments, at least one processing device is further configured to store an attribute table for each of the one or more component icons, each attribute table comprising an attribute field and an attribute value. In such an embodiment, the attribute field is a description of a physical component associated with a given component icon, and the attribute value is a value associated with the attribute field. In some embodiments, the unit action is determined based on at least one of the attribute table of the first component icon or the attribute table of the second component icon assigned to another unit in the plurality of component units.

[0012] In some embodiments, the at least one processing device is further configured to determine at least one power system structure value indicative of an operating efficiency of the power system structure. In some embodiments, the at least one power system structure value includes at least one of a cost of constructing the power system structure, a cost of operating the power system structure, or a system load of the power system structure.

[0013] In some embodiments, each physical element is a load, a generator, a storage device, or a power conversion device. In some embodiments, the power system structure representation is a schematic diagram. In some embodiments, the power system structure representation allows dynamic changes, including moving one of the component icons to another unit, wherein the at least one processing device is further configured to update the unit action of the moved component icon.

[0014] In some embodiments, the at least one processing device is further configured to provide a selectable icon having information on how to purchase a physical component associated with a given component icon.

[0015] In another example embodiment, a computer program product for dynamically generating a power system structure representation is provided. The computer program product includes at least one non-transitory computer-readable medium, which contains a computer-readable program code portion. The computer-readable program code portion includes an executable portion configured to provide one or more component icons, which can be added to the power system structure representation. One or more component icons each represent a physical element that can be used in the power system structure. The computer-readable program code portion also includes an executable portion, which is configured to receive an indication of a first component icon in one or more component icons to be used in the power system structure. The computer-readable program code portion also includes an executable portion, which is configured to assign the first component icon to one of the multiple component units represented by the power system structure. The computer-readable program code portion also includes an executable portion, which is configured to determine a unit action, which is configured to indicate the relationship between the unit to which the first component icon is assigned and at least another component unit of the multiple component units of the power system structure.

[0016] In some embodiments, the unit action is a connection type between the selected component icon and a second component icon assigned to another unit of the plurality of component units, the connection type indicating how physical components associated with the first component icon and the second component icon are connected in the power system structure.

[0017] In some embodiments, the computer readable program code portion includes an executable portion configured to store an attribute table for each of the one or more component icons, each attribute table including an attribute field and an attribute value. In such an embodiment, the attribute field is a description of a physical component associated with a given component icon, and the attribute value is a value associated with the attribute field. In some embodiments, the unit action is determined based on at least one of the attribute table of the first component icon or the attribute table of the second component icon assigned to another unit in the plurality of component units.

[0018] In some embodiments, the computer readable program code portion includes an executable portion configured to determine at least one power system structure value indicative of an efficiency of operation of the power system structure. In some embodiments, the at least one power system structure value includes at least one of a cost of constructing the power system structure, a cost of operating the power system structure, or a system load of the power system structure.

[0019] In some embodiments, each physical element is a load, a generator, a storage device, or a power conversion device. In some embodiments, the power system structure representation is a schematic diagram.

[0020] In some embodiments, the power system structure representation allows dynamic changes including moving one of the component icons to another unit, and the computer readable program code portion includes an executable portion configured to update the unit action of the moved component icon.

[0021] In some embodiments, the computer readable program code portion includes an executable portion configured to provide a selectable icon having information on how to purchase a physical component associated with a given component icon.

[0022] In another example embodiment, a computer-implemented method for dynamically generating a representation of a power system structure is provided. The method includes providing one or more component icons that can be added to the representation of the power system structure. The one or more component icons each represent a physical element that can be used in the power system structure. The method also includes receiving an indication of a first component icon of the one or more component icons to be used in the power system structure. The method also includes assigning the first component icon to one of a plurality of component cells of the representation of the power system structure. The method also includes determining a cell action that is configured to indicate a relationship between a cell to which the first component icon is assigned and at least another cell of the plurality of component cells of the power system structure.

[0023] In some embodiments, the unit action is a connection type between the selected component icon and a second component icon assigned to another unit of the plurality of component units, the connection type indicating how physical components associated with the first component icon and the second component icon are connected in the power system structure.

[0024] In some embodiments, the method further comprises storing an attribute table for each of the one or more component icons, each attribute table comprising an attribute field and an attribute value. In such embodiments, the attribute field is a description of a physical component associated with a given component icon, and the attribute value is a value associated with the attribute field. In some embodiments, the unit action is determined based on at least one of the attribute table of the first component icon or the attribute table of the second component icon assigned to another unit in the plurality of component units.

[0025] In some embodiments, the method further comprises determining at least one power system structure value indicative of an operating efficiency of the power system structure. In some embodiments, the at least one power system structure value comprises at least one of a cost of constructing the power system structure, a cost of operating the power system structure, or a system load of the power system structure.

[0026] In some embodiments, each physical element is a load, a generator, a storage device, or a power conversion device. In some embodiments, the power system structure representation is a schematic diagram.

[0027] In some embodiments, the power system structure representation allows dynamic changes, including moving one of the component icons to another unit, and the method further includes a unit action of updating the moved component icon.

[0028] In some embodiments, the method further includes providing a selectable icon having information on how to purchase the physical component associated with a given component icon.

[0029] In an exemplary embodiment, a controller for operating a power system structure. The controller includes at least one non-transitory storage device and at least one processing device, the at least one processing device coupled to the at least one non-transitory storage device. The at least one processing device is configured to receive a controller runtime code for the power system structure. The controller runtime code is specifically designed to operate the power system structure. The at least one processing device is also configured to automatically deploy the controller runtime code on the controller. The at least one processing device is also configured to debug the power system structure using the deployed controller runtime code, wherein the power system structure is remotely debugged.

[0030] In various embodiments, the at least one processing device is further configured to receive an update of the controller runtime code based on a change in the power system structure. In various embodiments, the at least one processing device is further configured to generate a configuration of the power system structure, wherein the controller runtime code is configured based on the generated configuration.

[0031] In various embodiments, the at least one processing device is further configured to monitor one or more variables of at least one physical element of the power system structure. In various embodiments, the at least one processing device is further configured to monitor one or more variables of the power system structure. In various embodiments, the at least one processing device is further configured to monitor one or more variables of the power system structure. In various embodiments, the at least one processing device is further configured to cause transmission of an alarm message based on a change in at least one of the one or more monitored variables of the power system structure. In various embodiments, the one or more monitored variables of the power system structure include at least one of power consumption or efficiency.

[0032] In another example embodiment, a computer program product for operating a power system structure via a controller is provided. The computer program product includes at least one non-transitory computer-readable medium, wherein the non-transitory computer-readable medium contains a computer-readable program code portion. The computer-readable program code portion includes an executable portion, which is configured to receive a controller runtime code of the power system structure. The controller runtime code is specifically designed to operate the power system structure. The computer-readable program code portion also includes an executable portion, which is configured to automatically deploy the controller runtime code on the controller. The computer-readable program code portion also includes an executable portion, which is configured to debug the power system structure using the deployed controller runtime code. The power system structure is remotely debugged.

[0033] In various embodiments, the computer readable program code portion further includes an executable portion configured to receive an update of the controller runtime code based on a change in the power system structure. In various embodiments, the computer readable program code portion further includes an executable portion configured to generate a configuration of the power system structure, wherein the controller runtime code is configured based on the generated configuration. In various embodiments, the computer readable program code portion further includes an executable portion configured to monitor one or more variables of at least one physical element of the power system structure.

[0034] In various embodiments, the computer readable program code portion further comprises an executable portion configured to monitor one or more variables of the power system structure. In various embodiments, the computer readable program code portion further comprises an executable portion configured to cause transmission of an alarm message based on a change in at least one of the one or more monitored variables of the power system structure. In various embodiments, the one or more monitored variables of the power system structure include at least one of power consumption or efficiency.

[0035] In another example embodiment, a computer-implemented method of operating a power system structure via a controller is provided. The method includes receiving a controller runtime code for the power system structure. The controller runtime code is specifically designed to operate the power system structure. The method also includes automatically deploying the controller runtime code on the controller. The method also includes debugging the power system structure using the deployed controller runtime code. The power system structure is remotely debugged.

[0036] In various embodiments, the method further comprises receiving an update to the controller runtime code based on a change in the power system structure. In various embodiments, the method further comprises monitoring one or more variables of at least one physical element of the power system structure. In various embodiments, the method further comprises generating a configuration of the power system structure, wherein the controller runtime code is configured based on the generated configuration.

[0037] In various embodiments, the method further comprises causing transmission of an alarm message based on a change in at least one of the one or more monitored variables of the power system structure. In various embodiments, the one or more monitored variables of the power system structure include at least one of power consumption or efficiency.

[0038] Embodiments of the present disclosure address the above needs and / or achieve other advantages by providing an apparatus (e.g., a system, a computer program product, and / or other device) and a method for dynamically generating a representation of a power system structure. System embodiments may include one or more memory devices (on which a computer-readable program code is stored), a communication device, and one or more processing devices (which are operably coupled to the one or more memory devices), wherein one or more processing devices are configured to execute the computer-readable program code to implement the embodiments. In a computer program product embodiment of the present disclosure, the computer program product includes at least one non-transitory computer-readable medium, which includes computer-readable instructions for executing the embodiments. Computer-implemented method embodiments of the present disclosure may include providing a computing system including a computer processing device and a non-transitory computer-readable medium, wherein the computer-readable medium includes a configured computer program instruction code so that when the instruction code is executed by the computer processing device, the computer processing device performs certain operations to implement the embodiments.

[0039] BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Having generally described embodiments of the present disclosure, reference will now be made to the accompanying drawings, in which:

[0041] Figure 1 A block diagram illustrating a system environment for dynamically generating a representation of a power system structure according to an embodiment of the present disclosure is provided;

[0042] Figure 2 Provided is a diagram showing an embodiment of the present disclosure Figure 1 A block diagram of a physical system 200;

[0043] Figure 3 Provided is a diagram showing an embodiment of the present disclosure Figure 1 A block diagram of a representation generation engine device 300;

[0044] Figure 4 Provided is a diagram showing an embodiment of the present disclosure Figure 1 A block diagram of a computing device system 400;

[0045] Figure 5 A flowchart of a method for creating a power system structure diagram according to an embodiment of the present disclosure is shown;

[0046] Figure 6 A complete example power system structure representation according to an embodiment of the present disclosure is shown;

[0047] Figure 7 A two-dimensional grid representation of a power system structure representation according to an embodiment of the present disclosure is shown;

[0048] Figure 8A-8C Three different component icon configurations according to embodiments of the present disclosure are shown;

[0049] Fig. 9 shows a generator element icon representing a physical element of a generator according to an embodiment of the present disclosure;

[0050] Fig.10 shows a storage element icon representing a physical element of a storage device according to an embodiment of the present disclosure;

[0051] Fig.11 A load element icon representing a load physical element according to an embodiment of the present disclosure is shown;

[0052] Fig.12 shows a converter element icon representing a converter physical element according to an embodiment of the present disclosure;

[0053] Fig.13 shows a component icon and a corresponding attribute table according to an embodiment of the present disclosure;

[0054] Figure 14-16 shows an example power system structure representation made in accordance with various embodiments of the present disclosure;

[0055] Fig.17 A flowchart of a method for dynamically generating a power system structure representation according to an embodiment of the present disclosure is shown;

[0056] Fig.18 An example power system structure according to an embodiment of the present disclosure is shown, the example power system structure including an implementation controller device for commissioning and / or operating the power system structure;

[0057] Fig.19 shows the structure of the runtime code received by the controller according to an embodiment of the present disclosure; and

[0058] Fig. 20A flow chart of a method for debugging a power system structure according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0059] The following will be a more comprehensive description of embodiments of the present disclosure with reference to the accompanying drawings, in which some but not all embodiments of the present disclosure are shown. In fact, the present disclosure can be implemented in many different forms and should not be construed as being limited to the embodiments set forth herein; on the contrary, these embodiments are provided so that the present disclosure meets applicable legal requirements. Unless otherwise expressly stated, any term expressed in the singular herein is also meant to include the plural form, and vice versa, where possible. In addition, as used herein, the terms "one" and / or "an" will mean "one or more", even if the phrase "one or more" is also used herein. In addition, when it is said that something is "based on" another thing, it may also be based on one or more other things. In other words, unless expressly stated, "based on" as used herein means "based at least in part" or "based at least in part". Throughout the text, the same reference numerals represent the same elements.

[0060] As described herein, the term "entity" can be any organization that utilizes one or more entity resources, including but not limited to one or more entity systems, one or more entity databases, one or more applications, one or more servers, etc. to perform one or more organizational activities associated with an entity. In some embodiments, an entity can be any organization that develops, maintains, utilizes and / or controls one or more applications and / or databases. The application described herein can be any software application that is configured to perform one or more operations of an entity. The database described herein can be any data storage of data associated with organizational activities associated with an entity. In some embodiments, an entity can be a financial institution, which can include any financial institution in this article, such as a commercial bank, a savings bank, a federal and state savings bank, a savings and loan association, a credit union, an investment company, an insurance company, etc. In some embodiments, a financial institution can allow a client to set up an account at a financial institution. In some embodiments, an entity can be a non-financial institution.

[0061] Many of the example embodiments and implementations described herein contemplate user interactions with a computing device and / or one or more communication devices and / or secondary communication devices. A "user" as referred to herein may refer to an entity or individual with the ability and / or authorization to access and use one or more applications provided by an entity and / or system of the present disclosure. Additionally, as used herein, the term "user computing device" or "mobile device" may refer to a mobile phone, computing device, tablet computer, wearable device, smart device, and / or any portable electronic device capable of receiving and / or storing data therein.

[0062] A "user interface" is any device or software that allows a user to input information (such as commands or data) to a device or allows a device to output information to a user. For example, a user interface includes a graphical user interface (GUI) or an interface for inputting computer-executable instructions that instruct a processing device to perform a specific function. A user interface typically uses certain input and output devices to input data received from a user or output data to a user. These input and output devices may include a display, mouse, keyboard, buttons, touchpad, touch screen, microphone, speaker, LED, light, joystick, switch, buzzer, bell, and / or other user input / output devices for communicating with one or more users.

[0063] As used herein, "machine learning algorithm" may refer to a program (mathematical and logical) that is configured to self-adjust and perform better when exposed to more data. To this extent, machine learning algorithms are able to adjust their own parameters given feedback on previous performance of making predictions on a data set. Machine learning algorithms contemplated, described, and / or used herein include supervised learning (e.g., using logistic regression, using back-propagation neural networks, using random forests, decision trees, etc.), unsupervised learning (e.g., using an Apriori algorithm, using K-means clustering), semi-supervised learning, reinforcement learning (e.g., using a Q-learning algorithm, using temporal difference learning), and / or any other suitable machine learning model type. Each of these types of machine learning algorithms can implement any one or more of the following: regression algorithms (e.g., ordinary least squares, logistic regression, stepwise regression, multivariate adaptive regression splines, local estimated scatter plot smoothing, etc.), instance-based methods (e.g., k-nearest neighbors, learning vector quantization, self-organizing maps, etc.), regularization methods (e.g., ridge regression, least absolute shrinkage and selection operators, elastic net, etc.), decision tree learning methods (e.g., classification and regression trees, iterative bisection3, C4.5, chi-square automatic interaction detection, decision stumps, random forests, multivariate adaptive regression splines, gradient boosting machines, etc.), Bayesian methods (e.g., Bayesian Bayes), average single dependency estimator, Bayesian trust network, etc.), kernel methods (e.g., support vector machine, radial basis function, etc.), clustering methods (e.g., k-means clustering, expectation maximization, etc.), association rule learning algorithms (e.g., Apriori algorithm, Eclat algorithm, etc.), artificial neural network models (e.g., perceptron method, back propagation method, Hopfield network method, self-organizing map method, learning vector quantization method, etc.), deep learning algorithms (e.g., restricted Boltzmann machine, deep trust network method, convolutional network method, stacked autoencoder method, etc.), dimensionality reduction methods (e.g., principal component analysis, partial least squares regression, Sammon mapping, multidimensional scaling, projection pursuit, etc.), integration methods (e.g., boosting, bootstrapped aggregation, AdaBoost, stacked generalization, gradient boosting machine method, random forest method, etc.), and / or any suitable form of machine learning algorithm.

[0064] As used herein, "machine learning model" may refer to a mathematical model generated by a machine learning algorithm based on sample data (called training data) that can make predictions or decisions without being explicitly programmed. A machine learning model represents what the machine learning algorithm has learned and the rules, numbers, and any other algorithm-specific data structures required to represent the classification.

[0065] Embodiments of the present disclosure include a method for organizing and automating a distributed power system design process. The method can be embedded in a graphics program, where component icons can be drawn on a two-dimensional spatial grid consisting of individual cells referenced by coordinates. The component icon is a representation of a physical component, such as a load asset, a storage asset, a generation asset, a power conversion device, a protection device, and / or the like. A table of attribute fields and values ​​is attached to each component icon to preserve its physical properties. When an empty cell of the spatial grid is selected, the disclosed method will suggest that a new entity be added to the selected empty cell of the spatial grid. When a non-empty cell of the spatial grid is selected, the disclosed method will suggest that the attribute value in the attribute field be attached to the selected non-empty cell. The attribute fields are grouped in independent data layers, supporting the reproducibility and combination of data layers. Multiple two-dimensional spatial grids can be linked by referencing component icons, thereby creating instances of existing designs and maximizing reproducibility.

[0066] Figure 1 A block diagram illustrating a system environment 100 for dynamically generating a representation of a power system structure is provided. Figure 1As shown, the environment 100 includes a representation generation engine device 300, an entity system 200, an implementation controller device 120, and a computing device system 400. One or more users 110 may be included in the system environment 100, wherein the user 110 interacts with other entities of the system environment 100 via a user interface of the computing device system 400. In some embodiments, one or more users 110 of the system environment 100 may be employees of an entity associated with the entity system 200 (e.g., application developers, database administrators, application owners, application end users, business analysts, financial agents, etc.).

[0067] Entity system 200 may be any system owned or controlled by an entity to support or perform one or more process steps described herein. In some embodiments, the entity is a financial institution. In some embodiments, the entity may be a non-financial institution. In some embodiments, the entity may be any organization that utilizes one or more entity resources to perform one or more organizational activities.

[0068] The representation generation engine device 300 is a system of the present disclosure, which is used to perform one or more process steps described herein. In some embodiments, the representation generation engine device 300 can be an independent system. In some embodiments, the representation generation engine device 300 can be a part of the entity system 200. For example, the method discussed herein can be performed by the entity system 200, the representation generation engine device 300, the computing device system 400 and / or a combination thereof.

[0069] The representation generation engine device 300, the implementation controller device 120, the entity system 200 and / or the computing device system 400 can perform network communication in the system environment 100 through the network 150. The network 150 may include a local area network (LAN), a wide area network (WAN) and / or a global area network (GAN). The network 150 can provide wired, wireless or a combination of wired and wireless communication between devices in the network. In one embodiment, the network 150 includes the Internet. In general, the representation generation engine device 300 is configured to communicate information or instructions with the entity system 200 and / or the computing device system 400 through the network 150. Although the entity system 200, the representation generation engine device 300, the computing device system 400 and the implementation controller device 120 are shown as separate components communicating via the network 150, one or more components discussed herein may be implemented via the same system (for example, a single system may include the entity system 200 and the representation generation engine device 300).

[0070] The computing device system 400 may be a system owned or controlled by an entity of the entity system 200 and / or the user 110. As such, the computing device system 400 may be a computing device of the user 110. Generally speaking, the computing device system 400 communicates with the user 110 via a user interface of the computing device system 400, and is further configured to communicate information or instructions with the representation generation engine device 300 and / or the entity system 200 via the network 150.

[0071] The implementation controller device 120 can be a system owned or controlled by an entity of the entity system 200. The implementation controller is configured to debug the physical power system structure based on the power system structure representation. The implementation controller device 120 can receive information related to one or more element icons in the power system structure representation (e.g., attribute values ​​from an attribute table corresponding to a given element icon). The implementation controller device 120 can be configured to automatically generate codes for physical elements associated with the element icons in the power system structure representation. Based on known information related to the physical elements, the implementation controller device 120 can generate codes for the operational functions of the physical power system structure (when constructed). As described below, the system can be configured to generate operational codes for the power system structure, and in some cases, once the power system structure is constructed, allow users to download operational codes for the power system structure. Therefore, since programming is not required to debug the power system structure, the implementation time of the power system structure is reduced.

[0072] Figure 2 A block diagram illustrating a physical system 200 in more detail according to an embodiment of the present disclosure is provided. Figure 2 As shown, in one embodiment, the entity system 200 includes one or more processing devices 220, which are operably coupled to the network communication interface 210 and the memory device 230. In some embodiments, the entity system 200 is operated by a first entity (such as a financial institution). In some embodiments, the entity system 200 can be a multi-tenant cluster storage system.

[0073] It should be understood that the memory device 230 may include one or more databases or other data structures / repositories. The memory device 230 also includes computer executable program code that instructs the processing device 220 to operate the network communication interface 210 to perform certain communication functions of the entity system 200 described herein. For example, in one embodiment of the entity system 200, the memory device 230 includes, but is not limited to, a representation generation engine application 250, one or more entity applications 270, and a data repository 280 including data accessed, retrieved, and / or calculated by the entity system 200. The one or more entity applications 270 can be any application developed, supported, maintained, utilized, and / or controlled by the entity. The network server application 240, the representation generation engine application 250, the computer executable program code of the one or more entity applications 270 perform certain logic, data extraction and data storage functions of the entity system 200 described herein, and the communication functions of the entity system 200.

[0074] The network server application 240, the representation generation engine application 250, and the one or more entity applications 270 are configured to store data in the data repository 280, or use the data stored in the data repository 280 when communicating with the representation generation engine device 300 and / or the computing device system 400 through the network communication interface 210 to perform one or more process steps described herein. In some embodiments, the entity system 200 can receive instructions from the representation generation engine device 300 via the representation generation engine application 250 to perform certain operations. The representation generation engine application 250 can be provided by the representation generation engine device 300. One or more entity applications 270 can be any application used, created, modified, promoted and / or managed by the entity system 200. The representation generation engine application 250 can communicate with the representation generation engine device 300. In some embodiments, parts of the methods discussed herein can be performed by the entity system 200.

[0075] Figure 3 A block diagram illustrating a representation generation engine device 300 in more detail according to various embodiments is provided. Figure 3As shown, in one embodiment, the representation generation engine device 300 includes one or more processing devices 320, which are operably coupled to the network communication interface 310 and the memory device 330. In some embodiments, the representation generation engine device 300 is operated by an entity. In some embodiments, the representation generation engine device 300 is owned or operated by an entity of the entity system 200. In some embodiments, the representation generation engine device 300 can be an independent system. In an alternative embodiment, the representation generation engine device 300 can be a part of the entity system 200. The representation generation engine device 300 can be configured to generate the power system structure representation discussed herein. That is, the representation generation engine device 300 can be configured to determine the interconnections between the various component icons (e.g., how the component icons interact, which icons are generating, using and / or storing power within the system).

[0076] It should be understood that the memory device 330 may include one or more databases or other data structures / repositories. The memory device 330 also includes computer executable program code that instructs the processing device 320 to operate the network communication interface 310 to perform certain communication functions of the representation generation engine device 300 described herein. For example, in one embodiment of the representation generation engine device 300, the memory device 330 includes, but is not limited to, a network provisioning application 340, a data collection application 350, an artificial intelligence engine 370, a representation generation engine executor 380, and a data repository 390, which includes any data processed or accessed by one or more applications in the memory device 330. The computer executable program code of the network provisioning application 340, the data collection application 350, the artificial intelligence engine 370, and the representation generation engine executor 380 can instruct the processing device 320 to perform certain logic, data processing, and data storage functions of the representation generation engine device 300 described herein, as well as the communication functions of the representation generation engine device 300.

[0077] The network supply application 340, the data collection application 350, the artificial intelligence engine 370, and the representation generation engine executor 380 are configured to call or use the data in the data repository 390 when communicating with the entity system 200 and / or the computing device system 400 through the network communication interface 310. In some embodiments, the network supply application 340, the data collection application 350, the artificial intelligence engine 370, and the representation generation engine executor 380 can store the data extracted or received from the entity system 200 and the computing device system 400 in the data repository 390. In some embodiments, the network supply application 340, the data collection application 350, the artificial intelligence engine 370, and the representation generation engine executor 380 can be part of a single application.

[0078] Figure 4A more detailed description of various embodiments is provided. Figure 1 400. However, it should be understood that a mobile phone is merely an example of one type of computing device system 400 that may benefit from, employ, or otherwise relate to embodiments of the present disclosure, and therefore should not be used to limit the scope of embodiments of the present disclosure. Other types of computing devices may include portable digital assistants (PDAs), pagers, mobile televisions, electronic media devices, desktop computers, workstations, laptops, cameras, video recorders, audio / video players, radios, GPS devices, wearable devices, Internet of Things devices, augmented reality devices, virtual reality devices, automated teller machines (ATM) devices, electronic kiosk devices, or any combination of the above.

[0079] Some embodiments of the computing device system 400 include a processor 410, which is communicatively coupled to devices such as memory 420, user output devices 436, user input devices 440, network interfaces 460, power supplies 415, clocks or other timers 450, cameras 480, and positioning system devices 475. The processor 410, as well as other processors described herein, generally includes circuits for implementing the communication and / or logic functions of the computing device system 400. For example, the processor 410 may include a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and / or other supporting circuits. The control and signal processing functions of the computing device system 400 are allocated between these devices based on their respective capabilities. Therefore, the processor 410 may also include the function of encoding and interleaving messages and data before modulation and transmission. The processor 410 may additionally include an internal data modem. In addition, the processor 410 may include the function of operating one or more software programs, which may be stored in the memory 420. For example, the processor 410 is capable of operating a connection program (e.g., a web browser application 422). The web browser application 422 may then allow the computing device system 400 to send and receive web content (eg, location-based content and / or other web page content) based on the Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), or the like.

[0080] The processor 410 is configured to communicate with one or more other devices on the network 150 using the network interface 460. In this regard, the network interface 460 includes an antenna 476, which is operably coupled to a transmitter 474 and a receiver 472 (collectively referred to as a "transceiver"). The processor 410 is configured to provide signals to the transmitter 474 and the receiver 472 and receive signals therefrom, respectively. The signal may include signaling information based on the air interface standard of the applicable cellular system of the wireless network 150. In this regard, the computing device system 400 can be configured to operate using one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the computing device system 400 can be configured to operate based on any one of a plurality of first generation, second generation, third generation, and / or fourth generation communication protocols, etc.

[0081] As described above, computing device system 400 has a user interface that, like other user interfaces described herein, consists of user output devices 436 and / or user input devices 440. User output devices 436 include one or more displays 430 (e.g., liquid crystal displays, etc.) and speakers 432 or other audio devices that are operably coupled to processor 410. The user interface may be used to present a power system structure representation as discussed herein.

[0082] The user input device 440 that allows the computing device system 400 to receive data from a user (e.g., user 110) may include any of a variety of devices that allow the computing device system 400 to receive data from the user 110, such as keys, keyboards, touch screens, touch pads, microphones, mice, joysticks, other pointer devices, buttons, soft keys, and / or other input devices. The user interface may also include a camera 480 (e.g., a digital camera).

[0083] The computing device system 400 may also include a positioning system device 475, which is configured to be used by the positioning system to determine the location of the computing device system 400. For example, the positioning system device 475 may include a GPS transceiver. In some embodiments, the positioning system device 475 is at least partially composed of the above-mentioned antenna 476, transmitter 474 and receiver 472. For example, in one embodiment, triangulation of mobile signals can be used to identify the approximate or precise geographic location of the computing device system 400. In other embodiments, the positioning system device 475 includes a proximity sensor or transmitter, such as a radio frequency identification (RFID) tag, which can sense or be sensed by devices known to be located near a merchant or other location to determine that the computing device system 400 is located near these known devices.

[0084] The computing device system 400 also includes a power source 415 (e.g., a battery) for powering various circuits and other devices used to operate the computing device system 400. Embodiments of the computing device system 400 may also include a clock or other timer 450 that is configured to determine actual or relative time and, in some cases, communicate the actual or relative time to the processor 410 or one or more other devices.

[0085] The computing device system 400 also includes a memory 420, which is operably coupled to the processor 410. As used herein, a memory includes any computer-readable medium (as defined below) configured to store data, code, or other information. The memory 420 may include a volatile memory, such as a volatile random access memory (RAM), which includes a cache area for temporarily storing data. The memory 420 may also include a non-volatile memory, which may be embedded and / or removable. The non-volatile memory may additionally or alternatively include an electrically erasable programmable read-only memory (EEPROM), flash memory, and the like.

[0086] The memory 420 may store any of a variety of applications, including computer executable instructions / codes executed by the processor 410 to implement the functions of the computing device system 400 and / or one or more process / method steps described herein. For example, the memory 420 may include applications such as a conventional web browser application 422, a representation generation engine application 421, and an entity application 424. These applications also typically indicate a graphical user interface (GUI) on the display 430, which allows the user 110 to interact with the entity system 200, the representation generation engine device 300, and / or other devices or systems. The memory 420 of the computing device system 400 may include a Short Message Service (SMS) application 423, which is configured to send, receive, and store data, information, communications, alerts, etc. via the wireless network 150. In some embodiments, the representation generation engine application 421 provided by the representation generation engine device 300 allows the user 110 to access the representation generation engine device 300. In some embodiments, the entity application 424 and the representation generation engine application 421 provided by the entity system 200 allow the user 110 to access functionality provided by the representation generation engine device 300 and the entity system 200 .

[0087] Memory 420 may also store any of a variety of information and data used by computing device system 400 and applications and devices making up or communicating with computing device system 400 to implement the functionality of computing device system 400 and / or other systems described herein.

[0088] Reference now Figure 5 , a method for performing creation of a schematic diagram of a power system structure (e.g., a distributed power system structure) according to an example embodiment is provided. The power system structure may include loads, generation, storage devices, power conversion elements, and / or other components of the power system structure. Creating a schematic diagram is a time-consuming and labor-intensive task, and through the presented method, the present disclosure accelerates and organizes the process of creating a schematic diagram. The method may be embodied as a computer program executed by a desktop computer or a mobile device (e.g., computing device 400).

[0089] Figure 6 A complete example power system structure representation is shown. As shown, there are multiple component cells (e.g., nine cells are shown, with cell 202 in the middle). Each component cell can have a component icon (e.g., asset 610) assigned therein. Each component icon corresponds to a physical element that can be used in the power system structure. The element is then connected to other component icons in other component cells using a visual representation of the connection of the physical element corresponding to a given component icon.

[0090] Reference now Figure 5 At block 500, the method may include creating a two-dimensional spatial array associated with a power system structure representation. Figure 7 As shown, the spatial array can be configured as a grid 201. The grid can be a two-dimensional spatial array of rows and columns of element units. The spatial array can be presented on a user interface of a user device (e.g., computing device 400). Each element unit is a unique location on the grid, which can be identified and referenced by the row number and column number of the unit, and has left, right, top, and bottom boundaries. For example, element unit 702 is located in the second row and second column of the power system structure representation. The number of rows and columns of the power system structure representation exceeds 1 and can be non-binding. The grid 701 of the power system structure representation can be used in various embodiments discussed herein.

[0091] Reference Figure 5 At block 510, the method may include adding a first component icon to the first component unit. Figure 8A-8C As shown, a first component icon 800 may be assigned to a given component unit 702. Fig. 8A, the first component icon 800 is a schematic representation of a physical component (e.g., an asset or link in a schematic). The physical component can be a load, a generator, a storage device, a power conversion device, a link representing an electrical connection, etc. The schematic representation of the component icon is confined within the boundaries of the component unit 702. Each component unit (e.g., component unit 702) can each contain at most one component icon. The component icon 800 may include a label 705, a symbol 706, and a first port at the top, wherein the first port includes a terminal 701. Optionally, the component icon may include an auxiliary terminal 704. As shown Figure 8B As shown, the component icon 800 may also include a second port at the bottom, which includes a terminal 703. Figure 3 (c), the embodiment of the entity optionally includes a third port on the left, the third port including terminal 703. Each of terminal 701, auxiliary terminal 704 and terminal 703 can connect the component icon to another component icon in another component unit.

[0092] A component icon can be one of multiple subcategories. For example, a component icon can be one of four subcategories. Fig. 9 As shown, an example component icon subclass may be a generator component icon 900 (e.g., corresponding to a generator physical component). As shown, the terminal 701 has an upward indication of the current flow direction 901 outside of the symbol 706, which indicates that the generator component icon 900 generates power for the power system structure (e.g., current flows out of the generator component icon 900).

[0093] like Fig.10 As shown, another example component icon subclass can be a storage component icon 1000 (corresponding to a storage device physical component). As shown, terminal 701 has a bidirectional current flow direction 1001 from symbol 706, which indicates that current can flow into and out of storage component icon 1000 (e.g., a storage device physical component stores and transmits power).

[0094] like Fig.11 As shown, another example component icon subclass may be a load component icon 1100 (corresponding to a load physical component). As shown, terminal 701 has a current direction 1101 into symbol 706, indicating that current may flow into load component icon 1100 (eg, the load physical component consumes power).

[0095] like Fig.12As shown, another example component icon subclass can be a converter component icon 1200 (corresponding to a converter physical component). The converter component icon 1200 can include a terminal 701 and a terminal 703. Thus, the converter can convert alternating current (AC) current into direct current (DC) current. For example, AC current can be received by the converter via terminal 701, then converted into DC current, and output to the power system structure via terminal 703. The component icons shown herein are merely illustrative and can include different configurations based on the design.

[0096] Reference now Figure 5 At block 520, the method includes generating a first attribute table associated with the first component icon. Fig.13 As shown, attribute table 1301 is associated with first component icon 800. First attribute table 1302 can be stored in a storage medium (e.g., physical device 200 and / or other components). Attribute table is a table containing attribute fields and related attribute values. Attribute field is a description of the physical characteristics of the physical component associated with the first component icon. Attribute value is the value of the attribute field. Examples of attribute fields include number of connections, rated voltage, rated current, rated power, etc. Each component icon can have an attribute table.

[0097] Reference Figure 5 In block 530, the method further includes adding a second component icon to the second component unit. Adding the second component icon to the second component unit may be the same or similar to adding the first component icon to the first component unit. Figure 5 At block 540, the method may also include generating a second attribute table associated with the second component icon. As discussed herein, the second attribute table may be generated in a manner similar to the first attribute table.

[0098] In some embodiments, one or more attribute values ​​of the second attribute table may be based on one or more attribute values ​​of the first attribute table. Figure 5 In block 550, the method includes calculating attribute values ​​of a second attribute table based on one or more attribute values ​​in the first attribute table. The attribute values ​​of the second attribute table may be calculated based on the attribute values ​​of the first attribute table. For example, the attribute values ​​of the second attribute table may be a function of the number of connections of the first port or the second port of the second component icon compared to the number of connections of the first port or the second port of the first component icon, the line color of the terminals of each component icon, a comparison of the attribute values ​​of the second attribute table with the attribute values ​​of the first attribute table, etc. The calculation of the attribute values ​​may also be based on a manufacturer comparison between a physical component associated with the first component icon and a physical component associated with the second component icon.

[0099] In some cases, the attribute table of each component icon may include layer attributes. For example, an attribute field of a given attribute table may include one of three attribute values ​​corresponding to a given layer (e.g., 0 (asset layer), 1 (converter layer), 2 (switchgear layer)). Figure 5 In the frame 510 of FIG. 8 , in drawing the first entity, the component icon 800 is drawn only when the attribute value of the first attribute field is greater than or equal to the attribute value of the second attribute field. Figure 5 In block 530 , in drawing the second entity, the second entity may be drawn only when the attribute value of the first attribute field is greater than or equal to the attribute value of the third attribute field.

[0100] Figure 14-16 1 is a diagram showing various example power system structures that can be generated using various embodiments of the present disclosure. As shown, component icons can be connected to each other to indicate the flow of current. Fig.14 shows the basic diagram, while Fig.15 A more complex diagram is shown, which includes component icon information, such as load, capacity, etc. Fig.16 Suggestions for component characteristics are also provided, along with estimated cost 1600 , load, and generated power values ​​1610 .

[0101] Fig.17 An example method for dynamically generating a power system structure representation is shown. The power system structure representation may be a schematic diagram. The power system structure may be a digital representation of a potential power system structure. Thus, the power system structure representation may be used to plan and construct a power system structure. Unless otherwise specified, Fig.17 The methods may include those discussed above. Figure 6 The method may be performed by the system discussed herein (e.g., entity system 200, representation generation engine device 300, implementation controller device 120, and / or computing device system 400). The example system may include at least one non-transitory storage device and at least one processing device coupled to the at least one non-transitory storage device. In such an embodiment, at least one processing device is configured to perform the method discussed herein.

[0102] Reference Fig.17In block 1700, the method includes providing one or more component icons that can be added to the power system structure representation. The method includes causing rendering of a user interface (e.g., provided to a computing device system 400 associated with a user 110). The user interface includes one or more component icons that can be selected by a user device. Each of the one or more component icons represents a physical element that can be used in the power system structure. Therefore, the user device can select multiple component icons. The physical element can include, for example, a load, a generator, a storage device, and / or a power conversion device. The component icon can include information about a given physical element, such as a component name, a charge, etc.

[0103] Reference Fig.17 Optional block 1710 of the method includes storing an attribute table for each of the one or more component icons. Each component icon may have an attribute table that includes information related to the physical component represented by the component icon. The attribute table may include attribute fields and attribute values ​​(as described above with reference to Fig.13 The attribute field is a description of the physical component, such as the component name, part number, and / or other identifier. The attribute value includes information related to the performance of the physical component, such as power capacity, power load, installation cost, and operating cost. Each physical component can have multiple attribute values.

[0104] The attribute table can be generated manually (e.g., an operator can manually enter values ​​into the attribute table). The attribute table can be generated by a third party. For example, a supplier or manufacturer of a given physical element can provide the information used in the attribute table. In some cases, the system can generate the attribute table based on the information provided by the third party. In some cases, a third-party supplier can provide the attribute table (e.g., a third-party supplier can generate an attribute table specifically for the system of this article). Additionally or alternatively, the attribute table can be automatically generated. The attribute values ​​of the attribute table can be determined based on information related to the physical element. For example, the system can be configured to generate the attribute table based on the technical specifications of a given physical element.

[0105] Reference Fig.17In box 1720, the method includes receiving an indication of a first component icon from one or more component icons for a power system structure. The system can receive input from a user via computing device 400 to use a given component icon in the power system structure representation. The user's input can be clicking and / or dragging the component icon. For example, a user can drag the component icon from a screen portion containing one or more component icons to a user interface portion containing the power system structure representation. In some cases, the indication can include a desired position of the first component icon in the power system structure representation (for example, a user can drag the first component icon to a specific position on the power system structure representation). In some cases, the system can be configured to automatically place the selected first component icon into the power system structure representation based on the positioning of one or more other icon elements on the power system structure representation.

[0106] Reference now Fig.17 In box 1730, the method includes assigning a first component icon to one of a plurality of component units of the power system structure representation. Based on the indication of the first component icon, the system is configured to assign the first component icon to one of the component units of the power system structure representation. Each component unit contains only a single component icon. As described above, the indication of the first component icon may include the positioning of the first component icon in the power system structure representation. Subsequent selected component icons can be assigned to the unit in the same manner as the first component icon. The power system structure representation allows dynamic changes via a user interface. For example, a user can move one of the component icons from one component unit to another. As will be discussed in more detail below with reference to box 1740, the system is configured to update the unit action of the moved component icon.

[0107] Reference now Fig.17 In block 1740 of the method, the method includes determining a unit action configured to indicate a relationship between a unit to which a first component icon is assigned and at least another unit of a plurality of component units of a power system structure. The unit action determines an interaction between different units in the representation of the power system structure. For example, the unit action of the first selected icon is a connection type between the selected first component icon and a second component icon assigned to another unit of the plurality of component units, and the connection type indicates how physical components associated with the first component icon and the second component icon are connected to each other in the power system structure.

[0108] Refer to the above FIG. 8A to FIG. 13, examples of connections between units are shown and discussed. The unit action is determined based on at least one of an attribute table of a first element icon or an attribute table of a second element icon assigned to another unit in a plurality of element units. The attribute table may include compatibility information for the physical elements, and the compatibility information may be used to determine how and / or whether two physical elements may successfully operate in a power system structure. For example, a load may require a particular amount of power to operate, so the system determines whether a power source (e.g., a battery) should be connected to the load in order to operate the load.

[0109] Reference Fig.17 In block 1750 of the method, the method includes determining at least one power system structure value indicating an operating efficiency of the power system structure. The system may also be configured to determine information about the power system structure. The power system structure value may include a cost of building the power system structure, a cost of operating the power system structure, or a system load of the power system structure. The power system structure value may be an estimate of a performance indicator of the power system structure in the power system structure representation. The power system structure value may be presented on a user interface. The power system structure value may be based on one or more attribute values ​​in an attribute table associated with a physical element in the power system structure. For example, each attribute table may include installation cost, operating cost, operating load, and / or other various characteristics that may be used to determine a system-wide performance indicator.

[0110] In addition, the method may include providing one or more additional platform tools that assist in building the power system structure represented by the power system structure representation. The platform tool can connect the user to one or more suppliers of physical elements in the power system structure representation. The user interface may have an optional icon with information about how to purchase the physical element associated with a given element icon. In addition, the user interface may provide a cost estimate based on real-time or near real-time pricing (e.g., the price provided by the supplier can be displayed on the user interface and / or used by the system to determine the cost estimate of the power system structure). The platform may be configured to facilitate the purchase of one or more components from the supplier within the platform. Additionally or optionally, the system may provide supplier information to the user so that the user can then contact the supplier to purchase the component.

[0111] The platform tool may also include providing information for one or more contractors who are capable of building at least a portion of the power system structure. For example, the system may store one or more contractors who are capable of performing one or more necessary installations. The system may be configured to recommend one or more contractors based on various user characteristics (e.g., location). For example, the system may recommend contractors that serve the area where the user plans to build the power system structure. The system may use various considerations (e.g., contractor grade, type of work, and contractor availability, etc.) to determine which contractor(s) to recommend. Recommendations of one or more contractors may be provided to the user on a user interface. In some cases, the contractor recommendation may include contact information that allows the user to contact the contractor. In some embodiments, the system may also be configured to facilitate communication between the contractor and the user (e.g., consumer). For example, the contractor may have an account in which the contractor may communicate with potential consumers.

[0112] In some embodiments, the system may also be configured to automatically generate operation codes for the power system structure based on the power system structure representation. For example, the implementation controller device 120 may be configured to generate operation codes that may be used to debug the physical power system structure based on the power system structure representation. The implementation controller device 120 may receive information related to one or more element icons in the power system structure representation (e.g., attribute values ​​from an attribute table corresponding to a given element icon). Since the power system structure representation includes element icons associated with physical elements, the attribute values ​​of the physical elements may be used to generate the necessary operation codes.

[0113] For example, batteries from different manufacturers may have slightly different operations, thus requiring different operation codes to account for any variations. Because component icons are associated with specific physical components, the attribute tables associated with the component icons may include information that can be used to generate operation codes for the physical components of the power system structure. Using the attribute tables for each component icon in the power system structure representation, the implementation device controller 120 can generate the operation codes required to debug the power system structure (e.g., the operation codes are sufficient to cause the physical components of the power system structure to operate in a desired manner).

[0114] The automatically generated operating code can be downloaded by the user for use once the power system structure is constructed. For example, the user interface can have a selectable icon that allows the user to download the operating code of the controller (e.g., the icon can read "Download Controller"). In addition, the implementation controller device 120 can be installed directly into the power system structure. For example, the implementation controller device 120 can communicate with the power system structure and provide the operating code therein. In some cases, the user can download the operating code from the system to another controller device used in the power system structure. Therefore, since no programming is required to debug the power system structure, the implementation time of the power system structure is reduced. As shown below with reference to Fig.19 and 20 As discussed, the operational code may also be referred to as "controller runtime code" or "runtime code".

[0115] In addition, the system can remotely test and debug the power system structure after completion. For example, the implementation controller device 120 can be configured to automatically test the power system structure when installed. The results of the automated testing can be compared with the estimated power system structure values ​​determined by the system. In addition, reports based on the testing can be automatically provided to support engineers to allow them to adjust or change the power system structure to achieve the desired performance.

[0116] Fig.18 An example power system structure according to an embodiment of the present disclosure is shown, which includes an implementation controller device for commissioning and / or operating the power system structure. As shown, an implementation controller device 120 ("controller 120") can be connected to one or more physical elements, such as an energy storage device (e.g., battery 1800), a solar array 1810, a power conversion system 1820, a relay 1830, a circuit breaker panel 1840, a grounding transformer 1850, and a utility grid 1860. The controller 120 is configured to control the operation of each physical element (e.g., manage the interaction between the solar array 1810 / battery 1800 and the rest of the utility grid 1860. The controller 120 can be configured to be remotely deployed and commissioned using the various operations discussed herein.

[0117] Fig.18The power system structure shown is only an example power system structure in which the controller discussed in this article can be used. Various power system structures may include different physical elements, such as loads, generators, storage devices, and / or power conversion devices. In addition, physical elements of different brands or models may be different, so each component can enable the controller 120 to be updated to operate effectively. During initial commissioning, a power system structure with a traditional controller must be manually debugged by a field programmer, which is time-consuming and expensive because system commissioning may take weeks. However, the controller 120 of various embodiments allows remote debugging because the controller runtime code is pre-generated (e.g., by the method discussed in this article). In addition, the controller 120 allows real-time tracking and power management, which can be used to improve the efficiency of the power system structure.

[0118] Fig.19 The structure of the runtime code received by the controller according to an embodiment of the present disclosure is shown. As shown, the runtime code may include information related to real-time runtime operations 1900 and non-real-time runtime operations 1950. Real-time runtime operations 1900 may include code and / or information related to algorithms 1910, commands 1920, communications with a communication interface 1930, and physical elements 1940 of the power system structure.

[0119] Algorithm 1910 may be used to determine various power system structure desired variables, such as desired / recommended voltage control, desired / recommended current control, and / or desired / recommended power control. The algorithm may use machine learning to determine the desired / recommended voltage control, desired / recommended current control, and / or desired / recommended power control. Commands 1920 may include the necessary code to perform initialization of the power system structure, stop and / or start the power system structure, reset the power system structure, and / or check for errors in the power system structure.

[0120] The communication interface information 1930 may include information and / or code for communicating with a communication interface. The communication interface information 1930 may use various communication protocols, such as Modbus RTU, Modbus TCP / IP, and / or CANbus. The communication interface information allows the controller 120 to communicate with various communication interfaces.

[0121] Real-time runtime operations associated with physical elements 1940 may include information and / or code associated with specific physical elements of a given power system structure. Physical elements may include, for example, energy storage devices, generators, and / or power conversion devices. Runtime code may vary specifically based on the specific physical elements of the power system structure.

[0122] The runtime code may also include real-time runtime operations 1950. Real-time runtime operations 1950 may include information and / or code related to automatic testing 1960, sending alarm messages 1970, remote monitoring 1980, and / or energy management 1990. Automated testing may include standard testing and / or predetermined testing. Automated testing may include initial testing, which is completed during and / or after commissioning, startup and / or shutdown testing, safety testing, and / or charge / discharge testing.

[0123] Information associated with the transmission of the alarm message 1970 may include sending field bit information about system operation, critical error information, and / or event logs to one or more users when a problem is determined. The alarm message may be the result of automated testing 1960 and / or remote monitoring 1980. Remote monitoring information 1980 includes instructions for monitoring the power system structure, such as monitoring performance, efficiency, and / or specific events (e.g., faults). Remote monitoring information 1980 may be used in conjunction with an energy management system 1990. The energy management system 1990 may include optimized operating variables. The energy management system 1990 may also be configured to send measurement data associated with the power system structure and / or receive operating variables of the power system structure. The runtime code may be stored in one or more files 1995. The runtime code may be stored as a JSON (a lightweight data exchange format based on the JavaScript language (JavaScript Object Notation)) file. The JSON file may then be transmitted to the controller 120 for reference below. Fig. 20 Use in the manner discussed.

[0124] The runtime code may include multiple files (e.g., multiple JSON files, etc.). For example, the runtime code may include one or more device configuration files (e.g., device JSON files) that list all physical elements present in the power system structure. Such a device configuration file may include references to other files, such as a control configuration file and / or an address mapping file.

[0125] The runtime code may also include one or more control configuration files (e.g., control JSON files) that include specific commands linked to a sequence of communication registers and values ​​to be sent within the power system structure. The specific commands are based on specific physical elements of the power system structure. Each individual physical element may have a separate control configuration file (e.g., each different type of physical element in the power system structure may have a control configuration file with specific commands for a given physical element).

[0126] The runtime code may also include one or more address mapping files that contain specific communication registers of the physical element. Each physical element may have a separate address mapping file. The runtime code may include various other files for debugging and / or operating the power system structure. The runtime code is configured based on a specific power system structure (e.g., when configuring a power system structure as discussed herein, the runtime code may be generated based on the physical elements of the power system structure).

[0127] Fig. 20 A flow chart showing a method of commissioning and / or operating a power system structure. The power system structure may be composed of Fig.17 The method may be performed by the controller 120 discussed herein. The example controller 120 may include at least one non-transitory storage device and at least one processing device coupled to the at least one non-transitory storage device. In such an embodiment, the at least one processing device is configured to perform the method discussed herein.

[0128] Reference Fig. 20 In block 2000, the method may include receiving a controller runtime code of the power system structure. The controller runtime code may be the controller runtime code described above with reference to Fig.19 Various instructions and information discussed herein. Controller runtime code can be generated using the system discussed herein. Controller runtime code is specifically designed to operate a power system structure.

[0129] The method may include generating a configuration of the power system structure. Using the systems and methods discussed herein, for example, referring to Figure 5 and Fig.17 The discussed method can generate various configurations of power system structures. Based on the power system structure system, the controller runtime code can be specifically configured to operate the power system structure. Therefore, the controller runtime code can be customized to operate the specific power system structure generated. The controller runtime code can also be updated based on any changes in the power system structure configuration.

[0130] The controller runtime code is configured to effectively operate the power system structure based on the physical elements of the power system structure. For example, a given power system structure may have a storage device that is a battery provided by a first supplier that is different from another battery provided by a second supplier. Therefore, the controller runtime code must take into account the specific characteristics of each physical element. The operations discussed herein allow the controller runtime code to be received by the controller (e.g., after being generated as described above) and implemented without any additional programming of the individual physical elements. The controller runtime code can be received via a wireless network (e.g., network 150).

[0131] Reference Fig. 20 At block 2010, the method may include automatically deploying controller runtime code on the controller. The controller 120 is configured to operate multiple power system structures by receiving the controller runtime code for a given power system structure. Thus, the controller 120 may have one or more base features that are consistent across any power system structure. The controller runtime code may then provide adjustments to the common structure, and the controller 120 may quickly and easily implement the controller runtime code.

[0132] Reference now Fig. 20 At block 220, the method may include debugging the power system structure using the deployed controller runtime code. The power system structure may be debugged remotely using the controller 120. Since the controller runtime code is designed for a specific power system structure, the controller 120, after automatically deploying the controller runtime code, may now operate the power system structure without any additional updates.

[0133] During and / or after commissioning of the power structure, the controller 120 may monitor the operation of the power structure to determine whether the power structure is operating as expected. For example, the controller 120 may confirm that expected physical elements are connected to the power structure before fully commissioning the power structure system and determine whether there are any unexpected physical elements in the power structure system. Any unexpected results may cause the controller 120 to cause an alarm message to be transmitted, as described below with reference to Fig. 20 In addition, the controller 120 may take other actions, such as delaying or canceling the commissioning if unexpected results are obtained.

[0134] As referenced below Fig. 20 As discussed in block 2040 of , the controller 120 may monitor the power system structure operation at the physical element level and / or the entire power system structure level to identify any potential problems. Based on the controller runtime code, the monitored variables may be compared to one or more expected values. For example, as described herein, in the case of generating a power system structure schematic, various expected variables may also be generated, such as expected power output / input, expected rated voltage, expected rated current, etc. The actual readings of the various monitored variables may be compared to the expected variables to identify any problems with the power system structure. For example, a power reading that is higher or lower than the expected power reading may indicate: a difference between a digital representation of the power system structure and the physical power system structure, or a problem with one or more physical elements of the power system structure (e.g., a battery may fail and cause a problem).

[0135] See now Fig. 20Optional block 2030 of the method may include: receiving an update to the controller runtime code based on a change in the power system structure. Whenever a physical element is replaced with a different physical element, the controller runtime code may be updated to account for the change. The user and / or system may update the power system representation with any changes to the power system structure (e.g., in the case where battery A is replaced with battery B in the power system structure, the element icon associated with battery A may be replaced within the element icon associated with battery B). The controller 120 may automatically identify changes to the physical element (e.g., the controller 120 may determine that the replacement physical element is different from the original physical element).

[0136] The controller runtime code may be updated based on changes to the power system structure. The system (e.g., representation generation engine 300, entity system 200, and / or controller 120) may determine whether changes to physical elements of the power system structure require changes to the controller runtime code. For example, the system may compare one or more properties of the original physical element and the replacement physical element to determine any differences in the properties. In the example of a property mismatch, the controller runtime code may be updated. The update to the controller runtime code may be received by the controller 120 and updated as described above with reference to the original controller runtime code (e.g., Fig. 20 The updated controller runtime code may replace the original controller runtime code, such that the controller 120 installs the controller runtime code in place of the original controller runtime code.

[0137] Reference now Fig. 20 At optional block 2040, the method may include monitoring one or more variables of at least one physical element of the power system structure and / or one or more variables of the power system structure. The controller 120 may monitor one or more variables of the entire power system structure (e.g., power consumption, voltage level, current level, operating efficiency, etc.). Additionally or alternatively, the controller may monitor one or more variables of a single physical element. For example, the controller 120 may monitor the power output of a generator.

[0138] Based on the controller runtime code, the monitored variables can be compared to one or more expected values. For example, as described herein, in the example of generating a schematic diagram of a power system structure, various expected variables, such as expected power output / input, expected rated voltage, expected rated current, etc., can also be generated. The actual readings of the various monitored variables can be compared to the expected variables to identify any problems with the power system structure. For example, a power reading that is higher or lower than the expected power reading can indicate: a difference between a digital representation of the power system structure and the physical power system structure, or a problem with one or more physical elements of the power system structure (e.g., a battery may fail and cause a problem).

[0139] The controller 120 is configured to allow near real-time monitoring. This monitoring allows any problems in the power system structure to be identified early. The controller 120 can monitor the various variables described above in near real time. For example, the controller 120 can track power consumption in real time. The variable values ​​monitored in real time or near real time can be compared with previously monitored variable values. For example, some monitored variables may remain approximately constant, and changes in the monitored variables indicate potential system failures. In another example, the monitored variables may be predictable (for example, the power consumption of the power system structure may be higher at certain times of the day or season), and the monitored variables can be compared with previous similar conditions.

[0140] The controller 120 is capable of remotely testing the power system structure. The remote testing of the controller 120 may include determining whether one or more physical elements are operating correctly, performing initial runtime tests to confirm whether the system is operating as expected, safety testing, startup and / or shutdown testing, etc. The configuration of the controller 120 allows remote testing to be completed without sending workers to inspect the power system structure. The controller 120 can analyze and / or transmit the results of the remote testing to identify any potential problems with the power system structure.

[0141] Reference now Fig. 20 At optional block 2050, the method may include causing transmission of an alarm message based on a change in at least one of the one or more monitored variables of the power system structure. The alarm message may indicate a potential fault in the power system structure. The alarm message may be transmitted to one or more programmers and / or operators of the power system structure. For example, the alarm message may be sent in the form of a notification to a manager of the power system structure.

[0142] In some embodiments, the controller 120 may be configured to determine one or more alarm actions. The alarm action may identify the type of potential fault and determine one or more changes to the power system structure. For example, the controller 120 may determine that one or more physical elements are not communicating properly within the controller 120, and therefore the physical elements need to be updated, repaired, and / or replaced. The controller 120 may also analyze the power system structure to identify any specific problems in the power system structure (e.g., one or more physical elements are not providing the expected energy output) and determine potential changes to address the problem.

[0143] As will be appreciated by those skilled in the art, the present disclosure may be embodied as a method (including, for example, a computer-implemented process, a business process, and / or any other process), an apparatus (including, for example, a system, a machine, a device, a computer program product, etc.), or a combination of the foregoing. Thus, embodiments of the present disclosure may take the form of a fully hardware embodiment, a fully software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which are generally referred to herein as a "system." In addition, embodiments of the present disclosure may take the form of a computer program product on a computer-readable medium having computer executable program code contained in the medium.

[0144] Any suitable transient or non-transient computer-readable medium may be utilized. The computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus. More specific examples of computer-readable media include, but are not limited to: an electrical connection having one or more conductors; a tangible storage medium such as a portable computer disk, hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), compact disc read-only memory (CD-ROM), or other optical or magnetic storage devices.

[0145] In the context of this document, a computer readable medium may be any medium that can contain, store, communicate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. Computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, fiber optic cable, radio frequency (RF) signal, or other medium.

[0146] The computer executable program code for performing operations of the embodiments of the present disclosure may be written in an object-oriented scripting or scriptless programming language, such as Java, Perl, Smalltalk, C++, etc. However, the computer program code for performing operations of the embodiments of the present disclosure may also be written in a conventional procedural programming language, such as the "C" programming language or a similar programming language.

[0147] The above reference method, device (system) and computer program product flowchart and / or block diagram describe the embodiment of the present disclosure.It should be understood that each frame of the flowchart and / or block diagram and / or the combination of frames in the flowchart and / or block diagram can be implemented by computer executable program code parts.These computer executable program code parts can be provided to the processor of general-purpose computer, special-purpose computer or other programmable data processing device to produce a specific machine, so that the code part executed by the processor of the computer or other programmable data processing device creates a mechanism for implementing the function / action specified in the flowchart and / or block diagram.

[0148] These computer-executable program code portions may also be stored in a computer-readable memory, which may direct a computer or other programmable data processing device to work in a specific manner, so that the code portions stored in the computer-readable memory produce an article of manufacture, which includes an instruction mechanism for implementing the functions / actions specified in the flowchart and / or block diagram.

[0149] The computer executable program code may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be executed on the computer or other programmable device to produce a computer-implemented process, so that the code portion executed on the computer or other programmable device provides steps for implementing the functions / actions specified in the flowchart and / or block diagram. Optionally, the steps or actions implemented by the computer program may be combined with the steps or actions implemented by an operator or person to perform the embodiments of the present disclosure.

[0150] As the phrase is used herein, a processor may be "configured to" perform a particular function in a variety of ways, including, for example, by executing specific computer-executable program code contained in a computer-readable medium, causing one or more general-purpose circuits to perform the function, and / or by causing one or more special-purpose circuits to perform the function.

[0151] The embodiments of the present disclosure are described above with reference to flowcharts and / or block diagrams. It should be understood that the steps of the process described herein can be performed in an order different from that shown in the flowchart. In other words, in some embodiments, the process represented by the blocks of the flowchart can be performed in an order different from that shown, can be combined or divided, or can be performed simultaneously. It should also be understood that in some embodiments, the blocks of the block diagram only show a conceptual description between the system and one or more systems shown by the blocks in the block diagram, and can be combined or share hardware and / or software with another or more systems shown by the blocks in the block diagram. Similarly, devices, systems, devices and / or the like can be composed of one or more devices, systems, devices and / or the like. For example, in the case where a processor is shown or described herein, the processor can be composed of a plurality of microprocessors or other processing devices, which can be coupled to each other or not coupled to each other. Similarly, in the case where a memory is shown or described herein, the memory can be composed of a plurality of memory devices, which can be coupled to each other or not coupled to each other.

[0152] Although certain exemplary embodiments have been described and shown in the accompanying drawings, it should be understood that such embodiments are intended to illustrate rather than limit the broad disclosure, and the disclosure is not limited to the specific structures and arrangements shown and described, as various other variations, combinations, omissions, modifications, and substitutions are possible in addition to those described in the above paragraphs. Those skilled in the art will appreciate that various adjustments and modifications may be made to the embodiments just described without departing from the scope and spirit of the disclosure. Therefore, it should be understood that within the scope of the appended claims, the disclosure may be implemented in a manner other than that specifically described herein.

Claims

1. A controller for operating an electric power system structure, the controller comprising: at least one non-transitory storage device; as well as at least one processing device coupled to the at least one non-transitory storage device, wherein the at least one processing device is configured to: receiving a controller runtime code of a power system structure, wherein the controller runtime code is specifically designed to operate the power system structure; automatically deploying the controller runtime code on the controller; and The power system structure is debugged using the deployed controller runtime code, wherein the power system structure is debugged remotely.

2. The controller according to claim 1, wherein: The at least one processing device is further configured to receive updates to the controller runtime code based on changes to the power system architecture.

3. The controller according to claim 1, wherein: The at least one processing device is further configured to generate a configuration of the power system architecture, wherein the controller runtime code is configured based on the generated configuration.

4. The controller according to claim 1, wherein: The at least one processing device is also configured to monitor one or more variables of at least one physical element of the power system structure.

5. The controller according to claim 1, wherein: The at least one processing device is also configured to monitor one or more variables of the power system structure.

6. The controller according to claim 5, wherein: The at least one processing device is further configured to cause transmission of an alarm message based on a change in at least one of the one or more monitored variables of the power system structure.

7. The controller according to claim 1, wherein: The one or more monitored variables of the power system structure include at least one of power consumption or efficiency.

8. A computer program product for operating a power system structure via a controller, the computer program product comprising at least one non-transitory computer readable medium, the at least one non-transitory computer readable medium containing computer readable program code portions, the computer readable program code portions comprising: an executable portion configured to receive a controller runtime code of a power system structure, wherein the controller runtime code is specifically designed to operate the power system structure; configured to automatically deploy an executable portion of the controller runtime code on the controller; and An executable portion configured to debug the power system architecture using the deployed controller runtime code, wherein the power system architecture is debugged remotely.

9. The computer program product according to claim 8, wherein: The computer readable program code portion also includes an executable portion configured to receive an update of the controller runtime code based on a change in the power system configuration.

10. The computer program product of claim 8, wherein: The computer readable program code portion also includes an executable portion configured to generate a configuration of the power system architecture, wherein the controller runtime code is configured based on the generated configuration.

11. The computer program product of claim 8, wherein: The computer readable program code portion also includes an executable portion configured to monitor one or more variables of at least one physical element of the power system structure.

12. The computer program product of claim 8, wherein: The computer readable program code portion also includes an executable portion configured to monitor one or more variables of the power system structure.

13. The computer program product of claim 12, wherein: The computer readable program code portion also includes an executable portion configured to cause transmission of an alarm message based on a change in at least one of the one or more monitored variables of the power system structure.

14. The computer program product of claim 8, wherein: The one or more monitored variables of the power system structure include at least one of power consumption or efficiency.

15. A computer-implemented method of operating a power system structure via a controller, the method comprising: receiving a controller runtime code of a power system structure, wherein the controller runtime code is specifically designed to operate the power system structure; automatically deploying the controller runtime code on the controller; and The power system structure is debugged using the deployed controller runtime code, wherein the power system structure is debugged remotely. 16 . The method of claim 15 , further comprising receiving an update to the controller runtime code based on a change in the power system architecture.

17. The method of claim 15, further comprising monitoring one or more variables of at least one physical element of the power system structure.

18. The method of claim 15, further comprising generating a configuration of the power system structure, wherein: The controller runtime code is configured based on the generated configuration.

19. The method of claim 18, further comprising causing transmission of an alarm message based on a change in at least one of the one or more monitored variables of the power system structure.

20. The method according to claim 15, wherein: The one or more monitored variables of the power system structure include at least one of power consumption or efficiency.

Images