WO2022107248A1 - Dispositif d'aide à la création d'écran de surveillance, procédé d'aide à la création d'écran de surveillance et programme d'aide à la création d'écran de surveillance - Google Patents

Dispositif d'aide à la création d'écran de surveillance, procédé d'aide à la création d'écran de surveillance et programme d'aide à la création d'écran de surveillance Download PDF

Info

Publication number
WO2022107248A1
WO2022107248A1 PCT/JP2020/043015 JP2020043015W WO2022107248A1 WO 2022107248 A1 WO2022107248 A1 WO 2022107248A1 JP 2020043015 W JP2020043015 W JP 2020043015W WO 2022107248 A1 WO2022107248 A1 WO 2022107248A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
screen
monitoring screen
update
monitoring
Prior art date
Application number
PCT/JP2020/043015
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 JP2021506004A priority Critical patent/JP6903247B1/ja
Priority to PCT/JP2020/043015 priority patent/WO2022107248A1/fr
Publication of WO2022107248A1 publication Critical patent/WO2022107248A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring

Definitions

  • This disclosure relates to a monitoring screen creation support device that supports the creation of a monitoring screen of a monitoring control system, a monitoring screen creation support method, and a monitoring screen creation support program.
  • a monitoring control system that monitors and controls the state of a monitoring control target such as a plant, a water treatment facility, or a railway facility is known.
  • a monitoring screen that displays the status of the monitoring and control target is displayed on the monitoring and control device.
  • the work of creating a monitoring screen is performed by the user operating a dedicated application installed on a terminal device such as a personal computer.
  • a terminal device such as a personal computer.
  • each user extracts the screen data, which is the monitoring screen data, to a shared folder such as a file server each time the work is completed. Every time I ported and started work, I was importing screen data from the shared folder, which was troublesome.
  • Patent Document 1 does not have a technique for creating a monitoring screen, but discloses a technique in which a server can easily collaborate with a plurality of users by sharing screen information of each terminal device.
  • the present disclosure has been made in view of the above, and is performed by a plurality of users while avoiding that the operation of creating a monitoring screen of one user is forcibly reflected on the monitoring screen being operated by another user.
  • the purpose is to obtain a monitoring screen creation support device that can support the monitoring screen creation work.
  • the monitoring screen creation support device of the present disclosure includes a storage unit, a screen display processing unit, a request reception unit, a conflict data detection unit, and a synchronization processing unit.
  • the storage unit stores screen data, which is data on the monitoring screen used in the monitoring control system.
  • the screen display processing unit causes a plurality of terminal devices operated by different users to editably display a monitoring screen based on screen data.
  • the request receiving unit receives an update request for the monitoring screen from a plurality of terminal devices whose monitoring screen is editably displayed by the screen display processing unit.
  • the conflict data detection unit detects conflict data, which is data in which the update target conflicts among the update requests from a plurality of terminal devices among the screen data when the update request is received from a plurality of terminal devices by the request reception unit. do.
  • conflict data is data in which the update target conflicts among the update requests from a plurality of terminal devices among the screen data when the update request is received from a plurality of terminal devices by the request reception unit. do.
  • the synchronization processing unit displays information indicating the contention state to be updated on at least one terminal device among the plurality of terminal devices, and the synchronization processing unit displays the information indicating the conflict status of the update target on at least one terminal device of the at least one terminal device. Let the user choose whether or not to confirm the update of the screen data based on the update request.
  • it is intended to support the work of creating a monitoring screen by a plurality of users while preventing the operation of creating a monitoring screen of one user from being forcibly reflected on the monitoring screen being operated by another user. It has the effect of being able to.
  • FIG. 1 shows an example of the confirmation screen displayed in the editor screen by the monitoring screen editor in the terminal apparatus which concerns on Embodiment 1.
  • the monitoring screen creation support device, the monitoring screen creation support method, and the monitoring screen creation support program according to the embodiment will be described in detail below based on the drawings.
  • FIG. 1 is a diagram showing an example of a configuration of an information processing system including a monitoring control device according to the first embodiment.
  • the information processing system 100 according to the first embodiment includes a monitoring control system 1, terminal devices 2 1 , 2 2 , ..., 2n , and a monitoring screen creation support device 3. .. n is, for example, an integer of 3 or more.
  • the terminal device 2 1 , 2 2 , ..., 2 n and the monitoring screen creation support device 3 are connected to each other so as to be communicable via the network 4.
  • the network 7 is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network).
  • the network 4 is a WAN such as the Internet.
  • the monitoring control system 1 monitors and controls the status of the monitoring control target.
  • the monitoring and control target is, for example, a plant such as a power receiving / distributing plant or an electric power plant, a substation, a power plant, a water treatment facility, a railway facility, or the like.
  • the monitoring control system 1 includes equipment 5 1 to 5 m and a monitoring control device 6.
  • m is an integer of 2 or more.
  • Each device 5 1 to 5 m is a device constituting a monitoring control target.
  • Each device 5 1 to 5 m is, for example, a pump, a solenoid valve, or a blower when the monitoring control target is a water treatment facility.
  • each device 5 1 to 5 m is, for example, a circuit breaker or a disconnector when the monitoring control target is a substation.
  • the devices 5 1 to 5 m are provided with a type of state measuring device according to the monitoring purpose, and from the devices 5 1 to 5 m , the data indicating the value measured by the state measuring device indicates the state to be monitored and controlled. It is output as the monitoring data shown.
  • the state measuring device is, for example, a flow rate sensor, a water level sensor, a characteristic detection sensor, or the like.
  • the characteristic detection sensor is a sensor that detects the concentration of NH 3 , a sensor that detects the concentration of NH 4+ , a sensor that detects the concentration of ammoniacal nitrogen, or the like when the monitoring control target is a sewage treatment plant.
  • the state measuring device is, for example, a voltage sensor, a current sensor, a temperature sensor, or the like when the monitoring control target is a substation.
  • the monitoring control device 6 is communicably connected to the devices 5 1 to 5 m via the network 7.
  • the network 7 is, for example, a LAN or a WAN.
  • the network 7 is a WAN such as the Internet.
  • the monitoring control device 6 includes a display unit (not shown) and an operation unit (not shown).
  • the monitoring control device 6 acquires monitoring data indicating the status of the monitoring control target from the devices 5 1 to 5 m via the network 7, and based on the acquired monitoring data, does not display a monitoring screen indicating the status of the monitoring control target. It is displayed on the illustrated display unit. As a result, the commander can grasp the state of the monitoring control target.
  • the monitoring control device 6 transmits control data indicating the control contents for controlling the devices 5 1 to 5 m to the devices 5 1 to 5 m based on the operation of the commander to the operation unit (not shown). Send via.
  • the devices 51 to 5 m are controlled by the control data.
  • the device 5 when each of the devices 5 1 to 5 m is shown without distinction, it may be referred to as the device 5.
  • the monitoring control device 6 is built in a cloud environment.
  • the cloud environment includes computer resources provided by the cloud service platform.
  • the cloud service platform is provided by a cloud service provider and includes, for example, PaaS (Platform as a Service). Since the monitoring control device 6 is built in a cloud environment, it may also be called a cloud server.
  • PaaS Platinum as a Service
  • the terminal devices 2 1 , 2 2 , ..., 2 n are operated by the users U 1 , U 2 , ..., Un .
  • the terminal device 2 1 is operated by the user U 1
  • the terminal device 2 2 is operated by the user U 2
  • the terminal device 2 n is operated by the user Un .
  • the terminal device 2 1 , 2 2 , ..., 2 n may be described as the terminal device 2
  • the users U 1 , U 2 , ..., U When each of n is shown without distinction individually, it may be described as user U.
  • the monitoring screen creation support device 3 supports the creation of the monitoring screen of the monitoring control device 6 by the user U of each terminal device 2. Creating such a monitoring screen also includes changing the monitoring screen.
  • the monitoring screen creation support device 3 is constructed in a cloud environment and may also be called a cloud server.
  • An application program such as a web browser or a dedicated editor is installed in the terminal device 2 so that the monitoring screen of the monitoring control system 1 can be created.
  • the user U causes the terminal device 2 to send the transmission request to the monitoring screen creation support device 3 by operating a web browser or a dedicated editor.
  • the monitoring screen creation support device 3 causes the terminal device 2 to editably display the monitoring screen of the monitoring control system 1 based on the transmission request from the terminal device 2. For example, the monitoring screen creation support device 3 transmits screen data to the terminal device 2, and the browser of the terminal device 2 displays the monitoring screen based on the screen data on the terminal device 2 in an editable manner.
  • the screen data is data for screen drawing including, for example, HTML (HyperText Markup Language) data, symbol data, character data, image data, audio data, and scripts.
  • the screen data includes, for example, symbol data, character data, image data, voice data, layout data, and the like. Data for.
  • each of the web browser and the dedicated editor that enables editing of the monitoring screen may be described as the monitoring screen editor.
  • the terminal device 2 causes the terminal device 2 to send an update request to the monitoring screen creation support device 3 by operating the monitoring screen editor.
  • the monitoring screen creation support device 3 updates the screen data based on the update request from the terminal device 2.
  • the update request includes update data for updating the screen data, and the monitoring screen creation support device 3 updates the screen data based on the data included in the update request.
  • the update data is the data of the portion of the screen data edited by the user U, or the screen data edited by the user U.
  • the monitoring screen creation support device 3 When the monitoring screen creation support device 3 receives update requests from a plurality of terminal devices 2, the monitoring screen creation support device 3 detects conflicting data, which is data in which the update target conflicts among the update requests from the plurality of terminal devices 2 among the screen data. do. When the conflict data is detected, the monitoring screen creation support device 3 causes at least one terminal device 2 of the plurality of terminal devices 2 to display information indicating the contention state to be updated, and the monitoring screen creation support device 3 of the at least one terminal device 2. Let the user U select whether or not to confirm the update of the screen data based on the update request.
  • conflicting data which is data in which the update target conflicts among the update requests from the plurality of terminal devices 2 among the screen data. do.
  • the monitoring screen creation support device 3 causes at least one terminal device 2 of the plurality of terminal devices 2 to display information indicating the contention state to be updated, and the monitoring screen creation support device 3 of the at least one terminal device 2. Let the user U select whether or not to confirm the update of the screen data based on the
  • the monitoring screen creation support device 3 monitors by a plurality of users U while avoiding that the operation of creating the monitoring screen of one user U is forcibly reflected on the monitoring screen being operated by another user U. It is possible to support the work of creating a screen.
  • FIG. 2 is a diagram showing an example of a monitoring screen according to the first embodiment.
  • the monitoring screen 90 shown in FIG. 2 has a plurality of symbols 91 1 , 91 2 , 91 3 , 91 4 , 91 5 , 91 6 , 91 7 , 91 8 , 91 9 , 91 10 , 91 11 , 91 12 , 91 13 , 91 14 ⁇ 91 15 ⁇ 91 16 ⁇ 91 17 ⁇ 91 18 ⁇ 91 19 ⁇ 91 20 ⁇ 91 21 ⁇ 91 22 ⁇ 91 23 are arranged.
  • Symbols 91 1 , 91 2 , 91 3 , 914 are symbols showing the figure of the pump, and symbols 91 5 , 916 , 917 are symbols showing the figure of the solenoid valve, and symbols 91 8 and 9 1 9 are shown.
  • 91 10 are symbols indicating the figure of the tank.
  • the symbols 91 11 are symbols indicating the figure of the blower.
  • Symbol 91 12 is a symbol showing a figure of a processing tank
  • symbol 91 13 is a symbol showing a figure of a bubble ejector.
  • the symbols 91 14 , 91 15 , 91 16 and 91 17 and 91 18 and 91 19 and 91 20 and 91 21 and 91 22 and 91 23 are symbols showing a figure of a pipe.
  • the symbols 91 1 to 91 23 may be described as the symbol 91.
  • FIG. 3 is a diagram showing an example of the configuration of the monitoring screen creation support device according to the first embodiment.
  • the monitoring screen creation support device 3 according to the first embodiment includes a communication unit 10, a storage unit 11, and a processing unit 12.
  • the communication unit 10 is communicably connected to the network 4 and transmits / receives information to / from each of the plurality of terminal devices 2 via the network 4.
  • the storage unit 11 includes a history data storage unit 20, a symbol data storage unit 21, a behavior data storage unit 22, a tag data storage unit 23, and a layout data storage unit 24.
  • the screen data of the monitoring screen 90 is stored by the symbol data storage unit 21, the behavior data storage unit 22, the tag data storage unit 23, and the layout data storage unit 24.
  • the history data storage unit 20 stores a history data table including history data which is data related to processing requests transmitted in the past from each terminal device 2 to the monitoring screen creation support device 3.
  • FIG. 4 is a diagram showing an example of a history data table stored in the history data storage unit according to the first embodiment. As shown in FIG. 4, the history data table stored in the history data storage unit 20 includes a "user ID (Identifier)", a "request type”, and a "time information”, and these information are associated with each other. There is.
  • the "User ID” is identification information unique to each user U.
  • the "request type” is data indicating the type of the processing request transmitted from the terminal device 2 and processed in the past by the monitoring screen creation support device 3.
  • the types of processing requests include transmission requests and update requests.
  • the transmission request is a request for transmitting screen data for forming the monitoring screen 90
  • the update request is a request for updating the screen data for forming the monitoring screen 90.
  • the "time information" is information indicating the date and time when the processing for the processing request transmitted from the terminal device 2 was executed by the monitoring screen creation support device 3.
  • the process for the process request is the screen data transmission process when the process request is a transmission request, and the screen data update process when the process request is an update request.
  • history data including "U001”, “update request” and “2020/12/21 10:55”, “U002”, “transmission request” and “2020/12 /” 21 10:35 ”is included, and historical data including“ U001 ”,“ transmission request ”, and“ 2020/12/21 10:00 ”is included.
  • the symbol data storage unit 21 stores a symbol data table including symbol data which is data of each symbol 91.
  • FIG. 5 is a diagram showing an example of a symbol data table stored in the symbol data storage unit according to the first embodiment. As shown in FIG. 5, the symbol data table stored in the symbol data storage unit 21 has "symbol ID”, “part ID”, “size”, “color arrangement”, “shadow”, “transparency”, and “rotation”. , And attribute information indicating the attributes of the symbol 91, such as "time information", which are associated with each other.
  • the "symbol ID” is identification information unique to each symbol 91 arranged on the monitoring screen 90.
  • the "part ID” is identification information unique to each part.
  • the parts are parts for the symbol 91 prepared in advance, and are, for example, pump parts, solenoid valve parts, blower parts, processing tank parts, piping parts, and the like.
  • the component may be a circle, a rectangle, a straight line, a curve, a figure, a button, a three-dimensional object, or the like. In this case, the symbol 91 is created by one or more components.
  • Size is information on the size of the symbol 91
  • color scheme is information on the color of the symbol 91
  • shadow is information on the shadow provided on the symbol 91
  • transparency is information on the symbol 91.
  • rotation is information on the rotation angle of the symbol 91
  • time information is information on the time when the symbol 91 is created or changed.
  • the behavior data storage unit 22 stores a behavior data table including behavior data which is data that defines the behavior of each symbol 91.
  • FIG. 6 is a diagram showing an example of a behavior data table stored in the behavior data storage unit according to the first embodiment. As shown in FIG. 6, the behavior data table stored in the behavior data storage unit 22 includes a "symbol ID”, a "behavior definition”, a "time information”, and the like, and these information are associated with each other.
  • the “symbol ID” is the same as the “symbol ID” shown in FIG.
  • the “behavior definition” is information that defines how the behavior of the symbol 91 should be according to the monitoring data transmitted from the device 5 specified by the tag data.
  • the behavior of the symbol 91 is, for example, a change in the color of the symbol 91, presence / absence of blinking of the symbol 91, switching of a pattern or a figure of the symbol 91, and the like.
  • the "time information” is information on the time when the behavior of the symbol 91 is created or changed.
  • the behavior data table shown in FIG. 6 includes behavior data including "S001”, “If ", and “2020/12/20 15:24", and “S002", “If ", and Behavioral data including “2020/12/21 7:12” and behavioral data including “S003”, “If ", and "2020/12/21 11:25” are included.
  • the "" in “If " includes information that defines the behavior of the symbol 91.
  • the tag data storage unit 23 stores a tag data table including data that defines how the tag data that identifies the device 5 and the symbol data are allocated.
  • FIG. 7 is a diagram showing an example of a tag data table stored in the tag data storage unit according to the first embodiment. As shown in FIG. 7, the tag data table stored in the tag data storage unit 23 includes "tag data”, “symbol ID”, "time information”, and the like, and these information are associated with each other.
  • Tag data is tag data that is data that identifies the device 5.
  • the “symbol ID” is the same as the “symbol ID” shown in FIG.
  • “Time information” is information on the time when the allocation between the symbol data and the tag data is set or updated.
  • the tag data table shown in FIG. 7 includes data including “T00001”, “S001”, and “2020/12/20 15:54”, and “T00002", “S012”, and “2020/12/21 9”. : 13 ”and data including“ T00003 ”,“ S002 ”, and“ 2020/12/21 11:43 ”are included.
  • the layout data storage unit 24 stores a layout data table including position data indicating the positions of a plurality of symbols 91 arranged on the monitoring screen 90.
  • FIG. 8 is a diagram showing an example of a layout data table stored in the layout data storage unit according to the first embodiment. As shown in FIG. 8, the layout data table stored in the layout data storage unit 24 includes a “symbol ID”, a “left”, a “top”, a “time information”, and the like, and these information are associated with each other. ing.
  • the “symbol ID” is the same as the “symbol ID” shown in FIG. “Left” is information representing the distance from the left end of the monitoring screen 90. “Top” is information representing the distance from the upper end of the monitoring screen 90. The “time information” is information on the time when the symbol 91 is set or updated on the monitoring screen 90.
  • the layout data table shown in FIG. 8 includes layout data including "S001”, “40px”, “0px”, and "2020/12/20 17:54", and “S002", “30px”, “50px”. , And layout data including "2020/12/21 12:13” and layout data including "S003”, “80px”, “70px”, and "2020/12/21 14:16".
  • each table shown in FIGS. 5 to 8 also contains information regarding the deleted symbol 91.
  • the deletion flag indicating that the symbol 91 has been deleted is set to 1, and the deletion flag is set to 0 for the information about the symbol 91 that has not been deleted.
  • the screen data transmitted in response to the transmission request from the terminal device 2 does not include information about the symbol 91 for which the deletion flag is set to 1.
  • the processing unit 12 includes an authentication processing unit 30, a request reception unit 31, a screen display processing unit 32, a conflict data detection unit 33, and a synchronization processing unit 34.
  • the authentication processing unit 30 authenticates the user U of the terminal device 2 that has accessed the monitoring screen creation support device 3.
  • the authentication processing unit 30 manages the user ID and password for each user U, and authenticates the user U based on the user ID and password of the user U transmitted from the terminal device 2.
  • the request receiving unit 31 receives a processing request transmitted from the terminal device 2 of the user U authenticated by the authentication processing unit 30 and received by the communication unit 10.
  • the request receiving unit 31 adds the history data indicating the history of the received processing request to the history data table of the history data storage unit 20.
  • the screen display processing unit 32 When the processing request received by the request receiving unit 31 is a transmission request, the screen display processing unit 32 reads out the screen data including the above-mentioned symbol data, behavior data, tag data, and layout data from the storage unit 11. The screen display processing unit 32 causes the communication unit 10 to transmit the read screen data to the terminal device 2 that is the transmission source of the transmission request, and causes the terminal device 2 to editably display the monitoring screen 90 based on the screen data.
  • FIG. 9 is a diagram showing how symbols are arranged on the monitoring screen displayed by the monitoring screen editor in the terminal device according to the first embodiment.
  • a symbol candidate can be selected from the symbol candidate list 92 including a plurality of types of symbol candidates, and the selected symbol candidate can be arranged on the monitoring screen 90 as the symbol 91.
  • the terminal device 2 can display a parts list which is a list of parts such as a circle, a rectangle, a straight line, a curve, a figure, a button, or a three-dimensional object by the monitoring screen editor.
  • a parts list which is a list of parts such as a circle, a rectangle, a straight line, a curve, a figure, a button, or a three-dimensional object by the monitoring screen editor.
  • the user U can select one or more parts from the parts list, create a symbol 91, and arrange the created symbol 91 on the monitoring screen 90.
  • FIG. 10 is a diagram showing how the terminal device according to the first embodiment is designed by the monitoring screen editor for the symbols arranged on the monitoring screen displayed in the editor screen. As shown in FIG. 10, the user U can set the size, color scheme, shadow, transparency, rotation, and the like as the design of the symbol 91 by operating the terminal device 2.
  • FIG. 11 is a diagram showing how the behavior definition is set for the symbols arranged on the monitoring screen displayed in the editor screen by the monitoring screen editor in the terminal device according to the first embodiment. As shown in FIG. 11, the user U can set the behavior definition for the symbol 91 by operating the terminal device 2.
  • the definition that the symbol 91 blinks in red when the tag data 1 is 1 and the symbol 91 does not blink in white when the tag data 1 is not 1 is the behavior definition of the symbol 91. Is set to.
  • FIG. 12 is a diagram showing how the tag data is set for the symbols arranged on the monitoring screen displayed in the editor screen by the monitoring screen editor in the terminal device according to the first embodiment. As shown in FIG. 12, the user U can set tag data in the symbol 91 by operating the terminal device 2.
  • the tag data 1 and the tag data 2 are selected from the tag data list 93 by the operation of the user U.
  • the tag data list 93 shown in FIG. 12 includes T00001, T00002, T00003, and the like as tag data.
  • the user U can edit the monitoring screen 90 displayed in the editor screen 80 by the monitoring screen editor by operating the terminal device 2.
  • An update button 81 is arranged on the editor screen 80, and the user U clicks the update button 81 by operating the terminal device 2, so that an update request from the terminal device 2 creates a monitoring screen via the network 4. It is transmitted to the support device 3.
  • the conflict data detection unit 33 has a plurality of screen data when an update request from a plurality of terminal devices 2 on which a monitoring screen 90 based on the same screen data is editably displayed is received by the request reception unit 31. Detects conflicting data, which is data in which the update target conflicts between the update requests from the terminal device 2.
  • the conflict data detection unit 33 updates the screen data based on the update request from one of the two terminal devices 2 on which the monitoring screen 90 based on the same screen data is displayed. After the update request from the other terminal device 2 is received by the request receiving unit 31, the process of detecting the conflict data is started.
  • the conflict data detection unit 33 starts the process of detecting the conflict data. .. Further, the conflict data detection unit 33 displays the conflict data when the synchronization processing unit 34 does not perform the update processing for the update requests sequentially transmitted from the plurality of terminal devices 2 on which the monitoring screen 90 based on the screen data is displayed. It is also possible to start the detection process.
  • the plurality of terminal devices 2 for which the update request is received by the request receiving unit 31 are the terminal devices 2 1 and 22 and the history data table is in the state shown in FIG.
  • the process for the transmission request from the terminal device 2 1 of the user U 1 is executed at 10:00 on December 21, 2020, and the process for the transmission request from the terminal device 2 2 of the user U 2 is executed. Processing is being carried out at 10:35 on December 21, 2020.
  • the processing for the update request from the terminal device 2 of each user U was not executed, and the screen data and the terminal device transmitted to the terminal device 21 1 were not executed. It is the same as the screen data transmitted to 22 . Therefore, the monitoring screens 90 that are editably displayed on the terminal devices 2 1 and 22 are the same.
  • the process for the update request from the terminal device 21 is executed at 10:55 on December 21, 2020.
  • the screen data is updated based on the update data included in the update request from the terminal device 21 and the screen data is updated based on the update data included in the update request from the terminal device 2 2 .
  • the editing result by the user U 1 is overwritten by the editing result by the user U 2 .
  • the conflict data detection unit 33 receives an update request from a plurality of terminal devices 2 1 and 22 in which a monitoring screen 90 based on the same screen data is editably displayed by the request reception unit 31. Performs processing to detect conflicting data. Then, the synchronization processing unit 34 causes the terminal device 2 2 to display information indicating the contention state to be updated in the monitoring screen 90 based on the conflict data, and causes the user U 2 of the terminal device 2 2 to display the screen data based on the update request. Lets you choose whether or not to confirm the update of. When the user U 2 of the terminal device 2 2 selects to confirm the update, the synchronization processing unit 34 executes the update of the screen data based on the update request of the terminal device 22.
  • the user U 2 can grasp the part where the update content by the user U 1 and the update content by the user U 2 conflict with each other, and determines whether or not to perform the update with the update content by the user U 2 . Can be done. Therefore, it is possible to appropriately support the work of creating the monitoring screen 90 by the plurality of users U.
  • the synchronization processing unit 34 further causes the terminal device 21 to display information indicating the contention state of the update target on the monitoring screen 90, and makes the user U 1 of the terminal device 2 1 receive an update request from the terminal device 2 2 . It is also possible to select whether or not to allow the update of the screen data based on the execution. In this case, the synchronization processing unit 34 is based on the update request of the terminal device 2 2 when the user U 1 of the terminal device 2 1 selects permission and the user U 2 of the terminal device 2 2 selects the confirmation of the update. Update the screen data.
  • the synchronization processing unit 34 includes a display processing unit 41 and an update processing unit 42.
  • the display processing unit 41 provides the terminal device 2 with a confirmation screen including information indicating a race condition to be updated and information of a plurality of buttons for selecting whether or not to confirm the update of screen data based on the update request. Display.
  • the display processing unit 41 can cause the terminal device 2 to display the confirmation screen by transmitting the confirmation screen data to the terminal device 2 in the same manner as the screen data.
  • FIG. 13 is a diagram showing an example of a confirmation screen displayed in the editor screen by the monitoring screen editor in the terminal device according to the first embodiment.
  • the monitoring screen 90 being edited by the user U may be described as the monitoring screen 90A
  • the latest monitoring screen 90 last updated by the synchronization processing unit 34 may be described as the monitoring screen 90B.
  • a confirmation screen 70 including the monitoring screen 90A being edited by the user U and the latest monitoring screen 90B updated last is displayed.
  • the latest monitoring screen 90B is a monitoring screen 90 based on the latest screen data stored in the monitoring screen creation support device 3, and is an example of information indicating a race condition to be updated.
  • the monitoring screen 90A being edited by the user U and the latest monitoring screen 90B are arranged side by side, and the user U has the monitoring screen 90A being edited and the latest monitoring screen 90B.
  • the user U has the monitoring screen 90A being edited and the latest monitoring screen 90B.
  • the monitoring screen 90A being edited by the user U and the latest monitoring screen 90B are arranged side by side. What is the monitoring screen 90A being edited by the user U and the latest monitoring screen 90B?
  • the confirmation screen 70 can also be a screen that is arranged on different layers and overlapped and overlapped. In this case, for example, the confirmation screen 70 may be a screen in which the latest monitoring screen 90B is superimposed on the monitoring screen 90A being edited by increasing the transparency. Further, the screen 70 which is superimposed on the latest monitoring screen 90B by increasing the transparency of the monitoring screen 90A being edited can be used as the confirmation screen 70.
  • the position of one screen and the other screen is slightly positioned.
  • the confirmation screens that are staggered and overlapped can be used as the confirmation screen 70.
  • the confirmation screen 70 has a tab for displaying the monitoring screen 90A being edited and a tab for displaying the latest monitoring screen 90B, and the user U alternates between these tabs by operating the terminal device 2.
  • the monitoring screen 90A being edited and the latest monitoring screen 90B can be switched alternately.
  • the area other than the conflicting part does not change even if the monitoring screen 90A being edited and the latest monitoring screen 90B are switched alternately, and the conflicting part is with the monitoring screen 90A being edited. It changes when the latest monitoring screen 90B is switched alternately. Therefore, the user U can easily grasp the contention state of the update target on the monitoring screen 90.
  • the edit continuation button 73 is a GUI (Graphical User Interface) button for continuing editing.
  • the update confirmation button 74 is a GUI button for confirming the update request.
  • the switching button 75 is a GUI button for switching the monitoring screen 90A being edited to the latest monitoring screen 90B.
  • the terminal device 2 sends an update cancellation request to the monitoring screen creation support device 3.
  • the update cancellation request is transmitted from the terminal device 2, the synchronization processing unit 34 of the monitoring screen creation support device 3 does not update the screen data based on the update request.
  • the terminal device 2 sends an update confirmation request to the monitoring screen creation support device 3.
  • the update confirmation request is transmitted from the terminal device 2, the synchronization processing unit 34 of the monitoring screen creation support device 3 updates the screen data based on the update request.
  • the terminal device 2 transmits a transmission request to the monitoring screen creation support device 3.
  • the screen display processing unit 32 of the monitoring screen creation support device 3 transmits the screen data stored in the storage unit 11 to the terminal device 2.
  • the terminal device 2 displays the latest monitoring screen 90B based on the screen data transmitted from the monitoring screen creation support device 3.
  • FIG. 14 is a diagram showing another example of the confirmation screen displayed by the monitoring screen editor in the terminal device according to the first embodiment.
  • the confirmation screen 70A shown in FIG. 14 includes information that emphasizes the contention portion of the update target on the monitoring screen 90 being edited as information indicating the contention state of the update target, and is similar to the confirmation screen 70 shown in FIG. , An edit continuation button 73, an update confirmation button 74, and a switching button 75 are arranged.
  • the symbols 91 2 , 915 , and 918 are highlighted with a frame line as the update target in which the update conflicts with the latest monitoring screen 90B. Further, the symbol 912 is highlighted that the color scheme has been changed from red to blue. Further, it is highlighted that the symbol 915 has been changed from the symbol of "S001" to the symbol of " S011 ". Further, the symbol 918 is a symbol added on the latest monitoring screen 90B but deleted on the monitoring screen 90A being edited, and is highlighted by a broken line.
  • the highlighting method is not limited to the above-mentioned example, and the synchronization processing unit 34 makes the characters added to the symbol 91 bold, increases the size of the symbol 91, or causes the symbol 91 to blink. Can be done.
  • the behavior data of the symbol 91 conflicts, the behavior of the monitoring screen 90A being edited and the behavior of the latest monitoring screen 90B can be alternately executed on the confirmation screens 70 and 70A. In this case, characters indicating the behavior of the monitoring screen 90A being edited and the behavior of the latest monitoring screen 90B are displayed in association with the symbol 91.
  • the synchronization processing unit 34 can highlight the content of the conflicting attribute information as a character string. .. Further, when the tag data of the symbol 91 conflicts between the monitoring screen 90A being edited and the latest monitoring screen 90B, the synchronization processing unit 34 can highlight the content of the conflicting tag data as a character string. ..
  • the update processing unit 42 updates when the update request is received by the request reception unit 31 and the conflict data is not detected by the conflict data detection unit 33, or the update is transmitted from the terminal device 2 to which the confirmation screens 70 and 70A are transmitted.
  • the update process is executed.
  • the update process is a process of updating the screen data stored in the storage unit 11 based on the update data included in the update request received by the request reception unit 31.
  • the update process is performed by updating the data to be updated that has been added, changed, or deleted by the user U among the screen data.
  • the update target is symbol data, behavior data, tag data allocation to symbols, or layout data.
  • the update processing unit 42 changes the position data and the time information of the symbol 91 whose arrangement has been changed in the layout data. Further, when the symbol 91 is added, the update processing unit 42 adds the position data and the time information of the added symbol 91 to the layout data.
  • the update processing unit 42 adds the data associated with the symbol 91 and the behavior definition and the time information to the behavior data table. Further, when the behavior definition assigned to the symbol 91 is changed, the update processing unit 42 changes the behavior definition assigned to the symbol 91 whose behavior definition has been changed in the behavior data table.
  • the update processing unit 42 adds the data corresponding to the symbol 91 and the tag data and the time information to the tag data table. Further, when the tag data assigned to the symbol 91 is changed, the update processing unit 42 changes the tag data to be assigned to the symbol 91 to which the tag data has been changed in the tag data table.
  • FIG. 15 is a flowchart showing an example of processing by the processing unit of the monitoring screen creation support device according to the first embodiment.
  • the processing unit 12 of the monitoring screen creation support device 3 determines whether or not the user U has been authenticated when there is an access from the terminal device 2 (step S10).
  • the processing unit 12 determines that the user U has not been authenticated (step S10: No)
  • the processing unit 12 transmits an authentication request to the terminal device 2 of the user U (step S11).
  • the processing unit 12 determines whether or not the user U can be authenticated based on the authentication information from the terminal device 2 in response to the authentication request transmitted in step S11 (step S12).
  • the processing unit 12 determines that the user U has been authenticated (step S12: Yes) or has determined that the user U has been authenticated (step S10: Yes)
  • the transmission request from the terminal device 2 is sent by the communication unit 10. It is determined whether or not it has been received (step S13).
  • the processing unit 12 determines that the transmission request has been received by the communication unit 10 (step S13: Yes)
  • the processing unit 12 accepts the transmission request and transmits the transmission request to the monitoring screen 90 based on the image data stored in the storage unit 11. It is displayed on the terminal device 2 (step S14). Then, the processing unit 12 adds the history data related to the transmission request to the history data table stored in the history data storage unit 20 and updates the history data table (step S15).
  • step S15 When the processing unit 12 has completed the process of step S15, or when it is determined that the transmission request has not been received by the communication unit 10 (step S13: No), the update request from the terminal device 2 is received by the communication unit 10. It is determined whether or not it has been done (step S16). When the processing unit 12 determines that the update request has been received by the communication unit 10 (step S16: Yes), the processing unit 12 accepts the update request and performs comparison processing (step S17). The process of step S17 is the process of steps S30 to S36 shown in FIG. 16, which will be described in detail later.
  • step S18 determines whether or not the conflict flag of the screen data is 1 (step S18).
  • step S18: Yes the processing unit 12 executes the conflict time processing (step S19).
  • the process of step S19 is the process of steps S80 to S86 shown in FIG. 21, which will be described in detail later.
  • step S18 the processing unit 12 updates the screen data stored in the storage unit 11 based on the update data included in the update request (step S20). Then, the processing unit 12 adds the history data related to the update request to the history data table stored in the history data storage unit 20 and updates the history data table (step S21).
  • step S19 determines that the user U has not been authenticated (step S12: No)
  • step S12 determines that the user U has not been authenticated (step S12: No)
  • the processing unit 12 receives the update request in the communication unit 10. If it is determined that this has not been done (step S16: No), the process shown in FIG. 15 is terminated.
  • FIG. 16 is a flowchart showing an example of comparison processing by the processing unit of the monitoring screen creation support device according to the first embodiment. As shown in FIG. 16, the processing unit 12 initializes the conflict flag of the screen data and sets the conflict flag of the screen data to 0 (step S30).
  • step S31 the processing unit 12 performs a symbol data comparison process for comparing the screen data and the update data with respect to the symbol data (step S31).
  • the process of step S31 is the process of steps S40 to S43 shown in FIG. 17, which will be described in detail later.
  • step S32 the processing unit 12 performs a behavior data comparison process for comparing the screen data and the update data with respect to the behavior data (step S32).
  • the process of step S32 is the process of steps S50 to S53 shown in FIG. 18, which will be described in detail later.
  • step S33 the processing unit 12 performs a tag data comparison process for comparing the screen data and the update data with respect to the tag data assigned to the symbol 91 (step S33).
  • the process of step S33 is the process of steps S60 to S63 shown in FIG. 19, which will be described in detail later.
  • step S34 the processing unit 12 performs layout data comparison processing for comparing screen data and update data with respect to layout data.
  • the process of step S34 is the process of steps S70 to S73 shown in FIG. 20, which will be described in detail later.
  • step S35 the processing unit 12 determines whether or not there is conflicting data.
  • the processing unit 12 conflicts when any one or more of the conflict flag of the symbol data, the conflict flag of the behavior data, the conflict flag of the tag data, and the conflict flag of the layout data is 1. Determine that there is data.
  • step S35: Yes the processing unit 12 sets the conflict flag of the screen data to 1 (step S36).
  • step S36 the processing unit 12 ends the processing shown in FIG.
  • FIG. 17 is a flowchart showing an example of symbol data comparison processing by the processing unit of the monitoring screen creation support device according to the first embodiment. As shown in FIG. 17, the processing unit 12 initializes the conflict flag of the symbol data and sets the conflict flag of the symbol data to 0 (step S40).
  • the processing unit 12 stores the time information indicating the transmission processing date and time, which is the date and time of the transmission processing of the screen data for the latest transmission request from the terminal device 2 that has transmitted the update request, in the history data table. Obtain from the inside (step S41). For example, when the terminal device 2 that has transmitted the update request is the terminal device 2 2 of the user U 2 and the history data table is in the state shown in FIG. 4, the processing unit 12 uses "2020/12/21 10" as the time information. : 35 ”information is acquired.
  • the processing unit 12 determines whether or not the symbol data is updated after the transmission processing date and time specified by the time information acquired in step S41 (step S42). For example, when the symbol data table is in the state shown in FIG. 5 and the information of "2020/12/21 10:35" is acquired as time information in step S41, the symbol data including the symbol ID of "S003" is obtained. , It is determined that the update was made after the transmission processing date and time.
  • step S42: Yes the processing unit 12 sets the symbol data conflict flag to 1 (step S43).
  • step S43 the processing unit 12 ends the processing shown in FIG.
  • FIG. 18 is a flowchart showing an example of behavior data comparison processing by the processing unit of the monitoring screen creation support device according to the first embodiment. As shown in FIG. 18, the processing unit 12 initializes the conflict flag of the behavior data and sets the conflict flag of the behavior data to 0 (step S50).
  • the processing unit 12 stores time information indicating the transmission processing date and time, which is the date and time of the transmission processing of screen data for the latest transmission request from the terminal device 2 that has transmitted the update request, as in the process of step S41. It is acquired from the history data table stored in 11 (step S51).
  • the processing unit 12 determines whether or not the behavior data is updated after the transmission processing date and time specified by the time information acquired in step S51 (step S52). For example, when the behavior data table is in the state shown in FIG. 6 and the information of "2020/12/21 10:35" is acquired as time information in step S51, the behavior data including the symbol ID of "S003" is obtained. , It is determined that the update was made after the transmission processing date and time.
  • step S52: Yes the processing unit 12 sets the behavior data conflict flag to 1 (step S53).
  • step S53 the processing unit 12 ends the processing shown in FIG.
  • FIG. 19 is a flowchart showing an example of tag data comparison processing by the processing unit of the monitoring screen creation support device according to the first embodiment. As shown in FIG. 19, the processing unit 12 initializes the tag data conflict flag and sets the tag data conflict flag to 0 (step S60).
  • the processing unit 12 stores time information indicating the transmission processing date and time, which is the date and time of the transmission processing of screen data for the latest transmission request from the terminal device 2 that has transmitted the update request, as in the process of step S41. It is acquired from the history data table stored in 11 (step S61).
  • the processing unit 12 determines whether or not the tag data is updated after the transmission processing date and time specified by the time information acquired in step S61 (step S62). For example, when the tag data table is in the state shown in FIG. 7, and the information of "2020/12/21 10:35" is acquired as time information in step S61, the tag data of "T000000" is the transmission processing date and time. It is determined that the update was made later than.
  • step S62: Yes the tag data conflict flag is set to 1 (step S63).
  • step S63 the processing unit 12 ends the processing shown in FIG.
  • FIG. 20 is a flowchart showing an example of layout data comparison processing by the processing unit of the monitoring screen creation support device according to the first embodiment. As shown in FIG. 20, the processing unit 12 initializes the conflict flag of the layout data and sets the conflict flag of the layout data to 0 (step S70).
  • the processing unit 12 stores time information indicating the transmission processing date and time, which is the date and time of the transmission processing of screen data for the latest transmission request from the terminal device 2 that has transmitted the update request, as in the process of step S41. It is acquired from the history data table stored in 11 (step S71).
  • the processing unit 12 determines whether or not the layout data is updated after the transmission processing date and time specified by the time information acquired in step S71 (step S72). For example, when the layout data table is in the state shown in FIG. 8 and the information of "2020/12/21 10:35" is acquired as time information in step S71, the data of "S002" and the data of "S003" are obtained. It is determined that the data is updated after the transmission processing date and time.
  • step S72 determines that the layout data is updated after the transmission processing date and time (step S72: Yes).
  • step S73 sets the layout data conflict flag to 1 (step S73).
  • step S73 ends the processing shown in FIG.
  • FIG. 21 is a flowchart showing an example of conflict-time processing by the processing unit of the monitoring screen creation support device according to the first embodiment.
  • the processing unit 12 causes the terminal device 2 that has transmitted the transmission request to display a confirmation screen including information indicating the race condition (step S80).
  • the processing unit 12 determines whether or not the update confirmation request from the terminal device 2 that has transmitted the transmission request has been received by the communication unit 10 (step S81). When it is determined that the update confirmation request has been received (step S81: Yes), the processing unit 12 accepts the update confirmation request and updates the screen data based on the update data included in the update request (step S82). Then, the processing unit 12 adds the history data related to the update request to the history data table stored in the history data storage unit 20 and updates the history data table (step S83).
  • step S81 determines whether or not the transmission request from the terminal device 2 that has transmitted the transmission request has been received by the communication unit 10. (Step S84).
  • step S84: Yes the processing unit 12 accepts the transmission request, acquires the latest screen data from the storage unit 11, and transmits the acquired screen data to the terminal that transmitted the transmission request. It is transmitted to the device 2 (step S85).
  • step S84 determines whether or not the update cancellation request from the terminal device 2 that has transmitted the transmission request has been received by the communication unit 10. (Step S86). When the processing unit 12 determines that the update cancellation request has not been received (step S86: No), the processing unit 12 shifts the processing to step S81.
  • the processing unit 12 ends the processing shown in FIG. 21 when the processing in step S83 is completed, when the processing in step S85 is completed, or when it is determined that the update cancellation request has been received (step S86: Yes).
  • FIG. 22 is a diagram showing an example of the hardware configuration of the monitoring screen creation support device according to the first embodiment.
  • the monitoring screen creation support device 3 includes a computer including a processor 101, a memory 102, and a communication device 103.
  • the processor 101, the memory 102, and the communication device 103 can send and receive information to and from each other by, for example, the bus 104.
  • the storage unit 11 is realized by the memory 102.
  • the communication unit 10 is realized by the communication device 103.
  • the processor 101 executes the function of the processing unit 12 by reading and executing the program stored in the memory 102.
  • the processor 101 is, for example, an example of a processing circuit, and includes one or more of a CPU (Central Processing Unit), a DSP (Digital Signal Processor), and a system LSI (Large Scale Integration).
  • the memory 102 includes one or more of RAM (Random Access Memory), ROM (Read Only Memory), flash memory, EPROM (Erasable Programmable Read Only Memory), and EEPROM (registered trademark) (Electrically Erasable Programmable Read Only Memory). include. Further, the memory 102 includes a recording medium in which a computer-readable program is recorded. Such recording media include one or more of non-volatile or volatile semiconductor memories, magnetic disks, flexible memories, optical discs, compact disks, and DVDs (Digital Versatile Discs).
  • the monitoring screen creation support device 3 may include integrated circuits such as an ASIC (Application Specific Integrated Circuit) and an FPGA (Field Programmable Gate Array).
  • the monitoring screen creation support device 3 may be configured to have two or more devices.
  • the monitoring screen creation support device 3 may be composed of two or more server devices.
  • the monitoring screen creation support device 3 may be composed of a processing server and a data server.
  • each of the two or more devices has, for example, the hardware configuration shown in FIG. 22. Communication between two or more devices is performed via the communication device 103.
  • the user U can select the conflicting points to be updated by operating the terminal device 2.
  • the synchronization processing unit 34 can add, change, or delete only the conflicting part selected by the user U from among the plurality of conflicting parts.
  • the terminal device 2 transmits an update confirmation request including information on the conflict location selected by the user U from the plurality of conflict locations from the terminal device 2 to the monitoring screen creation support device 3.
  • the user U can lock some of the edited screen data so that they cannot be changed.
  • the user U operates the terminal device 2 to specify data to be locked.
  • the terminal device 2 transmits an update request including the information of the designated data to the monitoring screen creation support device 3.
  • the synchronization processing unit 34 adds a flag indicating that the specified data cannot be edited and the user ID of the locked user U to the data table stored in the storage unit 11.
  • the display processing unit 41 of the synchronization processing unit 34 can include information on the data that cannot be edited together with the user ID of the locked user U in the confirmation screens 70 and 70A displayed in the editor screen 80. ..
  • the update processing unit 42 of the synchronization processing unit 34 does not update from the terminal device 2 of the user U other than the locked user U.
  • the monitoring screen creation support device 3 includes a storage unit 11, a screen display processing unit 32, a request reception unit 31, a conflict data detection unit 33, and a synchronization processing unit 34. Be prepared.
  • the storage unit 11 stores screen data which is data of the monitoring screen 90 used in the monitoring control system 1.
  • the screen display processing unit 32 causes a plurality of terminal devices 2 operated by different users U to editably display the monitoring screen 90 based on the screen data.
  • the request receiving unit 31 receives an update request for the monitoring screen 90 from a plurality of terminal devices 2 whose monitoring screen 90 is editably displayed by the screen display processing unit 32.
  • the conflict data detection unit 33 is data in which the update target conflicts between the update requests from the plurality of terminal devices 2 among the screen data when the update request is received from the plurality of terminal devices 2 by the request reception unit 31. Detect conflicting data.
  • the synchronization processing unit 34 causes at least one terminal device 2 of the plurality of terminal devices 2 to display information indicating the conflict state to be updated, and at least one.
  • the user U of the two terminal devices 2 is made to select whether or not to confirm the update of the screen data based on the update request.
  • the monitoring screen creation support device 3 prevents a plurality of users U from forcibly reflecting the creation operation of the monitoring screen 90 of one user U on the monitoring screen 90 being operated by another user U. It is possible to support the work of creating the monitoring screen 90 by.
  • the conflict data detection unit 33 updates the screen data based on an update request from a terminal device 2 other than at least one terminal device 2 among the plurality of terminal devices 2, and then at least one terminal device 2
  • the process of detecting the conflicting data is started.
  • the monitoring screen creation support device 3 determines whether or not to confirm the update of the screen data when the screen data is updated based on the update request of one of the plurality of update requests in which the update target conflicts. You can choose. Therefore, the monitoring screen creation support device 3 can support the creation work of the monitoring screen 90 by the plurality of users U.
  • the synchronization processing unit 34 updates the screen data based on the selection for confirming the update of the screen data by the user U of at least one terminal device 2
  • the synchronization processing unit 34 changes, adds, or deletes the screen data according to the update request. Add time information to the created data.
  • the time information is an example of the update time information.
  • the conflict data detection unit 33 detects the conflict data based on the time information added to the synchronization processing unit 34. As a result, the monitoring screen creation support device 3 can appropriately determine whether or not the update targets conflict with each other.
  • the screen data shows symbol data indicating the symbol 91 arranged on the monitoring screen 90, behavior data defining the behavior of the symbol 91, tag data indicating the device 5 associated with the symbol 91, and layout of the symbol 91. Includes at least one of the layout data.
  • Conflict data detection detects conflict data from at least one piece of data. As a result, the monitoring screen creation support device 3 can appropriately determine whether or not the update targets conflict with each other.
  • the synchronization processing unit 34 provides information indicating a race condition for updating the monitoring screen 90A being edited by at least one terminal device 2 and the latest monitoring screen 90B based on the screen data stored in the storage unit 11. Is displayed on at least one terminal device 2 as a confirmation screen 70. As a result, the user U can grasp the place where the update conflicts between the monitoring screen 90A being edited and the latest monitoring screen 90B by comparing the monitoring screen 90A being edited with the latest monitoring screen 90B. can.
  • the synchronization processing unit 34 arranges the monitoring screen 90A being edited and the latest monitoring screen 90B based on the screen data on different layers, and superimposes the screens as confirmation screens 70 and 70A at least one terminal device 2. To display. As a result, the user U can grasp the place where the update conflicts between the monitoring screen 90A being edited and the latest monitoring screen 90B by comparing the monitoring screen 90A being edited with the latest monitoring screen 90B. can.
  • the synchronization processing unit 34 includes at least one terminal device 2 including a confirmation screen 70A including information emphasizing conflict data on the monitoring screen 90A being edited by at least one terminal device 2 as information indicating a race condition to be updated. To display. As a result, the user U can grasp the part where the update conflicts between the monitoring screen 90A being edited and the latest monitoring screen 90B by the information emphasizing the conflicting data.
  • the synchronization processing unit 34 confirms a screen including an edit continuation button 73 for continuing editing, an update confirmation button 74 for confirming an update request, and a switching button 75 for displaying the latest monitoring screen 90B.
  • the screens 70 and 70A are displayed on at least one terminal device 2.
  • the user U can select a button as necessary from the edit continuation button 73, the update confirmation button 74, and the switching button 75. Therefore, the monitoring screen creation support device 3 can more effectively support the creation work of the monitoring screen 90 by the plurality of users U.
  • the monitoring screen creation support device is in that a user ID is further added to each column of each data table and user-specific screen data can be stored in the monitoring screen creation support device. It is different from the monitoring screen creation support device 3 according to 1.
  • the components having the same functions as those of the first embodiment are designated by the same reference numerals and the description thereof will be omitted, and the differences from the monitoring screen creation support device 3 of the first embodiment will be mainly described.
  • FIG. 23 is a diagram showing an example of the configuration of the monitoring screen creation support device according to the second embodiment.
  • the monitoring screen creation support device 3A according to the second embodiment includes the storage unit 11A and the processing unit 12A instead of the storage unit 11 and the processing unit 12. Different from.
  • the storage unit 11A replaces the symbol data storage unit 21, the behavior data storage unit 22, the tag data storage unit 23, and the layout data storage unit 24 with the symbol data storage unit 21A, the behavior data storage unit 22A, and the tag data storage unit 23A.
  • a layout data storage unit 24A which is different from the storage unit 11.
  • a "user ID” is added to each column of the symbol data table stored in the symbol data storage unit 21A. Similarly, a “user ID” is added to each column of the behavior data table stored in the behavior data storage unit 22A, and a “user ID” is added to each column of the tag data table stored in the tag data storage unit 23A. Is added. Further, a "user ID” is added to each column of the layout data table stored in the layout data storage unit 24A.
  • the screen data used as the screen data of the monitoring screen 90 of the monitoring control system 1 is used as the shared screen data
  • the screen data unique to the user U is used as the user screen data.
  • the user ID is not added to the "user ID” for the data included in the shared screen data
  • the "user” is used for the data included in the user screen data.
  • the user ID is added to "ID”.
  • the processing unit 12A is different from the processing unit 12 in that the screen display processing unit 32A and the synchronization processing unit 34A are provided in place of the screen display processing unit 32 and the synchronization processing unit 34.
  • the screen display processing unit 32A displays a monitoring screen 90 based on the shared screen data on the terminal device 2 that has transmitted the transmission request for the shared screen data. Display editable.
  • the screen display processing unit 32A sends a monitoring screen based on the user screen data to the terminal device 2 that has transmitted the user screen data transmission request. Display 90 in an editable manner.
  • the synchronization processing unit 34A is different from the synchronization processing unit 34 in that the display processing unit 41A and the update processing unit 42A are provided in place of the display processing unit 41 and the update processing unit 42.
  • the display processing unit 41A causes the terminal device 2 to display a confirmation screen 70 including information indicating a race condition to be updated and information of a plurality of buttons corresponding to the processing contents for updating the screen data based on the update request.
  • the plurality of buttons arranged on the confirmation screen 70 include a button for transmitting a user screen data update request.
  • FIG. 24 is a diagram showing an example of a confirmation screen displayed in the editor screen by the monitoring screen editor in the terminal device according to the second embodiment.
  • a user save button 76 is further arranged on the confirmation screen 70 shown in FIG.
  • the user save button 76 is a GUI button that stores user screen data in the monitoring screen creation support device 3A.
  • the terminal device 2 transmits a user screen data update request to the monitoring screen creation support device 3A.
  • the update processing unit 42A of the synchronization processing unit 34A updates the user screen data based on the update request for the user screen data.
  • the terminal device 2 transmits an update request for the shared screen data to the monitoring screen creation support device 3A.
  • the update processing unit 42A of the synchronization processing unit 34A updates the shared screen data based on the update request for the shared screen data.
  • the monitoring screen creation support device 3A can temporarily register the user screen data which is the screen data before the sharing management, the screen data of the monitoring screen 90 including the symbol 91 interrupted during the creation. , Or screen data of the monitoring screen 90 including the symbol 91 in the prototype stage that does not need to be shared as a whole can be managed.
  • the confirmation screen displayed by the display processing unit 41A is not limited to the confirmation screen 70 shown in FIG. 24, as in the case of the display processing unit 41.
  • the hardware configuration example of the processing unit 12A of the monitoring screen creation support device 3A according to the second embodiment is the same as the hardware configuration of the processing unit 12 of the monitoring screen creation support device 3 shown in FIG. 22.
  • the processor 101 can execute the function of the processing unit 12A by reading and executing the program stored in the memory 102.
  • the synchronization processing unit 34A transmits from the plurality of terminal devices 2 in addition to the shared screen data which is the screen data shared by the plurality of users U. Based on the request to be made, the user screen data, which is the data of the monitoring screen 90 that can be edited individually for each user U, is generated or updated. As a result, the monitoring screen creation support device 3A can temporarily register the user screen data which is the screen data before the sharing management, so that the screen data of the monitoring screen 90 including the symbol 91 interrupted during the creation, It is possible to manage the screen data of the monitoring screen 90 including the symbol 91 in the prototype stage that does not need to be shared as a whole.
  • the configuration shown in the above embodiments is an example, and can be combined with another known technique, can be combined with each other, and does not deviate from the gist. It is also possible to omit or change a part of the configuration.

Abstract

L'invention concerne un dispositif d'aide à la création d'écran de surveillance (3) étant pourvu d'une unité de traitement d'affichage d'écran (32), d'une unité de réception de requête (31), d'une unité de détection de données de conflit (33) et d'une unité de traitement de synchronisation (34). L'unité de traitement d'affichage d'écran (32) affiche un écran de surveillance sur la base de données d'écran, sur une pluralité de dispositifs terminaux d'une manière modifiable. L'unité de réception de requête (31) reçoit des requêtes de mise à jour de l'écran de surveillance à partir de la pluralité de dispositifs terminaux sur lesquels l'écran de surveillance est affiché d'une manière modifiable par l'unité de traitement d'affichage d'écran (32). Lorsque les requêtes de mise à jour provenant de la pluralité de dispositifs terminaux sont reçues par l'unité de réception de requête (31), l'unité de détection de données de conflit (33) détecte des données de conflit dans lesquelles des cibles de mise à jour sont en conflit entre les requêtes de mise à jour provenant de la pluralité de dispositifs terminaux dans les données d'écran. Lorsque les données de conflit ont été détectées par l'unité de détection de données de conflit (33), l'unité de traitement de synchronisation (34) amène les dispositifs terminaux à afficher des informations indiquant un état de conflit des cibles de mise à jour et amène les utilisateurs des dispositifs terminaux à faire une sélection pour déterminer si la mise à jour des données d'écran sur la base des requêtes de mise à jour doit être déterminée ou non.
PCT/JP2020/043015 2020-11-18 2020-11-18 Dispositif d'aide à la création d'écran de surveillance, procédé d'aide à la création d'écran de surveillance et programme d'aide à la création d'écran de surveillance WO2022107248A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2021506004A JP6903247B1 (ja) 2020-11-18 2020-11-18 監視画面作成支援装置、監視画面作成支援方法、および監視画面作成支援プログラム
PCT/JP2020/043015 WO2022107248A1 (fr) 2020-11-18 2020-11-18 Dispositif d'aide à la création d'écran de surveillance, procédé d'aide à la création d'écran de surveillance et programme d'aide à la création d'écran de surveillance

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/043015 WO2022107248A1 (fr) 2020-11-18 2020-11-18 Dispositif d'aide à la création d'écran de surveillance, procédé d'aide à la création d'écran de surveillance et programme d'aide à la création d'écran de surveillance

Publications (1)

Publication Number Publication Date
WO2022107248A1 true WO2022107248A1 (fr) 2022-05-27

Family

ID=76753186

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/043015 WO2022107248A1 (fr) 2020-11-18 2020-11-18 Dispositif d'aide à la création d'écran de surveillance, procédé d'aide à la création d'écran de surveillance et programme d'aide à la création d'écran de surveillance

Country Status (2)

Country Link
JP (1) JP6903247B1 (fr)
WO (1) WO2022107248A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08106412A (ja) * 1994-03-17 1996-04-23 Toshiba Corp ファイル編集システム及び共有ファイル編集システム
JPH11161535A (ja) * 1997-09-28 1999-06-18 Kodak Ltd 共有データ環境でのデータ競合解決方法
JP2004326176A (ja) * 2003-04-21 2004-11-18 Matsushita Electric Works Ltd 情報サーバ、情報サーバ用プログラムおよび情報システム
JP2006195972A (ja) * 2005-01-14 2006-07-27 Microsoft Corp 共有オブジェクトに対する複数ユーザ変更を同期させるための方法およびシステム
US20100198871A1 (en) * 2009-02-03 2010-08-05 Hewlett-Packard Development Company, L.P. Intuitive file sharing with transparent security

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08106412A (ja) * 1994-03-17 1996-04-23 Toshiba Corp ファイル編集システム及び共有ファイル編集システム
JPH11161535A (ja) * 1997-09-28 1999-06-18 Kodak Ltd 共有データ環境でのデータ競合解決方法
JP2004326176A (ja) * 2003-04-21 2004-11-18 Matsushita Electric Works Ltd 情報サーバ、情報サーバ用プログラムおよび情報システム
JP2006195972A (ja) * 2005-01-14 2006-07-27 Microsoft Corp 共有オブジェクトに対する複数ユーザ変更を同期させるための方法およびシステム
US20100198871A1 (en) * 2009-02-03 2010-08-05 Hewlett-Packard Development Company, L.P. Intuitive file sharing with transparent security

Also Published As

Publication number Publication date
JP6903247B1 (ja) 2021-07-14
JPWO2022107248A1 (fr) 2022-05-27

Similar Documents

Publication Publication Date Title
CN109308255B (zh) 一种用于a/b测试实验的方法和装置
US9304808B2 (en) Updating a workflow when a user reaches an impasse in the workflow
US7000107B2 (en) System and method for using dynamic web components to remotely control the security state of web pages
US20140282398A1 (en) Platform for developing and distributing mobile applications
CN104036196A (zh) 用于配置口令和用于解锁的装置和方法
WO2021073636A1 (fr) Système et procédé de résolution de conflit de code, dispositifs, appareil et support
US20160069007A1 (en) Sewing machine system, terminal device, method of synchronizing embroidery data for sewing machine system, and recording non-transitory medium storing program for terminal device
JP2015505627A (ja) クラウドコンテンツの認識
DE112016000290T5 (de) Techniken zum Teilen von Anwendungen
CN105635063A (zh) 物联网通信协议配置方法和装置
CN112994958B (zh) 一种网络管理系统、方法、装置及电子设备
US7490301B2 (en) Computer readable recording medium storing program for managing CAD data
CN113227964A (zh) 用于机器人过程自动化设计的基于上下文的建议
US8651951B2 (en) Game processing server apparatus
CN108829486A (zh) 一种背景设置方法、装置、设备和存储介质
RU2450351C1 (ru) Устройство обработки информации и способ управления выполнением
CN110955872A (zh) 一种权限控制方法、装置、终端以及介质
WO2022107248A1 (fr) Dispositif d'aide à la création d'écran de surveillance, procédé d'aide à la création d'écran de surveillance et programme d'aide à la création d'écran de surveillance
JP2008197751A (ja) 電子帳票作成管理システム及び電子帳票作成管理プログラム及びこのプログラムを記憶した記録媒体
JP2778504B2 (ja) ネットワーク管理システム
JP6391143B2 (ja) アクセス制御装置、情報共有システム、プログラム及びアクセス制御方法
KR100346647B1 (ko) 홈페이지 화면 이미지 자동변경 제어방법
US8898187B2 (en) Default location that may be dynamically changed
JP6596318B2 (ja) 連携サーバ、連携システム、および連携サーバの制御方法
JP2007034837A (ja) 電子部品実装システム

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021506004

Country of ref document: JP

Kind code of ref document: A

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

Ref document number: 20962412

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20962412

Country of ref document: EP

Kind code of ref document: A1