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

Abstract

We provide a facility maintenance management system that efficiently manages the maintenance of facilities. [Solution] The facility maintenance management system in this embodiment includes a registration reception unit that accepts registration of tasks in relation to the repair management or maintenance management of facilities, in association with repair tasks which are sudden tasks or maintenance tasks which are tasks that are scheduled in advance, and a schedule management unit that manages the schedule or status of the tasks accepted by the registration reception unit. The schedule management unit accepts the schedule or status of the repair tasks individually for each repair task and accepts the schedule or status of the maintenance tasks in a standardized manner.

Description

Technical Field

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

Background Art

[0002] For example, Patent Document 1 discloses a guest room inspection management system in which a terminal is connected to a server via the Internet. The system includes an inspection date input means for checking and inputting the status of equipment in the guest room and the status of the guest room on the date of input, an inspection instruction content input means for inputting instruction content regarding inspection target items, an inspection item implementation completion date input means for the date on which all implementation of items according to the inspection instruction content is completed, and a management target list display means. The system also has a database for recording the inspection date, which is the date when the status of the equipment in the guest room and the status of the guest room are checked, the inspection instruction content, which is the instruction content regarding inspection target items, and the inspection item implementation completion date, which is the date when all implementation of items according to the inspection instruction content is completed. The management target list display screen is displayed on the screen of the terminal, and in the management target list display screen, the inspection date and the inspection item implementation completion date are displayed for each management category that is a management target, and the inspection date is distinguished and displayed according to the set period during which the inspection has not been carried out, enabling the display of the progress status.

[0003] Further, Patent Document 2 discloses a facility maintenance support system including a reception system, a mobile system, a network system, and a base system. The base system has a task management table in which a plurality of tasks are defined. When the reception system receives a notification from the mobile system or the network system that the condition for transitioning to a second task, which is the next task, for an arbitrary first task among the plurality of tasks is satisfied based on the task management table, the reception system has means for automatically transitioning the states of the reception system, the mobile system, and the network system to the second task, which is the next task.

Prior Art Documents

Patent Documents

[0004] [Patent Document 1] Patent No. 5709337 [Patent Document 2] Japanese Patent Publication No. 2021-114098 [Overview of the project] [Problems that the invention aims to solve]

[0005] The present invention aims to efficiently manage and maintain facilities. [Means for solving the problem]

[0006] The facility maintenance management system according to the present invention includes a registration reception unit that accepts registration of work in relation to the repair management or maintenance management of a facility, in association with repair work which is an unexpected task or maintenance work which is a pre-scheduled task, and a schedule management unit that manages the schedule or status of the work accepted by the registration reception unit. The schedule management unit accepts the schedule or status of the repair work individually for each repair work and accepts the schedule or status of the maintenance work in a standardized manner.

[0007] Preferably, the system includes a registration reception unit that accepts registrations of services related to the repair or maintenance management of facilities, in relation to whether or not a contractor is involved, and a schedule management unit that manages the schedule or status of the services accepted by the registration reception unit, wherein the schedule management unit accepts the schedule or status of services in which a contractor is involved on an individual basis for each service in which a contractor is involved, and accepts the schedule or status of services in which a contractor is not involved in a standardized manner.

[0008] Preferably, the system further includes a grouping unit that consolidates the repair work received by the registration reception unit based on the cause of the repair, and a location setting unit that associates the locations to be repaired with the repair work received by the registration reception unit, wherein the location setting unit associates all the locations to be repaired with the work consolidated by the grouping unit.

[0009] Preferably, the registration reception unit further includes an equipment information storage unit that receives repair targets for repair or maintenance work and manages the equipment of the facility, and an equipment information synchronization unit that synchronizes the repair targets received by the registration reception unit with the target information stored in the equipment information storage unit, wherein the equipment information synchronization unit synchronizes the updated repair target information with the repair target information stored in the equipment information storage unit when the repair target information received by the registration reception unit is updated.

[0010] Preferably, the schedule management unit extracts tasks to be performed within a predetermined period including the current date, newly registered tasks, tasks with updated content, and completed tasks from the tasks received by the registration acceptance unit, and the schedule management unit displays all extracted tasks in association with the type of each task.

[0011] Preferably, the system further includes a work feasibility instruction unit that indicates whether the site where the contractor will perform the repair or maintenance work received by the registration acceptance unit is in a state where work can be commenced, and an authority granting unit that grants the contractor the authority to connect to information regarding the repair or maintenance work received by the registration acceptance unit, and the contractor connects to the work feasibility information indicated by the work feasibility instruction unit using the authority granted by the authority granting unit.

[0012] Preferably, the system further includes a maintenance planning department that plans facility maintenance work based on the actual maintenance work performed by the registration acceptance department, and the maintenance planning department estimates the budget for maintenance or repair work based on the actual maintenance or repair work performed by the registration acceptance department.

[0013] Preferably, the system further includes a distribution unit that distributes plans for repair or maintenance work to multiple facilities in a single batch.

[0014] Preferably, the system further includes a schedule monitoring unit that monitors the schedules of repair or maintenance work managed for each facility, which are registered by the registration acceptance unit, and the schedule monitoring unit extracts tasks that have exceeded their deadlines for each facility.

[0015] Preferably, the system further includes an approval-requiring task extraction unit that extracts repair work requiring approval, and a classification unit that classifies the repair work received by the registration acceptance unit based on the cost of carrying out the repair work and the importance of the repair work, and displays the repair work extracted by the approval-requiring task extraction unit according to the grade classified by the classification unit.

[0016] Preferably, the system further includes a routine task registration unit that accepts registration of routine tasks, which are maintenance tasks that are scheduled to be performed repeatedly, and the routine task registration unit accepts registration of confirmation items appropriate to each location when there are multiple locations where a routine task is performed.

[0017] The facility maintenance management method according to the present invention includes a registration acceptance step in which a computer accepts registration of work in relation to the repair management or maintenance management of a facility, in association with repair work which is an unexpected task or maintenance work which is a pre-scheduled task, and a schedule management step in which the computer manages the schedule or status of the work accepted in the registration acceptance step, wherein the schedule management step accepts the schedule or status of the repair work individually for each repair work and accepts the schedule or status of the maintenance work in a standardized manner.

[0018] The program according to the present invention causes a computer to execute a registration acceptance step for accepting registration of work in relation to the repair management or maintenance management of a facility, in association with repair work which is an unexpected task or maintenance work which is a pre-scheduled task, and a schedule management step for managing the schedule or status of the work accepted in the registration acceptance step. The schedule management unit accepts the schedule or status of the repair work individually for each repair work and accepts the schedule or status of the maintenance work in a standardized manner.

[0019] The facility maintenance management method according to the present invention includes a registration acceptance step in which a computer accepts registration of work in relation to the repair management or maintenance management of the facility, in association with whether or not a contractor is involved, and a schedule management step in which the computer manages the schedule or status of the work accepted in the registration acceptance step, wherein the schedule or status of work in which a contractor is involved is accepted individually for each work in which a contractor is involved, and the schedule or status of work in which a contractor is not involved is accepted in a standardized manner.

[0020] The program according to the present invention causes a computer to execute a registration acceptance step that accepts registration of work in relation to the repair management or maintenance management of a facility, in association with whether or not a contractor is involved, and a schedule management step that manages the schedule or status of the work accepted in the registration acceptance step. In the schedule management step, the schedule management unit accepts the schedule or status of work in which a contractor is involved individually for each work in which a contractor is involved, and accepts the schedule or status of work in which a contractor is not involved in a standardized manner. [Effects of the Invention]

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

[0022] [Figure 1] It is a diagram illustrating the overall configuration of the facility security management system 1. [Figure 2] It is a diagram illustrating the hardware configuration of the facility management server 2. [Figure 3] It is a diagram illustrating the functional configuration of the facility management server 2. [Figure 4] (a) is a diagram showing the maintenance work registration screen, and (b) is a diagram showing the repair work registration screen. [Figure 5] (a) is a diagram showing the list of repair work, maintenance work, and routine work, and (b) is a diagram showing the status update screen of the repair work. [Figure 6] (a) is a diagram showing the task list of the repair work, and (b) is a diagram showing the task list of the maintenance work. [Figure 7] (a) is a diagram exemplifying the common setting screen, and (b) is a diagram showing the progress status display screen of the work. [Figure 8] (a) is a diagram showing the history of the repair work, (b) is a diagram showing the details of the history of the repair work, and (c) is a diagram showing the history of the maintenance work. [Figure 9] (a) is a diagram showing the routine work registration screen, (b) is a diagram showing the registration screen of the work result of the routine work, and (c) is a diagram showing the list of the routine work. [Figure 10] It is a diagram illustrating the functional configuration of the head office server 4. [Figure 11] It is a diagram showing the approval judgment list. [Figure 12] It is a flowchart explaining the repair work registration process (S10) by the facility security management system 1. [Figure 13] It is a flowchart explaining the maintenance work registration process (S20) by the facility security management system 1. [Figure 14] It is a flowchart explaining the routine work registration process (S20) by the facility security management system 1.

Embodiments for Carrying Out the Invention

[0023] First, let me explain the background to the present invention. In facility maintenance management, the information and scheduling methods differ between repair work that occurs unexpectedly and maintenance work that is carried out based on a pre-planned schedule. Furthermore, even within maintenance work, the frequency of work and whether it can be carried out uniformly across multiple facilities differ between work carried out based on an annual plan, such as statutory inspections and periodic inspections, and routine check work. Until now, no task management tool has existed that manages facility maintenance management according to the type of work. In view of these issues, the present invention provides a facility maintenance management system that allows facility maintenance management to be implemented under different operational procedures depending on the type of work, and that enables the management of the performance of these operations at a headquarters that oversees multiple facilities.

[0024] Embodiments of the present invention will be described below with reference to the drawings. However, the scope of the present invention is not limited to the illustrated examples. Furthermore, in this embodiment, the facility maintenance management system 1 is described using an accommodation facility as an example, but the facilities in the present invention are not limited to accommodation facilities, but also include hot spring facilities, leisure facilities, and the like. Figure 1 is a diagram illustrating the overall configuration of the facility maintenance management system 1. As illustrated in Figure 1, the facility maintenance management system 1 manages repair or maintenance work at accommodation facilities and includes a facility management server 2, a user terminal 3, and a headquarters server 4. User terminal 3 is a computer terminal operated by the accommodation facility's employees and provides the user interface for the facility maintenance management system 1. Employees connect to the facility maintenance management system 1 from user terminal 3 to register, view, and update repair and maintenance tasks. Here, repair tasks refer to tasks to repair or restore facility equipment that have unexpectedly failed or been damaged in relation to the facility's repair or maintenance management, while maintenance tasks refer to tasks that are planned in advance to maintain the performance of the equipment and prevent failures or damage. Maintenance tasks include not only annual plans but also tasks that are scheduled as needed in accordance with operations. Furthermore, in this embodiment, tasks related to the facility's repair or maintenance management that involve a contractor are described as repair tasks, and tasks that do not involve a contractor are described as maintenance tasks, but this is not limited to this, and there may be cases where a contractor is involved in maintenance tasks. Furthermore, the equipment according to the present invention is not limited to equipment or devices within a facility, but also includes interior and exterior finishes. Examples of equipment include air conditioners, televisions, and refrigerators. Interior finishes are those that decorate the inside of a facility and include, for example, curtains, wallpaper, furniture, amenities, and other furnishings. Exterior finishes are those that decorate the outside of a facility and include, for example, exterior walls and roofs. Facility management server 2 is a computer terminal that manages repair and maintenance tasks at accommodation facilities. Facility management server 2 receives repair and maintenance tasks registered from user terminal 3 and manages each task according to its respective operational rules. Headquarters Server 4 is the server that oversees the maintenance management of each accommodation facility. Specifically, Headquarters Server 4 monitors the repair and maintenance work managed by each accommodation facility's facility management server 2, manages tasks that need to be performed at headquarters, plans maintenance, and distributes information necessary for facility maintenance management to each accommodation facility. Furthermore, the facility management server 2 and the headquarters server 4 may be implemented using cloud servers.

[0025] Figure 2 is a diagram illustrating the hardware configuration of facility management server 2. As illustrated in Figure 2, the facility management server 2 includes a CPU 500, memory 502, HDD 504, network interface 506 (network IF 506), display device 508, and input device 510, and these components are connected to each other via a bus 512. CPU500 is, for example, a central processing unit. Memory 502 is, for example, volatile memory and functions as main memory. HDD504 is, for example, a hard disk drive, which stores computer programs and other data files as a non-volatile recording device. Network IF506 is an interface for wired or wireless communication, and for example, it enables communication between user terminal 3 and headquarters server 4. The display device 508 is, for example, a liquid crystal display. The input device 510 is, for example, a keyboard and a mouse. Furthermore, the hardware configuration of headquarters server 4 is the same as that of facility management server 2.

[0026] Figure 3 is a diagram illustrating the functional configuration of the facility management server 2. As illustrated in Figure 3, the facility management server 2 in this example has the facility management program 20 installed, and is configured with a repair and maintenance database 600 (repair and maintenance DB600), an equipment information database 610 (equipment information DB610), and a routine work database 620 (routine work DB620). The facility management program 20 includes a registration reception unit 200, a schedule management unit 202, a location setting unit 204, an equipment information synchronization unit 206, a grouping unit 208, a status update unit 210, a task extraction unit 212, a deadline notification unit 214, a work feasibility instruction unit 216, an authorization granting unit 218, a progress display unit 220, a history search unit 222, a routine task registration unit 224, a routine deadline management unit 226, an alert determination unit 228, and a routine task display unit 230. Furthermore, part or all of the facility management program 20 may be implemented using hardware such as an ASIC. The facility management program 20 is stored on a recording medium such as a CD-ROM and installed on the facility management server 2 via this recording medium.

[0027] In the facility management program 20, the registration reception unit 200 accepts registrations of tasks related to the repair or maintenance management of facilities, in relation to repair tasks which are unexpected tasks or maintenance tasks which are pre-scheduled tasks. An unexpected task is a task that occurs accidentally and cannot be planned in advance, such as a task that arises due to equipment failure. Furthermore, the registration reception unit 200 accepts registration of tasks related to the repair management or maintenance management of the facility, in relation to whether or not a contractor is involved. Specifically, the registration reception unit 200 accepts registration by having the user distinguish between repair tasks and maintenance tasks on the task registration (task registration) screen illustrated in Figure 4(a). More specifically, the task registration screen is divided into a screen for registering repair tasks and a screen for registering maintenance tasks, and the registration reception unit 200 switches the registration screen based on the user's selection.

[0028] In the case of repair work, the registration reception unit 200 accepts registration from the user, as illustrated in Figure 4(b), including the location of the incident (guest rooms and facilities), the equipment to be repaired, the repair details (tasks to be resolved), the importance of the repair work, the status of the repair work (the next action to be taken), the deadline for the action, the action group and the name of the person in charge, the name of the related company (the name of the contractor), the name of the registrant, and, if necessary, images of the object to be repaired and audio data of any abnormal sounds. A repair task refers to the work necessary to carry out the repair work. The registration reception unit 200 assigns an identification number to the received repair work and stores it in the repair and maintenance DB 600 as a repair work. In the repair work registration screen illustrated in Figure 4(b), when a status is selected by the user, the registration reception unit 200 displays the action group responsible for the status, the name of the person in charge, and the action deadline. In addition, the repair and maintenance DB 600 manages contractors and their personnel in association, and in the repair work registration screen, when a contractor is entered by the user, the registration reception unit 200 displays the name of the person in charge associated with the entered contractor. This reduces the effort required for the user to enter each item. The registration reception unit 200 accepts, in the case of maintenance work, the classification label for the maintenance work (equipment management / environmental hygiene management / periodic cleaning / statutory inspection, etc.), maintenance content, target location, name of the responsible contractor, frequency, and selection of the month in which the maintenance work will be performed based on the frequency, as illustrated in Figure 4(a). Users can create a maintenance work schedule simply by checking the number of times the maintenance work will be performed and the corresponding month. The registration reception unit 200 assigns an identification number to the accepted maintenance work and stores it in the repair and maintenance DB 600 as maintenance work. If a contractor is involved in the maintenance work, the name of the person in charge associated with the contractor will be displayed when the contractor is entered during the registration of the maintenance work. Users can manage tasks according to either the repair work management method or the maintenance work management method simply by distinguishing whether the task being registered is a repair work or a maintenance work, and then registering it according to the respective registration screen.

[0029] The Schedule Management Unit 202 receives the schedule or status of repair work for each repair work, and the schedule or status of maintenance work in a standardized manner. Specifically, in the case of repair work, the Schedule Management Department 202 manages the task deadlines (action deadlines) for each task in the repair work for each repair project. On the other hand, in the case of maintenance work, the schedule management unit 202 manages the planned implementation months based on the frequency of maintenance work. The Schedule Management Unit 202 extracts tasks to be performed within a specified period including the current date, newly registered tasks, tasks with updated content, and completed tasks, and displays all extracted tasks in association with their respective types. Specifically, as illustrated in Figure 5(a), the Schedule Management Unit 202 displays a list of repair / maintenance tasks registered and updated today, associating them with the registration date for repairs, the scheduled year and month for maintenance, the status, target location, person in charge, and contractor. It also displays routine tasks (task checks) completed today. The task list in Figure 5(a) displays registered, updated, and completed tasks, thus also functioning as a daily report. When the Schedule Management Unit 202 displays tasks as a daily report, it may display one or more tasks arbitrarily selected from tasks to be performed during a specified period including the current date, newly registered tasks, tasks with updated content, and completed tasks, for example, tasks to be performed and tasks whose content has been updated.

[0030] The location setting unit 204 associates the location to be repaired or maintained with the registration process. Specifically, it associates the locations to be repaired and maintained that have been received by the registration reception unit 200. Specifically, the location setting unit 204 displays options for the target location (e.g., room number, public bath, restaurant, etc.) and accepts the user's selection. The equipment information synchronization unit 206 associates the registered repair or maintenance tasks with the equipment information to be repaired. Specifically, the equipment information synchronization unit 206 synchronizes the repair targets of the registered repair or maintenance tasks with the repair targets in the equipment information DB 610, which manages equipment information in advance. As a result, when the information of the repair targets is updated due to the execution of the repair or maintenance tasks, the equipment information stored in the equipment information DB 610 is updated. The equipment information DB 610 stores the equipment name, classification, manufacturer, name, model, and location associated with the equipment. Note that the equipment information DB 610 is an example of an equipment information storage unit according to the present invention. The grouping unit 208 consolidates repair tasks based on the cause of the repair work. Specifically, if the same equipment malfunctions or is damaged in multiple guest rooms due to the same cause, the grouping unit 208 does not register and manage separate repair tasks for each guest room, but rather registers multiple repair locations and manages them as a single repair task. By managing them together, for example, even if there is no malfunction yet, locations of equipment that may malfunction or be damaged due to the same cause can be registered in the same repair task and addressed before a malfunction occurs.

[0031] The status update unit 210 accepts user input and updates the status indicating the progress of repair and maintenance tasks. As illustrated in Figure 5(b), repair tasks have the following statuses: "Confirmation Required," "Order Feasibility Under Consideration," "Awaiting Approval," "Order Required," "Awaiting Final Confirmation," "Completed," and "Cancelled." These statuses are displayed on the status update screen for selection, and the system also has additional user-addable statuses: "In-House Handling," "Awaiting Vendor Confirmation," and "Vendor Handling." Each status has an implementation deadline (action deadline). The status update unit 210 accepts input of the implementation deadline each time the status is updated. Maintenance tasks have the following statuses: "Period Not Set," "Not Started," "In Progress," "Corrective Action Decision," "Corrective Action in Progress," and "Completed." The status update unit 210 also accepts input of the results of the work or task. Specifically, the status update unit 210 accepts input of content corresponding to each status and attachment of necessary documents. For example, when the status is "awaiting approval," it accepts an attached file of a vendor quote submitted by the user, and when the status is "completed," it accepts an attached file of a completion report. The status update unit 210 stores the status update history in the repair and maintenance DB 600. The task extraction unit 212 extracts repair and maintenance tasks received by the registration acceptance unit 200 based on the status, task completion deadline, or task completion deadline specified by the user. As illustrated in Figures 6(a) and 6(b), the task extraction unit 212 displays the extracted tasks separately as a repair task list or a maintenance task list. For example, the repair task list in Figure 6(b) displays incomplete tasks, tasks due today, expired tasks, and the number of tasks assigned, along with details for each task. The number of tasks assigned refers to tasks associated with the account; if viewed from a contractor's account, the number of tasks associated with the contractor or their representative is displayed. The deadline notification unit 214 issues notifications according to the number of days remaining until the task completion deadline or the work completion deadline managed by the schedule management unit 202.

[0032] The work availability instruction unit 216 indicates whether the site where the contractor will perform the repair or maintenance work, as accepted by the registration acceptance unit 200, is ready to begin work. Specifically, the work availability instruction unit 216 updates the display in real time to show whether a guest room has been checked out or not. For example, the work availability instruction unit 216 displays guest rooms that are available for work and those that are not, using different colors in the guest room list. The authorization granting unit 218 grants the authority to connect to information regarding repair or maintenance work received by the registration acceptance unit 200. Specifically, the authorization granting unit 218 allows the contractor performing the work to connect to the facility maintenance management system 1. More specifically, the authorization granting unit 218 grants specific accounts the authority to view the display indicating whether work is permissible by the work permissibility instruction unit 216, update specific statuses, and input work details. The contractor connects to the facility maintenance management system 1 using the account with the authority granted by the authorization granting unit 218. As illustrated in Figure 7(a), the ability to view tasks can be set for each contractor in the common settings tab.

[0033] The progress display unit 220 displays the progress of work when there are multiple targets for repair or maintenance work, for example, when all guest rooms of a lodging facility are the target. Specifically, as illustrated in Figure 7(b), the progress display unit 220 distinguishes and displays guest rooms in the target location by color-coding whether the work has been completed or not. This allows the user to intuitively grasp the progress of the work. The progress display unit 220 may also display the progress of the work as a percentage. The history search unit 222 searches for records of repair and maintenance work performed in the past. Specifically, as illustrated in Figure 8(a), the history search unit 222 displays records of repair and maintenance work on the user terminal 3 based on a specified classification, keyword, or period. As illustrated in Figure 8(b), the history search unit 222 displays the changes in status over time as detailed history of the repair work. Furthermore, as illustrated in Figure 8(c), the history search unit 222 displays the maintenance work history, associating it with the type of maintenance work (periodic inspection / statutory inspection), maintenance content, frequency, and month of implementation.

[0034] The routine task registration unit 224 accepts registration of routine tasks, which are maintenance tasks that are scheduled to be performed repeatedly. Specifically, the routine task registration unit 224 accepts registration of the routine task name, person in charge, frequency of routine task execution, duration of routine task execution, location of execution, check items, and warning conditions for confirmation results on the task check registration screen illustrated in Figure 9(a), and stores this information in the routine task DB 620. As illustrated in Figure 9(b), the routine task registration unit 224 accepts registration of check items corresponding to each location when there are multiple locations where a routine task is performed for a single routine task. The routine deadline management unit 226 manages the deadlines for routine tasks based on the frequency and duration of the routine tasks received by the routine task registration unit 224. The alert determination unit 228 receives the results of routine tasks and stores them in the routine task DB 620. The alert determination unit 228 also determines whether the confirmation results of the received check items meet the warning conditions. If the warning conditions are met, the alert determination unit 228 issues a warning. Specifically, the warning is an alert display. As illustrated in Figure 9(c), the routine task display unit 230 displays routine tasks received by the routine task registration unit 224 as a list in the "List" section, and displays completed routine tasks and routine tasks that have not yet been performed but whose next scheduled date has arrived in the "Archive" section.

[0035] Figure 10 is a diagram illustrating the functional configuration of the headquarters server 4. As illustrated in Figure 10, the headquarters server 4 in this example has the facility management control program 30 installed. The facility management control program 30 includes a distribution unit 300, a status monitoring unit 302, a classification unit 304, an approval-requiring task extraction unit 306, and a maintenance task planning unit 308. Furthermore, part or all of the facility management program 30 may be implemented using hardware such as an ASIC. The facility management program 30 is also stored on a recording medium such as a CD-ROM and installed on the headquarters server 4 via this recording medium.

[0036] The distribution unit 300 distributes information related to facility maintenance and management to multiple facilities in a single batch. Specifically, the distribution unit 300 distributes the annual maintenance plan, routine tasks, and settings of the facility maintenance management system 1 to the facility management server 2 of the overseeing accommodation facility. In addition, the distribution unit 300 distributes repair work plans to the facility management server 2 of the overseeing accommodation facility based on the repair work that has occurred. This makes it possible to distribute not only pre-planned work plans but also work plans that arise during operation. The Schedule Monitoring Unit 302 monitors the schedules of repair and maintenance tasks managed by multiple accommodation facilities overseen by headquarters. Specifically, the Schedule Monitoring Unit 302 extracts tasks from each facility's repair and maintenance database 600 that have exceeded their action deadlines and completion deadlines. The Schedule Monitoring Unit 302 displays the tasks that have exceeded their deadlines for each accommodation facility. This allows for the evaluation of the facility maintenance management capabilities of each facility. The classification unit 304 classifies the repair work received by the registration acceptance unit 200 based on the cost of carrying out the repair work or the importance of the repair work. Specifically, the classification unit 304 may determine the grade of the repair work based on the cost and the schedule of the repair work and classify the repair work, or it may classify the repair work based on the grade determined by the user at the time of registration acceptance of the repair work. The Approval-Required Task Extraction Unit 306 extracts repair tasks that require approval from headquarters, as requested by each accommodation facility. Specifically, the Approval-Required Task Extraction Unit 306 extracts repair tasks registered at each accommodation facility that have a status of "awaiting approval." As illustrated in Figure 11, the Approval-Required Task Extraction Unit 306 associates the repair tasks extracted by the Approval-Required Task Extraction Unit 306 with each grade classified by the Classification Unit 304 and displays them on the headquarters server 4 or a terminal connected to the headquarters server 4. The Maintenance Planning Department 308 plans facility maintenance operations based on the maintenance operations recorded by the Registration and Reception Department 200, and estimates the budget for maintenance operations based on the actual maintenance operations.

[0037] Figure 12 is a flowchart illustrating the registration process (S10) of repair work by the facility maintenance management system 1. As shown in Figure 12, in step 100 (S100), the user logs in to the facility maintenance management system 1 and determines whether the task to be registered is a repair task or a maintenance task. If the task to be registered is a repair task, the registration reception unit 200 opens the repair task registration screen in the task registration screen switching tab according to the user's operation. In step 105 (S105), the registration reception unit 200 accepts registration from the user of the location of the incident (guest rooms and facilities), the target equipment, the repair details (tasks to be resolved), the importance of the repair work, the status of the repair work (next action to be taken), the action deadline, the action group and person in charge, the names of related contractors (contractors), the name of the registrant, and, if necessary, images of the object to be repaired and audio data of any abnormal sounds. The location setting unit 204 also accepts the user's selection of the location of the object to be repaired (incident location) and associates the registered repair work with the selected location. The registration reception unit 200 assigns an identification number to the accepted repair work and stores it in the repair and maintenance DB 600 as a repair work. In step 110 (S110), the schedule management unit 202 manages the completion deadlines for the received repair work and the task deadlines for each status of the repair work.

[0038] In step 115 (S115), the equipment information synchronization unit 206 associates the repair target information received by the registration reception unit 200 with the repair target information stored in the equipment information DB 610. In step 120 (S120), if there are other repair tasks with the same cause of occurrence (S120: Yes), the registration of the repair task (S10) proceeds to S125; if there are no other repair tasks with the same cause of occurrence (S120: No), the process proceeds to S130. In step 125 (S125), the grouping unit 208 groups repair tasks that have the same cause and the same repair content. Specifically, the grouping unit 208 adds the target location for repair to the already registered repair tasks. The location setting unit 204 associates the location selected by the user with the repair task. In step 130 (S130), the schedule management unit 202 determines whether the task deadline for the repair work and the completion deadline for the repair work have been exceeded. If they have been exceeded (S130: Yes), it proceeds to S135; if they have not been exceeded (S130: No), it proceeds to S140. In step 135 (S135), the schedule management unit 202 displays the repair tasks that have exceeded their deadlines as overdue tasks in the summary display on the top screen of the facility maintenance management system 1. In step 140 (S140), the status update unit 210 accepts a status update based on the progress of the repair work tasks.

[0039] Figure 13 is a flowchart illustrating the registration process (S20) of maintenance tasks by the facility maintenance management system 1. As shown in Figure 13, in step 200 (S200), the user logs in to the facility maintenance management system 1 and determines whether the task to be registered is a repair task or a maintenance task. If the task to be registered is a maintenance task, the registration reception unit 200 opens the maintenance task registration screen in the task registration screen switching tab according to the user's operation. In step 205 (S205), the registration reception unit 200 accepts the classification of maintenance work (periodic inspection / statutory inspection), responsible person, target location, maintenance content, frequency, and selection of the month in which the maintenance work will be performed based on the frequency. The registration reception unit 200 assigns an identification number to the accepted maintenance work and stores it as maintenance work in the repair and maintenance DB 600. In step 210 (S210), the schedule reception unit 202 manages the deadlines based on the month in which the maintenance work is performed, according to the frequency of the registration reception unit 200. In step 215 (S215), the schedule management unit 202 determines whether the deadline has been exceeded. If the deadline has been exceeded (S215:Yes), it proceeds to S220. If the deadline has not been exceeded (S215:No), it proceeds to S225. In step 220 (S220), the schedule management unit 202 displays maintenance tasks that have exceeded their deadlines as tasks that are overdue, and tasks for which no deadline has been set as tasks that require scheduling adjustments, in the summary display on the top screen of the facility maintenance management system 1. In step 225 (S225), the status update unit 210 accepts a status update based on the progress of the maintenance work.

[0040] Figure 14 is a flowchart illustrating the registration process (S30) of routine tasks by the facility maintenance management system 1. As shown in Figure 14, in step 300 (S300), the user logs in to the facility maintenance management system 1 and determines whether the task to be registered is a routine maintenance task, i.e., an everyday maintenance task, or an annually planned maintenance task. If the task to be registered is a routine task, the routine task registration unit 224 opens the task check registration screen in the task check menu according to the user's operation. In step 305 (S305), the routine task reception unit 224 accepts registrations from the user regarding the name, label, person in charge, frequency, repetition period of the routine task, location of execution, and check items to be set according to the location of execution. The routine task reception unit 224 stores the accepted routine tasks in the routine task DB 620. In step 310 (S310), the routine deadline management unit 226 manages deadlines based on the routine work during the repeating period that has been received by the routine work reception unit 224.

[0041] In step 315 (S315), the routine deadline management unit 226 proceeds to S340 if the deadline for the routine work has been exceeded (S315: Yes), and proceeds to S320 if the deadline has not been exceeded (S315: No). In step 320 (S320), the alert determination unit 228 receives the confirmation result that the routine task has been performed and stores it in the routine task DB 620. In step 325 (S325), the alert determination unit 228 determines whether the received confirmation result satisfies the warning conditions. If the warning conditions are met (S325: Yes), the process proceeds to S330; if the warning conditions are not met (S325: No), the process proceeds to S335. In step 330 (S330), the alert determination unit 228 displays an alert indicating the result of the routine work confirmation. In step 335 (S335), the routine task display unit 230 moves the completed routine task to an archive that indicates it is a completed routine task. In step 340 (S340), if the routine task determined by the routine deadline management unit 226 to be overdue has a next scheduled execution within the repeat execution period (S340: Yes), the process proceeds to S335; otherwise, it proceeds to S345 (S340: No). In step 345 (S345), the routine task display unit 230 leaves any unperformed routine tasks that are not scheduled for the next time in the routine task list shown in Figure 9(c), along with an alert display.

[0042] As explained above, the facility maintenance management system 1 in this embodiment incorporates the distinction between repair work and maintenance work into the respective operational rules at the registration stage. As a result, even if the user does not have to manage registration details, schedules, or statuses based on whether the work is repair work or maintenance work, the facility maintenance management system 1 can manage the registration details, schedules, or statuses according to each type of work, as long as the work is differentiated. Furthermore, since the registered repair and maintenance tasks for each accommodation facility are also managed by headquarters, it is possible to monitor the completion of repair and maintenance tasks for each facility. Furthermore, in maintenance operations, routine tasks performed on a daily basis are managed separately from repair and maintenance tasks, and each accommodation facility can establish its own checklist. This allows for the management of routine tasks tailored to the specific characteristics of each accommodation facility.

[0043] (modified version) In the above embodiment, the facility management control program 30 is installed on the headquarters server 4, but it is not limited to this. For example, the facility management program 20 may have the functions of the facility management control program 30, and the range of usable functions may be determined according to the account's authority. [Explanation of symbols]

[0044] 1…Facility maintenance management system 2… Facility management server 3…User terminal 4… Headquarters Server 20…Facility Management Program 30…Facility Management Program 200...Registration Department 202…Schedule Management Department 204...Location setting section 206... Equipment Synchronization Department 208... Grouping Department 210...Status update section 212…Business extraction department 214…Deadline notification section 216...Work availability instruction section 218...Authorization Department 220...Progress display section 222...History Search Section 224... Routine Task Registration Department 226… Routine Deadline Management Department 228... Alert determination unit 230... Routine task display unit 300...Distribution Department 302... Schedule Monitoring Department 304...Classification section 306...Department for Extracting Approval-Required Tasks 308... Maintenance Operations Planning Department 600... Repair and Maintenance Database 610…Equipment Information Database 620...Routine Task Database

Claims

1. Regarding the repair and maintenance management of facilities, the registration department accepts registrations for work related to either unexpected repair work or pre-scheduled maintenance work. The schedule management unit manages the schedule or status of the work received by the aforementioned registration acceptance unit. It has, The aforementioned schedule management unit receives the schedule or status of the repair work individually for each repair work, and receives the schedule or status of the maintenance work in a standardized manner. Facility maintenance management system.

2. Regarding the repair and maintenance management of facilities, the registration department accepts registrations of services in relation to whether or not a contractor is involved, The schedule management unit manages the schedule or status of the work received by the aforementioned registration acceptance unit. It has, The aforementioned schedule management department receives the schedule or status of tasks involving the contractor on an individual basis for each task involving the contractor, and receives the schedule or status of tasks not involving the contractor in a standardized manner. Facility maintenance management system.

3. The repair work received by the aforementioned registration acceptance department is grouped into a grouping department based on the cause of the repair, The location setting unit associates the repair work received by the registration acceptance unit with the location to be repaired. It further possesses, The location setting unit associates all locations to be repaired with the tasks grouped by the grouping unit. A facility maintenance management system according to claim 1 or claim 2.

4. The aforementioned registration reception department accepts the items to be repaired for repair work or maintenance work. A facility information storage unit that manages the facility's equipment, The equipment information synchronization unit synchronizes the target of repair or maintenance work received by the registration acceptance unit with the target information stored in the equipment information storage unit. It further possesses, The aforementioned equipment information synchronization unit synchronizes the updated information on the equipment to be repaired with the information on the equipment to be repaired stored in the aforementioned equipment information storage unit when the information on the equipment to be repaired received by the registration acceptance unit is updated. A facility maintenance management system according to claim 1 or claim 2.

5. The aforementioned Schedule Management Department extracts tasks that should be performed within a specified period including the current date, newly registered tasks, tasks whose content has been updated, and tasks that have already been performed from the tasks received by the Registration Acceptance Department. The aforementioned schedule management unit displays all extracted tasks in association with the type of each task. The facility maintenance management system according to claim 1 or 2.

6. Regarding repair or maintenance work accepted by the registration acceptance unit, a work feasibility instruction unit indicates whether the site where the contractor will perform the work is in a condition to begin work, An authorization granting unit grants the authority to connect to information regarding repair or maintenance work received by the aforementioned registration acceptance unit. It further possesses, The contractor connects to the information indicating whether work is possible or not, as indicated by the work feasibility instruction unit, using the authority granted by the authority granting unit. A facility maintenance management system according to claim 1 or claim 2.

7. Based on the maintenance work records received by the aforementioned registration reception department, the maintenance work planning department plans the facility's maintenance work. It further possesses, The Maintenance Planning Department estimates the budget for maintenance or repair work based on the actual maintenance or repair work received by the Registration Acceptance Department. A facility maintenance management system according to claim 1 or claim 2.

8. A distribution unit that distributes plans for facility repair or maintenance work to multiple facilities in a single batch. Furthermore, it has A facility maintenance management system according to claim 1 or claim 2.

9. The Schedule Monitoring Department monitors the schedules for repair or maintenance work managed for each facility, as registered by the Registration Reception Department. It further possesses, The aforementioned schedule monitoring unit extracts tasks that have exceeded their deadlines for each facility. A facility maintenance management system according to claim 1 or claim 2.

10. A unit for extracting repair work that requires approval is used, A classification department classifies the repair work received by the aforementioned registration department based on the cost of carrying out the repair work and the importance of the repair work. It further possesses, The repair work extracted by the aforementioned approval-requiring work extraction unit is displayed according to the grade classified by the aforementioned classification unit. The facility maintenance management system according to claim 1 or 2.

11. The Routine Task Registration Department accepts registrations for routine tasks, which are among the maintenance tasks that are scheduled to be performed repeatedly. It further possesses, The aforementioned routine task registration unit accepts registration of confirmation items specific to each location when there are multiple locations where a single routine task is performed. The facility maintenance management system according to claim 1 or 2.

12. A computer accepts registration of tasks related to the repair or maintenance management of a facility, associating them with either unexpected repair tasks or pre-scheduled maintenance tasks. A computer manages the schedule or status of the business accepted in the registration acceptance step, and It has, In the aforementioned schedule management step, the schedule or status of the repair work is received individually for each repair work, and the schedule or status of the maintenance work is received in a standardized manner. Facility maintenance and management methods.

13. Regarding the repair and maintenance management of facilities, a registration acceptance step is provided for accepting registration of work related to either unexpected repair work or pre-scheduled maintenance work. A schedule management step for managing the schedule or status of the work accepted in the registration acceptance step, Have the computer run it, The aforementioned schedule management unit receives the schedule or status of the repair work individually for each repair work, and receives the schedule or status of the maintenance work in a standardized manner. program.

14. A computer accepts registration of business operations in relation to the repair or maintenance management of facilities, linking it to whether or not a contractor is involved. A computer manages the schedule or status of the business accepted in the registration acceptance step, and It has, In the aforementioned schedule management step, the schedule or status of tasks involving the contractor is received individually for each task involving the contractor, while the schedule or status of tasks not involving the contractor is received in a standardized manner. Facility maintenance and management methods.

15. Regarding the repair and maintenance management of facilities, a registration acceptance step is used to accept registration of services, linked to whether or not a contractor is involved. A schedule management step for managing the schedule or status of the work accepted in the registration acceptance step, Have the computer run it, In the aforementioned schedule management step, the schedule or status of tasks involving the contractor is received individually for each task involving the contractor, while the schedule or status of tasks not involving the contractor is received in a standardized manner. program.

Images