WO2018179364A1 - Système informatique et procédé de contrôle de flux données - Google Patents

Système informatique et procédé de contrôle de flux données Download PDF

Info

Publication number
WO2018179364A1
WO2018179364A1 PCT/JP2017/013685 JP2017013685W WO2018179364A1 WO 2018179364 A1 WO2018179364 A1 WO 2018179364A1 JP 2017013685 W JP2017013685 W JP 2017013685W WO 2018179364 A1 WO2018179364 A1 WO 2018179364A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
sensor
tag
flow
report
Prior art date
Application number
PCT/JP2017/013685
Other languages
English (en)
Japanese (ja)
Inventor
耕一 村山
裕教 江丸
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2017/013685 priority Critical patent/WO2018179364A1/fr
Priority to JP2019508133A priority patent/JP6685468B2/ja
Publication of WO2018179364A1 publication Critical patent/WO2018179364A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]

Definitions

  • the present invention relates to a computer system and a data flow control method, for example, a computer system that monitors and analyzes on-site sensor data.
  • Cloud that collects data from the data provider system at the site, etc., and the data usage destination system monitors the data provider system, analyzes the data provider system, and uses this to improve the data provider system The system is realized.
  • Patent Document 1 a sensor on the site connected to a network is matched with metadata of an application on the sensor data use side so that sensor data meeting the requirements is distributed to the application.
  • the operation information of the operator side system as the data usage destination system is the data provider Feedback is made to the developer side system as a system.
  • the data usage destination system uses, for example, data outside the sensor, such as operation information of time sale events at the shop in the field, monitoring the field information, analyzing the sensor data, etc.
  • data outside the sensor such as operation information of time sale events at the shop in the field, monitoring the field information, analyzing the sensor data, etc.
  • the present invention provides a computer system and a data flow control method capable of appropriately controlling the flow of data outside the sensor in addition to the sensor data in controlling the data flow from the data providing source system to the data using destination system. Objective.
  • a data providing source system is a first management device that manages a device having a sensor, sensor data that is sensor detection data, and tag data that associates data that cannot be directly acquired from the sensor with sensor data.
  • the data use destination system includes a second management device that executes data management using the sensor data based on the tag data, and the data control computer moves from the data providing source system to the data use destination system.
  • Sensor data flow from the data provider system to the data destination system Sensor data sent to the data utilization destination system based on the sensor data flow when the tag data flow is controlled, the tag data flow is determined to be updated, and the determination is affirmative. From this, the tag data transmitted to the data utilization destination system is determined, and the tag data flow is updated based on the determination.
  • the data providing source system uses the detection data of the sensor by the first management device.
  • Some sensor data and tag data in which data that cannot be directly acquired from the sensor is associated with the sensor data are respectively managed, and the data use destination system uses the second management device to manage the sensor data based on the tag data.
  • the data control computer executes the sensor data flow from the data providing source system to the data using destination system, and the tag data flow from the data providing source system to the data using destination system, respectively.
  • Control determine whether the tag data flow needs to be updated, and Then, based on the sensor data flow, the tag data transmitted to the data usage destination system is determined from the sensor data transmitted to the data usage destination system, and the tag data flow is updated based on the determination. did.
  • the present invention provides a computer system and a data flow control method capable of appropriately controlling the flow of data outside the sensor in addition to the sensor data in the control of the data flow from the data providing source system to the data using destination system. be able to.
  • reference numeral 1 denotes a report management system as a computer system according to this embodiment as a whole.
  • This report management system 1 defines sensor data and tag data usage information, which is data obtained by adding on-site information (tags) to sensor data, and generates reports in the form of figures, tables, etc. based on the usage information System to manage.
  • the report management system 1 includes one or more data providing source systems 2, one or more data use destination systems 3, and a data control computer 4, which are connected to each other via a network 5.
  • the network 5 is a network such as a LAN or a WAN, and is provided by wire or wireless.
  • the data providing source system 2 is a system that provides data in its own system to an external system, and is a system that operates on the site such as a store, an airport, a factory, a construction site, an event site, etc. This is referred to as a sensor management computer) and one or more IoT devices 7.
  • the data provider system 2 is a store system, and the IoT device 7 is installed on each floor of the store. Then, the data providing source system 2 acquires, as tags, images in the store, audio, information related to time sales for the installation floor and the entire store, information related to device maintenance, and the like.
  • the sensor management computer 6 is a computer that manages the IoT device 7 and the sensor 25 in the data providing source system 2, and includes a CPU 8, a memory 9, an input / output device 10, a storage device 11, and a network interface 12. Are connected by an internal bus 13.
  • the CPU 8 is a processor that controls the operation of the entire sensor management computer 6.
  • the memory 9 is composed of, for example, a volatile semiconductor memory and is used as a work memory for the CPU 8.
  • the memory 9 temporarily stores a sensor management program 14 that is a program for managing sensor data and a tag management program 17 that is a program for managing tag data when necessary.
  • the input / output device 10 includes, for example, a keyboard, a mouse, and a display, and is used when necessary information such as definition of tag data is input by an operation manager, for example.
  • the storage device 11 is composed of a large-capacity nonvolatile storage device such as a hard disk device or SSD (Solid State Drive), and is used for storing and holding programs and data for a long period of time.
  • a program stored in the storage device 11 is loaded into the memory 9, and the CPU 8 executes this program to execute various processes as the entire report management system 1.
  • the storage device 11 stores and holds a sensor management program 14 and a tag management program 17.
  • the network interface 12 is composed of, for example, a NIC (Network Interface Card) or the like, and performs protocol control during communication with the data use destination system 3, the data control computer 4, the IoT device 7, and the like.
  • NIC Network Interface Card
  • the IoT device 7 is a device that collects information in the data providing source system 2 by the sensor 25 and transmits it to a computer in the data providing source system 2 or a computer outside the data providing source system 2, and includes a CPU 20, a memory 21, An input / output device 22, a storage device 23, a network interface 24, and one or more sensors 25 are connected to each other via an internal bus 26.
  • the CPU 20 is a processor that controls the operation of the entire IoT device 7.
  • the memory 21 is composed of, for example, a volatile semiconductor memory and is used as a work memory for the CPU 20.
  • the input / output device 22 includes, for example, a keyboard, a mouse, and a display, and is used when necessary information such as sensor setting information is input by an operation manager, for example.
  • the storage device 23 is composed of a large-capacity nonvolatile storage device such as a hard disk device or SSD (Solid State Drive), and is used for storing and holding programs and data for a long period of time.
  • a program stored in the storage device 23 is loaded into the memory 21, and the CPU 20 executes the program to execute various processes as the entire report management system 1.
  • the network interface 24 is composed of, for example, a NIC (Network Interface Card) or the like, and performs protocol control during communication with the data use destination system 3, the data control computer 4, the sensor management computer 6, and the like.
  • NIC Network Interface Card
  • the sensor 25 is a device that measures and collects sensor data such as images, moving images, sounds, positions, pressures, accelerations, angles, temperatures, and humidity in the data provider system 2.
  • the IoT device 7 converts the sensor data acquired from this sensor into a data format that can be handled by each program in the report management system 1 and transmits it.
  • the data usage destination system 3 is a system that monitors and analyzes the status of the data providing source system 2 based on the field data provided from the data providing source system 2, and includes a user terminal 27 and a second management device (hereinafter referred to as a “second management device”). This is called a report management computer) 28.
  • the user terminal 27 is a PC, a smartphone, or the like operated by a user such as a developer or an operation manager who uses the report management system 1, and includes a CPU 29, a memory 30, an input / output device 31, a storage device 32, and a network interface 33. Each device is connected by an internal bus 34.
  • the CPU 29 is a processor that controls operation of the entire user terminal 27.
  • the memory 30 is composed of, for example, a volatile semiconductor memory and is used as a work memory for the CPU 29.
  • a user interface program 35 which will be described later, is temporarily stored in the memory 30 when necessary.
  • the input / output device 31 includes, for example, a keyboard, a mouse, and a display.
  • the user defines tag data, sets sensor data transmission destination (hereinafter referred to as sensor data flow definition), and sensor data at the user terminal.
  • tag data usage information hereinafter, this may be used as data management information).
  • the storage device 32 is composed of a large-capacity nonvolatile storage device such as a hard disk device or an SSD (Solid State Drive), and is used for storing and holding programs and data for a long period of time.
  • a program stored in the storage device 32 is loaded into the memory 30, and the CPU 29 executes the program to execute various processes as the entire report management system 1.
  • the storage device 32 stores and holds a user interface program 35.
  • the network interface 33 is composed of, for example, a NIC (Network Interface Card) or the like, and performs protocol control during communication with the data providing source system 2, the data control computer 4, the report management computer 28, and the like.
  • NIC Network Interface Card
  • the report management computer 28 is a computer that generates and displays a report for monitoring and analyzing the site of the data providing source system 2 based on the sensor data and the tag data acquired from the data providing source system 2, and includes a CPU 36, a memory 37, The system includes an input / output device 38, a storage device 39, and a network interface 40. Each device is connected by an internal bus 41.
  • the CPU 36 is a processor that controls the operation of the entire report management computer 28.
  • the memory 37 is composed of, for example, a volatile semiconductor memory and is used as a work memory for the CPU 36.
  • a report management program 42 is temporarily held in the memory 37 when necessary.
  • the report management program 42 is a program that generates and displays a report for monitoring and analyzing the site of the data providing source system 2 based on the sensor data and the tag data acquired from the data providing source system 2.
  • the input / output device 38 includes, for example, a keyboard, a mouse, and a display, and is used when, for example, a developer inputs definitions of sensor data and tag data usage information on a user terminal.
  • the storage device 39 is composed of a large-capacity nonvolatile storage device such as a hard disk device or SSD (Solid State Drive), and is used for storing and holding programs and data for a long period of time.
  • a program stored in the storage device 39 is loaded into the memory 37, and the CPU 36 executes the program to execute various processes as the entire report management system 1.
  • the storage device 39 stores and holds the report management program 42.
  • the network interface 40 is composed of, for example, a NIC (Network Interface Card) or the like, and performs protocol control when communicating with the data providing source system 2, the data control computer 4, the user terminal 27, and the like.
  • NIC Network Interface Card
  • the data control computer 4 is a computer that processes and controls data exchanged between the data providing source system 2 and the data use destination system 3, and includes a CPU 48, a memory 49, an input / output device 50, a storage device 51, and a network interface 52. Each device is connected by an internal bus 53.
  • the CPU 48 is a processor that controls the operation of the entire data control computer 4.
  • the memory 49 is composed of, for example, a volatile semiconductor memory and is used as a work memory for the CPU 48.
  • the memory 49 temporarily stores a sensor data processing program 54 and a tag data flow control program 58 when necessary.
  • the sensor data processing program 54 is a program for processing sensor data received from the IoT device 7 operating in the data providing source system 2, and performs processing such as analysis of the sensor data and receives it based on the sensor data flow definition.
  • the processed sensor data and the processed sensor data are transmitted to the report management computer 28 of the appropriate data usage destination system 3.
  • the tag data flow control program 58 is a program for transmitting the tag data defined by the tag management program 17 to the report management computer 28 of the appropriate data usage destination system 3.
  • the input / output device 50 includes, for example, a keyboard, a mouse, and a display, and is used when, for example, information on a transmission destination of sensor data is input by a developer.
  • the storage device 51 is composed of a large-capacity nonvolatile storage device such as a hard disk device or SSD (Solid State Drive), and is used for storing and holding programs and data for a long period of time.
  • a program stored in the storage device 51 is loaded into the memory 49, and the CPU 48 executes the program to execute various processes as the entire report management system 1.
  • the storage device 32 stores and holds a sensor data processing program 54 and a tag data flow control program 58.
  • the network interface 52 is composed of, for example, a NIC (Network Interface Card) or the like, and performs protocol control during communication with the data providing source system 2, the data use destination system 3, and the like.
  • NIC Network Interface Card
  • the report management system 1 is equipped with a report management function for displaying and managing sensor data and tag data information collectively in a diagram or table as a report based on various definition information input by a user.
  • the user interface program 35 of the report management system 1 displays the definition screen 70 shown in FIG. 2, and the user defines the tag definition from the tag definition screen 71 of the definition screen 70 and the sensor data flow definition from the sensor data flow definition screen 72. Each definition is input from the report definition screen 73 as report definition information.
  • the report management system 1 determines a transmission destination of tag data from the input tag definition, sensor data flow definition, and report definition information.
  • the tag definition screen 71 is a screen on which a tag definition, which is related information (tag data) between sensor data and information on the site of the data providing source system 2, is input by the user.
  • the tag name column 71A, the schedule column 71B, and the sensor A column 71C is provided.
  • a tag name is input to the tag name column 71A
  • a schedule is input to the schedule column 71B in the format of “start time-end time”. Note that the schedule is in one of three types: date only, time only, and date and time.
  • the sensor column 71C displays a list of sensor IDs of the IoT device 7, and one or more sensor IDs are selected and input by the user.
  • the sensor data flow definition screen 72 is a screen in which a sensor data flow definition, which is sensor data flow control information on where to send sensor data, is input by a user, and includes a transmission source column 72A and a transmission destination column 72B. Is done.
  • the transmission source column 72A is input with the transmission source of the sensor data
  • the transmission destination column 72B is input with the transmission destination of the sensor data by separating a plurality of values with commas.
  • the report definition screen 73 is a screen on which a report definition, which is usage information indicating what kind of report is displayed using the sensor data and tag data received by the data usage destination system 3, is entered by the user.
  • a column 73A, a reference data column 73B, and a range column 73C are provided.
  • the report name is input in the report name column 73A
  • the range is input in the format of “start date-end date” in the range column 73C.
  • a list of sensor IDs of the IoT device 7 is displayed as reference data, and one or more sensor IDs are selected and input by the user.
  • tag definition screen 71 the sensor data flow definition screen 72, and the report definition screen 73 may not be displayed together as the definition screen 70, but may be displayed individually.
  • the transmission destination of the tag data can be confirmed from the tag definition screen 121 that can only be referred to as shown in FIG.
  • the user can confirm where the tag data is transmitted and how much the tag data is used.
  • the tag definition screen 121 includes a tag ID field 121A, a tag name field 121B, a transmission destination 121C, and a report number field 121D.
  • the tag ID field 121A includes a tag ID for uniquely identifying tag data.
  • the tag name is displayed in 121B
  • the transmission destination of tag data is displayed in the transmission destination 121C
  • the number of reports described later is displayed in the report number column 121D.
  • the report management system 1 creates a report based on information input from the tag definition screen 71, the sensor data flow definition screen 72, and the report definition screen 73.
  • FIG. 4 displays a report 80 created by the report management system 1.
  • the report 80 displays the volume of noise in the store A for each hour as a line graph 81 based on the sensor data information, and displays the report name 86 as “store A noise data”.
  • the report 80 displays information such as business hours 82, a time sale period 83, a sensor state abnormality 84, and a temporary maintenance period 85 as tag data with the tag name clearly displayed.
  • the sensor management program 14 is provided with a sensor configuration management module 15, a sensor monitoring module 16, and a sensor configuration table TB10.
  • the sensor configuration management module 15 is a program for managing the sensor configuration table TB10, and the sensor monitoring module 16 periodically monitors the IoT device 7 to be managed and determines whether or not an abnormality has occurred in the sensor 25. This is a program to check.
  • the sensor configuration table TB10 is a table for storing sensor configuration information, and includes a sensor ID column TB11, a device ID column TB12, a data type column TB13, and a status column TB14. .
  • a sensor ID for uniquely identifying the sensor 25 is stored.
  • the device ID column TB12 a device ID that uniquely identifies the IoT device 7 is stored.
  • the device ID is, for example, an IP address, a host name, a UUID, or the like used in the report management system 1 of the IoT device 7.
  • the data type column TB13 data types such as “image” and “sound” indicating data handled by the sensor 25 are stored.
  • the sensor data includes data that can be measured by the function of the IoT device 7 itself. Therefore, the data type includes data such as “CPU usage rate” and “memory usage rate”.
  • the sensor ID is stored in the sensor ID column TB11 in a format that combines a device ID such as “D003-1” and a unique ID in the IoT device 7. Is done.
  • the status column TB14 stores a status such as “normal” or “abnormal” indicating whether the IoT device 7 or the sensor 25 can normally collect and transmit sensor data. The status is periodically updated by the sensor monitoring module 16.
  • the tag management program 17 includes a tag management module 18, a tag transmission module 19, and a tag definition table TB20.
  • the tag management module 18 is a program for registering, referring to, editing, and deleting tag data by managing tag data related to the IoT device 7 and the sensor 25 using the tag definition table TB20.
  • the tag transmission module 19 monitors the tag definition table TB20, and when the tag data of the tag definition table TB20 is updated by an input from the tag definition screen 71, the updated tag data is transmitted to the tag data flow control program 58. It is a program.
  • the tag definition table TB20 is a table for storing tag data, and includes a tag ID column TB21, a tag name column TB22, a schedule column TB23, and a related ID column TB24.
  • tag ID column TB21 a tag ID for uniquely identifying tag data is stored.
  • the tag name column TB22 stores the name of the tag data.
  • the schedule column TB23 stores a period or time when an on-site event occurs. For example, the period when the event at the site occurs is the business hours, the time sale period, and the temporary maintenance period of the store A when the IoT device 7 is permanently installed in the store A.
  • the sensor ID included in the tag data is stored in the related ID column TB24.
  • the sensor ID stored in the related ID column TB24 is selected from the sensor IDs stored in the sensor ID column TB11 in the sensor configuration table TB10.
  • the report management program 42 includes a sensor data reception module 43, a tag reception module 44, a report management module 45, a report base generation module 46, a tag synthesis module 47, a sensor data table TB30, a tag data table TB40, and a report metadata table TB50. Is provided.
  • the sensor data receiving module 43 receives the sensor data collected by the data providing source system 2 and the sensor data processed by the data control computer 4, and stores the sensor data and the processed sensor data in the sensor data table TB30. It is.
  • the tag receiving module 44 is a program that receives tag data defined by the data providing system 2 and transferred by the data control computer 4 and stores the tag data in the tag data table TB40.
  • the report management module 45 is a program that defines a report definition that is the contents of a report based on information input on the report definition screen 73 and stores the report definition in the report metadata table TB50.
  • the report base generation module 46 acquires sensor data and the like from the sensor data table TB30 based on the report definition of the report metadata table TB50, and generates a figure, a table, a graph and the like as a report base based on the sensor data and the like It is.
  • the tag synthesis module 47 acquires tag data from the tag data table TB40 based on the report definition of the report metadata table TB50, synthesizes the tag with the report base generated by the report base generation module 46, and generates a report 80 It is.
  • the sensor data table TB30 is a table for storing sensor data transmitted from the IoT device 7 and sensor data processed by the data control computer 4, and includes a sensor ID column TB31 and a time column TB32.
  • the data column TB33 is provided.
  • the sensor ID column TB31 stores the sensor ID of the sensor ID column of the sensor configuration table TB10 that is the sensor ID of the sensor 25 that is the generation source of the received sensor data.
  • the time column TB32 stores a period during which sensor data is measured.
  • sensor data measured by the sensor 25 or sensor data processed by the sensor data processing program 54 is stored.
  • sensor data for example, in the case of image data, “Image” is stored in the data column TB33 as a data type and a byte string of image data as a data value, such as “Image: ⁇ first image data>”. Is done.
  • As the processed sensor data for example, in the case of audio data, “dB: ⁇ value>”, “dB” is stored as the data type, and the sound pressure value is stored in the data column TB33 as the data value. .
  • the tag data table TB40 is a table having the same configuration as the tag definition table TB20, but only the tag data to be stored is included in the report definition of the report management program 42. This is different from the tag definition table TB20.
  • the report metadata table TB50 is a table that stores report definitions defined by the report management program.
  • a report type column TB55 is provided.
  • a report ID that is an ID for uniquely identifying the report 80 is stored.
  • the report ID is created by the report management module 45.
  • the report name column TB52 a character string indicating the name of the report 80 input on the report definition screen 73 is stored.
  • the reference data column TB53 one or more sensor IDs used for report generation are selected from the sensor data table TB30 and stored.
  • the data range column TB54 stores a time range for generating the report 80, which is input on the report definition screen 73.
  • a report type indicating the display format of the report 80 is stored in the report type column TB55.
  • the report type is, for example, “table” in which the display format of the report 80 is a table format, “line” in which the display format of the report 80 is a line graph format for each time series.
  • formats suitable for displaying sensor data such as a pie chart format and a bar graph format are prepared as report types.
  • the sensor data processing program 54 is provided with a sensor data flow management module 55, a sensor data processing module 56, a sensor data flow control module 57, and a sensor data flow table TB60.
  • the sensor data flow management module 55 is a program that manages the transmission destination for each sensor data received from the IoT device 7 and registers, refers to, edits, and deletes the sensor data flow according to the sensor data flow definition.
  • the sensor data flow management module 55 stores the sensor data flow definition in the sensor data flow table TB60.
  • the sensor data processing module 56 is a program for performing processing such as analysis and processing on the sensor data received by the sensor data processing program 54. For example, if the received sensor data is image data, the sensor data processing module 56 performs identification of a person shown in the image, analysis of the number of persons, and the like. When the received sensor data is voice data, the sensor data processing module 56 analyzes conversation contents, extracts a volume, and the like. After processing the sensor data, the sensor data processing module 56 transmits the processed sensor data to the sensor data flow control module 57. When sensor data processing is unnecessary, the sensor data processing module 56 transmits the sensor data as it is to the sensor data flow control module 57.
  • the sensor data flow control module 57 reports the sensor data received from the sensor data processing module 56 and the processed sensor data based on the transmission destination for each sensor data registered in the sensor data flow table TB60 to the report management program 42. Is a program to send to.
  • the sensor ID of the sensor data is information on the transmission source.
  • the sensor data flow table TB60 is a table that defines a transmission destination of sensor data received by the sensor data processing program 54, and includes a transmission source ID column TB61 and a transmission destination column TB62. .
  • the transmission source ID column TB61 stores a sensor ID indicating the transmission source of the sensor data
  • the transmission destination column TB62 stores an ID indicating the report management computer 28 that is the transmission destination of the sensor data.
  • the ID indicating the report management computer 28 is, for example, a host name, an IP address, or the like set in the report management computer 28.
  • the tag data flow control program 58 is provided with a tag data flow management module 59, a tag data flow control module 60, and a tag data flow table TB70.
  • the tag data flow management module 59 is a program that manages the transmission destination of the tag data.
  • the sensor data flow definition stored in is monitored, and if any one or more tables are updated, the report management computer 28 as the tag data transmission destination is determined and the tag data flow table TB70 is updated. It is a program to do.
  • the tag data flow control module 60 is a program that transmits tag data to the report management computer 28 based on the transmission destination of the tag data stored in the tag data flow table TB70.
  • the tag data flow table TB70 is a table for storing tag data flow control information that defines a transmission destination of tag data, and includes a tag ID column TB71 and a transmission destination column TB72.
  • the tag ID column TB71 stores the tag ID of the tag ID column TB21 of the tag definition table TB20
  • the transmission destination column TB72 stores an ID indicating the report management computer 28 that is the transmission destination of the tag data.
  • the ID indicating the report management computer 28 is, for example, a host name, an IP address, or the like set in the report management computer 28.
  • the number of reports described above can be obtained by counting the number of report IDs with overlapping sensor IDs and time ranges stored in the tag data table TB40 and the report metadata table TB50 at the transmission destination in the transmission destination column TB72.
  • FIG. 12 shows a processing procedure for tag data flow update processing executed by the tag data flow management module 59.
  • the tag data flow management module 59 updates the tag data flow table TB70 according to the processing procedure shown in FIG.
  • the tag data flow management module 59 detects the update of any one or more of the tag definition table TB20, the report metadata table TB50, and the sensor data flow table TB60, the tag data flow shown in FIG. Start the update process.
  • the tag data flow management module 59 first acquires the data of the tag definition table TB20 from the tag management program 17, and extracts a sensor related to the tag data whose update has been detected (SP11). Specifically, the value in the related ID column TB24 is compared with the value in the column storing the sensor ID in the updated table, and the matched sensor ID is extracted.
  • the tag data flow management module 59 acquires the data of the sensor data flow table TB60 from the sensor data processing program 54, extracts the transmission destination of the sensor data of the extracted sensor (SP12), and transmits the transmission destination of the tag data. Narrow down the report management computer 28. Specifically, the transmission destination in the transmission destination column TB62 in the sensor data flow table TB60 corresponding to the sensor ID extracted in step SP11 is extracted. However, the report definition is not made at this point, and the transmission destinations that do not need to transmit the tag data are also included.
  • the tag data flow management module 59 obtains the report metadata table TB50 from the report management program 42 of the report management computer 28 narrowed down as the transmission destination of the tag data, and extracts the sensor data used for the report definition. (SP13). Specifically, the sensor ID extracted in step SP12 is compared with the sensor ID in the reference data column TB53 of the report metadata table TB50, and the matched sensor ID is extracted.
  • the tag data flow management module 59 updates the tag data flow by updating the tag data flow table TB70 (SP14). Specifically, the tag data flow management module 59 refers to the tag ID in the tag ID column TB21 in the tag definition table TB20 corresponding to the sensor ID extracted in step SP13. Then, the tag data flow management module 59 updates the tag data flow by storing the transmission destination extracted in step SP12 in the transmission destination column TB72 of the tag data flow table TB70 corresponding to the tag ID. If the sensor ID cannot be extracted in step SP13, the tag data flow management module 59 ends the tag data flow update process as it is.
  • the tag data flow management module 59 determines whether there is tag data within the time range defined in the report definition (SP15). Specifically, the tag data flow management module 59 determines whether or not there is an overlapping portion of the time range between the time range in the data range column TB54 corresponding to the sensor ID extracted in step SP13 and the time range in the schedule column TB23. . If there is no tag data within the time range defined in the report definition and a negative result is obtained in the determination at step SP15, the tag data flow management module 59 ends the tag data flow update process.
  • the tag data flow management module 59 performs report management on the tag data within the time range.
  • the tag data flow control module 60 is instructed to transmit to the computer 28 (SP16), and the tag data flow update process is terminated.
  • the tag data flow control module 60 transmits tag data within the time range to the report management computer 28.
  • FIG. 13 shows a processing procedure for report display processing executed by the report management program 42.
  • the report management program 42 displays the report 80 shown in FIG. 4 according to the processing procedure shown in FIG.
  • the report management program 42 starts the report display processing shown in FIG. 13 when a report display is requested by designating a report name via the input / output device 31, for example.
  • the report base generation module 46 first refers to the report metadata table TB50 and generates a report base based on the report definition corresponding to the designated report name (SP21).
  • the report base generation module 46 acquires the sensor data in the time range of the data range column TB54 from the sensor data table TB30 among the sensor IDs stored in the reference data column TB53. Then, the report base generation module 46 generates a report base in the format stored in the report type column TB55.
  • FIG. 4 shows a case where “Store A noise data” is designated as the report name.
  • the tag synthesis module 47 acquires tag data from the tag data table TB40 (SP22).
  • This acquired tag data has the sensor ID of the reference data column TB53 corresponding to the specified report name as the sensor ID of the related ID column TB44, and the time range of the schedule column TB43 in the time range of the data range column TB54. Is included in the data.
  • the tag synthesis module 47 synthesizes the tag with the report base generated by the report base generation module 46 (SP23). Specifically, the tag synthesis module 47 displays the tag over the time range of the tag data acquired in step SP22 on the report base.
  • the tag data flow control program 58 manages tag data using the tag data flow table TB70, so that the tag definition table TB20.
  • the transmission destination of the tag data is changed based on the change of the report metadata table TB50 and the sensor data flow table TB60.
  • the tag data transmission destination is dynamically and appropriately changed, so that a large amount of sensor data is exchanged and the situation of the data provider and the definition of the report are updated every day. It is possible to add additional information to the report without setting.
  • the user can change the information for displaying the report without being aware of the transmission destination of the tag data which is the additional information, and the data providing source and the data using destination can be changed. It is possible to realize a computer system and a data flow control method that can exchange appropriate additional information without waste.
  • the present invention is not limited to this, and the report management program 42 may access the data provider system 2 to acquire tag data.
  • FIG. 14 shows the configuration of the report management system 90 when the report management program 42 accesses the data provider system 2.
  • the report management system 90 is different from the report management system 1 in that a tag data access control program 93 is provided instead of the tag data flow control program 58. Only this difference will be described.
  • the tag data access management module 94 included in the tag data access control program 93 performs a tag data access update process shown in FIG. Steps SP11 to SP14 of the tag data access update process are the same as steps SP31 to SP34 of the tag data flow update process, and a description thereof will be omitted.
  • the tag data access management module 94 uses an access unit (hereinafter referred to as an API) such as REST API (Representational State Transfer Application State Programming API) for accessing the tag data of the tag data flow table TB70 as tag data access management.
  • an API such as REST API (Representational State Transfer Application State Programming API)
  • REST API Real State Transfer Application State Programming API
  • tag data access management module 94 only has a request ID requesting access to tag data stored in the transmission destination column TB72 as a transmission destination, and the tag ID column TB71 corresponding to the transmission destination. It controls so that the tag data of the tag ID stored in can be accessed.
  • FIG. 16 shows a configuration of the report management system 100 when the information from the third management apparatus (hereinafter referred to as a base management computer) 102 is diverted.
  • the report management system 100 is different from the report management system 1 in that it further includes one or more site management computers 102. Only this difference will be described.
  • the base management computer 102 is a computer for managing the site where the IoT device 7 of the data providing source system 101 is installed as a base, and the memory 104 stores a base management program that is a program for managing base information. 109 is temporarily held when necessary. Note that the hardware configuration of the base management computer 102 is the same as that of the data control computer 4 and the like, and thus the description thereof is omitted.
  • the function of the site management program 109 differs depending on the type of business of the site, but here, a case where the data providing source system 2 is a system that operates at a store will be described.
  • the site management program 109 includes a site management module 110, a store business hours table TB80, a system operation schedule table TB90, and a system event management table TB100.
  • the base management module 110 has a business hours management function managed by the store business hours table TB80 for managing the business hours of the stores, and an operation schedule management for managing the operation schedules of the respective IoT devices 7 operating at the stores by the system operation schedule table TB90.
  • This is a program having a system event management function for managing the function and the state of each IoT device 7 and each sensor 25 operating in the store by the system event management table TB100.
  • the site management module 110 registers, references, updates, deletes values stored in the store business hours table TB80, the system operation schedule table TB90, and the system event management table TB100.
  • the store business hours table TB80 is a table for storing store business hours, and includes a store ID column TB81, a store name column TB82, and a business hours column TB83.
  • Store ID column TB81 which stores a store uniquely showing a store is stored. This store ID is numbered sequentially from 1 at the time of store registration.
  • Store name column TB82 stores a store name indicating the name of the store. This store name is used as a tag name in the tag definition.
  • the business hours column TB83 stores the business hours of the store in the format of “opening time-closing time”. The business hours of this store are used as a schedule in tag definition.
  • the system operation schedule table TB90 is a table for storing an operation schedule of the IoT device 7, and includes an event ID column TB91, an event name column TB92, and a schedule column TB93.
  • the event ID column TB91 stores an event ID that uniquely identifies the operation schedule. This event ID is numbered sequentially from 1 when the operation schedule occurs.
  • the event name column TB92 stores an event name indicating the contents of the operation schedule. This event name is used as a tag name in the tag definition.
  • the schedule column TB93 the operation schedule is stored in the format of “start time-end time”. This operation schedule is used as a schedule in the tag definition.
  • the system event management table TB100 is a table for storing status abnormalities and the like of the IoT device 7 and the sensor 25, and includes a time column TB101, an event ID column TB102, an event name column TB103, and a target sensor column TB104. It is configured with.
  • the time column TB101 stores the time when the state abnormality occurred. This time is used as a schedule in the tag definition.
  • the event ID column TB102 stores an event ID that uniquely identifies a state abnormality or the like. This event ID is numbered in order from 1 when a state abnormality occurs.
  • the event name column TB103 stores an event name indicating contents such as a state abnormality. This event name is used as a tag name in the tag definition.
  • the target sensor column TB104 stores the sensor ID of the sensor in which an error or warning has occurred. This sensor ID is used in the tag definition. When a plurality of sensor IDs are stored in the target sensor column TB104, they are separated by commas or the like.
  • the tag management program 17 accesses the base management program 109 of the base management computer 102 when accepting the input of the tag definition, and stores business hours Information corresponding to the tag name column 71A, schedule column 71B, and sensor column 71C is acquired from the table TB80, system operation schedule table TB90, and system event management table TB100, and acquired in the tag name column 71A, schedule column 71B, and sensor column 71C. Display information as initial value. By displaying the initial value in this way, the user only has to input the change from the initial value, and the input load on the user is reduced.
  • the data providing system 2 is a store system
  • the present invention is not limited to this, and the data providing system 2 may be a system installed at an airport.
  • the data providing source system 2 acquires the airport name, gate number, flight information, boarding rate, and the like as tags.
  • the present invention is not limited to this, and the sensor 25 may be externally attached to the IoT device 7 and connected via the network interface 204.
  • the present invention is not limited to this.
  • the tag definition is input from the input / output device 10 of the sensor management computer 6 as needed by the operation manager
  • the sensor data flow definition is input from the input / output device 50 of the data control computer 4 as needed by the developer. May be input from the report management computer 28 by the developer at any time.
  • the present invention is not limited to this, and the user terminal 27 is other than the data usage destination system 3. You may make it operate

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)

Abstract

Le problème décrit par la présente invention est de fournir un système informatique et un procédé de contrôle de flux de données capables de contrôler un flux de données d'un système de fournisseur de données à un système d'utilisateur de données de manière à contrôler de manière appropriée un flux de données sans capteur ainsi qu'un flux de données de capteur. La solution selon l'invention porte sur un ordinateur de commande de données qui est conçu pour : contrôler à la fois un flux de données de capteur d'un système de fournisseur de données à un système d'utilisateur de données et un flux de données d'étiquette du système de fournisseur de données au système d'utilisateur de données; déterminer si le flux de données d'étiquette doit être mis à jour ou non; et si la détermination est affirmative, déterminer des données d'étiquette qui doivent être transmises au système d'utilisateur de données, sur la base du flux de données de capteur et sur la base de données de capteur à transmettre au système d'utilisateur de données, et mettre à jour le flux de données d'étiquette sur la base de cette détermination.
PCT/JP2017/013685 2017-03-31 2017-03-31 Système informatique et procédé de contrôle de flux données WO2018179364A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2017/013685 WO2018179364A1 (fr) 2017-03-31 2017-03-31 Système informatique et procédé de contrôle de flux données
JP2019508133A JP6685468B2 (ja) 2017-03-31 2017-03-31 計算機システム及びデータフロー制御方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2017/013685 WO2018179364A1 (fr) 2017-03-31 2017-03-31 Système informatique et procédé de contrôle de flux données

Publications (1)

Publication Number Publication Date
WO2018179364A1 true WO2018179364A1 (fr) 2018-10-04

Family

ID=63677435

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2017/013685 WO2018179364A1 (fr) 2017-03-31 2017-03-31 Système informatique et procédé de contrôle de flux données

Country Status (2)

Country Link
JP (1) JP6685468B2 (fr)
WO (1) WO2018179364A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014041826A1 (fr) * 2012-09-12 2014-03-20 オムロン株式会社 Dispositif de production d'une instruction de régulation de flux de données et dispositif de gestion de capteur
JP2015226102A (ja) * 2014-05-26 2015-12-14 オムロン株式会社 仮想センサのメタデータ構造

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014041826A1 (fr) * 2012-09-12 2014-03-20 オムロン株式会社 Dispositif de production d'une instruction de régulation de flux de données et dispositif de gestion de capteur
JP2015226102A (ja) * 2014-05-26 2015-12-14 オムロン株式会社 仮想センサのメタデータ構造

Also Published As

Publication number Publication date
JPWO2018179364A1 (ja) 2019-06-27
JP6685468B2 (ja) 2020-04-22

Similar Documents

Publication Publication Date Title
US11181382B2 (en) Generating maps of private spaces using mobile computing device sensors
AU2017261597B2 (en) Portal for automatic software installation and configuration
US20150215376A1 (en) Systems and methods for deploying legacy software in the cloud
WO2012010599A1 (fr) Gestion et optimisation des flux de production entre des applications informatiques
US9888084B2 (en) Automatic network domain diagnostic repair and mapping
US20170372010A1 (en) Using sensors and location to trigger events and share data
US10319210B2 (en) Translating building automation events into mobile notifications
US20090138510A1 (en) Method and apparatus for associating help desk ticket with affected data processing system
WO2018179364A1 (fr) Système informatique et procédé de contrôle de flux données
US20240089330A1 (en) Communication apparatus, server, communication system, and communication method
US20220291954A1 (en) Computer System and Field Operation Supporting Method
WO2019031161A1 (fr) Unité de gestion de capteur, dispositif de capteur, procédé de gestion de capteur, et programme de gestion de capteur
EP3896666A1 (fr) Intégration d'informations d'emplacement dans un système de lutte contre les incendies
CN110083509A (zh) 一种日志数据的规整方法及装置
JP2016208184A (ja) 管理装置、管理システム、管理方法、および管理用プログラム
US9612889B2 (en) Integrating applications
JP5233121B2 (ja) 画面表示情報連携方法および画面表示情報連携システム
JP2024007040A (ja) 遠隔監視制御システム及び遠隔監視制御方法
CN114466005A (zh) 物联网设备编排
WO2017199336A1 (fr) Dispositif de gestion de maintenance, système de gestion de maintenance et programme
JP2002157389A (ja) 工程管理方法、工程管理装置、および工程管理プログラムを記録したコンピュータ読み取り可能な記録媒体
JP2009157644A (ja) 統合運用管理システム、統合運用管理方法及びプログラム及び記録媒体

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17903937

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019508133

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17903937

Country of ref document: EP

Kind code of ref document: A1