Screen creation system and screen creation process

Abstract

The present invention makes it possible for a mask creator to have a created mask that can be applied to many other business screens, and makes it possible for a screen user who creates (adapts) a business screen using the mask to simplify the setup work required for each project to which the mask is applied.This screen creation system comprises: a setup information creation unit for creating, based on a setup entry and a setup condition predefined for the entire selected screen mask and for each of the screen mask's components, setup information for each setup entry defined for the entire screen mask or the screen mask's component; and a screen creation unit for creating a screen based on the screen mask and the setup information generated by the setup information creation unit.

Description

Technical area

[0001] The present invention relates to a screen creation system and a screen creation method. State of the art

[0002] Previously, a technique was known in which a user creates a screen for a task by customizing a previously created screen mask based on this screen mask (e.g. a BI tool (Business Intelligence), SCADA (Supervisory Control And Data Acquisition), etc.).

[0003] Furthermore, it is conventionally known that, for a display item and display size selected by an operator, a plurality of screen divisions corresponding to the display size are displayed on a screen based on display information in a screen division storage area. When the operator designates an arbitrary screen division among the screen divisions displayed on the screen, the display size and screen division position information for the designated screen division are stored in a user-defined screen storage area, thereby allowing the configuration of the display screen to be freely adjusted as intended by the operator. See, for example, Patent Document 1. Citation listPatent document

[0004] Patent Document 1: Unexamined Japanese Patent Application Publication No. 2010-152992. Disclosure of the invention Problems to be solved by the invention

[0005] However, there is a problem that in order to apply the invention described in Patent Document 1 to different sites, such as manufacturing facilities, the mask needs to be customized or installed depending on the different facility configurations of manufacturing facilities and functions and the like that the facilities have, and the different display items and layout data of the task screens at each site and by each user, which requires time and effort.

[0006] Accordingly, it is desirable for a mask creator to allow a created mask to be applied to multiple task screens, and for a screen user who creates (customizes) a task screen using the mask to be able to simplify the setup creation work required for each task screen to which the mask is applied. Means of solving the tasks

[0007] One aspect of a screen creation system in the present disclosure includes: a setup information creation unit configured to create, based on a setup entry and a setup condition predefined for a selected screen as a whole or each of the constituent elements of the screen, setup information with respect to each setup entry defined for the screen as a whole or the constituent elements of the screen; and a screen creation unit configured to create a screen based on the screen and the setup information created by the setup information creation unit.

[0008] One aspect of a screen creation method in the present disclosure includes: a selection step of selecting a screen; a setup information creation step of creating, based on a setup entry and a setup condition predefined for the selected screen as a whole or for each of the constituent elements of the screen, setup information with respect to each setup entry defined for the entire screen or the constituent elements of the screen; and a screen creation step of creating a screen based on the screen and the created setup information. Effects of the invention

[0009] According to one aspect, a mask creator can apply a created mask to multiple task screens, and a screen user who creates (customizes) a task screen using the mask can simplify the setup creation work required for each task screen to which the mask is applied. Brief description of the drawings Fig. 1 is a functional block diagram of a screen creation system according to one embodiment; Fig. 2A is a figure showing an example of a setup master; Fig. 2B is a figure showing an example of a facility status table; Fig. 3 is a figure showing an example of a screen mask; Fig. 4 is a figure showing an example of setup entries and setup conditions; Fig. 5 is a figure showing an example of a screen mask; Fig. 6 is a figure showing an example of setup entries; Fig. 7 is a figure showing an example of screen creation of a screen mask; Fig. Figure 8 is a figure showing an example of meta-information about a data source; Fig. 9 is a figure showing an example of meta-information about a facility; and Fig. 10 is a flowchart illustrating a screen creation process of a screen creation device 1. Preferred mode for carrying out the invention

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

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

[0012] As in Fig. 1, a screen creation system SYS comprises a screen creation device 1, a data source 2 and a device 3.

[0013] The screen creation device 1, the data source 2, and the device 3 may be connected to each other via a network (not shown), such as a LAN (Local Area Network) or the Internet. In this case, the screen creation device 1, the data source 2, and the device 3 each include a communication unit (not shown) for communicating with each other via such a connection. Note that the screen creation device 1, the data source 2, and the device 3 may be connected to each other via a wired or wireless connection interface (not shown).

[0014] In Fig. 1, the screen creation device 1 is connected to the single data source 2 and the single device 3, but may also be connected to two or more data sources 2 and two or more devices 3. <Datenquelle 2>

[0015] The data source 2 may be, for example, a data server, a cloud server, etc., and stores a facility master that displays information related to the facility 3 located at each location, such as a manufacturing plant, and data such as a facility status table.

[0016] Fig. Figure 2A is a figure showing an example of the setup master. Fig. Figure 2B is a figure showing an example of a setup status.

[0017] As in Fig. As shown in Figure 2A, the facility master contains storage areas such as "Facility Name," "Model Number," and "Person in Charge." For example, the "Facility Name" storage area in the facility master stores facility names such as "Facility 1" and "Facility 2." For example, the "Model Number" storage area in the facility master stores model numbers such as "Model Number 1" and "Model Number 2." For example, the "Person in Charge" storage area in the facility master stores "Person in Charge A" and "Person in Charge B," which respectively designate responsible persons who manage the facilities with "Facility Name."

[0018] As in Fig. As shown in Figure 2B, the facility status table includes storage areas for “Facility Name,” “Status Start Time,” “Facility Status,” and “Program.”

[0019] For example, the "Facility Name" storage area in the Facility Status table stores the names of Facility 3, such as "Facility 1" and "Facility 2." The "Status Start Time" storage area in the Facility Status table stores, for example, a start date and time at which the status of each Facility 3 reached its current status.

[0020] The “Facility Status” storage area in the Facility Status Table stores, for example, “In Operation,” “Stopped,” and the like, which indicates the current status of each Facility 3 with a corresponding “Facility Name.”

[0021] The memory area for "Program" in the device status table stores, for example, "Program 1", "Program 2", etc., which indicates programs that are currently being executed or were last executed with respect to the respective devices 3 with a corresponding "device name".

[0022] Note that Data Source 2 can also store production performance information (a workpiece ID, a facility name, a processing step name, a start time, a finish time, etc.). <Einrichtung 3>

[0023] The devices 3 are a numerical control device, a robot control device, a machine tool, a robot, and the like, which are arranged at a location, e.g., a manufacturing plant. Each device 3 stores data, such as an executable function list indicating executable functions. The device 3 outputs the data, such as the executable function list, along with the device status indicating the current status, and the like, to the screen creation device 1 and the data source 2. <Bildschirm-Erstellungsvorrichtung 1>

[0024] The screen creation device 1 is, for example, a computer or the like, and is mutually connected to a display device (not shown), for example, a computer, which displays a screen related to the production at the facility 3 via a network (not shown), for example, the LAN and the Internet.

[0025] Examples of screens related to manufacturing at the facility include, but are not limited to: a manufacturing equipment monitoring screen, a facility status confirmation screen, an OEE (Overall Equipment Effectiveness) confirmation screen, a screen for recording the start and completion of a processing step, etc., as screens related to production; a screen for recording maintenance performance, a screen for recording a maintenance plan, a screen for referencing a maintenance history, etc., as screens related to facility maintenance; and a screen for recording a measurement result of a product, a screen for capturing the trend of the measurement result of the product, etc., as screens related to product quality. They are applicable to any screens related to manufacturing equipment.

[0026] Thus, the screen created in accordance with the device by the screen creation device 1 is applied to the display device (not shown) as described later. The display device (not shown) displays the screen created by the screen creation device 1 on a display unit (not shown) such as a liquid crystal display, thereby displaying the screen related to the production at the device (not shown) such as a numerical control device. Note that the screen creation device 1 may be directly reciprocally connected to the display device (not shown) via the connection interface (not shown).

[0027] As described later, the screen creating device 1 is a device different from the display device (not shown), but may include the display device (not shown).

[0028] As in Fig. As shown in Figure 1, the screen creation device 1 includes: a control unit 10; a storage unit 20; an input device 30, such as a keyboard, a mouse, or a touch panel; and an output device 40, such as a liquid crystal display. The control unit 10 includes a screen mask creation unit 100, a meta-information acquisition unit 101, a setup information creation unit 102, and a screen creation unit 103. <Speichereinheit 20>

[0029] The storage unit 20 may be an SSD (Solid State Drive), an HDD (Hard Disk Drive), etc. The storage unit 20 stores n screens 200-1 to 200-n (n is an integer equal to or greater than 1) associated with an operating system, an application program, and the like executed by the control unit 10.

[0030] If the screen masks 200-1 to 200-n do not need to be individually distinguished from one another, they are also referred to collectively as “screen mask 200” below.

[0031] The screen mask 200 is, for example, mask data of a screen created in advance based on an operation of a screen mask creator by the screen mask creation unit 100 described later. As shown in Fig. 1, the screen mask 200 contains a setup entry 201 and a setup condition 202 that are predefined by the screen mask creator.

[0032] Fig. 3 is a figure showing an example of the screen mask 200. Fig. 4 is a figure showing an example of the setup entry 201 and the setup condition 202.

[0033] As in Fig. 3, for example, three inventory elements 230a to 230c are set on the screen mask 200.

[0034] As in Fig. As shown in Figure 4, setup entries for the respective inventory items 230a to 230c are set in setup entry 201. For example, for inventory item 230a, a screen is set to display a list of devices and a selectable device selection pull-down. For inventory item 230b, a screen is set to display the model number and device status of the device selected via the device selection pull-down for inventory item 230a. For inventory item 230c, a screen is set to display an execute button.

[0035] In the setup condition 202, the conditions for the functions set for the respective items in the setup entry 201 are set based on meta information about the data of the data source 2 and the data of the facility 3 obtained from the meta information acquisition unit 101 described later. For example, in order to display the list of facilities on the facility selection pull-down for the inventory item 230a, in the meta information about the data of the data source 2 obtained from the meta information acquisition unit 101 described later, "Facility Master" is set as a table name (file name), "Facility Name" is set as a column name of data in "Facility Master", and "None" is set as a refinement condition for the data in the setup condition 202. It should be noted that in the setup condition 202, Fig. 4 an exact match condition is also specified for the table label “Facility Master” and the column label “Facility Name”.

[0036] Inventory item 230b contains two setup entries (the model number and the setup status).

[0037] Regarding the model number, in order to display the model number of the facility in the facility selection pull-down for the inventory item 230b, in the meta information of the data of the data source 2 obtained from the meta information acquisition unit 101 described later, in the setup condition 202, “Facility Master” is set as the table name (file name), “Model Number” is set as the column name of the data in “Facility Master”, and “None” is set as the refinement condition for the data.

[0038] Regarding the facility status, in order to display the facility status of the facility in the facility selection pull-down in the inventory item 230b, in the meta information of the data of the data source 2 obtained from the meta information acquisition unit 101 described later, in the setup condition 202, "Facility Status" is set as the table name (file name), and "Facility Status" is set as the column name of the data for "Facility Status," and "Facility Name" and "Latest Value" are set as the refinement conditions for the data. It should be noted that in the setup condition 202 (Facility Status) for the inventory item 230b in Fig. 4 an exact match condition is also specified for the table label “Facility Status” and the column label “Facility Status”.

[0039] In order for the execution button displayed in the inventory element 230c to function as a backup, "Backup" is specified as the function name in the meta information of the data of the executable function list stored in the device 3 in the setup condition 202. It should be noted that in the setup condition 202 (function of the execution button) of the inventory element 230c in Fig. 4 also specifies a condition for the exact match of the function name “Backup”.

[0040] As in Fig. 5, the screen mask 200 may contain an inventory element 230d, which is a symbol for the device. In this case, as shown in Fig. 6, the setup entry 201 for the inventory item 230d contains additional information. That is, the setup entry 201 for the inventory item 230d contains "screen refresh interval," "icon color," and "setup status (status)." The setup entry 201 contains entries in the second row and thereafter, surrounded by dashed lines, "target (entity / asset item)," "classification," "acquisition condition," "script input availability," "default value," "input type," and "description" as additional information for the setup entries "screen refresh interval," "icon color," and "setup status (status)." This additional information is a type of setup condition 202 for the setup entry.

[0041] The storage area for "Target (Entity / Inventory Element)" in the additional information stores setting values ​​that indicate whether the entire screen mask is considered the target or a specific inventory element is considered the target for the respective setup entries contained in setup entry 201 ("Screen Refresh Interval", "Icon Color", "Setup Status (Status)"). The additional information in Fig. 6 save setting values ​​for “Full Screen”, “Setup Icon” and “Setup Icon” for the respective setup entries “Screen Refresh Interval”, “Icon Color” and “Setup Status (Status)”.

[0042] The storage area for "Classification" in the additional information stores classifications of the respective setup entries. The additional information in Fig. 6 stores classifications for "Behavior," "Appearance," and "Data" for the respective setup items "Screen Refresh Interval," "Icon Color," and "Setup Status (Status)." The storage area for "Acquisition Condition" in the additional information stores settings (multiple names allowed) as data acquisition conditions when the "Classification" is "Data." The additional information in Fig. 6 save the acquisition conditions "Setup" and "Equal" for the setup entry "Setup Status (Status)" with the "Classification" of "Data." Note that the "Acquisition Condition" for "Screen Refresh Interval" and "Icon Color" is empty "-" because "Classification" specifies "Behavior" and "Appearance."

[0043] The "Script Input Availability" storage area in the additional information stores as a setting value whether a script can be set (true) or not (false). The additional information in Fig. 6 save “false”, “true” and “- (empty)” for the respective setup entries “screen refresh interval”, “icon color” and “setup status (status)”.

[0044] The memory area for "Default Value" in the additional information stores a value as the initial value for the respective setup entry. The additional information in Fig. 6 stores "10", "{{$.status == 1 ? 'green' : 'red'}}", and "- (empty)" for the respective setup entries "screen refresh interval", "icon color", and "facility status (status)". Note that "10" indicates that the screen refresh interval is 10 seconds. For example, "{{$.status == 1 ? 'green' : 'red'}}" is in JavaScript (R). In a case where the variable "status" set in the data is "1", the color of the facility icon is set to "green". In the other cases, the color of the facility icon is set to "red".

[0045] The storage area for "Data Type" in the additional information stores the type of data in the setup value. The additional information in Fig. 6 save “Numerical Value”, “Color” and “Numerical Value” for the respective setup entries “Screen Refresh Interval”, “Icon Color” and “Setup Status (Status)”.

[0046] The "Description" storage area in the additional information stores a description to convey the meaning of the setup entry to the mask creator and the screen user. The additional information in Fig. 6 save “Specify screen refresh interval in seconds”, “Specify icon color” and “-(empty)” for the respective setup entries “Screen refresh interval”, “Icon color” and “Setup status (status)”. <Steuereinheit 10>

[0047] The control unit 10 includes a CPU, a ROM, a RAM, a CMOS memory, and the like, which are configured to communicate with each other via a bus and are generally known to those skilled in the art. The CPU is a processor that controls the screen creation device 1 as a whole. The CPU reads system programs and application programs stored in the ROM via the bus and controls the screen creation device 1 as a whole according to the system programs and application programs. Accordingly, the control unit 10, as shown in Fig. 1, is configured to perform the functions of the screen mask creation unit 100, the meta-information acquisition unit 101, the setup information creation unit 102, and the screen creation unit 103. The RAM stores various data items, such as temporary calculation data and display data. The CMOS memory is backed up by a battery (not shown) and is thus configured as a non-volatile memory whose storage state is retained even when the power source of the screen creation device 1 is turned off.

[0048] Note that in the present embodiment, the example of the configuration in which the screen creation device 1 includes the screen mask creation unit is described. However, it is not limited to this. The screen mask creation unit may be configured as a mask creation device (not shown), which is a device different from the screen creation device 1. That is, the mask creator can create a screen mask via the mask creation device (not shown) and make the created screen mask available to a large number of users.

[0049] Before describing the functions of the screen mask creating unit 100, the meta information acquiring unit 101, the setup information creating unit 102 and the screen creating unit 103 in detail, the brief operation of each function will be described here.

[0050] The screen mask creation unit 100 creates the screen mask 200 that conforms to the function of the facility and site, such as a manufacturing facility, based on an input operation by the mask creator via the input tool 30, and stores the created screen mask 200 in the storage unit 20. The meta information acquisition unit 101 acquires the meta information about the data stored in the data source 2, the facility 3, and the like from the data source 2, the facility 3, and the like, and outputs the acquired meta information to the setup information creation unit 102.

[0051] The setup information creation unit 102 reads from the storage unit 20 the screen template 200 selected by the screen user who creates (customizes) the task screen using the screen template, and generates the setup information with respect to each setup entry for the entire screen template 200 or for each of the constituent elements 230a to 230c of the screen template based on the setup entry 201 and the setup condition 202 predefined for the read screen template 200 and the meta information input by the meta information acquisition unit 101. The setup information creation unit 102 outputs the created setup information to the screen creation unit 103.

[0052] The screen creation unit 103 creates the facility manufacturing-related screen based on the screen template 200 and the setup information created by the setup information creation unit 102, and uses the created screen as a facility manufacturing-related screen on the unillustrated display device. <Bildschirmmasken-Erstellungseinheit 100>

[0053] The screen mask creation unit 100 creates the screen mask 200 that conforms to the function of the facility and site, such as a manufacturing plant, based on an input operation by the mask creator via the input tool 30, and stores the created screen mask 200 in the storage unit 20. Specifically, for example, after accepting an instruction to create the screen mask 200 through an input operation by the mask creator, the screen mask creation unit 100 displays a creation screen 300 for the screen mask 200 on the output tool 40.

[0054] Fig. 7 is a figure showing an example of the creation screen 300 for the screen mask 200.

[0055] As in Fig. As shown in Figure 7, the creation screen 300 includes a screen setup area 310 and an inventory item list 320. Note that the inventory item list 320 includes, as inventory items, buttons (pull-down and run buttons, etc.), a table, a setup icon, and text information, for example. For each of the inventory items, a default setup entry 201 of the corresponding inventory item and its additional information, as well as the setup condition 202, can be set.

[0056] As in Fig. 7, the screen mask creation unit 100, for example, arranges and determines the facility icon at a desired position by dragging and dropping the facility icon through the input operation of the mask creator. Note that after determining the facility icon and its arrangement position, the screen mask creation unit 100 can automatically generate a source code for the screen mask 200 based on an input operation by the mask creator and based on the type and arrangement position of the constituent item, and edit the source code as needed (e.g., add logic). The screen mask creation unit 100 can create or correct the setup entry 201 for the constituent item and its additional information (e.g.,adjust the setup entry), create or correct the setup condition 202, and the like, as required, based on an input operation by the screen creator. The screen mask creation unit 100 may create a new screen mask 200 based on an existing screen mask 200. The screen mask creation unit 100 may internally include a debug function for the screen mask 200.

[0057] The screen mask creation unit 100 stores in the storage unit 20 as a screen mask 200 data including the setup entry 201 and the additional information as well as the setup condition 202, which are set in the screen mask setup area 310. <Meta-Informationen-Erfassungseinheit 101>

[0058] The meta information acquisition unit 101 acquires the meta information about 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 setup information creation unit 102.

[0059] Specifically, the meta-information acquisition unit 101 acquires, for example, metadata related to the facility at each site, such as a manufacturing facility, stored in the data source 2 (facility name, model number / name, person in charge, status start time information, facility status information, program name, etc.), as well as metadata related to the facility stored in the facility 3 (facility name, function name, etc.), which are then registered in advance. Note that in the facility 3, the list of executable functions of the facility 3 can be registered in advance, and connection information about the facility 3 to be set at each site (e.g., an IP address, etc.) can be registered. Database connection destination information (e.g., an IP address, a password, etc.) can be registered.) can be registered in advance, and the meta-information acquiring unit 101 can perform a query and acquire the meta-information.

[0060] The meta-information acquisition unit 101 may use a meta-information acquisition function included in an IoT (Internet of Things) platform and belonging to the device or software (an interface for calling the function (RPC: Remote Procedure Call), etc.) to communicate with the device. Preferably, in this case, the IoT platform exposes a document to the user indicating which meta-information (an interface (RPC) for calling the function) the device or software (converter) has for communicating with the device. Accordingly, the form creator can acquire the function included in the device in advance and then create the setup condition 202 for the screen form 200. The IoT platform defines common meta-information (interface) about the function, which is general regardless of the device (e.g.,File transfer, file acquisition, file list acquisition, file deletion, variable setting, variable acquisition, etc.). When the device that supports the common function or software that communicates with the device is used, the mask creator can create the setup condition 202 for the screen mask 200 without considering the device.

[0061] As in Fig. 8, for example, in a case where the data is a database, the meta information acquiring unit 101 acquires the list of tables and the list of column names and types of each table as meta information about the data from the data source 2.

[0062] Fig. Figure 8 is a figure showing an example of the meta information for data source 2. As in Fig. As shown in Figure 8, the meta information includes storage areas for "table name," "column label," and "type." For example, the storage area for "table name" in the meta information stores a table (data) such as "facility master" and "facility status." For example, the storage area for "column label" in the meta information stores column labels such as "facility name," "model number," "responsible person," "facility name," "facility status," and "status start time." For example, the storage area for "type" in the meta information stores data types such as "string," "date and time," and "numeric value" related to each column label "column label."

[0063] Note that in a case where the data is a CSV file or the like, the meta information acquiring unit 101 may acquire a list of file names or the header names of the respective files as meta information.

[0064] As in Fig. 9, in the case of meta-information about the device 3, the meta-information acquisition unit 101 may acquire a list of the functions (interfaces) and arguments executable in the device.

[0065] Fig. Figure 9 is a figure showing an example of the meta information about the facility 3. As in Fig. As shown in Figure 9, the facility meta-information includes three memory areas for “Facility”, “Executable Function” and “Argument”.

[0066] It is understood that the storage area for “facility” in the meta information about the facility 3 acquired by the meta information acquisition unit 101 stores, for example, facilities such as “facility 1” and “facility 2”.

[0067] It is understood that the storage area for “function name” in the acquired meta information about the facility 3 stores functions such as “backup”, “processing start” and “door opening and closing”.

[0068] It is understood that the storage area for “Argument” in the acquired meta information about the device 3 stores, for example, arguments such as “Start Time” with respect to each function of “Executable Function”.

[0069] Note that in the case of the meta information about the device 3, the meta information acquiring unit 101 can acquire the type of data, the file name, the type, and the like that can be acquired from the device 3. <Setup-Informationen-Erstellungseinheit 102>

[0070] For example, the setup information creation unit 102 reads from the storage unit 20 the screen template 200 selected by the screen user who creates (customizes) the task screen using the screen template, and generates the setup information with respect to each setup entry for the entire screen template 200 or for each of the constituent elements 230a to 230c of the screen template based on the setup entry 201 and the setup condition 202 predefined for the read screen template 200 and the meta information input from the meta information acquisition unit 101. The setup information creation unit 102 outputs the created setup information to the screen creation unit 103.

[0071] Specifically, the setup information creation unit 102 acquires, for example, candidates for corresponding settings by comparing the meta information acquired by the meta information acquisition unit 101 with the setup condition 202 for each setup entry 201. For example, the setup information creation unit 102 searches the storage area for “table name” in the meta information in Fig. 8 and retrieves the table label that exactly matches the table label “Facility Master” in the setup condition 202 for “Facility Selection Pull-Down” for the setup entry 201 in Fig. 4. Since “Facility Master” is defined in the meta information in Fig. 8, the setup information creation unit 102 then searches the storage area for “column label” in the meta information in Fig. 8 and retrieves the column label that exactly matches the column label of “Facility Name” in the setup condition 202 for “Facility Selection Pull-Down” for the setup entry 201 in Fig. 4. Since “Facility Name” in the meta information in Fig. 8, the setup information creation unit 102 therefore sets information (e.g., a query for the data source 2, a file path, etc.) for acquiring data from the setup master in Fig. 2A as setup information (candidates) for the setup entry in the facility selection pull-down for the inventory element 230a.

[0072] The setup information creation unit 102 searches the storage area for “table name” in the meta information in Fig. 8 and retrieves the table label that exactly matches the table label “Facility Master” in setup condition 202 for “Model Number” for setup entry 201 in Fig. 4. Since “Facility Master” is defined in the meta information in Fig. 7, the setup information creation unit 102 then searches the storage area for “column label” in the meta information in Fig. 8 and retrieves the column label that exactly matches the column label of “Model Number” in the setup condition 202 for “Model Number” for the setup entry 201 in Fig. 4. Since “model number” in the meta information in Fig. 8, the setup information creation unit 102 creates information (e.g., a query for the data source 2, a file path, etc.) for acquiring data from the setup master in Fig. 2A as setup information (candidates) about the setup entry in the model number for the inventory item 230b.

[0073] The setup information creation unit 102 searches the storage area for “table name” in the meta information in Fig. 8 and retrieves the table label that exactly matches the table label of “Facility Status” in the setup condition 202 for “Facility Status” for the setup entry 201 in Fig. 4. Since “Facility status” in the meta information in Fig. 8, the setup information creation unit 102 then searches the storage area for “column label” in the meta information in Fig. 8 and retrieves the column label that exactly matches the column label of “Facility Status” in the setup condition 202 for “Facility Status” for the setup entry 201 in Fig. 4. Since “Facility status” in the meta information in Fig. 8, the setup information creation unit 102 creates information (e.g., a query for the data source 2, a file path, etc.) for acquiring data from the setup status in Fig. 2B as setup information (candidates) for the setup entry in the setup status for the inventory item 230b.

[0074] The setup information creating unit 102 searches the meta information about the setup in Fig. 9 and retrieves the function name that exactly matches the function name “Backup” in the setup condition 202 for “Run Button Function” in the setup entry 201 in Fig. 4. Since “Backup” is included in the meta information about the facility in Fig. 9, the setup information creation unit 102 creates the meta information about the setup in Fig. 9 (e.g., the table, column label, file name, etc.) as the setup information (candidates) via the setup entry of the execution button of the inventory item 230c.

[0075] The setup information creation unit 102 then outputs the setup information created for each setup entry for the entire screen 200 or for each of the constituent elements 230a to 230c of the screen 200 to the screen creation unit 103.

[0076] Note that the setup information creation unit 102 compares the meta-information obtained from the meta-information acquisition unit 101 with the setup condition 202 for each setup entry 201 and determines candidates based on the exact match of the text. However, this is not limited. For example, the setup information creation unit 102 may determine candidates based on a partial match between the meta-information acquired by the meta-information acquisition unit 101 and the setup condition 202 for each setup entry 201.

[0077] Alternatively, the setup information generation unit 102 may calculate the textual similarity between the meta-information acquired by the meta-information acquisition unit 101 and the setup condition 202 for each setup entry 201 using a well-known method and output candidates in descending order of similarity or in an order of similarity. The setup information generation unit 102 may then, for example, display a result output of candidates on the output tool 40. If the result output is undesirable for the screen user who creates (customizes) a task screen using the screen template, the setup information generation unit 102 may display a list of candidates on the output tool 40 and output the candidates desired by the screen user.

[0078] In order to calculate the data content similarity between the meta information acquired by the meta information acquiring unit 101 and the setup condition 202 for each setup entry 201 with respect to each of the setup conditions 202, such as the table label and the column label, the setup information creating unit 102 may learn the features of the data with respect to each setup condition 202 in advance and thus calculate the similarity.

[0079] The setup information creation unit 102 compares the meta-information acquired by the meta-information acquisition unit 101 with the setup condition 202 for each setup item 201, and outputs the setting as setup information to the screen creation unit 103 described later when the number of candidates for the corresponding setting is one. On the other hand, when the number of candidates of the corresponding setting is two or more, the setup information creation unit 102 may output a notification indicating that the number of candidates is two or more and allow the screen user who is creating (customizing) the task screen to make a selection using the screen mask. For example, the setup information creation unit 102 may display a screen for selecting multiple candidates on the output instrument 40, thus allowing the screen user to make a selection.

[0080] When the number of setting candidates is zero, the setup information creation unit 102 may not automatically generate setup information and output information to the screen creation unit 103 described later. In this case, the setup information creation unit 102 may, for example, display a screen on the output device 40 to allow the screen user who generates (customizes) the task screen using the screen template to configure the setting, create setup information based on the manual setting by the screen user, and output the information to the screen creation unit 103. <Bildschirm-Erstellungseinheit 103>

[0081] The screen creation unit 103 creates a screen related to the facility production based on the screen template 200 and the setup information created by the setup information creation unit 102. The screen creation unit 103 can apply the created screen to the unillustrated display device as the screen related to the facility production. For example, the screen creation device 103 can be connected to a unillustrated task system and provide the created screen to the unillustrated task system. <Bildschirm-Erstellungsprozess der Bildschirm-Erstellungsvorrichtung 1>

[0082] Next, Fig. 10 the flow of a screen creation process of the screen creation device 1 is described.

[0083] Fig.10 is a flowchart illustrating the screen creation process of the screen creation device 1. The process described here is repeatedly executed each time the screen user selects the screen mask 200.

[0084] In step S11, the screen creation device 1 (control unit 10) accepts the selection of the screen mask 200 by the screen user via the input instrument 30.

[0085] In step S12, the screen creation device 1 (meta information acquisition unit 101) acquires the meta information about the data of the data source 2 and the data of the device 3, etc.

[0086] In step S13, the screen creating device 1 (setup information creating unit 102) creates the setup information with respect to each setup entry for the entire screen 200 or for each of the constituent elements 230a to 230c of the screen 200, based on the setup entry 201 and the setup condition 202 predefined for the screen 200 selected in step S11.

[0087] In step S14, the screen creating device 1 (screen creating unit 103) creates the screen based on the screen mask 200 selected in step S11 and the setup information created in step S13.

[0088] As described above, according to one embodiment, the screen creation system SYS includes the screen templates 200-1 to 200-n, including the predefined setup entry 201 and the setup condition 202, and acquires the meta-information about the data of the data source 2 and the data of the device 3 when the screen template 200 is selected by the screen user. The screen creation system SYS creates the setup information related to each setup entry for the entire screen template 200 or for each of the constituent elements 230a to 230c of the screen template based on the setup entry 201 and the setup condition 202 for the selected screen template 200 and on the acquired meta-information, and generates the screen based on the generated setup information and the selected screen template 200.Accordingly, the screen creation system SYS allows the screen creator to apply the created mask to multiple task screens, and enables the screen user who creates (customizes) the task screen using the mask to simplify the required setup creation work (e.g., the setup configuration at each location (manufacturing plant or the like), the function that each setup has, the difference in data name at each location (difference in data type), etc.) with respect to each task screen to which the mask is applied.

[0089] Although an embodiment has been described above, the screen creation system SYS is not limited to the above-described embodiment and includes modifications and improvements within a range in which the subject matter can be achieved. <Example of change>

[0090] In one embodiment, the screen creation device 1 is assumed to be a device other than the display device that displays a screen related to manufacturing in each of the devices (not shown), such as the numerical control device, a robot control device, a machine tool, and a robot, which are arranged at a site such as a manufacturing plant and are not shown. However, this is not limited to this. The screen creation device 1 may include, for example, the display device (not shown).

[0091] It should be noted that each function of the screen creation system SYS according to an embodiment can be achieved through hardware, software, or a combination thereof. Achieved through software here means achieved through a computer reading and executing a program.

[0092] The program can be stored and delivered to a computer using various types of non-transitory computer-readable media. Non-transitory computer-readable media includes various types of tangible storage media. Examples of non-transitory computer-readable media are magnetic recording media (e.g., a flexible disk, magnetic tape, and a hard disk drive), magneto-optical recording media (e.g., a magneto-optical disk), a CD-ROM (Read Only Memory), a CD-R, a CD-R / W, and semiconductor memories (e.g., a Mask ROM, a PROM (Programmable ROM), an EPROM (Erasable PROM), a Flash ROM, and a RAM). The program can be delivered to a computer through various types of transient computer-readable media. Examples of transient computer-readable media include electrical signals, optical signals, and electromagnetic waves.The transitory computer-readable media may deliver the program to the computer via a wired communication path, such as an electrical cable and an optical fiber, or a wireless communication path.

[0093] Steps for describing the program to be recorded on a recording medium include not only processes that are executed in time sequence according to the respective order, but also processes that are executed in parallel or individually and not necessarily in time sequence.

[0094] In other words, the screen creation system and the screen creation method in the present disclosure can be implemented as various types and various modes of embodiments having the following configurations.

[0095] (1) A screen creation system SYS in the present disclosure includes: a setup information creation unit 102 configured to create, based on a setup entry 201 and a setup condition 202 predefined for a screen 200 as a whole or each of the constituent elements 230a to 230c of the screen 200, setup information related to each setup entry 201 defined for the screen 200 as a whole or the constituent elements 230a to 230c of the screen 200; and a screen creation unit 103 configured to create a screen based on the screen 200 and the setup information created by the setup information creation unit 102.

[0096] According to the screen creation system SYS, for the mask creator, the created mask can be used for a larger number of screen users, and for the screen users, the setup creation work required for each task screen to which the mask is applied can be simplified.

[0097] (2) The screen creation system SYS according to (1) may further include a meta-information acquiring unit 101 configured to acquire meta-information about data, wherein the setup information creating unit 102 may set the meta-information acquired by the meta-information acquiring unit 101 as the setup information.

[0098] In this way, the screen creation system SYS can create a screen that better matches the application target (location).

[0099] (3) The screen creation system SYS according to (2), wherein the meta-information acquisition unit 101 can also acquire meta-information about a facility as the meta-information about the data, and the setup information creation unit 102 can set the meta-information about the facility acquired by the meta-information acquisition unit 101 as the setup information. Accordingly, the screen creation system SYS can create a screen corresponding to the type of facility at the application target (site).

[0100] (4) A screen creation method in the present disclosure includes: a selection step of selecting a screen 200; a setup information creation step of creating setup information based on a setup entry 201 and a setup condition 202 predefined for the selected screen 200 as a whole or each of the constituent elements 230a to 230c of the screen 200, with respect to each setup entry 201 defined for the screen 200 as a whole or the constituent elements 230a to 230c of the screen 200; and a screen creation step of creating a screen based on the screen 200 and the created setup information.

[0101] According to the screen creation method, similar beneficial effects as in (1) can be achieved.

[0102] (5) The screen creating method according to (4) may further comprise a meta-information acquiring step for acquiring meta-information about data, wherein the setup information creating step may set the acquired meta-information as setup information.

[0103] Accordingly, the screen creation process can produce similar beneficial effects as (2).

[0104] (6) In the screen creation method according to (5), the meta-information acquisition step may also acquire meta-information about a device as meta-information about the data, and the setup information creation step may set the meta-information acquired about the device as setup information. Accordingly, the screen creation method can provide similar advantageous effects as in (3). Explanation of reference symbols 1 screen creation device 10 Control unit 100 screen mask creation unit 101 Meta-information acquisition unit 102 Setup Information Creation Unit 103 Screen Creation Unit 20 storage units 200-1 to 200-n screen mask 201 Setup entry 202 Setup condition 30 Input instrument 40 Output Instrument 2 Data source 3 Facilities table 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 2010-152992

[0004]

Claims

[1] A screen creation system comprising: a setup information creation unit configured to, based on a setup entry and a setup condition predefined for an entire selected screen or each of the constituent elements of the screen, to create setup information relating to each setup entry defined for the screen as a whole or the constituent elements of the screen; and a screen creation unit configured to create a screen based on the screen mask and the setup information created by the setup information creation unit. [2] The screen creation system according to claim 1, further comprising a meta-information acquiring unit configured to acquire meta-information about data, wherein the setup information creating unit sets the meta-information acquired by the meta-information acquiring unit as setup information. [3] The screen creation system according to claim 2, wherein the meta information acquiring unit also acquires meta information about a device as the meta information about the data, and the setup information creating unit sets the meta information about the device acquired by the meta information acquiring unit as setup information. [4] A screen creation method comprising: a selection step for selecting a screen mask; a setup information creation step for creating, based on a setup entry and a setup condition predefined for the overall selected screen or each of the constituent elements of the screen, setup information with respect to each setup entry selected for the screen or the components of the screen mask are defined; and a screen creation step to create a screen based on the screen mask and the created setup information. [5] The screen creating method according to claim 4, further comprising a meta information acquiring step for acquiring meta information about data, wherein the setup information creating step sets the acquired meta information as setup information. [6] The screen creating method according to claim 5, wherein the meta information acquiring step also acquires meta information about a device as the meta information about the data, and the setup information creating step sets the meta information acquired about the device as setup information.

Images