Facility maintenance management system, facility maintenance management method, and program

Abstract

To provide a facility maintenance management system that efficiently manages the maintenance of facilities. [Solution] The facility maintenance management system in this embodiment is a facility maintenance management system that manages the tasks and cases for facility maintenance management carried out at each facility, and has a case information storage unit that stores case information related to cases that are requested by each facility and require advance budget allocation and approval for implementation, a case extraction unit that extracts the case information stored in the case information storage unit based on specified conditions, and a case display unit that displays a list of the case information extracted by the case extraction unit, and the case extraction unit extracts case information based on identification information that identifies the facility, the area to which the facility belongs, the status indicating the progress of the case, the priority of the case, the year the case is implemented, the month the case is implemented, the budget, whether the facility needs to be closed, the contractor in charge of the case, the reason the case needs to be implemented, or a combination of these.

Description

[Technical Field]

[0001] The present invention relates to a facility maintenance management system, a facility maintenance management method, and a program. [Background technology]

[0002] For example, Patent Document 1 discloses an information processing method characterized by the computer acquiring defect information related to a defect, identifying a maintenance plan corresponding to a similar defect similar to the defect, identifying a past defect based on the time of occurrence of the similar defect, and displaying past information related to the past defect and maintenance plan information related to the maintenance plan corresponding to the similar defect.

[0003] Patent Document 2 also discloses an information processing system in which an information processing device, a client terminal, and a contractor terminal are each connected to a network, and the information processing device extracts contractors who meet the request conditions for work requested from the client terminal via the network, wherein the information processing device refers to a first memory unit in which the contractor's contract conditions are stored, extracts the contractors who meet the request conditions for the work sent from the client terminal, and selects the contractors who are available to undertake the work, and a notification unit sends information about the contractors extracted by the matching unit to the client terminal, and refers to a second memory unit in which information about the client and the administrator associated with the client is stored, and notifies the administrator's terminal of the content of the information exchanged between the client and the contractor. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2024-146403 [Patent Document 2] Patent Publication No. 2021-26366 Summary of the Invention [Problem to be solved by the invention]

[0005] An object of the present invention is to efficiently perform maintenance management of facilities. [Means for solving the problem]

[0006] The facility maintenance management system of the present invention is a facility maintenance management system that manages the tasks and cases for facility maintenance management carried out at each facility, and has a case information storage unit that stores case information related to cases that are requested by each facility and require advance budget allocation and approval for implementation, a case extraction unit that extracts the case information stored in the case information storage unit based on specified conditions, and a case display unit that displays a list of the case information extracted by the case extraction unit, and the case extraction unit extracts case information based on identification information that identifies the facility, the area to which the facility belongs, the status indicating the progress of the case, the priority of the case, the year in which the case is implemented, the month in which the case is implemented, the budget, whether the facility needs to be closed, the contractor in charge of the case, the reason why the case needs to be implemented, or a combination of these.

[0007] Preferably, the system has a case information registration unit that registers case information for cases applied for by facilities, and an approval unit that associates the case information acquired by the case information registration unit with information on whether the case is approved or not and registers the information in the case information storage unit, and the case display unit associates the case information acquired by the case information registration unit with a status indicating the progress of the case and displays it.

[0008] Preferably, the system further includes a maintenance work storage unit that stores information regarding maintenance work, which is work that has been scheduled in advance, and a maintenance work registration unit that registers case information associated with information indicating that the work has been approved by the approval unit as maintenance work in the maintenance work storage unit.

[0009] Preferably, the system further includes a schedule visualization unit that graphs the schedule of case information associated with information indicating approval by the approval unit, by correlating it with the facility where the case will be performed, information identifying the case, and the period during which the case will be performed, and the case extraction unit extracts case information for facilities belonging to the specified area, and the schedule visualization unit displays a list of case schedules for facilities belonging to the specified area extracted by the case extraction unit.

[0010] Preferably, the system further comprises a repair work storage unit that stores repair work information relating to repair work, which is sudden work, in association with the area to which the facility belongs; a repair work extraction unit that extracts the repair work information stored in the repair work storage unit based on specified conditions; and a repair work display unit that displays the repair work information extracted by the repair work extraction unit, wherein the repair work extraction unit extracts repair work information based on the facility for which the repair work is to be performed, the registration date of the repair work, the subject of the repair, the cost of the repair, the status indicating the progress of the repair work, keywords, whether or not it is a recurring repair work, or a combination of these.

[0011] Preferably, the repair work extraction unit extracts repair work information for repair work that has a status indicating that the cost of repair is above a specified value and that is awaiting approval, and the repair work display unit displays the repair work information extracted by the repair work extraction unit.

[0012] Preferably, the repair work extraction unit extracts repair work information based on the content of the specified repair work, and the repair work display unit displays, by area, at least the facilities where the repair work was carried out and the costs incurred for the repair work from the repair work information extracted by the repair work extraction unit.

[0013] Preferably, the system further comprises a maintenance work extraction unit that extracts maintenance work information stored in the maintenance work storage unit based on specified conditions, and a maintenance work display unit that displays the maintenance work information extracted by the maintenance work extraction unit, and the maintenance work extraction unit extracts the maintenance work information based on the facility where the maintenance work is performed, the registration date of the maintenance work, the type of maintenance work, the frequency of the maintenance work, the year in which the maintenance work is performed, the month in which the maintenance work is performed, the content of the maintenance work, the cost of the maintenance work, the status indicating the progress of the maintenance work, keywords, or a combination of these.

[0014] Preferably, the system further comprises a maintenance work storage unit for storing maintenance work information relating to maintenance work that is work scheduled in advance, and a status monitoring unit for detecting updates to the status of the case information stored in the case information storage unit, the status of the repair work information stored in the repair work storage unit, or the status of the maintenance work information stored in the maintenance work storage unit, and a status monitoring unit for monitoring the registration date of the case information stored in the case information storage unit, the registration date of the repair work information stored in the repair work storage unit, or the number of days that have passed since the registration date of the maintenance work information stored in the maintenance work storage unit. The status monitoring unit extracts case information, repair work information, or maintenance work information for which a status update has not been detected for a specified period of time or longer, the elapsed days monitoring unit extracts case information, repair work information, or maintenance work information for which the number of days that have passed since the registration date is equal to or greater than a specified value, and the confirmation-required facility display unit further includes a confirmation-required facility display unit that displays case information, repair work information, or maintenance work information extracted by the status monitoring unit or the elapsed days monitoring unit from among cases, repair work, or maintenance work for which response has not been completed.

[0015] Preferably, the system further has a usage status display unit that displays the system usage status at each facility in association with a link connecting to the system environment of each facility, and the system usage status at the facility is the number of registered repair work or the number of registered cases at the facility.

[0016] Preferably, the system further comprises a repair work registration unit that registers the repair work information, a similar work extraction unit that extracts repair work information similar to the repair work information registered by the repair work registration unit from the repair work information stored in the repair work information storage unit based on the target of the repair and the location where the problem occurred, and a recurrence candidate display unit that displays the repair work information extracted by the similar work extraction unit as a candidate for recurring repair work.

[0017] Preferably, the system further comprises a recurrence information registration unit that associates the repair work information registered by the repair information registration unit with information on whether the repair work information extracted by the similar work extraction unit is a recurring repair work and registers the associated information in the repair work information storage unit, and a recurrence information display unit that displays the repair work information registered by the repair information registration unit in association with whether the information on the repair is a recurring repair work.

[0018] Preferably, the system further includes a recurrence work extraction unit that extracts repair work information for recurring repair work from information related to repairs stored in the repair work storage unit, and the recurrence information display unit displays a list of the repair work information extracted by the recurrence work extraction unit.

[0019] The facility maintenance management method of the present invention is a facility maintenance management method for managing tasks and projects for facility maintenance management carried out at each facility, and includes a project information storage step in which a computer stores project information related to projects that have been submitted by each facility and require advance budget allocation and approval for implementation, a project extraction step in which the computer extracts the project information stored in the project information storage step based on specified conditions, and a project display step in which the computer displays a list of the project information extracted in the project extraction step, wherein the project information is extracted in the project extraction step based on identification information that identifies the facility, the area to which the facility belongs, the status indicating the progress of the project, the priority of the project, the year in which the project is implemented, the month in which the project is implemented, the budget, whether the facility needs to be closed, the contractor in charge of the project, the reason the project needs to be implemented, or a combination of these.

[0020] The program of the present invention is a program for managing the tasks and projects for facility maintenance management carried out at each facility, and causes a computer to execute the following steps: a project information storage step for storing project information regarding projects that require advance budget allocation and approval for implementation from each facility; a project extraction step for extracting the project information stored in the project information storage step based on specified conditions; and a project display step for displaying the project information extracted in the project extraction step in a list; and in the project extraction step, project information is extracted based on identification information that identifies the facility, the area to which the facility belongs, the status indicating the progress of the project, the priority of the project, the year in which the project is implemented, the month in which the project is implemented, the budget, whether the facility needs to be closed, the contractor in charge of the project, the reason why the project needs to be implemented, or a combination of these. [Effects of the Invention]

[0021] According to the present invention, facility maintenance management can be carried out efficiently. [Brief explanation of the drawings]

[0022] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of a facility maintenance management system 1. FIG. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a store terminal 2. [Figure 3] 2 is a diagram illustrating an example of the functional configuration of a store terminal 2. FIG. [Figure 4] 1A is a diagram illustrating an example of a plan registration screen of the facility maintenance management system 1, and FIG. 1B is a diagram illustrating an example of a maintenance plan registration screen of the facility maintenance management system 1. FIG. [Figure 5] 1A is a diagram illustrating an example of a task update screen that displays candidates for recurring repair work in the facility maintenance management system 1. FIG. 1B is a diagram illustrating an example of a task search screen that displays the extraction results of recurring repair work in the facility maintenance management system 1. [Figure 6] 2 is a diagram illustrating an example of a functional configuration of a headquarters terminal 3. FIG. [Figure 7](a) is a diagram illustrating an example of a project search screen in the facility maintenance management system 1 that displays search results for planned projects, and (b) is a diagram illustrating an example of a project implementation status screen in the facility maintenance management system 1 that displays the schedule for planned projects. [Figure 8] (a) is a diagram illustrating an example of a repair task list screen in the facility maintenance management system 1, which displays a list of repair work across the stores operated by the system, and (b) is a diagram illustrating an example of a decision-making list screen in the facility maintenance management system 1, which displays a list of repair work across the stores operated by the system. [Figure 9] (a) is a diagram illustrating an example of a store implementation status screen in the facility maintenance management system 1, which displays the usage status of the facility maintenance management system 1 at each store, and (b) is a diagram illustrating an example of a maintenance task implementation status screen in the facility maintenance management system 1, which displays the schedule of maintenance work. [Figure 10] 10A is a diagram illustrating an example of a store viewing screen that displays the usage status of the facility maintenance management system 1 at each store in the facility maintenance management system 1. FIG. 10B is a diagram illustrating an example of a distribution confirmation screen that distributes maintenance plans and setting contents in the facility maintenance management system 1. [Figure 11] 10 is a table illustrating example project information stored in a project DB 600. [Figure 12] 10 is a table illustrating repair work information stored in a repair work DB 610. [Figure 13] 10 is a table illustrating an example of maintenance work information stored in a maintenance work DB 620. [Figure 14] 10 is a flowchart illustrating a management process (S10) of a planned case by the facility maintenance management system 1. [Figure 15] 10 is a flowchart illustrating the management process (S20) of a recurring task by the facility maintenance management system 1. DETAILED DESCRIPTION OF THE INVENTION

[0023] First, the background to the invention will be explained. Facility maintenance management involves unexpected repairs, regular, routine maintenance according to a set annual schedule, and large-scale projects that do not require immediate action but are budgeted for in advance and implemented this or next fiscal year, such as construction of a multi-story parking garage. Facilities identify these large-scale projects and submit them to headquarters, which then selects and approves the projects submitted by each facility. Approved projects are implemented at the facility this or next fiscal year, and headquarters monitors the implementation status of the projects and calculates estimated costs for revenue management and budget-to-actual management. However, for headquarters that operate a large number of facilities, consolidating projects from each store, monitoring the implementation status of approved projects, and calculating estimated costs from planned projects is a burden. Furthermore, discrepancies between budget and actual results are a major problem.

[0024] Furthermore, headquarters that operate multiple facilities require support to ensure that repair work, which has a significant impact on facility operations, and large-scale projects are carried out as scheduled. However, in many cases, after the headquarters has deployed implementation plans to the facilities, they are unable to consolidate and grasp the implementation status of the stores, and are therefore unable to provide appropriate support.

[0025] Furthermore, for repairs that occur again, facilities request contractors to take measures if they have records or if the person in charge remembers them, but if there are no records or memories, appropriate measures may not be taken and the symptoms may worsen. Even in facilities that manage repairs that occur again as recurring cases, numerous items on the ledger must be checked to see if similar issues have occurred, and the checking process itself is time-consuming.

[0026] In consideration of these issues, the present invention provides a facility maintenance management system that can manage large-scale spot projects at facilities, consolidate and grasp the operational status of these large-scale projects and facilities at headquarters, and further manage recurring repair work at the facilities.

[0027] Hereinafter, embodiments of the present invention will be described with reference to the drawings, but the scope of the present invention is not limited to the illustrated examples. In addition, in this embodiment, the facility is a commercial facility, and the facility maintenance management system 1 is described for multiple stores and the headquarters that operates them, but the facility in this invention is not limited to commercial facilities, and also includes hot spring facilities, leisure facilities, accommodation facilities, etc. The facility maintenance management system 1 manages the work and planning projects for store maintenance management carried out at each store operated by the headquarters. Specifically, the facility maintenance management system 1 manages the repair work, maintenance work, and planning projects carried out at each store, and the headquarters manages the work that the headquarters should carry out, grasps the implementation status of work at the stores it operates, and distributes maintenance plans to the stores. FIG. 1 is a diagram illustrating an example of the overall configuration of a facility maintenance management system 1. As shown in FIG. As shown in FIG. 1, the facility maintenance management system 1 includes a store terminal 2, a headquarters terminal 3, and a headquarters management server 4. The store terminal 2 is a computer terminal operated by a store employee who accesses the headquarters management server 4, and provides a user interface for the facility maintenance management system 1. The store employee uses the store terminal 2 to register, view, and update information related to repair work, maintenance work, and planning projects stored in the headquarters management server 4.

[0028] Here, repair work refers to work related to store repair management, such as repairing or restoring sudden breakdowns or damage to store equipment, and maintenance work refers to scheduled, regular, and routine work carried out in advance to maintain the performance of equipment and prevent breakdowns or damage. Planned projects are large-scale projects to be carried out this year or next year or later, such as construction of a multi-story parking lot, that do not require immediate response but require approval for implementation or a budget application. Planned projects are one example of projects related to the present invention. The headquarters terminal 3 is a computer terminal operated by headquarters employees who access the headquarters management server 4. Specifically, the headquarters terminal 3 provides an interface for operating the facility maintenance management system 1, and headquarters employees use the headquarters terminal 3 to view and update information related to repair work, maintenance work, and planning projects stored in the headquarters management server 4, and to distribute maintenance plans and facility maintenance management system 1 settings.

[0029] The headquarters management server 4 is a server that oversees the maintenance management of stores operated by the headquarters. Specifically, the headquarters management server 4 has a database that manages information related to repair work, maintenance work, and planned projects. Specifically, the headquarters management server 4 is configured with a planned project database 600 (planned project DB600), a repair work database 610 (repair work DB610), and a maintenance work database 620 (maintenance work DB620). The planned project DB600 is an example of a project information storage unit according to the present invention. The headquarters management server 4 may be realized by a cloud server.

[0030] FIG. 2 is a diagram illustrating an example of the hardware configuration of the store terminal 2. As shown in FIG. As shown in FIG. 2, the store terminal 2 includes a CPU 500, a memory 502, a HDD 504, a network interface 506 (network IF 506), a display device 508, and an input device 510, which are connected to one another via a bus 512. The CPU 500 is, for example, a central processing unit. The memory 502 is, for example, a volatile memory, and functions as a main storage device. The HDD 504 is, for example, a hard disk drive device, and serves as a non-volatile storage device for storing computer programs and other data files. The network IF 506 is an interface for wired or wireless communication, and realizes communication with the headquarters terminal 3 and headquarters management server 4, for example. The display device 508 is, for example, a liquid crystal display. The input device 510 is, for example, a keyboard and a mouse. The hardware configuration of the headquarters terminal 3 and the headquarters management server 4 is the same as that of the store terminal 2.

[0031] FIG. 3 is a diagram illustrating an example of the functional configuration of the store terminal 2. As shown in FIG. As shown in FIG. 3, a store terminal program 20 is installed in the store terminal 2 of this example. The store terminal program 20 has a case information registration unit 200, a maintenance work registration unit 202, a repair work registration unit 204, a similar work extraction unit 206, a recurrence candidate display unit 208, a recurrence information registration unit 210, a recurrence work extraction unit 212, and a recurrence information display unit 214. Note that part or all of the store terminal program 20 may be realized by hardware such as an ASIC. The store terminal program 20 is stored on a recording medium such as a CD-ROM, and is installed into the store terminal 2 via this recording medium.

[0032] The project information registration unit 200 submits to the headquarters planned projects to be implemented in the store this year or next year. Specifically, the project information registration unit 200 acquires application information for the planned projects entered on the planned project registration screen illustrated in FIG. 4(a) and transmits it to the headquarters management server 4. Specifically, the project information registration unit 200 registers the application information entered on the planned project registration screen as planned project information in the planned project DB 600 of the headquarters management server 4. The planned project information is an example of project information according to the present invention.

[0033] Here, the plan registration screen will be described. FIG. 4( a ) is a diagram illustrating a project registration screen of the facility maintenance management system 1. As shown in FIG. As shown in the example of FIG. 4(a), a store employee applies for a planned project from the planned project registration screen displayed on the store terminal 2. Specifically, the employee registers the details of the planned project, the priority of the planned project, whether or not the store will be closed to implement the planned project, the closure period, the implementation period of the planned project, the contractor implementing the planned project, the cost required to implement the planned project, and attached documents (e.g., an estimate for the planned project, supplementary documents for the planned project, etc.). The project information registration unit 200 detects the pressing of the register button, and associates the information entered on the planned project registration screen with information identifying the planned project, a status indicating the progress of the planned project, and area information to which the store that applied for the planned project belongs, and stores this as planned project information in the planned project DB 600.

[0034] The maintenance work registration unit 202 registers, as maintenance work, the planned cases approved by the headquarters from among the submitted planned cases in the maintenance work DB 620. Specifically, the maintenance work registration unit 202 registers, as maintenance work, planned case information associated with information indicating approval by the headquarters terminal 3 in the maintenance work DB 620. In this way, the planned cases are managed in accordance with the maintenance work management rules.

[0035] Here, a maintenance plan registration screen for registering an approved plan as a maintenance job will be described. FIG. 4(b) is a diagram illustrating an example of a maintenance plan registration screen of the facility maintenance management system 1. As shown in Figure 4(b), the maintenance plan registration screen displays the approved plan information already entered in the input fields, allowing store employees to check and register the plan information without having to re-enter it as a maintenance job. This not only saves the trouble of having to re-enter the information, but also reduces the chance of discrepancies between the information at the time of applying for the plan and the information registered as a maintenance job. Specifically, the maintenance plan registration screen is input with an overview, contractor, implementation guidelines, report, and remarks. The maintenance plan registration screen is input with the type of maintenance work (label), implementation details (implementation items), start year of the maintenance work, frequency of the maintenance work, and end year of the maintenance work as the overview, and the implementation month of the maintenance work is input with the implementation guidelines, and the confirmation items (maintenance work target, confirmation format, checkpoints) are accepted for registration. The store employee checks the input contents on the maintenance plan registration screen and performs the registration operation. The maintenance work registration unit 202 detects the pressing of the registration button and registers it in the maintenance work DB 620.

[0036] The repair work registration unit 204 registers repair work for repairing or restoring unexpected breakdowns or damage to store equipment. Specifically, the repair work registration unit 204 registers repair work information related to the repair work in the repair work DB 610.

[0037] The similar work extraction unit 206 extracts repair work similar to the repair work registered by the repair work registration unit 204 from the repair work information stored in the repair work DB 610, based on the target of the repair and the location where the problem occurred. In other words, when a repair work is registered, the similar work extraction unit 206 searches to see if the registered repair work is a recurrence of a repair work that has occurred in the past.

[0038] The recurrence candidate display unit 208 displays the repair work information extracted by the similar work extraction unit 206 as candidates for recurring repair work. Specifically, the recurrence candidate display unit 208 displays the candidates for recurring repair work in association with a recurrence check button on the task update screen illustrated in Fig. 5(a). The repair work information displayed as a recurrence candidate includes the registration date, the location where the repair occurred, the target of the repair, and symptoms.

[0039] The recurrence information registration unit 210 associates the repair work information registered by the repair work registration unit 204 with information on whether the repair work is a recurring repair work and registers it in the repair work information DB 610. Specifically, when the recurrence information registration unit 210 detects an input operation on the task update screen that determines that the repair work is a recurrence, the recurrence information registration unit 210 registers the registered repair work in the repair work DB 610 in association with the fact that the registered repair work is a recurrence of a repair work displayed as a recurrence candidate.

[0040] The recurring task extraction unit 212 extracts repair task information of the recurring repair task from the repair task information DB 610. Specifically, the recurring task extraction unit 212 extracts repair task information associated with information indicating the recurrence. The recurrence information display unit 214 displays the repair work information extracted by the recurrence work extraction unit 212 in association with information indicating that the repair work is a recurring repair work. Specifically, as illustrated in the task search screen of Fig. 5(b), a repair work with a check mark in the recurrence column is repair work information of a recurring repair work.

[0041] FIG. 6 is a diagram illustrating an example of the functional configuration of the headquarters terminal 3. As shown in FIG. 6, a headquarters terminal program 30 is installed in the headquarters terminal 3 of this example. The headquarters terminal program 30 has a case extraction unit 300, a case display unit 302, an approval unit 304, a planned case schedule visualization unit 306, a repair work extraction unit 308, a repair work display unit 310, a decision-requiring work extraction unit 312, an aggregation display unit 314, a maintenance work schedule visualization unit 316, a usage status display unit 318, a distribution unit 320, a case information update unit 322, a status monitoring unit 324, a number of days elapsed monitoring unit 326, a facility requiring confirmation display unit 328, a maintenance work extraction unit 330, and a maintenance work display unit 332. Note that part or all of the headquarters terminal program 30 may be realized by hardware such as an ASIC. The headquarters terminal program 30 is stored in a recording medium such as a CD-ROM, and is installed in the headquarters terminal 3 via this recording medium.

[0042] The project extraction unit 300 extracts planned project information stored in the planned project DB 600 based on specified conditions. Specifically, as illustrated in the project search screen of Fig. 7(a), the project extraction unit 300 extracts planned project information using, as search conditions, identification information for identifying the store, the area to which the store belongs, the status indicating the progress of the planned project, the priority of the planned project, the implementation year of the planned project, the implementation month of the project, the budget (amount), whether the store will be closed, the brand, keywords, the contractor in charge of the project, the reason why the project needs to be implemented, or a combination of these.

[0043] The case display unit 302 displays a list of the planned case information extracted by the case extraction unit 300. Specifically, as shown in the case search screen of FIG. 7(a), the case display unit 302 displays the extracted case information in association with the store identification information, the registration date, the priority of the planned case, the case content, the closing period, the completion month of the planned case, the contractor implementing the planned case, the budget (amount), and the status. Furthermore, the case display unit 302 may tally and display the budget (amount) of the planned case information extracted by the case extraction unit 300. This allows you to understand the costs involved in planned projects. For example, by extracting and displaying planned projects to be implemented in the next fiscal year, or by using the area and implementation month as search criteria to extract and aggregate planned project information, you can understand the costs involved for each implementation month in a specified area.

[0044] The approval unit 304 associates the planned project information of the planned project applied for by the store with approval / denial information for the planned project and registers the association in the planned project DB 600. Specifically, the approval unit 304 detects an operation by a headquarters employee to determine whether to approve the project, and associates the detection result with the planned project information. In other words, the approval unit 304 determines whether the headquarters will approve or disapprove the project.

[0045] The planned-project schedule visualization unit 306 graphs the schedule of the planned-project information associated with information indicating approval of the planned project by the approval unit 304, by associating the store that will implement the planned project, information that identifies the planned project, and the period during which the planned project will be implemented. Specifically, the schedule visualization unit 306 visualizes the schedule of the planned project that has been approved by the approval unit 304 and registered as a maintenance job in the store. More specifically, as exemplified in the project implementation status screen of FIG. 7(b), the planned-project schedule visualization unit 306 displays a list of the schedules of the planned projects extracted by the project extraction unit 300. The planned-project schedule visualization unit 306 is an example of a schedule visualization unit according to the present invention.

[0046] The repair work extraction unit 308 extracts repair work information for repair work registered at each store from the repair work DB 610 based on specified conditions. Specifically, as illustrated in the repair task list screen of FIG. 8( a), the repair work extraction unit 308 extracts repair work information based on the registration date of the repair work, the brand, the area to which the store performing the repair work belongs, the store performing the repair work, the repair target, the repair cost, the status indicating the progress of the repair work, keywords, whether the repair work is a recurring repair work, or a combination of these. This allows the extraction of repair work that is marked as completed within a given registration date range (e.g., the year in which the repair work was performed), thereby tallying up the actual repair costs for that given registration date range. Furthermore, the extraction of repair work that is not marked as completed within a registration date range of the last one to two months allows the tallying up the estimated costs for repair work for the last one to two months. In addition, repair targets can be included in the search criteria, so repair work for each plumbing facility can be extracted and compiled for use in cost analysis.

[0047] The repair work display unit 310 displays the repair work information extracted by the repair work extraction unit 308. Specifically, as illustrated in the repair task list screen of FIG. 8(a), the repair work display unit 310 displays the registration date, store name, repair content, location of repair, contractor performing the repair, cost (amount) for the repair, status indicating the progress of the repair work, and number of days the status has remained (number of days the same status has continued) for the repair work information extracted by the repair work extraction unit 308. Furthermore, the repair work display unit 310 may tally and display the cost (amount) for the repair of the repair work information extracted by the repair work extraction unit 308. By displaying repair work based on specified conditions, for example, repair work information for a specified area with similar repair content can be extracted and displayed, allowing for comparison of repair costs. In addition, for example, repair work in a waiting approval status that costs more than a predetermined amount can be extracted.

[0048] The approval-required task extraction unit 312 extracts repair work and planned projects that require approval from headquarters and that have been requested by each store. Specifically, the approval-required task extraction unit 312 extracts repair work that requires approval and repair work according to the progress of the planned projects. Taking repair work as an example, as illustrated in the approval decision list screen of FIG. 8(b), the approval-required task extraction unit 312 displays repair work registered at each store that has a status of "awaiting approval decision" divided into repair work whose deadline for payment decision is approaching and repair work whose deadline has passed. In addition, the approval-required task extraction unit 312 displays repair work that has "approval decision completed" and whose deadline for the next action has passed. The display by the approval-required task extraction unit 312 may display the number of extracted repair work, display repair work information for the extracted repair work, or both. When the display of repair work is a display of the number of cases, the repair work information is associated with the displayed number of cases. This makes it possible to prevent delays in approval decisions for repair work and planning projects that require approval, and also makes it possible to check which repair work and planning projects are pending after approval has been made.

[0049] The aggregated display unit 314 aggregates and displays the implementation status of maintenance work. Specifically, the aggregated display unit 314 displays the aggregated implementation status of maintenance work at all operated stores and the aggregated implementation status of maintenance work for each store. More specifically, as illustrated in FIG. 9( a), the aggregated display unit 314 calculates and displays, as the implementation status of maintenance work aggregated across all stores, the total number of stores, the aggregated number of maintenance work that is overscheduled, the aggregated number of maintenance work that is not scheduled for the current month, and the aggregated number of handled planned cases, and further displays, as the implementation status of maintenance work aggregated for each store, the number of maintenance work that is overscheduled at each store, the number of maintenance work that is not scheduled for the current month, and the number of handled planned cases.

[0050] The maintenance work schedule visualization unit 316 displays the annual schedule of maintenance work for each store. Specifically, the maintenance work schedule visualization unit 316 associates a link to the annual schedule of maintenance work for each store with the implementation status of each store displayed by the consolidated display unit 314. As exemplified in the maintenance task implementation status of FIG. 9(b), the maintenance work schedule visualization unit 316 visualizes the type (label) of maintenance work, the content of the maintenance work, the frequency of the maintenance work, the contractor performing the maintenance work, and the period for which the maintenance work is performed, in association with each other.

[0051] The usage status display unit 318 displays the usage status of the facility maintenance management system 1 at each store in association with a link connecting to the system environment of each store. Specifically, the usage status display unit 318 calculates and displays the number of registered repair jobs or the number of registered planned projects at each store. More specifically, as exemplified in the store viewing screen of FIG. 10(a), the usage status display unit 318 displays the store number, store name, total number of registered repair jobs (total number of registered repair tasks), and the number of registered repair jobs (number of repair tasks) registered within the most recent specified number of days in association with a link to the store page. This allows the headquarters to follow up on how to use the facility maintenance management system 1 for stores with a small number of registrations.

[0052] The distribution unit 320 distributes the maintenance plan and setting contents determined by the headquarters to one or more specified distribution destinations. Specifically, as shown in the maintenance plan distribution confirmation screen of FIG. 10(b), the distribution unit 320 receives a distribution destination from a headquarters employee, such as a brand, an area to which the store belongs, a store, or a combination of these, and distributes the maintenance plan information to the received distribution destinations. For example, the maintenance plan information includes the classification (label) of the maintenance plan, the implementation items, the start year, the implementation frequency, the end year, and whether or not a report is required.

[0053] The project information update unit 322 postpones the planned fiscal year of a planned project. Specifically, the project information update unit 322 postpones the planned fiscal year and implementation year of the planned project information stored in the planned project DB 600. More specifically, the project information update unit 322 postpones the planned fiscal year and implementation year of the planned project information of a planned project that has not been approved by the approval unit 304.

[0054] The status monitoring unit 324 detects updates to the status of the planned project information stored in the planned project information DB 600, the status of the repair work information stored in the repair work DB 610, or the status of the maintenance work information stored in the maintenance work DB 620. Specifically, the status monitoring unit 324 extracts project information, repair work information, or maintenance work information for which no status update has been detected for a specified period or longer. The elapsed days monitoring unit 326 monitors the number of days that have passed since the registration date of the planned case information stored in the planned case information DB 600, the registration date of the repair work information stored in the repair work DB 610, or the registration date of the maintenance work information stored in the maintenance work DB 620. Specifically, the elapsed days monitoring unit 326 extracts the planned case information, repair work information, or maintenance work information for which the number of days that have passed since the registration date is equal to or greater than a specified value.

[0055] The confirmation-required facility display unit 328 displays planned case information, repair work information, or maintenance work information extracted by the status monitoring unit 324 or the elapsed days monitoring unit 326 from among planned case information, repair work information, or maintenance work information whose status is not complete. This allows headquarters to identify stores where operations are slowing down.

[0056] The maintenance work extraction unit 330 extracts, based on specified conditions, maintenance work information stored in the maintenance work DB 620. Specifically, the maintenance work extraction unit 330 extracts the maintenance work information based on identification information for identifying the store, the registration date of the maintenance work, the type of maintenance work, the frequency of the maintenance work, the year the maintenance work was performed, the month the maintenance work was performed, the content of the maintenance work, the cost of the maintenance work, the status indicating the progress of the maintenance work, keywords, or a combination of these. The maintenance work display unit 332 displays the maintenance work information extracted by the maintenance work extraction unit 330. Furthermore, the maintenance work display unit 332 may tally and display the costs (amounts) required for the maintenance work of the maintenance work information extracted by the maintenance work extraction unit 330.

[0057] FIG. 11 is a table illustrating the project information stored in the project DB 600. As shown in FIG. As shown in FIG. 11, the project DB 600 stores project information related to projects submitted by each store that require prior budget allocation and approval for implementation. Project information includes a project ID, an area, a store, a registration date, project details, a rank, closure information, project period, a vendor, a budget, attached documents, a status, and a planned / implemented year. The project ID is information identifying the project. The area is information about the area to which the store implementing the project belongs. The store is the name of the store implementing the project. The rank is the priority of the project. The closure information indicates whether the project will be closed for implementation and, if so, the period of closure. The project period is the start and end months of the project. The vendor is information about the vendor implementing the project, and the budget is the cost of the project. The attached documents are information about materials required for the project. The status indicates the progress of the project, enabling the user to determine whether the project has been approved. The planned / implemented year is the project's planned year and implementation year.

[0058] FIG. 12 is a table illustrating repair work information stored in the repair work DB 610. As illustrated in FIG. 12, the repair work DB 610 stores repair work information related to repair work, which is unexpected work, in association with the area to which the store belongs. The repair work information associates a repair work ID with the area, store, registration date, location, target, whether the failure is a recurrence or not, repair content, contractor, status, label, amount, and action deadline. The repair work ID is information that identifies the repair work. The store is the name of the store that performs the repair work. The area is the area to which the store that performs the repair work belongs. The location is the location where the repair occurred. The target is the repair target. The contractor is the contractor that performs the repair. The status is the progress of the repair work. The label indicates replacement part information. The amount is the cost related to the repair work. The action deadline indicates the deadline for performing the task for each status.

[0059] FIG. 13 is a table illustrating an example of maintenance work information stored in the maintenance work DB 620. As shown in FIG. As shown in FIG. 13, the maintenance job DB 620 stores information about maintenance jobs that are scheduled in advance. The maintenance job information associates a maintenance job ID with a planned project ID, area, store, label, implementation item, registration date, start year, implementation frequency, end year, implementation month (start month and end month), contractor, amount, target, confirmation format, checkpoint, report, and status. The maintenance job ID is information that identifies the maintenance job. The planned project ID is the planned project ID registered as the maintenance job. The area is the area to which the store that will perform the maintenance job belongs. The store is the name of the store that will perform the maintenance job. The label is the classification label of the maintenance job (planned project / regular cleaning / voluntary inspection / statutory inspection, etc.). The implementation item is the content of the maintenance job. The contractor is the company that will perform the maintenance job. The amount is the cost of the maintenance job. The target is the target of the maintenance job. The confirmation format indicates the method of confirmation (implementation check / abnormality check). The report indicates whether a report on the maintenance job is required. The status indicates the progress of the maintenance work.

[0060] FIG. 14 is a flowchart illustrating the management process (S10) of the planned case by the facility maintenance management system 1. In the process of managing the planned projects (S10), a process will be described in which the headquarters manages the processes from the registration of the planned projects applied for by each store to the implementation of the plans in each store. As illustrated in FIG. 14, in step 100 (S100), a store employee logs in to the facility maintenance management system 1 from the store terminal 2 and applies for a planned project on the planned project registration screen. Specifically, the store employee inputs the planned project information required for applying for the planned project. The project information registration unit 200 of the store terminal 2 detects the registration operation, associates the planned project information with a status of "waiting for approval" and information about the area to which the store that applied for the planned project belongs, and stores the associated information in the planned project DB 600 as planned project information.

[0061] In step 105 (S105), the headquarters decides whether to approve the planned cases requested by the stores. Specifically, the approval-required task extraction unit 312 of the headquarters terminal 3 extracts planned cases that are requested by each store and require approval by the headquarters. Specifically, the approval-required task extraction unit 312 displays planned case information for planned cases whose status is "waiting for approval." In step 110 (S110), the approval unit 304 of the headquarters terminal 3 detects an operation to decide whether to approve the planned case determined based on the planned case information displayed by the approval-requiring task extraction unit 312, associates the detection result, and updates the planned case information stored in the planned case DB 600. If the planned case is approved (S110: Yes), the planned case management process (S10) proceeds to S115, and if approval is not possible (S110: No), the planned case management process (S10) proceeds to S120.

[0062] In step 115 (S115), the maintenance work registration unit 202 of the store terminal 2 registers the planned project information of the approved planned project as a maintenance project in the maintenance work DB 620 through the registration operation of a store employee based on the contents of the maintenance plan registration screen shown as an example in Figure 4(b). In step 120 (S120), the implementation year of the planned project that was not approved is postponed. Specifically, the project information update unit 322 of the headquarters terminal 3 updates the implementation year of the planned project information of the planned project that was not approved and is stored in the planned project DB 600 to be postponed to the year following the implementation year. In step 125 (S125), the consolidated display unit 314 of the headquarters terminal 3 displays, on the store implementation status screen of FIG. 9(a), the implementation status of maintenance work consolidated for all stores operated by the headquarters, and the implementation status of maintenance work consolidated for each store. Furthermore, the planned case schedule visualization unit 306 extracts from the maintenance case DB 620 planned cases registered as maintenance cases that match the conditions specified on the case implementation status screen of FIG. 9(b), and displays a graph of the implementation schedule of the registered planned cases. This allows headquarters employees to check the implementation status of the planned cases registered as maintenance cases.

[0063] FIG. 15 is a flowchart illustrating the management process (S20) of a recurring case by the facility maintenance management system 1. As illustrated in Figure 15, in step 200 (S200), a store employee logs in to the facility maintenance management system 1 and registers a repair job, and the repair job registration unit 204 of the store terminal 2 acquires the registration information for the repair job, associates it with identification information, and stores the repair job information in the repair job DB 610 of the headquarters management server 4. In step 205 (S205), the similar task extraction unit 206 of the store terminal 2 extracts repair task information that has a similar repair target and problem occurrence location to the repair task information acquired by the repair task registration unit 204 from the repair task information stored in the repair task information DB 610 of the head office management server 4. If the similar task extraction unit 206 finds similar repair task information (S205: Yes), the recurrence case management process (S20) proceeds to S210, and if similar repair task information is not found (S205: No), the recurrence case management process (S20) ends.

[0064] In step 210 (S210), the recurrence candidate display unit 208 of the store terminal 2 displays the repair work information extracted by the similar work extraction unit 206 as a candidate for recurring repair work on the repair work task update screen of Figure 5(a). In step 215 (S215), if the recurrence information registration unit 210 of the store terminal 2 detects an entry in the check box on the task update screen indicating that the repair work information displayed as a recurrence candidate is a recurrence case (S215: Yes), the recurrence case management process (S20) proceeds to S220, and if no check is detected in the check box, the recurrence case management process (S20) ends. In step 220 (S220), the recurrence information registration unit 210 of the store terminal 2 registers the repair work information for which a check mark has been entered in the recurrence check field in the repair work information DB 610 as a recurring repair work.

[0065] In step 225 (S225), if the recurring work extraction unit 212 of the store terminal 2 detects a check mark in the recurrence check button on the search screen for repair work tasks in Figure 5 (b) (S225: Yes), the recurring case management process (S20) proceeds to S230, and if not (S225: No), the recurring case management process (S20) terminates processing. In step 230 (S230), the recurring task extraction unit 212 extracts, from the repair task DB 610, repair task information associated with the fact that the case is a recurring case. In step 235 (S235), the recurrence information display unit 214 of the shop terminal 2 displays a list of the task information of the recurred repair task extracted by the recurrence task extraction unit 212 as a search result on the task search screen.

[0066] As explained above, the facility maintenance management system 1 in this embodiment can manage not only repetitive tasks such as repair and maintenance work, but also planned projects for spot responses to be carried out at each store in the following fiscal year, so that the headquarters can grasp the tasks that need to be carried out and identify problems such as schedule delays, and it is possible to prevent the scope of impact from becoming too large, especially for large-scale projects.In addition, since expenses are also managed, it is also useful for calculating expected expenses. Furthermore, the facility maintenance management system 1 allows for a cross-sectional search of repair work, maintenance work, and planning projects registered at each store, and allows for confirmation of the implementation status aggregated at headquarters, thereby providing support to stores that are lagging behind in their maintenance management work. Furthermore, the facility maintenance management system 1 manages whether the repair work that has occurred is a recurrence of repair work that has been done in the past. This makes it possible to use the information as a reference for the costs and time required for similar repair work when it occurs, and also allows for quick response since it can be handled based on past cases.

[0067] (Variation) In the above embodiment, the headquarters terminal program 30 is installed on the headquarters terminal 3, but this is not limited to this. For example, the headquarters terminal program 30 may be installed on the headquarters management server 4, and the headquarters management server 4 may have the functions of the headquarters terminal program 30. [Explanation of symbols]

[0068] 1...Facility maintenance management system 2...Store terminal 3...Headquarters terminal 4...Headquarters management server 20...Store terminal program 30... Headquarters terminal program 200...Project Information Registration Department 202...Maintenance Business Registration Department 204...Repair Business Registration Department 206…Similar business extraction department 208...Recurrence candidate display section 210...Recurrence Information Registration Department 212...Recurring Business Extraction Department 214...Recurrence information display section 300…Project extraction department 302…Project display section 304...Approval Department 306…Planning Project Schedule Visualization Department 308…Repair work extraction department 310…Repair work display department 312...Approval-required business extraction section 314...Integrated display section 316…Maintenance Work Schedule Visualization Department 318...Usage status display section 320…Distribution Department 322…Project information update department 324...Schedule Monitoring Department 326... Elapsed Days Monitoring Unit 328... Facility display area requiring confirmation 330…Maintenance work extraction department 332…Maintenance work display section 600...Planning project database 610...Repair work database 620...Maintenance business database

Claims

1. A facility maintenance management system that manages the tasks and projects for facility maintenance management carried out at each facility operated by the headquarters, a case information storage unit for storing case information relating to cases that require advance budget allocation and approval for implementation and that are applied for by each facility; a case extraction unit that extracts case information stored in the case information storage unit based on specified conditions; a case display unit that displays a list of case information extracted by the case extraction unit; and The project information includes project identification information, facility identification information, the area to which the facility belongs, the budget, and the project planning year and implementation year, The case extraction unit extracts case information of facilities belonging to a specified area, the project display unit aggregates and displays budgets for projects for each area to which the facilities extracted by the project extraction unit belong; a case information registration unit that registers case information of cases applied for by facilities; an approval unit that associates the case information acquired by the case information registration unit with information on whether or not the case is approved and registers the information in the case information storage unit; a schedule visualization unit that visualizes a schedule of the project information associated with information indicating that the project has been approved by the approval unit, by associating the facility where the project will be performed, information identifying the project, and a period during which the project will be performed with the schedule; and The schedule visualization unit displays a list of schedules of cases of facilities belonging to the specified area extracted by the case extraction unit. Facility maintenance management system.

2. The case display unit displays the case information acquired by the case information registration unit in association with a status indicating the progress of the case. The facility maintenance management system according to claim 1 .

3. a maintenance work storage unit for storing maintenance work information relating to maintenance work that is a work scheduled in advance; a maintenance work registration unit that registers, in the maintenance work storage unit, case information associated with information indicating that the approval has been given by the approval unit, as a maintenance work; Further having The facility maintenance management system according to claim 1 .

4. a repair work storage unit that stores repair work information relating to repair work, which is an unexpected work, in association with the area to which the facility belongs; a repair work extraction unit that extracts repair work information stored in the repair work storage unit based on specified conditions; a repair work display unit that displays the repair work information extracted by the repair work extraction unit; and The repair work extraction unit extracts repair work information based on the facility where the repair work is to be performed, the registration date of the repair work, the object of the repair, the cost of the repair, the status indicating the progress of the repair work, keywords, whether or not the repair work is a recurring repair work, or a combination thereof. The facility maintenance management system according to claim 1 .

5. The repair work extraction unit extracts repair work information of repair works that have a status indicating that the repair cost is equal to or greater than a specified value and that the repair work is waiting for approval, The repair work display unit displays the repair work information extracted by the repair work extraction unit. The facility maintenance management system according to claim 4.

6. The repair work extraction unit extracts repair work information based on the content of the specified repair work, The repair work display unit displays, by area, at least the facilities where repair work was performed and the costs incurred for the repair work, from the repair work information extracted by the repair work extraction unit. The facility maintenance management system according to claim 4.

7. a maintenance work extraction unit that extracts maintenance work information stored in the maintenance work storage unit based on specified conditions; a maintenance work display unit that displays the maintenance work information extracted by the maintenance work extraction unit; and The maintenance work extraction unit extracts maintenance work information based on the facility where the maintenance work is performed, the registration date of the maintenance work, the type of maintenance work, the frequency of the maintenance work, the year in which the maintenance work is performed, the month in which the maintenance work is performed, the content of the maintenance work, the cost of the maintenance work, the status indicating the progress of the maintenance work, keywords, or a combination thereof. The facility maintenance management system according to claim 3 .

8. A maintenance work storage unit that stores maintenance work information related to maintenance work that is scheduled in advance. and a status monitoring unit that detects an update of a status of the project information stored in the project information storage unit, a status of the repair work information stored in the repair work storage unit, or a status of the maintenance work information stored in the maintenance work storage unit; an elapsed days monitoring unit that monitors the number of days that have passed since the registration date of the case information stored in the case information storage unit, the registration date of the repair work information stored in the repair work storage unit, or the registration date of the maintenance work information stored in the maintenance work storage unit; and The status monitoring unit extracts case information, repair work information, or maintenance work information for which a status update has not been detected for a specified period of time or longer, The elapsed days monitoring unit extracts case information, repair work information, or maintenance work information for which the number of days that have elapsed since the registration date is equal to or greater than a specified value, a confirmation-required facility display unit that displays case information, repair work information, or maintenance work information extracted by the status monitoring unit or the elapsed days monitoring unit from among cases, repair work, or maintenance work for which the response has not been completed; Further having The facility maintenance management system according to claim 4.

9. A usage status display section that displays the system usage status at each facility and the links connecting to the system environment at each facility. and The system usage status at the facility is the number of registered repair jobs or the number of registered cases at the facility. The facility maintenance management system according to claim 4.

10. a repair work registration unit that registers the repair work information; a similar work extraction unit that extracts repair work information similar to the repair work information registered by the repair work registration unit from the repair work information stored in the repair work storage unit based on the repair target and the location where the problem occurs; a recurrence candidate display unit that displays the repair work information extracted by the similar work extraction unit as a candidate for a recurring repair work; Further having The facility maintenance management system according to claim 4.

11. A recurrence information registration unit that associates the repair work information registered by the repair work registration unit with information on whether the repair work information extracted by the similar work extraction unit is a recurring repair work and registers the information in the repair work storage unit; a recurrence information display unit that displays the repair work information registered by the repair work registration unit in association with whether or not the information on the repair is a recurring repair work; Further having The facility maintenance management system according to claim 10.

12. a recurring work extraction unit that extracts repair work information of a recurring repair work from the information on repairs stored in the repair work storage unit; and The recurrence information display unit displays a list of repair work information extracted by the recurrence work extraction unit. The facility maintenance management system according to claim 11.

13. A facility maintenance management method for managing operations and matters for facility maintenance management carried out at each facility operated by a headquarters, comprising: a case information storage step in which the computer stores case information relating to cases that require advance budget allocation and approval for implementation and that have been applied for by each facility; a case extraction step in which the computer extracts the case information stored in the case information storage step based on specified conditions; a case display step in which the computer displays the case information extracted by the case extraction step in a list; and The project information includes project identification information, facility identification information, the area to which the facility belongs, the budget, and the project planning year and implementation year, In the case extraction step, case information of facilities belonging to the designated area is extracted; In the project display step, the project budgets for each area to which the facility belongs are tallied and displayed; a case information registration step in which the computer registers case information of the case applied for by the facility; an approval step in which the computer associates approval / non-approval information for the case with the case information acquired in the case information registration step and registers the information; a schedule visualization step in which the computer graphs the schedule of the project information associated with information indicating that the project has been approved in the approval step, by associating the facility where the project will be implemented, information identifying the project, and a period during which the project will be implemented; and In the schedule visualization step, a list of schedules of the cases of facilities belonging to the specified area extracted in the case extraction step is displayed. Facility maintenance management methods.

14. A program for managing the tasks and projects for facility maintenance management carried out at each facility operated by the headquarters, a case information storage step for storing case information relating to cases that require advance budget allocation and approval for implementation and that have been applied for by each facility; a case extraction step for extracting cases based on conditions; a case display step of displaying a list of the case information extracted by the case extraction step; on the computer, The project information includes project identification information, facility identification information, the area to which the facility belongs, the budget, and the project planning year and implementation year, In the case extraction step, case information of facilities belonging to the designated area is extracted; In the project display step, the project budgets for each area to which the facility belongs are tallied and displayed; a case information registration step for registering case information of a case applied for by a facility; an approval step of registering information on whether or not the project is approved in association with the project information acquired in the project information registration step; a schedule visualization step of graphing the schedule of the project information associated with information indicating approval in the approval step, by associating the facility where the project will be performed, information identifying the project, and the period during which the project will be performed; on the computer, In the schedule visualization step, a list of schedules of the cases of facilities belonging to the specified area extracted in the case extraction step is displayed. program.

Images