JP2007300373A - Apparatus information management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an apparatus information management system which ensures the security of apparatus information and easily adds, changes, or deletes externally enabled operations to an apparatus information memory having stored apparatus information. <P>SOLUTION: The apparatus information management system 1 comprises an apparatus information table 73, an operation setting file folder 42a, client computers 31, 50, and an indicating server 43. The apparatus information table 73 stores apparatus information, and the file folder 42a stores an operation setting file enabling specific operations to the information table 73 from outside. The client computers 31, 50 enable the registration of the operating setting file in the file folder 42a. The indicating server 43 refers to the operation setting file to make an access screen 60 for showing available operations to the apparatus information table 73 from outside. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a device information management system that accumulates device information related to devices and provides the device information to the outside as needed.

  In recent years, there has been an increasing number of cases in which device information related to devices such as air conditioning facilities is collected and services for managing devices based on the collected device information are introduced. Specific contents of such services include equipment abnormality monitoring, failure prediction, charge management such as electricity charges associated with the use of equipment, proposals for improvement of equipment usage by data analysis, creation of various reports, etc. .

  In order to realize such a service, in many cases, a database for accumulating device information is prepared in an information collection center or the like that is remote from the property where the device is deployed. In such cases, from the aspect of protecting customer information, even if the staff of the information collection center, etc. are aiming to provide the above services to customers, appropriate restrictions will be placed on access to the database. Is required.

In this regard, Patent Document 1 discloses a configuration in which device information relating to a large number of devices is collected in one database, and a person who has attempted to access this database from the outside is displayed on a predetermined access screen. A configuration is adopted in which device information is acquired by selecting an operation. That is, the operations permitted to the user are restricted, and the safety of the device information is taken into consideration.
JP-A-2004-318333

  However, in the case of Patent Document 1, the access screen (see FIG. 11 of Patent Document 1) provided to a person who tries to access the database is designed to accept only a predetermined operation selection. Therefore, for example, every time an operation that should be permitted to the user is added, in addition to developing a functional module that realizes the operation related to the addition, the access screen must be corrected, Development costs will increase. However, if an access screen is not prepared and the user is allowed to access the database directly without limitation, the safety of the device information may be impaired.

  An object of the present invention is to provide a device information management system that can ensure the safety of device information and can easily add, change, or delete operations that can be performed from the outside with respect to a device information storage unit that stores device information. There is to do.

  The device information management system according to the first aspect of the present invention comprises a device information storage unit, an operation setting information storage unit, an operation setting information registration unit, and a screen creation unit, stores device information about the device, and if necessary Provide device information to the outside. Device information is stored in the device information storage unit. Operation setting information is stored in the operation setting information storage unit. The operation setting information is information that enables a specific operation to be performed on the device information storage unit from the outside. The operation setting information registration unit can add, change, or delete the operation setting information from the operation setting information storage unit. The screen creation unit creates an access screen with reference to the operation setting information storage unit. The access screen displays operations that can be performed on the device information storage unit from the outside.

  In this device information management system, device information is stored in the device information storage unit. Access to the device information storage unit from the outside is performed via an access screen created by the screen creation unit. When creating the access screen, the screen creation unit determines the operations that can be performed on the device information storage unit from the outside based on the operation setting information stored in the operation setting information storage unit. The operation determined to be able to be performed from the outside on the device information storage unit is displayed. That is, in this device information management system, operations that can be performed on the device information storage unit from the outside are limited by the operation setting information, and the operation setting information is stored in the operation setting information storage unit via the operation setting information registration unit. By adding, changing or deleting, it is possible to register operations that can be performed on the device information storage unit from the outside. Thereby, in this device information management system, the safety of the device information is ensured, and addition, change, or deletion of operations that can be performed from the outside with respect to the device information storage unit in which the device information is stored can be easily performed.

  The device information management system according to the second invention is the device information management system according to the first invention, wherein the specific operation is an operation for extracting at least a part of the device information from the device information storage unit.

  In this device information management system, it is possible to impose restrictions on extracting device information stored in the device information storage unit from the outside.

  A device information management system according to a third invention is the device information management system according to the first or second invention, wherein the operation setting information includes information for associating a specific user with a specific operation. The screen creation unit creates an access screen according to the user.

  In this device information management system, operations that can be performed on the device information storage unit from the outside are registered in association with the user who is the operation subject, and dedicated operations are displayed for each user. Access screen is created. In other words, in this device information management system, it is possible to limit the operations permitted for each user for each user.

  A device information management system according to a fourth invention is the device information management system according to any one of the first to third inventions, wherein the operation setting information storage unit includes an operation setting file storage unit, an operation list storage unit, Have The operation setting file storage unit stores an operation setting file describing the contents of a specific operation in a predetermined format. The operation list storage unit stores an operation list created based on the operation setting file. The operation list is a list of operations that can be performed on the device information storage unit from the outside. The operation setting information registration unit can add, change, or delete an operation setting file from the operation setting file storage unit. The screen creation unit creates an access screen with reference to the operation list storage unit.

  In this device information management system, when an operation setting file in which a description of operations that can be performed on the device information storage unit from the outside is described in a predetermined format is registered in the operation setting information storage unit, the contents of the operation setting file are stored. Based on this, a list of operations that can be performed on the device information storage unit from the outside is created, and an access screen is created based on this operation list. That is, from the outside, it is not necessary to directly modify the operation list referred to by the screen creation unit when the access screen is created. Therefore, when performing registration work, it is only necessary to describe the content of the operation in a predetermined format and store it in a predetermined location, and it is possible to add, change or delete operations that can be performed from the outside to the device information storage unit. It becomes easy.

  A device information management system according to a fifth invention is a device information management system according to any one of the first to fourth inventions, comprising an operation request information creation unit, an operation request information storage unit, and an operation execution unit. Further prepare. The operation request information creating unit, when an external request is made to perform at least one of the operations that can be performed on the device information storage unit from the outside displayed on the access screen, The operation request information shown is created. Operation request information is stored in the operation request information storage unit. The operation execution unit refers to the operation request information storage unit and executes an operation requested from the outside.

  In this device information management system, operations that can be performed from the outside to the device information storage unit are displayed on an access screen accessible from the outside. When an operation is selected via the access screen, operation request information is created and stored in the operation request information storage unit. On the other hand, the operation execution unit sequentially executes the operations selected via the access screen based on the operation request information stored in the operation request information storage unit. As described above, in the device information management system, it is possible to cause the operation execution unit to execute the operation selected via the access screen.

  A device information management system according to a sixth aspect of the present invention is the device information management system according to the fifth aspect of the present invention, wherein the operation execution unit associates information related to the execution progress of the operation corresponding to the operation request information with the operation request information. Store in the information storage. The screen creation unit refers to the operation request information storage unit and generates an execution progress display screen. The execution progress display screen displays the execution progress of the operation executed by the operation execution unit.

  In this device information management system, information related to the execution progress of the operation selected via the access screen is stored in the operation request information storage unit in association with the operation request information corresponding to the operation. Then, based on the information related to the execution progress stored in the operation request information storage unit, an execution progress display screen for displaying the execution progress of the operation is created by the screen creation unit. Thereby, it is possible to grasp the execution progress of the selected operation from the outside.

  In the device information management system according to the first aspect of the invention, the safety of the device information is ensured, and the addition, change, or deletion of operations that can be performed from the outside with respect to the device information storage unit in which device information is stored is facilitated. .

  In the device information management system according to the second invention, it is possible to impose restrictions on extracting device information stored in the device information storage unit from the outside.

  In the device information management system according to the third aspect of the present invention, it is possible to limit the operations permitted for each user for each user.

  In the device information management system according to the fourth aspect of the present invention, it is easier to add, change or delete operations that can be taken from the outside with respect to the device information storage unit.

  In the device information management system according to the fifth aspect of the present invention, it is possible to cause the operation execution unit to execute the selected operation.

  In the device information management system according to the sixth aspect of the present invention, it is possible to grasp the execution progress of the selected operation from the outside.

<Overall configuration of device information management system>
FIG. 1 shows a device information management system 1 according to an embodiment of the present invention. The equipment information management system 1 is mainly operated in the information collection center 20, collects equipment information related to the air conditioning equipment 14 from the air conditioning equipment 14 having a predetermined communication function, and appropriately manages the collected equipment information. System.

  The information collection center 20 exists remotely from the property 10 where the air conditioning equipment 14 is deployed, and relates to maintenance of the air conditioning equipment 14 based on the equipment information related to the air conditioning equipment 14 collected by the equipment information management system 1. It is provided to provide a service to an administrator of the air conditioning equipment 14. Services related to the maintenance of the air conditioning equipment 14 include monitoring of abnormality of the air conditioning equipment 14, prediction of failure, charge management such as electricity charges associated with the use of the air conditioning equipment 14, proposals for improving the usage of the air conditioning equipment 14 by data analysis, For example, preparation of a report. In the description of the present embodiment, the information collection center 20 collects device information from a plurality of air conditioning facilities 14 deployed in a plurality of properties 10, but at the time of service start-up, 1 Device information may be collected only from the air conditioning facility 14.

  In addition to the information collection center 20, a service center 30 is provided at a remote location of the property 10 as an organization that provides services related to maintenance of the air conditioning equipment 14. In response to a request from the information collection center 20, the service center 30 performs the maintenance work of the air conditioning equipment 14 determined to be necessary in the information collection center 20, up to the property 10 where the air conditioning equipment 14 related to the abnormality is deployed. A service person is dispatched, or equipment information related to the air conditioning equipment 14 is provided from the information collection center 20, and a service related to the maintenance of the air conditioning equipment 14 is provided to an administrator of the air conditioning equipment 14 independently. Or Note that the business operator that operates the information collection center 20 and the business operator that operates the service center 30 may be the same or different.

  The equipment information management system 1 is mainly installed in the facility management apparatus 13 installed in the property 10, the server computer 40 and client computer 50 installed in the information collection center 20, and the service center 30. A client computer 31; Hereinafter, these components constituting the device information management system 1 will be described in detail.

<Details of component parts of device information management system>
(1) Facility management device The facility management device 13 is installed in the property 10 and performs air-conditioning control according to a command from an administrator of the air-conditioning facility 14 in the same property 10 or to the administrator of the air-conditioning facility 14. The air conditioner 14 or the parts constituting the air conditioner 14 are presented. The facility management device 13 has a communication function with the air conditioning facility 14 and can be connected to the Internet line 6. The facility management device 13 collects device information related to the air conditioner 14 from the air conditioner 14 and processes the collected device information. In this state, it is periodically transmitted to the server computer 40 in the information collection center 20 via the Internet line 6 (in this embodiment, device information for one day is transmitted once a day at a predetermined time). The equipment information here includes, for example, the operating time of the air conditioning equipment 14, the amount of power consumption, the operation mode during operation, the indoor temperature / outdoor temperature detected by a sensor attached to the air conditioning equipment 14, and the air conditioning equipment 14 The state of the parts that make up is included. Furthermore, although an abnormality in the air conditioning facility 14 may be detected in the facility management apparatus 13, in such a case, after the abnormality is detected, information indicating that fact is immediately transmitted to the server computer 40 as device information.

  The air conditioning facility 14 may be a multi-type air conditioning facility including a plurality of indoor units and outdoor units, or may be a central air conditioning facility including a heat source device and a secondary side air conditioning device. Further, it may be a commercial air conditioner introduced into a large building or a home air conditioner. That is, the air conditioning equipment 14 may be any type of air conditioning equipment as long as it has a communication function with the outside.

(2) Server Computer As shown in FIG. 2, the server computer 40 is a computer group composed of a plurality of computers installed in the information collection center 20. The server computer 40 includes a database server (hereinafter referred to as DB server) 41, a registration server 42, a display server 43, and an execution server 44 described below. The computers constituting the server computer 40 including these servers 41 to 44 are connected via the LAN 7 and can communicate with each other.

a) DB Server The DB server 41 stores a device information table 73, an operation setting table 70, and an operation request table 71.

  In the equipment information table 73, equipment information about the air conditioning equipment 14 that is sent from the equipment management apparatus 13 of each property 10 via the Internet line 6 periodically or when an abnormality is detected is sequentially obtained as time-series data. It will be accumulated. The huge amount of device information stored in the device information table 73 is stored in the client computer 50 installed in the information collection center 20 or the client computer 31 installed in the service center 30 as necessary. And is used by the staff of the information collection center 20 or the staff of the service center 30 to perform services related to the maintenance of the air conditioning equipment 14. However, since customer information is managed in the device information table 73, access authority to the device information table 73 is strictly managed, and full access authority is a part of the information collection center 20 and the service center 30. Is given only to administrators. General staff other than some managers of the information collection center 20 and the service center 30 cannot directly access the device information table 73. Access to the device information table 73 by these general staff is as follows. All are performed via the access screens 60 to 63 (see FIGS. 6 to 9) provided by the display server 43 described below. Further, even for the same general staff, the access authority to the device information table 73 differs depending on the business contents and the like.

  The operation setting table 70 shown in FIG. 3 stores information related to operations that general staff can take on the device information table 73, that is, information related to access privileges of the general staff to the device information table 73. One record stored in the operation setting table 70 corresponds to one operation, and the operation setting table 70 is a list of operations that general staff can take on the device information table 73 as a whole. More specifically, the operation ID field stores the operation ID, the VALID field stores information indicating whether the operation is enabled or disabled, and the operation setting file field stores the operation. The operation setting file created by the administrator for definition is compressed and stored, the operation setting file name field stores the file name of the operation setting file, and the update date and time field indicates the update date and time of the operation setting file. Is stored, the heading field stores the heading when the operation is displayed on the access screens 60 to 63, and the display order field stores the display order when the operation is displayed on the access screen 60. In the JSP file field, an input screen (access screen 61) prompting the user to input parameters necessary for executing the operation is displayed. JSP file definition is stored in a compressed.

  Further, one record stored in the operation request table 71 shown in FIG. 4 corresponds to one operation actually requested by the general staff via the access screens 60 to 62. More specifically, the request ID field stores the ID of the request, the operation ID field stores the ID of the requested operation (same as the operation ID in the operation setting table 70), and the status field stores the request ID. The progress of execution of the requested operation (waiting for execution, executing, normal termination, abnormal termination) is stored, and the reason for abnormal termination of the requested operation is stored in the reason field, and the start time field Stores the start time of the requested operation, the end time field stores the end time of the requested operation, and the user name field stores the user name of the general employee who requested the operation, The parameter field stores the contents of the parameters necessary for execution of the operation input by the general staff via the access screen 61, and the result The file name field stores the file name attached to the result file created by executing the requested operation, and the download flag field indicates whether the result file has been downloaded to the client computers 31, 60, etc. A flag to indicate is stored. In the result file, for example, when the general staff requests to retrieve and extract the device information from the device information table 73, the device information retrieved and extracted by executing the operation is recorded.

b) Registration Server The registration server 42 is for setting the access authority to the device information table 73 of general staff, and only accesses from some administrators of the information collection center 20 and the service center 30. Accepted. In other words, an administrator who has access authority to the registration server 42 can permit general staff to perform a specific operation on the device information table 73.

  When these administrators want to allow general staff to perform a specific operation on the device information table 73, an operation setting file is described and created in a predetermined format. The file is stored in a predetermined file folder (hereinafter, “operation setting file folder”) 42 a prepared in the registration server 42. This operation setting file is the same as the operation setting file that is compressed and stored in the operation setting file field of the operation setting table 70.

  On the other hand, the registration server 42 checks the operation setting file folder 42a at a predetermined interval or when a request is received, and if there is a change in the operation setting file folder 42a, the change is reflected in the operation setting table 70. .

c) Display Server The display server 43 is a WWW server compatible with the HTTP protocol, and includes a display block 43a and an operation block 43b for operating the operation request table 72. The display block 43 a refers to the operation setting table 70 stored in the DB server 41, and creates access screens 60 to 63 when a general staff accesses the device information table 73. When the display block 43a receives an operation request for the device information table 73 from the general staff via the access screens 60 to 62, the operation block 43b creates information on the requested operation, and the DB server 41 Are stored in the operation request table 71. The display block 43a displays the progress of the operation requested by the general staff via the access screens 60 to 62 to the general staff.

d) Execution Server The execution server 44 sequentially reads records from the operation request table 71 stored in the DB server 41 and executes operations corresponding to the records. Then, the execution server 44 reflects the execution progress in the operation request table 71. Further, the execution server 44 distributes the result file created by executing the operation to the general staff in response to a request from the general staff.

(3) Client computer in the information collection center The client computer 50 installed in the information collection center 20 is one or a plurality of ordinary personal computers connected to the LAN 7, and includes an input device 51 such as a mouse or a keyboard. I have. A browser is installed in the client computer 50, and when a general staff member of the information collection center 20 accesses the device information table 73, the client computer 50 is connected to the display server 43 via the browser and displays the display server 43. The access screens 60 to 63 are received from the block 43a. Further, a general staff who has requested an operation on the device information table 73 via the access screens 60 to 62 provided from the display block 43a can download a result file created by executing the operation via a browser. .

(4) Client computer in service center The client computer 31 installed in the service center 30 is installed in the information collection center 20 except that it is connected to the server computer 40 via the Internet line 6 instead of the LAN 7. It has the same configuration as the client computer 50. The client computer 31 includes an input device 32 that corresponds to the input device 51 of the client computer 50.

<Processing flow when operations permitted for general staff are registered>
Next, processing when operations that can be performed by the general staff on the device information table 73 are registered will be described.

  As described above, an administrator who has the authority to access the registration server 42 can permit a general staff member to perform a specific operation on the device information table 73. The operation setting file described in a predetermined format is stored in the operation setting file folder 42a of the registration server 42.

  The operation setting file prepared at this time is described in the XML format. Access to this operation setting file is related to the query for executing the operation to be permitted, the user name of the general employee who is permitted or not permitted when restricting the general staff who is permitted the operation, and the operation. Information related to comments displayed on the screens 60 to 63, headings when the operations are displayed on the access screens 60 to 63, display order when the operations are displayed on the access screen 60, and execution of the operations When the input of a parameter is required, information defining the input screen 61 that prompts the input of the parameter, the file name attached to the result file created by executing the operation, and the result file are formatted For example, information specifying an XSLT style sheet is described by being sandwiched between predetermined start tags and end tags. In this operation setting file, the file name of the SQL file describing the query can be described instead of the query for executing the operation to be permitted. In this case, the administrator separately prepares an SQL file describing the query and stores it in a predetermined file folder in the execution server 44. In this operation setting file, the file name of the JSP file that defines the input screen can be described instead of the information that defines the input screen that prompts the input of parameters. In this case, the administrator separately prepares a JSP file that defines the input screen and stores it in a predetermined file folder in the registration server 42. When the administrator designates an XSLT style sheet in the operation setting file, the administrator prepares the XSLT style sheet separately and stores it in a predetermined file folder in the registration server 42.

  On the other hand, the registration server 42 checks the change in the operation setting file folder 42a and reflects it in the operation setting table 70 by executing the processing according to the flowchart shown in FIG. To do.

  That is, in step S51, the registration server 42 sets the operation setting file name field and the update date / time field of the record in which the value of the VALID field is “valid” among all the records stored in the operation setting table 70. Read all values of.

  Next, the registration server 42 repeats the following steps S52 to S57 for all operation setting files stored in the operation setting file folder 42a.

  In step S52, the registration server 42 selects one operation setting file that has not been checked among the operation setting files stored in the operation setting file folder 42a.

  Next, in step S53, the registration server 42 determines that the value of the VALID field is “valid” based on the information read in step S51, and the value of the operation setting file name field and the update date / time field. It is determined whether or not there is a record in the operation setting table 70 whose value is the same as the file name and update date / time of the operation setting file selected in step S52. If it is determined that it does not exist, the flow proceeds to step S54, and if it is determined that it exists, the flow skips steps S54 to S57.

  In step S54, the registration server 42 determines that the value of the VALID field is “valid” and the value of the operation setting file name field is selected in step S52 based on the information read in step S51. It is determined whether or not there is a record in the operation setting table 70 that is equal to the file name of the setting file but whose value in the update date / time field is different from the update date / time of the operation setting file selected in step S52. If it is determined that it exists, the flow proceeds to step S55, and if it is determined that it does not exist, the flow skips step S55 and proceeds to S56.

  In step S55, the registration server 42 sets the value of the VALID field of the record determined to exist in step S54 to “invalid”, and the flow proceeds to step S56.

  In step S56, the registration server 42 checks the format of the operation setting file selected in step S52, and if it is determined that the file is described in a predetermined format, the flow proceeds to step S57, If it is determined that the format is not described, the flow skips step S57 and proceeds.

  In step S57, the registration server 42 newly adds one record to the operation setting table 70 based on the operation setting file selected in step S52. At this time, if the JSP file specified in the operation setting file is stored in a predetermined file folder in the registration server 42, the registration server 42 compresses the JSP file and displays the JSP file field. When the information defining the input screen (access screen 61) that prompts the user to input parameters is described in the operation setting file, the JSP that defines the input screen (access screen 61) based on the information is described. Create a file, compress it, and store it in the JSP file field.

  Next, in step S58, the registration server 42 stores all records in the operation setting file folder 42a for all records in which the value of the VALID field is “valid” among all the records stored in the operation setting table 70. Check whether the operation setting file corresponding to the record exists. When a record for which no corresponding operation setting file exists is found, the value of the VALID field of the record is set to “invalid”.

  Thus, the administrator creates a new operation setting file and adds it to the operation setting file folder 42a, updates the contents of the operation setting file already stored in the operation setting file folder 42a, or By deleting the operation setting file already stored in the operation setting file folder 42a, a new operation permitted for general staff is added, and the contents of operations currently permitted for general staff are changed, or It is now possible to delete the registration of operations that are currently permitted for general employees.

<Flow of processing when general staff acquires device information from the device information table>
(Processing flow until general staff requests an operation on the device information table)
Next, a process when the general staff of the information collection center 20 acquires device information related to the air conditioning equipment 14 from the device information table 73 via the client computer 50 will be described. The process when the general staff of the service center 30 acquires device information related to the air conditioning equipment 14 from the device information table 73 via the client computer 31 is also described in the same manner. Further, in the following description, the operation setting file currently registered in the operation setting file folder 42 a enables general staff of the information collection center 20 to search and extract device information from the device information table 73. Suppose that it is for.

  When the general staff acquires the device information from the device information table 73, first, the general staff designates the URL of the display server 43 on the browser installed in the client computer 50 and accesses the display server 43. On the other hand, the display block 43a of the display server 43 requested to be accessed by the client computer 50 transmits an authentication screen to the general staff to input the user name and password to the browser, and the user sent via the authentication screen Authenticate general staff based on name and password. When the display block 43a confirms that the general staff has the authority to access the device information table 73, the display block 43a creates an access screen 60 (see FIG. 6) corresponding to the general staff and transmits it to the browser.

  When the access screen 60 is created in the display server 43, the operation setting table 70 is referred to. The display block 43a of the display server 43 displays the operation setting stored in the operation setting file field of the record in which the value of the VALID field is “valid” among all the records stored in the operation setting table 70. Check all files. Subsequently, the display block 43a determines that the value of the VALID field is “valid” in the operation setting table 70 based on the description in the tag related to the user restriction in the operation setting file and the user name sent via the authentication screen. The record corresponding to the operation permitted to the general staff who currently requests access is selected. Then, the display block 43a displays an operation selection button 102 corresponding to the record selected in this way on the access screen 60. The selected one record corresponds to one operation selection button 102 displayed on the access screen 60. Here, the button name given to the operation selection button 102 displayed on the access screen 60 and the display order of the plurality of operation selection buttons 102 on the access screen 60 are respectively a heading field and a display order field of the operation setting table 70. Is determined by referring to the value of. Thus, the access screen 60 provided by the display block 43a is created according to the general staff.

  When the general staff selects the operation selection button 102 displayed on the access screen 60 via the input device 51, information indicating that the operation selection button 102 is selected is displayed via the browser on the display server. 43.

  At this time, the display block 43a creates further access screens 61 and 62 (see FIG. 7 and FIG. 8) according to the selected operation selection button 102, and transmits them to the browser. The access screen 61 is a screen when parameter input is required to execute the selected operation, and the access screen 62 is a screen when parameter input is not required to execute the selected operation. . Specifically, when the information indicating that the operation selection button 102 has been selected is received from the client computer 50, the display block 43a reads a record corresponding to the selected operation selection button 102 from the operation setting table 70.

  Here, when a JSP file is stored in the JSP file field of the read record, the display block 43a displays an access screen 61, which is an input screen for prompting input of parameters based on the JSP file, on the browser. And accepts parameter input from general staff. On the access screen 61, an operation headline 200 corresponding to the operation selection button 102 selected by the general staff, a comment 201 related to the operation, and a text for allowing the general staff to input parameters necessary for executing the operation. An area 202 and an execution button 203 are displayed. When the general staff inputs a parameter in the text area 202 and presses the execute button 203, information indicating that is transmitted to the display block 43a together with the input parameter.

  On the other hand, when no JSP file is stored in the JSP file field of the read record, the display block 43a displays an access screen 62 that is a confirmation screen based on the JSP file stored in the display server 43 in advance. Is displayed on the browser. On the access screen 62, an operation headline 300 corresponding to the operation selection button 102 selected by the general staff, a comment 301 related to the operation, and an execution button 303 are displayed. When the general staff presses the execution button 303, information indicating that is transmitted to the display block 43a.

  Subsequently, when the display block 43a receives information indicating that the execution buttons 203 and 303 have been pressed from the client computer 50, the operation block 43b performs an operation requested by a general staff member by pressing the execution buttons 203 and 303. A corresponding record is newly created and added to the operation request table 71 of the DB server 41. In the state immediately after the record is added to the operation request table 71, “waiting for execution” is stored in the state field, and “NULL” is stored in the reason for abnormality, start time, end time, and download flag fields. In the user name field, the user name of the general employee who requested the operation is stored. Further, in the parameter field, when an operation is requested through the access screen 61, parameters input by general staff through the access screen 61 are stored, and the operation is requested through the access screen 62. In the case of “No”, “NULL” is stored.

(Processing flow when requested operation is executed for device information table)
The execution server 44 sequentially reads out the records stored in the operation request table 71 and whose status field value is “Waiting for execution”, and executes the operation corresponding to the record. Then, the execution server 44 stores the start time in the start time field of the operation request table 71 at the start of the operation, and stores “being executed” in the status field, and the end time of the operation request table 71 at the end of the operation. The end time is stored in the field, and either “normal end” or “abnormal end” is stored in the status field. At this time, if the operation ends abnormally, the estimated reason for abnormality is stored in the reason for abnormality field.

  Here, the access screen 60 shown in FIG. 6 is referred to again. The display block 43a of the display server 43 refers to the operation request table 71 updated from time to time by the execution server 44, and the general staff has requested the areas 100 and 103 on the access screen 60 in the past predetermined period. Displays the execution progress of the operation. Further, on the access screen 60, a download button 104 for requesting a general staff to download a result file created by executing the operation for the normally completed operation is displayed. The download button 104 is displayed only when the value of the download flag field in the operation request table 71 is “NULL”. When the download button is pressed by a general staff member and the result file is downloaded, the operation request table is displayed. The value of the download flag field 71 is changed to “done”.

  Furthermore, a redisplay button 101 is displayed on the access screen 60. When the redisplay button 101 is pressed by a general staff, the display block 43a refers to the operation setting table 70 and the operation request table 71. The access screen 60 is recreated. Thereby, the general staff can browse the access screen 60 based on the latest information at any time.

  The access screen 63 shown in FIG. 9 is a screen displayed on the browser when the download button 104 displayed on the access screen 60 is pressed by a general staff. On the access screen 63, the headline 400, the comment 401, the radio button 402 for allowing the general staff to select the file format (CSV format, TXT format, XML format) for downloading the result file, and the ZIP format are compressed. A check button 403 and an execution button 404 for causing a general staff to select whether or not to download in the state are displayed. When the general staff presses the execution button 404, information indicating that is transmitted to the display server 43 together with information indicating the selection status of the radio button 402 and the check button 403. Subsequently, when the execution server 44 receives these pieces of information via the display server 43, the execution server 44 prepares a result file in the file format and compression format selected by the general staff and transmits the result file to the client computer 50. When the XML format is selected by the radio button 402, the result file is transmitted together with the XSLT stylesheet stored in a predetermined file folder in the registration server 42.

<Features>
(1)
In this device information management system 1, general staff can access the device information table 73 only via the access screen 60 provided by the display block 43 a of the display server 43. The access screen 60 is automatically created by the display block 43a based on a predetermined format operation setting file created by some administrators. That is, since operations that the general staff can take on the device information table 73 are restricted by some administrators, the safety of the device information is ensured, and the administrator It is possible to easily permit a specific operation to the device information table 73.

(2)
The operation setting file that allows a general staff member to perform a specific operation on the device information table 73 includes a user name of a general staff member who wants to permit the specific operation or does not allow the specific operation. Can be described. Thereby, the administrator of the information collection center 20 and the service center 30 can restrict the operations permitted for each user.

(3)
The general staff can obtain the result file in which the device information searched and extracted from the device information table 73 is recorded in a format selected by the user from the CSV format, the TXT format, or the XML format. As a result, the general staff can easily use the downloaded device information in a general-purpose application such as Microsoft EXCEL (registered trademark), and the workability when providing services related to the maintenance of the air conditioning equipment 14 is improved. To do.

<Modification>
(1)
The server computer 40 may be composed of a single computer. In the case where the server computer 40 is composed of a plurality of computers, the roles played by the respective computers may be different from those of the above-described embodiment. For example, one computer having both the function of the registration server 42 and the function of the execution server 44 may be prepared.

(2)
The property 10, the information processing center 20, and the service center 30 may be connected not by the Internet line 6 but by another communication line such as a dedicated line.

(3)
In the above embodiment, only operations for searching and extracting the device information stored in the device information table 73 are exemplified as operations that can be performed by the general staff on the device information table 73. The type of operation is not limited to this. For example, a general staff may be allowed to update data stored in the device information table 73.

(4)
In the above embodiment, only the air conditioning facility 14 is exemplified as the device managed by the device information management system 1, but the present invention is also applicable to other types of devices such as a water heater and a lighting device.

(5)
When the operation setting table 70 is not prepared in the DB server 41 and an operation for the device information table 73 is requested, the execution server 44 directly stores the operation setting file in the operation setting file folder 42a of the registration server 42. It may be configured to read.

  Alternatively, when the operation setting file folder 42a is not prepared in the registration server 42 and an operation permitted to general staff is added, changed, or deleted, the administrator directly accesses the operation setting table 70, for example. It is good also as a structure which adds, changes, or deletes the record corresponding to operation.

  The present invention ensures the safety of device information and can easily add, change or delete operations that can be taken from the outside to the device information storage unit in which device information is stored. Is useful as a device information management system for storing device information and providing device information to the outside as needed.

The figure which shows the structure of the apparatus information management system which concerns on this invention. The figure which shows the structure in an information management center. The figure which shows the structure of an operation setting table. The figure which shows the structure of an operation request table. The flowchart which shows the registration process of operation permitted to the general staff performed in the server for registration. The figure which shows an access screen. The figure which shows an access screen. The figure which shows an access screen. The figure which shows an access screen.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Device information management system 14 Air-conditioning equipment 32, 51 Input device 42a Operation setting file folder 43a Display block 43b Operation block 44 Execution server 60 Access screen 70 Operation setting table 71 Operation request table 41 Device information table

Claims (6)

A device information management system (1) for storing device information related to a device (14) and providing the device information to the outside as needed.
A device information storage unit (73) for storing the device information;
An operation setting information storage unit (42a, 70) that stores operation setting information that enables a specific operation to be performed on the device information storage unit (73) from the outside;
An operation setting information registration unit () that allows the operation setting information to be added to the operation setting information storage unit (42a, 70), changed, or deleted from the operation setting information storage unit (42a, 70). 32, 51),
A screen creation unit that creates an access screen (60) for displaying operations that can be performed on the device information storage unit (73) from the outside with reference to the operation setting information storage unit (42a, 70). (43a),
Comprising
Device information management system (1). The specific operation is an operation of extracting at least a part of the device information from the device information storage unit (73).
The device information management system (1) according to claim 1. The operation setting information includes information associating a specific user with the specific operation,
The screen creation unit (43a) creates the access screen (60) according to a user.
The device information management system (1) according to claim 1 or 2. The operation setting information storage unit (42a, 70)
An operation setting file storage unit (42a) for storing an operation setting file describing the contents of the specific operation in a predetermined format;
An operation list storage unit (70) that stores an operation list that is created based on the operation setting file and that is a list of operations that can be performed on the device information storage unit (73) from the outside;
Have
The operation setting information registration unit (32, 51) adds, changes, or deletes the operation setting file from the operation setting file storage unit (42a) to the operation setting file storage unit (42a). Enable
The screen creation unit (43a) creates the access screen (60) with reference to the operation list storage unit (70).
The device information management system (1) according to any one of claims 1 to 3. When it is requested from the outside that at least one of the operations that can be performed on the device information storage unit (73) from the outside displayed on the access screen (60) is performed. An operation request information creating unit (43b) for creating operation request information indicating that;
An operation request information storage unit (71) in which the operation request information is stored;
With reference to the operation request information storage unit (71), an operation execution unit (44) for executing an operation requested from the outside,
Further comprising
The device information management system (1) according to any one of claims 1 to 4. The operation execution unit (44) stores information related to the execution progress of the operation corresponding to the operation request information in the operation request information storage unit (71) in association with the operation request information,
The screen creation unit (43a) refers to the operation request information storage unit (71) and generates an execution progress display screen (60) that displays the progress of the operation executed by the operation execution unit (44). To
The device information management system (1) according to claim 5.

Images