Data management system, and data management method

JPWO2023199727A5Inactive Publication Date: 2024-11-08
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024514871
Authority / Receiving Office
JP · JP
Patent Type
Applications
Filing Date
2024-08-29
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent
Patent Text Reader

Abstract

The present invention enables a registration state of data input and registered using an input application to be confirmed visually. A data management system (100) comprises: a user terminal for accepting input of input data (D1) and transmitting the same; and a data management server (1) for receiving and registering the input data (D1) transmitted from the user terminal. The data management server (1) possesses a plurality of input form applications (AP1), and manages the registration of the input data (D1) for each input form application (AP1). The user terminal associates a graphical image (IM) serving as a base for displaying a registration state of the input data (D1) with one of the plurality of input form applications (AP1), and overlays and displays on the graphical image (IM) a frame image (FR) representing the registration state of the input data (D1) managed using the input form application (AP1) associated with the graphical image (IM). A display mode of the frame image (FR) is varied in accordance with the registration state of the input data (D1).
Need to check novelty before this filing date? Find Prior Art

Description

Data management system and data management method

[0001] The present invention relates to a data management system for managing data relating to various facilities, and a data management method for managing the data.

[0002] Conventionally, it is known to acquire various data obtained from devices or facilities and visually display the status of the data. For example, it is known to estimate the operating status of a device from sensor information obtained from the device and display the estimated operating status on an operating status transition diagram (see, for example, Patent Document 1). It is also known to display icons representing devices on a layout diagram (see, for example, Patent Document 2).

[0003] Patent No. 6961850 Patent No. 4909674

[0004] One method of acquiring data related to devices and facilities is to use an input application to input data and register it on a server, etc. Even for data that has been input and registered using an input application, there are times when you want to visually check the registration status of the data and which device or facility the data relates to.

[0005] An object of the present invention is to enable visual confirmation of the registration status of data that has been input and registered using an input application.

[0006] Below, several aspects will be described as means for solving the problems. These aspects can be combined as needed. A data management system according to one aspect of the present invention includes a user terminal that inputs and transmits input data related to equipment, and a data management server that receives and registers the input data transmitted from the user terminal. In this data management system, the data management server has multiple input form applications. The input form applications are executable on the user terminal and are used to input input data related to equipment using the user terminal. The data management server also manages the registration of input data on an input form application basis.

[0007] The user terminal associates a graphic image serving as a base for displaying the registration status of the input data with one of a plurality of input form applications, and overlays a frame image on the graphic image to display the registration status of the input data managed by the input form application associated with the graphic image. At this time, the user terminal changes the display mode of the frame image depending on the registration status of the input data.

[0008] In the data management system, one input form application is associated with a graphic image, and a frame image representing the registration status of input data managed by the input form application is overlaid on the graphic image. The display mode of the frame image is changed depending on the registration status of the input data. This allows the registration status of input data entered and registered in the input form application to be visually confirmed.

[0009] In the data management system, the frame image may be associated with one of the input fields arranged in the input form application associated with the graphic image. This allows a specific data item to be associated with the frame image when multiple data items can be input as input data in the input form application. As a result, it is possible to check the registration status of input data related to a specific data item more precisely.

[0010] In the data management system described above, the color of the border of the frame image or the color used to fill the interior of the frame image may be changed depending on the registration status of the input data. This allows the registration status of the input data to be confirmed at a glance by looking at the frame image overlaid on the graphic image.

[0011] In the data management system, the frame image may display attribute information of the associated input field, thereby enabling a user to recognize at a glance which data item of the input data is being displayed in the frame image.

[0012] In the above data management system, the user terminal may specify a frame image to display a list of input data managed by the input form application or input data corresponding to the input field associated with the specified frame image, thereby enabling the user to check a list of input data managed by the input form application associated with the graphic image overlaid with the frame image, or a list of input data related to a specific data item.

[0013] A data management method according to another aspect of the present invention is a data management method in a data management system including a user terminal and a data management server. The data management server has a plurality of input form applications. The input form applications are executable on the user terminal and are used to input input data related to equipment using the user terminal. The data management server also manages the registration of input data on an input form application basis. The data management method includes the following steps: ◎ A step in which the user terminal inputs and transmits input data related to equipment using the input form applications. ◎ A step in which the data management server receives and registers the input data transmitted from the user terminal. ◎ A step in which the user terminal associates a graphical image that serves as a base for displaying the registration status of the input data with one of the plurality of input form applications. ◎ A step in which the user terminal overlays and displays a frame image that displays the registration status of input data managed by the input form application associated with the graphical image on the graphical image. ◎ A step in which the user terminal changes the display mode of the frame image depending on the registration status of the input data.

[0014] In the data management method, one input form application is associated with a graphic image, and a frame image representing the registration status of input data managed by the input form application is overlaid on the graphic image. The display mode of the frame image is varied depending on the registration status of the input data. This allows the registration status of input data entered and registered in the input form application to be visually confirmed.

[0015] You can visually check the registration status of input data entered and managed in the input form application.

[0016] 1 is a diagram showing the overall configuration of a data management system. FIG. 1 is a diagram showing a specific configuration of a data management server. FIG. 2 is a diagram showing an example of a table data file. FIG. 3 is a diagram showing a specific configuration of a user terminal. FIG. 4 is a diagram showing an example of a display screen of an input form application. FIG. 5 is a diagram showing an example of a monitoring application. FIG. 6 is a diagram showing an example of a list display of input data / actual data displayed when a frame image is specified. FIG. 7 is a diagram showing an example of an application creation screen of an input form application. FIG. 8 is a diagram showing an example of an application creation screen of a monitoring application. FIG. 9 is a diagram showing an example of an application creation screen of a monitoring application. FIG. 10 is a diagram showing an example of an application creation screen when a position for installing a frame image is specified. FIG. 11 is a diagram showing an example of an application creation screen when a new frame image is placed. A flowchart showing the operation of a data management server. A flowchart showing the operation of a user terminal. A diagram showing an example of a start screen. A diagram showing an example of a start screen for monitoring mode.

[0017] 1. First Embodiment (1) Overview of Data Management System The following describes a data management system 100. The data management system 100 is installed in, for example, a factory, a plant, or the like, and is a system that implements "4M variation management" in a paperless manner. The 4M variation management is a concept that includes (i) management related to raw materials (Material) used in the production of products, (ii) management related to workers (Man) of factories, plants, etc., (iii) management related to the operation (Method) of factories, plants, etc., and (iv) management related to equipment (Machine) of factories, plants, etc.

[0018] Management of raw materials includes, for example, sending raw material shortage notifications to notify users that raw materials have run out, and managing raw material information. Management of workers includes, for example, managing worker information, providing various types of information in multiple languages, and calling personnel (trouble calls) when problems occur with equipment in factories, plants, etc. Management of operations includes, for example, managing product inspection results, managing work-related documents such as work procedures, and managing information about production lots. Management of equipment includes, for example, notifying users of problems that occur with equipment, and managing equipment inspections.

[0019] (2) Overall Configuration of Data Management System The overall configuration of the data management system 100 will be described using Fig. 1. Fig. 1 is a diagram showing the overall configuration of the data management system. The data management system 100 mainly includes a data management server 1, a first user terminal T1, and a second user terminal T2.

[0020] The data management server 1 is a computer system including a processor, a storage device (e.g., RAM, ROM, hard disk, SSD, etc.), and a network interface, and is a server that manages various applications, data, information, etc. related to the data management system 100. The data management server 1 registers and manages input data transmitted from the first user terminal T1.

[0021] The first user terminal T1 is a mobile terminal such as a tablet terminal or a smartphone that can communicate with the data management server 1 via a network (e.g., WAN, LAN, Internet, etc.). The first user terminal T1 is used by a worker who works in a factory, plant, etc. where the data management system 100 is installed. The worker can execute an input form application AP1 (described below) on the first user terminal T1 and input input data D1 related to the equipment.

[0022] In addition, the first user terminal T1 can check the registration status of the input data D1 entered in the input form application AP1 and registered in the data management server 1 by executing the monitoring application AP2 described below.

[0023] The data management system 100 includes a data transmission device 3. The data transmission device 3 is installed near a facility and transmits performance data D2 related to the facility to the data management server 1. The data transmission device 3 is, for example, a BLE (Bluetooth (registered trademark) LE) beacon button, an RFID reader, or an IC card reader.

[0024] The data management system 100 includes a second user terminal T2. The second user terminal T2 is a terminal such as a personal computer that can be used by an operator. The operator can use the second user terminal T2 to access the data management server 1 and create an input form application AP1 and a monitoring application AP2.

[0025] The first user terminal T1 may also have the same functions as the second user terminal T2. Conversely, the second user terminal T2 may also have the same functions as the first user terminal T1.

[0026] (3) Specific Configuration of Data Management Server The specific configuration of the data management server 1 will be described with reference to Fig. 2. Fig. 2 is a diagram showing the specific configuration of the data management server. The data management server 1 has a storage unit 11 and a processing unit 13.

[0027] The storage unit 11 is configured as a storage area of ​​the storage device of the data management server 1 and stores various information. Specifically, the storage unit 11 stores a plurality of input form applications AP1, a monitoring application AP2, input data D1, performance data D2, and user information UI. The storage unit 11 also stores programs (control programs, application creation programs) that are executed by the data management server 1 to realize each function of the data management server 1.

[0028] The input form application AP1 is an application that is executed on the first user terminal T1 and / or the second user terminal T2, and that allows the user to use the user terminal to input input data D1 related to equipment managed by the data management system 100. Examples of the input form application AP1 include an application that inputs information related to equipment trouble (e.g., the location of a fault in the equipment, the details of the fault, etc.) as the input data D1, and an application that inputs information related to equipment inspection (e.g., actual measurement data related to the equipment, etc.) as the input data D1.

[0029] The monitoring application AP2 is an application that is executed on the first user terminal T1 and / or the second user terminal T2 to check the registration status of the input data D1 and actual data D2 entered in the input form application AP1 and registered in the data management server 1.

[0030] The input form application AP1 and the monitoring application AP2 are created using the second user terminal T2 (or the first user terminal T1) and then stored in the storage unit 11. The input form application AP1 and the monitoring application AP2 are, for example, web applications executed on a web browser of the user terminal.

[0031] The input data D1 and performance data D2 are registered in the data management server 1 by being stored in the memory unit 11. In the data management server 1, there are two types of data registration: "provisional registration" and "registration." Provisional registration of data is performed when a specified operation needs to be performed on the data. For example, if the data relates to a problem with equipment and some kind of response is required for the problem, the data is provisionally registered. Once some kind of response is performed for the problem, the data is officially registered.

[0032] Furthermore, the input data D1 and the performance data D2 are managed in the storage unit 11 for each input form application AP1. Specifically, input data D1 entered using a specific input form application AP1 is associated with that specific input form application AP1. Furthermore, performance data D2 generated for a specific purpose is associated with an input form application AP1 created for the same purpose. For example, performance data D2 related to a problem with equipment A is associated with an input form application AP1 created specifically for the problem with the same equipment A.

[0033] The association of the input data D1 and the performance data D2 with the input form application AP1 can be realized by generating a dedicated data storage file (referred to as a table data file TD) for each input form application AP1, as shown in Fig. 3, and saving the input data D1 and the performance data D2 in this table data file TD. The structure of the table data file TD will be explained later. Fig. 3 is a diagram showing an example of a table data file.

[0034] The user information UI is information for managing users who can log in to the data management server 1 using the first user terminal T1 or the second user terminal T2. Specifically, the user information UI records the user ID and password used to log in to the data management server 1. The user information UI also records a list of the input form application AP1 and monitoring application AP2 that each user wishes to use.

[0035] In the user information UI, users (user IDs) are managed in user group units defined by specific attributes. These user groups are defined, for example, by the organization, department, team, etc. to which the workers (users) belong. For example, each user group includes workers (users) who belong to the same organization, department, team, etc. The user information UI manages access rights, such as for viewing input data D1 and performance data D2 and manipulating data, for each of the user groups.

[0036] The processing unit 13 is configured by the CPU of the data management server 1 and executes programs stored in the storage unit 11 to realize various functions of the data management server 1. Specifically, the processing unit 13 executes a control program to store and manage in the storage unit 11 the input data D1 entered using the input form application AP1 and transmitted from the user terminal, and the performance data D2 transmitted from the data transmission device 3.

[0037] In addition, the processing unit 13 provides the applications (input form application AP1, monitoring application AP2) that have been requested to be executed by the first user terminal T1 and the second user terminal T2 that have accessed the data management server 1 to these user terminals.

[0038] Furthermore, the processing unit 13 executes the application creation program to provide the second user terminal T2 (or the first user terminal T1) with a function for creating an application. Specifically, the processing unit 13 executes the application creation program on the user terminal to display an application creation screen on the user terminal. By performing predetermined operations on the application creation screen, an operator can create an application without having advanced knowledge of systems and programs. Application creation will be explained in more detail later.

[0039] (4) Specific Configuration of User Terminal The specific configuration of the user terminal will be explained below using Figure 4. Figure 4 is a diagram showing the specific configuration of the user terminal. The first user terminal T1 and the second user terminal T2 have almost the same configuration. Therefore, the following explanation will be given using the configuration of the first user terminal T1 as an example. The first user terminal T1 has a processing unit 41, a memory unit 43, a display unit 45, and an input unit 47.

[0040] The processing unit 41 is configured with a CPU and the like, and realizes various functions of the first user terminal T1 by executing programs stored in the storage unit 43. Specifically, the processing unit 41 executes applications held by the data management server 1. The storage unit 43 is configured with storage devices such as RAM, ROM, HDD, and SSD, and stores various settings and parameters for operating the first user terminal T1, programs for realizing the functions of the first user terminal T1, and the like.

[0041] The display unit 45 is a display device configured by a liquid crystal display, an organic EL display, etc., and displays various information, etc. The input unit 47 is an input device such as a touch panel, a keyboard, etc. for inputting various information.

[0042] (5) Structure of the Table Data File The structure of the table data file TD for storing the input data D1 and the performance data D2 will be explained below with reference to Fig. 3. The table data file TD has columns COL1 to COL5 and cells arranged in the row direction in each of the columns COL1 to COL4.

[0043] The cells in the first row of each of columns COL1 to COL5 are data item recording rows CE1. The cells in the second row and subsequent rows of each of columns COL1 to COL5 are data storage rows CE2. Input data D1 and performance data D2 are stored in each row of the data storage row CE2.

[0044] The data item recording row CE1 contains the names of the data items stored in the cells of each column of the data storage row CE2. In the example shown in FIG. 3, column COL1 of the data item recording row CE1 contains "Status." This means that column COL1 of the data storage row CE2 stores the registration form of the input data D1 and the performance data D2. The data registration form means whether the data is registered as provisional registration or as formal registration. Column COL2 of the data item recording row CE1 contains "Location." This means that column COL2 of the data storage row CE2 stores the identification number of the location (device) where the input data D1 and the performance data D2 were acquired.

[0045] Column COL3 of data item recording row CE1 states "Location Name." This means that column COL3 of data storage row CE2 stores the name of the location (equipment) where input data D1 and performance data D2 were acquired. Column COL4 of data item recording row CE1 states "Occurrence Time." This means that column COL4 of data storage row CE2 stores the time when an equipment problem or the like occurred. Column COL5 of data item recording row CE1 states "Person in Charge." This means that column COL5 of data storage row CE2 stores the name of the worker who is taking some kind of action regarding the equipment problem or the like.

[0046] (6) Specific Examples of Input Form Applications A specific example of an input form application AP1 used in the data management system 100 will be described below with reference to Fig. 5. Fig. 5 is a diagram showing an example of a display screen of an input form application. Note that the input form application AP1 described below is an example of an input form application AP1 used in the data management system 100, and input form applications AP1 other than those described below can also be freely created and used in the data management system 100.

[0047] 5 is an application for inputting input data D1 related to equipment trouble. The display screen ID1 of this input form application AP1 has input fields IF1 to IF4, item name display sections ITM1 to ITM4, and buttons B1 and B2.

[0048] Input fields IF1 to IF4 are fields for entering each data item of input data D1. Input field IF1 is a field for entering the identification number of the location where the trouble occurred. Input field IF2 is a field for entering the name of the location where the trouble occurred. Input field IF3 is a field for entering the time when the trouble occurred. Input field IF4 is a field for entering the name of the worker who is taking the prescribed action to resolve the trouble.

[0049] The item name display sections ITM1 to ITM4 are arranged near the corresponding input fields IF1 to IF4, and display the item names of the data items to be input using the corresponding input fields.

[0050] Button B1 is a button that commands the input data D1 to be registered in the data management server 1 by "provisional registration." Button B2 is a button that commands the input data D1 to be registered in the data management server 1 by "registration." When buttons B1 and B2 are pressed, the data values ​​entered in each input field of the input form application AP1 are sent to the data management server 1 as input data D1. At this time, a command as to whether to register the input data D1 as a provisional registration or as a formal registration is also sent to the data management server 1.

[0051] When the input form application AP1 shown in FIG. 5 is created, a table data file TD having the structure shown in FIG. 3 described above is generated.

[0052] (7) Specific Examples of Monitoring Applications A specific example of a monitoring application AP2 used in the data management system 100 will be described below with reference to Fig. 6. Fig. 6 is a diagram showing an example of a monitoring application. The monitoring application AP2 shown in Fig. 6 is an application created in association with the input form application AP1 as shown in Fig. 5. Note that the monitoring application AP2 described below is an example of a monitoring application AP2 used in the data management system 100, and monitoring applications AP2 other than those described below can also be freely created and used in the data management system 100.

[0053] The monitoring application AP2 has a graphic image IM and a frame image FR. The graphic image IM serves as a base for displaying the registration status of the input data D1 and / or the performance data D2. In other words, the frame image FR, which displays the registration status of the input data D1 and / or the performance data D2, is overlaid on the graphic image IM. The graphic image IM may be any image, but may be, for example, a layout diagram of a facility (e.g., a factory or office). As will be described later, the graphic image IM is associated with one of multiple input form applications AP1.

[0054] The frame image FR is displayed overlaid on the graphic image IM. The frame image FR displays the registration status of the input data D1 and / or performance data D2 managed by the input form application AP1 associated with the graphic image IM. One of the input forms of the input form application AP1 is associated with each frame image FR. That is, one of the columns of the table data file TD is associated with each frame image FR. Therefore, each frame image FR displays the registration status of the input data D1 and / or performance data D2 having a specific data value of a specific data item set in the input form (column).

[0055] In the case of the monitoring application AP2 shown in Fig. 6, the frame image FR is associated with the input field IF1 of the input form application AP1 shown in Fig. 4. That is, the frame image FR is associated with the column COL2 (location) of the table data file TD shown in Fig. 3. Therefore, in the monitoring application AP2 shown in Fig. 6, each frame image FR displays the registration status of the input data D1 and / or performance data D2 having the identification number of a specific location.

[0056] In this way, a specific data item that can be input in the input form application AP1 can be associated with the frame image FR. As a result, it is possible to check the registration status more precisely, for example, by checking the registration status of the input data D1 and / or the performance data D2 related to the specific data item. That is, as described above, it is possible to display the registration status of the input data D1 and / or the performance data D2 having a specific data value of the specific data item in each frame image FR.

[0057] The frame image FR includes a first frame image FR1 and a second frame image FR2. The first frame image FR1 displays the registration status of the input data D1 and / or the performance data D2. The first frame image FR1 displays the registration status of the input data D1 and / or the performance data D2 by varying the display mode. Specifically, the color used to fill the first frame image FR1 varies depending on the registration status of the input data D1 and / or the performance data D2. For example, if the input data D1 and performance data D2 to be monitored do not exist, the first frame image FR1 is filled in green. If the input data D1 and / or performance data D2 to be monitored are provisionally registered and a worker name has not been entered, the first frame image FR1 is filled in red. On the other hand, if the input data D1 and / or performance data D2 to be monitored are provisionally registered and a worker name has been entered, the first frame image FR1 is filled in yellow.

[0058] As another example of differentiating the display mode, the color of the frame of the first frame image FR1 may be different depending on the registration status of the input data D1 and / or the achievement data D2. It is possible to arbitrarily set how the color of the first frame image FR1 is changed depending on the registration status of the input data D1 and / or the achievement data D2. By changing the color of the first frame image FR1 depending on the registration status of the input data D1 and / or the achievement data D2 in this way, the registration status of the input data D1 and / or the achievement data D2 can be confirmed at a glance by looking at the frame image FR overlaid on the graphic image IM.

[0059] The first frame image FR1 also displays information about the input data D1 and / or performance data D2 being monitored. Specifically, the upper section of the first frame image FR1 displays the data values ​​of the input data D1 and / or performance data D2 being monitored. The lower section of the first frame image FR1 displays the attribute information. Therefore, the lower section of the first frame image FR1 is associated with one of the input fields of the input form application AP1.

[0060] For example, in the case of the monitoring application AP2 shown in Figure 6, the input field IF2 of the input form application AP1 is associated with the lower section of the first frame image FR1. That is, the lower section of the first frame image FR1 is associated with column COL3 of the table data file TD shown in Figure 3. As a result, the upper section of the first frame image FR1 displays the identification number of the location of the data being monitored. Meanwhile, the lower section displays the specific location name of that location identification number as attribute information.

[0061] By displaying the attribute information of the input field associated with the frame image FR in the first frame image FR1, it is possible to recognize at a glance which data item and which data value of the input data D1 and / or performance data D2 are being displayed in the frame image.

[0062] The second frame image FR2 is associated with some of the input fields of the input form application AP1 and displays the data items to be entered into the associated input fields. For example, in the example shown in Figure 6, the second frame image FR2 is associated with the input field IF4. This allows the name of the worker who is taking the required action to resolve the problem to be displayed in the second frame image FR2. The data items to be displayed in the second frame image FR2 can be selected arbitrarily.

[0063] Furthermore, in the monitoring application AP2, when a specific frame image FR is designated (for example, by touching a specific frame image FR or by moving the mouse cursor onto the frame image FR and clicking), a list L is displayed showing a list of input data D1 and / or performance data D2 corresponding to the input field (column) associated with the frame image FR, as shown in FIG. 7 . The example shown in FIG. 7 is an example of the list L displayed when a frame image FR with "101" displayed in the upper row of the first frame image FR1 is designated. That is, the input data D1 and / or performance data D2 for which the data value "101" is stored in column COL2 of the table data file TD are displayed in a list. FIG. 7 is a diagram showing an example of a list display of input data / actual data displayed when a frame image is designated.

[0064] The list L displayed when the frame image FR is designated may display a list of all the input data D1 and / or performance data D2 managed by the input form application AP1 associated with the graphic image IM of the monitoring application AP2. This allows the user to check the list of input data D1 and / or performance data D2 managed by the input form application AP1 associated with the graphic image IM on which the frame image FR is overlaid, or the list of input data D1 and / or performance data D2 related to a specific data item.

[0065] By using the above-described monitoring application AP2, it is possible to visually check the registration status of the input data D1 entered and registered using the input form application AP1, and the registration status of the performance data D2 transmitted from the data transmission device 3 and registered.

[0066] (8) Input Form Application Creation Program Hereinafter, an application creation program for creating the input form application AP1 will be described with reference to FIG. 8. FIG. 8 is a diagram showing an example of an application creation screen for the input form application. The application creation program for the input form application AP1 displays an application creation screen GUI1 as shown in FIG. 8 on the display unit of the second user terminal T2. The application creation screen GUI1 is a user interface for creating the outline of the display screen to be displayed by the input form application AP1. The input form application AP1 is generated based on the outline of the display screen created using the application creation screen GUI1.

[0067] The application creation screen GUI1 has a parts list display section PL, a parts placement area FI1, a save button B5, and a cancel button B6. The parts list display section PL displays a list of parts PA that can be placed in the parts placement area FI1.

[0068] The component placement area FI1 is an area for placing the component PA. The component placement area FI1 corresponds to the display screen of the input form application AP1. A header component PA' is placed in advance at the top of the component placement area FI1. In the header component PA', the content to be displayed in the header section (top) of the display screen is set.

[0069] The parts PA displayed in the parts list display section PL can be moved and placed at desired positions in the part placement area FI1, for example, by a drag-and-drop operation. In the input form application AP1, the parts PA correspond to elements that realize the functions of the input form application AP1, such as an input interface (input field). The placement positions of the parts PA in the part placement area FI1 are reflected on the display screen when the input form application AP1 is generated. In other words, the placement of the parts PA in the part placement area FI1 and the placement of the elements on the display screen are the same.

[0070] A component PA placed in the component placement area FI1 has a title TI, a component delete button B8, a component edit button B9, and a component duplicate button B10. The title TI indicates the name of the component PA. The component delete button B8 is a button for deleting the component PA from the component placement area FI1.

[0071] The edit part button B9 is a button for making various settings for the part PA. When the edit part button B9 is pressed, a setting screen for making detailed settings for the part PA is displayed. The user can make detailed settings for each element included in the input form application AP1 by making various settings for the part PA in this setting screen. The contents of the title TI can also be set in this setting screen. The duplicate part button B10 is a button for duplicating the part PA. Only the edit part button B9 is placed on the header part PA'.

[0072] The save button B5 is a button for generating an input form application AP1 using the component placement area FI1 in which the component PA is placed as the skeleton of the display screen, and for saving the generated input form application AP1 in the storage unit 11 of the data management server 1. When the save button B5 is pressed, the following process is specifically executed.

[0073] First, the component placement area FI1 in which the component PA is placed is sent to the processing unit 13 of the data management server 1. Next, the processing unit 13 converts the component placement area FI1 into a display screen for the input form application AP1. The processing unit 13 also converts the component PA placed in the component placement area FI1 into a corresponding element and places it on the display screen. Furthermore, the processing unit 13 converts the title TI of the component PA into an item name display area and places it on the display screen. After this, the processing unit 13 stores the input form application AP1 generated as described above in the storage unit 11.

[0074] Furthermore, when the input form application AP1 is created, the processing unit 13 generates a table data file TD based on the components placed in the component placement area FI1. More specifically, the table data file TD is generated by adding columns corresponding to the components placed in the component placement area FI1. For the input form application AP1 shown in Figure 5, a table data file TD like that shown in Figure 3 is generated.

[0075] The cancel button B6 is a button for canceling the creation of the input form application AP1 using the application creation screen GUI1.

[0076] In this way, by using the application creation screen GUI1, a user can create a desired input form application AP1 and a corresponding table data file TD by simply placing any part PA selected from the parts list display section PL at any position in the part placement area FI1, even if the user does not have advanced knowledge of systems and programs.

[0077] (9) Monitoring Application Creation Program Hereinafter, an application creation program for creating the monitoring application AP2 will be described with reference to Figures 9 and 10. Figures 9 and 10 are diagrams showing examples of application creation screens for the monitoring application. The application creation program for the monitoring application AP2 displays an application creation screen GUI2 on the display unit of the second user terminal T2. The application creation screen GUI2 is a screen for inputting various settings for the monitoring application AP2. The monitoring application AP2 is generated based on the settings input using the application creation screen GUI2.

[0078] The application creation screen GUI2 for the monitoring application AP2 has switching tabs TAB1 and TAB2. The switching tabs TAB1 and TAB2 switch the functions of the application creation screen GUI2. In detail, when the switching tab TAB1 is selected, a GUI for making general settings for the monitoring application AP2 is displayed, as shown in Fig. 9. On the other hand, when the switching tab TAB2 is selected, a GUI for placing a frame image FR in a graphic image IM is displayed, as shown in Fig. 10.

[0079] The GUI for general settings of the monitoring application AP2 shown in FIG. 9 includes input fields FD1 to FD10, a list display button LI1, check boxes CB1 and CB2, and buttons B11 to B13.

[0080] The input field FD1 is a field for inputting the application name of the monitoring application AP2 in any expression. The input field FD2 is a field for inputting information (e.g., an application name) for identifying the input form application AP1 that manages the input data D1 and performance data D2 for monitoring the registration status. That is, information about the input form application AP1 to be associated with the graphic image IM is input into the input field FD2.

[0081] The list display button LI1 is used to specify an icon for displaying the monitoring application AP2. Pressing the list display button LI1 displays a list of icons that can be used to display the monitoring application AP2. The operator can select a desired icon from this list.

[0082] The check box CB1 specifies whether or not the registration status monitoring targets are to be limited to the provisionally registered input data D1 and the performance data D2. If the check box CB1 is checked, the registration status monitoring targets are to be limited to the provisionally registered input data D1 and the performance data D2.

[0083] The button B11 is used to specify a graphic image IM to be associated with the input form application AP1 specified in the input field FD2. When the button B11 is pressed, a dialog box for specifying the graphic image IM is displayed, and the user can select the graphic image IM from the dialog box.

[0084] The input fields FD3 and FD4 are fields for setting the dimensions (height, width) of the first frame image FR1, and the input fields FD5 and FD6 are fields for setting the dimensions (height, width) of the second frame image FR2.

[0085] The input field FD7 is a field for setting the input field of the input form application AP1 to be associated with the frame image FR. Specifically, the column name of the column to be associated with the frame image FR in the table data file TD is entered in the input field FD7. As a result, each frame image FR displays the registration status of the input data D1 and / or performance data D2 having a specific data value in the column associated with the frame image FR.

[0086] The input field FD8 is a field for setting an input field of the input form application AP1 to be associated with the lower part of the first frame image FR1. More specifically, the input field FD8 specifies a column of the table data file TD that stores data values ​​to be displayed as attribute information.

[0087] The input field FD9 is a field for setting the input field of the input form application AP1 to be associated with the second frame image FR2. Specifically, the input field FD9 is used to input which column of the table data file TD is to be associated with the second frame image FR2, i.e., the column name of the associated column. As a result, each second frame image FR2 of the monitoring application AP2 displays the data value stored in the column associated with that second frame image FR2.

[0088] In the case of the monitoring application AP2 shown in Fig. 6, the second framed image FR2 is associated with the input field IF4 of the input form application AP1 shown in Fig. 4. That is, the second framed image FR2 is associated with column COL5 (person in charge) of the table data file TD shown in Fig. 3. As a result, each second framed image FR2 displays the name of the worker included in the input data D1 and / or performance data D2 for the location displayed in the upper row of the corresponding first framed image FR1.

[0089] The check box CB2 specifies the display mode of the first frame image FR1, i.e., the color to fill the first frame image FR1. The check box CB2 with the description "All empty" specifies the display mode (fill color) when input data D1 and / or performance data D2 are registered but no data values ​​exist for all data items.

[0090] The check box CB2 marked "Partially empty" specifies the display mode (fill color) when input data D1 and / or performance data D2 are registered but no data values ​​exist for some data items. In the case of the monitoring application AP2 shown in Figure 6, if no data value exists in column COL5 of the table data file TD, the first frame image FR1 is filled with the color specified in this check box CB2.

[0091] The check box CB2 with the description "Not all empty" specifies the display mode (fill color) when input data D1 and / or performance data D2 are registered and data values ​​exist in all data items. In the case of the monitoring application AP2 shown in Figure 6, when a data value exists in column COL5 of the table data file TD, the first frame image FR1 is filled with the color specified in this check box CB2.

[0092] The check box CB2 with the words "No Data" specifies the display mode (fill color) when input data D1 and actual data D2 having specific data values ​​of the data items associated with the frame image FR are not registered.

[0093] It is possible to check multiple checkboxes CB2, that is, in the application creation program of the monitoring application AP2, multiple display modes of the first frame image FR1 can be specified depending on the registration state.

[0094] The input field FD10 is a field for specifying the period of the input data D1 and / or performance data D2 whose registration status is to be monitored. Therefore, a field for inputting time-related data in the input form application AP1 is specified in the input field FD10. That is, a column in the table data file TD in which time-related data is stored is specified in the input field FD10. This allows the monitoring application AP2 to monitor the registration status of the input data D1 and / or performance data D2 for a predetermined period (e.g., one day) based on, for example, the time stored in the input data D1 and / or performance data D2.

[0095] On the other hand, the GUI shown in FIG. 10 for placing a frame image FR on a graphic image IM displays the graphic image IM specified using the GUI button B11 shown in FIG. 9. In this GUI, by performing an operation on the desired location of the frame image FR of the graphic image IM (e.g., by touching the location or by moving the mouse cursor to the location and clicking), a dialog box DB such as that shown in FIG. 11 is displayed. The dialog box DB displays the name of the data item entered in the input field of the input form application AP1 associated with the frame image FR. More specifically, the contents of the data item record row CE1 of the column of the table data file TD associated with the frame image FR are displayed. In the monitoring application AP2 shown in FIG. 6, the name "Location" is displayed as shown in FIG. 11. FIG. 11 illustrates an example of the display of the application creation screen when the location for the frame image is specified.

[0096] By entering a data value that can be taken by the data item of the input field (column) associated with the frame image FR into the input field FD11 of the above dialog box and pressing the "Yes" button B14, a new frame image FR (outline) is placed in the graphic image IM, as shown in Figure 12. Pressing the "No" button B15 in the dialog box DB allows the placement of the current frame image to be canceled. Figure 12 shows an example of the display on the application creation screen when a new frame image has been placed.

[0097] The button B12 is a button for generating a monitoring application AP2 based on the setting information set using the application creation screen GUI2, and for saving the generated monitoring application AP2 in the storage unit 11 of the data management server 1. When the button B12 is pressed, the following process is specifically executed.

[0098] First, the setting information set using the application creation screen GUI2 is sent to the processing unit 13 of the data management server 1. Next, the processing unit 13 generates a monitoring application AP2 based on the received setting information and stores it in the storage unit 11.

[0099] The button B13 is a button for canceling the creation of the monitoring application AP2 using the application creation screen GUI2.

[0100] In this way, even if an operator does not have advanced knowledge of systems and programs, he or she can create the desired monitoring application AP2 by simply using the application creation screen GUI2 to make the necessary settings (i.e., specifying the associated input form application AP1, specifying the graphic image IM, setting the frame image FR, etc.).

[0101] (10) Operation of Data Management System (10-1) Operation of Data Management Server The operation of the data management system 100 will be described below. First, the operation of the data management server 1 will be described with reference to Fig. 13. Fig. 13 is a flowchart showing the operation of the data management server.

[0102] The processing unit 13 of the data management server 1 determines whether it has received input data D1 from the user terminal executing the input form application AP1 or whether it has received performance data D2 from the data transmission device 3 (step S11). If it has not received the input data D1 or performance data D2 ("No" in step S11), the operation of the data management server proceeds to step S13. If it has received the input data D1 or performance data D2 ("Yes" in step S11), the processing unit 13 stores and registers the received input data D1 or performance data D2 in the storage unit 11 (step S12).

[0103] When registering the historical data D2, the processing unit 13 determines which facility the historical data D2 relates to and for what purpose. This determination can be made, for example, based on the identification information of the data transmission device 3 that is the sender of the historical data D2. The processing unit 13 then associates the received historical data D2 with an input form application AP1 for the same purpose related to the same facility and stores it in the storage unit 11. Specifically, for example, if the received historical data D2 is data related to a problem with facility A, the processing unit 13 stores this historical data D2 in a table data file TD created for the input form application AP1 used for the purpose related to the problem with facility A.

[0104] The processing unit 13 also stores the received input data D1 in the table data file TD of the input form application AP1 used when the input data D1 was entered.

[0105] In this way, the data management server 1 can manage the input data D1 and the performance data D2 for each input form application AP1. After registering the input data D1 or the performance data D2, the operation of the data management server 1 proceeds to step S13.

[0106] In step S13, it is determined whether or not to stop the operation of the data management server 1. If the operation of the data management server 1 is to be continued ("No" in step S13), the operation of the data management server 1 returns to step S11. That is, the above steps S11 to S12 are repeatedly executed by the data management server 1. On the other hand, if the operation of the data management server 1 is to be stopped ("Yes" in step S13), the data management server is stopped.

[0107] (10-2) Operation of the User Terminal The operation of the user terminal will be described below with reference to Fig. 14. Fig. 14 is a flowchart showing the operation of the user terminal. First, a user using the user terminal logs in to the data management server 1 using the user ID and password that the user has (step S21).

[0108] When the user logs in to the data management server 1, a start screen GUI3 as shown in Fig. 15 is displayed on the display unit of the user terminal. Fig. 15 is a diagram showing an example of the start screen. After this, the operation mode is switched to a monitoring mode (step S22). The monitoring mode is an operation mode for executing monitoring of the registration status of the input data D1 and / or the performance data D2 in the data management system 100.

[0109] To transition to the monitoring mode, the following steps are performed: First, an operation is performed on the mode list display section ML of the start screen GUI3 to display a list of operation modes, and then the monitoring mode is selected from the list of operation modes to transition the operation mode to the monitoring mode.

[0110] When the operation mode transitions to the monitoring mode, a start screen GUI4 as shown in Fig. 16 is displayed on the display unit of the user terminal. Fig. 16 is a diagram showing an example of the start screen of the monitoring mode. The start screen GUI4 of the monitoring mode displays an icon ICO1 for adding (creating) a monitoring application AP2 and an icon ICO2 of a monitoring application AP2 that can be executed by the currently logged-in worker.

[0111] After transitioning to the monitoring mode, a monitoring application AP2 is created as necessary (step S23). In detail, the monitoring application AP2 is created as follows.

[0112] First, an operation is performed on icon ICO1 on the start screen GUI4 to execute a program for creating a monitoring application AP2 on the user terminal. After executing the program and displaying the application creation screen GUI2 on the display unit of the user terminal, various settings for the monitoring application AP2 are performed. First, an input form application AP1 that manages the input data D1 and / or performance data D2 to be monitored is specified. This is achieved by entering information about the input form application AP1 to be specified (such as the application name) in the input field FD2 of the application creation screen GUI2 shown in FIG.

[0113] Next, a graphic image IM that will be the basis for displaying the data registration status is associated with the input form application AP1 specified above. This is achieved by using the button B11 on the application creation screen GUI2 to select the graphic image IM that you want to associate with the input form application AP1.

[0114] Thereafter, the application creation screen GUI2 is used to set the size of the frame image FR, set the input field (column) to be associated with the frame image FR, set the display mode of the first frame image FR1, and the like.

[0115] After completing the above various settings, the application creation screen GUI2 shown in Fig. 10 is displayed, and the frame image FR is placed by specifying the corresponding position of the graphic image IM. After that, by pressing the button B12, the monitoring application AP2 is generated and stored in the storage unit 11. When the creation of the monitoring application AP2 is complete, the screen returns to the start screen GUI4 of the monitoring mode shown in Fig. 16. At this time, the icon ICO2 of the newly created monitoring application AP2 is added and displayed on the start screen GUI4.

[0116] While the monitoring mode start screen GUI4 is displayed, the user operates the icon ICO2 to execute the desired monitoring application AP2 on the user terminal (step S24). As a result, a display screen of the monitoring application AP2, such as that shown in Fig. 6, is displayed on the display unit of the user terminal.

[0117] On the display screen of the monitoring application AP2, each frame image FR displayed overlaid on the graphic image IM displays the registration status of the corresponding input data D1 and / or performance data D2 (step S25). Specifically, the display mode of each frame image FR varies depending on the registration status of the corresponding input data D1 and / or performance data D2. More specifically, the color used to fill the interior of the first frame image FR1 of each frame image FR varies depending on the registration status of the input data D1 and / or performance data D2. Furthermore, if a data value exists in column COL5 of the input data D1 and / or performance data D2 to be monitored, the data value (worker name) of column COL5 is displayed in the second frame image FR2.

[0118] In this way, the monitoring application AP2 created using the user terminal associates one input form application AP1 with a graphic image IM, and overlays this graphic image IM with a frame image FR that represents the registration status of the input data managed by the input form application. The display mode of the frame image FR varies depending on the registration status of the input data D1 and / or the performance data D2. This monitoring application AP2 allows the user to visually check the registration status of the input data D1 entered and registered by the input form application AP1 and / or the performance data D2 acquired by the data transmission device 3.

[0119] Furthermore, the monitoring application AP2 fills the first frame image FR1 with different colors depending on the registration status of the input data D1 and / or the performance data D2, which allows the user to check the registration status of the input data D1 and / or the performance data D2 at a glance at the frame image FR overlaid on the graphic image IM.

[0120] 2. Features of the Embodiments The above-described embodiments can also be described as follows. (1) A data management system (e.g., data management system 100) includes user terminals (e.g., first user terminal T1, second user terminal T2) that input and transmit input data related to equipment (e.g., input data D1), and a data management server (e.g., data management server 1) that receives and registers the input data transmitted from the user terminals. In this data management system, the data management server has multiple input form applications (e.g., input form application AP1). The input form applications are executable on the user terminals and are used to input input data related to equipment using the user terminals. Furthermore, the data management server manages the registration of input data on an input form application basis.

[0121] The user terminal associates a graphic image (e.g., graphic image IM) that serves as a base for displaying the registration status of the input data with one of a plurality of input form applications, and overlays a frame image (e.g., frame image FR) that displays the registration status of the input data managed by the input form application associated with the graphic image on the graphic image. At this time, the user terminal changes the display mode of the frame image depending on the registration status of the input data.

[0122] In the data management system, one input form application is associated with a graphic image, and a frame image representing the registration status of input data managed by the input form application is overlaid on the graphic image. The display mode of the frame image is changed depending on the registration status of the input data. This allows the registration status of input data entered and registered in the input form application to be visually confirmed.

[0123] (2) In the data management system described in (1) above, the frame image may be associated with one of the input fields (e.g., input fields IF1 to IF4) arranged in the input form application associated with the graphic image. This allows a specific data item to be associated with the frame image when multiple data items can be entered as input data in the input form application. This allows for more precise confirmation of the registration status, such as checking the registration status of input data related to a specific data item.

[0124] (3) In the data management system of (1) or (2) above, the color of the border of the frame image or the color used to fill the inside of the frame image may be changed depending on the registration status of the input data. This allows the registration status of the input data to be confirmed at a glance by looking at the frame image overlaid on the graphic image.

[0125] (4) In the data management system of (2) or (3) above, the frame image may display attribute information of the associated input field, thereby making it possible to recognize at a glance which data item of the input data is displayed in the frame image.

[0126] (5) In the data management systems described in (1) to (4) above, the user terminal may specify a frame image to display a list of input data managed by the input form application or input data corresponding to the input field associated with the specified frame image. This allows the user to check a list of input data managed by the input form application associated with the graphic image overlaid with the frame image, or a list of input data related to a specific data item.

[0127] (6) A data management method is a data management method in a data management system including a user terminal and a data management server. The data management server has multiple input form applications. The input form applications are executable on the user terminal and are used to input input data related to equipment using the user terminal. The data management server also manages the registration of input data on an input form application basis. The data management method includes the following steps: ◎ A step in which the user terminal inputs and transmits input data related to equipment using the input form application (e.g., step S11). ◎ A step in which the data management server receives and registers the input data transmitted from the user terminal (e.g., step S12). ◎ A step in which the user terminal associates a graphic image serving as a base for displaying the registration status of the input data with one of the multiple input form applications (e.g., step S23). ◎ A step in which the user terminal overlays a frame image, displaying the registration status of input data managed by the input form application associated with the graphic image, on the graphic image (e.g., steps S24-S25). A step in which the user terminal changes the display mode of the frame image depending on the registration status of the input data (for example, step S25).

[0128] In the data management method, one input form application is associated with a graphic image, and a frame image representing the registration status of input data managed by the input form application is overlaid on the graphic image. The display mode of the frame image is varied depending on the registration status of the input data. This allows the registration status of input data entered and registered in the input form application to be visually confirmed.

[0129] 3. Other Embodiments While the above describes an embodiment of the present invention, the present invention is not limited to the above embodiment and various modifications are possible without departing from the spirit of the invention. In particular, the multiple embodiments and modifications described in this specification can be combined as needed. (A) The processing order and / or processing content of each step included in the flowchart described in the first embodiment above can be changed without departing from the spirit of the present invention. For example, in the flowchart showing the operation of the user terminal in FIG. 14, if the desired monitoring application AP2 already exists, the processing of step S23 may be omitted. In other words, the desired monitoring application AP2 may be executed without creating the monitoring application AP2.

[0130] (B) In the monitoring mode, multiple monitoring applications AP2 may be executed simultaneously. In this case, which of the multiple monitoring applications AP2 is displayed on the display unit may be selectable by switching tabs, etc.

[0131] (C) The input form application AP1 and the monitoring application AP2 are not limited to web applications provided by the data management server 1, but may be applications that can be executed independently on the user terminal.

[0132] The present invention can be widely applied to data management systems that manage data relating to various facilities.

[0133] 100: Data management system 1: Data management server 11: Storage unit 13: Processing unit 3: Data transmission device T1: First user terminal T2: Second user terminal 41: Processing unit 43: Storage unit 45: Display unit 47: Input unit AP1: Input form application AP2: Monitoring application D1: Input data D2: Performance data FR: Frame image FR1: First frame image FR2: Second frame image IM: Graphic image L: List TD: Table data file

Claims

1. A data management system including a user terminal for inputting and transmitting input data related to equipment, and a data management server for receiving and registering the input data transmitted from the user terminal, The data management server includes: a plurality of input form applications executable on the user terminal for inputting the input data relating to the facility using the user terminal; managing the registration of the input data for each input form application; The user terminal includes: Associating a graphical image serving as a base for displaying a registration state of the input data with one of the plurality of input form applications; a frame image indicating a registration state of the input data managed by the input form application associated with the graphic image is overlaid on the graphic image; A display mode of the frame image is changed depending on a registration state of the input data; the frame image is placed at a position by displaying the graphic image in a user interface for placing the frame image on the graphic image and performing a predetermined operation at a position on the displayed graphic image where the frame image is to be placed; the frame image is associated with one of the input fields arranged in the input form application associated with the graphic image, and displays a data item inputted into the associated input field; Data management system.

2. The frame image is a first frame image that is associated with a first input field arranged in the input form application associated with the graphic image and displays a data item inputted into the first input field; a second frame image that is associated with a second input field arranged in the input form application associated with the graphic image and displays a data item inputted into the second input field; The data management system of claim 1 , comprising:

3. The data management system according to claim 1 , wherein a color of the frame line of the frame image or a color used to fill the inside of the frame image is changed depending on a registration state of the input data.

4. A data management system as described in claim 2, wherein the first frame image displays attribute information entered into the first input field.

5. The data management system described in claim 2, wherein the user terminal, by specifying the frame image, displays a list of the input data managed by the input form application or the input data corresponding to the input field associated with the specified frame image.

6. A data management method in a data management system including a user terminal and a data management server that is executable on the user terminal, has a plurality of input form applications for inputting input data related to equipment using the user terminal, and manages registration of the input data on a per-input form application basis, comprising: The user terminal inputs and transmits the input data related to the facility using the input form application; a step of the data management server receiving and registering the input data transmitted from the user terminal; a step of associating, by the user terminal, a graphic image serving as a basis for displaying a registration status of the input data with one of the plurality of input form applications; a step of displaying, by the user terminal, a frame image indicating a registration status of the input data managed by the input form application associated with the graphic image, overlaying the graphic image; a step of changing a display mode of the frame image by the user terminal depending on a registration state of the input data; Equipped with the frame image is placed at a position by displaying the graphic image in a user interface for placing the frame image on the graphic image and performing a predetermined operation at a position on the displayed graphic image where the frame image is to be placed; the frame image is associated with one of the input fields arranged in the input form application associated with the graphic image, and displays a data item inputted into the associated input field; Data management methods.