Screen display data generation system, screen display data generation method and program
By using a server to generate screen display data from device and unit configuration information, the workload for creating monitoring screen displays is significantly reduced, enhancing efficiency and cost-effectiveness in control system integration.
Patent Information
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- MITSUBISHI ELECTRIC CORP
- Filing Date
- 2019-04-25
- Publication Date
- 2026-06-11
AI Technical Summary
Existing methods for generating monitoring screen displays require significant workload and effort, particularly in extracting device information from previous developments, such as piping and instrumentation diagrams.
A server obtains device identification and unit configuration information, generating screen display data using a template that includes this information, thereby simplifying the process of creating monitoring screen displays.
This approach drastically reduces the effort required to prepare monitoring screen displays, lowers development time, and decreases integration costs while allowing for easy expansion and management of control system configurations.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
Technical area
[0001] The present disclosure relates to a screen display data generation system, a screen display data generation method and a program. background
[0002] If an irregularity occurs in a control system within a facility's measuring equipment, the network or device that is the source of the irregularity is identified using a monitoring screen display that shows the control system's configuration. Such a monitoring screen display is created during the control system's design as a suitable display for the system. Because an operating state encompassing the device's irregularity is displayed on a screen display, the task of creating a monitoring screen display involves assigning a reference point to a part of the display and reproducing the monitoring screen display after the reference point of the data indicating the operating state has been acquired.Accordingly, the use of a technique for setting a monitoring screen display from information from another application is conceivable (see, for example, patent literature 1). Patent literature 1 discloses the linking of setting data of a monitoring screen display with a device using a list of information about the device, which was extracted from information determined by a prior development, such as a piping and instrumentation diagram.
[0003] Patent literature 2 discloses a control device with a human-machine interface (HMI), comprising: an HMI display unit 4 with a motion sensor; an IEEE 802.11 interface; and a CPU that sends data collected from the control device and HMI display data, which formats the collected data for display, to a smartphone via the IEEE 802.11 interface. Based on the detection result of the motion sensor, the CPU determines whether an operator has approached. If an operator has approached, it retrieves information about the operator's smartphone via the IEEE 802.11 interface and authenticates the smartphone based on the determined unique information. If authentication is successful, it sends the HMI display data and the collected data. If authentication fails, it does not send the HMI display data or the collected data.Patent literature 3 discloses a maintenance server, a remote monitoring system, and a remote monitoring method. The server is connected via a network to several work machines, each equipped with a display device for showing machine status information and an operator panel for predefined operations. It is also connected to a monitoring terminal, which has a display panel and remotely monitors the work machines' information. Communication between the work machines and the server is unidirectional, flowing from the work machines to the server. The server comprises a first and a second memory, as well as a display processing unit. The display processing unit generates a simulated image for the display panel and causes the monitoring terminal's display panel to show a maintenance screen with this simulated image. Citation list of patent literature Patent literature 1: WO 2014 / 064 819 A1 Patent literature 2: DE 11 2012 006 413 T5 Patent literature 3: US 2019 / 0 025 787 A1 Brief description of the invention: Technical problem
[0004] In addition to the preceding development, such as the piping and instrumentation diagram, the technical work described in patent literature 1 requires the extraction of a device from information determined by the preceding development. Accordingly, there is room to reduce the effort required to prepare the monitoring screen display.
[0005] Taking into account the aforementioned circumstances, one objective of the present disclosure is to reduce the workload required to prepare the monitoring screen display. Solution to the problem
[0006] The above problem is solved by the invention according to the subject matter of the independent claims. Advantageous embodiments of the invention are defined in the dependent claims. Advantageous effects of the invention
[0007] According to the present disclosure, a server obtains device identification information and unit configuration information from a control device, and a generating means generates screen display data relating to the control device specified by the device identification information from a template that includes the unit configuration information. Accordingly, the task of generating a monitoring screen display can be greatly simplified. This reduces the effort required to prepare the monitoring screen display. Brief description of drawings Fig. 1 is a drawing showing a configuration of a control system according to an embodiment of the present disclosure; Fig. 2 is a first drawing which shows an example of a monitoring screen display according to the embodiment; Fig. 3 is a second drawing which shows an example of the monitoring screen display according to the embodiment; Fig. 4 is a third drawing which shows an example of the monitoring screen display according to the embodiment; Fig. Figure 5 is a drawing showing a hardware configuration of a generation device and a server according to the embodiment; Fig. Figure 6 is a drawing showing a functional configuration of the server according to the embodiment; Fig. 7 is a drawing which shows information stored in a settings information memory area according to the embodiment; Fig. Figure 8 is a drawing showing hierarchy information according to the embodiment; Fig. Figure 9 is a drawing showing a functional configuration of the generating device according to the embodiment; Fig. 10 is a drawing which shows an example of a template according to the embodiment; Fig. 11 is a drawing which shows information stored in an image memory according to the embodiment; Fig. 12 is a drawing which shows detailed information according to the embodiment; Fig. 13 is a flowchart showing server processing according to the embodiment; Fig. 14 is a flowchart showing a template preparation process according to the embodiment; Fig. 15 is a flowchart showing a monitoring process according to the embodiment; Fig. Figure 16 is a drawing which shows a relationship between the monitoring screen display and a unit according to the embodiment; Fig. Figure 17 is a drawing showing a screen display data generation system according to a modified example; Fig. Figure 18 is a drawing showing a generating device according to the modified example; and Fig. Figure 19 is a drawing showing a control system according to the modified example. Description of embodiments
[0008] A screen display data generation system 100 according to an embodiment of the present disclosure is described in detail below with reference to drawings. embodiment
[0009] The screen display data generation system 100 according to the present embodiment corresponds to a part of a control system 1000, which is installed in a factory. The control system 1000 is a factory automation (FA) system, which is, for example, a production system, an inspection system, or a processing system. As described in Fig. As shown in Figure 1, the control system comprises 1000 (i) several control devices 30 which control devices 40, and (ii) the screen data generation system 100 as a monitoring system which monitors an operating state of each of the control devices 30.
[0010] The control devices 30 are industrial controllers, such as programmable logic controllers (PLCs). Each of the devices 40 controlled by the control devices 30 is, for example, a sensor, an actuator, or a robot. Controlling the devices 40 by the control devices 30 can include collecting measurement results obtained by communicating with the devices 40, which are sensors.
[0011] The screen display data generation system 100 includes (i) a generating device 10 which generates screen display data for displaying a monitoring screen display 101 which is used to monitor the operating states of the control devices 30, and (ii) a server 20 which obtains information about the control devices 30 from the control devices 30 and makes the obtained information available in response to an external request.
[0012] The generating device 10 is a personal computer (PC), such as an industrial personal computer (IPC) or a mobile device that can be worn by a user. Generating device 10 is an example of a means of generating screen display data for displaying a monitoring screen in the screen display data generation system 100. Generating device 10 displays the operating states of the control devices 30 in real time by generating screen display data and then updating the displayed content of the monitoring screen as needed. Generating device 10 is connected to server 20 via a dedicated line, such as a USB (Universal Serial Bus), and communicates with server 20.
[0013] Server 20 is a computer device with server functionality. Server 20 is an example of a server that retrieves information from the control devices 30 in the screen display data generation system 100 in order to provide that information. Server 20 is implemented as a database management system (DBMS) server, which is configured, for example, with OPC UA (Open Platform Communication Unified Architecture). Server 20 is connected to the control devices 30 via a field network (FA network), which is, for example, a field network, and communicates with the control devices 30.
[0014] Now, concrete examples of the surveillance screen display 101 will be presented with reference to the Fig. 2, Fig. 3 to Fig. 4 described. Fig. Figure 2 shows an example of the monitoring screen display 101. The configuration of the control system 1000, along with the names of the control devices 30 contained in the control system 1000, is displayed on this monitoring screen display 101. When the user selects an image of one of the control devices 30 displayed on the monitoring screen display 101, the monitoring screen display 101 shows an image 50 of the selected control device 30, as shown in Fig. 3 is shown.
[0015] As in Fig. As shown in Figure 3, each of the control devices 30 comprises several units. In particular, a power supply unit, represented by Figure 51, a central processing unit (CPU), represented by Figure 53, a network unit, represented by Figure 54, and an analog unit, represented by Figure 55, are attached to a base unit, represented by Figure 51, thereby forming the control device 30. A Figure 50, which represents an actual external appearance of such a control device 30, is displayed on the monitoring screen 101.
[0016] Furthermore, the operating state of the control devices 30 corresponds to the operating states of the units contained in the control devices 30. Accordingly, the in Fig. Figure 50, shown in Figure 3, is linked to the actual state of each unit. In particular, Figure 50 can display, according to the actual state, the blinking or illumination of a light-emitting diode (LED), the displayed content of a liquid crystal display, and the input state of a switch of each unit. However, if, for example, a part associated with the LED is in the Fig. As shown in Figure 3, the displayed size of a part that the user is supposed to pay attention to can be small. Accordingly, the monitoring screen display 101 shows the operating status of each unit as shown in Figure 3. Fig. 4 shown.
[0017] The monitoring screen display 101 of the Fig. 4 shows an operating state of the CPU. Monitoring screen display 101 is shown when the user selects the CPU which is in Fig. 3. Image 53 is assigned to it. The user's selection is, for example, a click of a cursor located in a display area of image 53, or a tap in the display area. The monitoring screen display 101 shows (i) image 53, which represents the appearance of the CPU, and (ii) an area 56, which provides detailed information about the CPU.
[0018] Area 56 includes (i) a box 561 which specifies a model name of the CPU, (ii) an area 562 which indicates a state of the LED, and (iii) an area 563 which indicates an input state of a hardware switch. In area 562, a black box indicates a light-off state, a white box indicates a light-on state, and a hatched box indicates a blinking state.
[0019] Server 20 and generating unit 10 work together, enabling the display of the monitoring screen 101 according to the configuration of the control unit 30 and the model of the units as shown in the Fig. 2, Fig. 3 to Fig. 4 is shown, it is achieved.
[0020] The following describes the hardware configurations of the generation device 10 and the server 20 with regard to Fig. 5 described. The generating device 10 and the server 20 each comprise a processor 61, a main memory 62, an auxiliary memory 63, an input device 64, an output device 65, and a communicator 66 as their hardware configuration. The main memory 62, the auxiliary memory 63, the input device 64, the output device 65, and the communicator 66 are all connected to the processor 61 via the internal bus 67.
[0021] The processor 61 comprises a CPU element. The processor 61 implements various types of functions of the generating device 10 and the server 20 by executing a program P1 stored in the auxiliary memory unit 63 and performs processing described later.
[0022] The main memory 62 comprises a random access memory (RAM). The program P1 is loaded from the auxiliary memory 63 into the main memory 62. The main memory 62 is used as a working area of the processor 61.
[0023] Auxiliary memory 63 comprises non-volatile memory, such as an EEPROM (Electrically Erasable Programmable Read-Only Memory) or a hard disk drive (HDD). In addition to the program P1, auxiliary memory 63 stores various data used for processing by processor 61. Auxiliary memory 63 supplies processor 61 with the data to be used by processor 61 and stores data supplied by processor 61 according to an instruction from processor 61.
[0024] The input device 64 includes an input device, for example an input key or a pointing device. The input device 64 receives the information entered by the user of the generating device 10 and the server 20 and communicates the received information to the processor 61.
[0025] The output device 65 includes an output device, such as a liquid crystal display (LCD) or a loudspeaker. The output device 65 provides the user with various types of information according to the instructions of the processor 61.
[0026] The communicator 66 comprises a network interface circuit for communicating with an external device. The communicator 66 receives a signal from the external device and outputs data specified by this signal to the processor 61. The communicator 66 also transmits a signal to the external device indicating data output by the processor 61. Without any specific limitation, in Fig. Figure 5 shows a communicator 66 as a representative example. For instance, server 20 can separately include a communicator 66 connected to the generating device 10 and a communicator 66 connected to the control device 30.
[0027] Through cooperation of the in Fig. The hardware configuration shown in section 5 enables the generating device 10 and the server 20 to perform various types of functions. As shown in Fig. As shown in section 6, server 20 includes, in particular, its functions. (i) a first communicator 21 for communicating with the generating device 10, (ii) a second communicator 22 for communicating with the control device 30, (iii) a server storage 23 which stores various types of data, and (iv) a controller 24 which controls the components of the server 20 to execute various processes.
[0028] The first communicator 21 is primarily implemented by communicator 66 of server 20. The first communicator 21 receives a request from generation device 10 and forwards this request to controller 24. Additionally, the first communicator 21 receives data from controller 24 indicating a response to the request from generation device 10 and transmits this data to generation device 10.
[0029] The second communicator 22 is primarily implemented through communicator 66 on server 20. The second communicator 22 (i) transmits and receives data to and from the control devices 30 in accordance with the instructions of the controller 24 and (ii) forwards communication between the controller 24 and the control devices 30.
[0030] Server memory 23 is primarily implemented through the auxiliary memory 63 of server 20. Server memory 23 is an example of a server storage device that stores several pieces of configuration information, described later, and provides this information according to the configurations of the control devices 30 in the screen display data generation system 100. Server memory 23 manages data, for example, according to OPC UA. The data managed by server memory 23 includes information for generating the monitoring screen display 101.
[0031] Control 24 is primarily implemented by processor 61 of server 20. Control 24 (i) obtains from the control devices 30 via the second communicator 22 device identification information concerning the control devices 30 and unit configuration information concerning the units contained in the control devices 30 and (ii) stores the related information in a configuration information storage area 231 of the server storage 23.
[0032] The device identification information, for example, is distinguishing information used to differentiate one control unit 30 from another. This information can be a user-defined device name, a device name generated by the respective control unit 30 itself, or the address of the respective control unit 30. Furthermore, the unit configuration information is information used to specify the units, such as identifying the type of each unit contained in the control unit 30 and / or the model name of each unit. If the unit type or model name is specified, the data can be used to display the unit's operating status on the monitoring screen display 101. Accordingly, such unit configuration information is used. Fig. Figure 6 shows an example in which server 20 obtains unit configuration information from four units contained in a controller 30 named "PLC30". The unit configuration information can include unit identification information that differs from the type and model name to distinguish the unit from other units.
[0033] In addition, the controller 24 refers to a setting information storage area 232, which was previously stored in the server memory 23, and reads the setting information which is assigned to the unit configuration information obtained by the control devices 30. Fig. Figure 7 shows an example of the data stored in the settings information memory area 232. As in Fig. As shown in Figure 7, the unit configuration information relating to various types of units that may be contained in the control devices 30 is stored in the setting information memory area 232, associated with setting information which specifies a setting for displaying the operating states of the units.
[0034] The configuration information specifies, in conjunction with each other, an identifier name, which indicates the operating state of the unit, and an address, which is a memory area of the unit where the data specifying the operating state is stored. The address is also referred to as a device address. The identifier name corresponds to a label of the operating state and is used so that server 20 can identify the operating state that was sent as a message to generating device 10. For example, in Fig. 7. An operating state, indicated by a label "Ready" of a CPU whose model name is "Type-CPU77", is specified by a data value at address "D100" of the CPU. When the generating device 10 requests an operating state with a label name "Ready", the server 20 obtains the operating state of the unit by accessing the device address with that label name.
[0035] Data which is part of the unit configuration information of the Fig. 6 correspond to are in Fig. 7 indicated by arrows. The controller 24 reads the data from the setting information memory area 232 and combines the acquired device identification information and the unit configuration information with the read data, thereby generating a hierarchy information 233 in which the device identification information, the unit configuration information, and the setting information are hierarchized in that order. Next, the controller 24 stores the generated hierarchy information 233 in the server memory 23. The hierarchy information 233 is read by the controller 24 from the server memory 23 in response to a request from the generating device 10 and is then provided to the generating device 10.
[0036] Fig. Figure 8 shows an example of the hierarchy information 233. As in Fig. As shown in Figure 8, the hierarchization information 233 comprises information that is hierarchized according to (i) a first hierarchy to which the device identification information belongs, (ii) a second hierarchy, which includes the unit configuration information, and (iii) a third hierarchy, which includes the attitude information of each unit.
[0037] Although the configuration information storage area 231 and the hierarchy information 233 in Fig. 6 shown separately, the hierarchy information 233 can be stored in the configuration information storage area 231.
[0038] Next, a functional configuration of the generating device 10 is described. The generating device 10 obtains the hierarchy information 233, which is managed by the server 20, thereby preparing a template for the monitoring screen display 101. As in Fig. As shown in Figure 9, the generating device comprises 10 (i) a communicator 11 to communicate with the server 20, (ii) an image storage device 12 which stores in advance an image as material for preparing the template, which is a screen display component, (iii) a template store 13 which stores the prepared template, (iv) a controller 14 which controls a component of the generating device 10 in order to generate screen display data of the monitoring screen display 101 from the template, and (v) a display 15 which displays the monitoring screen display 101.
[0039] Communicator 11 is primarily implemented by communicator 66 of generating unit 10. Communicator 11 transmits and receives data to and from server 20 according to instructions from controller 14 and forwards communication between controller 14 and server 20.
[0040] Image memory 12 and template memory 13 are database management systems (DBMSs) primarily implemented through the auxiliary memory 63 of the generation device 10. Image memory 12 is an example of an image storage device of the screen display data generation system 100 for storing a unit image, which is an image of the unit. Template memory 13 is also an example of a template storage device of the screen display data generation system 100 for storing a template of screen display data. Details of the data managed by image memory 12 and template memory 13 are described later.
[0041] The control unit 14 is primarily implemented by the processor 61 of the generating device 10. The control unit 14 requests the server 20 to provide the hierarchy information 233, thereby obtaining the hierarchy information 233 transmitted by the server 20. As in Fig. As shown in Figure 10, the controller 14 next prepares a template which includes, as a configuration property and as a model name property, the type and model name specified by the unit configuration information in the hierarchy information, and stores the prepared template in the template memory 13.
[0042] Furthermore, the controller 14 refers to the image memory 12 and reads the data associated with the unit configuration information. As in Fig. As shown in 11, the image memory 12 stores data for each unit, in which (i) a model name property, (ii) a unity image which represents the appearance of the unity, (iii) a status display image which serves as a basis for displaying an operating state of the unit, and (iv) a status display table which provides details for displaying the operating status in the status display image, are associated with each other. The unit image is used to display the information contained in the Fig. 2 and Fig. 3 shown in the monitoring screen display 101 is used, and the status indicator image is used to display the in Fig. 4 shown in the monitoring screen display 101 is used.
[0043] The controller 14 reads the unit image, the status display image, and the status display table from the image memory 12, which are assigned to the model name property of the template. Next, the controller 14 stores the location information in the template, which specifies the location of the unit image assigned to the respective unit in the image memory 12. As in Fig. As shown in Figure 10, the controller 14 stores, in particular, a path of the unit image in the template as a unit file property associated with the configuration property and the model name property.
[0044] In addition, the controller 14 stores the status display image and the status display table, which are assigned to the respective unit, along with the path associated with the configuration property and the model name property, as detailed information in the template. Fig. Figure 12 shows a concrete example of the detailed information. As in Fig. As shown in 12, the detailed information includes (i) an image file showing the status indicator image, and (ii) a state display table read from image memory 12.
[0045] The status display table contains table data that associates the object name of a screen display component, which displays the operating state, with the flag name for retrieving the operating state from server 20. The object name of the screen display component is preset. Controller 14 assigns the flag name to a value that is equal to the flag name in the hierarchy information 233. Controller 14 prepares the template as described above.
[0046] Next, the controller 14 generates screen display data from the prepared template and transmits this data to the display 15, thereby triggering the display of the monitoring screen 101 on the display 15. The controller 14 then updates the display content of the monitoring screen 101 using data indicating the operating status, which is obtained in real time from the server 20.
[0047] The display 15 is primarily implemented by the output 65 of the generating unit 10. Specifically, the display 15 shows the information provided by the controller 14 on the screen display and according to the instructions of the controller 14.
[0048] Next, a processing operation performed by the screen display data generation system 100 will be described.
[0049] Fig. Figure 13 shows a server process that is executed by server 20. This server process is started by executing a specific program on server 20.
[0050] During server processing, server 20 selects a non-selected control device from connected control devices 30 (step S11). Specifically, the controller 24 selects a control device 30 from one or more control devices 30 capable of communicating with server 20 in a predetermined sequence. The predetermined sequence could, for example, be a sequence in which communication is established or a descending order of the communication address values.
[0051] Next, server 20 obtains the device identification information and the unit configuration information from the selected control device 30 (step S12). Specifically, controller 24 obtains the message information by requesting control device 30, via the second communicator 22, to send a message containing the device identification information and the unit configuration information. Controller 24 then stores the obtained information in the configuration information memory area 231 of server memory 23.
[0052] Next, server 20 reads the setting information associated with the unit configuration information from server memory 23 (step S13). Specifically, controller 24 locates and reads from the setting information memory area 232 of server memory 23 the setting information that has the same values as the type and model name of the unit configuration information obtained in step S12. This reads the setting information for each of the units contained in the controller 30 selected in step S11.
[0053] Next, server 20 generates the hierarchy information 233, in which the device identification information, the unit configuration information, and the setting information are hierarchically ordered in that order (step S14). Specifically, controller 24 associates the device identification information and the unit configuration information obtained in step S12 with the setting information read in step S13, thereby generating the hierarchy information 233 as a block of structured data. Controller 24 then stores the generated hierarchy information 233 in server memory 23.
[0054] Next, server 20 determines whether the hierarchy information 233 has been generated for all of the control devices 30 (step S15). In particular, controller 24 determines whether the hierarchy information 233 is stored in server memory 23 for all of the control devices 30 that are connected to and can communicate with server 20.
[0055] If server 20 determines that the hierarchy information 233 has not been generated for all of the control devices 30 (No in step S15), server 20 repeats the processes from step S11. This generates the hierarchy information 233 in an ordered manner for the unselected control devices 30 and stores it in server memory 23. On the other hand, if server 20 determines that the hierarchy information 233 has been generated for all of the control devices 30 (Yes in step S15), server 20 provides the hierarchy information 233 in response to the external request (step S16). Specifically, in response to a request from the generating device 10, controller 24 reads the hierarchy information 233 from server memory 23 and provides the read information. Server processing then ends.
[0056] A template preparation process, which is executed by the generation device 10, is next described with reference to Fig. 14 described. This template preparation processing is started by executing a specific program of the generation device 10.
[0057] During template preparation processing, the generating device 10 obtains the hierarchy information 233 for all control devices 30 to be monitored (step S21). Specifically, the controller 14 obtains the hierarchy information 233 by requesting the server 20 to provide the hierarchy information 233 concerning one or more control devices 30. The control devices 30 to be monitored can be all of the control devices 30 connected to the server 20, control devices 30 selected by the user, or control devices 30 that meet a condition preset in the generating device 10. The preset condition could, for example, be that the user can perform monitoring with access authorization previously granted to the user.
[0058] Next, the generating unit 10 prepares a template for each control unit 30, which includes (i) as the configuration property a type which is specified by the unit configuration information, and (ii) as the model name property, a model which is specified by the unit configuration information (step S22). In particular, the controller 14 generates data of a template which contains a value equal to the unit configuration information in the hierarchy information 233 obtained in step S21.
[0059] Next, the generating device 10 saves the location information of the unit image, which is assigned to the unit configuration information, into the template as a unit file property for all units of the respective control device 30 (step S23). In particular (i) the controller 14 searches in the image memory 12 for a unit image which is assigned to the unit configuration information in the hierarchization information 233 obtained in step S21, and (ii) stores a path of this unit image to image storage unit 12 in the template prepared in step S22.
[0060] Next (i) the generating device 10 generates for all of the units of the respective control device 30 the status display table, which includes as a label name a label of an operating state specified by the setting information, and (ii) saves the generated table to the template (step S24).
[0061] In particular (i) the controller 14 generates the status display table which includes a value equal to the identifier name contained in the setting information in the hierarchy information 233 referred to in step S21, and (ii) stores the generated status display table in the detailed information of the template prepared in step S22.
[0062] This completes templates for generating screen display data, which are used to display the monitoring screen display 101 on the display 15, for all of the control devices 30.
[0063] A monitoring process, which is carried out by the generating device 10, is next described with reference to Fig. 15 described. The monitoring processing is started by executing a specific program of the generating device 10 after completion of the template preparation processing.
[0064] During monitoring processing, the generating device 10 determines whether the monitoring screen display 101 is changed (step S31). In particular, the controller 14 determines whether the user has previously entered a change instruction to modify the monitoring screen display 101.
[0065] If the generating unit 10 determines that the monitoring screen display 101 has not been changed (No in step S31), the processing by the generating unit 10 proceeds to step S33. On the other hand, if the generating unit 10 determines that the monitoring screen display 101 has been changed (Yes in step S31), the generating unit 10 changes the monitoring screen display 101 according to the change instruction. In particular, the controller 14 changes the template according to the change instruction (step S32).
[0066] The change instruction can, for example, (i) a change in the arrangement of screen display components and (ii) include adding and deleting a screen display component.
[0067] Next (i) the generating device 10 obtains from the server 20, by means of the identifier name, an operating state of the control device 30, which is the subject of monitoring, and (ii) Based on the template, the screen display data is generated (step S33). In particular, the controller 14 queries the server 20 for the operating state, which is specified by the identifier name. Because the server 20 obtains the operating state of each of the control devices 30 in real time, the generating device 10 can obtain the operating states of the control devices 30 from the server 20.
[0068] Next, the generating device 10 transmits the screen display data to the display 15, thereby updating and displaying the monitoring screen display 101 (step S34). The processing by the generating device 10 then repeats the processes from step S33. This updates the display content of the monitoring screen display 101.
[0069] In the manner described above, as in Fig. Figure 16 clearly shows the relevance of the screen display components of the monitoring screen display 101 for the data of each unit via the template's status display table and the information managed by the server 20. Furthermore, such relevance is defined using the hierarchy information 233, as shown in Fig. 8 is shown.
[0070] As described above, server 20 obtains the device identification information and unit configuration information from the control devices 30, and generation device 10 therefore generates the screen display data for the control devices 30, as specified by the device identification information, from the template containing the unit configuration information. Accordingly, the work involved in generating the monitoring screen display 101 can be drastically simplified. This reduces the workload for preparing the monitoring screen display 101. In particular, the development time required to generate the monitoring screen display 101 can be reduced, and the development costs for system integration can be lowered.
[0071] Furthermore, if the configuration of the control system 1000 is changed, the monitoring screen display 101 must also be changed. However, if the template is regenerated, the monitoring screen display 101 is changed according to the configuration of the control system 1000. Therefore, revising the monitoring screen display 101 is unnecessary. This simplifies the expansion of the control system 1000.
[0072] Furthermore, the data concerning the control devices 30 are provided as structured hierarchical information 233. Accordingly, data management between the generating device 10 and the server 20 is simple. Moreover, even if the monitoring display 101 is changed, an operator does not need to understand the relationship between (i) the screen display components for monitoring the states of the units and (ii) the configurations of the control devices 30 do not need to be considered, and the operator can simply perform the work. For example, the device address is managed by the server 20 along with the tag name, and the tag name is managed by the generating device 10 along with the names of the screen display components. Accordingly, the operator does not need to record the device address and the tag name, and the operator only needs to provide an instruction to change a screen display component as an object to be changed.
[0073] Furthermore, the generating device 10 creates the screen display data by combining the setting information with the template, which includes the unit configuration information in the hierarchy information 233. In particular, as in Fig. As shown in 10, the generating device 10 produces, after adding a Fig. The status display table shown in Figure 12, which includes the identifier name, is linked to the template, which includes the unit type and model name based on the setting information, and the screen display data from this template. This enables the generating unit 10 to display various types of information on the monitoring screen display 101 using the setting information previously stored in the server 20 together with the information transmitted by the control units 30.
[0074] Furthermore, the hiring information includes (i) the operating status label of the unit and (ii) the address of the unit which specifies the area in which the data indicating the operating state are stored.
[0075] Next, the generating device 10 applies the label in the setting information to the identifier name in the status display table. This allows the generating device 10 to obtain the operating status of the unit using the label without managing the device address.
[0076] Furthermore, server 20 stores several pieces of setting information beforehand, selects the setting information that corresponds to the unit configuration information transmitted by the control devices 30, and generates the hierarchy information 233. Accordingly, server 20 can generate the hierarchy information 233 from the setting information, which is assigned to various units that may each be contained in the control devices 30.
[0077] In addition (i) the generating device 10 stores the unit image, which is an image representing the appearance of the respective unit, and (ii) generates the screen display data from the template which includes the path of the unit image.
[0078] Accordingly, the appearance of the unit is displayed on the monitoring screen 101 based on the screen display data. Therefore, the user, who visually confirms the monitoring screen 101, can visually confirm an image on the monitoring screen 101 with the same configuration as the actual external appearance of the respective control device 30. This allows a control device 30, whose status is displayed on the monitoring screen 101, to be easily associated with the housing of an actual control device 30.
[0079] Although the embodiment of the present disclosure is described above, the present disclosure is not limited to the embodiment described above.
[0080] Without any particular limitation, an example is described above in which the generating device 10 and the server 20 are separate devices. As in Fig. As shown in Figure 17, the generating device 10 can have the software-implemented function of the server 20.
[0081] Without any particular limitation, an example is described above in which the generating device 10 itself displays the monitoring screen display 101. As in Fig. As shown in Figure 18, the generating device 10 can display the monitoring screen display 101 by transmitting screen display data to an external display terminal 15a.
[0082] Furthermore, the image memory 12 can be omitted in the configuration of the generation device 10, and the settings information memory area 232 of the server memory 23 can be omitted in the configuration of the server 20. As in Fig.As shown in Figure 19, the generating device 10 can obtain required information from an external image server 12a, which stores data that is the same as that stored in the image memory 12, and the server 20 can obtain required information from an external settings information server 232a, which stores information that is the same as that stored in the settings information memory area 232.
[0083] Without any particular limitations, an example is described above according to which the generating device 10 prepares the template. Several templates, encompassing different types and model names, can be previously stored in the template storage medium. Furthermore, the generating device 10 (i) select a template which is associated with the unit configuration information contained in the hierarchy information 233 obtained from server 20, and (ii) apply the setting information to the selected template in order to switch to a state in which the template can be used for monitoring processing.
[0084] Regarding the configuration information provided by server 20 to generation device 10, the device address contained in the configuration information can be omitted. Furthermore, the configuration information can include other information that differs from the label and device address of the operating state.
[0085] Furthermore, the functions of the generating device 10 and the server 20 can be achieved through dedicated hardware or through a normal computer system.
[0086] For example, the program P1 executed by processor 61 is stored on a non-volatile, computer-readable recording medium. This recording medium, which stores the program P1, is then distributed, and the program P1 is installed on a computer, thereby creating a device for performing the processing described above. Possible examples of such a recording medium include a CD-ROM (Compact Disc-Read-Only Memory), a DVD (Digital Versatile Disc), and a magneto-optical (MO) disk.
[0087] Alternatively, the program P1 can be pre-stored in a hard disk device located in a server device connected to a communication network, such as the Internet, and the program P1 can be downloaded to the computer, for example by superimposing the program P1 onto a carrier wave.
[0088] Furthermore, the processing described above can be achieved by starting and executing program P1 while program P1 is being transmitted over the communication network.
[0089] Furthermore, the processing described above can also be achieved by (i) Running the program P1 completely or partially on the server device and (ii) Executing the program while the computer transmits and receives information relating to the processing over the communication network.
[0090] Even in a case where the functions described above are realized by splitting between operating systems (OS) or in cooperation between an OS and an application program, it is possible to store only a part different from the OS in the recording medium, and such a recording medium can be distributed or the part different from the operating systems can be downloaded to the computer.
[0091] Furthermore, the means of realizing the functions of the generating device 10 and the server 20 is not limited to software, and the functions can be partially or completely realized by dedicated hardware with a circuit.
[0092] The foregoing describes some exemplary embodiments for illustrative purposes. Although the preceding discussion has presented certain embodiments, the person skilled in the art understands that changes in form and detail may be made without departing from the broader spirit and scope of the invention. Accordingly, the description and drawings are to be understood as explanatory rather than restrictive. This detailed description is therefore not to be regarded as limiting, and the scope of the invention is defined solely by the appended claims together with the full scope of the equivalents associated with such claims. Industrial applicability
[0093] The present disclosure is suitable for monitoring the operating state of a system. Reference symbol list 1000 control system 100 Screen Display Data Generation System 101 Monitoring screen display 10 generating device 11 Communicator 12 image storage 12a Image server 13 Template storage 14 Control 15 ads 15a Display terminal 20 servers 21 first communicator 22 second communicator 23 server storage 231 Configuration Information Storage Area 232 Settings information storage area 232a Settings Information Server 233 Hierarchy Information 24 Control 30 Control unit 40 Device 50 to 55 images 56 area 61 processor 62 GB main memory 63 Auxiliary storage 64 inputters 65 editors 66 Communicator 67 internal bus 561 Box 562, 563 area P1 Program
Claims
Screen display data generation system (100), comprising: a generation means (10) for generating screen display data for displaying a monitoring screen display (101) used for monitoring an operating state of a control device (30) controlling a device (40); and a server (20) comprising a server storage means (23) for storing setting information specifying a setting for displaying, on the monitoring screen display (101), an operating state of a unit contained in the control device (30), the server (20) being configured to obtain from the control device (30) device identification information for identifying the control device (30) and unit configuration information relating to the unit, and to generate and provide hierarchy information (233) in which the obtained device identification information,The related unit configuration information and the setting information are hierarchically structured, wherein the generating means (10) comprises a template storage means (13) for storing a template of the screen display data and an image storage means (12) for storing unit images, which are multiple images of a plurality of the respective units, and generates the screen display data by combining the setting information with the template, wherein the screen display data are data that (i) relate to the control device (30), which is specified by the device identification information contained in the hierarchization information (233), and (ii) serve to display the monitoring screen display (101), which comprises the unit images, wherein the template comprises the unit configuration information and includes location information that specifies the locations of the respective unit images in the image storage means (12).wherein the locations of the unit images are assigned to the unit configuration information contained in the hierarchy information (233), wherein the image storage means (12) stores a state display image and a state display table, which serve to display the operating state of the unit associated with the assigned unit image of the unit images, wherein the state display table includes a name of a screen display component that displays the operating state and an identifier name for obtaining the operating state from the server (20), and wherein the generation means (10) stores in the state display table as the identifier name a label of the operating state which is specified by the setting information contained in the hierarchy information (233). Screen display data generation system (100) according to claim 1, wherein the setting information includes the label of the operating state of the unit and an address of the unit which specifies an area in which data specifying the operating state are stored. Screen display data generation system (100) according to claim 1 or 2, wherein the server storage means (23) stores several pieces of the setting information and the server (20) reads from the server storage means (23) the setting information which is associated with the unit configuration information obtained from the control device (30). Screen display data generation system (100) according to any one of claims 1 to 3, wherein the unit configuration information specifies a type of unit and / or a model of unit and the generation means (10) generates the screen display data from the template which comprises the type specified by the unit configuration information contained in the hierarchy information (233) and / or the model specified by the unit configuration information contained in the hierarchy information (233). Method for generating screen display data, the method comprising: a step of obtaining, by a server (20) from a control device (30) controlling a device (40), device identification information for identifying the control device (30) and unit configuration information relating to a unit contained in the control device (30) in order to generate and provide hierarchy information (233) in which the obtained device identification information, the obtained unit configuration information and a setting information are hierarchically ordered, wherein the setting information specifies a setting for displaying an operating state of the unit on a monitoring screen display (101) which is used to monitor an operating state of the control device (30);a step of generating, by a generating means (10), the screen display data by combining the setting information with a template, wherein the screen display data are data that (i) relate to the control device (30) which is specified by the device identification information contained in the hierarchy information (233), and (ii) serve to display the monitoring screen display (101) which comprises unit images, which are multiple images of a plurality of the respective units, wherein the template comprises the unit configuration information and includes location information which specifies the locations of the respective unit images in an image storage means (12), wherein the locations of the unit images are associated with the unit configuration information contained in the hierarchy information (233);and a step of storing, by the generating means (10), a label of an operating state, which is specified by the setting information contained in the hierarchization information (233), into a state display table, which is stored in the image storage means (12) together with a state display image for displaying the operating state of the unit associated with the associated unit image of the unit images, wherein the state display table includes a name of a screen display component that displays an operating state and a flag name for obtaining the operating state from the server (20), wherein the label is stored as the flag name.; A program that causes a computer to function as: a generating means (10) for generating screen display data for displaying a monitoring screen display (101) used to monitor an operating state of a control device (30) controlling a device (40); and a server means (20) comprising a server storage means (23) for storing setting information specifying a setting for displaying, on the monitoring screen display (101), an operating state of a unit contained in the control device (30), wherein the server means (20) is configured to obtain from the control device (30) device identification information for identifying the control device (30) and unit configuration information relating to the unit, and to generate and provide hierarchy information (233) in which the obtained device identification information,The related unit configuration information and the setting information are hierarchically structured, wherein the generating means (10) comprises a template storage means (13) for storing a template of the screen display data and an image storage means (12) for storing unit images, which are multiple images of a plurality of the respective units, and generates the screen display data by combining the setting information with the template, wherein the screen display data are data that (i) relate to the control device (30), which is specified by the device identification information contained in the hierarchization information (233), and (ii) serve to display the monitoring screen display (101), which comprises the unit images, wherein the template comprises the unit configuration information and includes location information that specifies the locations of the respective unit images in the image storage means (12).wherein the locations of the unit images are assigned to the unit configuration information contained in the hierarchy information (233), wherein the image storage means (12) stores a state display image and a state display table, which serve to display the operating state of the unit associated with the assigned unit image of the unit images, wherein the state display table includes a name of a screen display component that displays the operating state and an identifier name for obtaining the operating state from the server means (20), and wherein the generation means (10) stores in the state display table as the identifier name a label of the operating state which is specified by the setting information contained in the hierarchy information (233).