WO2019167340A1 - Report generating system and program - Google Patents

Report generating system and program Download PDF

Info

Publication number
WO2019167340A1
WO2019167340A1 PCT/JP2018/040333 JP2018040333W WO2019167340A1 WO 2019167340 A1 WO2019167340 A1 WO 2019167340A1 JP 2018040333 W JP2018040333 W JP 2018040333W WO 2019167340 A1 WO2019167340 A1 WO 2019167340A1
Authority
WO
WIPO (PCT)
Prior art keywords
maintenance
report
work
history information
information
Prior art date
Application number
PCT/JP2018/040333
Other languages
French (fr)
Japanese (ja)
Inventor
晋一郎 大谷
裕希 川野
利宏 妻鹿
横田　守真
康次 長谷川
Original Assignee
三菱電機株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機株式会社 filed Critical 三菱電機株式会社
Priority to TW108105973A priority Critical patent/TW201939381A/en
Publication of WO2019167340A1 publication Critical patent/WO2019167340A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/16—Real estate

Definitions

  • the present invention relates to a report creation system and program. In particular, it relates to the creation of reports when maintenance personnel perform maintenance work on equipment.
  • Japanese Patent Application Laid-Open No. 08-129414 Japanese Patent Laid-Open No. 10-017231 Japanese Patent Laid-Open No. 2002-089941 JP 2003-306276 A JP 2005-142754 A JP 2008-033470 A JP 2000-187699 A JP 2005-228025 A JP 2011-018124 A JP 2004-005140 A JP 2007-140954 A JP 2017-034425 A Japanese Patent No. 4873916
  • the object of the present invention is to automatically create a report by specifying the contents of maintenance work performed by maintenance personnel from maintenance work history information.
  • the report creation system includes a collection unit that collects history information related to maintenance work performed by the maintenance staff on the equipment to be managed, and a history information storage unit that stores the history information collected by the collection unit.
  • the estimation means for estimating the content of the maintenance work performed by the maintenance staff based on the history information stored in the history information storage means, and the maintenance work of the work content estimated by the estimation means has been performed.
  • a report creation means for creating a report for reporting the report.
  • Log information relating to maintenance work performed on the equipment performed by the maintenance staff recorded between logging in to the equipment management system and logging off is handled as the history information.
  • the facility management system includes a change history information storage unit that stores log information regarding changes in setting contents for the facility, and the maintenance terminal is log information regarding maintenance work for the facility performed by the maintenance staff.
  • Work history information storage means, and the estimation means performs maintenance work on the equipment performed by the maintenance staff from log information stored in the change history information storage means and work history information storage means. Log information is handled as the history information.
  • the report creation device includes the collection unit, the estimation unit, and the report creation unit, and the collection unit displays a work log corresponding to a maintenance person designated by the report creation device as the history information. It is something to collect as.
  • the report creation means is a report corresponding to the work content of the maintenance staff included in the history information
  • a report is created by applying item data included in the history information to a form.
  • an evidence document creating means for extracting history information including the item data included in the report from the history information storage means and creating an evidence document indicating the extracted history information. It is.
  • forbidden information storage means in which prohibition information related to information prohibiting publication on the evidence document is registered in advance, and the evidence document creating means is an evidence document in a state where the information prohibiting publication is not visible. Is to create.
  • work procedure information storage means for storing work procedure information indicating the work procedure of the maintenance work, and items changed by the maintenance work performed by the maintenance personnel based on the work procedure information are brought into a state before the setting change.
  • Rollback procedure manual creation means for creating a rollback procedure manual to be returned.
  • the program according to the present invention is implemented by the maintenance staff based on the history information collected by the collection means, the collection means for collecting the history information regarding the maintenance work performed by the maintenance staff on the equipment to be managed by the maintenance staff. It is intended to function as estimation means for estimating the content of maintenance work, and report creation means for creating a report for reporting that the maintenance work of the work content estimated by the estimation means has been performed.
  • the contents of the maintenance work performed by the maintenance staff can be identified from the history information of the maintenance work, and a report can be automatically created.
  • FIG. 1 is an overall configuration and a block configuration diagram showing an embodiment of a report creation system according to the present invention.
  • 2 is a hardware configuration diagram of a computer forming a report creation device 30 according to Embodiment 1.
  • FIG. 6 is a diagram illustrating an example of a data configuration of change history information accumulated in a change history DB according to Embodiment 1.
  • FIG. 3 is a flowchart showing a report creation process in the first embodiment. 6 is a diagram illustrating an example of history information collected in the first embodiment.
  • FIG. 3 is a diagram showing a part of a report created in Embodiment 1.
  • FIG. FIG. 10 is a block configuration diagram of a report creation device in a second embodiment. 10 is a flowchart showing evidence creation processing according to the second embodiment.
  • FIG. 10 is a block configuration diagram of a report creation device in a third embodiment.
  • FIG. 10 is a block configuration diagram of a report creation apparatus in a fourth embodiment.
  • 14 is a flowchart showing a rollback procedure manual creation process in the fourth embodiment.
  • FIG. 1 is an overall configuration and a block configuration diagram showing an embodiment of a report creation system according to the present invention.
  • FIG. 1 shows a configuration in which the facility management system 10, the maintenance terminal 20, and the report creation apparatus 30 are connected via the network 2.
  • the equipment management system 10 is a system built in a building where equipment to be maintained is installed, and is a system for managing customer equipment.
  • the facility is, for example, a building facility that requires maintenance work such as an air conditioning facility or a lighting facility.
  • the maintenance terminal 20 is a terminal device used when maintenance personnel perform maintenance work such as setting changes and defect corrections on equipment. It is carried when maintenance personnel visit the site to perform maintenance work.
  • the maintenance terminal 20 is connected to the facility management system 10 via the network 2 when performing maintenance work from a remote location.
  • the report creation device 30 is a device that collects a history of maintenance work from the facility management system 10 or the maintenance terminal 20 and creates a report.
  • FIG. 1 shows a configuration in which one unit is connected.
  • FIG. 2 is a hardware configuration diagram of a computer forming the report creating apparatus 30 in the present embodiment.
  • the computer forming the report creating apparatus 30 in the present embodiment can be realized by a general-purpose hardware configuration such as a personal computer (PC). That is, the report creation apparatus 30 connects the CPU 51, ROM 52, RAM 53, hard disk drive (HDD) 54, input / output controller 58, and network interface (IF) 59 to the internal bus 60 as shown in FIG. Composed.
  • the input / output controller 58 connects a mouse 55 and a keyboard 56 provided as input means and a display 57 provided as display means.
  • a network interface (IF) 59 is provided as a communication means.
  • the hardware configuration may be the same as in FIG.
  • the maintenance terminal 20 is required to have portability, and accordingly, the user interface (input means and display means) may be slightly different, such as being configured with a touch panel.
  • the configuration may be the same as in FIG.
  • the facility management system 10 in the present embodiment includes a communication processing unit 11, a facility management unit 12, a document processing unit 13, and a change history database (DB) 14. Note that components not used in the description of the present embodiment are omitted from the drawings.
  • the communication processing unit 11 communicates with the maintenance terminal 20 and the report creation device 30.
  • the facility management unit 12 manages the entire facility installed in the building. When the setting of the facility managed by the facility management system 10 is changed, the change history is recorded in the change history DB 14.
  • the facility management unit 12 transmits change history information to the report creation device 30 via the communication processing unit 11 in response to a request from the report creation device 30.
  • the document processing unit 13 performs document processing such as display and printing of a document such as a report sent from the report creation apparatus 30.
  • FIG. 3 is a diagram showing an example of the data structure of the change history information stored in the change history DB 14 in the present embodiment.
  • the change history information is log information related to the change of the setting content for the equipment, but not only the change content but also information related to all events such as operation and processing accompanying the change is recorded in the change history DB 14 as the change history information.
  • the change history information includes “date and time”, “signal ID”, “signal name”, “operation content”, “details”, and “user ID”. “Date and time” is information indicating the date and time when an event occurs (when an operation, processing, or the like is performed).
  • “Signal ID” is identification information for identifying a signal to be operated, and “Signal name” is the name of the signal.
  • the signal is information regarding the facility, and is a control signal or a data signal.
  • the “operation content” is information indicating the content (type) of the performed operation, and the “detail” is detailed information regarding the operation content.
  • the setting value after the change is set.
  • “User ID” is information for specifying the maintenance engineer who performed the operation, and the user ID of the maintenance engineer is set. As shown in FIG. 3, item data is set only for items necessary for setting.
  • Each component 11 to 13 in the facility management system 10 is realized by a cooperative operation of a computer forming the facility management system 10 and a program operating on a CPU mounted on the computer.
  • the change history DB 14 is realized by an HDD installed in the facility management system 10. Alternatively, external storage means may be used via a network.
  • the maintenance terminal 20 includes a communication processing unit 21, a maintenance work processing unit 22, a history management unit 23, and a work history database (DB) 24. Note that components not used in the description of the present embodiment are omitted from the drawings.
  • the communication processing unit 21 performs communication with the facility management system 10 and the report creation device 30.
  • the maintenance work processing unit 22 operates when maintenance personnel perform maintenance work on equipment, and performs processing related to maintenance. The contents of the executed processing are recorded in the work history DB 24 as work history information.
  • the history management unit 23 manages work history information stored in the work history DB 24.
  • the history management unit 23 transmits work history information to the report creation device 30 via the communication processing unit 21 in response to a request from the report creation device 30.
  • the processing performed according to the operation of the maintenance staff for example, the connection processing to the equipment management system 10, the processing according to the operation by the maintenance staff, and the communication history with the equipment management system 10, etc.
  • Log information relating to maintenance work on the work is accumulated as work history information.
  • information related to the work content is set and registered in correspondence with the date and time when the work was performed, but the data items to be registered differ depending on the work content.
  • Each component 21 to 23 in the maintenance terminal 20 is realized by a cooperative operation of a computer forming the maintenance terminal 20 and a program operating on a CPU mounted on the computer.
  • the work history DB 24 is realized by an HDD mounted on the maintenance terminal 20.
  • external storage means may be used via a network.
  • the report creation apparatus 30 includes a communication processing unit 31, a history information collection unit 32, a work content estimation unit 33, a report creation unit 34, a document transmission unit 35, a history information database (DB) 41, and a report form database (DB). 42. Note that components not used in the description of the present embodiment are omitted from the drawings.
  • the communication processing unit 31 performs communication with the facility management system 10 and the maintenance terminal 20.
  • the history information collection unit 32 is provided as a collection unit, and collects history information related to maintenance work performed on maintenance target equipment by maintenance personnel.
  • the history information collection unit 32 collects change history information from the facility management system 10 and work history information from the maintenance terminal 20 as history information, and stores the history information in the history information DB 41.
  • the work content estimation unit 33 is provided as an estimation unit, and estimates the content of maintenance work (hereinafter also referred to as “work content”) performed by the maintenance staff based on the history information stored in the history information DB 41.
  • the report creation unit 34 is provided as a report creation unit, and creates a report that reports that the maintenance work of the work content estimated by the work content estimation unit 33 has been performed.
  • the document transmission unit 35 transmits a document created by the report creation device 30, that is, a report in the case of the present embodiment, to the facility management system 10 via the communication processing unit 31.
  • the history information DB 41 is a history information storage unit that stores history information collected by the history information collection unit 32.
  • the report creation unit 34 creates a report by applying the item data included in the history information to the report form corresponding to the content of the maintenance work performed by the maintenance staff.
  • the report form DB 42 This is a report form storage means for storing a fixed form (report form) of a report used for report creation by the report creation unit 34. A report form is prepared in advance for each maintenance work.
  • Each component 31 to 35 in the report creating apparatus 30 is realized by a cooperative operation of a computer that forms the report creating apparatus 30 and a program that operates on a CPU 51 mounted on the computer.
  • the DBs 41 and 42 are realized by the HDD 54 mounted on the report creation apparatus 30.
  • external storage means may be used via a network.
  • the program used in this embodiment can be provided not only by communication means but also by storing it in a computer-readable recording medium such as a CD-ROM or USB memory.
  • the program provided from the communication means or the recording medium is installed in the computer, and various processes are realized by the CPU of the computer sequentially executing the program.
  • the maintenance staff does the maintenance work on the equipment installed in the building from the office where the report creation apparatus 30 is installed without visiting the site. That is, when performing remote maintenance, the maintenance staff logs in to the maintenance terminal 20, connects to the equipment management system 10 via the network 2, and further logs in to the equipment management system 10.
  • the work history DB 24 of the maintenance terminal 20 records such connection history and operation history with the equipment management system 10.
  • the maintenance worker activates the maintenance work processing unit 22 by performing a predetermined operation, and starts the maintenance work.
  • the maintenance work processing unit 22 performs maintenance such as changing the set value for the equipment according to the operation of the maintenance staff.
  • the operation history DB 24 of the maintenance terminal 20 records such an operation history and a disconnection history with the equipment management system 10. In addition, a history of maintenance work performed after connection to the facility management system 10 and disconnection is also recorded in the work history DB 24.
  • the first log information (change history information) of maintenance work by a series of operations is the change history information of the operation content “login”
  • the last log information (change (History information) is change history information of the operation content “log off”.
  • the maintenance staff When the maintenance staff finishes the maintenance work, the maintenance staff prepares a report to report to the customer that the maintenance work has been performed and the details of the work. For this purpose, the maintenance staff logs in to the report creation apparatus 30. This may be logged in via the network 2 from the maintenance terminal 20 or directly logged in to the report creation apparatus 30.
  • the report creation processing in the present embodiment will be described with reference to the flowchart shown in FIG.
  • the report creation process in this embodiment is started.
  • the history information collection unit 32 first collects history information from the facility management system 10 and the maintenance terminal 20 (step 101). Specifically, change history information and work history information including the user ID of the maintenance person who has logged into the report creation apparatus 30 are collected as history information.
  • FIG. 5 shows an example of history information collected by the history information collection unit 32, that is, history information related to the maintenance work most recently performed by the maintenance staff.
  • the history information collected by the history information collection unit 32 is a change history of a maintenance person who has logged into the report creation apparatus 30 (in this example, a maintenance person whose user ID is “user A”).
  • the operation content of the first record is “login”, and the operation content of the last record is “logoff”.
  • FIG. 5 shows only the change history information for convenience, and the work history information is omitted.
  • the work history information is included in the history information
  • the first record of the history information when arranged in chronological order is the work history information indicating the connection with the equipment management system 10
  • the last record is the equipment management system 10. It can be estimated that the work history information indicates the disconnection.
  • the facility management system 10 and the maintenance terminal 20 are described as collection destinations of history information.
  • other equipment such as a communication device (gateway) that relays communication is related to maintenance work. Information to be collected may be collected.
  • a maintenance person who has performed maintenance work creates a report by himself. That is, the user who has logged into the report creation apparatus 30 is a maintenance worker who has performed maintenance work, and collects history information corresponding to the user ID of the maintenance worker.
  • the report creation process may be performed by another person such as an administrator.
  • the user ID of the maintenance worker who actually performed the maintenance work is input and designated. If it is an administrator etc., it is thought that it has grasped
  • the work content estimation unit 33 estimates the content of the maintenance work performed on the equipment based on the collected history information (step 102).
  • the item “operation content” included in the history information includes a character string that can identify the maintenance work performed by the maintenance personnel. According to the setting example shown in FIG. 5, the history information including “execution schedule setting” corresponds to this.
  • the operation content (character string) that can specify the maintenance work is set in advance in a storage means that can be referred to by the work content estimation unit 33, or is defined in advance in the work content estimation unit 33, for example. In this embodiment, even if the content of the maintenance work performed by the maintenance staff is not clear in this way, the content of the maintenance work can be specified by estimation by referring to the history information.
  • the work content estimation unit 33 estimates the content of the maintenance work performed on the equipment based on the history information.
  • the history information referred to this estimation is history information corresponding to the maintenance worker who performed the maintenance work, and the operation content is history information from login to logoff.
  • such history information is narrowed down when the history information collection unit 32 collects information.
  • the present invention is not limited to this.
  • the history information collection unit 32 collects log information related to all maintenance work such as uncollected change history information and work history information, and the history information that the work content estimation unit 33 refers to when estimating the content of maintenance work. You may make it narrow down.
  • the report form DB 42 has a standard report form for each work content. Therefore, when the content of the maintenance work (work content) is estimated, the report creation unit 34 performs the work. A report form corresponding to the content is read out and acquired from the report form DB 42 (step 103). Then, the report creation unit 34 creates a report by applying the item data included in the history information to the acquired report form (step 104). Based on the history information shown in FIG. 5, the work start time is specified by the history information of the operation content “login”, and the work end time is specified by the history information of the operation content “log off”.
  • the work content is specified by the operation content “execution schedule setting”, but the target of operation is the signal ID “A12345”, and the content of the setting of the execution schedule is detailed from “Tuesday 15:00 to ON” Each is identified.
  • the item data of the items included in the history information is extracted and applied to a predetermined area of the report form, thereby completing the report.
  • a part of the prepared report is shown in FIG.
  • the document transmission unit 35 transmits the report to the equipment management system 10 installed in the building where the equipment to be maintained is located (step 105).
  • Presentation of the report to the customer is not limited to transmission by electronic data, and other means such as sending a printed matter may be used.
  • a report that reports that the maintenance work has been performed can be automatically created and provided to the customer.
  • the content of the maintenance work can be specified by estimation by referring to the history information.
  • a report can be automatically created for unsteady maintenance work that is not scheduled in advance.
  • Embodiment 2 a report is created by executing the report creation process, and can be presented to a customer even from a remote location.
  • the maintenance staff performs the maintenance work without visiting the site (building), in other words, the maintenance work is not performed in front of the customer, so the customer received the report.
  • the site building
  • the maintenance work is not performed in front of the customer, so the customer received the report.
  • the present embodiment is characterized by providing a function of creating evidence in order to eliminate such doubts.
  • “Evidence” is a document for proving whether maintenance work has actually been performed. Since the change history information and the work history information are log information recorded when the maintenance work is performed, in this embodiment, the history information (change history information and work used to create the report is used. It is an evidence document that proves that the maintenance work was actually performed by showing the history information). As a result, it can be proved that the report is a document that is legitimately created based on the log information actually recorded as the maintenance work was actually performed. Become.
  • the report is basically a document that is created only once to report that the maintenance work has been carried out immediately after the completion of the maintenance work, whereas the evidence is always available after the maintenance work is finished. This document can be created any number of times.
  • FIG. 7 is a block diagram of the report creation apparatus in the present embodiment.
  • the configurations of the facility management system 10 and the maintenance terminal 20 in the present embodiment may be the same as those in the first embodiment. Further, the hardware configuration of the report creation apparatus 30 may be the same as that of the first embodiment.
  • the report creation apparatus 30 in the present embodiment has a configuration in which an evidence creation unit 36 is added to the first embodiment. In addition, the same code
  • the evidence creation unit 36 is provided as evidence document creation means, extracts history information including item data included in the report from the history information DB 41, and creates an evidence document indicating the extracted history information.
  • the evidence creating unit 36 is realized by a cooperative operation of a computer that forms the report creating apparatus 30 and a program that operates on the CPU 51 mounted on the computer.
  • the evidence creation process is executed in response to an operation instruction from an administrator or the like in response to a request from a customer. It is assumed that the created report is stored in a storage means (not shown).
  • the evidence creation unit 36 extracts the history information by analyzing the selected report and creates a report form.
  • the fitted item data is extracted (step 201).
  • the item data to be extracted includes item data that can specify the work content. If the work content can be identified from the report, the report form used to create the report can be identified. Therefore, item data can be extracted by comparing the report form with the report.
  • the evidence creation unit 36 extracts history information including the extracted item data from the history information DB 41 (step 202). Specifically, when the work start time “10:00” can be extracted by analyzing the report, the history information set at that date is extracted. Similarly, when the work end time “10:15” can be extracted, the history information set at that date is extracted. Also, history information in which the work content corresponding to the work content “A schedule has been set for the device” is set as the operation content is extracted. Also, history information in which the work content corresponding to the work content “AC1234: 2F air conditioning A is added to the control target” is set in detail is extracted. It should be noted that the history information in which the work content corresponding to the work content “Turn device on at 15:00 every Tuesday” is set in detail has already been extracted. The history information extracted by the above processing is shown in FIG.
  • the evidence creating unit 36 creates evidence including the history information extracted as described above (step 203).
  • the evidence including the extracted history information in the form of a table is created.
  • the evidence form is not limited to this, and a form is prepared for each work content as in the report. You may make it do.
  • the document transmission unit 35 transmits the evidence to the equipment management system 10 (step 204).
  • evidence is created as described above and provided to the customer.
  • the customer can confirm that the maintenance work is actually performed and that the contents of the report are valid by presenting the log information recorded by the maintenance work.
  • the history information used to create the report is presented as evidence.
  • the information presented as evidence is not limited to history information, and maintenance work is actually performed. Other information may be used as long as the information indicates that it has been broken.
  • FIG. 10 is a block configuration diagram of the report creation apparatus according to the present embodiment.
  • the configurations of the facility management system 10 and the maintenance terminal 20 in the present embodiment may be the same as those in the first embodiment. Further, the hardware configuration of the report creation apparatus 30 may be the same as that of the first embodiment.
  • the report creation apparatus 30 in the present embodiment has a configuration in which a posting prohibition database (DB) 43 is added to the second embodiment.
  • DB posting prohibition database
  • symbol is attached
  • the posting prohibition DB 43 is realized by the HDD 54 installed in the report creation apparatus 30. Alternatively, external storage means may be used via a network.
  • the posting prohibition DB 43 prohibition information related to information prohibiting posting on evidence is registered in advance.
  • the work history information recorded in the maintenance terminal 20 may include confidential information that cannot be disclosed to customers.
  • item data is extracted from the history information (work history information) according to the report form and applied, so it is easy to prevent confidential information from being posted on the report.
  • the evidence created as if the history information is reversed from the report contains confidential information that is not included in the report because the work history information is posted as it is. There is a possibility that it will end up.
  • the posting prohibition DB 43 is provided.
  • the evidence creation unit 36 creates the evidence in a state where the information prohibited from posting in the evidence cannot be visually recognized by referring to the posting prohibition DB 43.
  • the “invisible state” is a state in which the customer or the like cannot visually recognize the corresponding information.
  • the confidential information is not included in the evidence, that is, the evidence is created in a state where the corresponding information is deleted.
  • the relevant information is blurred or partially lost and included in the evidence in an invisible state. If it is a string, include it in the evidence in an unreadable state. If confidential information is included in a predetermined frame, the inside of the frame may be masked.
  • “prohibited information related to information prohibited from being published in evidence” is information indicating that the information is prohibited from being published in evidence.
  • the prohibition information on the information prohibiting the posting on the evidence can be said to be synonymous with the information for specifying the confidential information.
  • the email address itself that is not included may be registered in the posting prohibition DB 43, the domain after @ may be included, or the evidence of all email addresses "@" May be registered in the posting prohibition DB 43.
  • information that matches the prohibition information or a character string including the prohibition information is included in the evidence in a state where it cannot be visually recognized.
  • “Information prohibiting publication in evidence” includes a URL and a MAC address that may be included in the communication history in addition to an e-mail address. Moreover, it is not necessary to limit to a character string, and an image may be sufficient.
  • the evidence creation unit 36 in the present embodiment refers to the posting prohibition DB 43 when creating the evidence in step 202 of FIG. 8 in the second embodiment, and information to be published in the evidence is registered in the posting prohibition DB 43. If so, the information is made invisible.
  • the posting prohibition DB 43 may be set in more detail. For example, even if the character string is the same, it may be set to prohibit the posting for each item included in the history information.
  • Embodiment 4 As described above, in the maintenance work, the setting for the equipment is changed as necessary. However, there are cases where the customer desires to return the contents changed for some reason to the original settings. This embodiment is characterized in that a rollback procedure manual for responding to such a request from a customer is created.
  • FIG. 11 is a block configuration diagram of the report creation apparatus in the present embodiment.
  • the configurations of the facility management system 10 and the maintenance terminal 20 in the present embodiment may be the same as those in the first embodiment. Further, the hardware configuration of the report creation apparatus 30 may be the same as that of the first embodiment.
  • the report creation apparatus 30 in the present embodiment has a configuration in which a procedure manual creation unit 37 and a work procedure database (DB) 44 are added to the first embodiment.
  • DB 44 stores work procedure information indicating the work procedure of the maintenance work.
  • the procedure manual creation unit 37 is provided as a rollback procedure manual creation unit, and returns the setting changed by the maintenance work performed by the maintenance staff based on the work procedure information stored in the work procedure DB 44 to the state before the setting change. Create a rollback procedure.
  • the procedure manual creation unit 37 is realized by a cooperative operation of a computer that forms the report creation device 30 and a program that operates on the CPU 51 mounted on the computer.
  • the work procedure DB 44 is realized by the HDD 54 mounted on the report creation apparatus 30.
  • external storage means may be used via a network.
  • rollback procedure manual creation processing in the present embodiment will be described using the flowchart shown in FIG.
  • the rollback procedure manual creation process is executed in response to an operation instruction from an administrator or the like in response to a request from a customer. It is assumed that the created report is stored in a storage means (not shown).
  • the administrator selects a report corresponding to the maintenance work in which the setting change to be restored is performed from the generated reports according to the request from the customer.
  • the procedure manual creation unit 37 identifies the content of the maintenance work (work content) by analyzing the report selected by the administrator (step 401). Subsequently, the procedure manual creation unit 37 extracts a work procedure corresponding to the specified work content from the work procedure DB 44 (step 402). Then, based on the extracted work procedure, a rollback procedure manual showing a procedure for restoring the setting contents is created (step 403). Basically, it can be created by rearranging maintenance work procedures in reverse order.
  • the set value is set to “details” of the change history information accumulated in the change history DB 14 of the facility management system 10.
  • the setting value after the setting change can be acquired from the history information (change history information acquired from the facility management system 10) referenced when the report is created, the setting value before the setting change cannot be acquired. Therefore, the procedure manual creation unit 37 needs to acquire the setting value before the setting change by making an inquiry to the equipment management system 10.
  • the procedure manual creation unit 37 creates a procedure for returning the setting contents and creates a rollback procedure manual by acquiring the setting value before the setting change from the equipment management system 10, the document transmission is performed.
  • the unit 35 transmits the rollback procedure manual to the equipment management system 10 (step 404).
  • the customer can restore the changed settings by referring to the rollback procedure that has been sent. For this reason, the maintenance staff does not have to go to the site where the customer's building is located.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Tourism & Hospitality (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • Human Resources & Organizations (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A report generating device (30) has: a history information collection unit (32) for collecting history information relating to a maintenance operation executed for a facility to be managed by a maintenance person from a facility management system (10) and a maintenance terminal (20); an operation content estimation unit (33) for estimating the content of the maintenance operation executed by the maintenance person on the basis of the collected history information; a report form database (42) for storing a stylized form of a report prepared for each operation content; and a report generation unit (34) for generating a report by filling item data included in the history information in a report form corresponding to the content of the maintenance operation executed by the maintenance person.

Description

報告書作成システム及びプログラムReport creation system and program
　本発明は、報告書作成システム及びプログラムに関する。特に保守員が設備に対する保守作業を実施した際の報告書の作成に関する。 The present invention relates to a report creation system and program. In particular, it relates to the creation of reports when maintenance personnel perform maintenance work on equipment.
　ビル管理システムの保守では、顧客の要望に応じたシステムの設定変更作業や操作支援等の非定常の保守作業が度々発生している。従来では、顧客から連絡があると現地に訪問することによって対応していた。しかし、迅速な対応と保守作業の効率化を実現するため、近年では、現地に出向くことなく遠隔地のデータセンターや事業所から顧客のシステムにアクセスすることで保守作業を実行する遠隔保守が取り入れられている。 In building management system maintenance, non-stationary maintenance work such as system setting change work and operation support according to customer demands frequently occurs. In the past, when a customer contacted, they responded by visiting the site. However, in order to realize quick response and efficient maintenance work, in recent years, remote maintenance that performs maintenance work by accessing the customer's system from a remote data center or office without going to the site has been adopted. It has been.
　遠隔保守が終了すると、その作業内容を顧客に報告するために作業報告書を作成している。従来では、保守作業のスケジュールの作成に利用した情報を参照することで作業報告書の作成を自動化する技術が提案されている（例えば、特許文献１）。 When the remote maintenance is completed, a work report is created to report the work contents to the customer. Conventionally, a technique for automating creation of a work report by referring to information used for creating a maintenance work schedule has been proposed (for example, Patent Document 1).
特開平０８－１２９４１４号公報Japanese Patent Application Laid-Open No. 08-129414 特開平１０－０１７２３１号公報Japanese Patent Laid-Open No. 10-017231 特開２００２－０８９９４１号公報Japanese Patent Laid-Open No. 2002-089941 特開２００３－３０６２７６号公報JP 2003-306276 A 特開２００５－１４２７５４号公報JP 2005-142754 A 特開２００８－０３３４７０号公報JP 2008-033470 A 特開２０００－１８７６９９号公報JP 2000-187699 A 特開２００５－２２８０２５号公報JP 2005-228025 A 特開２０１１－０１８１２４号公報JP 2011-018124 A 特開２００４－００５１４０号公報JP 2004-005140 A 特開２００７－１４０９５４号公報JP 2007-140954 A 特開２０１７－０３４４２５号公報JP 2017-034425 A 特許第４８７３９１６号明細書Japanese Patent No. 4873916
　しかしながら、従来においては、保守作業の内容が明らかになっているのが前提で報告書を自動作成している。 However, in the past, reports have been automatically created on the assumption that the contents of maintenance work have become clear.
　本発明は、保守員が実施した保守作業の内容を保守作業の履歴情報から特定して報告書を自動作成することを目的とする。 The object of the present invention is to automatically create a report by specifying the contents of maintenance work performed by maintenance personnel from maintenance work history information.
　本発明に係る報告書作成システムは、保守員が管理対象の設備に対して実施した保守作業に関する履歴情報を収集する収集手段と、前記収集手段により収集された履歴情報を記憶する履歴情報記憶手段と、前記履歴情報記憶手段に記憶されている履歴情報に基づき前記保守員が実施した保守作業の内容を推定する推定手段と、前記推定手段により推定された作業内容の保守作業が実施されたことを報告する報告書を作成する報告書作成手段と、を有するものである。 The report creation system according to the present invention includes a collection unit that collects history information related to maintenance work performed by the maintenance staff on the equipment to be managed, and a history information storage unit that stores the history information collected by the collection unit. The estimation means for estimating the content of the maintenance work performed by the maintenance staff based on the history information stored in the history information storage means, and the maintenance work of the work content estimated by the estimation means has been performed. And a report creation means for creating a report for reporting the report.
　また、前記設備を管理する設備管理システムと、前記保守員が前記設備に対する保守作業を実施する際に用いる保守用端末と、を有し、前記推定手段は、前記保守員が前記保守用端末から前記設備管理システムにログインしてからログオフするまでの間に記録された、前記保守員が実施した前記設備に対する保守作業に関するログ情報を前記履歴情報として取り扱うものである。 And an equipment management system for managing the equipment, and a maintenance terminal used when the maintenance staff carries out maintenance work on the equipment, and the estimating means is provided by the maintenance staff from the maintenance terminal. Log information relating to maintenance work performed on the equipment performed by the maintenance staff recorded between logging in to the equipment management system and logging off is handled as the history information.
　また、前記設備管理システムは、前記設備に対する設定内容の変更に関するログ情報を記憶する変更履歴情報記憶手段を有し、前記保守用端末は、前記保守員が実施した前記設備に対する保守作業に関するログ情報を記憶する作業履歴情報記憶手段を有し、前記推定手段は、前記変更履歴情報記憶手段及び作業履歴情報記憶手段に記憶されているログ情報の中から前記保守員が実施した前記設備に対する保守作業に関するログ情報を前記履歴情報として取り扱うものである。 In addition, the facility management system includes a change history information storage unit that stores log information regarding changes in setting contents for the facility, and the maintenance terminal is log information regarding maintenance work for the facility performed by the maintenance staff. Work history information storage means, and the estimation means performs maintenance work on the equipment performed by the maintenance staff from log information stored in the change history information storage means and work history information storage means. Log information is handled as the history information.
　また、前記収集手段、前記推定手段及び前記報告書作成手段を有する報告書作成装置を有し、前記収集手段は、前記報告書作成装置で指定された保守員に該当する作業ログを前記履歴情報として収集するものである。 In addition, the report creation device includes the collection unit, the estimation unit, and the report creation unit, and the collection unit displays a work log corresponding to a maintenance person designated by the report creation device as the history information. It is something to collect as.
　また、作業内容毎に用意されている報告書フォームを記憶する報告書フォーム記憶手段を有し、前記報告書作成手段は、前記履歴情報に含まれている保守員の作業内容に対応する報告書フォームに、前記履歴情報に含まれている項目データを当てはめることで報告書を作成するものである。 In addition, it has a report form storage means for storing a report form prepared for each work content, and the report creation means is a report corresponding to the work content of the maintenance staff included in the history information A report is created by applying item data included in the history information to a form.
　また、前記報告書に含まれている前記項目データを含む履歴情報を前記履歴情報記憶手段の中から抽出し、その抽出した履歴情報を示す証拠文書を作成する証拠文書作成手段と、を有するものである。 And an evidence document creating means for extracting history information including the item data included in the report from the history information storage means and creating an evidence document indicating the extracted history information. It is.
　また、前記証拠文書への掲載を禁止する情報に関する禁止情報が予め登録されている禁止情報記憶手段を有し、前記証拠文書作成手段は、前記掲載を禁止する情報を視認できない状態にて証拠文書を作成するものである。 In addition, forbidden information storage means in which prohibition information related to information prohibiting publication on the evidence document is registered in advance, and the evidence document creating means is an evidence document in a state where the information prohibiting publication is not visible. Is to create.
　また、前記保守作業の作業手順を示す作業手順情報を記憶する作業手順情報記憶手段と、前記作業手順情報に基づき前記保守員が実施した保守作業によって設定変更された事項を設定変更前の状態に戻すロールバック手順書を作成するロールバック手順書作成手段と、を有するものである。 Also, work procedure information storage means for storing work procedure information indicating the work procedure of the maintenance work, and items changed by the maintenance work performed by the maintenance personnel based on the work procedure information are brought into a state before the setting change. Rollback procedure manual creation means for creating a rollback procedure manual to be returned.
　本発明に係るプログラムは、コンピュータを、保守員が管理対象の設備に対して実施した保守作業に関する履歴情報を収集する収集手段、前記収集手段により収集された履歴情報に基づき前記保守員が実施した保守作業の内容を推定する推定手段、前記推定手段により推定された作業内容の保守作業が実施されたことを報告する報告書を作成する報告書作成手段、として機能させるためのものである。 The program according to the present invention is implemented by the maintenance staff based on the history information collected by the collection means, the collection means for collecting the history information regarding the maintenance work performed by the maintenance staff on the equipment to be managed by the maintenance staff. It is intended to function as estimation means for estimating the content of maintenance work, and report creation means for creating a report for reporting that the maintenance work of the work content estimated by the estimation means has been performed.
　本発明によれば、保守員が実施した保守作業の内容を保守作業の履歴情報から特定して報告書を自動的に作成することができる。 According to the present invention, the contents of the maintenance work performed by the maintenance staff can be identified from the history information of the maintenance work, and a report can be automatically created.
本発明に係る報告書作成システムの一実施の形態を示した全体構成及びブロック構成図である。1 is an overall configuration and a block configuration diagram showing an embodiment of a report creation system according to the present invention. 実施の形態１における報告書作成装置３０を形成するコンピュータのハードウェア構成図である。2 is a hardware configuration diagram of a computer forming a report creation device 30 according to Embodiment 1. FIG. 実施の形態１における変更履歴ＤＢに蓄積される変更履歴情報のデータ構成の一例を示す図である。6 is a diagram illustrating an example of a data configuration of change history information accumulated in a change history DB according to Embodiment 1. FIG. 実施の形態１における報告書作成処理を示すフローチャートである。3 is a flowchart showing a report creation process in the first embodiment. 実施の形態１において収集される履歴情報の一例を示す図である。6 is a diagram illustrating an example of history information collected in the first embodiment. FIG. 実施の形態１において作成される報告書の一部を示す図である。3 is a diagram showing a part of a report created in Embodiment 1. FIG. 実施の形態２における報告書作成装置のブロック構成図である。FIG. 10 is a block configuration diagram of a report creation device in a second embodiment. 実施の形態２におけるエビデンス作成処理を示すフローチャートである。10 is a flowchart showing evidence creation processing according to the second embodiment. 実施の形態２において作成されるエビデンスの内容を示す図である。It is a figure which shows the content of the evidence produced in Embodiment 2. FIG. 実施の形態３における報告書作成装置のブロック構成図である。FIG. 10 is a block configuration diagram of a report creation device in a third embodiment. 実施の形態４における報告書作成装置のブロック構成図である。FIG. 10 is a block configuration diagram of a report creation apparatus in a fourth embodiment. 実施の形態４におけるロールバック手順書作成処理を示すフローチャートである。14 is a flowchart showing a rollback procedure manual creation process in the fourth embodiment.
　以下、図面に基づいて、本発明の好適な実施の形態について説明する。 Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.
実施の形態１．
　図１は、本発明に係る報告書作成システムの一実施の形態を示した全体構成及びブロック構成図である。図１には、設備管理システム１０、保守用端末２０及び報告書作成装置３０がネットワーク２を介して接続されている構成が示されている。 Embodiment 1 FIG.
FIG. 1 is an overall configuration and a block configuration diagram showing an embodiment of a report creation system according to the present invention. FIG. 1 shows a configuration in which the facility management system 10, the maintenance terminal 20, and the report creation apparatus 30 are connected via the network 2.
　設備管理システム１０は、保守対象の設備が設置されているビル内に構築されたシステムであって、顧客の設備を管理するシステムである。設備は、例えば、空気調和設備、照明設備等保守作業を要するビルの設備である。保守用端末２０は、保守員が設備に対して設定変更や不具合修正等の保守作業を実施する際に用いられる端末装置である。保守員が現地に訪問して保守作業を実施する場合には携行される。保守用端末２０は、遠隔地から保守作業を実施する場合には設備管理システム１０にネットワーク２を介して接続する。報告書作成装置３０は、設備管理システム１０や保守用端末２０から保守作業に関する履歴を収集し、報告書を作成する装置である。 The equipment management system 10 is a system built in a building where equipment to be maintained is installed, and is a system for managing customer equipment. The facility is, for example, a building facility that requires maintenance work such as an air conditioning facility or a lighting facility. The maintenance terminal 20 is a terminal device used when maintenance personnel perform maintenance work such as setting changes and defect corrections on equipment. It is carried when maintenance personnel visit the site to perform maintenance work. The maintenance terminal 20 is connected to the facility management system 10 via the network 2 when performing maintenance work from a remote location. The report creation device 30 is a device that collects a history of maintenance work from the facility management system 10 or the maintenance terminal 20 and creates a report.
　なお、設備管理システム１０が設置されるビルは複数存在し、また保守用端末２０は各保守員によって個々に使用される。このため、ネットワーク２には複数の設備管理システム１０及び保守用端末２０が接続されることにもなり得る。しかし、設備管理システム１０及び保守用端末２０それぞれは、以下に説明する構成を有していればよいので、図１には１台ずつ接続した構成を示している。 There are a plurality of buildings where the facility management system 10 is installed, and the maintenance terminal 20 is used individually by each maintenance staff. For this reason, a plurality of equipment management systems 10 and maintenance terminals 20 may be connected to the network 2. However, since each of the facility management system 10 and the maintenance terminal 20 only needs to have a configuration described below, FIG. 1 shows a configuration in which one unit is connected.
　図２は、本実施の形態における報告書作成装置３０を形成するコンピュータのハードウェア構成図である。本実施の形態において報告書作成装置３０を形成するコンピュータは、パーソナルコンピュータ（ＰＣ）等従前から存在する汎用的なハードウェア構成で実現できる。すなわち、報告書作成装置３０は、図２に示したようにＣＰＵ５１、ＲＯＭ５２、ＲＡＭ５３、ハードディスクドライブ（ＨＤＤ）５４、入出力コントローラ５８、及びネットワークインタフェース（ＩＦ）５９を、内部バス６０に接続して構成される。入出力コントローラ５８は、入力手段として設けられたマウス５５とキーボード５６、及び表示手段として設けられたディスプレイ５７をそれぞれ接続する。ネットワークインタフェース（ＩＦ）５９は、通信手段として設けられている。 FIG. 2 is a hardware configuration diagram of a computer forming the report creating apparatus 30 in the present embodiment. The computer forming the report creating apparatus 30 in the present embodiment can be realized by a general-purpose hardware configuration such as a personal computer (PC). That is, the report creation apparatus 30 connects the CPU 51, ROM 52, RAM 53, hard disk drive (HDD) 54, input / output controller 58, and network interface (IF) 59 to the internal bus 60 as shown in FIG. Composed. The input / output controller 58 connects a mouse 55 and a keyboard 56 provided as input means and a display 57 provided as display means. A network interface (IF) 59 is provided as a communication means.
　設備管理システム１０も同じコンピュータであることからハードウェア構成は図２と同じでよい。保守用端末２０は、携帯性が要求され、これに伴いユーザインタフェース（入力手段及び表示手段）がタッチパネルで構成されるなど若干異なるかもしれないが、同じコンピュータであることからハードウェアの基本的な構成は図２と同様でよい。 Since the equipment management system 10 is also the same computer, the hardware configuration may be the same as in FIG. The maintenance terminal 20 is required to have portability, and accordingly, the user interface (input means and display means) may be slightly different, such as being configured with a touch panel. The configuration may be the same as in FIG.
　図１に戻り、本実施の形態における設備管理システム１０は、通信処理部１１、設備管理部１２、文書処理部１３及び変更履歴データベース（ＤＢ）１４を有している。なお、本実施の形態の説明に用いない構成要素については図から省略している。通信処理部１１は、保守用端末２０や報告書作成装置３０との間の通信を行う。設備管理部１２は、ビルに設置されている設備全体を管理する。設備管理システム１０が管理している設備の設定が変更された場合、その変更履歴を変更履歴ＤＢ１４に記録する。また、設備管理部１２は、報告書作成装置３０からの要求に応じて変更履歴情報を、通信処理部１１を介して報告書作成装置３０へ送信する。文書処理部１３は、報告書作成装置３０から送られてくる報告書等の文書の表示、印刷等の文書処理を行う。 Returning to FIG. 1, the facility management system 10 in the present embodiment includes a communication processing unit 11, a facility management unit 12, a document processing unit 13, and a change history database (DB) 14. Note that components not used in the description of the present embodiment are omitted from the drawings. The communication processing unit 11 communicates with the maintenance terminal 20 and the report creation device 30. The facility management unit 12 manages the entire facility installed in the building. When the setting of the facility managed by the facility management system 10 is changed, the change history is recorded in the change history DB 14. In addition, the facility management unit 12 transmits change history information to the report creation device 30 via the communication processing unit 11 in response to a request from the report creation device 30. The document processing unit 13 performs document processing such as display and printing of a document such as a report sent from the report creation apparatus 30.
　図３は、本実施の形態における変更履歴ＤＢ１４に蓄積される変更履歴情報のデータ構成の一例を示す図である。変更履歴情報は、設備に対する設定内容の変更に関するログ情報であるが、変更内容のみならず、変更に伴う操作、処理等の全ての事象に関する情報が変更履歴情報として変更履歴ＤＢ１４に記録される。変更履歴情報には、「日時」、「信号ＩＤ」、「信号名称」、「操作内容」、「詳細」及び「ユーザＩＤ」が含まれている。「日時」は、事象が発生したとき（操作、処理等が行われたとき）の日時を示す情報である。「信号ＩＤ」は、操作対象となった信号を識別するための識別情報であり、「信号名称」は、その信号の名称である。信号は、設備に関する情報であり、制御信号又はデータ信号である。「操作内容」は、実施された操作の内容（種別）を示す情報であり、「詳細」は、当該操作内容に関する詳細な情報である。設定変更がされた場合には、その変更後の設定値が設定される。「ユーザＩＤ」は、操作をした保守員を特定するための情報であり、当該保守員のユーザＩＤが設定される。図３に示すように、項目データは設定に必要な項目のみに設定される。 FIG. 3 is a diagram showing an example of the data structure of the change history information stored in the change history DB 14 in the present embodiment. The change history information is log information related to the change of the setting content for the equipment, but not only the change content but also information related to all events such as operation and processing accompanying the change is recorded in the change history DB 14 as the change history information. The change history information includes “date and time”, “signal ID”, “signal name”, “operation content”, “details”, and “user ID”. “Date and time” is information indicating the date and time when an event occurs (when an operation, processing, or the like is performed). “Signal ID” is identification information for identifying a signal to be operated, and “Signal name” is the name of the signal. The signal is information regarding the facility, and is a control signal or a data signal. The “operation content” is information indicating the content (type) of the performed operation, and the “detail” is detailed information regarding the operation content. When the setting is changed, the setting value after the change is set. “User ID” is information for specifying the maintenance engineer who performed the operation, and the user ID of the maintenance engineer is set. As shown in FIG. 3, item data is set only for items necessary for setting.
　設備管理システム１０における各構成要素１１～１３は、設備管理システム１０を形成するコンピュータと、コンピュータに搭載されたＣＰＵで動作するプログラムとの協調動作により実現される。また、変更履歴ＤＢ１４は、設備管理システム１０に搭載されたＨＤＤにて実現される。あるいは、外部にある記憶手段をネットワーク経由で利用してもよい。 Each component 11 to 13 in the facility management system 10 is realized by a cooperative operation of a computer forming the facility management system 10 and a program operating on a CPU mounted on the computer. The change history DB 14 is realized by an HDD installed in the facility management system 10. Alternatively, external storage means may be used via a network.
　保守用端末２０は、通信処理部２１、保守作業処理部２２、履歴管理部２３及び作業履歴データベース（ＤＢ）２４を有している。なお、本実施の形態の説明に用いない構成要素については図から省略している。通信処理部２１は、設備管理システム１０や報告書作成装置３０との間の通信を行う。保守作業処理部２２は、保守員が設備に対して保守作業を実施する際に動作して保守に関連する処理を実施する。実施された処理の内容は、作業履歴情報として作業履歴ＤＢ２４に記録される。履歴管理部２３は、作業履歴ＤＢ２４に蓄積されている作業履歴情報を管理する。履歴管理部２３は、報告書作成装置３０からの要求に応じて作業履歴情報を、通信処理部２１を介して報告書作成装置３０へ送信する。 The maintenance terminal 20 includes a communication processing unit 21, a maintenance work processing unit 22, a history management unit 23, and a work history database (DB) 24. Note that components not used in the description of the present embodiment are omitted from the drawings. The communication processing unit 21 performs communication with the facility management system 10 and the report creation device 30. The maintenance work processing unit 22 operates when maintenance personnel perform maintenance work on equipment, and performs processing related to maintenance. The contents of the executed processing are recorded in the work history DB 24 as work history information. The history management unit 23 manages work history information stored in the work history DB 24. The history management unit 23 transmits work history information to the report creation device 30 via the communication processing unit 21 in response to a request from the report creation device 30.
　作業履歴ＤＢ２４には、保守員の操作に応じて実施された処理、例えば設備管理システム１０への接続処理や、保守員による操作に応じた処理、更に設備管理システム１０との通信履歴等、設備に対する保守作業に関するログ情報が作業履歴情報として蓄積される。作業履歴情報のデータ構成は、作業が実施された日時に対応させて、作業の内容に関する情報が設定登録されるが、登録されるデータ項目は作業内容によって異なる。 In the work history DB 24, the processing performed according to the operation of the maintenance staff, for example, the connection processing to the equipment management system 10, the processing according to the operation by the maintenance staff, and the communication history with the equipment management system 10, etc. Log information relating to maintenance work on the work is accumulated as work history information. In the data structure of the work history information, information related to the work content is set and registered in correspondence with the date and time when the work was performed, but the data items to be registered differ depending on the work content.
　保守用端末２０における各構成要素２１～２３は、保守用端末２０を形成するコンピュータと、コンピュータに搭載されたＣＰＵで動作するプログラムとの協調動作により実現される。また、作業履歴ＤＢ２４は、保守用端末２０に搭載されたＨＤＤにて実現される。あるいは、外部にある記憶手段をネットワーク経由で利用してもよい。 Each component 21 to 23 in the maintenance terminal 20 is realized by a cooperative operation of a computer forming the maintenance terminal 20 and a program operating on a CPU mounted on the computer. The work history DB 24 is realized by an HDD mounted on the maintenance terminal 20. Alternatively, external storage means may be used via a network.
　報告書作成装置３０は、通信処理部３１、履歴情報収集部３２、作業内容推定部３３、報告書作成部３４、文書送信部３５、履歴情報データベース（ＤＢ）４１及び報告書フォームデータベース（ＤＢ）４２を有している。なお、本実施の形態の説明に用いない構成要素については図から省略している。通信処理部３１は、設備管理システム１０や保守用端末２０との間の通信を行う。履歴情報収集部３２は、収集手段として設けられ、保守員が管理対象の設備に対して実施した保守作業に関する履歴情報を収集する。履歴情報収集部３２は、設備管理システム１０から変更履歴情報を、保守用端末２０から作業履歴情報を、それぞれ履歴情報として収集し、履歴情報ＤＢ４１に保存する。作業内容推定部３３は、推定手段として設けられ、履歴情報ＤＢ４１に記憶されている履歴情報に基づき保守員が実施した保守作業の内容（以下、「作業内容」ともいう）を推定する。報告書作成部３４は、報告書作成手段として設けられ、作業内容推定部３３により推定された作業内容の保守作業が実施されたことを報告する報告書を作成する。文書送信部３５は、報告書作成装置３０において作成された文書、すなわち本実施の形態の場合は報告書を、通信処理部３１を介して設備管理システム１０へ送信する。 The report creation apparatus 30 includes a communication processing unit 31, a history information collection unit 32, a work content estimation unit 33, a report creation unit 34, a document transmission unit 35, a history information database (DB) 41, and a report form database (DB). 42. Note that components not used in the description of the present embodiment are omitted from the drawings. The communication processing unit 31 performs communication with the facility management system 10 and the maintenance terminal 20. The history information collection unit 32 is provided as a collection unit, and collects history information related to maintenance work performed on maintenance target equipment by maintenance personnel. The history information collection unit 32 collects change history information from the facility management system 10 and work history information from the maintenance terminal 20 as history information, and stores the history information in the history information DB 41. The work content estimation unit 33 is provided as an estimation unit, and estimates the content of maintenance work (hereinafter also referred to as “work content”) performed by the maintenance staff based on the history information stored in the history information DB 41. The report creation unit 34 is provided as a report creation unit, and creates a report that reports that the maintenance work of the work content estimated by the work content estimation unit 33 has been performed. The document transmission unit 35 transmits a document created by the report creation device 30, that is, a report in the case of the present embodiment, to the facility management system 10 via the communication processing unit 31.
　履歴情報ＤＢ４１は、履歴情報収集部３２により収集された履歴情報を記憶する履歴情報記憶手段である。報告書作成部３４は、保守員が実施した保守作業の内容に対応する報告書フォームに、履歴情報に含まれている項目データを当てはめることで報告書を作成するが、報告書フォームＤＢ４２は、報告書作成部３４による報告書作成に用いられる報告書の定型フォーム（報告書フォーム）を記憶する報告書フォーム記憶手段である。報告書フォームは、保守作業の内容毎に予め用意されている。 The history information DB 41 is a history information storage unit that stores history information collected by the history information collection unit 32. The report creation unit 34 creates a report by applying the item data included in the history information to the report form corresponding to the content of the maintenance work performed by the maintenance staff. The report form DB 42 This is a report form storage means for storing a fixed form (report form) of a report used for report creation by the report creation unit 34. A report form is prepared in advance for each maintenance work.
　報告書作成装置３０における各構成要素３１～３５は、報告書作成装置３０を形成するコンピュータと、コンピュータに搭載されたＣＰＵ５１で動作するプログラムとの協調動作により実現される。また、各ＤＢ４１，４２は、報告書作成装置３０に搭載されたＨＤＤ５４にて実現される。あるいは、外部にある記憶手段をネットワーク経由で利用してもよい。 Each component 31 to 35 in the report creating apparatus 30 is realized by a cooperative operation of a computer that forms the report creating apparatus 30 and a program that operates on a CPU 51 mounted on the computer. The DBs 41 and 42 are realized by the HDD 54 mounted on the report creation apparatus 30. Alternatively, external storage means may be used via a network.
　また、本実施の形態で用いるプログラムは、通信手段により提供することはもちろん、ＣＤ－ＲＯＭやＵＳＢメモリ等のコンピュータ読み取り可能な記録媒体に格納して提供することも可能である。通信手段や記録媒体から提供されたプログラムはコンピュータにインストールされ、コンピュータのＣＰＵがプログラムを順次実行することで各種処理が実現される。 Further, the program used in this embodiment can be provided not only by communication means but also by storing it in a computer-readable recording medium such as a CD-ROM or USB memory. The program provided from the communication means or the recording medium is installed in the computer, and various processes are realized by the CPU of the computer sequentially executing the program.
　保守員は、現地に訪問せずに報告書作成装置３０が設置されている事務所からビルに設置の設備に対して保守作業を行うとする。すなわち、遠隔保守を行う場合、保守員は、保守用端末２０にログインし、設備管理システム１０とネットワーク２を介して接続し、更に設備管理システム１０にログインする。保守用端末２０の作業履歴ＤＢ２４には、このような設備管理システム１０との接続履歴や操作履歴が記録される。そして、保守員が所定の操作を行うことで保守作業処理部２２を起動し、保守作業を開始する。保守作業処理部２２は、保守員の操作に応じて設備に対して設定値の変更等の保守を実施する。 Suppose that the maintenance staff does the maintenance work on the equipment installed in the building from the office where the report creation apparatus 30 is installed without visiting the site. That is, when performing remote maintenance, the maintenance staff logs in to the maintenance terminal 20, connects to the equipment management system 10 via the network 2, and further logs in to the equipment management system 10. The work history DB 24 of the maintenance terminal 20 records such connection history and operation history with the equipment management system 10. Then, the maintenance worker activates the maintenance work processing unit 22 by performing a predetermined operation, and starts the maintenance work. The maintenance work processing unit 22 performs maintenance such as changing the set value for the equipment according to the operation of the maintenance staff.
　保守員が保守作業を終了すると、設備管理システム１０からログオフする。そして、設備管理システム１０との接続を切断する。保守用端末２０の作業履歴ＤＢ２４には、このような操作履歴や設備管理システム１０との切断履歴が記録される。また、設備管理システム１０に接続してから切断されるまでに実施された保守作業の履歴も作業履歴ＤＢ２４に記録される。 When the maintenance staff finishes the maintenance work, the facility management system 10 logs off. Then, the connection with the facility management system 10 is disconnected. The operation history DB 24 of the maintenance terminal 20 records such an operation history and a disconnection history with the equipment management system 10. In addition, a history of maintenance work performed after connection to the facility management system 10 and disconnection is also recorded in the work history DB 24.
　保守用端末２０を利用した保守作業は、一連の操作に基づき実施されるが、設備に対する一連の操作の内容は、変更履歴ＤＢ１４にも蓄積される。図３に示す変更履歴情報の登録例のように、一連の操作による保守作業の先頭のログ情報（変更履歴情報）は、操作内容“ログイン“の変更履歴情報であり、最終のログ情報（変更履歴情報）は、操作内容“ログオフ“の変更履歴情報である。 Maintenance work using the maintenance terminal 20 is performed based on a series of operations, but the contents of the series of operations on the equipment are also stored in the change history DB 14. As in the example of registration of change history information shown in FIG. 3, the first log information (change history information) of maintenance work by a series of operations is the change history information of the operation content “login”, and the last log information (change (History information) is change history information of the operation content “log off”.
　保守員は、保守作業を終了すると、保守作業を実施したこと及びその作業内容を顧客に報告するために報告書を作成する。そのために、保守員は、報告書作成装置３０にログインする。これは、保守用端末２０からネットワーク２経由でログインしてもよいし、報告書作成装置３０に直接ログインしてもよい。以下、本実施の形態における報告書作成処理について図４に示すフローチャートを用いて説明する。 When the maintenance staff finishes the maintenance work, the maintenance staff prepares a report to report to the customer that the maintenance work has been performed and the details of the work. For this purpose, the maintenance staff logs in to the report creation apparatus 30. This may be logged in via the network 2 from the maintenance terminal 20 or directly logged in to the report creation apparatus 30. Hereinafter, the report creation processing in the present embodiment will be described with reference to the flowchart shown in FIG.
　保守員が、画面表示された報告書作成ボタンを選択することで、本実施の形態における報告書作成処理は開始される。本処理が開始されると、まず、履歴情報収集部３２は、設備管理システム１０及び保守用端末２０から履歴情報を収集する（ステップ１０１）。具体的には、報告書作成装置３０にログインした保守員のユーザＩＤを含む変更履歴情報及び作業履歴情報を履歴情報として収集する。 When the maintenance staff selects the report creation button displayed on the screen, the report creation process in this embodiment is started. When this process is started, the history information collection unit 32 first collects history information from the facility management system 10 and the maintenance terminal 20 (step 101). Specifically, change history information and work history information including the user ID of the maintenance person who has logged into the report creation apparatus 30 are collected as history information.
　更に、実施された保守作業に関する変更履歴情報に絞り込むために、直近に当該保守員のユーザＩＤでログインされてからログオフされるまでの間の変更履歴情報に絞り込んで収集する。直近かどうかは、変更履歴情報に含まれる「日時」を参照すればよい。作業履歴情報に対しても同様である。履歴情報収集部３２が収集した履歴情報、すなわち、当該保守員が直近に実施した保守作業に関する履歴情報の例を図５に示す。図５に例示したように、履歴情報収集部３２により収集される履歴情報は、報告書作成装置３０にログインした保守員（この例では、ユーザＩＤが“ユーザＡ”の保守員）の変更履歴情報であって、時系列順に並べると、このうちの先頭レコードの操作内容は“ログイン”、最終レコードの操作内容は“ログオフ”となる。なお、図５には、便宜的に変更履歴情報のみを示し、作業履歴情報に関しては省略している。 Furthermore, in order to narrow down to change history information related to the maintenance work performed, the change history information from the last login with the user ID of the maintenance staff to the logoff is collected and collected. Whether it is the latest or not may be referred to “date and time” included in the change history information. The same applies to the work history information. FIG. 5 shows an example of history information collected by the history information collection unit 32, that is, history information related to the maintenance work most recently performed by the maintenance staff. As illustrated in FIG. 5, the history information collected by the history information collection unit 32 is a change history of a maintenance person who has logged into the report creation apparatus 30 (in this example, a maintenance person whose user ID is “user A”). When the information is arranged in chronological order, the operation content of the first record is “login”, and the operation content of the last record is “logoff”. FIG. 5 shows only the change history information for convenience, and the work history information is omitted.
　仮に、履歴情報に作業履歴情報が含まれるとしたならば、時系列順に並べたときの履歴情報の先頭レコードは設備管理システム１０との接続を示す作業履歴情報、最終レコードは設備管理システム１０との切断を示す作業履歴情報、と推測できる。なお、本実施の形態では、設備管理システム１０及び保守用端末２０を履歴情報の収集先として説明しているが、例えば、通信を中継する通信機器（ゲートウェイ）等その他の装置から保守作業に関連する情報を収集するようにしてもよい。 If the work history information is included in the history information, the first record of the history information when arranged in chronological order is the work history information indicating the connection with the equipment management system 10, and the last record is the equipment management system 10. It can be estimated that the work history information indicates the disconnection. In the present embodiment, the facility management system 10 and the maintenance terminal 20 are described as collection destinations of history information. However, for example, other equipment such as a communication device (gateway) that relays communication is related to maintenance work. Information to be collected may be collected.
　なお、本実施の形態では、保守作業を実施した保守員が自ら報告書を作成する場合を想定している。つまり、報告書作成装置３０にログインしたユーザは、保守作業をした保守員であって、その保守員のユーザＩＤに対応する履歴情報を収集するようにしている。ただ、報告書の作成処理を管理者等他の者が実施できるようにしてもよい。この場合、報告書作成装置３０にログインした後、報告書作成ボタンを選択させる前に、保守作業を実際に実施した保守員のユーザＩＤを入力指定させるようにする。管理者等であれば、報告書作成対象の保守作業を実施した保守員のユーザＩＤを把握していると考えられる。 In this embodiment, it is assumed that a maintenance person who has performed maintenance work creates a report by himself. That is, the user who has logged into the report creation apparatus 30 is a maintenance worker who has performed maintenance work, and collects history information corresponding to the user ID of the maintenance worker. However, the report creation process may be performed by another person such as an administrator. In this case, after logging in to the report creation apparatus 30, before selecting the report creation button, the user ID of the maintenance worker who actually performed the maintenance work is input and designated. If it is an administrator etc., it is thought that it has grasped | ascertained user ID of the maintenance worker who performed the maintenance work of report preparation object.
　続いて、作業内容推定部３３は、収集された履歴情報に基づき設備に対して実施された保守作業の内容を推定する（ステップ１０２）。履歴情報に含まれる項目「操作内容」には、保守員が実施した保守作業を特定可能な文字列が含まれている。図５に示す設定例に従うと、“実行スケジュール設定”を含む履歴情報がこれに該当する。保守作業を特定可能な操作内容（文字列）は、例えば、作業内容推定部３３が参照可能な記憶手段に予め設定したり、作業内容推定部３３の内部に予め定義したりしておく。本実施の形態においては、このように保守員が実施する保守作業の内容が明らかでない場合であっても履歴情報を参照することによって推定により保守作業の内容を特定することができる。 Subsequently, the work content estimation unit 33 estimates the content of the maintenance work performed on the equipment based on the collected history information (step 102). The item “operation content” included in the history information includes a character string that can identify the maintenance work performed by the maintenance personnel. According to the setting example shown in FIG. 5, the history information including “execution schedule setting” corresponds to this. The operation content (character string) that can specify the maintenance work is set in advance in a storage means that can be referred to by the work content estimation unit 33, or is defined in advance in the work content estimation unit 33, for example. In this embodiment, even if the content of the maintenance work performed by the maintenance staff is not clear in this way, the content of the maintenance work can be specified by estimation by referring to the history information.
　このように、作業内容推定部３３は、履歴情報に基づき設備に対して実施された保守作業の内容を推定することになる。この推定に参照する履歴情報は、保守作業を実施した保守員に対応する履歴情報であって操作内容がログインからログオフまでの履歴情報である。本実施の形態では、このような履歴情報の絞込みを履歴情報収集部３２が情報の収集時に行うようにしたが、これに限る必要はない。例えば、履歴情報収集部３２は、未収集の変更履歴情報及び作業履歴情報等あらゆる保守作業に関するログ情報を収集するようにし、作業内容推定部３３が保守作業の内容の推定時に、参照する履歴情報を絞り込むようにしてもよい。 Thus, the work content estimation unit 33 estimates the content of the maintenance work performed on the equipment based on the history information. The history information referred to this estimation is history information corresponding to the maintenance worker who performed the maintenance work, and the operation content is history information from login to logoff. In the present embodiment, such history information is narrowed down when the history information collection unit 32 collects information. However, the present invention is not limited to this. For example, the history information collection unit 32 collects log information related to all maintenance work such as uncollected change history information and work history information, and the history information that the work content estimation unit 33 refers to when estimating the content of maintenance work. You may make it narrow down.
　前述したように報告書フォームＤＢ４２には、作業内容毎に報告書の定型フォームが用意されているので、保守作業の内容（作業内容）が推定されると、報告書作成部３４は、その作業内容に対応する報告書フォームを報告書フォームＤＢ４２から読み出し取得する（ステップ１０３）。そして、報告書作成部３４は、取得した報告書フォームに、履歴情報に含まれている項目データを当てはめることで報告書を作成する（ステップ１０４）。図５に示す履歴情報に基づくと、操作内容“ログイン”の履歴情報によって作業開始時刻が特定され、操作内容“ログオフ”の履歴情報によって作業終了時刻が特定される。そして、作業内容は、前述したように操作内容“実行スケジュール設定”によって特定されるが、操作の対象は信号ＩＤ“Ａ１２３４５”、 実行スケジュールの設定の内容は詳細“火曜日１５：００～　ＯＮ”からそれぞれ特定される。このように、履歴情報に含まれている項目の項目データを抽出し、報告書フォームの所定の領域に当てはめることで、報告書は完成される。作成された報告書の一部を図６に示す。 As described above, the report form DB 42 has a standard report form for each work content. Therefore, when the content of the maintenance work (work content) is estimated, the report creation unit 34 performs the work. A report form corresponding to the content is read out and acquired from the report form DB 42 (step 103). Then, the report creation unit 34 creates a report by applying the item data included in the history information to the acquired report form (step 104). Based on the history information shown in FIG. 5, the work start time is specified by the history information of the operation content “login”, and the work end time is specified by the history information of the operation content “log off”. As described above, the work content is specified by the operation content “execution schedule setting”, but the target of operation is the signal ID “A12345”, and the content of the setting of the execution schedule is detailed from “Tuesday 15:00 to ON” Each is identified. In this manner, the item data of the items included in the history information is extracted and applied to a predetermined area of the report form, thereby completing the report. A part of the prepared report is shown in FIG.
　報告書が作成されると、文書送信部３５は、保守対象となった設備のあるビルに設置の設備管理システム１０に報告書を送信する（ステップ１０５）。顧客への報告書の提示は、電子データによる送信に限らず、印刷物を送付するなど他の手段を用いてもよい。 When the report is created, the document transmission unit 35 transmits the report to the equipment management system 10 installed in the building where the equipment to be maintained is located (step 105). Presentation of the report to the customer is not limited to transmission by electronic data, and other means such as sending a printed matter may be used.
　本実施の形態によれば、以上のようにして保守作業が実施されると、実施されたことを報告する報告書を自動的に作成して顧客に提供することができる。特に、本実施の形態においては、保守員が実施する保守作業の内容が明らかでない場合であっても履歴情報を参照することによって推定により保守作業の内容を特定することができる。これにより、予めスケジュールされていない非定常の保守作業に対しても報告書を自動的に作成することができるようになる。 According to the present embodiment, when the maintenance work is performed as described above, a report that reports that the maintenance work has been performed can be automatically created and provided to the customer. In particular, in the present embodiment, even if the content of the maintenance work performed by the maintenance staff is not clear, the content of the maintenance work can be specified by estimation by referring to the history information. As a result, a report can be automatically created for unsteady maintenance work that is not scheduled in advance.
実施の形態２．
　実施の形態１では、上記報告書作成処理を実施することによって報告書を作成し、遠隔地からでも顧客に提示できるようにした。ただ、遠隔保守の場合、保守員は、現地（ビル）に訪問することなく保守作業を実施する、換言すると顧客の目の前で保守作業を実施しないことから、顧客は、報告書を受け取ったとしても保守作業が実際に実施されたのかどうか疑念を抱く可能性もある。また、報告書の内容に疑念を抱くかもしれない。 Embodiment 2. FIG.
In the first embodiment, a report is created by executing the report creation process, and can be presented to a customer even from a remote location. However, in the case of remote maintenance, the maintenance staff performs the maintenance work without visiting the site (building), in other words, the maintenance work is not performed in front of the customer, so the customer received the report. However, there is a possibility of doubting whether the maintenance work was actually performed. You may also have doubts about the content of the report.
　そこで、本実施の形態においては、このような疑念を解消するために、エビデンスを作成する機能を提供することを特徴としている。「エビデンス」というのは、保守作業が実際に実施されたかを証明するための文書である。変更履歴情報及び作業履歴情報は、保守作業が実施されることによって記録されるログ情報であることから、本実施の形態においては、報告書の作成に用いられた履歴情報（変更履歴情報及び作業履歴情報）を示すことによって保守作業が実際に実施されたかを証明する証拠文書である。これにより、報告書が、保守作業が実際に実施されたことに伴い実際に記録されているログ情報に基づき正当に作成された文書であることも証明できるので、報告書は信用される文書となる。 Therefore, the present embodiment is characterized by providing a function of creating evidence in order to eliminate such doubts. “Evidence” is a document for proving whether maintenance work has actually been performed. Since the change history information and the work history information are log information recorded when the maintenance work is performed, in this embodiment, the history information (change history information and work used to create the report is used. It is an evidence document that proves that the maintenance work was actually performed by showing the history information). As a result, it can be proved that the report is a document that is legitimately created based on the log information actually recorded as the maintenance work was actually performed. Become.
　なお、報告書は、基本的には保守作業終了直後に保守作業を実施したことを報告するために１度だけ作成される文書であるのに対し、エビデンスは、保守作業が終了した以降はいつでも何回でも作成可能な文書である。 The report is basically a document that is created only once to report that the maintenance work has been carried out immediately after the completion of the maintenance work, whereas the evidence is always available after the maintenance work is finished. This document can be created any number of times.
　図７は、本実施の形態における報告書作成装置のブロック構成図である。なお、本実施の形態における設備管理システム１０及び保守用端末２０の構成は、実施の形態１と同じでよい。また、報告書作成装置３０のハードウェア構成も実施の形態１と同じでよい。本実施の形態における報告書作成装置３０は、実施の形態１に、エビデンス作成部３６を追加した構成を有している。なお、実施の形態１と同じ構成要素には同じ符号を付け説明を省略する。エビデンス作成部３６は、証拠文書作成手段として設けられ、報告書に含まれている項目データを含む履歴情報を履歴情報ＤＢ４１の中から抽出し、その抽出した履歴情報を示す証拠文書を作成する。エビデンス作成部３６は、報告書作成装置３０を形成するコンピュータと、コンピュータに搭載されたＣＰＵ５１で動作するプログラムとの協調動作により実現される。 FIG. 7 is a block diagram of the report creation apparatus in the present embodiment. The configurations of the facility management system 10 and the maintenance terminal 20 in the present embodiment may be the same as those in the first embodiment. Further, the hardware configuration of the report creation apparatus 30 may be the same as that of the first embodiment. The report creation apparatus 30 in the present embodiment has a configuration in which an evidence creation unit 36 is added to the first embodiment. In addition, the same code | symbol is attached | subjected to the same component as Embodiment 1, and description is abbreviate | omitted. The evidence creation unit 36 is provided as evidence document creation means, extracts history information including item data included in the report from the history information DB 41, and creates an evidence document indicating the extracted history information. The evidence creating unit 36 is realized by a cooperative operation of a computer that forms the report creating apparatus 30 and a program that operates on the CPU 51 mounted on the computer.
　次に、本実施の形態におけるエビデンス作成処理について図８に示すフローチャートを用いて説明する。エビデンス作成処理は、顧客からの要望に応じて管理者等の操作指示に応じて実行される。なお、作成済みの報告書は、図示しない記憶手段に保存されているものとする。 Next, the evidence creation processing in the present embodiment will be described using the flowchart shown in FIG. The evidence creation process is executed in response to an operation instruction from an administrator or the like in response to a request from a customer. It is assumed that the created report is stored in a storage means (not shown).
　作成された報告書の中からエビデンス作成対象の報告書が管理者等により選択されると、エビデンス作成部３６は、選択された報告書を解析することによって履歴情報から抽出して報告書フォームに当てはめた項目データを抽出する（ステップ２０１）。抽出する項目データには、作業内容を特定しうる項目データも含まれている。報告書から作業内容が特定できると、報告書の作成に用いられた報告書フォームが特定できる。従って、報告書フォームと報告書とを対比することで項目データは抽出できる。 When a report for which evidence is to be created is selected from among the created reports by an administrator or the like, the evidence creation unit 36 extracts the history information by analyzing the selected report and creates a report form. The fitted item data is extracted (step 201). The item data to be extracted includes item data that can specify the work content. If the work content can be identified from the report, the report form used to create the report can be identified. Therefore, item data can be extracted by comparing the report form with the report.
　続いて、エビデンス作成部３６は、抽出した項目データを含む履歴情報を、履歴情報ＤＢ４１の中から抽出する（ステップ２０２）。具体的には、報告書を解析することによって作業開始時刻“１０時００分”を抽出できると、その日時に設定されている履歴情報を抽出する。同様に、作業終了時刻“１０時１５分”を抽出できると、その日時に設定されている履歴情報を抽出する。また、作業内容の“機器にスケジュールを設定しました。”に対応する作業内容が操作内容に設定されている履歴情報を抽出する。また、作業内容の“ＡＣ１２３４：２Ｆ　空調Ａを制御対象に追加します。”に対応する作業内容が詳細に設定されている履歴情報を抽出する。なお、作業内容の“毎週火曜日の１５：００に機器をＯＮにします。”に対応する作業内容が詳細に設定されている履歴情報は、既に抽出済みである。以上の処理にて抽出した履歴情報を図９に示す。 Subsequently, the evidence creation unit 36 extracts history information including the extracted item data from the history information DB 41 (step 202). Specifically, when the work start time “10:00” can be extracted by analyzing the report, the history information set at that date is extracted. Similarly, when the work end time “10:15” can be extracted, the history information set at that date is extracted. Also, history information in which the work content corresponding to the work content “A schedule has been set for the device” is set as the operation content is extracted. Also, history information in which the work content corresponding to the work content “AC1234: 2F air conditioning A is added to the control target” is set in detail is extracted. It should be noted that the history information in which the work content corresponding to the work content “Turn device on at 15:00 every Tuesday” is set in detail has already been extracted. The history information extracted by the above processing is shown in FIG.
　エビデンス作成部３６は、以上のようにして抽出した履歴情報を含むエビデンスを作成する（ステップ２０３）。なお、本実施の形態では、抽出した履歴情報を表形式にて含むエビデンスを作成するようにしたが、エビデンスのフォームはこれに限る必要はなく、報告書と同様に作業内容毎にフォームを用意するようにしてもよい。 The evidence creating unit 36 creates evidence including the history information extracted as described above (step 203). In this embodiment, the evidence including the extracted history information in the form of a table is created. However, the evidence form is not limited to this, and a form is prepared for each work content as in the report. You may make it do.
　エビデンス作成部３６がエビデンスを作成すると、文書送信部３５は、そのエビデンスを設備管理システム１０へ送信する（ステップ２０４）。 When the evidence creation unit 36 creates the evidence, the document transmission unit 35 transmits the evidence to the equipment management system 10 (step 204).
　本実施の形態によれば、以上のようにしてエビデンスが作成され、顧客に提供される。顧客は、保守作業が実施されることで記録されるログ情報が提示されることで、実際に保守作業が実施されたこと、並びに報告書の記載内容が正当であること、が確認できる。 According to the present embodiment, evidence is created as described above and provided to the customer. The customer can confirm that the maintenance work is actually performed and that the contents of the report are valid by presenting the log information recorded by the maintenance work.
　なお、本実施の形態では、報告書の作成に用いられた履歴情報をエビデンスとして提示するようにしたが、エビデンスとして提示する情報は、履歴情報に限定する必要はなく、保守作業が実際に行われたことを示す情報であれば他の情報でもよい。 In this embodiment, the history information used to create the report is presented as evidence. However, the information presented as evidence is not limited to history information, and maintenance work is actually performed. Other information may be used as long as the information indicates that it has been broken.
実施の形態３．
　図１０は、本実施の形態における報告書作成装置のブロック構成図である。なお、本実施の形態における設備管理システム１０及び保守用端末２０の構成は、実施の形態１と同じでよい。また、報告書作成装置３０のハードウェア構成も実施の形態１と同じでよい。本実施の形態における報告書作成装置３０は、実施の形態２に、掲載禁止データベース（ＤＢ）４３を追加した構成を有している。なお、実施の形態２と同じ構成要素には同じ符号を付け説明を省略する。掲載禁止ＤＢ４３は、報告書作成装置３０に搭載されたＨＤＤ５４にて実現される。あるいは、外部にある記憶手段をネットワーク経由で利用してもよい。 Embodiment 3 FIG.
FIG. 10 is a block configuration diagram of the report creation apparatus according to the present embodiment. The configurations of the facility management system 10 and the maintenance terminal 20 in the present embodiment may be the same as those in the first embodiment. Further, the hardware configuration of the report creation apparatus 30 may be the same as that of the first embodiment. The report creation apparatus 30 in the present embodiment has a configuration in which a posting prohibition database (DB) 43 is added to the second embodiment. In addition, the same code | symbol is attached | subjected to the same component as Embodiment 2, and description is abbreviate | omitted. The posting prohibition DB 43 is realized by the HDD 54 installed in the report creation apparatus 30. Alternatively, external storage means may be used via a network.
　掲載禁止ＤＢ４３には、エビデンスへの掲載を禁止する情報に関する禁止情報が予め登録されている。例えば、保守用端末２０に記録される作業履歴情報には、顧客に公開できない秘匿性のある情報が含まれている場合がある。報告書を作成する際には、報告書フォームに従って履歴情報（作業履歴情報）から項目データを抽出して当てはめることから、秘匿性のある情報を報告書に掲載されないようにすることは容易である。ただ、報告書から履歴情報を逆引きするかのように作成されるエビデンスには、作業履歴情報の内容がそのまま掲載されてしまうことで、報告書に掲載されない秘匿性のある情報が含まれてしまう可能性が生じてくる。 In the posting prohibition DB 43, prohibition information related to information prohibiting posting on evidence is registered in advance. For example, the work history information recorded in the maintenance terminal 20 may include confidential information that cannot be disclosed to customers. When creating a report, item data is extracted from the history information (work history information) according to the report form and applied, so it is easy to prevent confidential information from being posted on the report. . However, the evidence created as if the history information is reversed from the report contains confidential information that is not included in the report because the work history information is posted as it is. There is a possibility that it will end up.
　そこで、本実施の形態においては、掲載禁止ＤＢ４３を設けるようにした。本実施の形態におけるエビデンス作成部３６は、掲載禁止ＤＢ４３を参照することによってエビデンスへの掲載が禁止されている情報を視認できない状態にてエビデンスを作成する。「視認できない状態」というのは、顧客等が、該当する情報を視認できない状態である。具体的には、秘匿性のある情報をエビデンスに含めない、すなわち該当する情報を削除した状態でエビデンスを作成する。あるいは、該当する情報をぼやかしたり、一部を欠損させたりして、視認できない状態でエビデンスに含める。文字列であれば判読できない状態にてエビデンスに含める。秘匿性のある情報が所定の枠内に含まれるのであれば、その枠内をマスキングするなどしてもよい。 Therefore, in this embodiment, the posting prohibition DB 43 is provided. The evidence creation unit 36 according to the present embodiment creates the evidence in a state where the information prohibited from posting in the evidence cannot be visually recognized by referring to the posting prohibition DB 43. The “invisible state” is a state in which the customer or the like cannot visually recognize the corresponding information. Specifically, the confidential information is not included in the evidence, that is, the evidence is created in a state where the corresponding information is deleted. Alternatively, the relevant information is blurred or partially lost and included in the evidence in an invisible state. If it is a string, include it in the evidence in an unreadable state. If confidential information is included in a predetermined frame, the inside of the frame may be masked.
　また、「エビデンスへの掲載を禁止する情報に関する禁止情報」というのは、エビデンスへの掲載禁止に該当することを示す情報である。本実施の形態の場合、エビデンスへの掲載を禁止することから、エビデンスへの掲載を禁止する情報に関する禁止情報は、秘匿性のある情報を特定するための情報と同義ということもできる。例えば、エビデンスにメールアドレスを含まないようにする場合、含めないメールアドレスそのものを掲載禁止ＤＢ４３に登録するようにしてもよいし、＠以降のドメインを含めてもよいし、全てのメールアドレスのエビデンスの掲載を禁止するのであれば“＠”を掲載禁止ＤＢ４３に登録するようにしてもよい。これにより、禁止情報に合致する情報、あるいは禁止情報を含む文字列は、視認できない状態でエビデンスに含まれることになる。 In addition, “prohibited information related to information prohibited from being published in evidence” is information indicating that the information is prohibited from being published in evidence. In the case of the present embodiment, since the posting on the evidence is prohibited, the prohibition information on the information prohibiting the posting on the evidence can be said to be synonymous with the information for specifying the confidential information. For example, when an email address is not included in the evidence, the email address itself that is not included may be registered in the posting prohibition DB 43, the domain after @ may be included, or the evidence of all email addresses "@" May be registered in the posting prohibition DB 43. As a result, information that matches the prohibition information or a character string including the prohibition information is included in the evidence in a state where it cannot be visually recognized.
　「エビデンスへの掲載を禁止する情報」としては、メールアドレスの他にＵＲＬや、通信履歴に含まれることになるかもしれないＭＡＣアドレス等である。また、文字列に限定する必要はなく画像でもよい。 “Information prohibiting publication in evidence” includes a URL and a MAC address that may be included in the communication history in addition to an e-mail address. Moreover, it is not necessary to limit to a character string, and an image may be sufficient.
　本実施の形態におけるエビデンス作成部３６は、実施の形態２における図８のステップ２０２においてエビデンスを作成する際、掲載禁止ＤＢ４３を参照し、エビデンスに掲載しようとする情報が掲載禁止ＤＢ４３に登録されている場合、その情報を視認できない状態にする。 The evidence creation unit 36 in the present embodiment refers to the posting prohibition DB 43 when creating the evidence in step 202 of FIG. 8 in the second embodiment, and information to be published in the evidence is registered in the posting prohibition DB 43. If so, the information is made invisible.
　本実施の形態によれば、秘匿性のある情報を顧客に公開せずにすむ。なお、掲載禁止ＤＢ４３には、より詳細に設定してもよい。例えば、同じ文字列であっても履歴情報に含まれる項目毎に掲載の禁止の是非を設定するようにしてもよい。 According to this embodiment, confidential information need not be disclosed to customers. The posting prohibition DB 43 may be set in more detail. For example, even if the character string is the same, it may be set to prohibit the posting for each item included in the history information.
実施の形態４．
　前述したように、保守作業では、必要に応じて設備に対する設定を変更する。ただ、顧客が何らかの理由により設定変更した内容を元の設定に戻したいと要望する場合がある。本実施の形態は、このような顧客からの要望に応えるためのロールバック手順書を作成することを特徴としている。 Embodiment 4 FIG.
As described above, in the maintenance work, the setting for the equipment is changed as necessary. However, there are cases where the customer desires to return the contents changed for some reason to the original settings. This embodiment is characterized in that a rollback procedure manual for responding to such a request from a customer is created.
　図１１は、本実施の形態における報告書作成装置のブロック構成図である。なお、本実施の形態における設備管理システム１０及び保守用端末２０の構成は、実施の形態１と同じでよい。また、報告書作成装置３０のハードウェア構成も実施の形態１と同じでよい。本実施の形態における報告書作成装置３０は、実施の形態１に、手順書作成部３７及び作業手順データベース（ＤＢ）４４を追加した構成を有している。なお、実施の形態１と同じ構成要素には同じ符号を付け説明を省略する。保守作業の手順は、作業内容によってほぼ同じ手順になると考えられる。作業手順ＤＢ４４には、この保守作業の作業手順を示す作業手順情報が記憶されている。手順書作成部３７は、ロールバック手順書作成手段として設けられ、作業手順ＤＢ４４に記憶されている作業手順情報に基づき保守員が実施した保守作業によって変更された設定を設定変更前の状態に戻すロールバック手順書を作成する。 FIG. 11 is a block configuration diagram of the report creation apparatus in the present embodiment. The configurations of the facility management system 10 and the maintenance terminal 20 in the present embodiment may be the same as those in the first embodiment. Further, the hardware configuration of the report creation apparatus 30 may be the same as that of the first embodiment. The report creation apparatus 30 in the present embodiment has a configuration in which a procedure manual creation unit 37 and a work procedure database (DB) 44 are added to the first embodiment. In addition, the same code | symbol is attached | subjected to the same component as Embodiment 1, and description is abbreviate | omitted. The procedure of maintenance work is considered to be almost the same depending on the work content. The work procedure DB 44 stores work procedure information indicating the work procedure of the maintenance work. The procedure manual creation unit 37 is provided as a rollback procedure manual creation unit, and returns the setting changed by the maintenance work performed by the maintenance staff based on the work procedure information stored in the work procedure DB 44 to the state before the setting change. Create a rollback procedure.
　手順書作成部３７は、報告書作成装置３０を形成するコンピュータと、コンピュータに搭載されたＣＰＵ５１で動作するプログラムとの協調動作により実現される。作業手順ＤＢ４４は、報告書作成装置３０に搭載されたＨＤＤ５４にて実現される。あるいは、外部にある記憶手段をネットワーク経由で利用してもよい。 The procedure manual creation unit 37 is realized by a cooperative operation of a computer that forms the report creation device 30 and a program that operates on the CPU 51 mounted on the computer. The work procedure DB 44 is realized by the HDD 54 mounted on the report creation apparatus 30. Alternatively, external storage means may be used via a network.
　次に、本実施の形態におけるロールバック手順書作成処理について図１２に示すフローチャートを用いて説明する。ロールバック手順書作成処理は、顧客からの要望に応じて管理者等の操作指示に応じて実行される。なお、作成済みの報告書は、図示しない記憶手段に保存されているものとする。 Next, rollback procedure manual creation processing in the present embodiment will be described using the flowchart shown in FIG. The rollback procedure manual creation process is executed in response to an operation instruction from an administrator or the like in response to a request from a customer. It is assumed that the created report is stored in a storage means (not shown).
　管理者は、顧客からの要望に応じて、作成された報告書の中から元に戻したい設定変更を実施した保守作業に対応する報告書を選択する。手順書作成部３７は、管理者により選択された報告書を解析することによって保守作業の内容（作業内容）を特定する（ステップ４０１）。続いて、手順書作成部３７は、特定した作業内容に対応する作業手順を作業手順ＤＢ４４の中から抽出する（ステップ４０２）。そして、抽出した作業手順に基づき、設定内容を元に戻すための手順を示すロールバック手順書を作成する（ステップ４０３）。基本的には、保守作業の作業手順を逆の順番に並べ替えることで作成できる。 The administrator selects a report corresponding to the maintenance work in which the setting change to be restored is performed from the generated reports according to the request from the customer. The procedure manual creation unit 37 identifies the content of the maintenance work (work content) by analyzing the report selected by the administrator (step 401). Subsequently, the procedure manual creation unit 37 extracts a work procedure corresponding to the specified work content from the work procedure DB 44 (step 402). Then, based on the extracted work procedure, a rollback procedure manual showing a procedure for restoring the setting contents is created (step 403). Basically, it can be created by rearranging maintenance work procedures in reverse order.
　なお、設定値は、設備管理システム１０の変更履歴ＤＢ１４に蓄積されている変更履歴情報の「詳細」に設定されている。報告書の作成時に参照した履歴情報（設備管理システム１０から取得した変更履歴情報）から設定変更後の設定値は取得できるが、設定変更前の設定値は取得できない。そのため、手順書作成部３７は、設備管理システム１０に問い合わせることによって設定変更前の設定値を取得する必要がある。 The set value is set to “details” of the change history information accumulated in the change history DB 14 of the facility management system 10. Although the setting value after the setting change can be acquired from the history information (change history information acquired from the facility management system 10) referenced when the report is created, the setting value before the setting change cannot be acquired. Therefore, the procedure manual creation unit 37 needs to acquire the setting value before the setting change by making an inquiry to the equipment management system 10.
　このようにして、手順書作成部３７が、設定内容を元に戻す手順を作成し、また設備管理システム１０から設定変更前の設定値を取得することでロールバック手順書を作成すると、文書送信部３５は、そのロールバック手順書を設備管理システム１０へ送信する（ステップ４０４）。 In this way, when the procedure manual creation unit 37 creates a procedure for returning the setting contents and creates a rollback procedure manual by acquiring the setting value before the setting change from the equipment management system 10, the document transmission is performed. The unit 35 transmits the rollback procedure manual to the equipment management system 10 (step 404).
　顧客は、送信されてきたロールバック手順書を参照することで、変更された設定を元に戻すことができる。このため、保守員は、顧客のビルのある現地へ出向かなくて済むようになる。 The customer can restore the changed settings by referring to the rollback procedure that has been sent. For this reason, the maintenance staff does not have to go to the site where the customer's building is located.
　上記各実施の形態においては、それぞれ特徴とする構成要素及びその動作について説明したが、これらの構成を適宜組み合わせて構成してもよい。 In each of the above-described embodiments, characteristic components and their operations have been described, but these configurations may be combined as appropriate.
　２　ネットワーク、１０　設備管理システム、１１，２１，３１　通信処理部、１２　設備管理部、１３　文書処理部、１４　変更履歴データベース（ＤＢ）、２０　保守用端末、２２　保守作業処理部、２３　履歴管理部、２４　作業履歴データベース（ＤＢ）、３０　報告書作成装置、３２　履歴情報収集部、３３　作業内容推定部、３４　報告書作成部、３５　文書送信部、３６　エビデンス作成部、３７　手順書作成部、４１　履歴情報データベース（ＤＢ）、４２　報告書フォームデータベース（ＤＢ）、４３　掲載禁止データベース（ＤＢ）、４４　作業手順データベース（ＤＢ）、５１　ＣＰＵ、５２　ＲＯＭ、５３　ＲＡＭ、５４　ハードディスクドライブ（ＨＤＤ）、５５　マウス、５６　キーボード、５７　ディスプレイ、５８　入出力コントローラ、５９　ネットワークインタフェース（ＩＦ）、６０　内部バス。 2 network, 10 equipment management system, 11, 21, 31 communication processing section, 12 equipment management section, 13 document processing section, 14 change history database (DB), 20 maintenance terminal, 22 maintenance work processing section, 23 history management section , 24 work history database (DB), 30 report creation device, 32 history information collection unit, 33 work content estimation unit, 34 report creation unit, 35 document transmission unit, 36 evidence creation unit, 37 procedure manual creation unit, 41 History information database (DB), 42 report form database (DB), 43 posting prohibition database (DB), 44 work procedure database (DB), 51 CPU, 52 ROM, 53 RAM, 54 hard disk drive (HDD), 55 mouse , 56 keyboard, 57 display Lee, 58 input and output controller, 59 network interface (IF), 60 internal bus.

Claims (9)

  1. 　保守員が管理対象の設備に対して実施した保守作業に関する履歴情報を収集する収集手段と、
    　前記収集手段により収集された履歴情報を記憶する履歴情報記憶手段と、
    　前記履歴情報記憶手段に記憶されている履歴情報に基づき前記保守員が実施した保守作業の内容を推定する推定手段と、
    　前記推定手段により推定された作業内容の保守作業が実施されたことを報告する報告書を作成する報告書作成手段と、
    　を有する報告書作成システム。     A collection means for collecting history information on maintenance work performed by the maintenance staff on the equipment to be managed;
    History information storage means for storing history information collected by the collecting means;
    Estimating means for estimating the content of maintenance work performed by the maintenance staff based on history information stored in the history information storage means;
    A report creation means for creating a report for reporting that the maintenance work of the work content estimated by the estimation means has been performed;
    Report creation system with
  2. 　前記設備を管理する設備管理システムと、
    　前記保守員が前記設備に対する保守作業を実施する際に用いる保守用端末と、
    　を有し、
    　前記推定手段は、前記保守員が前記保守用端末から前記設備管理システムにログインしてからログオフするまでの間に記録された、前記保守員が実施した前記設備に対する保守作業に関するログ情報を前記履歴情報として取り扱う請求項１に記載の報告書作成システム。     An equipment management system for managing the equipment;
    A maintenance terminal used when the maintenance staff carries out maintenance work on the equipment;
    Have
    The estimation means includes log information relating to maintenance work performed on the equipment performed by the maintenance staff, recorded between the maintenance staff logging in to the equipment management system and logging off from the maintenance terminal. The report creation system according to claim 1 handled as information.
  3. 　前記設備管理システムは、前記設備に対する設定内容の変更に関するログ情報を記憶する変更履歴情報記憶手段を有し、
    　前記保守用端末は、前記保守員が実施した前記設備に対する保守作業に関するログ情報を記憶する作業履歴情報記憶手段を有し、
    　前記推定手段は、前記変更履歴情報記憶手段及び作業履歴情報記憶手段に記憶されているログ情報の中から前記保守員が実施した前記設備に対する保守作業に関するログ情報を前記履歴情報として取り扱う請求項２に記載の報告書作成システム。     The facility management system includes a change history information storage unit that stores log information related to a change in setting contents for the facility,
    The maintenance terminal has work history information storage means for storing log information related to maintenance work for the equipment performed by the maintenance staff,
    3. The estimation means handles log information related to maintenance work for the equipment performed by the maintenance staff as log information from log information stored in the change history information storage means and work history information storage means. Report creation system described in
  4. 　前記収集手段、前記推定手段及び前記報告書作成手段を有する報告書作成装置を有し、
    　前記収集手段は、前記報告書作成装置で指定された保守員に該当する作業ログを前記履歴情報として収集することを特徴とする請求項１から請求項３のいずれか１項に記載の報告書作成システム。     A report creation device having the collection means, the estimation means, and the report creation means;
    The report according to any one of claims 1 to 3, wherein the collection unit collects, as the history information, a work log corresponding to a maintenance staff designated by the report creation device. Creation system.
  5. 　作業内容毎に用意されている報告書フォームを記憶する報告書フォーム記憶手段を有し、
    　前記報告書作成手段は、前記履歴情報に含まれている保守員の作業内容に対応する報告書フォームに、前記履歴情報に含まれている項目データを当てはめることで報告書を作成する請求項１に記載の報告書作成システム。     Report form storage means for storing report forms prepared for each work content,
    2. The report creation means creates a report by applying item data included in the history information to a report form corresponding to the work contents of a maintenance worker included in the history information. Report creation system described in
  6. 　前記報告書に含まれている前記項目データを含む履歴情報を前記履歴情報記憶手段の中から抽出し、その抽出した履歴情報を示す証拠文書を作成する証拠文書作成手段と、
    　を有する請求項５に記載の報告書作成システム。     Evidence document creation means for extracting history information including the item data included in the report from the history information storage means, and creating an evidence document indicating the extracted history information;
    The report creation system according to claim 5.
  7. 　前記証拠文書への掲載を禁止する情報に関する禁止情報が予め登録されている禁止情報記憶手段を有し、
    　前記証拠文書作成手段は、前記掲載を禁止する情報を視認できない状態にて証拠文書を作成する請求項６に記載の報告書作成システム。     Prohibition information storage means in which prohibition information related to information prohibiting publication in the evidence document is registered in advance,
    The report creation system according to claim 6, wherein the evidence document creation unit creates the evidence document in a state where the information prohibiting the posting cannot be visually recognized.
  8. 　前記保守作業の作業手順を示す作業手順情報を記憶する作業手順情報記憶手段と、
    　前記作業手順情報に基づき前記保守員が実施した保守作業によって設定変更された事項を設定変更前の状態に戻すロールバック手順書を作成するロールバック手順書作成手段と、
    　を有する請求項１に記載の報告書作成システム。     Work procedure information storage means for storing work procedure information indicating a work procedure of the maintenance work;
    A rollback procedure manual creating means for creating a rollback procedure manual for returning items changed by maintenance work performed by the maintenance staff based on the work procedure information to a state before the setting change;
    The report creation system according to claim 1.
  9. 　コンピュータを、
    　保守員が管理対象の設備に対して実施した保守作業に関する履歴情報を収集する収集手段、
    　前記収集手段により収集された履歴情報に基づき前記保守員が実施した保守作業の内容を推定する推定手段、
    　前記推定手段により推定された作業内容の保守作業が実施されたことを報告する報告書を作成する報告書作成手段、
    　として機能させるためのプログラム。     Computer
    A collection means for collecting history information related to maintenance work performed on maintenance-managed equipment by maintenance personnel;
    Estimating means for estimating the content of maintenance work performed by the maintenance staff based on history information collected by the collecting means;
    A report creation means for creating a report for reporting that the maintenance work of the work content estimated by the estimation means has been performed;
    Program to function as.
PCT/JP2018/040333 2018-03-02 2018-10-30 Report generating system and program WO2019167340A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
TW108105973A TW201939381A (en) 2018-03-02 2019-02-22 Report generating system and program

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2018-037504 2018-03-02
JP2018037504A JP2019153054A (en) 2018-03-02 2018-03-02 Report creating system and program

Publications (1)

Publication Number Publication Date
WO2019167340A1 true WO2019167340A1 (en) 2019-09-06

Family

ID=67804912

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2018/040333 WO2019167340A1 (en) 2018-03-02 2018-10-30 Report generating system and program

Country Status (3)

Country Link
JP (1) JP2019153054A (en)
TW (1) TW201939381A (en)
WO (1) WO2019167340A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11143871A (en) * 1997-11-12 1999-05-28 Fuji Xerox Co Ltd Document disclosure device and medium for storing document disclosure program
WO2003001421A1 (en) * 2001-06-21 2003-01-03 Kabushiki Kaisha Toshiba Electronic report making supporting apparatus, method, and program
JP2006040194A (en) * 2004-07-30 2006-02-09 Toshiba Corp Field work management system
JP2008139985A (en) * 2006-11-30 2008-06-19 Toshiba Corp On site inspection monitoring support apparatus
JP2011065289A (en) * 2009-09-15 2011-03-31 Ricoh Co Ltd Remote management device, remote management system, improvement proposal method, improvement proposal program, and recording medium with the program recorded thereon
JP2012178074A (en) * 2011-02-28 2012-09-13 Mitsubishi Electric Corp Plant operation/maintenance terminal and record management method for plant operation/maintenance

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6156983B2 (en) * 2013-05-21 2017-07-05 Kddi株式会社 Procedure separation apparatus, method, and program for separating work history on a terminal into procedures for each job

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11143871A (en) * 1997-11-12 1999-05-28 Fuji Xerox Co Ltd Document disclosure device and medium for storing document disclosure program
WO2003001421A1 (en) * 2001-06-21 2003-01-03 Kabushiki Kaisha Toshiba Electronic report making supporting apparatus, method, and program
JP2006040194A (en) * 2004-07-30 2006-02-09 Toshiba Corp Field work management system
JP2008139985A (en) * 2006-11-30 2008-06-19 Toshiba Corp On site inspection monitoring support apparatus
JP2011065289A (en) * 2009-09-15 2011-03-31 Ricoh Co Ltd Remote management device, remote management system, improvement proposal method, improvement proposal program, and recording medium with the program recorded thereon
JP2012178074A (en) * 2011-02-28 2012-09-13 Mitsubishi Electric Corp Plant operation/maintenance terminal and record management method for plant operation/maintenance

Also Published As

Publication number Publication date
JP2019153054A (en) 2019-09-12
TW201939381A (en) 2019-10-01

Similar Documents

Publication Publication Date Title
JP4304174B2 (en) Centralized system for managing computer tests
US20130226639A1 (en) Task management method and task management apparatus
JP6452168B2 (en) Maintenance work procedure data management apparatus, system, method and program
US8484719B2 (en) Information processing apparatus, information processing method, and media storing a program therefor
EP2214109A1 (en) Network storage device collector
JP2008071242A (en) Construction site management system
JP5017174B2 (en) Method of collecting actual labor information, information processing system, management device, and information processing device
JP4900925B2 (en) Access authority management system
WO2019167340A1 (en) Report generating system and program
JP2016181022A (en) Information processing apparatus, information processing program, information processing method, and data center system
JP2019505424A (en) How to associate a location with a device
JP2002297796A (en) Inquiry type fault countermeasure support method using work flow system
JP2016115024A (en) Facility management assistance device and program
CN112693983B (en) Information display system and information display method
JP4831152B2 (en) Destination information management system, communication terminal device, and destination information management program
US20040049414A1 (en) Apparatus and method for sharing information related to a continuous process improvement project
JP6855364B2 (en) Log collection system and program
JP2013033380A (en) Software management system, management server and control method and program of software management system
JP2002351702A (en) Method and device for preparing terminal operation statistical data utilizing online
JP2000200301A (en) System for diagnozing/proposing computerization of building
JP2001147945A (en) Shop job progress monitoring device
JP5267564B2 (en) Output program, output method, output device, troubleshooting support program, troubleshooting support method, and troubleshooting support device
JP2003203145A (en) Personnel management support system and method therefor
WO2023242959A1 (en) Specifying device, specifying method, and specifying program
JP5492031B2 (en) Work management system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18907563

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18907563

Country of ref document: EP

Kind code of ref document: A1