Screen generating device and screen generating method

Abstract

With the present invention, it is possible to present a template creator with a screen including the most suitable configuration items corresponding to a method of using the template screen, and to enable a template creator who uses a template to create (customize) a display screen to easily create a screen suitable for work locations by configuring the template screen.This screen generation device includes: an automatic configuration screen generation unit for generating a configuration screen for the purpose of configuring configuration items each defined in previously generated screen template information; a configuration information generation unit for generating configuration information based on the information for each of the configuration items configured on the configuration screen; and an automatic screen generation unit for generating the screen based on the template information and the configuration information generated by the configuration information generation unit.

Description

Technical area

[0001] The present invention relates to a screen generating apparatus and a screen generating method for generating a screen in connection with manufacturing according to respective work sites. Background of the technology

[0002] Conventionally, techniques are known (e.g. Business Intelligence (BI) tools and Supervisory Control And Data Acquisition (SCADA)) that allow a user to create a workstation-specific screen based on a pre-generated screen mask by adapting the screen mask.

[0003] In addition, another conventional technique is known that allows information or data that a user wants to check to be displayed on a screen while allowing a certain degree of freedom in its arrangement. See, for example, Patent Document 1.

[0004] Furthermore, regarding a display element and a display size selected by a worker, while displaying a plurality of segmented screens corresponding to the display size on one screen based on display information of a segmented screen storage area, a technique is known in which, when the worker selects a segmented screen from among the plurality of segmented screens displayed on the screen, a configuration of the display screen is freely adjusted according to an intention of the worker, who stores the display size and segmented screen position information of the selected segmented screen in a user-defined screen storage area. For example, see Patent Document 2. Citation listPatent document Patent Document 1: Unexamined Japanese Patent Application, Publication No. 2000-066709 Patent Document 2: Unexamined Japanese Patent Application, Publication No. 2010-152882 Disclosure of the invention Problems to be solved by the invention

[0005] However, according to the inventions disclosed in Patent Documents 1 and 2, when a screen mask is applied to a worksite, it requires customization according to the differences between different worksites and the specific needs of specific users. Therefore, a general-purpose mask would complicate work at the time of application in any worksite. Furthermore, masks specialized for a specific workplace or equipment would have a problem that their intended use would be limited.

[0006] In order to cope with the circumstances described above, there is a need to present a mask creator with a screen including the most suitable configuration items corresponding to a method of using a mask screen, and to enable a screen creator who uses a mask to create (customize) a display screen to easily create a screen suitable for each work location by configuring the mask screen. Means to solve the problems

[0007] One aspect of a screen generation device of the present disclosure includes: an automatic configuration screen generation unit configured to generate a configuration screen to configure each of the configuration items defined in pre-generated template information for a display screen; a configuration information generation unit configured to generate configuration information based on information for each of the configuration items configured on the configuration screen; and an automatic screen generation unit configured to generate the screen based on the template information and the configuration information generated by the configuration information generation unit.

[0008] One aspect of a screen generation method of the present disclosure provides a screen generation method that causes a computer to function as a screen generation device, and includes: a selection step of selecting one of pieces of pre-generated template information for a display screen; an automatic configuration screen generation step of generating a configuration screen for configuring each of the configuration items defined in the selected template information; a configuration information generation step of generating configuration information based on information for each of the configuration items configured on the configuration screen; and an automatic screen generation step of generating the display screen based on the selected template information and the generated configuration information. Short description of the drawings Fig. 1 is a functional block diagram of a screen generation system according to an embodiment; Fig. 2 is a drawing showing an example of a device status table; Fig. 3 is a drawing showing an example of template information; Fig. 4 is a drawing showing an example of a template screen in template information on a factory monitoring screen; Fig. 5 is a drawing showing examples of appearances / behaviors in configuration items in the template information on the factory monitoring screen; Fig. 6 is a drawing showing an example of usage data in the configuration items in the template information on the factory monitoring screen; Fig. 7 is a drawing showing an example of a template screen in the template information on a production performance registration screen; Fig. 8 is a drawing showing examples of appearances / behaviors in configuration items in the template information on the production performance registration screen; Fig. 9 is a drawing showing an example of usage data in the configuration items in the template information on the production performance registration screen; Fig. 10 is a drawing showing an example of configuration information; Fig. 11 is a drawing showing an example of a template information creation screen; Fig. 12 is a drawing showing an example of metainformation in a data source; Fig. 13 is a drawing showing an example of device meta information; Fig. 14A is a drawing showing an example of a screen management screen; Fig. 14B is a drawing showing an example of a template selection screen; Fig. 15 is a drawing showing an example of a configuration screen for the factory monitoring screen; Fig. 16 is a drawing showing an example of a configuration screen that appears when a device icon (a component) is selected; Fig. 17 is a drawing showing another example of the configuration screen that appears when the device icon (component) is selected; Fig. 18 is a drawing showing another example of the configuration screen that appears when the device icon (component) is selected; Fig. 19 is a drawing showing an example of a configuration screen for the production performance registration screen; Fig. 20 is a drawing showing an example of a configuration screen configured with a workpiece master; Fig. 21 is a drawing showing an example of a configuration screen displayed when a production performance registration has been selected and a production performance table has been configured; Fig. 22 is a drawing showing an example of a configuration screen displayed when a production performance table has been configured and input items have been selected; Fig. 23 is a drawing showing another example of the configuration screen displayed when a production performance table has been configured and input items have been selected; Fig. 24 is a drawing showing an example of configuration information for the production performance registration screen that has been updated; Fig. 25 is a flowchart for explaining a generation process performed by a screen generation device when configuration information is to be newly generated; Fig. 26 is a flowchart for explaining a generation process performed by the screen generation device when existing configuration information is to be edited; and Fig. 27 is a flowchart for explaining a generation process performed by the screen generation device when a work screen is to be displayed by selecting configuration information. Preferred embodiments of the invention

[0009] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. <Ausführungsform>

[0010] Fig. 1 is a functional block diagram of a screen generation system according to one embodiment.

[0011] As in Fig. 1, a screen generation system SYS comprises a screen generation device 1, a data source 2 and devices 3.

[0012] The screen generation device 1, the data source 2, and the devices 3 may be connected to each other via a network (not shown), such as a local area network (LAN) or the Internet. In this case, the screen generation device 1, the data source 2, and the devices 3 may each include a communication unit (not shown) to communicate with each other via such connections. Furthermore, the screen generation device 1, the data source 2, and the devices 3 may be directly connected to each other via a connection interface (not shown), either wired or wirelessly.

[0013] In addition, the screen generating device 1, although in Fig. 1 is connected to one data source 2 and one device 3, may be connected to two or more data sources 2 and two or more devices 3. <Datenquelle 2>

[0014] The data source 2 may, for example, be a data server, a cloud server, or similar, which stores data such as a device status table and a production performance table that display information about the devices 3 deployed at each work location, e.g., in a factory.

[0015] Fig. Figure 2 is a drawing showing an example of a device status table.

[0016] As in Fig. As shown in Figure 2, the device status table has, for example, memory areas for “Device Name”, “ZStatus Start Time”, “Device Status” and “Program”.

[0017] In the storage area for the “Device Name” in the device status table, devices such as “Device 1” and “Device 2” are stored.

[0018] The memory area for the “status start time” in the device status table stores, for example, the start date / times at which the device status assumed the current status.

[0019] For example, the “Device Status” storage area in the Device Status Table stores information indicating the current status such as “in operation” or “out of operation” for each of the devices corresponding to the “Device Name”.

[0020] The memory area for the "Program" in the device status table stores, for example, a program that is currently running or was last run, such as "Program 1" or "Program 2", with respect to each of the devices corresponding to the "Device Name".

[0021] In addition, the production performance table can be stored in data source 2 (which can include, for example, workpiece IDs, device names, step names, start times, completion times, etc.). <Geräte 3>

[0022] The device 3 may be a numerical control device, a robot control device, a machine tool, a robot, or the like, provided at the worksite, e.g., in the factory. Data such as an executable function list indicating executable functions is stored in the device 3. The device 3 outputs data such as the executable function list, along with a device status indicating the current status, or the like, to the screen generation device 1 and the data source 2. < Screen generating device 1>

[0023] The screen generating device 1 may be, for example, a web server, a cloud server, a virtual server, or the like, and may be connected to a display device (not shown) of a computer or the like that displays a manufacturing-related screen via a network (not shown) such as a LAN or the Internet.

[0024] In this situation, examples of screens related to production include a factory monitoring screen, a screen for checking equipment status, a screen for checking overall equipment effectiveness (OEE), and a screen for recording the start and completion of steps. Examples of screens related to equipment maintenance include a screen for recording actual maintenance performance, a screen for registering a maintenance plan, and a screen used to look up maintenance history. Examples of a screen related to product quality include a screen for registering a product measurement result and a screen used to understand a trend in the product measurement results. However, the possible embodiments are not limited to these examples.The present disclosure is applicable to any display relating to manufacturing or production.

[0025] As explained above, the screen generated by the screen generating device 1 is applied to the display device (not shown) as described below. The display device (not shown) displays the screen generated by the screen generating device 1 on a display unit (not shown), such as a liquid crystal display, to display the screen in terms of manufacturing. In this situation, the screen generating device 1 may be directly connected to the display device (not shown) via a connection interface (not shown).

[0026] Even if it is a device other than the display device (not shown), as will be explained later, the screen generating device 1 may be constructed to include the display device (not shown).

[0027] As in Fig. As shown in Figure 1, the screen generation device 1 includes: a control unit 10, a storage unit 20, an input device 30 such as a keyboard, a mouse, a touch panel, and / or the like, and an output device 40 such as a liquid crystal display. Furthermore, the control unit 10 includes a template generation unit 100, a meta-information acquisition unit 101, an automatic configuration screen generation unit 102, a configuration information generation unit 103, an automatic screen generation unit 104, a configuration information management unit 105, and a user information management unit 106. <Speichereinheit 20>

[0028] The storage unit 20 may be a solid state drive (SSD), a hard disk drive (HDD), or the like. Along with an operating system, an application program, and the like executed by the control unit 10, the storage unit 20 stores m pieces of template information 200-1 to 200-m, n pieces of configuration information 210-1 to 210-n, and user information 220 (where m and n each denote an integer of 1 or greater).

[0029] In the following sections, the pieces of template information 200-1 to 200-m may be collectively referred to as "template information 200" if no individual distinction is required. If no individual distinction is required, the pieces of configuration information 210-1 to 210-n may also be referred to as "configuration information 210."

[0030] The template information 200 is, for example, information for generating a screen (which may be referred to as a “work screen” hereinafter) and is generated in advance by the template generation unit 100 (explained later) based on an operation performed by a template generator. As shown in Fig. 3, the template information 200 includes a template ID predefined by the template creator, a template screen 201, configuration items 202, and a template behavior 203. In addition, as explained later, the configuration items 202 include appearances / behaviors 202a and usage data 202b due to differences in the accompanying information and configuration screens to be used to specify configuration.

[0031] The template ID is an identifier for uniquely identifying the template information 200 and can be configured, for example, from letters, numbers or a combination of both, such as “XXX”.

[0032] The following explains examples of the template screen 201, the configuration items 202, and the template behavior 203 in cases where the template information 200 is (a) the factory monitoring screen and (b) a production performance registration screen. However, it should be noted that the template screen 201, the configuration items 202, and the template behavior 203 on screens other than the factory monitoring screen and the production performance registration screen are also the same as those on the factory monitoring screen and the production performance registration screen. (a) An example of the factory monitoring screen

[0033] Fig. 4 is a drawing showing an example of the template screen 201 in the template information 200 on the factory monitoring screen.

[0034] As in Fig. 4, the template screen 201 is configured, for example, with six components 230a to 230f. Components 230a and 230d are each configured with text to display a device name. Components 230b and 230e are each configured with a device icon representing the corresponding device 3. Components 230c and 230f are each configured with a text field to display, for example, the name of a workpiece produced with the corresponding device.

[0035] Fig. 5 is a drawing showing examples of the appearances / behaviors 202a in the configuration items 202 in the template information 200 on the factory monitoring screen. Fig. 5 shows the appearances / behaviors 202a in the configuration items 202 for the component 230b (a device symbol A) among the components 230a to 230f on the template screen 201. As in Fig. As shown in Figure 5, the appearances / behaviors 202a in the configuration entries 202 for the component 230b may include the accompanying information. Furthermore, the configuration items 202 do not necessarily have to correspond to any of the components on the template screen 201. For example, it is possible to provide the configuration items in necessary units, such as those relating to the entirety of the template screen or those relating collectively to multiple components.

[0036] In other words, the appearances / behaviors 202a for component 230b have configuration item groups such as "entire screen," "configuration shared by device icons," "configuration shared by labels," and four "device icons A," and the like. Furthermore, the appearances / behaviors 202a include the accompanying information corresponding to each of the configuration item groups such as "entire screen," "configuration shared by device icons," "configuration shared by labels," and the four "device icons A" to the items enclosed in the dashed box in the second row and thereafter. The accompanying information for the appearances / behaviors 202a includes items such as "configuration item name," "classification," "default value," "detailed configuration item," "script input capability," "input type," and "description."This accompanying information serves as a kind of configuration conditions for the manifestations / behaviors 202a.

[0037] A storage area for the "configuration item name" in the accompanying information stores a name for identifying a corresponding configuration item with respect to each of the configuration item groups comprising the appearances / behaviors 202a. In the accompanying information in Fig. 5, with respect to each of the configuration item groups, such as the “entire screen,” the “configuration shared by device icons,” the “configuration shared by labels,” and the four “device icons A,” configuration values such as a “screen refresh interval,” an “icon size,” a “font size,” an “icon color,” a “position (top),” a “position (left),” a “screen transition target,” or the like are stored.

[0038] The storage area for the “Classification” in the accompanying information stores classifications of the manifestations / behaviors 202a. In the accompanying information in Fig. 5, either "behavior" or "appearance" is stored with respect to each of the configuration item groups, such as "entire screen", "configuration shared by device icons", "configuration shared by labels" and the four "device icons A".

[0039] The storage area for the “default value” in the accompanying information stores the initial values of the manifestations / behaviors 202a. In the accompanying information in Fig. 5, with respect to each of the configuration item groups, such as "entire screen", "configuration shared by device icons", "configuration shared by labels", and the four "device icons A", the following is stored: "10", "40 px", "10 pt", "{{$ .status == 1 ? 'green' : 'red'}}", "100 px", "100 px", or "boardld?machineld=machineld". In this case, "10" indicates that the screen is refreshed at an interval of ten seconds. In addition, "40 px" indicates that the size of the icon for the device is 40 pixels. In addition, "10 pt" indicates that the font size of the label is 10 points. Furthermore, for example, “{{$ .status == 1 ? 'green' : 'red'}}” is written in JavaScript (registered trademark) and indicates that if the variable “status” configured in the data is equal to “1”, the device icon is colored “green” and otherwise the device icon is colored “red”.Furthermore, "100 px" indicates the top and left coordinates where the device icon A is positioned as component 230b on the working screen. Furthermore, "boardld?machineld=machineld" indicates a screen transition target that is used when the device icon A is pressed.

[0040] The storage area for the "detailed configuration item" in the accompanying information stores whether the configuration item should be displayed (true) or not displayed (false) on the configuration screen used to configure the configuration item, since the detailed configuration is a configuration item with a low change frequency. In the accompanying information in Fig. 5 is stored as either “false” or “true” with respect to each of the configuration item groups such as “entire screen”, “configuration shared by device icons”, “configuration shared by labels” and the four “device icons A”.

[0041] The "Script Input Capability" storage area in the accompanying information stores as a configuration value whether a script is configurable (true) or not configurable (false). In the accompanying information in Fig. 5 is stored as either “false” or “true” with respect to each of the configuration item groups such as “entire screen”, “configuration shared by device icons”, “configuration shared by labels” and the four “device icons A”.

[0042] The storage area for the "Input Types" in the accompanying information stores the data types for the configuration values. In the accompanying information in Fig. 5, with respect to each of the configuration item groups, such as ‘entire screen’, ‘configuration shared by device icons’, ‘configuration shared by labels’ and the four ‘device icons A’, the following is stored: ‘numeric value’, ‘pixel’, ‘point’, ‘color’, ‘pixel’, ‘pixel’ or ‘string’.

[0043] The "Description" storage area in the accompanying information stores a description to inform a screen generator about the meaning of the names of the configuration items.

[0044] Fig. 6 is a drawing showing an example of the usage data 202b in the configuration entries 202 in the template information 200 on the factory monitoring screen. Fig. Figure 6 shows the usage data 202b in the configuration entries 202 corresponding to component 230b (device symbol A) and component 230c (label A) among components 230a to 230f on the template screen 201. In this case, the usage data 202b of components 230a and 230d to 230f are the same as in the examples with component 230b and component 230c, so the explanations are omitted. As in Fig. 6, the usage data 202b in the configuration elements 202 corresponding to the component 230b and the component 230c may include the accompanying information.

[0045] In other words, the usage data 202b corresponding to the component 230b and the component 230c includes the configuration item groups such as "device icon A," "label A," and the like. Furthermore, the usage data 202b includes the items enclosed in the dashed box in the second row and thereafter as accompanying information corresponding to each of the configuration item groups such as "device icon A" and "label A," while including items such as "configuration item name," "classification," "usage data name," "meta information," "acquisition condition," and "description." This accompanying information serves as a type of configuration condition for the usage data 202b.

[0046] The storage area for the "configuration item name" in the accompanying information stores therein, with respect to each of the configuration item groups comprising the usage data 202b, a configuration value indicating whether the data represents a status or a specific variable. In the accompanying information in Fig. 6, with respect to each of the configuration element groups, such as the “Device Symbol A” and the “Label A”, the following configuration value is stored: “Status”, “Variable 1” or the like.

[0047] The storage area for the “Classifications” in the accompanying information stores classifications of the usage data 202b. In the accompanying information in Fig. 6 “Usage data” is stored for each of the configuration groups, such as “Equipment Symbol A” and “Label A”.

[0048] The “Usage Data Name” storage area in the accompanying information stores a usage data variable name such as “Status” or “Variable 1” related to each of the configuration item groups such as “Device Icon A” and “Label A”.

[0049] The “meta information” storage area in the accompanying information stores therein meta information of the usage data associated with each of the configuration item groups such as the “device icon A” and the “label A” based on meta information of the data stored in the data source 2, the device 3, and the like acquired by the meta information acquisition unit 101 (explained later).

[0050] The "collection condition" storage area in the accompanying information stores therein a condition (e.g., a "device name", a "status start time", a "sorting order", a "collection amount", etc.) and a default value (e.g., "=", "descending order", "1", etc.) to be used at the time of collecting the usage data corresponding to each of the configuration item groups such as "device icon A" and "description A".

[0051] The "Description" storage area in the accompanying information stores a description to inform the screen generator about the meaning of the names of the configuration items.

[0052] The template behavior 203 stores, for example, source code such as a script for executing a process based on the configurations of the appearances / behaviors 202a and the usage data 202b. The source code of the template behavior 203 may, for example, include code to refresh the screen at a specific time interval (e.g., 10 seconds) configured as the "screen refresh interval" in the appearances / behaviors 202a. Further, the source code may include code that captures data from the metainformation associated with the "status" of the "device icon A" in the usage data 202b and makes the captured data usable as the usage data name "status." Further, the source code may include code that captures data from the metainformation associated with the "variable 1" of the "label A" in the usage data 202b and makes the captured data usable as the usage data name "variable 1."Additionally, the source code may include code that interprets a script of the configuration value of the appearances / behaviors 202a based on the usage data 202b (e.g., determines that the icon should be colored "green" because the value of the "status" for the "device icon A" is "1") or that displays the template screen 201 based on the configuration value.

[0053] The template information 200 in the factory monitoring screen example has thus been explained. (b) An example of the production performance registration screen

[0054] Fig. 7 is a drawing showing an example of the template screen 201 in the template information 200 on the production performance registration screen.

[0055] As in Fig. For example, as shown in Figure 7, the template screen 201 is configured with four components 240a to 240d. Components 240a and 240b are configured with text boxes for displaying a workpiece ID and a step. Components 240c and 240d are configured with buttons for entering a start time and a completion time of the step corresponding to the aforementioned workpiece ID.

[0056] Fig. 8 is a drawing showing examples of the appearances / behaviors 202a in the configuration items 202 in the template information 200 on the production performance registration screen. Fig. 8 shows the appearances / behaviors 202a in the configuration elements 202 corresponding to the components 240a and 240b, among the components 240a to 240d on the template screen 201. As in Fig. 8, the appearances / behaviors 202a in the configuration elements 202 corresponding to the components 240a and 240b may include accompanying information.

[0057] In other words, the appearances / behaviors 202a corresponding to components 240a and 240b include configuration item groups such as "input item." Furthermore, the appearances / behaviors 202a include the items enclosed in the dashed box in the second row and thereafter as accompanying information corresponding to each of the configuration item groups, such as the two "input names," including items such as "configuration item name," "classification," "default value," "detailed configuration item," "script input capability," "input type," and "description."

[0058] The storage area for the "configuration item names" in the accompanying information stores, for each configuration item group contained in the appearances / behaviors 202a, a name for identifying a corresponding one of the configuration items. In the accompanying information in Fig. 8, a configuration value, such as “Element Name” or “Master”, is stored with respect to each of the configuration element groups, such as the two “Input Elements”.

[0059] The storage area for the “Classification” in the accompanying information stores classifications of the manifestations / behaviors 202a. In the accompanying information in Fig. 8 is stored in relation to each of the configuration element groups, such as the two “input elements”, “appearance” or “appearances / behaviors”.

[0060] The memory area for the “default value” in the accompanying information stores initial values of the appearances / behaviors 202a. In the accompanying information in Fig. 8, with respect to each of the configuration item groups, such as the two "input items," the following is stored: "[Workpiece ID, Step]" or "{{$.master1}}, {{$.master2}}." The notation "{{$.master1}}, {{$.master2}}" can be written, for example, in JavaScript (registered trademark) and stores (displays) data corresponding to the metainformation acquired by the metainformation acquisition unit 101 (explained later).

[0061] The storage area for the "detailed configuration item" in the accompanying information stores whether the configuration item should be displayed (true) or not displayed (false) as a detailed configuration, which is a configuration item with a low change frequency, on the configuration screen used for configuring the configuration item. In the accompanying information in Fig. 8 is stored as either “false” or “true” with respect to each of the configuration element groups, such as the two “input elements”.

[0062] In the "Script Input Capability" storage area in the accompanying information, the configuration value stores whether a script is configurable (true) or not configurable (false). In the accompanying information in Fig. 8 is stored as either “false” or “true” for each of the configuration groups, such as the two “input elements”.

[0063] The storage area for the "Input Type" in the accompanying information stores the data types for the configuration values. In the accompanying information in Fig. 8 is stored for each of the configuration element groups, e.g. the two “input elements”, “string, array”.

[0064] The "Description" storage area in the accompanying information stores a description to inform the screen generator about the meaning of the names of the configuration items.

[0065] Fig. 9 is a drawing showing an example of the usage data 202b in the configuration items 202 in the template information 200 on the production performance registration screen. Fig. 9 shows the usage data 202b in the configuration items 202 corresponding to each of the components 240a and 240b among the components 240a to 240d on the template screen 201. Since the usage data 202b of the components 240c and 240d also correspond to those of the components 240a and 240b, their explanation is omitted. As in Fig. 9, the usage data 202b in the configuration elements 202 corresponding to the components 240a and 240b may include accompanying information.

[0066] In other words, the usage data 202b corresponding to the components 240a and 240b includes configuration item groups such as "production performance registration," "master," and the like. Furthermore, the usage data 202b includes the items enclosed in the dashed box in the second row and thereafter as the accompanying information corresponding to each of the configuration item groups such as the three "production performance registrations" and the "master," while including items such as "configuration item name," "classification," "usage data name," "meta information," "acquisition condition," and "description." This accompanying information serves as a type of configuration condition for the usage data 202b.

[0067] In the storage area for the "configuration item name" in the accompanying information, a configuration value is stored for each of the configuration item groups included in the usage data 202b, indicating which element it is. In the accompanying information in Fig. 9 For each of the configuration groups, such as the three “production performance registrations” and the “master”, the following configuration value is stored: “start time”, “completion time”, “registration item”, “input item master” or similar.

[0068] The storage area for the “Classification” in the accompanying information stores classifications of the usage data 202b. In the accompanying information in Fig. 9 “Usage data” is stored for each of the configuration groups, such as the three “Production Performance Registrations” and the “Master”.

[0069] The “usage data name” storage area in the accompanying information stores therein a variable usage data name such as “- (empty)” or “Master” with respect to each of the configuration item groups in the usage data 202b such as the three “production performance registrations” and the “Master”.

[0070] The storage area for the “meta information” in the accompanying information stores therein meta information of the usage data associated with each of the configuration item groups in the usage data 202b, such as the three “production performance registrations” and the “master”, based on the meta information of the data stored in the data source 2, the device 3, and the like, which was acquired by the meta information acquisition unit 101 (explained later) from the data source 2, the equipment 3, and the like.

[0071] The storage area for the "acquisition condition" in the accompanying information storage contains a condition to be used at the time of acquiring the usage data with respect to each of the configuration item groups in the usage data 202b, such as the three "production performance registrations" and the "master". In the usage data 202b in Fig. 9 is configured to “- (empty)”.

[0072] The "Description" storage area in the accompanying information stores a description to inform the screen generator about the meaning of the configuration item names.

[0073] For example, the template behavior 203 on the production performance registration screen stores source code such as a script used to execute a process based on the configurations of the appearances / behaviors 202a and the usage data 202b. The source code of the template behavior 203 may include, for example, code for acquiring master data from the metainformation associated with the "master input item" of the appearances / behaviors 202a and setting the acquired master data into various types of pull-down menus. Furthermore, the source code may include code for re-registering data based on a current time and input status when the START button serving as component 240c is pressed.The source code may further include code for updating data based on a current time and an input status when the COMPLETE button serving as component 240d is pressed. The source code may further include code for displaying an input interface (e.g., a workpiece, a step, a device, etc.) in accordance with the configuration value of the input element.

[0074] This explains the template information 200 in the example of the production performance registration screen.

[0075] Next, the configuration information 210 is explained.

[0076] The configuration information 210 is generated by the configuration information generation unit 103 (explained later).

[0077] Fig. 10 is a drawing showing an example of the configuration information 210. In this case, Fig. 10 an example of the configuration information 210 for the factory monitoring screen.

[0078] As in Fig. 10, the configuration information 210 includes a configuration information ID (an automatically generated UUID or the like when the configuration information is newly created) for identifying the configuration information 210, a screen name, and a template ID of the template information 200 to be used.

[0079] As will be explained later, the configuration information 210 comprises a table 211 in which a configuration item group whose default value is defined by the screen generator among the Fig. 5, as well as a configuration item name and a configuration value after the change. Furthermore, the configuration information 210 includes a table 212 in which a configuration item group whose default value was changed by the screen generator is stored under the configuration item names shown in Fig. 6, as well as a configuration element name and a configuration value after the change.

[0080] The configuration information 210 is thus explained.

[0081] Next, user information 220 is explained.

[0082] In the user information 220, information about a user is stored in advance.

[0083] More specifically, the user information 220 may include, for example, a user ID, full name, phone number, email address, and the like of the user, along with a current role, department, years of service, and the like. Furthermore, as explained later, the user information 220 may include information about the operating permission on the work screen or the like. <Steuereinheit 10>

[0084] The control unit 10 includes a CPU, a ROM, a RAM, a CMOS memory, and the like. These elements are capable of communicating with each other via a bus and are well known among those skilled in the art.

[0085] The CPU is a processor that controls the entirety of the screen generating device 1. The CPU reads a system program and an application program stored in the ROM via the bus and controls the entirety of the screen generating device 1 according to the system program and the application program. As shown in Fig. 1, the control unit 10 is configured to realize functions of the template generation unit 100, the meta information acquisition unit 101, the automatic configuration screen generation unit 102, the configuration information generation unit 103, the automatic screen generation unit 104, the configuration information management unit 105, and the user information management unit 106. The RAM stores various types of data such as temporary calculation data, display data, and the like. The CMOS memory is configured as a non-volatile memory backed by a battery (not shown) and maintains a storage status even when the electric power supply of the screen generation device 1 is turned off.

[0086] Although the present embodiment uses the example in which the screen generation device 1 includes the template generation unit 100, possible embodiments are not limited to this example. The template generation unit 100 may be configured as a template generation device (not shown) that is a different device from the screen generation device 1. In other words, the template generator can generate the template information 200 using the template generation device (not shown) and provide the generated template information 200 to a large number of users.

[0087] Before explaining in detail the individual functions such as the template generation unit (100), the meta-information acquisition unit (101), the automatic configuration screen generation unit (102), the configuration information generation unit (103), the automatic screen generation unit (104), the configuration information management unit (105), and the user information management unit (106), an overview of the operation of each function will be provided. The template generation unit 100 generates the template information 200 corresponding to the functions of the device or the workstation, e.g., a factory, based on an input operation performed by the template generator via the input device 30, and stores the generated template information 200 in the storage unit 20.

[0088] The meta information acquisition unit 101 acquires the meta information of the data stored in the data source 2, the device 3, and the like from the data source 2, the device 3, and the like, and outputs the acquired meta information to a configuration screen generated by the automatic configuration screen generation unit 102.

[0089] The automatic configuration screen generation unit 102 reads from the storage unit 20 the template information 200 selected by the screen generator who generates (customizes) a working screen and also generates the configuration screen to generate the configuration information 210 related to the configuration item with respect to the entire screen or each of the components (e.g., components 230a to 230f) on the screen, based on the appearances / behaviors 202a and the usage data 202b in the configuration items 202 defined in advance in the read template information 200. If the screen generator has selected existing configuration information 210, the automatic configuration screen generation unit 102 may also read from the storage unit 20 the template information 200 associated with the selected configuration information 210.The automatic configuration screen generation unit 102 may generate a configuration screen for editing (customizing) the selected configuration information 210 based on the appearances / behaviors 202a and the usage data 202b in the configuration items 202 defined in advance in the read template information 200 and the configuration information 210.

[0090] The configuration information generation unit 103 generates the configuration information 210 based on the configuration value configured or edited by the screen generator on the configuration screen generated by the automatic configuration screen generation unit 102, and stores the generated configuration information 210 in the storage unit 20.

[0091] The automatic screen generation unit 104 generates the work screen serving as a manufacturing-related screen based on the configuration information 210 selected according to an input operation performed by a screen user and the template information 200 associated with the selected configuration information 210, and further causes the generated work screen to be displayed on a display device (not shown).

[0092] The configuration information management unit 105 manages the configuration information 210 generated by the configuration information generation unit 103 based on the configuration information ID with which the configuration information 210 is configured.

[0093] The user information management unit 106 manages the user information 220 with respect to each of the users, such as the template creator, the screen creator, and the screen user. <Template generation unit 100>

[0094] The template generation unit 100 generates the template information 200 corresponding to the functions of the device 3 or the workstation, e.g., a factory, based on an input operation performed by the template generator via the input device 30, and stores the generated template information 200 in the storage unit 20.

[0095] More specifically, for example, after receiving an instruction to generate the template information 200 according to the input operation performed by the template generator, the template generation unit 100 displays a generation screen 300 for the template information 200 on the output device 40.

[0096] Fig. 11 shows an example of the generation screen 300 for the template information 200.

[0097] As in Fig. As shown in Figure 11, the generation screen 300 includes a template screen configuration area 310 and a component list 320. In this case, the component list 320 includes, as components, for example, buttons (e.g., a pull-down menu, a run button, etc.), a table, a device icon, a text display, and / or the like. Furthermore, each of the components can be configured with the appearances / behaviors 202a and the usage data 202b in the configuration items 202 that are standard for the component.

[0098] For example, as in Fig. As shown in Figure 11, the template generation unit 100 drags the device icon according to an input operation performed by the template generator, and arranges and determines the device icon in a desired position. With respect to components 230a and 230c to 230f, the template generation unit 100 similarly drags to arrange and determine a device icon, a text display, or the like in a desired position according to an input operation performed by the template generator. As a result, the template generation unit 100 is able to Fig. 4 or the like.

[0099] After the components, such as the device icon, and their arrangement positions have been determined, the template generation unit 100 automatically generates the template screen 201, the appearances / behaviors 202a and the usage data 202b in the configuration items 202, and the source code of the template behavior 203 based on the types and arrangement positions of the components. In this case, the template generation unit 100 can edit the source code of the template behavior 203 based on an input from the template generator (e.g., adding a template behavior or adding a configuration item that is not associated with a component). Furthermore, the template generation unit 100 can generate or correct the appearances / behaviors 202a and the usage data 202b in the configuration items 202 corresponding to a component based on an input operation performed by the template generator.by adjusting a configuration item), if necessary. Further, the template generation unit 100 may generate new template information 200 based on the existing template information 200. Moreover, the template generation unit 100 may incorporate a debugging function for the template information 200. Furthermore, based on an operation performed by the template creator, the template generation unit 100 may configure the template information 200 with usage authorization information about users permitted to use the template information 200 and / or with editing authorization information about users permitted to edit the template information 200.

[0100] The template generation unit 100 stores in the storage unit 20 data including the template screen 201 configured in the configuration area 310 of the template screen, the appearances / behaviors 202a and the usage data 202b in the configuration items 202, and the template behavior 203 as template information 200. < Metainformation Acquisition Unit 101>

[0101] The meta information acquisition unit 101 acquires the meta information of the data stored in the data source 2, the device 3, and the like from the data source 2, the device 3, and the like, and outputs the acquired meta information to the automatic configuration screen generation unit 102.

[0102] More specifically, the meta-information acquisition unit 101 has, for example, previously acquired and registered metadata (e.g., a device name, a model number name, a responsible person's name, startup time information, device status information, a program name, etc.) related to the devices at each workstation, e.g., a factory, stored in the data source 2, as well as metadata (a device name, a function name, etc.) related to the devices and stored in the devices 3. In this case, the device 3 may have previously registered a list of functions that can be performed by the device 3, along with a registration of connection information (e.g., an IP address) of the device 3 to be configured at each workstation. Further, connection destination information (e.g., an IP address and password, etc.) may be stored in the data source 2.) of a database in advance, so that the meta information acquiring unit 101 acquires the meta information by executing a query.

[0103] Furthermore, the meta-information acquisition unit 101 may utilize a meta-information acquisition function of the device or software (e.g., an interface called Remote Procedure Call (RPC) for calling a function, etc.) used to communicate with the device and intended for an Internet of Things (IoT) platform. In this situation, it is desirable to configure the IoT platform to publish a document for users to indicate what type of meta-information (the interface (the RPC) used to call the function) is available from the device or the software (a converter) used to communicate with the device.In this way, the template creator can create the accompanying information (the configuration conditions) for the appearances / behaviors 202a and the usage data 202b in the configuration items 202 after understanding the functions of the device in advance.

[0104] When the IoT platform defines common meta information (an interface) related to common functions (e.g., transferring a file, acquiring a file, acquiring a list of files, deleting a file, configuring a variable, acquiring a variable, etc.) independent of the device, in order to use a device or software that communicates with the device according to the common functions, the template generator can generate the accompanying information (the configuration conditions) for the appearances / behaviors 202a and the usage data 202b in the configuration items 202 without being aware of the devices.

[0105] For example, if the data source 2 is a database, the meta information acquisition unit 101 acquires from the data source 2 a list of tables and a list of column names and formats for each of the tables as meta information of the data, as shown in Fig. 12 shown.

[0106] Fig. Figure 12 shows an example of the meta information in data source 2.

[0107] As in Fig. As shown in Figure 12, the meta information includes storage areas for “table name”, “column name” and “format”.

[0108] The storage area for the “table name” in the meta information stores tables (data) such as a “production performance table” and a “device status table”.

[0109] The storage area for the “column name” in the meta information stores, for example, column names such as “workpiece ID”, “step start time”, “step end time”, “step”, “device name”, “device status”, “status start time” and the like.

[0110] The “Format” storage area in the metadata stores, for example, a data format such as “string,” “date / time,” “numeric value,” or similar, for each of the column names listed under “Column Name.”

[0111] In this case, if the data is a CSV file or the like, the meta information acquiring unit 101 may acquire a list of file names or header names in each file as meta information.

[0112] If the meta information is the device 3, the meta information acquisition unit 101 may also acquire a list of functions (interfaces) that can be executed by the device and the arguments, as shown in Fig. 13 shown.

[0113] Fig. 13 is a drawing showing an example of the meta information of the device 3.

[0114] As in Fig. As shown in Figure 13, the meta information includes storage areas for “device”, “function name” and “argument”.

[0115] It is observed that the storage area for the “device” in the meta information of the device 3 obtained from the meta information acquisition unit 101 stores, for example, devices such as “machine tool A-1”, “machine tool A-2”, and so on.

[0116] It can be observed that the storage area for the “function name” in the meta information of the device 3 stores, for example, functions such as “save the machining program”, “start machining”, “door open / close function”, and the like.

[0117] It can be observed that the storage area for the “argument” in the meta information of the device 3 stores, for example, arguments such as a “start time” with respect to each of the functions in the “function name”.

[0118] In this case, when the meta information originates from the device 3, the meta information acquisition unit 101 may acquire the types, file names, formats, and the like of the data that can be acquired from the device 3. <Automatische Konfigurationsbildschirmerzeugungseinheit 102>

[0119] The automatic configuration screen generation unit 102 reads from the storage unit 20 the template information 200 selected by the screen generator, which generates (customizes) the work screen using the template information 200. Based on the template screen 201, the configuration items 202, and the template behavior 203 defined in advance in the read template information 200, the automatic configuration screen generation unit 102 generates a configuration screen for inputting configuration information used by the screen generator to customize (generate) the work screen, with respect to the entire work screen or each of the configuration items corresponding to the constituent parts. The automatic configuration screen generation unit 102 displays the generated configuration screen on the output device 40.In this way, the screen generator can customize (generate) the working screen through the configuration screen generated by the automatic configuration screen generation unit 102.

[0120] When the screen generator has selected existing configuration information 210 generated by the configuration information generation unit 103 (explained later), the automatic configuration screen generation unit 102 may read the selected configuration information 210 from the storage unit 20. The automatic configuration screen generation unit 102 may read the template information 200 corresponding to the template ID associated with the configuration information 210 from the storage unit 20. Based on the existing configuration information 210 and the read template information 200, the automatic configuration screen generation unit 102 may generate a configuration screen for inputting a configuration, which is used by the screen generator to edit the already generated configuration information (screen) with respect to each of the configuration items.In this way, the screen generator can adjust (edit) the existing configuration information 210 (screen) through the configuration screen generated by the automatic configuration screen generation unit 102.

[0121] Furthermore, based on the authorization information in the user information 220 and the editing authorization information configured in the template information 200, the automatic configuration screen generation unit 102 may generate a configuration screen including only one or more configuration items for which editing operations are permitted depending on the user.

[0122] Next, examples will be explained where the generated configuration screen is (a) a configuration screen for the factory monitoring screen and (b) a configuration screen for the production performance registration screen. In this case, in the factory monitoring screen example (a), an example will be explained where the screen generator selects the template information 200 to newly generate a configuration screen. Furthermore, in the production performance registration screen example (b), an example will be explained where the screen generator selects the existing configuration information 210 to generate a configuration screen for editing the selected existing configuration information 210.In addition, the automatic configuration screen generation unit 102 is also capable of generating configuration screens for screens other than the factory monitoring screen and the production performance registration screen, in the same manner as the factory monitoring screen and the production performance registration screen. (a) Regarding the factory monitoring screen configuration screen

[0123] More specifically, for example, upon receiving an instruction to select the screen 200 from the screen generator via the input device 30, the automatic configuration screen generation unit 102 displays on the output device 40 a screen management screen 400 including a CREATE NEW button 401 generated by the configuration information management unit 105 (explained later) and a configuration information table 402 of the existing configuration information 210, as shown in Fig. 14A. In this case, the configuration information table 402 includes the IDs of the configuration information 210, the name of a work screen to be generated based on each piece of configuration information 210, and the buttons or keys corresponding to the configuration information 210. Further, the operation keys include a display button for displaying the work screen based on the configuration information 210; an edit button for displaying a configuration screen for editing the configuration information 210; a copy button for copying the configuration information 210; and a delete button for deleting the configuration information 210.

[0124] As a result of pressing the RECREATE button 401 on the screen management screen 400 based on an input operation performed by the screen generator via the input device 30, the automatic configuration screen generation unit 102 causes a Fig. 14B is displayed on the output device 40. In this case, the template selection screen 410 includes, as shown in Fig. 14B, a template information table 411 with the template information 200, a DELETE button 412 and a CREATE button 413.

[0125] When the CREATE button 413 is pressed after the template information 200 in the row corresponding to the “factory monitoring screen” identified with the ID “1” in the template information table 411 on the template selection screen 410 is selected based on an input operation performed by the screen generator via the input device 30, the automatic configuration screen generation unit 102 generates a configuration screen 450 for the Fig. Factory monitoring screen shown in Figure 15.

[0126] Fig. Figure 15 shows an example of the factory monitoring configuration screen 450.

[0127] As in Fig. 15, the generated configuration screen 450 includes, for example, five display areas 451 to 455. The display area 451 displays an input field for entering an arbitrary screen name (a configuration information name), such as "Factory Monitoring Screen," and a SAVE key / button 456 for saving a configuration value configured on the configuration screen 450, or the like. Furthermore, the display area 452 displays a pull-down menu used to select one of the configuration item groups from the list of configuration item groups (e.g., the entire screen or the areas represented by the device icons in Fig. 5 shared configuration). Furthermore, the display area 453 shows the template screen 201 as the default value in Fig. 4 from the template information 200 on the factory monitoring screen displayed on the template selection screen 410 in Fig. 14A was selected. As explained later, the display area 454 displays an interface used to set up a configuration related to the usage data based on the accompanying information of the component usage data 202b (or the entire screen) related to the configuration item group selected in the display area 452 or the template screen 201 selected in the display area 453. As explained later, the display area 455 displays an interface used to set up a configuration for each of the configuration items based on the accompanying information of the component appearances / behaviors 202a (or the entire screen) related to the configuration item group selected in the display area 452 or the template screen 201 selected in the display area 453.

[0128] For example, based on an input operation performed by the screen creator who creates (customizes) the working screen using the template information 200, the device icon A (the component 230b in Fig. 4), which represents the “Machine Tool A-1”, on the configuration screen 450 in Fig. 15 is selected from the template screen 201 displayed in the display area 453. As a result, the configuration screen 450 causes a configuration screen related to the usage data 202b for the selected equipment icon A (the component 230b) to be displayed in the display area 454, and further causes a configuration screen related to the appearances / behaviors 202a for the selected equipment icon A (the component 230b) to be displayed in the display area 455. In this situation, the configuration screen 450 can realize the same display based on an input operation performed by the screen creator even when the "Equipment Icon A" is selected from the pull-down menu for the configuration item group displayed in the display area 452.

[0129] Fig. Figure 16 shows an example of the configuration screen 450 that appears when the device icon (component 230b) is selected. The same features apply to the other components 230a and 230c through 230f as in the example of component 230b.

[0130] For example, if the "equipment icon A" is selected from the pull-down menu of the configuration item group in the display area 452, the configuration screen 450 realizes a display in the display area 453 in which the selected equipment icon (the component 230b) is surrounded by a solid rectangular frame.

[0131] As in Fig. 16, the configuration screen 450 displays the interface for the configuration items, such as an icon color, the display position, and the like, of the selected device icon A (the component 230b), based on the accompanying information of the appearances / behaviors 202a. In other words, for example, triggered by selecting the device icon A from the pull-down menu for the configuration item group in the display area 452, the configuration screen 450 displays a text field for entering configuration values (a character string, a numeric value, a script, etc.), an icon color, a screen transition target, and the like, based on the accompanying information of the appearances / behaviors 202a in Fig. 5. On the configuration screen 450 in Fig. 16, for example, the text field for the icon color and the screen transition target shows the default values of the appearance / behavior 202a in Fig. 5. If the screen generator has subsequently added a condition that the device icon A (component 230b) should be colored “yellow” if the status of the device icon A (component 230b) is “2”, the script for the icon color configuration element is processed as shown in Fig. 17 shown.

[0132] In this way, the screen generator can specify the configurations relating to the appearances / behaviors 202a by referring to the displayed default values (the configuration values), thus saving the need to enter configuration values for all configuration items that may remain at the default values.

[0133] Furthermore, on the configuration screen 450 in Fig. 16 under the detailed element configurations for the manifestations / behaviors 202a in Fig. 5 the position (top) and the position (left) of the configuration items configured to be "true" are integrated together and displayed, for example, as a detailed item configuration so that it can be used in accordance with an operation (press) performed by the screen generator on a section corresponding to the detailed configuration. Fig. Figure 16 shows the configuration screen 450 that is displayed when the detailed configuration has been used.

[0134] Furthermore, the configuration screen 450, triggered by the selection of the “Device Icon A” from the pull-down menu for the configuration item group in the display area 452, displays in the display area 454 an interface for the configuration item for the usage data corresponding to the selected device icon A (the component 230b) based on the accompanying information of the usage data 202b, as shown in Fig. 17. For example, on the configuration screen 450, the table name containing the meta information acquired by the meta information acquisition unit 101 is Fig. 12, is configured in a pull-down menu 460. After selecting the "Device Status Table" from the pull-down menu 460 according to an input operation performed by the screen generator, the configuration screen 450 displays the column names and formats in the selected table as a column name list 462. Further, the configuration screen 450 displays a configuration item 461 corresponding to the "Device Icon A" selected from the pull-down menu for the configuration item group in the display area 452, as well as already configured meta information 463 with which the column names are to be configured by a drag-and-drop operation or the like from the column name list 462 to the configuration item 461.

[0135] For example, if the column name "Device Status (the numerical value)" in the column name list 462 has been dragged and dropped into the configuration item 461 based on an input operation performed by the screen creator, the configuration screen 450 displays a collection condition button 464 used to configure a collection condition for the data representing the "Device Status Table / Device Status" configured in the already configured meta information 463, according to the accompanying information of the usage data 202b in the configuration items 202 for the component 230b. Thereafter, the configuration screen 450, triggered by pressing the COLLECTION CONDITION button 464 based on an input operation by the screen creator, realizes a modal display of a configuration screen 465 for the collection condition, as shown in Fig. 18. Based on the “collection condition” in the accompanying information for the usage data 202b in Fig. 6, for example, the configuration screen 450 requests the screen creator to configure the "device name" as "Machine Tool A-1" and further receives input from the screen creator.

[0136] Further, based on the "collection condition" in the accompanying information for the usage data 202b, the configuration screen 450 configures the configuration value of each of the configuration items related to the status start time, the sorting order, and the collection amount using the default value. Furthermore, the configuration value of each of the configuration items related to the status start time, the sorting order, and the collection amount can be changed from the default value based on an input operation performed by the screen creator.

[0137] Furthermore, the configuration screen 450 can add a capture condition when an ADD button 466 is pressed through an input operation of the screen generator. In addition to "equal to (=)", the accompanying information for the usage data 202b can also be configured as capture conditions with "not equal to (#)", "comprehensive", a greater than / less than relationship, an aggregate function in Structured Query Language (SQL), a capture set, and the like.

[0138] After the configuration (editing of the screen) on the configuration screen 450 is completed, the screen creator presses the SAVE button 456, so that the configuration information creation unit 103 (explained later) can, based on the inputs on the configuration screen 450, create the e.g. Fig. 10, which is to be stored in the storage unit 20. (b) Regarding the configuration screen for the production performance registration screen

[0139] Upon receiving an instruction to select the screen information 200 from the screen generator via the input device 30, the automatic configuration screen generation unit 102 displays the screen management screen 400 on the output device 40 in Fig. 14A, which was generated by the configuration information management unit 105 (will be explained later). When the EDIT button is pressed for the configuration information 210 relating to the "production performance registration screen A" corresponding to the ID "YYY" on the screen management screen 400 based on an input operation performed by the screen generator via the input device 30, the automatic configuration screen generation unit 102 reads the configuration information 210 from the storage unit 20. The automatic configuration screen generation unit 102 reads from the storage unit 20 the template information 200 corresponding to the template ID configured in the read configuration information 210. Based on the template information 200 and the read configuration information 210, the automatic configuration screen generation unit 102 generates the Fig. 19 shown configuration screen 450 displayed on the output device 40.

[0140] Fig. 19 shows an example of the configuration screen 450 for the production performance registration screen.

[0141] As in Fig. 19, the generated configuration screen 450 displays, for example, the template screen 201 for the production performance registration screen based on the template information 200 read from the storage unit 20 in the display area 453.

[0142] For example, when the "Master" is selected from the pull-down menu in the display area 452 and a "Workpiece Master" is selected from a pull-down menu 470 in the display area 454, the configuration screen 450 displays a column name list 472 of the meta information of the selected "Workpiece Master" based on an input operation performed by the screen generator. Furthermore, the configuration screen 450 displays a configuration item 471 corresponding to the "Workpiece Master" and the already configured meta information 473, through which the column names from the column name list 472 are to be configured into the configuration item 471 by a drag-and-drop operation or the like. For example, as shown in Fig. 19, when the column name of "Workpiece ID (character string)" in the column name list 472 is dragged and dropped into the already configured meta information 473 based on an input operation by the screen generator, "Workpiece Master: Workpiece ID" is added. Furthermore, on the configuration screen 450, as shown in Fig. 20, when the "Step Master" and the "Device Master" are each similarly selected from the pull-down menu 470 in the display area 454 based on an input operation performed by the screen creator, the "Step Name (String)" and the "Device Name (String)" are each pulled from the column name list 472 and configured into the already configured meta information 473.

[0143] Next, for example, as in Fig. 21, when the "Production Performance Registration" is selected from the pull-down menu in the display area 452 and the "Production Performance Table" is selected from the pull-down menu 470 in the display area 454, the configuration screen 450 displays the column name list 472 of the meta information of the selected "Production Performance Table" based on an input operation performed by the screen generator. Similar to the example of the "Workpiece Master," on the configuration screen 450, based on an input operation performed by the screen generator, the "Start Time (Date / Time)" is dragged from the column name list 472 to the already configured meta information 473 and configured as the "Start Time (Date / Time)" in the configuration item 471.Further, on the configuration screen 450, based on an input operation of the screen creator, the "Completion Time (Date / Time)" is dragged and dropped from the column name list 472 into the already configured meta information 473 and configured as the "Completion Time (Date / Time)" in the configuration item 471. Furthermore, on the configuration screen 450, based on an input operation performed by the screen creator, the "Workpiece ID (String)", the "Step Name (String)", and the "Device Name (String)" can be dragged and dropped into the already configured meta information 473 from the column name list 472 as the "Registration Item (Strings, Multiple)" in the configuration item 471, as partially shown in the drawing.

[0144] When the “input item” is selected from the pull-down menu in the display area 452 based on an input operation performed by the screen generator, the configuration screen 450 displays in the display area 455 an interface of the configuration items of the item name, the master, and the detailed configuration including the selected input item, as shown in Fig. 22, based on the accompanying information of manifestations / behaviors 202a in Fig. 8. In other words, for example, triggered by selecting the “Input Item” from the pull-down menu for the configuration item group in the display area 452, the configuration screen 450 displays a text field for entering configuration values (a character string, a script, etc.) of the item name, the master, and the like based on the accompanying information of the manifestations / behaviors 202a in Fig. 8. Further, the configuration screen 450 may display ADD buttons 474 and 475 for the element name and the master to add configuration values of the element name and the master based on an input operation performed by the screen generator, as shown in Fig. 23. As a result, the screen creator can insert the "device" component 240e into the display area 453.

[0145] Additionally, the screen generator can create configurations related to the appearances / behaviors 202a and the usage data 202b by referring to the displayed default values (the configuration values). Furthermore, the screen generator can avoid entering configurations related to configuration items that do not need to be modified based on the selected configuration information.

[0146] After the configuration (editing of the screen) on the configuration screen 450 is completed, the screen creator presses the SAVE button 456, so that the configuration information creation unit 103 (explained later) creates the configuration information 210 based on what has been edited on the configuration screen 450 and further updates the configuration information 210 stored in the storage unit 20.

[0147] Fig. 24 is a drawing showing an example of the configuration information 210 for the production performance registration screen that has been updated.

[0148] As in Fig. 24, the configuration information 210 includes a configuration information ID configured when the information was newly created, a screen name, and a template ID of the template information 200 to be used.

[0149] Furthermore, the configuration information 210 includes a table 211 in which the configuration item groups whose default values have been changed by the creator of the screen are listed under the appearances / behaviors 202a in Fig. 8, as in Fig. 20 to 23, as well as configuration item names and configuration values after the change. Furthermore, the configuration information 210 includes a table 212 in which the configuration item groups whose default values were changed by the screen creator are stored under the usage data 202b in Fig. 9 as well as the names of the configuration elements and the values are saved after the configuration has been changed. <Konfigurationsinformationserzeugungseinheit 103>

[0150] Based on the information about the configuration items configured on the configuration screen 450, the configuration information generation unit 103 generates the configuration information 210.

[0151] More specifically, for example, when the SAVE button 456 on the configuration screen 450 is pressed by the screen generator, the configuration information generation unit 103 adds a configuration information ID (an automatically generated UUID or the like when the configuration information is newly generated), a screen mask name, a template ID of the template information 200 to be used to the configuration information 210, as shown in Fig. 10 or Fig. 24. The configuration information generation unit 103 generates, to be added to the configuration information 210, tables 211 and 212 that display the configuration item groups for the configuration items whose default values have been changed by the screen generator, among the appearances / behaviors 202a and the usage data 202b in the configuration items 202 of the template information 200 to be used, as well as configuration item names and configuration values after the change. The configuration information generation unit 103 stores (updates) the generated configuration information 210 in the storage unit 20. <Automatische Bildschirmerzeugungseinheit 104>

[0152] After receiving an instruction to select a work screen from the screen user via the input device 30, the automatic screen generation unit 104 displays, for example, on the output device 40 the Fig. 14A, which was generated by the configuration information management unit 105 (explained later). When a DISPLAY button for the work screen, such as the "Factory Monitoring Screen A" corresponding to the ID "XXX" on the screen management screen 400, is pressed based on an input operation performed by the screen user, the automatic screen generation unit 104 reads from the storage unit 20 the configuration information 210 for the selected work screen based on an instruction from the configuration information management unit 105 (explained later). The automatic screen generation unit 104 reads from the storage unit 20 the template information 200 corresponding to the template ID configured in the read configuration information 210.The automatic screen generation unit 104 generates a work screen as a production-related screen based on the read template information 200 and the configuration information 210. In this case, the automatic screen generation unit 104 may generate a work screen including only one or more configuration items for which operations are permitted depending on the user, based on the approval information in the user information 220 and the usage approval information in the template information 200.

[0153] The automatic screen generation unit 104 can transfer the generated work screen to a display device (not shown) as a screen for production. For example, the screen generation device 104 can be connected to a work system (not shown) so that the generated screen is provided to a work system (not shown). <Konfigurationsinformationsverwaltungseinheit 105>

[0154] The configuration information management unit 105 manages the configuration information 210 generated by the configuration information generation unit 103.

[0155] More specifically, for example, upon receiving an instruction to display the configuration information 210 from the user via the input device 30, the configuration information management unit 105 reads the configuration information 210 that can be displayed with respect to each user based on the user information 220 among the configuration information 210 stored in the storage unit 20. The configuration information management unit 105 displays on the output device 40 the configuration information 210 shown in Fig. 14A, which displays a list of the configuration information 210 read.

[0156] When the user presses the DISPLAY button, the configuration information management unit 105 outputs the selected configuration information 210 to the automatic screen generation unit 104. Based on the configuration information 210 and the corresponding screen information 200, the automatic screen generation unit 104 generates a work screen and displays the generated work screen on a display device (not shown). When the user presses the EDIT button, the configuration information management unit 105 outputs the selected configuration information 210 to the automatic configuration screen generation unit 102. The automatic configuration screen generation unit 102 generates the configuration screen 450 for the selected configuration information 210 to be displayed on the display device 40.Further, when a COPY SCREEN button is pressed by the user, the configuration information management unit 105 copies the selected configuration information 210 and stores the copied configuration information 210 in the storage unit 20 after assigning it a new configuration information ID. When the user presses a DELETE button, the configuration information management unit 105 deletes the selected configuration information 210 from the storage unit 20.

[0157] In this situation, the configuration information management unit 105 can, based on the authorization information in the user information 220, the usage authorization information and / or the editing authorization information in the template information 200, for example, control whether it is permitted to perform operations (display, edit, copy and delete) on each of the screens on the screen management screen 400 in Fig. 14A or not. Based on the user information 220, the configuration information management unit 105 can, for example, cause the buttons for the operations that are not permitted for each user to be not displayed, to be grayed out, or the like. <Nutzerinformationsverwaltungseinheit 106>

[0158] The user information management unit 106 manages the user information 220.

[0159] More specifically, the user information management unit 106 may manage, for example, in the user information 220, authorization information relating to the operations permitted for each user with respect to each screen (the configuration information 210). With this arrangement, as explained above, the configuration information management unit 105 may, based on the authorization information in the user information 220, the usage authorization information and / or the editing authorization information in the template information 200, for example, on the screen management screen 400 in Fig. 14A, control whether operations (viewing, editing, copying, and deleting) are permitted on each screen. For example, the configuration information management unit 105 may cause the buttons for operations that are not permitted to be hidden, grayed out, or the like.

[0160] Furthermore, the user information management unit 106 may manage, in the user information 220, authorization information related to a configuration editing operation with respect to each of the configuration items in the template information 200. With this arrangement, the automatic configuration screen generation unit 102 can control whether or not editing of the configuration items on the configuration screen 450 is permitted based on the authorization information in the user information 220 or the usage authorization information or the editing authorization information in the template information 200 (or the configuration information 210). For example, the automatic configuration screen generation unit 102 may cause the configuration items whose editing is prohibited to be not displayed, to be grayed out, or the like.

[0161] Alternatively, the automatic screen generation unit 104 may generate a work screen based on the authorization information in the user information 220 or the usage authorization information in the template information 200 (or the configuration information 210). In other words, even if the work screen is the same as a factory monitoring screen or a production performance registration screen, the configuration items to be displayed on the work screen may be different for different users. With this arrangement, it is possible to allow each user to monitor a different device 3, even if the work screen (the configuration information 210) is the same. <Von der Bildschirmerzeugungsvorrichtung durchgeführte Erzeugungsprozesse 1 >

[0162] In the following, a flow of generation processes performed by the screen generation device 1 will be described with reference to FIG. Fig. 25 to 27. In the following sections, the generation processes performed by the screen generation device 1 will be explained using (a) an example in which the configuration information 210 is to be newly generated, (b) an example in which the existing configuration information 210 is to be edited, and (c) an example in which the work screen is to be displayed. (a) The example in which the configuration information 210 is to be recreated

[0163] Fig. 25 is a flowchart for explaining a generation process performed by the screen generation device 1 when the configuration information 210 is to be regenerated. The flow in the present example is executed each time an instruction to regenerate a work screen is received from the screen generation device.

[0164] In step S11, the automatic configuration screen generation unit 102 receives a new generation instruction as a result of the screen generator pressing the CREATE NEW button 401 on the screen management screen 400 via the input device 30. The automatic configuration screen generation unit 102 receives a selection of the template information 200 for the work screen to be newly generated by the screen generator in the template information table 411 on the template selection screen 410.

[0165] In step S12, the meta information acquisition unit 101 acquires the meta information of the data in the data source 2, the device 3, and the like from the data source 2, the device 3, and the like.

[0166] In step S13, the automatic configuration screen generation unit 102 generates the configuration screen 450 based on the template information 200 of the work screen selected in step S11 to be displayed on the output device 40.

[0167] In step S14, the automatic configuration screen generation unit 102 receives configurations related to each of the appearances / behaviors 202a and the usage data 202b in the configuration items 202 based on an input operation on the configuration screen 450 performed by the screen generator.

[0168] In step S15, the configuration information generation unit 103, triggered, for example, by pressing the SAVE / SAVE button 456 on the configuration screen 450, generates the configuration information 210 to which the newly created configuration information ID, a screen template name, and a template ID of the template information 200 to be used are appended. Furthermore, the configuration information generation unit 103 generates tables 211 and 212 displaying the configuration item groups for the configuration items whose default values have been changed among the appearances / behaviors 202a and the usage data 202b in the configuration items 202 in the template information 200, as well as configuration item names and post-change configuration values, to be configured into the configuration information 210.

[0169] In step S16, the configuration information generation unit 103 stores the configuration information 210 generated in step S15 in the storage unit 20. (b) The example in which the existing configuration information 210 is to be edited

[0170] Fig. 26 is a flowchart for explaining a generation process performed by the screen generation device 1 when editing the existing configuration information 210. The flow in this example is executed each time an instruction to edit the existing configuration information 210 is received from the screen generation device.

[0171] Since in this case the processes in step S22, step S24 and step S25 are combined with the processes in step S12, step S14 and step S15 in Fig. 25 are identical, the corresponding explanations are omitted.

[0172] In step S21, which is triggered by pressing the EDIT button for the work screen displayed on the screen management screen 400 based on an input operation performed by the screen generator, the automatic configuration screen generation unit 102 receives an instruction to edit the configuration information 210.

[0173] In step S23, the automatic configuration screen generation unit 102 reads the configuration information 210 for the work screen selected in step S11 from the storage unit 20. The automatic configuration screen generation unit 102 reads the template information 200 from the storage unit 20, which is identified by the template ID configured in the read configuration information 210. Based on the template information 200 and the read configuration information 210, the automatic configuration screen generation unit 102 generates the configuration screen 450 to be displayed on the output device 40.

[0174] In step S26, the configuration information generation unit 103 stores the configuration information 210 generated in step S25 in the storage unit 20 to perform an update. (c) The example in which a work screen is to be displayed by selecting the configuration information 210

[0175] Fig. Fig. 27 is a flowchart for explaining a generation process performed by the screen generation device 1 when a work screen is to be displayed by selecting the configuration information 210. The flow in the present example is executed each time the screen user selects the configuration information 210 and a display command is received.

[0176] In step S31, which is triggered by pressing a DISPLAY key for the work screen displayed on the screen management screen 400 based on an input operation performed by the screen user, the automatic screen generation unit 104 receives an instruction to display the work screen.

[0177] In step S32, the automatic screen generation unit 104 reads the configuration information 210 of the selected work screen from the storage unit 20.

[0178] In step S33, the automatic screen generation unit 104 reads from the storage unit 20 the template information 200 corresponding to the template ID configured in the configuration information 210 read in step S32.

[0179] In step S34, the automatic screen generation unit 104 generates the work screen based on the template information 200 read in step S33 and the configuration information 210 read in step S32.

[0180] In step S35, the automatic screen generation unit 104 displays the work screen generated in step S34 on a display device (not shown).

[0181] As explained above, the screen generation system SYS according to one embodiment is capable of presenting the template generator with the screen including the most suitable configuration items corresponding to the method of using the template screen, and is also capable of enabling the screen generator who uses the template to generate (customize) the work screen to easily generate the screen suitable for each work station by configuring the template screen.

[0182] Starting from a single screen template, the screen generator can easily create multiple screens with different data displays, layouts, and / or behaviors. For example, even if the screen performs the same task, it is possible to easily create a working screen optimized for the needs of each user.

[0183] In addition, the screen generation system SYS is able to easily generate the screen on which the data visible to each user is limited or added, and is thus able to manage the screen displayable to each user from the multitude of generated screens.

[0184] In addition, since the generated screen has the ID, it is possible to easily realize the transition between the screens by specifying the ID as a configuration item at the link target.

[0185] One embodiment has been explained thus; however, the screen generating system SYS is not limited to the above-described embodiment and includes modifications, improvements, and the like within the scope of achieving the object. <Erstes Beispiel für eine Modifikation>

[0186] In one embodiment, the screen generating device 1 is a device other than the display device that displays the screen in connection with manufacturing; however, possible embodiments are not limited to this example. For example, the screen generating device 1 may include the display device (not shown). <Zweites Beispiel für eine Modifikation>

[0187] For example, in one embodiment, the automatic configuration screen generation unit 102 generates the configuration screen 450 in Japanese, while the configuration information generation unit 103 generates the configuration information 210 in Japanese, and the automatic screen generation unit 104 generates the Japanese language screen; however, possible embodiments are not limited to this example.

[0188] For example, the automatic configuration screen generation unit 102 may generate the configuration screen 450 that specifies a configuration for each of the various languages (e.g., Japanese, English, and Chinese, etc.), so that the configuration information generation unit 103 generates the configuration information 210 in each language based on the information configured on the configuration screen 450, and the screen generation unit 104 generates the screen corresponding to each language based on the configuration information 210.

[0189] It is possible to realize each of the functions included in the screen generation system SYS in one embodiment using hardware, software, or a combination thereof. In this case, "implemented by software" means that it is realized as a result of a computer reading and executing a program.

[0190] The program can be stored on various types of non-transitory computer-readable media for delivery to the computer. Examples of non-transitory computer-readable media include tangible storage media of various kinds. Examples of non-transitory computer-readable media include magnetic recording media (e.g., flexible disk, magnetic tape, hard disk drive), opto-magnetic recording media (e.g., opto-magnetic disk), CD-ROM (Read Only Memory), CD-R, CD-R / W, semiconductor memory (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), Flash ROM, RAM). Furthermore, the program can be delivered to the computer via various types of volatile computer-readable media. Examples of volatile computer-readable media include electrical signals, optical signals, and electromagnetic waves.The transient computer-readable medium may deliver the program to the computer via a wired communication path, such as cabling, optical fiber, etc., or via a wireless communication path.

[0191] In this case, the steps describing the program recorded on the recording medium include both the processes executed chronologically according to the sequential order and the processes executed in parallel or individually, although they are not necessarily executed chronologically.

[0192] The present disclosure has thus been explained in detail; however, the present disclosure is not limited to the individual embodiments described above. Various kinds of additions, replacements, changes, and partial deletions can be made to the embodiment without departing from the gist of the present disclosure or the scope of the present disclosure as defined in the claims and their equivalents. Furthermore, the embodiments can be practiced in combination. For example, in the embodiment described above, the order of operations and the order of methods are merely examples, and possible embodiments are not limited to these examples. The same applies to the use of numerical values or mathematical formulas in the descriptions of the above-mentioned embodiments.

[0193] With respect to the embodiments and modification examples described above, the following additions are disclosed. (Supplement 1)

[0194] A screen generation device (1) comprises: an automatic configuration screen generation unit (102) configured to generate a configuration screen (450) for configuring each of the configuration items defined in pre-prepared template information (200) for a screen; a configuration information generation unit (103) configured to generate configuration information based on information for each of the configuration items configured on the configuration screen (450); and an automatic screen generation unit (104) configured to generate a screen based on the template information (200) and the configuration information (210) generated by the configuration information generation unit (103). (Supplement 2)

[0195] The automatic configuration screen generation unit (102) generates the configuration screen (450) for editing the configuration information (210) generated by the configuration information generation unit (103), and the configuration information generation unit (103) generates the configuration information (210) based on the information edited on the configuration screen (450). (Supplement 3)

[0196] The configuration element (202) refers to at least one selected from: usage data, behaviors and manifestations. (Supplement 4)

[0197] The template information (200) includes the configuration item (202), a template screen (201) and a template behavior (203). (Supplement 5)

[0198] The screen generation device (1) according to Supplement 1 or 2 further comprises: a meta-information acquisition unit (101) configured to acquire one or both of usage data meta-information and device meta-information. The automatic configuration screen generation unit (102) generates the configuration screen (450) for configuring the configuration information (210) based on the meta-information acquired by the meta-information acquisition unit (101); and the configuration information generation unit (103) generates the configuration information (210) based on the information configured on the configuration screen (450). (Supplement 6)

[0199] The screen is a screen related to manufacturing. (Supplement 7)

[0200] The screen generating device (1) according to Supplement 1 or 2 further comprises a template generating unit (100) configured to generate the template information (200). (Supplement 8)

[0201] The screen generation device (1) according to Supplement 1 or 2 further comprises a configuration information management unit (105) configured to manage the generated configuration information (210). (Supplement 9)

[0202] The screen generating device (1) according to Supplement 8 further comprises a user information management unit (106) configured to manage user information (220). (Supplement 10)

[0203] Based on the user information (220), the configuration information management unit (105) controls an operation performed by each user on the configuration information (210). (Supplement 11)

[0204] The automatic configuration screen generation unit (102) generates the configuration screen (450) based on the user information (220) and either the template information (200) or the configuration information (210); and the configuration information generation unit (103) generates the configuration information (210) based on the information edited on the configuration screen (450). (Supplement 12)

[0205] The automatic screen generation unit (104) generates the screen based on the user information (220), the template information (200) and the configuration information (210). (Supplement 13)

[0206] The automatic configuration screen generation unit (102) generates the configuration screen (450) on which the configuration item is configured for each of the languages; the configuration information generation unit (103) generates the configuration information (210) for each of the languages based on the information configured on the configuration screen (450); and the automatic screen generation unit (104) generates the display screen corresponding to the languages. (Supplement 14)

[0207] A screen generation method is a screen generation method that causes a computer to function as a screen generation device (1), and includes: a selection step of selecting a piece of pre-prepared template information (200) for a screen; an automatic configuration screen generation step of generating a configuration screen (450) for configuring each of the configuration items defined in the selected template information (200); a configuration information generation step of generating configuration information (210) based on information for each of the configuration items configured on the configuration screen (450); and an automatic screen generation step of generating the screen based on the selected template information (200) and the generated configuration information (210). Explanation of reference symbols 1 screen generating device 10 Control unit 100 template generation unit 101 Metainformation acquisition unit 102 automatic configuration screen generation unit 103 Configuration information generation unit 104 automatic screen generation unit 105 Configuration Information Management Unit 106 User Information Management Unit 20 storage units 200-1 to 200-m template information 201 Template screen 202 Configuration element 202a Manifestations / Behaviors 202b Usage Data 203 Template behavior 210-1 to 210-n configuration information 220 User information 2 Data source 3 devices SYS screen creation system QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] JP 2000-066709

[0004] JP 2010-152882

[0004]

Claims

[1] A screen generating device comprising: an automatic configuration screen generation unit configured to generate a configuration screen to configure each of the configuration items defined in pre-created template information for a screen; a configuration information generation unit configured to generate configuration information based on information for each of the configuration items configured on the configuration screen; and an automatic screen generation unit configured to generate the screen based on the template information and the configuration information generated by the configuration information generation unit. [2] The screen generating device according to claim 1, wherein the automatic configuration screen generation unit generates the configuration screen for editing the configuration information generated by the configuration information generation unit, and the configuration information generation unit generates the configuration information based on the information edited on the configuration screen. [3] The screen generating device according to claim 1 or 2, wherein the configuration item relates to at least one selected from usage data, a behavior, and an appearance. [4] The screen generating apparatus according to claim 1 or 2, wherein the template information includes the configuration item, a template screen, and a template behavior. [5] The screen generating device according to claim 1 or 2, further comprising: a meta-information acquisition unit configured to acquire one or both of usage data meta-information and device meta-information, wherein the automatic configuration screen generation unit generates the configuration screen for configuring the configuration information based on the meta information acquired by the meta information acquisition unit, and the configuration information generation unit generates the configuration information based on the information configured on the configuration screen. [6] The screen generating apparatus according to claim 1 or 2, wherein the screen is a manufacturing-related screen. [7] The screen generating device according to claim 1 or 2, further comprising a template generating unit configured to generate the template information. [8] The screen generating device according to claim 1 or 2, further comprising a configuration information managing unit configured to manage the generated configuration information. [9] The screen generating apparatus according to claim 8, further comprising a user information management unit configured to manage user information. [10] The screen generating apparatus according to claim 9, wherein the configuration information management unit controls an operation performed by each user on the configuration information based on the user information. [11] The screen generating device according to claim 9, wherein the automatic configuration screen generation unit generates the configuration screen based on the user information and either the template information or the configuration information, and the configuration information generation unit generates the configuration information based on the information edited on the configuration screen. [12] The screen generating device according to claim 9, wherein the automatic screen generating unit generates the screen based on the user information, the template information, and the configuration information. [13] The screen generating device according to claim 1 or 2, wherein the automatic configuration screen generation unit generates the configuration screen on which the configuration items for each of the languages are configured, the configuration information generation unit generates the configuration information for each of the languages based on the information configured on the configuration screen, and the automatic screen generation unit generates the screen corresponding to the languages. [14] A screen generation method that causes a computer to act as a screen generation device, the screen generation method comprising: a selection step for selecting pre-created template information for a screen; an automatic configuration screen generation step for generating a configuration screen for configuring each of the configuration items defined in the selected template information; a configuration information generation step for generating configuration information based on information for each of the configuration items configured on the configuration screen; and an automatic screen generation step to generate the screen based on the selected template information and the generated configuration information.

Images