JP7421275B2 - data management device - Google Patents

Description

The present invention relates to a data management device that manages power amount data regularly collected from smart meters.

Full liberalization of the electricity retail market began in 2016, and low-voltage customers became subject to wheeling charges. The number of consumers subject to the calculation of wheeling charges is steadily increasing, and when the legal separation of electricity transmission and transmission is implemented in 2020, all low-voltage consumers will be subject to the calculation of wheeling charges. Calculation of wheeling charges requires data on the amount of electricity used by each customer (also called 30-minute electricity amount data), but due to the legal separation of electricity transmission and transmission, the amount of data on the amount of electricity used by each customer is It becomes huge. In order to complete the calculation of wheeling charges for each electricity retailer within a predetermined time, a mechanism is needed that allows the computer performing the calculation to obtain the necessary data from devices such as servers at high speed.

The sensor data management device described in Patent Document 1 divides sensor data transmitted from each of a plurality of sensor terminals into groups based on registration interval, arrival time, update frequency, etc., and stores data in memory for each group. It is stored and managed in pages, which are units of reading and writing to the page buffer.

JP2017-167977A

Since the 30-minute power consumption data used in calculating the wheeling fee is periodically transmitted from the smart meter, there are no differences in the data registration interval, arrival time, update frequency, etc., and the invention described in Patent Document 1 It is difficult to group and manage them in a similar way. That is, each page stores 30-minute power amount data transmitted from each smart meter in chronological order. Therefore, even if the invention described in Patent Document 1 is applied, it is difficult to group and manage 30-minute power consumption data that is regularly collected and stored on a server etc. so that it can be read out at high speed. It is not possible to shorten the time required for calculation. In order to be able to read 30-minute power amount data at high speed, it is necessary to reduce the number of pages that store 30-minute power amount data for consumers who purchase electricity from the same electricity retailer. .

The present invention has been made in view of the above, and an object of the present invention is to provide a data management device that can shorten the time required for processing to calculate a wheeling fee.

In order to solve the above-mentioned problems and achieve the purpose, a data management device according to the present invention acquires power amount data from a storage device that stores power amount data periodically transmitted from a smart meter in chronological order. It includes a data acquisition section and a data storage section that stores the power amount data acquired by the data acquisition section. The data acquisition unit collects the power amount data so that the power amount data of consumers who purchase power from the same contractor are in the same group based on the contractor ID indicating the contractor from whom the consumer purchases power. and a relocation unit that groups the power amount data of the same group and stores them collectively in a predetermined range of the storage area that constitutes the data storage unit. The storage area includes a plurality of blocks that can be accessed by an external device at once, and the data acquisition unit stores the same group of power amount data in one block. The data management device includes a calculation unit definition holding section that holds a calculation unit definition that defines a calculation unit that is a unit for calculating a wheeling fee. A calculation unit is formed including one or more blocks, and the data acquisition unit stores the same group of power amount data in one calculation unit.

According to the present invention, it is possible to realize a data management device that can shorten the time required for processing to calculate a wheeling fee.

A diagram showing a configuration example of a wheeling fee calculation system configured by applying the data management device according to the first embodiment. Diagram showing an example of a hardware configuration that realizes a data management device A diagram showing an example of the arrangement within the storage area of power amount data held by the storage device of the wheeling fee calculation system shown in FIG. Flowchart illustrating an example of the operation of the data acquisition unit of the data management device according to the first embodiment A diagram illustrating an example of the arrangement of power amount data held by the data storage unit of the data management device according to the first embodiment in a storage area. A diagram showing a configuration example of a wheeling fee calculation system configured by applying the data management device according to the second embodiment A diagram showing an example of a calculation unit definition held by the calculation unit definition holding unit of the data management device according to the second embodiment. Flowchart showing an example of the operation of the data acquisition unit of the data management device according to the second embodiment A diagram showing an example of the arrangement of power amount data held by the data storage unit of the data management device according to Embodiment 2 within the storage area. A diagram showing a configuration example of a wheeling fee calculation system configured by applying the data management device according to Embodiment 3.

DESCRIPTION OF THE PREFERRED EMBODIMENTS A data management device according to an embodiment of the present invention will be described in detail below with reference to the drawings. Note that the present invention is not limited to this embodiment.

Embodiment 1.
FIG. 1 is a diagram showing a configuration example of a wheeling fee calculation system configured by applying the data management device according to the first embodiment. FIG. 1 also shows a data collection system 100 that collects data necessary for the wheeling fee calculation system to calculate the wheeling fee.

The wheeling fee calculation system shown in FIG. 1 calculates wheeling fees in cooperation with a data collection system 100 that collects power amount data indicating the amount of power used by a consumer from a smart meter 101 installed at the customer. The power amount data that the data collection system 100 collects from each smart meter 101 is 30-minute power amount data indicating the amount of power used for 30 minutes. The 30-minute power amount data includes, in addition to the power amount information, a smart meter ID (Identification) indicating the smart meter 101 that outputs the 30-minute power amount data. Note that in this embodiment, the power amount data collected by the data collection system 100 is 30-minute power amount data, for example. The power amount data collected by the data collection system 100 may be any data that indicates the amount of power used for a predetermined period of time, and is not limited to data that indicates the amount of power used for 30 minutes. For example, the power amount data collected by the data collection system 100 may be data indicating the amount of power used for one hour, data indicating the amount of power used for 15 minutes, or the like.

The wheeling fee system shown in FIG. and an application server 300 that performs calculations. The storage device 200 is a server device equipped with a database or the like.

The data management device 1 includes a data acquisition unit 20 that acquires 30-minute power amount data from a storage device 200, and a data storage unit 30 that stores the 30-minute power amount data acquired by the data acquisition unit 20. The data acquisition unit 20 includes a rearrangement unit 21 that rearranges the acquired 30-minute power amount data and stores the rearranged data in the storage area of the data storage unit 30. The data storage unit 30 stores 30-minute power amount data similarly to the storage device 200 described above, but the arrangement of the 30-minute power amount data in the storage area, that is, the arrangement of each 30-minute power amount data is different from the storage device 200. different. The rearrangement unit 21 of the data acquisition unit 20 rearranges each 30-minute power amount data so that the application server 300 can efficiently read the 30-minute power amount data necessary for calculating the wheeling fee. The data is stored in the storage area of the data storage unit 30. The details of the operation in which the relocation unit 21 rearranges each 30-minute power amount data will be explained separately.

Here, the hardware configuration of the data management device 1 according to this embodiment will be explained. FIG. 2 is a diagram showing an example of a hardware configuration that implements the data management device 1. As shown in FIG.

The data management device 1 is realized by, for example, the hardware shown in FIG. 2, specifically, a processor 91, a memory 92, and a communication interface 93.

The processor 91 is a CPU (Central Processing Unit, also referred to as a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, a DSP (Digital Signal Processor)), a system LSI (Large Scale Integration), or the like. Further, the memory 92 is a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable ROM), an EEPROM (registered trademark) (Electrically Erasable Programmable ROM), or the like. The communication interface 93 is a network interface card or the like.

The data acquisition unit 20 of the data management device 1 is realized by a processor 91 and a memory 92. Specifically, a program for operating as the data acquisition unit 20 is stored in the memory 92, and the processor 91 reads and executes the program stored in the memory 92, thereby realizing the data acquisition unit 20. Ru. Note that the data acquisition unit 20 implemented by the processor 91 and the memory 92 acquires 30-minute power amount data from the storage device 200 via the communication interface 93.

The data storage unit 30 of the data management device 1 is realized by a memory 92. Note that the data management device 1 may be implemented by a computer, and the data storage unit 30 may be implemented by a general database constructed using a DBMS (Database Management System).

Returning to the explanation of FIG. 1, the application server 300 includes a business function unit 301 that calculates the wheeling fee. Here, the wheeling fee is determined independently for each electricity retailer that sells electricity to consumers. This means that the method of calculating wheeling charges differs depending on the electricity retailer. Therefore, the business function unit 301 calculates the wheeling fee for each electricity retailer with which each consumer has a contract. The calculated wheeling charges are provided to each electricity retailer. Note that in the following explanation, the electricity retailer will be referred to as a "contractor."

Next, the operation of the data acquisition unit 20 of the data management device 1, specifically, acquires the 30-minute power amount data from the storage device 200, sorts it, and writes the 30-minute power amount data into the data storage unit 30. The operation will be explained. Note that in the following description, 30-minute power amount data may be referred to as power amount data.

FIG. 3 is a diagram showing an example of the arrangement of power amount data held in the storage device 200 of the wheeling fee calculation system shown in FIG. 1 within a storage area. In FIG. 3, one rectangle in which alphabets and numerical values are written indicates one piece of power amount data. Also, alphabets indicate contractors, and numbers indicate consumers. For example, the power amount data in which "A10" is written is the power amount data of "consumer 10" who purchases power from "contractor A".

Generally, when an external device accesses a storage device such as a memory to write and read data, it is done in blocks of fixed size. That is, the range that an external device can access at one time is a block, and the storage device is configured to include a plurality of blocks. The same applies to the storage device 200. In this embodiment, one block is an area reserved for storing 10 pieces of power amount data. That is, one block can store 10 pieces of power amount data. In FIG. 3, ten squares surrounded by thick lines represent one block. For example, the block described at the left end stores 10 pieces of power amount data indicated by A10, A57, A51, C6, A59, B22, A48, B8, A27, and A53.

As described above, the power amount data collected by the data collection system 100 from each smart meter 101 is written in the storage device 200 in chronological order. Therefore, as shown in FIG. 3, each block, which is a unit that is accessed by an external device, stores power amount data of consumers who are different contractors. In this case, the electricity amount data of consumers who purchase electricity from the same contractor is stored distributed in many blocks, so in order to calculate the wheeling charge for each contractor, it is necessary to It is necessary to access all the blocks in which the electric power amount data of the consumers who purchase electric power are stored, and it takes time to read the data. In this way, if the electricity amount data required to calculate the wheeling fee is stored in a distributed manner over many blocks, the time required to read the data will be longer, and the time required to complete the calculation of the wheeling fee will also be longer. turn into.

Therefore, the data management device 1 according to the present embodiment reads the power amount data from the storage device 200, and the application server 300 efficiently reads the power amount data necessary for calculating the wheeling fee for each contractor. The power amount data is rearranged and stored in the data storage unit 30 so that it can be output. Here, the data storage unit 30 is assumed to be configured so that when an external device accesses and writes and reads data, data is written and read in units of blocks with a fixed size, similarly to the storage device 200. Note that the data management device 1 stores the smart meter ID of each smart meter 101, the consumer ID indicating the consumer who uses each smart meter 101, and the subscriber ID indicating the subscriber from whom each consumer purchases electricity. It is assumed that a correspondence table showing the correspondence relationship between the two is maintained.

FIG. 4 is a flowchart illustrating an example of the operation of the data acquisition unit 20 of the data management device 1 according to the first embodiment. The flowchart in FIG. 4 shows an operation in which the data acquisition unit 20 acquires power amount data from the storage device 200, sorts it, and stores it in the data storage unit 30.

As shown in FIG. 4, the data acquisition unit 20 first acquires power amount data from the storage device 200 (step S11). The data acquisition unit 20 then groups the acquired power amount data (step S12). The data acquisition unit 20 according to the present embodiment performs grouping based on the contractor ID in step S12. Specifically, the data acquisition unit 20 performs grouping so that the power amount data of consumers who purchase power from the same contractor are in the same group. Next, the data acquisition unit 20 rearranges each piece of power amount data so that the storage locations of the same group of power amount data are physically close to each other and stores it in the data storage unit 30 (step S13). Specifically, the data acquisition unit 20 stores power amount data of the same group in a block that is a unit that is accessed by an external device. Each process of step S12 and step S13 is performed by the relocation unit 21 of the data acquisition unit 20.

The data acquisition unit 20 periodically repeatedly executes the operation shown in the flowchart of FIG. 4, such as executing the operation at midnight or every hour. Note that the data acquisition unit 20 acquires the power amount data newly accumulated in the storage device 200 after the previous operation was performed in step S11 described above.

FIG. 5 is a diagram illustrating an example of the arrangement of power amount data held by the data storage unit 30 of the data management device 1 according to the first embodiment within the storage area. In FIG. 5, similarly to FIG. 3, one rectangle in which alphabets and numerical values are written indicates one power amount data. Also, alphabets indicate contractors, and numbers indicate consumers. Further, each block, which is a unit that is accessed by an external device, is composed of an area reserved for storing 10 pieces of power amount data. Figure 5 shows an example where each block stores electricity amount data for each group in just the right amount, but in reality, there is a storage area in which no electricity amount data is stored. There are blocks that do. It is desirable that the same group of power amount data be stored in one block.

Note that in this embodiment, the unit (block) for accessing the data storage section 30 provided in the data management device 1 and the unit for accessing the storage device 200 have the same size, but these sizes may be different.

FIG. 5 shows an arrangement in which the data acquisition section 20 reads out and rearranges each piece of power amount data held in the storage device 200 in the arrangement shown in FIG. 3, and stores the data in the data storage section 30.

In the example shown in FIG. 5, power amount data of a consumer who purchases power from contractor A (hereinafter referred to as "contractor A's power amount data") is arranged in blocks B1 to B6. In addition, power amount data of consumers purchasing power from Contractor B (hereinafter referred to as "Contractor B's power amount data") is arranged in blocks B7 to B9, Power amount data of a consumer (hereinafter referred to as "power amount data of contractor C") is arranged in block B10. Therefore, when the application server 300 calculates the wheeling fee for the contractor A, it is possible to read all of the power amount data of the contractor A in six data read processes, and the time required for data reading can be shortened. Similarly, when calculating the wheeling fee for Contractor B, the application server 300 can read out all of the power amount data of Contractor B in three data read processes, and when calculating the wheeling fee for Contractor C, , it is possible to read out all the power amount data of the contractor C in one data read process.

In this way, in the data management device 1 according to the present embodiment, the data acquisition unit 20 stores the 30-minute power amount data collected from the smart meters 101 of each customer from the storage device 200 that stores the 30-minute power amount data in chronological order. Power amount data is acquired and grouped so that the power amount data of consumers purchasing power from the same contractor are in the same group. Further, the data acquisition unit 20 rearranges each 30-minute power amount data so that the storage locations of the 30-minute power amount data of the same group are physically close to each other, and stores the 30-minute power amount data in the data storage unit 30. This allows the application server 300 to efficiently read the 30-minute power amount data used in calculating the wheeling fee from the data storage unit 30, reducing the time required for the process of calculating the wheeling fee. realizable. Note that the "processing for calculating the wheeling fee" herein includes processing for making necessary preparations for calculating the wheeling fee, such as a process for reading out 30-minute power amount data used for calculation.

Embodiment 2.
FIG. 6 is a diagram showing a configuration example of a wheeling fee calculation system configured by applying the data management device according to the second embodiment. In FIG. 6, the same components as those in the wheeling fee calculation system according to the first embodiment shown in FIG. 1 are given the same reference numerals. The components other than the data management device 1a are the same as the wheeling fee calculation system according to the first embodiment. Therefore, description of the components other than the data management device 1a will be omitted. Note that although there are a plurality of application servers 300, each application server 300 is the same as the application server 300 described in the first embodiment. In the wheeling fee calculation system according to the first embodiment, one application server 300 calculates the wheeling fee, but in the wheeling fee calculation system according to the second embodiment, a plurality of application servers 300 calculate the wheeling fee. are performed in parallel. That is, in the wheeling fee calculation system according to the second embodiment, the wheeling fee calculation process is performed by distributing it to a plurality of application servers 300. The data management device 1a holds power amount data in an arrangement that allows a plurality of application servers 300 to calculate wheeling charges in parallel.

The data management device 1a according to the second embodiment includes a data acquisition section 20a, a data storage section 30, a calculation unit definition acquisition section 40, and a calculation unit definition holding section 50.

The data acquisition section 20a includes a relocation section 21a. The relocation unit 21a rearranges the power amount data acquired from the storage device 200 in consideration of the calculation unit definition held by the calculation unit definition holding unit 50, and stores the data in the data storage unit 30.

The calculation unit definition holding unit 50 holds, for example, information on the configuration shown in FIG. 7 as a calculation unit definition. FIG. 7 is a diagram showing an example of a calculation unit definition held by the calculation unit definition holding unit 50 of the data management device 1a according to the second embodiment. The calculation unit is a unit for calculating the wheeling fee, and indicates power amount data used when one application server 300 calculates the wheeling fee. In this embodiment, as shown in FIG. 7, the calculation unit definition includes a "calculation unit name", a "contractor ID", and a "consumer ID". "Calculation unit name" is the name of the calculation unit, "contractor ID" is the identification information of the contractor, and "consumer ID" is the identification information of the consumer.

The calculation unit definition in the example shown in FIG. 7 includes information on a total of four calculation units. In the calculation unit definition shown in FIG. 7, the information registered in the row with the calculation unit name "calculation unit 001" is the customer ID that purchases electricity from the contractor whose contract ID is "contractor 001". indicates that the power amount data of each consumer from "consumer 0000001 to consumer 0010000" is taken as one unit, and the wheeling fee is calculated using these power amount data. Similarly, the information registered in the row with the calculation unit name "Calculation unit 002" indicates that the customer ID of the customer purchasing electricity from the contractor ID "Contractor 001" is "Consumer 0010001~ This shows that the power amount data of each consumer of "Consumer 0020000" is taken as one unit, and the wheeling fee is calculated using these power amount data. In addition, the information registered in the row with the calculation unit name "Calculation unit 003" indicates that the customer ID purchasing electricity from the contractor ID "Contractor 002" is "Consumer 0020001~Demand 0025000" as one unit, and the wheeling charge is calculated using these power amount data. The information registered in the row with the calculation unit name "Calculation unit 004" is the customer ID of "Consumer 0025001~Customer 0025300" who is purchasing electricity from the contractor with the contractor ID "Contractor 003". '' indicates that the power amount data of each consumer is taken as one unit, and the wheeling fee is calculated using these power amount data.

The calculation unit definition acquisition section 40 acquires the calculation unit definition held by the calculation unit definition holding section 50 from the outside. The calculation unit definition acquisition section 40 may be configured to acquire calculation unit definition data from the outside using a communication function or the like, or may have a screen for inputting the calculation unit definition on a display section (not shown). It may be configured to display the calculation unit definition and receive input from the user for the calculation unit definition using an input device such as a mouse or a keyboard.

FIG. 8 is a flowchart showing an example of the operation of the data acquisition unit 20a of the data management device 1a according to the second embodiment. The flowchart in FIG. 8 shows an operation in which the data acquisition unit 20a acquires power amount data from the storage device 200, sorts it, and stores it in the data storage unit 30.

As shown in FIG. 8, the data acquisition unit 20a first acquires power amount data from the storage device 200 (step S21). The data acquisition unit 20a next confirms the contractor associated with the acquired power amount data (step S22). Specifically, the data acquisition unit 20a confirms the subscriber ID associated with the smart meter ID included in the acquired power amount data. At this time, the data acquisition unit 20a checks each of the power amount data acquired in step S21.

The data acquisition unit 20a then stores the power amount data in the data storage unit 30 according to the calculation unit definition held by the calculation unit definition storage unit 50 (step S23). For example, when the calculation unit definition holding unit 50 holds the calculation unit definition with the content shown in FIG. 7, in step S23, the relocation unit 21a of the data acquisition unit 20a , among the consumers who purchase electricity from the subscriber with the subscriber ID of 001, the power amount data of the consumers with the consumer ID of 0000001 to 0010000 is stored. In addition, the relocation unit 21a of the data acquisition unit 20a assigns the customer ID of the customers who purchase electricity from the contractor whose customer ID is 001 to the calculation unit whose calculation unit name is calculation unit 002. stores electric energy data of consumers 0010001 to 0020000. In addition, the relocation unit 21a of the data acquisition unit 20a assigns the customer ID of the customers who purchase electricity from the contractor whose customer ID is 002 to the calculation unit whose calculation unit name is calculation unit 003. stores electric energy data of consumers 0020001 to 0025000. In addition, the relocation unit 21a of the data acquisition unit 20a assigns the customer ID of the customers who purchase electricity from the contractor whose customer ID is 003 to the calculation unit whose calculation unit name is calculation unit 004. stores electric energy data of consumers 0025001 to 0025300.

The data acquisition unit 20a periodically repeatedly executes the operation shown in the flowchart of FIG. 8, such as executing the operation at midnight or every hour. Note that the data acquisition unit 20a acquires the power amount data newly accumulated in the storage device 200 after the previous operation was performed in step S21 described above.

FIG. 9 is a diagram illustrating an example of the arrangement of power amount data held by the data storage unit 30 of the data management device 1a according to the second embodiment within the storage area. In FIG. 9, similarly to FIG. 5, one rectangle in which an alphabet and a numerical value are written indicates one power amount data. Also, alphabets indicate contractors, and numbers indicate consumers. Further, each block, which is a unit that is accessed by an external device, is composed of an area reserved for storing 10 pieces of power amount data. Also, one or more blocks form one calculation unit. In the example shown in FIG. 9, blocks B1 and B2 form calculation unit #1, blocks B3 and B4 form calculation unit #2, blocks B5 and B6 form calculation unit #3, and blocks B7 and B8 forms calculation unit #4, block B9 forms calculation unit #5, and block B10 forms calculation unit #6.

When the data acquisition unit 20a rearranges the power amount data so as to have the arrangement shown in FIG. It becomes possible to perform the processing of reading and calculating the transportation fee in parallel. That is, as shown in FIG. 9, calculation of the transportation fee for contractor A can be distributed among application servers #1 to #3. Further, it becomes possible to calculate the transportation fee for the contractor B by distributing it to the application servers #1 and #2.

The data acquisition unit 20 of the data management device 1 according to Embodiment 1 and the data acquisition unit 20a of the data management device 1a according to the present embodiment are configured to collect power amount data of consumers purchasing power from the same contractor. They have in common that each power amount data is rearranged and stored in the data storage unit 30 so that the storage locations thereof are physically close to each other. When rearranging each power amount data, the data acquisition unit 20a considers the calculation unit of the wheeling fee in addition to the group to which each power amount data belongs (contractor from which each consumer purchases power). .

According to the data management device 1a according to the present embodiment, it becomes possible for a plurality of application servers 300 to calculate the wheeling fee in parallel, and the time required for the process of calculating the wheeling fee is longer than in the first embodiment. can be further shortened.

Embodiment 3.
FIG. 10 is a diagram showing a configuration example of a wheeling fee calculation system configured by applying the data management device according to the third embodiment. In FIG. 10, the same components as those of the wheeling fee calculation system according to the second embodiment shown in FIG. 6 are given the same reference numerals.

The wheeling fee calculation system according to the present embodiment has a configuration in which power amount data collected by the data collection system 100 from the smart meter 101 is directly input from the data collection system 100 to the data management device 1b.

The data management devices 1 and 1a described in Embodiments 1 and 2 periodically acquire power amount data, but the timing at which the data management device 1b according to the present embodiment acquires power amount data is depends on the operation of data collection system 100. That is, the data management device 1b acquires the power amount data at the timing when the data collection system 100 outputs the power amount data.

The data management device 1b is obtained by replacing the data acquisition unit 20a of the data management device 1a according to the second embodiment with a data acquisition unit 20b. The data acquisition section 20b includes a rearrangement section 21b.

Every time power amount data is input from the data collection system 100, the relocation unit 21b checks the contractor associated with the input power amount data, and the calculation unit definition holding unit 50 holds the information. The power amount data is stored in the data storage unit 30 according to the calculation unit definition. This operation is similar to the operation in which the relocation unit 21a of the data acquisition unit 20a that constitutes the data management device 1a according to the second embodiment rearranges the power amount data. That is, when the power amount data is input, the relocation unit 21b identifies the subscriber ID of the contractor associated with the power amount data and the customer who is using the smart meter 101 that outputs the power amount data. Compare the consumer ID with the calculation unit definition and store the power amount data in an unused area within the calculation unit that is associated with the input power amount data, that is, an area where no power amount data is stored. . When the relocation unit 21b rearranges the power amount data input to the data acquisition unit 20b and stores it in the data storage unit 30, the arrangement in the data storage unit 30 is also as shown in FIG.

In this way, the data management device 1b that directly acquires power amount data from the data collection system 100 purchases power from the same contractor, similar to the data management devices 1 and 1a according to the first and second embodiments. Each piece of power amount data can be rearranged so that the storage locations of the consumer's power amount data in the data storage unit 30 are physically close to each other. Therefore, the same effects as in the first and second embodiments can be obtained.

Note that in this embodiment, an example has been described in which the data management device 1a according to the second embodiment directly acquires power amount data from the data collection system 100, but the data management device according to the first embodiment It is also possible for the device 1 to directly acquire power amount data from the data collection system 100.

The configurations shown in the embodiments described above are examples of the contents of the present invention, and can be combined with other known techniques, and the configurations can be modified without departing from the gist of the present invention. It is also possible to omit or change parts.

Reference Signs List 1, 1a, 1b data management device, 20, 20a, 20b data acquisition unit, 21, 21a, 21b relocation unit, 30 data storage unit, 40 calculation unit definition acquisition unit, 50 calculation unit definition storage unit, 100 data collection system , 101 smart meter, 200 storage device, 300 application server, 301 business function department.

Claims (4)

a data acquisition unit that acquires the power amount data from a storage device that stores the power amount data periodically transmitted from the smart meter in chronological order;
a data storage unit that stores the power amount data acquired by the data acquisition unit;
Equipped with
The data acquisition unit acquires the electricity amount data based on a contractor ID indicating a contractor from whom the consumer purchases electricity, and determines whether the electricity amount data of the consumers who purchase electricity from the same contractor are the same. a relocation unit that groups the power amount data of the same group into a certain range of a storage area constituting the data storage unit ;
The storage area includes a plurality of blocks that can be accessed at once by an external device, and the data acquisition unit stores power amount data of the same group in one block,
a calculation unit definition holding unit that holds a calculation unit definition that defines a calculation unit that is a unit for calculating wheeling charges;
Equipped with
The calculation unit is formed including one or more of the blocks,
The data acquisition unit stores power amount data of the same group in one calculation unit.
A data management device characterized by: a data acquisition unit that acquires the power amount data from a storage device that stores the power amount data collected from the smart meter;
a data storage unit that stores the power amount data acquired by the data acquisition unit;
Equipped with
The data acquisition unit groups each of the acquired power amount data so that the same group has the same electricity retailer contracted by the consumer where the smart meter from which the power amount data is collected is installed. and storing the same group of power amount data collectively in a certain range of a storage area that constitutes the data storage unit,
The storage area includes a plurality of blocks that can be accessed at once by an external device, and the data acquisition unit stores power amount data of the same group in one block,
a calculation unit definition holding unit that holds a calculation unit definition that defines a calculation unit that is a unit for calculating wheeling charges;
Equipped with
The calculation unit is formed including one or more of the blocks,
The data acquisition unit stores power amount data of the same group in one calculation unit.
A data management device characterized by: a calculation unit definition acquisition unit that acquires the calculation unit definition from outside;
3. The data management device according to claim 2 , further comprising: a. a data acquisition unit that acquires the power amount data from a data collection system that collects the power amount data periodically transmitted from the smart meter;
a data storage unit that stores the power amount data acquired by the data acquisition unit;
Equipped with
The data acquisition unit acquires the electricity amount data based on a contractor ID indicating a contractor from whom the consumer purchases electricity, and determines whether the electricity amount data of the consumers who purchase electricity from the same contractor are the same. a relocation unit that groups the power amount data of the same group into a certain range of a storage area constituting the data storage unit ;
The storage area includes a plurality of blocks that can be accessed at once by an external device, and the data acquisition unit stores power amount data of the same group in one block,
a calculation unit definition holding unit that holds a calculation unit definition that defines a calculation unit that is a unit for calculating wheeling charges;
Equipped with
The calculation unit is formed including one or more of the blocks,
The data acquisition unit stores power amount data of the same group in one calculation unit.
A data management device characterized by:

Images