Data structures, programs, numerical management systems, and communication methods

Abstract

To provide a new numerical value management system capable of specifying meaning of a numerical value and numerical data even without any protocol specifications.SOLUTION: A numerical value management system uses a pair of logical data structures composed of a logical database constructed on a database server in which numerical data including multiple numerical values related to a time stamp are recorded, and a data identification ID for uniquely specifying the attribute of a numerical value for composing the numerical data. The data identification ID includes a unit ID comprising at least a two-byte character string prescribing a unit of the numerical data, and at least a four-byte item ID composed of an item number comprising at least a two-byte integer value for uniquely specifying a type ID after defining at least a two-byte type ID prescribing a type of the numerical data, and the type ID. The unit ID is related to a name and a unit character string, and the type ID includes a character string at least corresponding to each type ID, and the unit ID.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a data structure including an identifier for numeric data and a numeric management system using the data structure. [Background technology]

[0002] Any digitalized numerical data, such as numerical data obtained from measuring equipment, is given meaning using a data table (called a channel table in the case of measurements). For example, Figure 5(A) shows an example of a simple channel table. In this example, channel 1 is the generated power in kW, channel 2 is the temperature in °C, and channel 3 is the solar radiation intensity in kW / m. 2 This shows that.

[0003] Unlike communication over multiple routes, when multiple types of numerical data are sent and received by a data communication device over a single route, not only the value of the data being sent but also the order in which it is sent is important on the receiving side. A protocol specification is a table that indicates the meaning of the data received at which order on the receiving side, and is set in advance by the sender.

[0004] Patent Document 1 discloses a method for transferring data from a sensor by adding information such as the unit of measurement, precision, and error to a message header when encoding a sensor signal. Patent Document 2 discloses a method for controlling wireless communication for a photovoltaic power generation system, which discloses a method for recognizing integrated power generation data and the like by adding identification information for the photovoltaic power generation system to part of the communication data sent between a transmitter and a receiver. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2011-520309 A [Patent Document 2] JP 2006-277383 A [Patent Document 3] Special Publication No. 2017-530671 Summary of the Invention [Problem to be solved by the invention]

[0006] There are many different types of data tables for digital data and communication protocols for communication data, and no unified standards exist. For example, the channel tables included in the protocol specifications for measuring instruments differ for each measuring instrument. The communication protocols between the PCS (power conditioner) and the control terminal connected to the PCS in a solar power generation system also differ for each manufacturer and model.

[0007] For example, Figure 5(B) shows an example of a channel table for a certain PCS. The channel table shows the physical quantity represented by the data for each channel (e.g., input voltage, input current), data size (4 bytes, 6 bytes), data format (position of decimal point, etc.), data range, remarks, etc. Such channel tables are provided with more detailed annotations. For example, annotations include: set the sign but not the decimal point; data No. 4 [output voltage (V)] when the PCS is stopped is the grid voltage; data No. 4 [output voltage (V)] when the PCS is in independent operation is the independent output voltage (only for types with independent operation function).

[0008] Moreover, the specifications listed in such channel tables are frequently updated, so protocol specifications must always be version-controlled to prevent problems at the measurement equipment installation site.

[0009] Furthermore, the channel numbers of a measurement terminal are only unique within each measurement terminal. If there are multiple measurement terminals in one power generation system, the channel numbers may overlap. In other words, this problem is caused by the use of a protocol specification that is only used locally and whose specifications are frequently updated, and it is a fundamental problem that has not been fundamentally addressed for many years.

[0010] The present invention has been made in consideration of the above, and aims to provide a new data structure that makes it possible to globally identify the meanings of numerical values ​​and numerical data even if the protocol specification, which was previously only available locally, is made uniquely available globally, even if the protocol specification is not available on the local side. [Means for solving the problem]

[0011] The data structure according to the present invention comprises: A logical database constructed on a database server in which numerical data including a plurality of numerical values ​​associated with a timestamp is recorded; A data identification ID that uniquely identifies an attribute of a numerical value constituting the numerical data; A pair of logical data structures consisting of: The data identification ID is A unit ID consisting of a character string of at least two bytes that defines a unit of the numerical data; an item ID of at least 4 bytes consisting of an item number consisting of an integer value of at least 2 bytes for uniquely identifying the type ID after defining a type ID of at least 2 bytes that specifies the type of the numerical data; and Including, The unit ID is associated with a name and a unit string; The type ID includes at least a character string corresponding to a type ID and the unit ID.

[0012] In the above configuration, the unit ID may be further associated with a prefix that is placed before the unit.

[0013] In the above configuration, the data identification ID is The ID is recorded in an ID management server that is physically or logically separated from the database. The new registration of the multiple numbers associated with the updated timestamp or the reading of any number recorded in the database is performed via middleware, The data identification ID and each of the numerical values ​​included in the plurality of numerical data associated with the data identification ID may be configured to be always treated as a pair of data.

[0014] In the above configuration, the middleware may be executed in a measurement terminal that acquires the numerical data.

[0015] In the above configuration, the middleware may be executed in a middleware server that is physically or logically independent from the measurement terminal. Here, a "middleware server" refers to a server that is physically or logically independent from other servers and that implements data access middleware (hereinafter sometimes referred to as "middleware"), which is a program.

[0016] The numerical control system according to the present invention includes at least The data structure according to any one of claims 3 to 5 is used, and includes the ID management server, the database server, and the middleware interposed between the ID management server and the database server.

[0017] In the above configuration, the middleware may be configured to proxy requests and responses to the database. Effect of the Invention

[0018] According to the present invention, there is no need to prepare data tables or protocol specifications locally to interpret the data, which relieves users from the need to manage protocol versions, eliminating confusion in the field and contributing to greater utilization of data. [Brief description of the drawings]

[0019] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a power generation system according to a first embodiment. [Diagram 2] FIG. 2 is a table illustrating a list of physical unit IDs. [Diagram 3] FIG. 3 is a table illustrating a list of physics type IDs. [Figure 4] Figure 4 shows the format of the item ID. [Diagram 5] (A) An example of a simple channel table. (B) An example of a channel table for a PCS. [Figure 6] (A) is a configuration diagram when no data access middleware 102 is deployed and the user directly accesses the measurement data server 4 via multiple remote monitoring sites 1 to 3, and (B) is a configuration diagram when the measurement data server 4 is accessed via data access middleware. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] The basic idea of ​​the present invention is to prepare a table (database) to which an identifier (defined as a "data identification ID" in this specification) for uniquely identifying all data (numeric values) handled within the same system or units, etc. associated with the numeric values ​​is assigned, separate from the measurement database, and to centrally manage data, etc. using the identifier. Details of the data identification ID will be explained below in each embodiment. Numeric values ​​representing physical quantities are accompanied by the units of the respective physical quantities, and further accompanied by unit prefixes of decimals such as m (milli), μ (micro), p (pico), and large numbers such as k (kilo), M (mega). These also need to be uniquely identified, so they are treated as a type of numerical data and are referred to as "data, etc." in this specification.

[0021] (First embodiment) -Data identification ID applied to physical quantity-

[0022] In the first embodiment, a data identification ID (physical quantity data identification ID) that is applied to a physical quantity that is acquired mainly through a measuring instrument and exchanged through digital communication will be described.

[0023] [Data Identification ID] Here, the data identification ID will be explained in more detail. For example, a data identification ID for a physical quantity (hereinafter referred to as "physical quantity data identification ID") is composed of a. a physical unit ID and b. a physical type ID, both of which are stored as files in all software and referenced as necessary. It is preferable that a list of physical unit IDs and physical type IDs be stored on a server so that they can be referenced or downloaded at any time via a telecommunications line such as the Internet.

[0024] a. Physical unit ID Figure 2 is a table showing an example of a list of physical unit IDs. A physical unit ID is a value that specifies a physical unit, and is common to all software. It has items such as ID, name, and unit string. Even for the same unit, a physical unit ID is assigned to each unit prefix (m, k, G, M, etc.). For example, when expressing power, not only the unit but also the prefix is ​​important, such as 200W or 200kW. There are not many types of physical unit IDs, so they can be adequately expressed with, for example, 2 bytes (65536 ways).

[0025] b.Physical type ID The physical type ID is a value for identifying the physical or functional type of data, such as solar radiation, temperature, DC power, and power conditioner (PCS) output power, and is assigned to every physical quantity. The same applies to calculated values ​​such as indexes and efficiency. The physical type ID is also expressed in 2 bytes.

[0026] Figure 3 is a table showing an example of a list of physics type IDs. For the broad classification of photovoltaic power generation, physics type IDs are assigned to physical quantities that will be handled in a photovoltaic power generation system. Each physics type ID is assigned an item name and a tag name.

[0027] The physics type ID is associated with the name, TAG name, variable name, unit ID, (unit string), etc., and is defined as an integer value for the physics type ID (ID) and as a string for the physics type name (name).

[0028] Although only the classification, item name, ID, and TAG name are listed in Figure 3, the unit ID is set for each physical type ID. For example, for DC voltage, "V" is assigned, and a unit ID is assigned to that "V".

[0029] <Class definition example for physical type ID> class Tphysic ID { int ID; / / Physical type ID string name; / / Physical type name int unit_ID / / Physical unit ID string unit_name / / Unit name void set() / / Set the physical type name, unit ID, and unit name from the physical unit ID. };

[0030] As shown in Fig. 3, for example, the DC voltage in a photovoltaic power generation system is assigned an ID of 2000 and a TAG name of PV_DC_V. Similarly, the DC current is assigned an ID of 2001 and a TAG name of PV_DC_1. In this way, it is possible to define any physical type by a predetermined physical type ID. ID=2000 TAG name: PV_DC_V (Meaning: DC voltage of solar power generation) ID=2001 TAG name: PV_DC_1 (Meaning: Direct current from solar power generation)

[0031] In addition, in consideration of cases where there are multiple unique physical type IDs, such as when there are multiple systems of measuring equipment at one measurement site, the "item ID" is defined by adding a 2-byte natural number starting with 1 to the 2-byte physical type ID as the "item number." For example, even if there are multiple systems, each of which is connected to multiple PCSs, numbers are not assigned starting from 1 for each system, but rather to the whole system. In addition, when there are multiple physical type IDs assigned the same physical type ID, such as pyranometers and module temperatures, they can be distinguished by the item ID.

[0032] <Class design example> A class is an object in a program, and first a "class of all calculation formulas" that governs them as a whole is defined, and then under this class of all calculation formulas, "classes of each calculation formula" are defined according to the difference in the calculation method. In this way, just like with channels, they are divided into a "class of all calculation formulas" and a "class of each calculation formula".

[0033] A formula is a formula for performing calculations on measurement data (raw data). Data obtained by this formula is defined as formula data and is handled separately from measurement data.

[0034] class Tkeisanki { int siki_su; vevtor <tsiki>siki; void <tsiki>siki; void addEmptyVectorSiki (int siki_su); }; class Tsiki { Tkomoku_ID komoku_ID; / / Item ID class

[0035] The concept of identification ID is applied not only to measurement data, but also to data calculated based on that data using a specific formula.

[0036] c.Item ID An item ID is defined as a value that combines a physics type ID and an item number if there are multiple physical type IDs. An item ID must be unique and never be duplicated within a single site's data group (measurement channel, calculation formula, input formula, etc.).

[0037] The format of the item ID is shown in Figure 4. As shown in this figure, the item ID is in the form of a combination of an item number (2 bytes) and a physical type ID (2 bytes).

[0038] Item numbers are consecutive integer numbers starting from 1. Even if there are only a few identical physical type IDs, the number is always 1. Numbers will never be duplicated on one site. For example, even if there are multiple systems, each connected to multiple PCSs, numbers are not assigned starting from 1 for each system, but are assigned overall. Furthermore, even if there are multiple measurement terminals and multiple measurement systems, numbers are similarly assigned so that there are no duplicates. It is also used when there are multiple items with the same physical type ID, such as multiple pyranometers or multiple module temperatures. * It is possible to handle all item IDs in the class as shown below, but we will define them just in case.

[0039] d. Integrated data processing (data access middleware) class A class that provides integrated access to data. It can process not only measurement data but also other types of data (for example, formula data, input data, diagnostic data, statistical data, etc.) in a general-purpose manner. When accessing measurement data and the various data shown in 3.4.1, be sure to use this class. Do not directly access data files, and do not directly reference data variables in channel classes. <Data type> (1) Measurement data (2) Formula data (3) Input data (4) Diagnostic data (5)Statistical Data For each data type, a data number and item ID are set.

[0040] By allowing applications running on each application server 5 to access the database through a common interface provided by this middleware rather than directly, not only can data destruction and unauthorized access be prevented, but all applications can also access the data in a common manner.

[0041] <Class Design> The data acquisition function was previously inside Tchannel, but this will be moved outside and made independent as a new class. -It is now possible to obtain data using various parameters. - All types of data can be retrieved without having to worry about them, using only the item ID. If the time is not specified, the data at the time indicated by Tchannel.time (the data stored in Tch_.data) is obtained (usually the most recent time and data are stored). By using item ID 2, you can get data about appetizers.

[0042] <Class Design> / / Integrated data processing (data access middleware) class definition class Tdata { enum data_type {DATATYPE_CH, DATATYPE_CAL, DATATYPE_INPUT, DATATYPE_DIAG, DATATYPE_TOKEI}}; / / Data type: measurement data, calculation formula, input value, diagnostic value, statistical value double get_data (Tkomoku_ID komoku_ID) / / Get data from item ID class double get_data (Tkomoku_ID komoku_ID, Ttime time) / / Get data from item ID class and time bool get_data (Tkomoku_ID komoku_ID, Ttime time_s, Ttime time_e, double *data) / / Get data between item ID class and time range bool get_data (Tkomoku_ID komoku_ID, Ttime time, int kosu, double *data) / / Get the specified number of data items from the item ID class and time double get_data (int data_type, int no) / / Get from data type and data number };; If no time is specified, the latest value will be used. Many other data import functions are possible.

[0043] (Second embodiment) [System configuration example] FIG. 1 is a diagram showing a configuration example in which the data identification ID described in the first embodiment is applied to a power generation system. In this system, a power generation system 1 and a measurement data server 4 are connected via a network, and further, various application servers 5 (5a to 5c) and the measurement data server 4 are connected via a data access middleware 102. Furthermore, an ID management server 101 that manages data identification IDs is provided, and can communicate with the data access middleware 102 to exchange necessary ID management data.

[0044] The measurement terminals 2 (2a, 2b) acquire various measurement data from the PCS and are connected to a measurement data server 4 via a telecommunications line such as the Internet. Measurement data from various locations is collected in the measurement data server 4. The data server 4 is a server that manages a database of measurement data and the like, and the database itself may have a conventional data structure consisting of a timestamp linked to an identifier that identifies the power generation system (power plant) and multiple numeric strings linked to the timestamp.

[0045] Here, the power generation systems 1 (1A, 1B) are components of power plants scattered around the country, and may vary depending on the scale of the power plants. For example, the power generation system 1A has multiple measurement terminals 2 (2a, 2b, ...), while the power generation system 1B has an actinometer 3 in addition to one or more measurement terminals 2 (2a, 2b, ...). The measurement terminal 2 is connected to a power generation control device called a PCS (not shown) and a power generation control device for controlling the PCS, and the PCS is connected to a power generation device (for example, a solar power generation panel).

[0046] However, the type of power generation device is not particularly limited, and any power generation device that requires control of the amount of power generation may be used. For example, in addition to solar power, power generation devices using wind, geothermal, hydroelectric, and other natural energies are envisioned. Since the amount of power generated by these types of power generation is largely subject to fluctuations due to weather conditions, etc., there is a high need to monitor the status of the equipment in each system and detect equipment failures and their signs through measurement data collected in a measurement data server 4 located in a remote location.

[0047] The various application servers 5 (5a to 5c) provide various services by utilizing various measurement data stored in the measurement data server 4. For example, there is a remote monitoring system 5a for diagnosing the operating status of a power generation system in a remote location, an O&M (operation and maintenance) system 5b for checking the operating status and performing maintenance, and a power generation diagnosis system 5c for diagnosing abnormalities, failures, or deterioration over time of equipment in the power generation system.

[0048] Conventional power generation systems are configured so that the application server 5 directly accesses the measurement data server 4 to request and respond to data. However, in a configuration where each application server 5 directly accesses the database, there is a risk that the database recorded in the measurement data server 4 may be destroyed due to concentrated access to the database server, errors in the programs executed on each application server 5, or other unforeseen circumstances. Alternatively, there is an increased risk that the application server 5 may be used as a springboard to cause unauthorized access to the measurement database server 4.

[0049] In order to avoid such problems, this embodiment adopts a configuration in which a data access middleware 102 is interposed between the measurement data server 4 and the application server 5, and a configuration in which management data requests and responses to the data access middleware 102 are managed by an ID management server 101 for uniquely identifying measurement data of power generation systems scattered around the world and various data associated with the measurement data.

[0050] The ID management server 101 is a server for managing data identification IDs, and enables data, etc. to be uniquely identified without depending on the measurement terminal even if there are multiple measurement terminals. The data access middleware 102 can be operated on any of the servers, or may be operated on the measurement terminal 2a.

[0051] With this configuration, each application server 5 can access the measurement database 4 through an interface commonized by the data access middleware 102, thereby reducing the risk of destruction of data in the measurement data server 4 or unauthorized access to the measurement data server 4.

[0052] The data access middleware 102 has a function of receiving a request from the application server 5 and returning the necessary data. For this reason, it is necessary to register in advance the relationship between the ID management information for identifying data and the measurement data in the ID management server 101. This does not necessarily have to be done by the data access middleware 102 itself, but can be realized by inputting the necessary information to the ID management server 101 in advance. The ID management server 101 manages a database of data identification IDs, and stores a table that assigns meaning to numeric strings contained in the database (table) recorded in the measurement data server 4. Therefore, it has a function of returning specific ID management data corresponding to the required data in response to a request from the data access middleware 102.

[0053] There is no limitation on the method of implementing the data access middleware 102, and it may be configured to operate on a single dedicated server connected to a network. For example, although not required, the data access middleware may be implemented on a web server as a web application. In this case, it may be configured so that data requests are made from the application server 5 as URLs including specific commands and data in the server domain, etc. Alternatively, in a simpler system, it may be implemented such that similar functions are installed inside one or more measurement terminals 2 in the power generation system 1.

[0054] The measurement data recorded in the measurement data server 4 is a collection of numerical data that can be expressed as a table consisting of a timestamp and multiple numerical data at that time, and these numerical values ​​are usually recorded for each power generation system (power plant). It is possible to determine which power generation system or measurement site the measurement data was uploaded from by setting it in advance. Also, it is set in advance which numerical data corresponds to which identification ID. The order of the numerical data will not change unless the settings of the measurement terminal are changed. Conversely, when the settings of the measurement terminal are changed, it is necessary to make sure that the settings of the ID management server 101 are also changed.

[0055] Next, the operation of the data access middleware 102 will be described. The application server 5 requiring data assigns an identification ID to the requested measurement data and requests it from the data access middleware 102. In response to the request, the data access middleware 102 accesses the measurement data server 4, reads out the required data, and returns a response to the application server 5. The data request sent from the application server 5 to the data access middleware 102 may have the following format: Power Plant ID: 123456 (Laplace Power Plant) Measurement system ID: 789 (measurement system 1) Item ID: 10 (AC power of PCS1) Request period: February 1, 2022

[0056] When the data access middleware 102 is accessed by providing an identification ID such as that described above, an inquiry can be made to the ID management server to request data for February 1, 2022 of the AC power of the first PCS of the measurement system 1 at the Laplace power plant. Then, since the target record and target position of the data recorded in the measurement data server 4 can be known from the information registered in advance in the ID management server 101, the data access middleware 102 accesses the measurement data server 4 to obtain the required measurement data, and sends a response to the application server 5. The application server 5 can request data by providing multiple data identification IDs. For example, multiple measurement items can be requested from multiple power plants, and data for multiple periods can also be requested. The data access middleware 102 may be configured to calculate the aggregation process (for example, average value or integrated value) for the specified period and return the result.

[0057] <Examples of using data access middleware> The advantages of using data access middleware will be explained with reference to examples. Fig. 6(A) shows a configuration diagram in which the data access middleware 102 is not deployed and the user directly accesses the measurement data server 4 via multiple remote monitoring sites 1 to 3. In contrast, Fig. 6(B) shows a configuration diagram in which the measurement data server 4 is accessed via data access middleware. A use case of data access middleware will be explained by comparing the two.

[0058] First, as a premise, the data access middleware 102 is a system that requests the reading of specific data from a logical database constructed on a database server in which numerical data including multiple numerical values ​​is recorded, and responds to that request.

[0059] In a conventional configuration that does not use middleware (Fig. 6(A)), a data read request is sent to the measurement database server 4 via multiple remote monitoring sites 5a-5c, and a response of numerical data corresponding to the read request is received via each remote monitoring site. The meaning of the numerical data obtained from the measurement data server 4 is interpreted either by the remote monitoring site or by the party that requested the data.

[0060] On the other hand, in the configuration of Fig. 6(B), all requests for numerical data are made via the data access middleware 102. As shown in Fig. 1, the data access middleware 102 communicates with the ID management server 101, and is premised on being able to "assign meaning" to the numerical data by linking attributes of the numerical data recorded in the measurement database server 4. That is, the data access middleware is a program executed to request the numerical data from the measurement database server 4, and upon receiving a read request for specific data included in the numerical data, reads the specific data from the measurement database server 4. Then, the data access middleware acquires ID management data including a data identification ID from the ID management server in which a data identification ID that uniquely identifies the attributes of the numerical values ​​constituting the numerical data is recorded, and responds to the read request with the attributes of the numerical values ​​included in the specific data linked.

[0061] An example will be described in which the above basic configuration is applied to a mechanism for analyzing measurement data from a photovoltaic power generation system. Here, the photovoltaic power generation system (power plant) is assumed to have a mechanism for uploading measurement data acquired from a measurement terminal or measuring device installed in each photovoltaic power generation system (power plant) to a measurement database server 4, as shown in Fig. 1.

[0062] [Case 1] When obtaining the same type of data (e.g., generated power amount) from multiple power plants, instead of accessing each remote monitoring site as shown in Fig. 6(A), processing can be done with a single request by going through the middleware as shown in Fig. 6(B). The ability to obtain data from multiple power plants across multiple sites is useful for customers and O&M (operation and maintenance) companies that monitor multiple power plants simultaneously. For example, when realizing a function to display each data of the power plants owned in a list, even if the data is accessed through different communication media such as a website or application software running on a smartphone, all data can be obtained through the middleware.

[0063] [Case 2] Current power generation diagnostic functions that diagnose equipment anomalies, failures, or deterioration over time are implemented for each power plant individually. Therefore, it is only possible to perform diagnosis based on comparison with past power generation data accumulated for each power plant. However, by utilizing data access middleware, it is possible to obtain the necessary data from multiple different power plants. This makes it possible to analyze the obtained data. For example, by comparing separate data of similar configurations across multiple power plants from multiple perspectives, such as geographically nearby power plants, power plants with the same rated capacity, and power plants with similar equipment configurations, it is possible to perform power generation diagnosis to detect equipment failures or abnormalities.

[0064] [Case 3] As mentioned above, there are generally many different types of data, but middleware that handles data managed as a "set of data identification ID and data" has the advantage of being able to standardize the handling of data regardless of its type. In other words, even if the source data is not only your own company's data but also other companies' data, the middleware absorbs the differences, so when customers or higher-level applications request data, they do not need to be aware of the differences in the source data, making it simpler and easier for the data requester.

[0065] In the above [Case 1] to [Case 3] explained using Fig. 6(A) and Fig. 6(B), all of them are examples of a user or a specific device requesting measurement data from the measurement data server 4 that records "measurement data" with the analysis of power generation data in a photovoltaic power generation system in mind, and receiving the desired measurement data (numerical data) in response via "middleware". However, it is important to note that the requested numerical data is returned after the numerical data is given meaning by linking it to a data identification ID. It goes without saying that the numerical data is not limited to measurement data, but includes character strings and all data that can be handled on a computer. Such a mechanism can be applied to a diagnostic system that detects equipment failures or abnormalities.

[0066] Second embodiment: Data communication method When the application server 5 for handling data makes an access request to the measurement data server 4 to the middleware 102, the necessary data can be identified using the data identification ID. Therefore, the middleware 102 can quickly obtain the necessary data from the database managed by the measurement data server 4 and send the data back to the application server 5 that received the access request.

[0067] There is not only one specific means for realizing this, but as an example, a method using a so-called WebAPI is assumed. Generally, a WebAPI is a web application program in which the required data is returned from a target server URL by adding an option (additional information) to the URL and communicating with the URL. In the above case, the target middleware server 101 is started as a web server, and the URL becomes the entrance of the middleware, and an access request is made by adding information such as a data identification ID, data period, and data format as options. In addition, it is assumed that the returned data can be arbitrarily selected from multiple output formats such as binary format, JSON format, and CSV format, which are easy to handle for each application, by prior setting.

[0068] Here, we will again take a photovoltaic power generation system as an example. Conventionally, when a measurement terminal connected to a power conditioner (PCS) in a photovoltaic power generation system receives and displays the generated power from the PCS, it is necessary to refer to a channel table and set the corresponding channel number. This is because the data obtained from the PCS is simply a list of numbers immediately after acquisition. Information about which of the sequentially arranged numbers represents what data (for example, the first number is the AC power of the first PCS) is defined by the channel table.

[0069] At the PCS installation site, the order changes when additional PCSs are installed or communication specifications are changed, and the channel table is often updated each time. This is often the cause of problems. In general, the order seems to depend on the PCS communication protocol.

[0070] Therefore, by setting an identification ID (physical quantity identification ID) for the generated power instead of the channel table and always treating the identification ID and the corresponding data as a pair, it is possible to ensure that the meaning of the data is not lost even if the order in which the data is saved changes. For example, no matter what position in the channel table the data representing the generated power is in, it can be identified by using the identification ID as a marker. There is also no need to specify the order in which the data is saved.

[0071] Similarly, when sending data over a network, as long as the rule that data and an ID are always paired is observed, the order of transmission is meaningless and data can be sent at any time. In other words, there is no need to specify a protocol.

[0072] Furthermore, channel numbers are only unique within each measurement terminal. If there are multiple measurement terminals within one power generation system, there is a possibility of duplication of channel numbers. In this regard, since the data identification ID can be assigned a unique value within the same power generation system, it is possible to identify and obtain unique data without depending on the measurement terminal, even if there are multiple measurement terminals.

[0073] The ability to extract only the necessary data in a manner independent of the order, as in this embodiment, contributes to a dramatic improvement in the versatility of processing.

[0074] The data identification ID can also be applied to calculation formulas, input values, and calculated values, allowing calculated values ​​and measured values ​​to be treated equally. If all sites follow the same rules, uniform processing will be possible, regardless of the unique system formats of each site. If this method were adopted in all measurement systems around the world, all data around the world could be handled generically.

[0075] <Example 1> It is possible to build a system in which the application server 5 requests the generated power from each of the multiple power generation systems 1 (1A, 1B, ...) and obtains the total value. This can be a great advantage for users who manage multiple power generation systems. In the conventional system, the application had to request and obtain information from each power generation system and then add them up, which took a lot of time.In addition, communication was required for each request to each power generation system, which was wasteful, so the advantage of this system is great.

[0076] <Example 2> Assume that there are two power generation systems 1A and 1B located relatively close to each other, and only one of them (for example, power generation system 1B) is equipped with an actinometer 3. Since actinometers 3 are expensive, it is often not realistic to install them in all power plants. However, since actinometers 3 are useful for predicting and maintaining power generation, it would be preferable if actinometer data could be used for predicting and maintaining power generation in the same way for power generation systems that do not have actinometers installed. Previously, it was not easy to use data from a power generation system as data from another power generation system, but by requesting data using an identification ID, it is possible to obtain data that goes beyond the unit of the power generation system, expanding the scope of data utilization.

[0077] In the first and second embodiments described with reference to FIG. 1, an example of a data identification ID specialized for a measurement system has been described. However, the most essential point is that each piece of data in the "database" managed by the data server is uniquely identified by a "data identification ID" and is thereby given meaning. Although the use of an "ID management server" separate from the "data server" to manage the data identification ID and the access to the "data server" via "data access middleware" are one of the most reasonable aspects as a specific configuration example, other configurations are also conceivable, such as including the function of the ID management server as part of the measurement data server, omitting the middleware server, or aggregating multiple servers to simplify depending on the scale of data handled.

[0078] (Third embodiment) The essence of this invention is that it does not matter what type of data is handled. The important thing is that the database is separated from the ID management server that manages the data identification ID, and the database is accessed via the data access middleware. Therefore, the numerical data handled can be numerical values ​​other than physical quantities, such as monetary data such as sales and profits. For example, accounting information such as sales and profits was generally configured to be referenced only within a specific system such as a financial management system. However, by setting up an ID management server that manages data IDs separately from the database server, and accessing the database via data access middleware, data can be referenced without being tied to a specific system, making it easier to link systems. For example, numerical data such as sales and profits can be used for current sales analysis and future profit planning, and may be needed outside of the financial management system. However, this was inconvenient as only the necessary data had to be output as a separate file, etc., but by managing the data as data with a data ID assigned in advance, it can be referenced immediately when requested by the system that needs it, providing extremely high convenience. [Industrial Applicability]

[0079] As IoT devices become more widespread, it will be impossible to handle the numerical data acquired by IoT devices in a general manner if the data is defined according to each company's own specifications or for each location (site). However, if each company exchanges numerical data using similar communication rules based on the data structure of this invention, it will become possible to handle numerical data equally across different devices, just like IP addresses and QR codes (registered trademark), and the industrial potential will be extremely great.< / tsiki> < / tsiki>

Claims

1. A first data element that stores numerical data including multiple numerical values ​​associated with a timestamp, acquired by a measuring instrument, A second data element that stores a data identification ID that is associated with each of the aforementioned plurality of numerical values ​​and identifies the attributes of said numerical value, Includes, The second data element is managed by an ID management server, and the data structure includes information relating the data identification ID to the plurality of numerical values ​​contained in the first data element. A data structure used in a process in which a target numerical value is identified from among the multiple numerical values ​​based on the aforementioned data identification ID, or in which the meaning of the target numerical value is assigned.

2. The data structure according to claim 1, wherein the first data element stores time-series numerical data ordered by the timestamp.

3. The data structure according to claim 1, wherein the data identification ID includes a unit ID that defines the unit of the numerical data, a type ID that defines the type of the numerical data, and an item ID that uniquely identifies the type ID.

4. The data structure according to claim 1, further comprising a third data element that stores a calculated value generated by an operation based on the numerical data associated with the data identification ID, wherein the calculated value is associated with the data identification ID.

5. The data structure according to claim 4, wherein the third data element may be stored as the same data element as the first data element or as a different data element.

6. The data structure according to claim 1, wherein the calculated value includes an index, efficiency, average value, or cumulative value.

7. A program for causing a process to receive a data request based on a data identification ID using the data structure described in any one of claims 1 to 6, obtain ID management data corresponding to the data identification ID from an ID management server, obtain a target numerical value from the numerical data, and generate a response with the ID management data attached.

8. An ID management server for managing the second data element constituting the data structure according to any one of claims 1 to 6, the ID management server including a database for storing the data identification ID.

9. A measurement data server that holds the first data element constituting the data structure according to any one of claims 1 to 6.

10. Middleware for mediating data requests and responses to a data structure according to any one of claims 1 to 6, wherein middleware receives a read request based on a data identification ID, obtains ID management data corresponding to the data identification ID from an ID management server, obtains a target numerical value from a measurement data server, and generates a response with the ID management data attached.

11. A numerical management system comprising the ID management server according to claim 8, the measurement data server according to claim 9, and the middleware according to claim 10.

12. The numerical management system according to claim 11, wherein the numerical management system is applied to multiple measurement points, and acquires data of the same attributes obtained from the multiple measurement points via the middleware, based on a data identification ID.

13. A numerical management system according to claim 12, which is used to diagnose equipment installed at multiple measurement points, acquires data of the same attributes via the middleware, and diagnoses the equipment based on the acquired data.

14. The middleware according to claim 10, characterized in that it runs on a web server, receives a read request via Web API in which additional information including a data identification ID is attached to the URL of the web server, and returns the necessary information in response to the read request.

15. The numerical management system according to claim 12, wherein a single application acquires time-series data obtained from multiple measurement points via the middleware and calculates a sum of the data.

16. The numerical management system according to claim 12, which is applied to a first measurement point where a pyranometer is installed and a second measurement point where a pyranometer is not installed, and applies the pyranometer data acquired at the first measurement point to the data utilization at the second measurement point.

17. The numerical management system according to claim 11, wherein the ID management server that manages the data identification ID and the measurement data server that holds the numerical data acquired by the measuring instrument are separated, and data access is performed via middleware.

18. A method for communicating numerical data acquired by a device, wherein the numerical data is transmitted in association with a data identification ID that identifies the attributes of the numerical data, and the receiving side can handle the numerical data without depending on the transmission order or a device-specific communication protocol by assigning meaning to the numerical data based on the data identification ID.

Images